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 3972faf7ce 108: onsuccess: #637: 1: Success after binutils/gcc/linux/gl [...] discards 0a460442cd 107: onsuccess: #636: 1: Success after binutils/gcc/linux/gl [...] discards d85c949d68 106: onsuccess: #635: 1: Success after binutils/gcc/linux/gd [...] discards 38afd564b7 105: onsuccess: #631: 1: Success after binutils/gcc/linux/gd [...] discards 287c8bb2d9 104: onsuccess: #630: 1: Success after binutils/gcc/linux/gd [...] discards 028f4d9fa4 103: onsuccess: #629: 1: Success after binutils/gcc/gdb: 68 commits discards 8e1c77bb03 102: onsuccess: #628: 1: Success after binutils/gcc/glibc/gd [...] discards 1053c99265 101: onsuccess: #627: 1: Success after binutils/gcc/linux/gd [...] discards ebf7e01321 100: onsuccess: #625: 1: Success after binutils/gcc/linux/gd [...] discards 88c816a1cf 99: onsuccess: #624: 1: Success after binutils/gcc/linux/gli [...] discards b1b7c2fb24 98: onsuccess: #623: 1: Success after binutils/gcc/linux/gdb [...] discards e78496aca7 97: onsuccess: #622: 1: Success after binutils/gcc/gdb: 8 commits discards 7bf162a82d 96: onsuccess: #621: 1: Success after binutils/gcc/linux/gli [...] discards 40ce6f29f8 95: onsuccess: #619: 1: Success after binutils: 5 commits discards 2401ef86ad 94: onsuccess: #616: 1: Success after binutils: 2 commits discards d6d17cacf2 93: onsuccess: #613: 1: Success after binutils: 19 commits discards 842c35765b 92: onsuccess: #611: 1: Success after binutils/gcc/linux/gli [...] discards 5f2ead2f52 91: onsuccess: #610: 1: Success after binutils/gcc/linux/gli [...] discards 282b61c219 90: onsuccess: #606: 1: Success after binutils/gcc/linux/gli [...] discards 963396a391 89: onsuccess: #605: 1: Success after binutils/gcc/linux/gdb [...] discards 62214ea6e4 88: onsuccess: #604: 1: Success after binutils/gcc/linux/gdb [...] discards b48c8f2848 87: onsuccess: #603: 1: Success after binutils/gcc/linux/gli [...] discards 5f5906059a 86: onsuccess: #602: 1: Success after binutils/gcc/linux/gli [...] discards 1e12c9dcf2 85: onsuccess: #601: 1: Success after binutils/gcc/linux/gli [...] discards 430ba87afe 84: onsuccess: #600: 1: Success after binutils/gcc/linux/gli [...] discards fcd3ce50c2 83: onsuccess: #599: 1: Success after binutils/gcc/linux/gli [...] discards 372d35a892 82: onsuccess: #598: 1: Success after binutils/gcc/linux/gli [...] discards de2910af58 81: onsuccess: #597: 1: Success after binutils/gcc/linux/gdb [...] discards be612b5473 80: onsuccess: #596: 1: Success after binutils/gcc/linux/gli [...] discards 8c3af189f0 79: onsuccess: #595: 1: Success after binutils/gcc/linux/gli [...] discards b36e458da8 78: onsuccess: #594: 1: Success after binutils/gcc/linux/gli [...] discards 6648510431 77: onsuccess: #593: 1: Success after binutils/gcc/linux/gli [...] discards aa3663946c 76: onsuccess: #592: 1: Success after linux: 63 commits discards 9d682db830 75: onsuccess: #591: 1: Success after gcc: 25 commits discards bad3572f66 74: onsuccess: #590: 1: Success after binutils: 16 commits discards 253ac1dcd5 73: onsuccess: #588: 1: Success after binutils/gcc/linux/gdb [...] discards b5b94834bd 72: onsuccess: #587: 1: Success after binutils/gcc/linux/gdb [...] discards 73cb1511f1 71: onsuccess: #586: 1: Success after binutils/gcc/linux/gdb [...] discards 3f2e75b2b3 70: onsuccess: #585: 1: Success after binutils/gcc/linux/gli [...] discards b15de400b8 69: onsuccess: #584: 1: Success after binutils/gcc/glibc/gdb [...] discards 90dc38e216 68: onsuccess: #583: 1: Success after binutils/gcc/linux/gli [...] discards a27c8e3f10 67: onsuccess: #582: 1: Success after binutils/gcc/linux/gdb [...] discards 410cb23581 66: onsuccess: #581: 1: Success after binutils/gcc/linux/gli [...] discards 70cd83303f 65: onsuccess: #580: 1: Success after binutils/gcc/linux/gdb [...] discards 311a011131 64: onsuccess: #579: 1: Success after binutils/gcc/linux/gli [...] discards fc885d99b5 63: onsuccess: #577: 1: Success after binutils/gcc/linux/gli [...] discards 4bea9e8597 62: onsuccess: #576: 1: Success after binutils/gcc/linux/gdb [...] discards e0abc6f59a 61: onsuccess: #575: 1: Success after binutils/gcc/linux/gli [...] discards 8c26248e4f 60: onsuccess: #574: 1: Success after binutils/gcc/linux/gli [...] discards ff78908b9b 59: onsuccess: #573: 1: Success after binutils/gcc/linux/gli [...] discards fcc5eec54f 58: onsuccess: #572: 1: Success after binutils/gcc/linux/gli [...] discards 05ff02bd77 57: onsuccess: #571: 1: Success after binutils/gcc/linux/gli [...] discards e83e469ed0 56: onsuccess: #570: 1: Success after binutils/gcc/linux/gli [...] discards 46ef284fb5 55: onsuccess: #569: 1: Success after binutils/gcc/linux/gli [...] discards f44d4bfa82 54: onsuccess: #568: 1: Success after binutils/gcc/linux/gli [...] discards 7b67d91573 53: onsuccess: #567: 1: Success after binutils/gcc/linux/gdb [...] discards 85144c6566 52: onsuccess: #566: 1: Success after binutils/gcc/linux/gli [...] discards 7a29abcd55 51: onsuccess: #565: 1: Success after binutils/gcc/linux/gli [...] discards 59b61ba7cc 50: onsuccess: #564: 1: Success after binutils/gcc/linux/gli [...] discards 7287a47ab1 49: onsuccess: #562: 1: Success after binutils: 9 commits discards f4a625e021 48: onsuccess: #559: 1: Success after binutils: 6 commits discards fd89628997 47: onsuccess: #556: 1: Success after binutils: 12 commits discards afa34fd30c 46: onsuccess: #554: 1: Success after binutils/gcc/linux/gdb [...] discards ea8322a3e8 45: onsuccess: #553: 1: Success after binutils/gcc/linux/gdb [...] discards 723713a61c 44: onsuccess: #552: 1: Success after binutils/gcc/linux/gli [...] discards 03ef8cb1f9 43: onsuccess: #550: 1: Success after binutils/gcc/linux/gli [...] discards f10d926014 42: onsuccess: #549: 1: Success after binutils/gcc/linux/gli [...] discards 41f911b213 41: onsuccess: #548: 1: Success after binutils/gcc/glibc/gdb [...] discards 93b978539e 40: onsuccess: #547: 1: Success after binutils/gcc/linux/gdb [...] discards a960716fbd 39: onsuccess: #546: 1: Success after binutils/gcc/glibc/gdb [...] discards 0fd8014f1f 38: onsuccess: #545: 1: Success after binutils/gcc/linux/gli [...] discards 72342b8c58 37: onsuccess: #544: 1: Success after binutils/gcc/glibc/gdb [...] discards 757a2e089f 36: onsuccess: #543: 1: Success after binutils/gcc/linux/gli [...] discards 4a0849d87f 35: onsuccess: #542: 1: Success after binutils/gcc/linux/gli [...] discards ba3a09ec4d 34: onsuccess: #541: 1: Success after binutils/gcc/linux/gli [...] discards 4ee3b4f565 33: onsuccess: #540: 1: Success after binutils/gcc/linux/gli [...] discards 125a846949 32: onsuccess: #539: 1: Success after binutils/gcc/linux/gdb [...] discards cf68d26108 31: onsuccess: #538: 1: Success after binutils/gcc/linux/gli [...] discards 9721bbf640 30: onsuccess: #537: 1: Success after binutils/gcc/linux/gli [...] discards 4470d7a2d1 29: onsuccess: #536: 1: Success after binutils/gcc/glibc/gdb [...] discards bb59c56535 28: onsuccess: #535: 1: Success after binutils/gcc/linux/gli [...] discards 930fff98ce 27: onsuccess: #534: 1: Success after binutils/gcc/linux/gli [...] discards 5ab74b82f0 26: onsuccess: #533: 1: Success after binutils/gcc/linux/gdb [...] discards d9af8cd600 25: onsuccess: #532: 1: Success after binutils/gcc/linux/gdb [...] discards f0d94c2159 24: onsuccess: 1: Success after binutils/gcc/linux/gdb: 216 commits discards a2e275a4f6 23: onsuccess: 1: Success after binutils/gcc/linux/gdb: 129 commits discards 803b362edc 22: onsuccess: 1: Success after binutils/gcc/linux/glibc/gdb [...] discards 6d1cd8057d 21: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 010f407550 20: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 17fb122c1b 19: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards df8c60b59e 18: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 937dbda4ae 17: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] discards fc8aa4e547 16: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 0ccd8aad54 15: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 50e827c363 14: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 32f3efeabf 13: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 1fdae56d8e 12: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 7dd917c259 11: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 154f2ce2be 10: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 0ed163b300 9: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] discards a2fefcf412 8: onsuccess: binutils-gcc-linux-glibc-gdb: 1 new 48d0b5cd6b 8: onsuccess: binutils-gcc-linux-glibc-gdb: 1 new 4f53ec6e86 9: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] new 2816bc8c76 10: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 5978449533 11: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 92fe7e9577 12: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new be7d1daf8c 13: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 43f07e9611 14: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 772dcd4c52 15: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new ce01c8c6d6 16: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new b3f6229bbf 17: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] new e6f738f6ab 18: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new b2d19c5f30 19: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 2e438edbb3 20: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 8cf11dd8ff 21: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 9e5eafc7f3 22: onsuccess: 1: Success after binutils/gcc/linux/glibc/gdb [...] new 7db4efb9c3 23: onsuccess: 1: Success after binutils/gcc/linux/gdb: 129 commits new d24706259f 24: onsuccess: 1: Success after binutils/gcc/linux/gdb: 216 commits new 8ba4eb916f 25: onsuccess: #532: 1: Success after binutils/gcc/linux/gdb [...] new b0a970c137 26: onsuccess: #533: 1: Success after binutils/gcc/linux/gdb [...] new e2453aeb82 27: onsuccess: #534: 1: Success after binutils/gcc/linux/gli [...] new e09dd5f5f7 28: onsuccess: #535: 1: Success after binutils/gcc/linux/gli [...] new d2ca098f41 29: onsuccess: #536: 1: Success after binutils/gcc/glibc/gdb [...] new 9b2c4f1e68 30: onsuccess: #537: 1: Success after binutils/gcc/linux/gli [...] new b228bc4eff 31: onsuccess: #538: 1: Success after binutils/gcc/linux/gli [...] new 005fd9b687 32: onsuccess: #539: 1: Success after binutils/gcc/linux/gdb [...] new f434649110 33: onsuccess: #540: 1: Success after binutils/gcc/linux/gli [...] new a9aa78956b 34: onsuccess: #541: 1: Success after binutils/gcc/linux/gli [...] new 7197efb69a 35: onsuccess: #542: 1: Success after binutils/gcc/linux/gli [...] new 1cfd301400 36: onsuccess: #543: 1: Success after binutils/gcc/linux/gli [...] new e6eaf1fdd0 37: onsuccess: #544: 1: Success after binutils/gcc/glibc/gdb [...] new 8c49dfdf42 38: onsuccess: #545: 1: Success after binutils/gcc/linux/gli [...] new f5825ce3e5 39: onsuccess: #546: 1: Success after binutils/gcc/glibc/gdb [...] new 43bd0dc61a 40: onsuccess: #547: 1: Success after binutils/gcc/linux/gdb [...] new 962f0d983b 41: onsuccess: #548: 1: Success after binutils/gcc/glibc/gdb [...] new 289077a14a 42: onsuccess: #549: 1: Success after binutils/gcc/linux/gli [...] new e618ba4b50 43: onsuccess: #550: 1: Success after binutils/gcc/linux/gli [...] new 73faef8887 44: onsuccess: #552: 1: Success after binutils/gcc/linux/gli [...] new af04c16ce1 45: onsuccess: #553: 1: Success after binutils/gcc/linux/gdb [...] new 4d9e522b05 46: onsuccess: #554: 1: Success after binutils/gcc/linux/gdb [...] new 583ea5a919 47: onsuccess: #556: 1: Success after binutils: 12 commits new 812501e0e4 48: onsuccess: #559: 1: Success after binutils: 6 commits new 3e696654e0 49: onsuccess: #562: 1: Success after binutils: 9 commits new 16501fa5cc 50: onsuccess: #564: 1: Success after binutils/gcc/linux/gli [...] new b1acd27af8 51: onsuccess: #565: 1: Success after binutils/gcc/linux/gli [...] new c99807ddf4 52: onsuccess: #566: 1: Success after binutils/gcc/linux/gli [...] new e0e034fba1 53: onsuccess: #567: 1: Success after binutils/gcc/linux/gdb [...] new cde26f47c6 54: onsuccess: #568: 1: Success after binutils/gcc/linux/gli [...] new 51999e3478 55: onsuccess: #569: 1: Success after binutils/gcc/linux/gli [...] new 8387836125 56: onsuccess: #570: 1: Success after binutils/gcc/linux/gli [...] new 16b080a5b9 57: onsuccess: #571: 1: Success after binutils/gcc/linux/gli [...] new 109601c83d 58: onsuccess: #572: 1: Success after binutils/gcc/linux/gli [...] new 2a82dba768 59: onsuccess: #573: 1: Success after binutils/gcc/linux/gli [...] new 83698f5829 60: onsuccess: #574: 1: Success after binutils/gcc/linux/gli [...] new 72eb2661bf 61: onsuccess: #575: 1: Success after binutils/gcc/linux/gli [...] new 89d78d2d3d 62: onsuccess: #576: 1: Success after binutils/gcc/linux/gdb [...] new 276217c162 63: onsuccess: #577: 1: Success after binutils/gcc/linux/gli [...] new 9c588a585b 64: onsuccess: #579: 1: Success after binutils/gcc/linux/gli [...] new d9f07d25b1 65: onsuccess: #580: 1: Success after binutils/gcc/linux/gdb [...] new fae0b5ccdf 66: onsuccess: #581: 1: Success after binutils/gcc/linux/gli [...] new e8fe385a0c 67: onsuccess: #582: 1: Success after binutils/gcc/linux/gdb [...] new 1200e874b5 68: onsuccess: #583: 1: Success after binutils/gcc/linux/gli [...] new e3b02a12fd 69: onsuccess: #584: 1: Success after binutils/gcc/glibc/gdb [...] new 991c43da46 70: onsuccess: #585: 1: Success after binutils/gcc/linux/gli [...] new 8cb18fccfe 71: onsuccess: #586: 1: Success after binutils/gcc/linux/gdb [...] new 655afe9ff1 72: onsuccess: #587: 1: Success after binutils/gcc/linux/gdb [...] new 2e5b61b968 73: onsuccess: #588: 1: Success after binutils/gcc/linux/gdb [...] new 5a04b576e9 74: onsuccess: #590: 1: Success after binutils: 16 commits new 033a1b7a8f 75: onsuccess: #591: 1: Success after gcc: 25 commits new 33e2bed002 76: onsuccess: #592: 1: Success after linux: 63 commits new 154d79d53d 77: onsuccess: #593: 1: Success after binutils/gcc/linux/gli [...] new 4623cd6818 78: onsuccess: #594: 1: Success after binutils/gcc/linux/gli [...] new 568fb93cb4 79: onsuccess: #595: 1: Success after binutils/gcc/linux/gli [...] new 4d2dd8edd4 80: onsuccess: #596: 1: Success after binutils/gcc/linux/gli [...] new f9ba64ba6a 81: onsuccess: #597: 1: Success after binutils/gcc/linux/gdb [...] new b905fd46ce 82: onsuccess: #598: 1: Success after binutils/gcc/linux/gli [...] new cc33c5c33f 83: onsuccess: #599: 1: Success after binutils/gcc/linux/gli [...] new 546a437ec7 84: onsuccess: #600: 1: Success after binutils/gcc/linux/gli [...] new 3cf9845931 85: onsuccess: #601: 1: Success after binutils/gcc/linux/gli [...] new 372ba88ddc 86: onsuccess: #602: 1: Success after binutils/gcc/linux/gli [...] new 55f0cf8988 87: onsuccess: #603: 1: Success after binutils/gcc/linux/gli [...] new b943a2bbec 88: onsuccess: #604: 1: Success after binutils/gcc/linux/gdb [...] new 0f83788fc5 89: onsuccess: #605: 1: Success after binutils/gcc/linux/gdb [...] new e6c5947e04 90: onsuccess: #606: 1: Success after binutils/gcc/linux/gli [...] new d1b1aafece 91: onsuccess: #610: 1: Success after binutils/gcc/linux/gli [...] new 79c5914262 92: onsuccess: #611: 1: Success after binutils/gcc/linux/gli [...] new 5bf5fc2d82 93: onsuccess: #613: 1: Success after binutils: 19 commits new bd52b3592a 94: onsuccess: #616: 1: Success after binutils: 2 commits new 72997f35f8 95: onsuccess: #619: 1: Success after binutils: 5 commits new 047460e160 96: onsuccess: #621: 1: Success after binutils/gcc/linux/gli [...] new c757cef8ae 97: onsuccess: #622: 1: Success after binutils/gcc/gdb: 8 commits new 1303874afd 98: onsuccess: #623: 1: Success after binutils/gcc/linux/gdb [...] new 14e8b2a9b5 99: onsuccess: #624: 1: Success after binutils/gcc/linux/gli [...] new f2dba96df1 100: onsuccess: #625: 1: Success after binutils/gcc/linux/gd [...] new c6af5291e8 101: onsuccess: #627: 1: Success after binutils/gcc/linux/gd [...] new c89f7660bc 102: onsuccess: #628: 1: Success after binutils/gcc/glibc/gd [...] new 42b5dd8e9e 103: onsuccess: #629: 1: Success after binutils/gcc/gdb: 68 commits new 3051ab8073 104: onsuccess: #630: 1: Success after binutils/gcc/linux/gd [...] new 5b28c7922f 105: onsuccess: #631: 1: Success after binutils/gcc/linux/gd [...] new 843dd2caba 106: onsuccess: #635: 1: Success after binutils/gcc/linux/gd [...] new 923b1da7bf 107: onsuccess: #636: 1: Success after binutils/gcc/linux/gl [...] new 7b9e3c3090 108: onsuccess: #637: 1: Success after binutils/gcc/linux/gl [...] new f7f389aa89 109: onsuccess: #638: 1: Success after binutils/gcc/linux/gl [...]

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 (3972faf7ce) \ 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 1748 -> 1712 bytes 02-prepare_abe/console.log.xz | Bin 2732 -> 2756 bytes 03-build_abe-binutils/console.log.xz | Bin 39900 -> 39988 bytes 04-build_abe-gcc/console.log.xz | Bin 214948 -> 216420 bytes 05-clean_sysroot/console.log.xz | Bin 312 -> 312 bytes 06-build_abe-linux/console.log.xz | Bin 8800 -> 9524 bytes 07-build_abe-glibc/console.log.xz | Bin 244388 -> 245160 bytes 08-build_abe-gdb/console.log.xz | Bin 38888 -> 38936 bytes 09-build_abe-dejagnu/console.log.xz | Bin 3920 -> 3860 bytes 10-build_abe-check_binutils/console.log.xz | Bin 2088 -> 2108 bytes 11-check_regression/console.log.xz | Bin 6184 -> 6192 bytes 11-check_regression/results.compare | 8 +- 11-check_regression/results.compare2 | 20 +- 12-update_baseline/console.log | 62 ++--- dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- git/gdb_rev | 2 +- git/glibc_rev | 2 +- git/linux_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 2 +- mail/mail-subject.txt | 2 +- manifest.sh | 38 ++-- sumfiles/binutils.log.xz | Bin 63160 -> 62880 bytes sumfiles/binutils.sum | 62 ++--- sumfiles/gas.log.xz | Bin 81796 -> 81792 bytes sumfiles/gas.sum | 272 +++++++++++----------- sumfiles/ld.log.xz | Bin 121956 -> 121768 bytes sumfiles/ld.sum | 348 ++++++++++++++--------------- 30 files changed, 410 insertions(+), 418 deletions(-)