This is an automated email from the git hooks/post-receive script.
tcwg-buildslave pushed a change to branch linaro-local/ci/tcwg_gnu_native_check_binutils/master-arm in repository toolchain/ci/base-artifacts.
discards 0397b5e6cd 103: onsuccess: #529: 1: Success after binutils/gcc/linux/gl [...] discards 46e2321990 102: onsuccess: #527: 1: Success after binutils: 5 commits discards bf7c1c1761 101: onsuccess: #524: 1: Success after binutils: 2 commits discards 53761f254d 100: onsuccess: #521: 1: Success after binutils: 10 commits discards d102ac9acd 99: onsuccess: #519: 1: Success after binutils/gcc/linux/gli [...] discards a4cc560623 98: onsuccess: #518: 1: Success after binutils/gcc/linux/gli [...] discards 7b6045c49a 97: onsuccess: #517: 1: Success after binutils/gcc/linux/gli [...] discards 37f05d99f0 96: onsuccess: #516: 1: Success after binutils/gcc/linux/gli [...] discards 66a61bcb81 95: onsuccess: #515: 1: Success after binutils/gcc/linux/gdb [...] discards c416b9fbdb 94: onsuccess: #514: 1: Success after binutils/gcc/linux/gdb [...] discards 454dee972e 93: onsuccess: #513: 1: Success after binutils/gcc/linux/gli [...] discards e616f97b5d 92: onsuccess: #512: 1: Success after binutils/gcc/linux/gli [...] discards 59bef7dbe3 91: onsuccess: #511: 1: Success after linux: 27 commits discards e780b333d8 90: onsuccess: #510: 1: Success after glibc: 5 commits discards 9e79d8a2a3 89: onsuccess: #508: 1: Success after binutils: 12 commits discards 33b51d2482 88: onsuccess: #506: 1: Success after linux: 34 commits discards 69ef52633c 87: onsuccess: #505: 1: Success after glibc: 7 commits discards 0d05c33136 86: onsuccess: #503: 1: Success after binutils: 12 commits discards 2bfdb70f51 85: onsuccess: #501: 1: Success after binutils/gcc/linux/gli [...] discards 05d8a2f75c 84: onsuccess: #500: 1: Success after binutils/gcc/linux/gli [...] discards 21dfdcf4c2 83: onsuccess: #499: 1: Success after binutils/gcc/linux/gdb [...] discards f171625652 82: onsuccess: #498: 1: Success after binutils/gcc/linux/gli [...] discards d0c030e535 81: onsuccess: #497: 1: Success after binutils/gcc/linux/gli [...] discards 346dcb7c4f 80: onsuccess: #496: 1: Success after binutils/gcc/linux/gli [...] discards 0e5a32675e 79: onsuccess: #495: 1: Success after binutils/gcc/linux/gli [...] discards 15fdb2bcc7 78: onsuccess: #494: 1: Success after binutils/gcc/linux/gli [...] discards ce2bb066df 77: onsuccess: #493: 1: Success after binutils/gcc/linux/gdb [...] discards 207732a32e 76: onsuccess: #492: 1: Success after binutils/gcc/linux/gdb [...] discards 54ef0a0879 75: onsuccess: #491: 1: Success after binutils/gcc/linux/gdb [...] discards acba51cc47 74: onsuccess: #490: 1: Success after binutils/gcc/linux/gli [...] discards 43d73c37b1 73: onsuccess: #489: 1: Success after binutils/gcc/glibc/gdb [...] discards de940e7bff 72: onsuccess: #488: 1: Success after binutils/gcc/linux/gli [...] discards 03cac2eb80 71: onsuccess: #487: 1: Success after binutils/gcc/linux/gdb [...] discards 08a5d4a616 70: onsuccess: #486: 1: Success after binutils/gcc/linux/gli [...] discards d9e2a35db3 69: onsuccess: #485: 1: Success after binutils/gcc/linux/gdb [...] discards 0290be894b 68: onsuccess: #484: 1: Success after binutils/gcc/linux/gli [...] discards 39ce2e638d 67: onsuccess: #483: 1: Success after binutils/gcc/linux/gli [...] discards 0e6be98d63 66: onsuccess: #482: 1: Success after binutils/gcc/linux/gli [...] discards 277ae56897 65: onsuccess: #481: 1: Success after binutils/gcc/linux/gdb [...] discards 439eae1ea2 64: onsuccess: #480: 1: Success after binutils/gcc/linux/gli [...] discards 9114fab29d 63: onsuccess: #479: 1: Success after binutils/gcc/linux/gli [...] discards b746e69b62 62: onsuccess: #478: 1: Success after binutils/gcc/linux/gli [...] discards 060aa45107 61: onsuccess: #477: 1: Success after binutils/gcc/linux/gli [...] discards a1df7d656d 60: onsuccess: #476: 1: Success after binutils/gcc/linux/gli [...] discards e670ea99bc 59: onsuccess: #475: 1: Success after binutils/gcc/linux/gli [...] discards 532dfb1401 58: onsuccess: #474: 1: Success after binutils/gcc/linux/gli [...] discards 5ec3023b3a 57: onsuccess: #473: 1: Success after binutils/gcc/linux/gli [...] discards efed2e5493 56: onsuccess: #472: 1: Success after binutils/gcc/linux/gdb [...] discards 9955f27fb9 55: onsuccess: #471: 1: Success after binutils/gcc/linux/gli [...] discards 284f6ea497 54: onsuccess: #470: 1: Success after binutils/gcc/linux/gli [...] discards 397ee8aca5 53: onsuccess: #469: 1: Success after binutils/gcc/linux/gli [...] discards fe74caf74a 52: onsuccess: #467: 1: Success after binutils: 9 commits discards 3534f6c2de 51: onsuccess: #464: 1: Success after binutils: 6 commits discards d36a7ed311 50: onsuccess: #461: 1: Success after binutils: 12 commits discards 6a573d404c 49: onsuccess: #459: 1: Success after binutils/gcc/linux/gdb [...] discards 9e2611e795 48: onsuccess: #458: 1: Success after binutils/gcc/linux/gdb [...] discards b3c2bb16fd 47: onsuccess: #457: 1: Success after binutils/gcc/linux/gli [...] discards f62c40e6d9 46: onsuccess: #455: 1: Success after binutils/gcc/linux/gli [...] discards cb7024ee0b 45: onsuccess: #454: 1: Success after binutils/gcc/linux/gli [...] discards b4576c0c6d 44: onsuccess: #453: 1: Success after binutils/gcc/glibc/gdb [...] discards 4e988a5686 43: onsuccess: #452: 1: Success after binutils/gcc/linux/gdb [...] discards 20e989fd38 42: onsuccess: #451: 1: Success after binutils/gcc/glibc/gdb [...] discards 515eee1195 41: onsuccess: #450: 1: Success after binutils/gcc/linux/gli [...] discards de0b711a74 40: onsuccess: #449: 1: Success after glibc-2.36.9000-121-g5 [...] discards bb7703e8d1 39: onsuccess: #447: 1: Success after binutils: 5 commits discards 728e265140 38: onsuccess: #445: 1: Success after glibc-2.36.9000-120-g9 [...] discards ae58d26d97 37: onsuccess: #443: 1: Success after binutils: 2 commits discards 638811da99 36: onsuccess: #441: 1: Success after binutils/gcc/linux/gli [...] discards 54008a08e6 35: onsuccess: #440: 1: Success after binutils/gcc/linux/gli [...] discards 4e1e81ecb2 34: onsuccess: #439: 1: Success after binutils/gcc/linux/gli [...] discards 416890ada3 33: onsuccess: #438: 1: Success after binutils/gcc/linux/gdb [...] discards aa0dc9e044 32: onsuccess: #437: 1: Success after binutils/gcc/linux/gli [...] discards 623545539e 31: onsuccess: #436: 1: Success after binutils/gcc/linux/gli [...] discards 944c615913 30: onsuccess: #435: 1: Success after binutils/gcc/glibc/gdb [...] discards 1ff06668e6 29: onsuccess: #434: 1: Success after binutils/gcc/linux/gli [...] discards 8124461c7f 28: onsuccess: #433: 1: Success after binutils/gcc/linux/gli [...] discards 59c578fabf 27: onsuccess: #432: 1: Success after binutils/gcc/linux/gdb [...] discards df6a83e116 26: onsuccess: #431: 1: Success after binutils/gcc/linux/gdb [...] discards a9662f5457 25: onsuccess: #430: 1: Success after binutils/gcc/linux/gdb [...] discards eb9b2725b1 24: onsuccess: 1: Success after binutils/gcc/linux/gdb: 127 commits discards 53dee40fa9 23: onsuccess: 1: Success after binutils/gcc/linux/glibc/gdb [...] discards 4e09fd348b 22: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] discards 2704e46a0a 21: onsuccess: 1: Successful build after linux: 79 commits discards bece752b79 20: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 55a81c1fc8 19: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 584d1eb4ed 18: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards f1d571929e 17: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] discards 7b7c513c2c 16: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 53124c383b 15: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 70057033f0 14: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards fc09414952 13: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 3f155f8aed 12: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards d41bf13ed4 11: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 75126fc9b3 10: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards fe1b70fb57 9: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] discards 95e3d67ac3 8: onsuccess: 1: Successful build after binutils/gcc/glibc/g [...] discards 40b8d47773 7: onsuccess: binutils-gcc-linux-glibc-gdb: 1 discards a5e1013381 6: onsuccess: binutils-gcc-linux-glibc-gdb: 1 discards 46f5b975a8 5: onsuccess: binutils-gcc-linux-glibc-gdb: 1 discards cce1a31c31 4: onsuccess: binutils-gcc-linux-glibc-gdb: 1 discards 6a31cd0981 3: onsuccess: binutils-gcc-linux-glibc-gdb: 1 new 5906e32e98 3: onsuccess: binutils-gcc-linux-glibc-gdb: 1 new 718558ddf8 4: onsuccess: binutils-gcc-linux-glibc-gdb: 1 new c49d0f6e98 5: onsuccess: binutils-gcc-linux-glibc-gdb: 1 new e78670cfb8 6: onsuccess: binutils-gcc-linux-glibc-gdb: 1 new 273ef92bb3 7: onsuccess: binutils-gcc-linux-glibc-gdb: 1 new d89b802ef2 8: onsuccess: 1: Successful build after binutils/gcc/glibc/g [...] new 67d7863da2 9: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] new a20e5598fd 10: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new d456b90bd2 11: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 3cbfa1e704 12: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 238d00be32 13: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new de39579727 14: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 79eca72610 15: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 7e5e8bbbe2 16: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 3bb8a39b30 17: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] new ed2edbe6d0 18: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new ed91bee117 19: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new a4e1be7597 20: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new ba851123ee 21: onsuccess: 1: Successful build after linux: 79 commits new 79d9663f89 22: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] new 60083a54f3 23: onsuccess: 1: Success after binutils/gcc/linux/glibc/gdb [...] new 452845463d 24: onsuccess: 1: Success after binutils/gcc/linux/gdb: 127 commits new 2a0c81fadd 25: onsuccess: #430: 1: Success after binutils/gcc/linux/gdb [...] new d4c1e084c3 26: onsuccess: #431: 1: Success after binutils/gcc/linux/gdb [...] new 535cacc57a 27: onsuccess: #432: 1: Success after binutils/gcc/linux/gdb [...] new fefc492f06 28: onsuccess: #433: 1: Success after binutils/gcc/linux/gli [...] new 985c8980ba 29: onsuccess: #434: 1: Success after binutils/gcc/linux/gli [...] new aba326cff4 30: onsuccess: #435: 1: Success after binutils/gcc/glibc/gdb [...] new 11ce999149 31: onsuccess: #436: 1: Success after binutils/gcc/linux/gli [...] new cc762ebd0d 32: onsuccess: #437: 1: Success after binutils/gcc/linux/gli [...] new 586eda8f4e 33: onsuccess: #438: 1: Success after binutils/gcc/linux/gdb [...] new 5531ec717e 34: onsuccess: #439: 1: Success after binutils/gcc/linux/gli [...] new e771176691 35: onsuccess: #440: 1: Success after binutils/gcc/linux/gli [...] new a7cabc71a4 36: onsuccess: #441: 1: Success after binutils/gcc/linux/gli [...] new 09e6af5d51 37: onsuccess: #443: 1: Success after binutils: 2 commits new c2f75ae1be 38: onsuccess: #445: 1: Success after glibc-2.36.9000-120-g9 [...] new f1e034ede8 39: onsuccess: #447: 1: Success after binutils: 5 commits new f0da4e9a41 40: onsuccess: #449: 1: Success after glibc-2.36.9000-121-g5 [...] new 2a2b09d867 41: onsuccess: #450: 1: Success after binutils/gcc/linux/gli [...] new 7207fa84f2 42: onsuccess: #451: 1: Success after binutils/gcc/glibc/gdb [...] new cc4c93df51 43: onsuccess: #452: 1: Success after binutils/gcc/linux/gdb [...] new b0c5ecef28 44: onsuccess: #453: 1: Success after binutils/gcc/glibc/gdb [...] new b4a46c1d17 45: onsuccess: #454: 1: Success after binutils/gcc/linux/gli [...] new 4bbc779061 46: onsuccess: #455: 1: Success after binutils/gcc/linux/gli [...] new 3452d85aaf 47: onsuccess: #457: 1: Success after binutils/gcc/linux/gli [...] new d7e5eab694 48: onsuccess: #458: 1: Success after binutils/gcc/linux/gdb [...] new 395fe9d643 49: onsuccess: #459: 1: Success after binutils/gcc/linux/gdb [...] new 494a486295 50: onsuccess: #461: 1: Success after binutils: 12 commits new 0b6fc26ccd 51: onsuccess: #464: 1: Success after binutils: 6 commits new e0a825116a 52: onsuccess: #467: 1: Success after binutils: 9 commits new 3af8bde19e 53: onsuccess: #469: 1: Success after binutils/gcc/linux/gli [...] new 4c5421d35c 54: onsuccess: #470: 1: Success after binutils/gcc/linux/gli [...] new 217c728e3a 55: onsuccess: #471: 1: Success after binutils/gcc/linux/gli [...] new ac59268c63 56: onsuccess: #472: 1: Success after binutils/gcc/linux/gdb [...] new 7939d69774 57: onsuccess: #473: 1: Success after binutils/gcc/linux/gli [...] new d4e53223de 58: onsuccess: #474: 1: Success after binutils/gcc/linux/gli [...] new 542590c32a 59: onsuccess: #475: 1: Success after binutils/gcc/linux/gli [...] new c3f3e65550 60: onsuccess: #476: 1: Success after binutils/gcc/linux/gli [...] new b150f98a46 61: onsuccess: #477: 1: Success after binutils/gcc/linux/gli [...] new 01a931bdc1 62: onsuccess: #478: 1: Success after binutils/gcc/linux/gli [...] new c3844ed7f3 63: onsuccess: #479: 1: Success after binutils/gcc/linux/gli [...] new a55d79240f 64: onsuccess: #480: 1: Success after binutils/gcc/linux/gli [...] new a093ea2332 65: onsuccess: #481: 1: Success after binutils/gcc/linux/gdb [...] new dd3fd44320 66: onsuccess: #482: 1: Success after binutils/gcc/linux/gli [...] new 283c31ca41 67: onsuccess: #483: 1: Success after binutils/gcc/linux/gli [...] new b344b6004a 68: onsuccess: #484: 1: Success after binutils/gcc/linux/gli [...] new 4f359f576a 69: onsuccess: #485: 1: Success after binutils/gcc/linux/gdb [...] new a9e4878636 70: onsuccess: #486: 1: Success after binutils/gcc/linux/gli [...] new cf99d5afb7 71: onsuccess: #487: 1: Success after binutils/gcc/linux/gdb [...] new 6227de7deb 72: onsuccess: #488: 1: Success after binutils/gcc/linux/gli [...] new 4949bf78b4 73: onsuccess: #489: 1: Success after binutils/gcc/glibc/gdb [...] new 667dd99233 74: onsuccess: #490: 1: Success after binutils/gcc/linux/gli [...] new 53422731ae 75: onsuccess: #491: 1: Success after binutils/gcc/linux/gdb [...] new 91a1abb711 76: onsuccess: #492: 1: Success after binutils/gcc/linux/gdb [...] new dac9148492 77: onsuccess: #493: 1: Success after binutils/gcc/linux/gdb [...] new 53556b6010 78: onsuccess: #494: 1: Success after binutils/gcc/linux/gli [...] new f93870e2fe 79: onsuccess: #495: 1: Success after binutils/gcc/linux/gli [...] new d152630107 80: onsuccess: #496: 1: Success after binutils/gcc/linux/gli [...] new 535e47028c 81: onsuccess: #497: 1: Success after binutils/gcc/linux/gli [...] new 015ae91692 82: onsuccess: #498: 1: Success after binutils/gcc/linux/gli [...] new 76cb34aee7 83: onsuccess: #499: 1: Success after binutils/gcc/linux/gdb [...] new 6bfe4e23ea 84: onsuccess: #500: 1: Success after binutils/gcc/linux/gli [...] new 7560854d27 85: onsuccess: #501: 1: Success after binutils/gcc/linux/gli [...] new b19bb60b07 86: onsuccess: #503: 1: Success after binutils: 12 commits new db27699b1a 87: onsuccess: #505: 1: Success after glibc: 7 commits new a68f199d2e 88: onsuccess: #506: 1: Success after linux: 34 commits new 46480c8800 89: onsuccess: #508: 1: Success after binutils: 12 commits new 3562aa0025 90: onsuccess: #510: 1: Success after glibc: 5 commits new 1e46606bea 91: onsuccess: #511: 1: Success after linux: 27 commits new 5097a25c6c 92: onsuccess: #512: 1: Success after binutils/gcc/linux/gli [...] new 692900e66a 93: onsuccess: #513: 1: Success after binutils/gcc/linux/gli [...] new 7cf33a9944 94: onsuccess: #514: 1: Success after binutils/gcc/linux/gdb [...] new 2ac9b3bb53 95: onsuccess: #515: 1: Success after binutils/gcc/linux/gdb [...] new 13194db21b 96: onsuccess: #516: 1: Success after binutils/gcc/linux/gli [...] new c423d6654d 97: onsuccess: #517: 1: Success after binutils/gcc/linux/gli [...] new 015cd8a847 98: onsuccess: #518: 1: Success after binutils/gcc/linux/gli [...] new 44f550cf75 99: onsuccess: #519: 1: Success after binutils/gcc/linux/gli [...] new 42245a364b 100: onsuccess: #521: 1: Success after binutils: 10 commits new 1a9861129a 101: onsuccess: #524: 1: Success after binutils: 2 commits new 0e675a0efc 102: onsuccess: #527: 1: Success after binutils: 5 commits new 619a4d7ddb 103: onsuccess: #529: 1: Success after binutils/gcc/linux/gl [...] new c35199a524 104: onsuccess: #530: 1: Success after gcc: 7 commits
This update added new revisions after undoing existing revisions. That is to say, some revisions that were in the old version of the branch are not in the new version. This situation occurs when a user --force pushes a change and generates a repository containing something like this:
* -- * -- B -- O -- O -- O (0397b5e6cd) \ N -- N -- N refs/heads/linaro-local/ci/tcwg_gnu_native_check_binutil [...]
You should already have received notification emails for all of the O revisions, and so the following emails describe only the N revisions from the common base, B.
Any revisions marked "omits" are not gone; other references still refer to them. Any revisions marked "discards" are gone forever.
The 102 revisions listed above as "new" are entirely new to this repository and will be described in separate emails. The revisions listed as "adds" were already present in the repository and have only been added to this reference.
Summary of changes: 01-reset_artifacts/console.log.xz | Bin 1672 -> 1744 bytes 02-prepare_abe/console.log.xz | Bin 2756 -> 2732 bytes 03-build_abe-binutils/console.log.xz | Bin 53460 -> 52736 bytes 04-build_abe-gcc/console.log.xz | Bin 236744 -> 234948 bytes 05-clean_sysroot/console.log.xz | Bin 316 -> 316 bytes 06-build_abe-linux/console.log.xz | Bin 9096 -> 8832 bytes 07-build_abe-glibc/console.log.xz | Bin 238984 -> 236372 bytes 08-build_abe-gdb/console.log.xz | Bin 53180 -> 52408 bytes 09-build_abe-dejagnu/console.log.xz | Bin 3924 -> 3872 bytes 10-build_abe-check_binutils/console.log.xz | Bin 2104 -> 2068 bytes 11-check_regression/console.log.xz | Bin 6536 -> 4872 bytes 11-check_regression/results.compare | 8 +- 11-check_regression/results.compare2 | 30 +-- 12-update_baseline/console.log | 64 +++--- dashboard/dashboard-generate.sh | 2 +- git/gcc_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 2 +- mail/mail-subject.txt | 2 +- manifest.sh | 18 +- sumfiles/binutils.log.xz | Bin 62220 -> 62304 bytes sumfiles/binutils.sum | 62 +++--- sumfiles/gas.log.xz | Bin 98036 -> 98092 bytes sumfiles/gas.sum | 270 +++++++++++----------- sumfiles/ld.log.xz | Bin 131508 -> 131580 bytes sumfiles/ld.sum | 344 ++++++++++++++--------------- 26 files changed, 395 insertions(+), 411 deletions(-)