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 4ff0572fd2 105: onsuccess: #631: 1: Success after binutils/gcc/linux/gd [...] discards e45fb08bae 104: onsuccess: #630: 1: Success after binutils/gcc/linux/gd [...] discards d8c69f7259 103: onsuccess: #629: 1: Success after binutils/gcc/gdb: 68 commits discards 6690efd542 102: onsuccess: #628: 1: Success after binutils/gcc/glibc/gd [...] discards c5b37a0e4d 101: onsuccess: #627: 1: Success after binutils/gcc/linux/gd [...] discards 9be99d420e 100: onsuccess: #625: 1: Success after binutils/gcc/linux/gd [...] discards 28f814fb1e 99: onsuccess: #624: 1: Success after binutils/gcc/linux/gli [...] discards b98db157b2 98: onsuccess: #623: 1: Success after binutils/gcc/linux/gdb [...] discards ba87223c81 97: onsuccess: #622: 1: Success after binutils/gcc/gdb: 8 commits discards b4d138268f 96: onsuccess: #621: 1: Success after binutils/gcc/linux/gli [...] discards d285db7fb0 95: onsuccess: #619: 1: Success after binutils: 5 commits discards e6466b7f8c 94: onsuccess: #616: 1: Success after binutils: 2 commits discards 9d5ef66892 93: onsuccess: #613: 1: Success after binutils: 19 commits discards 91a0a716c8 92: onsuccess: #611: 1: Success after binutils/gcc/linux/gli [...] discards 831e8d4d31 91: onsuccess: #610: 1: Success after binutils/gcc/linux/gli [...] discards 9cbf28e1fd 90: onsuccess: #606: 1: Success after binutils/gcc/linux/gli [...] discards a9934b0f27 89: onsuccess: #605: 1: Success after binutils/gcc/linux/gdb [...] discards 4aa16f3cfa 88: onsuccess: #604: 1: Success after binutils/gcc/linux/gdb [...] discards b281444793 87: onsuccess: #603: 1: Success after binutils/gcc/linux/gli [...] discards 09fe88329d 86: onsuccess: #602: 1: Success after binutils/gcc/linux/gli [...] discards b661d10747 85: onsuccess: #601: 1: Success after binutils/gcc/linux/gli [...] discards 5367040edd 84: onsuccess: #600: 1: Success after binutils/gcc/linux/gli [...] discards c2e297d835 83: onsuccess: #599: 1: Success after binutils/gcc/linux/gli [...] discards b541591641 82: onsuccess: #598: 1: Success after binutils/gcc/linux/gli [...] discards 27bdfc28ee 81: onsuccess: #597: 1: Success after binutils/gcc/linux/gdb [...] discards 085e42b1f2 80: onsuccess: #596: 1: Success after binutils/gcc/linux/gli [...] discards 6bf5fa0b56 79: onsuccess: #595: 1: Success after binutils/gcc/linux/gli [...] discards aa9618a92d 78: onsuccess: #594: 1: Success after binutils/gcc/linux/gli [...] discards 2dc869a773 77: onsuccess: #593: 1: Success after binutils/gcc/linux/gli [...] discards 4932f15bd9 76: onsuccess: #592: 1: Success after linux: 63 commits discards c5f58ddb30 75: onsuccess: #591: 1: Success after gcc: 25 commits discards 6e440540d0 74: onsuccess: #590: 1: Success after binutils: 16 commits discards 5a8b033ef4 73: onsuccess: #588: 1: Success after binutils/gcc/linux/gdb [...] discards aeb7fe86ed 72: onsuccess: #587: 1: Success after binutils/gcc/linux/gdb [...] discards 6f6f367959 71: onsuccess: #586: 1: Success after binutils/gcc/linux/gdb [...] discards 83b43ebf52 70: onsuccess: #585: 1: Success after binutils/gcc/linux/gli [...] discards 0a890b43af 69: onsuccess: #584: 1: Success after binutils/gcc/glibc/gdb [...] discards 85659fa1d2 68: onsuccess: #583: 1: Success after binutils/gcc/linux/gli [...] discards 6a1dd54ddc 67: onsuccess: #582: 1: Success after binutils/gcc/linux/gdb [...] discards 314b980b4b 66: onsuccess: #581: 1: Success after binutils/gcc/linux/gli [...] discards 305e8f86b0 65: onsuccess: #580: 1: Success after binutils/gcc/linux/gdb [...] discards e78e0f05a0 64: onsuccess: #579: 1: Success after binutils/gcc/linux/gli [...] discards 683db576e2 63: onsuccess: #577: 1: Success after binutils/gcc/linux/gli [...] discards 0d780ac951 62: onsuccess: #576: 1: Success after binutils/gcc/linux/gdb [...] discards bcf42e9e95 61: onsuccess: #575: 1: Success after binutils/gcc/linux/gli [...] discards 44ad92b61c 60: onsuccess: #574: 1: Success after binutils/gcc/linux/gli [...] discards 7e1001c3aa 59: onsuccess: #573: 1: Success after binutils/gcc/linux/gli [...] discards eae0c4acb4 58: onsuccess: #572: 1: Success after binutils/gcc/linux/gli [...] discards eb9379e2d8 57: onsuccess: #571: 1: Success after binutils/gcc/linux/gli [...] discards 4149491b9f 56: onsuccess: #570: 1: Success after binutils/gcc/linux/gli [...] discards 7f0aec5241 55: onsuccess: #569: 1: Success after binutils/gcc/linux/gli [...] discards 3e9a71b4ff 54: onsuccess: #568: 1: Success after binutils/gcc/linux/gli [...] discards 9b6f16f12c 53: onsuccess: #567: 1: Success after binutils/gcc/linux/gdb [...] discards 6c2d2cc8e0 52: onsuccess: #566: 1: Success after binutils/gcc/linux/gli [...] discards d02dca45d7 51: onsuccess: #565: 1: Success after binutils/gcc/linux/gli [...] discards 4c0d6a1a08 50: onsuccess: #564: 1: Success after binutils/gcc/linux/gli [...] discards 430b68cc7a 49: onsuccess: #562: 1: Success after binutils: 9 commits discards d31c626577 48: onsuccess: #559: 1: Success after binutils: 6 commits discards 3c00412a6b 47: onsuccess: #556: 1: Success after binutils: 12 commits discards a9c10f882b 46: onsuccess: #554: 1: Success after binutils/gcc/linux/gdb [...] discards e201151150 45: onsuccess: #553: 1: Success after binutils/gcc/linux/gdb [...] discards cbc9a47c39 44: onsuccess: #552: 1: Success after binutils/gcc/linux/gli [...] discards 4235a020a4 43: onsuccess: #550: 1: Success after binutils/gcc/linux/gli [...] discards c20244a7e7 42: onsuccess: #549: 1: Success after binutils/gcc/linux/gli [...] discards 84cf1328e1 41: onsuccess: #548: 1: Success after binutils/gcc/glibc/gdb [...] discards bb496652af 40: onsuccess: #547: 1: Success after binutils/gcc/linux/gdb [...] discards 71bdf04d79 39: onsuccess: #546: 1: Success after binutils/gcc/glibc/gdb [...] discards f419f32e1e 38: onsuccess: #545: 1: Success after binutils/gcc/linux/gli [...] discards ad6c7478db 37: onsuccess: #544: 1: Success after binutils/gcc/glibc/gdb [...] discards 6579c26ce4 36: onsuccess: #543: 1: Success after binutils/gcc/linux/gli [...] discards 0b0f1fde69 35: onsuccess: #542: 1: Success after binutils/gcc/linux/gli [...] discards f82d829990 34: onsuccess: #541: 1: Success after binutils/gcc/linux/gli [...] discards de4544ef59 33: onsuccess: #540: 1: Success after binutils/gcc/linux/gli [...] discards 6b16ef25ef 32: onsuccess: #539: 1: Success after binutils/gcc/linux/gdb [...] discards 657463ca96 31: onsuccess: #538: 1: Success after binutils/gcc/linux/gli [...] discards 6d933123fa 30: onsuccess: #537: 1: Success after binutils/gcc/linux/gli [...] discards e4c5194063 29: onsuccess: #536: 1: Success after binutils/gcc/glibc/gdb [...] discards 3a07679761 28: onsuccess: #535: 1: Success after binutils/gcc/linux/gli [...] discards 70a5f91fdb 27: onsuccess: #534: 1: Success after binutils/gcc/linux/gli [...] discards 56efc80a8d 26: onsuccess: #533: 1: Success after binutils/gcc/linux/gdb [...] discards a35ff0ec15 25: onsuccess: #532: 1: Success after binutils/gcc/linux/gdb [...] discards 35915a259b 24: onsuccess: 1: Success after binutils/gcc/linux/gdb: 216 commits discards 681cec22b8 23: onsuccess: 1: Success after binutils/gcc/linux/gdb: 129 commits discards dfe93fee3a 22: onsuccess: 1: Success after binutils/gcc/linux/glibc/gdb [...] discards 462fc2c293 21: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 42ecd80e15 20: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 701541441c 19: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 713729ddee 18: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards ba4c1d36ba 17: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] discards 4dc70872da 16: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 3026e3a6ea 15: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 5d542b38dd 14: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards a305d9e72c 13: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards dfa742932e 12: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards d41448d887 11: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards e657710ebe 10: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards f1db2eaabe 9: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] discards 53d6614002 8: onsuccess: binutils-gcc-linux-glibc-gdb: 1 discards a516678184 7: onsuccess: binutils-gcc-linux-glibc-gdb: 1 discards 05f23676cf 6: onsuccess: binutils-gcc-linux-glibc-gdb: 1 discards ba3b770cc3 5: onsuccess: binutils-gcc-linux-glibc-gdb: 1 new 91ed1dcd28 5: onsuccess: binutils-gcc-linux-glibc-gdb: 1 new 020adbe403 6: onsuccess: binutils-gcc-linux-glibc-gdb: 1 new 0a69770618 7: onsuccess: binutils-gcc-linux-glibc-gdb: 1 new 2abb2ffa5f 8: onsuccess: binutils-gcc-linux-glibc-gdb: 1 new 0e707b89e0 9: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] new f5c8c5bbd1 10: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 192a84b0a2 11: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 4324f970b4 12: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new d6613b9851 13: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 7759a81554 14: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new b9e965d775 15: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new e3ca7ea049 16: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 902fdda548 17: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] new f679453215 18: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 88b0319e9b 19: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new dd4e0aab93 20: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new aaa283ede2 21: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 621786f80f 22: onsuccess: 1: Success after binutils/gcc/linux/glibc/gdb [...] new 326c54322b 23: onsuccess: 1: Success after binutils/gcc/linux/gdb: 129 commits new 49978ba140 24: onsuccess: 1: Success after binutils/gcc/linux/gdb: 216 commits new 725becd473 25: onsuccess: #532: 1: Success after binutils/gcc/linux/gdb [...] new 25fc0d5136 26: onsuccess: #533: 1: Success after binutils/gcc/linux/gdb [...] new 8341ac5dd5 27: onsuccess: #534: 1: Success after binutils/gcc/linux/gli [...] new 204fd27c69 28: onsuccess: #535: 1: Success after binutils/gcc/linux/gli [...] new 5010e503db 29: onsuccess: #536: 1: Success after binutils/gcc/glibc/gdb [...] new eacfbb0284 30: onsuccess: #537: 1: Success after binutils/gcc/linux/gli [...] new d939a43acf 31: onsuccess: #538: 1: Success after binutils/gcc/linux/gli [...] new 2ceeb5d8eb 32: onsuccess: #539: 1: Success after binutils/gcc/linux/gdb [...] new 744301bcf0 33: onsuccess: #540: 1: Success after binutils/gcc/linux/gli [...] new cf396ca3f6 34: onsuccess: #541: 1: Success after binutils/gcc/linux/gli [...] new c6de2dc8b8 35: onsuccess: #542: 1: Success after binutils/gcc/linux/gli [...] new 2a6e68cf02 36: onsuccess: #543: 1: Success after binutils/gcc/linux/gli [...] new ba00bb2ce6 37: onsuccess: #544: 1: Success after binutils/gcc/glibc/gdb [...] new aff72e6cc7 38: onsuccess: #545: 1: Success after binutils/gcc/linux/gli [...] new 4125c1ed9f 39: onsuccess: #546: 1: Success after binutils/gcc/glibc/gdb [...] new 71212eabf6 40: onsuccess: #547: 1: Success after binutils/gcc/linux/gdb [...] new 74b2e3016c 41: onsuccess: #548: 1: Success after binutils/gcc/glibc/gdb [...] new f69754a119 42: onsuccess: #549: 1: Success after binutils/gcc/linux/gli [...] new 1deeb79ac3 43: onsuccess: #550: 1: Success after binutils/gcc/linux/gli [...] new 780dda3b0e 44: onsuccess: #552: 1: Success after binutils/gcc/linux/gli [...] new fb3ae6ca34 45: onsuccess: #553: 1: Success after binutils/gcc/linux/gdb [...] new 735e96ef81 46: onsuccess: #554: 1: Success after binutils/gcc/linux/gdb [...] new 59bdeec392 47: onsuccess: #556: 1: Success after binutils: 12 commits new 765707ed33 48: onsuccess: #559: 1: Success after binutils: 6 commits new 79cff7710e 49: onsuccess: #562: 1: Success after binutils: 9 commits new abcf3d3be6 50: onsuccess: #564: 1: Success after binutils/gcc/linux/gli [...] new 9439a2d79a 51: onsuccess: #565: 1: Success after binutils/gcc/linux/gli [...] new 0917c16c2f 52: onsuccess: #566: 1: Success after binutils/gcc/linux/gli [...] new ef58917371 53: onsuccess: #567: 1: Success after binutils/gcc/linux/gdb [...] new a77d0d09cc 54: onsuccess: #568: 1: Success after binutils/gcc/linux/gli [...] new 32aefd4d65 55: onsuccess: #569: 1: Success after binutils/gcc/linux/gli [...] new 77ce07e63f 56: onsuccess: #570: 1: Success after binutils/gcc/linux/gli [...] new b1b2ea1df0 57: onsuccess: #571: 1: Success after binutils/gcc/linux/gli [...] new de74acef7d 58: onsuccess: #572: 1: Success after binutils/gcc/linux/gli [...] new 8d9d0e6378 59: onsuccess: #573: 1: Success after binutils/gcc/linux/gli [...] new 7814b94dd4 60: onsuccess: #574: 1: Success after binutils/gcc/linux/gli [...] new 4b0d316bc8 61: onsuccess: #575: 1: Success after binutils/gcc/linux/gli [...] new 7c10f9dfad 62: onsuccess: #576: 1: Success after binutils/gcc/linux/gdb [...] new 35610de52d 63: onsuccess: #577: 1: Success after binutils/gcc/linux/gli [...] new d025f858e3 64: onsuccess: #579: 1: Success after binutils/gcc/linux/gli [...] new 55c08b66d3 65: onsuccess: #580: 1: Success after binutils/gcc/linux/gdb [...] new 9b1369ecca 66: onsuccess: #581: 1: Success after binutils/gcc/linux/gli [...] new 64b39aa654 67: onsuccess: #582: 1: Success after binutils/gcc/linux/gdb [...] new 96f04418bd 68: onsuccess: #583: 1: Success after binutils/gcc/linux/gli [...] new c13356c65b 69: onsuccess: #584: 1: Success after binutils/gcc/glibc/gdb [...] new 6bf745e036 70: onsuccess: #585: 1: Success after binutils/gcc/linux/gli [...] new 21ecdb371e 71: onsuccess: #586: 1: Success after binutils/gcc/linux/gdb [...] new 945ef41ebb 72: onsuccess: #587: 1: Success after binutils/gcc/linux/gdb [...] new e8d533457e 73: onsuccess: #588: 1: Success after binutils/gcc/linux/gdb [...] new 8bba29cf78 74: onsuccess: #590: 1: Success after binutils: 16 commits new ffc44b5ce3 75: onsuccess: #591: 1: Success after gcc: 25 commits new 3e1b97c01a 76: onsuccess: #592: 1: Success after linux: 63 commits new f072956e6c 77: onsuccess: #593: 1: Success after binutils/gcc/linux/gli [...] new febdf3ab33 78: onsuccess: #594: 1: Success after binutils/gcc/linux/gli [...] new 1da07e058f 79: onsuccess: #595: 1: Success after binutils/gcc/linux/gli [...] new 1cc8e63723 80: onsuccess: #596: 1: Success after binutils/gcc/linux/gli [...] new f2b762037f 81: onsuccess: #597: 1: Success after binutils/gcc/linux/gdb [...] new 49b55e4a02 82: onsuccess: #598: 1: Success after binutils/gcc/linux/gli [...] new 232302b747 83: onsuccess: #599: 1: Success after binutils/gcc/linux/gli [...] new 563abe11cd 84: onsuccess: #600: 1: Success after binutils/gcc/linux/gli [...] new 96ddc0b810 85: onsuccess: #601: 1: Success after binutils/gcc/linux/gli [...] new 594301ed4f 86: onsuccess: #602: 1: Success after binutils/gcc/linux/gli [...] new 6930f3b7d0 87: onsuccess: #603: 1: Success after binutils/gcc/linux/gli [...] new 94f65ea374 88: onsuccess: #604: 1: Success after binutils/gcc/linux/gdb [...] new b0e6fd37c9 89: onsuccess: #605: 1: Success after binutils/gcc/linux/gdb [...] new 7cbba76a04 90: onsuccess: #606: 1: Success after binutils/gcc/linux/gli [...] new 5f71f325e6 91: onsuccess: #610: 1: Success after binutils/gcc/linux/gli [...] new d73d30192e 92: onsuccess: #611: 1: Success after binutils/gcc/linux/gli [...] new d78136e85a 93: onsuccess: #613: 1: Success after binutils: 19 commits new d53799c9ba 94: onsuccess: #616: 1: Success after binutils: 2 commits new 26fe6b64b6 95: onsuccess: #619: 1: Success after binutils: 5 commits new 3b8142c495 96: onsuccess: #621: 1: Success after binutils/gcc/linux/gli [...] new 97c316869a 97: onsuccess: #622: 1: Success after binutils/gcc/gdb: 8 commits new edfd20089b 98: onsuccess: #623: 1: Success after binutils/gcc/linux/gdb [...] new 86c205eb24 99: onsuccess: #624: 1: Success after binutils/gcc/linux/gli [...] new e61d780e8e 100: onsuccess: #625: 1: Success after binutils/gcc/linux/gd [...] new ca4ed217a0 101: onsuccess: #627: 1: Success after binutils/gcc/linux/gd [...] new 29effea6ea 102: onsuccess: #628: 1: Success after binutils/gcc/glibc/gd [...] new 1ee55ba9da 103: onsuccess: #629: 1: Success after binutils/gcc/gdb: 68 commits new 069bbefa83 104: onsuccess: #630: 1: Success after binutils/gcc/linux/gd [...] new 9bdfc45da7 105: onsuccess: #631: 1: Success after binutils/gcc/linux/gd [...] new 6199e678f1 106: onsuccess: #635: 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 (4ff0572fd2) \ 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 1684 -> 1688 bytes 02-prepare_abe/console.log.xz | Bin 2724 -> 2728 bytes 03-build_abe-binutils/console.log.xz | Bin 40156 -> 39832 bytes 04-build_abe-gcc/console.log.xz | Bin 214640 -> 212648 bytes 05-clean_sysroot/console.log.xz | Bin 312 -> 312 bytes 06-build_abe-linux/console.log.xz | Bin 9512 -> 8572 bytes 07-build_abe-glibc/console.log.xz | Bin 243644 -> 244496 bytes 08-build_abe-gdb/console.log.xz | Bin 39608 -> 38924 bytes 09-build_abe-dejagnu/console.log.xz | Bin 3856 -> 3836 bytes 10-build_abe-check_binutils/console.log.xz | Bin 2612 -> 2048 bytes 11-check_regression/console.log.xz | Bin 5876 -> 5808 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 | 34 +-- sumfiles/binutils.log.xz | Bin 62952 -> 63012 bytes sumfiles/binutils.sum | 62 +++--- sumfiles/gas.log.xz | Bin 81728 -> 81724 bytes sumfiles/gas.sum | 272 +++++++++++------------ sumfiles/ld.log.xz | Bin 121712 -> 121644 bytes sumfiles/ld.sum | 346 ++++++++++++++--------------- 29 files changed, 392 insertions(+), 392 deletions(-)