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-aarch64 in repository toolchain/ci/base-artifacts.
discards 7ac48b318b 100: onsuccess: #625: 1: Success after binutils/gcc/linux/gd [...] discards 3e6c4bb595 99: onsuccess: #624: 1: Success after binutils/gcc/linux/gli [...] discards de0d545783 98: onsuccess: #623: 1: Success after binutils/gcc/linux/gdb [...] discards 7a5f957ded 97: onsuccess: #622: 1: Success after binutils/gcc/gdb: 8 commits discards 06faaa9b0a 96: onsuccess: #621: 1: Success after binutils/gcc/linux/gli [...] discards 6f09db6f9d 95: onsuccess: #619: 1: Success after binutils: 5 commits discards d995c0bdbd 94: onsuccess: #616: 1: Success after binutils: 2 commits discards d4046d0752 93: onsuccess: #613: 1: Success after binutils: 19 commits discards e7cf7ddf51 92: onsuccess: #611: 1: Success after binutils/gcc/linux/gli [...] discards ab4938d32e 91: onsuccess: #610: 1: Success after binutils/gcc/linux/gli [...] discards d6e1cb883a 90: onsuccess: #606: 1: Success after binutils/gcc/linux/gli [...] discards 570ca91c28 89: onsuccess: #605: 1: Success after binutils/gcc/linux/gdb [...] discards 4a74440ace 88: onsuccess: #604: 1: Success after binutils/gcc/linux/gdb [...] discards de33837e26 87: onsuccess: #603: 1: Success after binutils/gcc/linux/gli [...] discards 0456eb22d0 86: onsuccess: #602: 1: Success after binutils/gcc/linux/gli [...] discards da8d9a2ae6 85: onsuccess: #601: 1: Success after binutils/gcc/linux/gli [...] discards 55984ed3d7 84: onsuccess: #600: 1: Success after binutils/gcc/linux/gli [...] discards 1647271b6a 83: onsuccess: #599: 1: Success after binutils/gcc/linux/gli [...] discards 4cda86bd7b 82: onsuccess: #598: 1: Success after binutils/gcc/linux/gli [...] discards 321804399a 81: onsuccess: #597: 1: Success after binutils/gcc/linux/gdb [...] discards 25904ecb6d 80: onsuccess: #596: 1: Success after binutils/gcc/linux/gli [...] discards de8da6584f 79: onsuccess: #595: 1: Success after binutils/gcc/linux/gli [...] discards 3806e2a185 78: onsuccess: #594: 1: Success after binutils/gcc/linux/gli [...] discards 6f6b10fd0d 77: onsuccess: #593: 1: Success after binutils/gcc/linux/gli [...] discards 1c587624c2 76: onsuccess: #592: 1: Success after linux: 63 commits discards 1e0b75373b 75: onsuccess: #591: 1: Success after gcc: 25 commits discards e7a369cb20 74: onsuccess: #590: 1: Success after binutils: 16 commits discards 6221f35189 73: onsuccess: #588: 1: Success after binutils/gcc/linux/gdb [...] discards 23a85f8863 72: onsuccess: #587: 1: Success after binutils/gcc/linux/gdb [...] discards baff8366de 71: onsuccess: #586: 1: Success after binutils/gcc/linux/gdb [...] discards 25482e1013 70: onsuccess: #585: 1: Success after binutils/gcc/linux/gli [...] discards 98769f11df 69: onsuccess: #584: 1: Success after binutils/gcc/glibc/gdb [...] discards 529a99e8e1 68: onsuccess: #583: 1: Success after binutils/gcc/linux/gli [...] discards 008d47f87e 67: onsuccess: #582: 1: Success after binutils/gcc/linux/gdb [...] discards 639f93d51d 66: onsuccess: #581: 1: Success after binutils/gcc/linux/gli [...] discards 909a71881c 65: onsuccess: #580: 1: Success after binutils/gcc/linux/gdb [...] discards 49c755dfe7 64: onsuccess: #579: 1: Success after binutils/gcc/linux/gli [...] discards f87713b2a3 63: onsuccess: #577: 1: Success after binutils/gcc/linux/gli [...] discards bfe719d35d 62: onsuccess: #576: 1: Success after binutils/gcc/linux/gdb [...] discards 96426f1e3b 61: onsuccess: #575: 1: Success after binutils/gcc/linux/gli [...] discards 9d82018337 60: onsuccess: #574: 1: Success after binutils/gcc/linux/gli [...] discards 3d5eb6294f 59: onsuccess: #573: 1: Success after binutils/gcc/linux/gli [...] discards f1f1fa56f2 58: onsuccess: #572: 1: Success after binutils/gcc/linux/gli [...] discards 2f1c349472 57: onsuccess: #571: 1: Success after binutils/gcc/linux/gli [...] discards ad179c8188 56: onsuccess: #570: 1: Success after binutils/gcc/linux/gli [...] discards 4ef785899c 55: onsuccess: #569: 1: Success after binutils/gcc/linux/gli [...] discards 691321a263 54: onsuccess: #568: 1: Success after binutils/gcc/linux/gli [...] discards ee3772a636 53: onsuccess: #567: 1: Success after binutils/gcc/linux/gdb [...] discards 4891646b1d 52: onsuccess: #566: 1: Success after binutils/gcc/linux/gli [...] discards 4bf695ffed 51: onsuccess: #565: 1: Success after binutils/gcc/linux/gli [...] discards 023a1f39d1 50: onsuccess: #564: 1: Success after binutils/gcc/linux/gli [...] discards cd350c6106 49: onsuccess: #562: 1: Success after binutils: 9 commits discards 1eebaedd7e 48: onsuccess: #559: 1: Success after binutils: 6 commits discards e1643cbe02 47: onsuccess: #556: 1: Success after binutils: 12 commits discards 2009bbae96 46: onsuccess: #554: 1: Success after binutils/gcc/linux/gdb [...] discards 2c501c2e7b 45: onsuccess: #553: 1: Success after binutils/gcc/linux/gdb [...] discards 1e6aa48680 44: onsuccess: #552: 1: Success after binutils/gcc/linux/gli [...] discards ec027cc4a1 43: onsuccess: #550: 1: Success after binutils/gcc/linux/gli [...] discards 8ebbee122f 42: onsuccess: #549: 1: Success after binutils/gcc/linux/gli [...] discards 1fdef755c0 41: onsuccess: #548: 1: Success after binutils/gcc/glibc/gdb [...] discards c5c710c35f 40: onsuccess: #547: 1: Success after binutils/gcc/linux/gdb [...] discards e6c4e91829 39: onsuccess: #546: 1: Success after binutils/gcc/glibc/gdb [...] discards 7339c1afd8 38: onsuccess: #545: 1: Success after binutils/gcc/linux/gli [...] discards 9b00ed62bb 37: onsuccess: #544: 1: Success after binutils/gcc/glibc/gdb [...] discards 588a7f74e2 36: onsuccess: #543: 1: Success after binutils/gcc/linux/gli [...] discards 81fe305db3 35: onsuccess: #542: 1: Success after binutils/gcc/linux/gli [...] discards ea3ea85c38 34: onsuccess: #541: 1: Success after binutils/gcc/linux/gli [...] discards fb393d3598 33: onsuccess: #540: 1: Success after binutils/gcc/linux/gli [...] discards 8ee0a86fba 32: onsuccess: #539: 1: Success after binutils/gcc/linux/gdb [...] discards 53211a05a7 31: onsuccess: #538: 1: Success after binutils/gcc/linux/gli [...] discards 37d71e25b3 30: onsuccess: #537: 1: Success after binutils/gcc/linux/gli [...] discards 42b830e919 29: onsuccess: #536: 1: Success after binutils/gcc/glibc/gdb [...] discards 1fb8b18037 28: onsuccess: #535: 1: Success after binutils/gcc/linux/gli [...] discards 1c39e30dca 27: onsuccess: #534: 1: Success after binutils/gcc/linux/gli [...] discards 2b7dc79fd9 26: onsuccess: #533: 1: Success after binutils/gcc/linux/gdb [...] discards d7d9e5d486 25: onsuccess: #532: 1: Success after binutils/gcc/linux/gdb [...] discards c9a38bae1f 24: onsuccess: 1: Success after binutils/gcc/linux/gdb: 216 commits discards 4405d79f63 23: onsuccess: 1: Success after binutils/gcc/linux/gdb: 129 commits discards bc1040cd5d 22: onsuccess: 1: Success after binutils/gcc/linux/glibc/gdb [...] discards 8a972104f0 21: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 494b8a90d9 20: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 2460cc9ce4 19: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 9da3ba4092 18: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards b2071437ea 17: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] discards 8ef9d39ad6 16: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 74fd2e94cf 15: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 1279ab4d8f 14: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards dd5d849055 13: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 700f38553e 12: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 01d5c44972 11: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 8c4efd3e88 10: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 9bc20146b7 9: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] discards bc3aeb97c9 8: onsuccess: binutils-gcc-linux-glibc-gdb: 1 discards 02bdc5f23a 7: onsuccess: binutils-gcc-linux-glibc-gdb: 1 discards adcbe767ce 6: onsuccess: binutils-gcc-linux-glibc-gdb: 1 discards f789cc2db4 5: onsuccess: binutils-gcc-linux-glibc-gdb: 1 discards d05a583657 4: onsuccess: binutils-gcc-linux-glibc-gdb: 1 discards 637c335240 3: onsuccess: binutils-gcc-linux-glibc-gdb: 1 discards c7b6c5821b 2: onsuccess: binutils-gcc-linux-glibc-gdb: 1 discards ca26fa1d5c 1: onsuccess: binutils-gcc-linux-glibc-gdb: 1 discards 1f54c02c2a 0: update: binutils-gcc-linux-glibc-gdb: 1 new 4247311958 0: update: binutils-gcc-linux-glibc-gdb: 1 new 63754f1afe 1: onsuccess: binutils-gcc-linux-glibc-gdb: 1 new d07800b998 2: onsuccess: binutils-gcc-linux-glibc-gdb: 1 new c083b558ed 3: onsuccess: binutils-gcc-linux-glibc-gdb: 1 new 0e8cf091da 4: onsuccess: binutils-gcc-linux-glibc-gdb: 1 new 068fcee0e6 5: onsuccess: binutils-gcc-linux-glibc-gdb: 1 new 10424af18a 6: onsuccess: binutils-gcc-linux-glibc-gdb: 1 new c2b69595a4 7: onsuccess: binutils-gcc-linux-glibc-gdb: 1 new 8bd6a81d86 8: onsuccess: binutils-gcc-linux-glibc-gdb: 1 new 961ce662ac 9: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] new 5f41c8abb0 10: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new ac796165bc 11: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 0fd425922a 12: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 98121e56e0 13: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new af2372a858 14: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 08d4f4a8f0 15: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 6ffeeb82e0 16: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 95d6e916eb 17: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] new 4dc3d33888 18: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new bfa8f36b64 19: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 8af5356766 20: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 60f18181fa 21: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 3fa3f3351f 22: onsuccess: 1: Success after binutils/gcc/linux/glibc/gdb [...] new 63096f706d 23: onsuccess: 1: Success after binutils/gcc/linux/gdb: 129 commits new 0fa8c762e6 24: onsuccess: 1: Success after binutils/gcc/linux/gdb: 216 commits new f8e48104c0 25: onsuccess: #532: 1: Success after binutils/gcc/linux/gdb [...] new 490aaa50e3 26: onsuccess: #533: 1: Success after binutils/gcc/linux/gdb [...] new f22cd56c91 27: onsuccess: #534: 1: Success after binutils/gcc/linux/gli [...] new 4ddfe0f28f 28: onsuccess: #535: 1: Success after binutils/gcc/linux/gli [...] new 276dd7616d 29: onsuccess: #536: 1: Success after binutils/gcc/glibc/gdb [...] new 29d13a69a5 30: onsuccess: #537: 1: Success after binutils/gcc/linux/gli [...] new d7b08a20f5 31: onsuccess: #538: 1: Success after binutils/gcc/linux/gli [...] new 738e2597e9 32: onsuccess: #539: 1: Success after binutils/gcc/linux/gdb [...] new 91d0f1b9dc 33: onsuccess: #540: 1: Success after binutils/gcc/linux/gli [...] new 915346ab55 34: onsuccess: #541: 1: Success after binutils/gcc/linux/gli [...] new afa892fbbd 35: onsuccess: #542: 1: Success after binutils/gcc/linux/gli [...] new 4b52554b64 36: onsuccess: #543: 1: Success after binutils/gcc/linux/gli [...] new d2e94d020a 37: onsuccess: #544: 1: Success after binutils/gcc/glibc/gdb [...] new 2cae0b4b1a 38: onsuccess: #545: 1: Success after binutils/gcc/linux/gli [...] new 5df39a455f 39: onsuccess: #546: 1: Success after binutils/gcc/glibc/gdb [...] new 659d45b2b3 40: onsuccess: #547: 1: Success after binutils/gcc/linux/gdb [...] new 5a55ac10de 41: onsuccess: #548: 1: Success after binutils/gcc/glibc/gdb [...] new a1d3ccb458 42: onsuccess: #549: 1: Success after binutils/gcc/linux/gli [...] new 745b0af47d 43: onsuccess: #550: 1: Success after binutils/gcc/linux/gli [...] new 0ba068fb31 44: onsuccess: #552: 1: Success after binutils/gcc/linux/gli [...] new b7381749a3 45: onsuccess: #553: 1: Success after binutils/gcc/linux/gdb [...] new 0b6631de7a 46: onsuccess: #554: 1: Success after binutils/gcc/linux/gdb [...] new 36074cac73 47: onsuccess: #556: 1: Success after binutils: 12 commits new 25c9aadfd0 48: onsuccess: #559: 1: Success after binutils: 6 commits new 6d812b2c0f 49: onsuccess: #562: 1: Success after binutils: 9 commits new 3beb4feae7 50: onsuccess: #564: 1: Success after binutils/gcc/linux/gli [...] new 58e5f683c1 51: onsuccess: #565: 1: Success after binutils/gcc/linux/gli [...] new 08809b16a6 52: onsuccess: #566: 1: Success after binutils/gcc/linux/gli [...] new b4f1a59787 53: onsuccess: #567: 1: Success after binutils/gcc/linux/gdb [...] new 07bb4843b2 54: onsuccess: #568: 1: Success after binutils/gcc/linux/gli [...] new aa308c8913 55: onsuccess: #569: 1: Success after binutils/gcc/linux/gli [...] new 8dcee6bb15 56: onsuccess: #570: 1: Success after binutils/gcc/linux/gli [...] new 6bc12022b4 57: onsuccess: #571: 1: Success after binutils/gcc/linux/gli [...] new 6e9b2571ce 58: onsuccess: #572: 1: Success after binutils/gcc/linux/gli [...] new 3541873df7 59: onsuccess: #573: 1: Success after binutils/gcc/linux/gli [...] new d83599329c 60: onsuccess: #574: 1: Success after binutils/gcc/linux/gli [...] new dea6843660 61: onsuccess: #575: 1: Success after binutils/gcc/linux/gli [...] new e23bc62a0a 62: onsuccess: #576: 1: Success after binutils/gcc/linux/gdb [...] new 6ec9e5a1c6 63: onsuccess: #577: 1: Success after binutils/gcc/linux/gli [...] new 8f6f9dc083 64: onsuccess: #579: 1: Success after binutils/gcc/linux/gli [...] new 58f479ba07 65: onsuccess: #580: 1: Success after binutils/gcc/linux/gdb [...] new 2e876e0f32 66: onsuccess: #581: 1: Success after binutils/gcc/linux/gli [...] new 13176a1569 67: onsuccess: #582: 1: Success after binutils/gcc/linux/gdb [...] new 65c519cb6e 68: onsuccess: #583: 1: Success after binutils/gcc/linux/gli [...] new e8da90c28e 69: onsuccess: #584: 1: Success after binutils/gcc/glibc/gdb [...] new fe11e168ce 70: onsuccess: #585: 1: Success after binutils/gcc/linux/gli [...] new 967fa966a9 71: onsuccess: #586: 1: Success after binutils/gcc/linux/gdb [...] new 7d6d724951 72: onsuccess: #587: 1: Success after binutils/gcc/linux/gdb [...] new 0750f3bd34 73: onsuccess: #588: 1: Success after binutils/gcc/linux/gdb [...] new 26d63e6ee0 74: onsuccess: #590: 1: Success after binutils: 16 commits new b7373e6b3d 75: onsuccess: #591: 1: Success after gcc: 25 commits new f4fe86de56 76: onsuccess: #592: 1: Success after linux: 63 commits new 83a8b322a6 77: onsuccess: #593: 1: Success after binutils/gcc/linux/gli [...] new f3e49094c8 78: onsuccess: #594: 1: Success after binutils/gcc/linux/gli [...] new f9ea9da409 79: onsuccess: #595: 1: Success after binutils/gcc/linux/gli [...] new 7e558a28c9 80: onsuccess: #596: 1: Success after binutils/gcc/linux/gli [...] new cd6184fde7 81: onsuccess: #597: 1: Success after binutils/gcc/linux/gdb [...] new 9576a4f406 82: onsuccess: #598: 1: Success after binutils/gcc/linux/gli [...] new ce7cb08b60 83: onsuccess: #599: 1: Success after binutils/gcc/linux/gli [...] new 458246c486 84: onsuccess: #600: 1: Success after binutils/gcc/linux/gli [...] new 06b665f956 85: onsuccess: #601: 1: Success after binutils/gcc/linux/gli [...] new 98bcd0c3c6 86: onsuccess: #602: 1: Success after binutils/gcc/linux/gli [...] new 6c711400ef 87: onsuccess: #603: 1: Success after binutils/gcc/linux/gli [...] new 65500b959c 88: onsuccess: #604: 1: Success after binutils/gcc/linux/gdb [...] new 99f6305616 89: onsuccess: #605: 1: Success after binutils/gcc/linux/gdb [...] new 20df257d7e 90: onsuccess: #606: 1: Success after binutils/gcc/linux/gli [...] new e2b3e17e1f 91: onsuccess: #610: 1: Success after binutils/gcc/linux/gli [...] new 1053ad72b7 92: onsuccess: #611: 1: Success after binutils/gcc/linux/gli [...] new d645b91540 93: onsuccess: #613: 1: Success after binutils: 19 commits new 9b46f00631 94: onsuccess: #616: 1: Success after binutils: 2 commits new 60f9fe45ca 95: onsuccess: #619: 1: Success after binutils: 5 commits new 97ce56beb6 96: onsuccess: #621: 1: Success after binutils/gcc/linux/gli [...] new e1b746ce6a 97: onsuccess: #622: 1: Success after binutils/gcc/gdb: 8 commits new 9e605882f1 98: onsuccess: #623: 1: Success after binutils/gcc/linux/gdb [...] new 7305931ef5 99: onsuccess: #624: 1: Success after binutils/gcc/linux/gli [...] new a8b36e9814 100: onsuccess: #625: 1: Success after binutils/gcc/linux/gd [...] new df57771967 101: onsuccess: #627: 1: Success after binutils/gcc/linux/gd [...]
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 (7ac48b318b) \ 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 1688 -> 1696 bytes 02-prepare_abe/console.log.xz | Bin 2724 -> 2752 bytes 03-build_abe-binutils/console.log.xz | Bin 40064 -> 39888 bytes 04-build_abe-gcc/console.log.xz | Bin 215660 -> 215648 bytes 05-clean_sysroot/console.log.xz | Bin 312 -> 312 bytes 06-build_abe-linux/console.log.xz | Bin 8844 -> 8292 bytes 07-build_abe-glibc/console.log.xz | Bin 243756 -> 244148 bytes 08-build_abe-gdb/console.log.xz | Bin 39772 -> 39180 bytes 09-build_abe-dejagnu/console.log.xz | Bin 3836 -> 3840 bytes 10-build_abe-check_binutils/console.log.xz | Bin 2752 -> 2196 bytes 11-check_regression/console.log.xz | Bin 5864 -> 5760 bytes 11-check_regression/results.compare | 8 +- 11-check_regression/results.compare2 | 6 +- 12-update_baseline/console.log | 40 ++++ dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- git/gdb_rev | 2 +- git/linux_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 2 +- mail/mail-subject.txt | 2 +- manifest.sh | 32 +-- sumfiles/binutils.log.xz | Bin 62676 -> 63084 bytes sumfiles/binutils.sum | 62 +++--- sumfiles/gas.log.xz | Bin 81756 -> 81776 bytes sumfiles/gas.sum | 270 +++++++++++----------- sumfiles/ld.log.xz | Bin 121708 -> 121684 bytes sumfiles/ld.sum | 346 ++++++++++++++--------------- 29 files changed, 410 insertions(+), 370 deletions(-)