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 6199e678f1 106: onsuccess: #635: 1: Success after binutils/gcc/linux/gd [...] discards 9bdfc45da7 105: onsuccess: #631: 1: Success after binutils/gcc/linux/gd [...] discards 069bbefa83 104: onsuccess: #630: 1: Success after binutils/gcc/linux/gd [...] discards 1ee55ba9da 103: onsuccess: #629: 1: Success after binutils/gcc/gdb: 68 commits discards 29effea6ea 102: onsuccess: #628: 1: Success after binutils/gcc/glibc/gd [...] discards ca4ed217a0 101: onsuccess: #627: 1: Success after binutils/gcc/linux/gd [...] discards e61d780e8e 100: onsuccess: #625: 1: Success after binutils/gcc/linux/gd [...] discards 86c205eb24 99: onsuccess: #624: 1: Success after binutils/gcc/linux/gli [...] discards edfd20089b 98: onsuccess: #623: 1: Success after binutils/gcc/linux/gdb [...] discards 97c316869a 97: onsuccess: #622: 1: Success after binutils/gcc/gdb: 8 commits discards 3b8142c495 96: onsuccess: #621: 1: Success after binutils/gcc/linux/gli [...] discards 26fe6b64b6 95: onsuccess: #619: 1: Success after binutils: 5 commits discards d53799c9ba 94: onsuccess: #616: 1: Success after binutils: 2 commits discards d78136e85a 93: onsuccess: #613: 1: Success after binutils: 19 commits discards d73d30192e 92: onsuccess: #611: 1: Success after binutils/gcc/linux/gli [...] discards 5f71f325e6 91: onsuccess: #610: 1: Success after binutils/gcc/linux/gli [...] discards 7cbba76a04 90: onsuccess: #606: 1: Success after binutils/gcc/linux/gli [...] discards b0e6fd37c9 89: onsuccess: #605: 1: Success after binutils/gcc/linux/gdb [...] discards 94f65ea374 88: onsuccess: #604: 1: Success after binutils/gcc/linux/gdb [...] discards 6930f3b7d0 87: onsuccess: #603: 1: Success after binutils/gcc/linux/gli [...] discards 594301ed4f 86: onsuccess: #602: 1: Success after binutils/gcc/linux/gli [...] discards 96ddc0b810 85: onsuccess: #601: 1: Success after binutils/gcc/linux/gli [...] discards 563abe11cd 84: onsuccess: #600: 1: Success after binutils/gcc/linux/gli [...] discards 232302b747 83: onsuccess: #599: 1: Success after binutils/gcc/linux/gli [...] discards 49b55e4a02 82: onsuccess: #598: 1: Success after binutils/gcc/linux/gli [...] discards f2b762037f 81: onsuccess: #597: 1: Success after binutils/gcc/linux/gdb [...] discards 1cc8e63723 80: onsuccess: #596: 1: Success after binutils/gcc/linux/gli [...] discards 1da07e058f 79: onsuccess: #595: 1: Success after binutils/gcc/linux/gli [...] discards febdf3ab33 78: onsuccess: #594: 1: Success after binutils/gcc/linux/gli [...] discards f072956e6c 77: onsuccess: #593: 1: Success after binutils/gcc/linux/gli [...] discards 3e1b97c01a 76: onsuccess: #592: 1: Success after linux: 63 commits discards ffc44b5ce3 75: onsuccess: #591: 1: Success after gcc: 25 commits discards 8bba29cf78 74: onsuccess: #590: 1: Success after binutils: 16 commits discards e8d533457e 73: onsuccess: #588: 1: Success after binutils/gcc/linux/gdb [...] discards 945ef41ebb 72: onsuccess: #587: 1: Success after binutils/gcc/linux/gdb [...] discards 21ecdb371e 71: onsuccess: #586: 1: Success after binutils/gcc/linux/gdb [...] discards 6bf745e036 70: onsuccess: #585: 1: Success after binutils/gcc/linux/gli [...] discards c13356c65b 69: onsuccess: #584: 1: Success after binutils/gcc/glibc/gdb [...] discards 96f04418bd 68: onsuccess: #583: 1: Success after binutils/gcc/linux/gli [...] discards 64b39aa654 67: onsuccess: #582: 1: Success after binutils/gcc/linux/gdb [...] discards 9b1369ecca 66: onsuccess: #581: 1: Success after binutils/gcc/linux/gli [...] discards 55c08b66d3 65: onsuccess: #580: 1: Success after binutils/gcc/linux/gdb [...] discards d025f858e3 64: onsuccess: #579: 1: Success after binutils/gcc/linux/gli [...] discards 35610de52d 63: onsuccess: #577: 1: Success after binutils/gcc/linux/gli [...] discards 7c10f9dfad 62: onsuccess: #576: 1: Success after binutils/gcc/linux/gdb [...] discards 4b0d316bc8 61: onsuccess: #575: 1: Success after binutils/gcc/linux/gli [...] discards 7814b94dd4 60: onsuccess: #574: 1: Success after binutils/gcc/linux/gli [...] discards 8d9d0e6378 59: onsuccess: #573: 1: Success after binutils/gcc/linux/gli [...] discards de74acef7d 58: onsuccess: #572: 1: Success after binutils/gcc/linux/gli [...] discards b1b2ea1df0 57: onsuccess: #571: 1: Success after binutils/gcc/linux/gli [...] discards 77ce07e63f 56: onsuccess: #570: 1: Success after binutils/gcc/linux/gli [...] discards 32aefd4d65 55: onsuccess: #569: 1: Success after binutils/gcc/linux/gli [...] discards a77d0d09cc 54: onsuccess: #568: 1: Success after binutils/gcc/linux/gli [...] discards ef58917371 53: onsuccess: #567: 1: Success after binutils/gcc/linux/gdb [...] discards 0917c16c2f 52: onsuccess: #566: 1: Success after binutils/gcc/linux/gli [...] discards 9439a2d79a 51: onsuccess: #565: 1: Success after binutils/gcc/linux/gli [...] discards abcf3d3be6 50: onsuccess: #564: 1: Success after binutils/gcc/linux/gli [...] discards 79cff7710e 49: onsuccess: #562: 1: Success after binutils: 9 commits discards 765707ed33 48: onsuccess: #559: 1: Success after binutils: 6 commits discards 59bdeec392 47: onsuccess: #556: 1: Success after binutils: 12 commits discards 735e96ef81 46: onsuccess: #554: 1: Success after binutils/gcc/linux/gdb [...] discards fb3ae6ca34 45: onsuccess: #553: 1: Success after binutils/gcc/linux/gdb [...] discards 780dda3b0e 44: onsuccess: #552: 1: Success after binutils/gcc/linux/gli [...] discards 1deeb79ac3 43: onsuccess: #550: 1: Success after binutils/gcc/linux/gli [...] discards f69754a119 42: onsuccess: #549: 1: Success after binutils/gcc/linux/gli [...] discards 74b2e3016c 41: onsuccess: #548: 1: Success after binutils/gcc/glibc/gdb [...] discards 71212eabf6 40: onsuccess: #547: 1: Success after binutils/gcc/linux/gdb [...] discards 4125c1ed9f 39: onsuccess: #546: 1: Success after binutils/gcc/glibc/gdb [...] discards aff72e6cc7 38: onsuccess: #545: 1: Success after binutils/gcc/linux/gli [...] discards ba00bb2ce6 37: onsuccess: #544: 1: Success after binutils/gcc/glibc/gdb [...] discards 2a6e68cf02 36: onsuccess: #543: 1: Success after binutils/gcc/linux/gli [...] discards c6de2dc8b8 35: onsuccess: #542: 1: Success after binutils/gcc/linux/gli [...] discards cf396ca3f6 34: onsuccess: #541: 1: Success after binutils/gcc/linux/gli [...] discards 744301bcf0 33: onsuccess: #540: 1: Success after binutils/gcc/linux/gli [...] discards 2ceeb5d8eb 32: onsuccess: #539: 1: Success after binutils/gcc/linux/gdb [...] discards d939a43acf 31: onsuccess: #538: 1: Success after binutils/gcc/linux/gli [...] discards eacfbb0284 30: onsuccess: #537: 1: Success after binutils/gcc/linux/gli [...] discards 5010e503db 29: onsuccess: #536: 1: Success after binutils/gcc/glibc/gdb [...] discards 204fd27c69 28: onsuccess: #535: 1: Success after binutils/gcc/linux/gli [...] discards 8341ac5dd5 27: onsuccess: #534: 1: Success after binutils/gcc/linux/gli [...] discards 25fc0d5136 26: onsuccess: #533: 1: Success after binutils/gcc/linux/gdb [...] discards 725becd473 25: onsuccess: #532: 1: Success after binutils/gcc/linux/gdb [...] discards 49978ba140 24: onsuccess: 1: Success after binutils/gcc/linux/gdb: 216 commits discards 326c54322b 23: onsuccess: 1: Success after binutils/gcc/linux/gdb: 129 commits discards 621786f80f 22: onsuccess: 1: Success after binutils/gcc/linux/glibc/gdb [...] discards aaa283ede2 21: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards dd4e0aab93 20: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 88b0319e9b 19: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards f679453215 18: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 902fdda548 17: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] discards e3ca7ea049 16: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards b9e965d775 15: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 7759a81554 14: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards d6613b9851 13: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 4324f970b4 12: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 192a84b0a2 11: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards f5c8c5bbd1 10: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 0e707b89e0 9: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] discards 2abb2ffa5f 8: onsuccess: binutils-gcc-linux-glibc-gdb: 1 discards 0a69770618 7: onsuccess: binutils-gcc-linux-glibc-gdb: 1 discards 020adbe403 6: onsuccess: binutils-gcc-linux-glibc-gdb: 1 new 00b3c44b5e 6: onsuccess: binutils-gcc-linux-glibc-gdb: 1 new c81fa51b6e 7: onsuccess: binutils-gcc-linux-glibc-gdb: 1 new 00abc5a5d4 8: onsuccess: binutils-gcc-linux-glibc-gdb: 1 new 3a1ab8c899 9: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] new d91a8b20f4 10: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 80462e19c8 11: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new bc867f859e 12: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new c32c63e1c8 13: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 41421c53af 14: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 63f19074e4 15: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new a948e4cd9c 16: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 9c4f4442ac 17: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] new 2395b2509d 18: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new c95839929d 19: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 545b31757f 20: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new d6d4ecd93d 21: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 34af0519b1 22: onsuccess: 1: Success after binutils/gcc/linux/glibc/gdb [...] new 5b9d5eb579 23: onsuccess: 1: Success after binutils/gcc/linux/gdb: 129 commits new 44b0ff97c2 24: onsuccess: 1: Success after binutils/gcc/linux/gdb: 216 commits new 578cb82ada 25: onsuccess: #532: 1: Success after binutils/gcc/linux/gdb [...] new 7cc40cce54 26: onsuccess: #533: 1: Success after binutils/gcc/linux/gdb [...] new 5b6c570bad 27: onsuccess: #534: 1: Success after binutils/gcc/linux/gli [...] new 00aaab0fa8 28: onsuccess: #535: 1: Success after binutils/gcc/linux/gli [...] new e889584fdb 29: onsuccess: #536: 1: Success after binutils/gcc/glibc/gdb [...] new 0eb09762f7 30: onsuccess: #537: 1: Success after binutils/gcc/linux/gli [...] new f4c18eea00 31: onsuccess: #538: 1: Success after binutils/gcc/linux/gli [...] new 2a5e664ebe 32: onsuccess: #539: 1: Success after binutils/gcc/linux/gdb [...] new 9c2c2bf755 33: onsuccess: #540: 1: Success after binutils/gcc/linux/gli [...] new b7bd7ab637 34: onsuccess: #541: 1: Success after binutils/gcc/linux/gli [...] new 1e57af5a20 35: onsuccess: #542: 1: Success after binutils/gcc/linux/gli [...] new 46c247d90d 36: onsuccess: #543: 1: Success after binutils/gcc/linux/gli [...] new 49a193917d 37: onsuccess: #544: 1: Success after binutils/gcc/glibc/gdb [...] new fea91458d4 38: onsuccess: #545: 1: Success after binutils/gcc/linux/gli [...] new b78f07c398 39: onsuccess: #546: 1: Success after binutils/gcc/glibc/gdb [...] new c82d41636a 40: onsuccess: #547: 1: Success after binutils/gcc/linux/gdb [...] new 903701dd4d 41: onsuccess: #548: 1: Success after binutils/gcc/glibc/gdb [...] new 694a200549 42: onsuccess: #549: 1: Success after binutils/gcc/linux/gli [...] new bd398ffd88 43: onsuccess: #550: 1: Success after binutils/gcc/linux/gli [...] new 6c38383553 44: onsuccess: #552: 1: Success after binutils/gcc/linux/gli [...] new 2560d28705 45: onsuccess: #553: 1: Success after binutils/gcc/linux/gdb [...] new 3b6678cef7 46: onsuccess: #554: 1: Success after binutils/gcc/linux/gdb [...] new 78d9d2045e 47: onsuccess: #556: 1: Success after binutils: 12 commits new 76051e3ca4 48: onsuccess: #559: 1: Success after binutils: 6 commits new d8c6917917 49: onsuccess: #562: 1: Success after binutils: 9 commits new 13ec2ad7cf 50: onsuccess: #564: 1: Success after binutils/gcc/linux/gli [...] new 8b05b6cc5f 51: onsuccess: #565: 1: Success after binutils/gcc/linux/gli [...] new cf6eafd3ab 52: onsuccess: #566: 1: Success after binutils/gcc/linux/gli [...] new f83c18b024 53: onsuccess: #567: 1: Success after binutils/gcc/linux/gdb [...] new d4b66f9882 54: onsuccess: #568: 1: Success after binutils/gcc/linux/gli [...] new a8c6e04111 55: onsuccess: #569: 1: Success after binutils/gcc/linux/gli [...] new eee37d9b78 56: onsuccess: #570: 1: Success after binutils/gcc/linux/gli [...] new 8e149ba60e 57: onsuccess: #571: 1: Success after binutils/gcc/linux/gli [...] new f63aba7f35 58: onsuccess: #572: 1: Success after binutils/gcc/linux/gli [...] new de5cd3d82c 59: onsuccess: #573: 1: Success after binutils/gcc/linux/gli [...] new b17322e3d0 60: onsuccess: #574: 1: Success after binutils/gcc/linux/gli [...] new afbc24dee6 61: onsuccess: #575: 1: Success after binutils/gcc/linux/gli [...] new fc7a877cc4 62: onsuccess: #576: 1: Success after binutils/gcc/linux/gdb [...] new 4942ce357f 63: onsuccess: #577: 1: Success after binutils/gcc/linux/gli [...] new aa2cccc1a9 64: onsuccess: #579: 1: Success after binutils/gcc/linux/gli [...] new b638a3b0b0 65: onsuccess: #580: 1: Success after binutils/gcc/linux/gdb [...] new 2250b22384 66: onsuccess: #581: 1: Success after binutils/gcc/linux/gli [...] new db729f16c6 67: onsuccess: #582: 1: Success after binutils/gcc/linux/gdb [...] new 326c8b65c5 68: onsuccess: #583: 1: Success after binutils/gcc/linux/gli [...] new 7adfaf4db8 69: onsuccess: #584: 1: Success after binutils/gcc/glibc/gdb [...] new a0a8c4bca7 70: onsuccess: #585: 1: Success after binutils/gcc/linux/gli [...] new 4163abdf54 71: onsuccess: #586: 1: Success after binutils/gcc/linux/gdb [...] new ec44315036 72: onsuccess: #587: 1: Success after binutils/gcc/linux/gdb [...] new 65a2c4fb37 73: onsuccess: #588: 1: Success after binutils/gcc/linux/gdb [...] new 4fdb60b1ab 74: onsuccess: #590: 1: Success after binutils: 16 commits new 7f9c944af8 75: onsuccess: #591: 1: Success after gcc: 25 commits new d4b56a5c58 76: onsuccess: #592: 1: Success after linux: 63 commits new e394edd339 77: onsuccess: #593: 1: Success after binutils/gcc/linux/gli [...] new 4ac4694c2f 78: onsuccess: #594: 1: Success after binutils/gcc/linux/gli [...] new 925210ae03 79: onsuccess: #595: 1: Success after binutils/gcc/linux/gli [...] new 49e777cb75 80: onsuccess: #596: 1: Success after binutils/gcc/linux/gli [...] new 6d38f657cb 81: onsuccess: #597: 1: Success after binutils/gcc/linux/gdb [...] new cca7bd2492 82: onsuccess: #598: 1: Success after binutils/gcc/linux/gli [...] new 341cf8eb2e 83: onsuccess: #599: 1: Success after binutils/gcc/linux/gli [...] new 86695c02c4 84: onsuccess: #600: 1: Success after binutils/gcc/linux/gli [...] new ecc5a362fc 85: onsuccess: #601: 1: Success after binutils/gcc/linux/gli [...] new 0c8b84f3cd 86: onsuccess: #602: 1: Success after binutils/gcc/linux/gli [...] new d27dcc3dad 87: onsuccess: #603: 1: Success after binutils/gcc/linux/gli [...] new c8f2eb90c7 88: onsuccess: #604: 1: Success after binutils/gcc/linux/gdb [...] new 7cad9eac8e 89: onsuccess: #605: 1: Success after binutils/gcc/linux/gdb [...] new 7c7b6be72b 90: onsuccess: #606: 1: Success after binutils/gcc/linux/gli [...] new f4958f7e63 91: onsuccess: #610: 1: Success after binutils/gcc/linux/gli [...] new dd1721fed8 92: onsuccess: #611: 1: Success after binutils/gcc/linux/gli [...] new eea98c2881 93: onsuccess: #613: 1: Success after binutils: 19 commits new 86ad45c436 94: onsuccess: #616: 1: Success after binutils: 2 commits new 11226f183b 95: onsuccess: #619: 1: Success after binutils: 5 commits new c6206080e6 96: onsuccess: #621: 1: Success after binutils/gcc/linux/gli [...] new 1a0bbd44bd 97: onsuccess: #622: 1: Success after binutils/gcc/gdb: 8 commits new 766d9634d2 98: onsuccess: #623: 1: Success after binutils/gcc/linux/gdb [...] new 11504226a8 99: onsuccess: #624: 1: Success after binutils/gcc/linux/gli [...] new 1575423a36 100: onsuccess: #625: 1: Success after binutils/gcc/linux/gd [...] new c3fff22bd2 101: onsuccess: #627: 1: Success after binutils/gcc/linux/gd [...] new 8696e774ba 102: onsuccess: #628: 1: Success after binutils/gcc/glibc/gd [...] new 569d284981 103: onsuccess: #629: 1: Success after binutils/gcc/gdb: 68 commits new 2786e9448d 104: onsuccess: #630: 1: Success after binutils/gcc/linux/gd [...] new 5539ebbd65 105: onsuccess: #631: 1: Success after binutils/gcc/linux/gd [...] new 53df92a219 106: onsuccess: #635: 1: Success after binutils/gcc/linux/gd [...] new bd6749f998 107: onsuccess: #636: 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 (6199e678f1) \ 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 -> 1704 bytes 02-prepare_abe/console.log.xz | Bin 2728 -> 2712 bytes 03-build_abe-binutils/console.log.xz | Bin 39832 -> 39836 bytes 04-build_abe-gcc/console.log.xz | Bin 212648 -> 215520 bytes 05-clean_sysroot/console.log.xz | Bin 312 -> 312 bytes 06-build_abe-linux/console.log.xz | Bin 8572 -> 8500 bytes 07-build_abe-glibc/console.log.xz | Bin 244496 -> 244100 bytes 08-build_abe-gdb/console.log.xz | Bin 38924 -> 39144 bytes 09-build_abe-dejagnu/console.log.xz | Bin 3836 -> 3832 bytes 10-build_abe-check_binutils/console.log.xz | Bin 2048 -> 2332 bytes 11-check_regression/console.log.xz | Bin 5808 -> 6064 bytes 11-check_regression/results.compare | 8 +- 11-check_regression/results.compare2 | 6 +- 12-update_baseline/console.log | 34 +-- 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 63012 -> 63160 bytes sumfiles/binutils.sum | 62 +++--- sumfiles/gas.log.xz | Bin 81724 -> 81752 bytes sumfiles/gas.sum | 272 +++++++++++------------ sumfiles/ld.log.xz | Bin 121644 -> 121732 bytes sumfiles/ld.sum | 346 ++++++++++++++--------------- 30 files changed, 391 insertions(+), 391 deletions(-)