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 bd6749f998 107: onsuccess: #636: 1: Success after binutils/gcc/linux/gl [...] discards 53df92a219 106: onsuccess: #635: 1: Success after binutils/gcc/linux/gd [...] discards 5539ebbd65 105: onsuccess: #631: 1: Success after binutils/gcc/linux/gd [...] discards 2786e9448d 104: onsuccess: #630: 1: Success after binutils/gcc/linux/gd [...] discards 569d284981 103: onsuccess: #629: 1: Success after binutils/gcc/gdb: 68 commits discards 8696e774ba 102: onsuccess: #628: 1: Success after binutils/gcc/glibc/gd [...] discards c3fff22bd2 101: onsuccess: #627: 1: Success after binutils/gcc/linux/gd [...] discards 1575423a36 100: onsuccess: #625: 1: Success after binutils/gcc/linux/gd [...] discards 11504226a8 99: onsuccess: #624: 1: Success after binutils/gcc/linux/gli [...] discards 766d9634d2 98: onsuccess: #623: 1: Success after binutils/gcc/linux/gdb [...] discards 1a0bbd44bd 97: onsuccess: #622: 1: Success after binutils/gcc/gdb: 8 commits discards c6206080e6 96: onsuccess: #621: 1: Success after binutils/gcc/linux/gli [...] discards 11226f183b 95: onsuccess: #619: 1: Success after binutils: 5 commits discards 86ad45c436 94: onsuccess: #616: 1: Success after binutils: 2 commits discards eea98c2881 93: onsuccess: #613: 1: Success after binutils: 19 commits discards dd1721fed8 92: onsuccess: #611: 1: Success after binutils/gcc/linux/gli [...] discards f4958f7e63 91: onsuccess: #610: 1: Success after binutils/gcc/linux/gli [...] discards 7c7b6be72b 90: onsuccess: #606: 1: Success after binutils/gcc/linux/gli [...] discards 7cad9eac8e 89: onsuccess: #605: 1: Success after binutils/gcc/linux/gdb [...] discards c8f2eb90c7 88: onsuccess: #604: 1: Success after binutils/gcc/linux/gdb [...] discards d27dcc3dad 87: onsuccess: #603: 1: Success after binutils/gcc/linux/gli [...] discards 0c8b84f3cd 86: onsuccess: #602: 1: Success after binutils/gcc/linux/gli [...] discards ecc5a362fc 85: onsuccess: #601: 1: Success after binutils/gcc/linux/gli [...] discards 86695c02c4 84: onsuccess: #600: 1: Success after binutils/gcc/linux/gli [...] discards 341cf8eb2e 83: onsuccess: #599: 1: Success after binutils/gcc/linux/gli [...] discards cca7bd2492 82: onsuccess: #598: 1: Success after binutils/gcc/linux/gli [...] discards 6d38f657cb 81: onsuccess: #597: 1: Success after binutils/gcc/linux/gdb [...] discards 49e777cb75 80: onsuccess: #596: 1: Success after binutils/gcc/linux/gli [...] discards 925210ae03 79: onsuccess: #595: 1: Success after binutils/gcc/linux/gli [...] discards 4ac4694c2f 78: onsuccess: #594: 1: Success after binutils/gcc/linux/gli [...] discards e394edd339 77: onsuccess: #593: 1: Success after binutils/gcc/linux/gli [...] discards d4b56a5c58 76: onsuccess: #592: 1: Success after linux: 63 commits discards 7f9c944af8 75: onsuccess: #591: 1: Success after gcc: 25 commits discards 4fdb60b1ab 74: onsuccess: #590: 1: Success after binutils: 16 commits discards 65a2c4fb37 73: onsuccess: #588: 1: Success after binutils/gcc/linux/gdb [...] discards ec44315036 72: onsuccess: #587: 1: Success after binutils/gcc/linux/gdb [...] discards 4163abdf54 71: onsuccess: #586: 1: Success after binutils/gcc/linux/gdb [...] discards a0a8c4bca7 70: onsuccess: #585: 1: Success after binutils/gcc/linux/gli [...] discards 7adfaf4db8 69: onsuccess: #584: 1: Success after binutils/gcc/glibc/gdb [...] discards 326c8b65c5 68: onsuccess: #583: 1: Success after binutils/gcc/linux/gli [...] discards db729f16c6 67: onsuccess: #582: 1: Success after binutils/gcc/linux/gdb [...] discards 2250b22384 66: onsuccess: #581: 1: Success after binutils/gcc/linux/gli [...] discards b638a3b0b0 65: onsuccess: #580: 1: Success after binutils/gcc/linux/gdb [...] discards aa2cccc1a9 64: onsuccess: #579: 1: Success after binutils/gcc/linux/gli [...] discards 4942ce357f 63: onsuccess: #577: 1: Success after binutils/gcc/linux/gli [...] discards fc7a877cc4 62: onsuccess: #576: 1: Success after binutils/gcc/linux/gdb [...] discards afbc24dee6 61: onsuccess: #575: 1: Success after binutils/gcc/linux/gli [...] discards b17322e3d0 60: onsuccess: #574: 1: Success after binutils/gcc/linux/gli [...] discards de5cd3d82c 59: onsuccess: #573: 1: Success after binutils/gcc/linux/gli [...] discards f63aba7f35 58: onsuccess: #572: 1: Success after binutils/gcc/linux/gli [...] discards 8e149ba60e 57: onsuccess: #571: 1: Success after binutils/gcc/linux/gli [...] discards eee37d9b78 56: onsuccess: #570: 1: Success after binutils/gcc/linux/gli [...] discards a8c6e04111 55: onsuccess: #569: 1: Success after binutils/gcc/linux/gli [...] discards d4b66f9882 54: onsuccess: #568: 1: Success after binutils/gcc/linux/gli [...] discards f83c18b024 53: onsuccess: #567: 1: Success after binutils/gcc/linux/gdb [...] discards cf6eafd3ab 52: onsuccess: #566: 1: Success after binutils/gcc/linux/gli [...] discards 8b05b6cc5f 51: onsuccess: #565: 1: Success after binutils/gcc/linux/gli [...] discards 13ec2ad7cf 50: onsuccess: #564: 1: Success after binutils/gcc/linux/gli [...] discards d8c6917917 49: onsuccess: #562: 1: Success after binutils: 9 commits discards 76051e3ca4 48: onsuccess: #559: 1: Success after binutils: 6 commits discards 78d9d2045e 47: onsuccess: #556: 1: Success after binutils: 12 commits discards 3b6678cef7 46: onsuccess: #554: 1: Success after binutils/gcc/linux/gdb [...] discards 2560d28705 45: onsuccess: #553: 1: Success after binutils/gcc/linux/gdb [...] discards 6c38383553 44: onsuccess: #552: 1: Success after binutils/gcc/linux/gli [...] discards bd398ffd88 43: onsuccess: #550: 1: Success after binutils/gcc/linux/gli [...] discards 694a200549 42: onsuccess: #549: 1: Success after binutils/gcc/linux/gli [...] discards 903701dd4d 41: onsuccess: #548: 1: Success after binutils/gcc/glibc/gdb [...] discards c82d41636a 40: onsuccess: #547: 1: Success after binutils/gcc/linux/gdb [...] discards b78f07c398 39: onsuccess: #546: 1: Success after binutils/gcc/glibc/gdb [...] discards fea91458d4 38: onsuccess: #545: 1: Success after binutils/gcc/linux/gli [...] discards 49a193917d 37: onsuccess: #544: 1: Success after binutils/gcc/glibc/gdb [...] discards 46c247d90d 36: onsuccess: #543: 1: Success after binutils/gcc/linux/gli [...] discards 1e57af5a20 35: onsuccess: #542: 1: Success after binutils/gcc/linux/gli [...] discards b7bd7ab637 34: onsuccess: #541: 1: Success after binutils/gcc/linux/gli [...] discards 9c2c2bf755 33: onsuccess: #540: 1: Success after binutils/gcc/linux/gli [...] discards 2a5e664ebe 32: onsuccess: #539: 1: Success after binutils/gcc/linux/gdb [...] discards f4c18eea00 31: onsuccess: #538: 1: Success after binutils/gcc/linux/gli [...] discards 0eb09762f7 30: onsuccess: #537: 1: Success after binutils/gcc/linux/gli [...] discards e889584fdb 29: onsuccess: #536: 1: Success after binutils/gcc/glibc/gdb [...] discards 00aaab0fa8 28: onsuccess: #535: 1: Success after binutils/gcc/linux/gli [...] discards 5b6c570bad 27: onsuccess: #534: 1: Success after binutils/gcc/linux/gli [...] discards 7cc40cce54 26: onsuccess: #533: 1: Success after binutils/gcc/linux/gdb [...] discards 578cb82ada 25: onsuccess: #532: 1: Success after binutils/gcc/linux/gdb [...] discards 44b0ff97c2 24: onsuccess: 1: Success after binutils/gcc/linux/gdb: 216 commits discards 5b9d5eb579 23: onsuccess: 1: Success after binutils/gcc/linux/gdb: 129 commits discards 34af0519b1 22: onsuccess: 1: Success after binutils/gcc/linux/glibc/gdb [...] discards d6d4ecd93d 21: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 545b31757f 20: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards c95839929d 19: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 2395b2509d 18: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 9c4f4442ac 17: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] discards a948e4cd9c 16: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 63f19074e4 15: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 41421c53af 14: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards c32c63e1c8 13: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards bc867f859e 12: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 80462e19c8 11: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards d91a8b20f4 10: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 3a1ab8c899 9: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] discards 00abc5a5d4 8: onsuccess: binutils-gcc-linux-glibc-gdb: 1 discards c81fa51b6e 7: onsuccess: binutils-gcc-linux-glibc-gdb: 1 new f866582d9a 7: onsuccess: binutils-gcc-linux-glibc-gdb: 1 new a2fefcf412 8: onsuccess: binutils-gcc-linux-glibc-gdb: 1 new 0ed163b300 9: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] new 154f2ce2be 10: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 7dd917c259 11: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 1fdae56d8e 12: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 32f3efeabf 13: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 50e827c363 14: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 0ccd8aad54 15: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new fc8aa4e547 16: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 937dbda4ae 17: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] new df8c60b59e 18: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 17fb122c1b 19: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 010f407550 20: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 6d1cd8057d 21: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 803b362edc 22: onsuccess: 1: Success after binutils/gcc/linux/glibc/gdb [...] new a2e275a4f6 23: onsuccess: 1: Success after binutils/gcc/linux/gdb: 129 commits new f0d94c2159 24: onsuccess: 1: Success after binutils/gcc/linux/gdb: 216 commits new d9af8cd600 25: onsuccess: #532: 1: Success after binutils/gcc/linux/gdb [...] new 5ab74b82f0 26: onsuccess: #533: 1: Success after binutils/gcc/linux/gdb [...] new 930fff98ce 27: onsuccess: #534: 1: Success after binutils/gcc/linux/gli [...] new bb59c56535 28: onsuccess: #535: 1: Success after binutils/gcc/linux/gli [...] new 4470d7a2d1 29: onsuccess: #536: 1: Success after binutils/gcc/glibc/gdb [...] new 9721bbf640 30: onsuccess: #537: 1: Success after binutils/gcc/linux/gli [...] new cf68d26108 31: onsuccess: #538: 1: Success after binutils/gcc/linux/gli [...] new 125a846949 32: onsuccess: #539: 1: Success after binutils/gcc/linux/gdb [...] new 4ee3b4f565 33: onsuccess: #540: 1: Success after binutils/gcc/linux/gli [...] new ba3a09ec4d 34: onsuccess: #541: 1: Success after binutils/gcc/linux/gli [...] new 4a0849d87f 35: onsuccess: #542: 1: Success after binutils/gcc/linux/gli [...] new 757a2e089f 36: onsuccess: #543: 1: Success after binutils/gcc/linux/gli [...] new 72342b8c58 37: onsuccess: #544: 1: Success after binutils/gcc/glibc/gdb [...] new 0fd8014f1f 38: onsuccess: #545: 1: Success after binutils/gcc/linux/gli [...] new a960716fbd 39: onsuccess: #546: 1: Success after binutils/gcc/glibc/gdb [...] new 93b978539e 40: onsuccess: #547: 1: Success after binutils/gcc/linux/gdb [...] new 41f911b213 41: onsuccess: #548: 1: Success after binutils/gcc/glibc/gdb [...] new f10d926014 42: onsuccess: #549: 1: Success after binutils/gcc/linux/gli [...] new 03ef8cb1f9 43: onsuccess: #550: 1: Success after binutils/gcc/linux/gli [...] new 723713a61c 44: onsuccess: #552: 1: Success after binutils/gcc/linux/gli [...] new ea8322a3e8 45: onsuccess: #553: 1: Success after binutils/gcc/linux/gdb [...] new afa34fd30c 46: onsuccess: #554: 1: Success after binutils/gcc/linux/gdb [...] new fd89628997 47: onsuccess: #556: 1: Success after binutils: 12 commits new f4a625e021 48: onsuccess: #559: 1: Success after binutils: 6 commits new 7287a47ab1 49: onsuccess: #562: 1: Success after binutils: 9 commits new 59b61ba7cc 50: onsuccess: #564: 1: Success after binutils/gcc/linux/gli [...] new 7a29abcd55 51: onsuccess: #565: 1: Success after binutils/gcc/linux/gli [...] new 85144c6566 52: onsuccess: #566: 1: Success after binutils/gcc/linux/gli [...] new 7b67d91573 53: onsuccess: #567: 1: Success after binutils/gcc/linux/gdb [...] new f44d4bfa82 54: onsuccess: #568: 1: Success after binutils/gcc/linux/gli [...] new 46ef284fb5 55: onsuccess: #569: 1: Success after binutils/gcc/linux/gli [...] new e83e469ed0 56: onsuccess: #570: 1: Success after binutils/gcc/linux/gli [...] new 05ff02bd77 57: onsuccess: #571: 1: Success after binutils/gcc/linux/gli [...] new fcc5eec54f 58: onsuccess: #572: 1: Success after binutils/gcc/linux/gli [...] new ff78908b9b 59: onsuccess: #573: 1: Success after binutils/gcc/linux/gli [...] new 8c26248e4f 60: onsuccess: #574: 1: Success after binutils/gcc/linux/gli [...] new e0abc6f59a 61: onsuccess: #575: 1: Success after binutils/gcc/linux/gli [...] new 4bea9e8597 62: onsuccess: #576: 1: Success after binutils/gcc/linux/gdb [...] new fc885d99b5 63: onsuccess: #577: 1: Success after binutils/gcc/linux/gli [...] new 311a011131 64: onsuccess: #579: 1: Success after binutils/gcc/linux/gli [...] new 70cd83303f 65: onsuccess: #580: 1: Success after binutils/gcc/linux/gdb [...] new 410cb23581 66: onsuccess: #581: 1: Success after binutils/gcc/linux/gli [...] new a27c8e3f10 67: onsuccess: #582: 1: Success after binutils/gcc/linux/gdb [...] new 90dc38e216 68: onsuccess: #583: 1: Success after binutils/gcc/linux/gli [...] new b15de400b8 69: onsuccess: #584: 1: Success after binutils/gcc/glibc/gdb [...] new 3f2e75b2b3 70: onsuccess: #585: 1: Success after binutils/gcc/linux/gli [...] new 73cb1511f1 71: onsuccess: #586: 1: Success after binutils/gcc/linux/gdb [...] new b5b94834bd 72: onsuccess: #587: 1: Success after binutils/gcc/linux/gdb [...] new 253ac1dcd5 73: onsuccess: #588: 1: Success after binutils/gcc/linux/gdb [...] new bad3572f66 74: onsuccess: #590: 1: Success after binutils: 16 commits new 9d682db830 75: onsuccess: #591: 1: Success after gcc: 25 commits new aa3663946c 76: onsuccess: #592: 1: Success after linux: 63 commits new 6648510431 77: onsuccess: #593: 1: Success after binutils/gcc/linux/gli [...] new b36e458da8 78: onsuccess: #594: 1: Success after binutils/gcc/linux/gli [...] new 8c3af189f0 79: onsuccess: #595: 1: Success after binutils/gcc/linux/gli [...] new be612b5473 80: onsuccess: #596: 1: Success after binutils/gcc/linux/gli [...] new de2910af58 81: onsuccess: #597: 1: Success after binutils/gcc/linux/gdb [...] new 372d35a892 82: onsuccess: #598: 1: Success after binutils/gcc/linux/gli [...] new fcd3ce50c2 83: onsuccess: #599: 1: Success after binutils/gcc/linux/gli [...] new 430ba87afe 84: onsuccess: #600: 1: Success after binutils/gcc/linux/gli [...] new 1e12c9dcf2 85: onsuccess: #601: 1: Success after binutils/gcc/linux/gli [...] new 5f5906059a 86: onsuccess: #602: 1: Success after binutils/gcc/linux/gli [...] new b48c8f2848 87: onsuccess: #603: 1: Success after binutils/gcc/linux/gli [...] new 62214ea6e4 88: onsuccess: #604: 1: Success after binutils/gcc/linux/gdb [...] new 963396a391 89: onsuccess: #605: 1: Success after binutils/gcc/linux/gdb [...] new 282b61c219 90: onsuccess: #606: 1: Success after binutils/gcc/linux/gli [...] new 5f2ead2f52 91: onsuccess: #610: 1: Success after binutils/gcc/linux/gli [...] new 842c35765b 92: onsuccess: #611: 1: Success after binutils/gcc/linux/gli [...] new d6d17cacf2 93: onsuccess: #613: 1: Success after binutils: 19 commits new 2401ef86ad 94: onsuccess: #616: 1: Success after binutils: 2 commits new 40ce6f29f8 95: onsuccess: #619: 1: Success after binutils: 5 commits new 7bf162a82d 96: onsuccess: #621: 1: Success after binutils/gcc/linux/gli [...] new e78496aca7 97: onsuccess: #622: 1: Success after binutils/gcc/gdb: 8 commits new b1b7c2fb24 98: onsuccess: #623: 1: Success after binutils/gcc/linux/gdb [...] new 88c816a1cf 99: onsuccess: #624: 1: Success after binutils/gcc/linux/gli [...] new ebf7e01321 100: onsuccess: #625: 1: Success after binutils/gcc/linux/gd [...] new 1053c99265 101: onsuccess: #627: 1: Success after binutils/gcc/linux/gd [...] new 8e1c77bb03 102: onsuccess: #628: 1: Success after binutils/gcc/glibc/gd [...] new 028f4d9fa4 103: onsuccess: #629: 1: Success after binutils/gcc/gdb: 68 commits new 287c8bb2d9 104: onsuccess: #630: 1: Success after binutils/gcc/linux/gd [...] new 38afd564b7 105: onsuccess: #631: 1: Success after binutils/gcc/linux/gd [...] new d85c949d68 106: onsuccess: #635: 1: Success after binutils/gcc/linux/gd [...] new 0a460442cd 107: onsuccess: #636: 1: Success after binutils/gcc/linux/gl [...] new 3972faf7ce 108: onsuccess: #637: 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 (bd6749f998) \ 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 1704 -> 1748 bytes 02-prepare_abe/console.log.xz | Bin 2712 -> 2732 bytes 03-build_abe-binutils/console.log.xz | Bin 39836 -> 39900 bytes 04-build_abe-gcc/console.log.xz | Bin 215520 -> 214948 bytes 05-clean_sysroot/console.log.xz | Bin 312 -> 312 bytes 06-build_abe-linux/console.log.xz | Bin 8500 -> 8800 bytes 07-build_abe-glibc/console.log.xz | Bin 244100 -> 244388 bytes 08-build_abe-gdb/console.log.xz | Bin 39144 -> 38888 bytes 09-build_abe-dejagnu/console.log.xz | Bin 3832 -> 3920 bytes 10-build_abe-check_binutils/console.log.xz | Bin 2332 -> 2088 bytes 11-check_regression/console.log.xz | Bin 6064 -> 6184 bytes 11-check_regression/results.compare | 8 +- 11-check_regression/results.compare2 | 20 +- 12-update_baseline/console.log | 38 ++-- 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 | 36 +-- sumfiles/binutils.log.xz | Bin 63160 -> 63160 bytes sumfiles/binutils.sum | 62 ++--- sumfiles/gas.log.xz | Bin 81752 -> 81796 bytes sumfiles/gas.sum | 272 +++++++++++----------- sumfiles/ld.log.xz | Bin 121732 -> 121956 bytes sumfiles/ld.sum | 349 +++++++++++++++-------------- 30 files changed, 406 insertions(+), 397 deletions(-)