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 319556d762f 112: onsuccess: #641: 1: Success after binutils/gcc/linux/g [...] discards 697c041eba8 111: onsuccess: #640: 1: Success after binutils/gcc/linux/g [...] discards 0565536ae52 110: onsuccess: #639: 1: Success after binutils/gcc/linux/g [...] discards 4159c05f548 109: onsuccess: #638: 1: Success after binutils/gcc/linux/g [...] discards 50840e8a911 108: onsuccess: #637: 1: Success after binutils/gcc/linux/g [...] discards b1de3f2cc26 107: onsuccess: #636: 1: Success after binutils/gcc/linux/g [...] discards acd6fa5cde6 106: onsuccess: #635: 1: Success after binutils/gcc/linux/g [...] discards b62eb559bbb 105: onsuccess: #631: 1: Success after binutils/gcc/linux/g [...] discards 00a0ab659d5 104: onsuccess: #630: 1: Success after binutils/gcc/linux/g [...] discards 32a310a2d5a 103: onsuccess: #629: 1: Success after binutils/gcc/gdb: 68 [...] discards 1c4f1185259 102: onsuccess: #628: 1: Success after binutils/gcc/glibc/g [...] discards 640d1ac7718 101: onsuccess: #627: 1: Success after binutils/gcc/linux/g [...] discards faa6eb05448 100: onsuccess: #625: 1: Success after binutils/gcc/linux/g [...] discards d72015cfc88 99: onsuccess: #624: 1: Success after binutils/gcc/linux/gl [...] discards 7b4e447e875 98: onsuccess: #623: 1: Success after binutils/gcc/linux/gd [...] discards 2e87a7552a7 97: onsuccess: #622: 1: Success after binutils/gcc/gdb: 8 commits discards c0cb44f7336 96: onsuccess: #621: 1: Success after binutils/gcc/linux/gl [...] discards e2927bd79eb 95: onsuccess: #619: 1: Success after binutils: 5 commits discards 1a8481c6881 94: onsuccess: #616: 1: Success after binutils: 2 commits discards 62669774570 93: onsuccess: #613: 1: Success after binutils: 19 commits discards 5089caf287f 92: onsuccess: #611: 1: Success after binutils/gcc/linux/gl [...] discards 38553f78d2b 91: onsuccess: #610: 1: Success after binutils/gcc/linux/gl [...] discards 0e8a82986ec 90: onsuccess: #606: 1: Success after binutils/gcc/linux/gl [...] discards 961a0324af2 89: onsuccess: #605: 1: Success after binutils/gcc/linux/gd [...] discards 83e7e7841f4 88: onsuccess: #604: 1: Success after binutils/gcc/linux/gd [...] discards a9689d05dc7 87: onsuccess: #603: 1: Success after binutils/gcc/linux/gl [...] discards e87f0690acf 86: onsuccess: #602: 1: Success after binutils/gcc/linux/gl [...] discards 2d8ab0f1187 85: onsuccess: #601: 1: Success after binutils/gcc/linux/gl [...] discards dce0e221f69 84: onsuccess: #600: 1: Success after binutils/gcc/linux/gl [...] discards 25d6c775c99 83: onsuccess: #599: 1: Success after binutils/gcc/linux/gl [...] discards 5f3cd063c82 82: onsuccess: #598: 1: Success after binutils/gcc/linux/gl [...] discards 92f4ac59878 81: onsuccess: #597: 1: Success after binutils/gcc/linux/gd [...] discards 3a726ac7830 80: onsuccess: #596: 1: Success after binutils/gcc/linux/gl [...] discards ba7a0cf4afe 79: onsuccess: #595: 1: Success after binutils/gcc/linux/gl [...] discards 3f08a7ed5f2 78: onsuccess: #594: 1: Success after binutils/gcc/linux/gl [...] discards f3c48428680 77: onsuccess: #593: 1: Success after binutils/gcc/linux/gl [...] discards 9c312005472 76: onsuccess: #592: 1: Success after linux: 63 commits discards 4d5904786ba 75: onsuccess: #591: 1: Success after gcc: 25 commits discards e8a51519e9b 74: onsuccess: #590: 1: Success after binutils: 16 commits discards 0ed2aaa86bc 73: onsuccess: #588: 1: Success after binutils/gcc/linux/gd [...] discards 35c0eac4bff 72: onsuccess: #587: 1: Success after binutils/gcc/linux/gd [...] discards 5f43892ff98 71: onsuccess: #586: 1: Success after binutils/gcc/linux/gd [...] discards 7efd467ea93 70: onsuccess: #585: 1: Success after binutils/gcc/linux/gl [...] discards 3a6a2732d7c 69: onsuccess: #584: 1: Success after binutils/gcc/glibc/gd [...] discards c8bbab7f980 68: onsuccess: #583: 1: Success after binutils/gcc/linux/gl [...] discards 215dcc05f8f 67: onsuccess: #582: 1: Success after binutils/gcc/linux/gd [...] discards 90a42825b52 66: onsuccess: #581: 1: Success after binutils/gcc/linux/gl [...] discards b23aa2967cb 65: onsuccess: #580: 1: Success after binutils/gcc/linux/gd [...] discards 3f24b9e47f6 64: onsuccess: #579: 1: Success after binutils/gcc/linux/gl [...] discards c501b2aa1d4 63: onsuccess: #577: 1: Success after binutils/gcc/linux/gl [...] discards e52fc8d2f24 62: onsuccess: #576: 1: Success after binutils/gcc/linux/gd [...] discards ddedd9efc92 61: onsuccess: #575: 1: Success after binutils/gcc/linux/gl [...] discards 72cfd198852 60: onsuccess: #574: 1: Success after binutils/gcc/linux/gl [...] discards 8f31dc75c92 59: onsuccess: #573: 1: Success after binutils/gcc/linux/gl [...] discards 03587442175 58: onsuccess: #572: 1: Success after binutils/gcc/linux/gl [...] discards 9f2c35ec7c0 57: onsuccess: #571: 1: Success after binutils/gcc/linux/gl [...] discards 26e650acde0 56: onsuccess: #570: 1: Success after binutils/gcc/linux/gl [...] discards 1b980920895 55: onsuccess: #569: 1: Success after binutils/gcc/linux/gl [...] discards 443e201e8e3 54: onsuccess: #568: 1: Success after binutils/gcc/linux/gl [...] discards 5bf0e1eb0b4 53: onsuccess: #567: 1: Success after binutils/gcc/linux/gd [...] discards 773ace5667b 52: onsuccess: #566: 1: Success after binutils/gcc/linux/gl [...] discards 0133cc9d2cb 51: onsuccess: #565: 1: Success after binutils/gcc/linux/gl [...] discards aeb020ff688 50: onsuccess: #564: 1: Success after binutils/gcc/linux/gl [...] discards 9764823e004 49: onsuccess: #562: 1: Success after binutils: 9 commits discards d3c9e51f90b 48: onsuccess: #559: 1: Success after binutils: 6 commits discards 16993a26700 47: onsuccess: #556: 1: Success after binutils: 12 commits discards 0a7bca08ffd 46: onsuccess: #554: 1: Success after binutils/gcc/linux/gd [...] discards 12c1fc74c53 45: onsuccess: #553: 1: Success after binutils/gcc/linux/gd [...] discards 1f56eea1879 44: onsuccess: #552: 1: Success after binutils/gcc/linux/gl [...] discards 6f2e23c043a 43: onsuccess: #550: 1: Success after binutils/gcc/linux/gl [...] discards bf84cf17e40 42: onsuccess: #549: 1: Success after binutils/gcc/linux/gl [...] discards a58b412696f 41: onsuccess: #548: 1: Success after binutils/gcc/glibc/gd [...] discards 5bb2415093c 40: onsuccess: #547: 1: Success after binutils/gcc/linux/gd [...] discards d3d80b1f28d 39: onsuccess: #546: 1: Success after binutils/gcc/glibc/gd [...] discards d74973d29d4 38: onsuccess: #545: 1: Success after binutils/gcc/linux/gl [...] discards f9a21983764 37: onsuccess: #544: 1: Success after binutils/gcc/glibc/gd [...] discards a9cf550fb72 36: onsuccess: #543: 1: Success after binutils/gcc/linux/gl [...] discards ca7d85a5404 35: onsuccess: #542: 1: Success after binutils/gcc/linux/gl [...] discards 90a5ffbebc7 34: onsuccess: #541: 1: Success after binutils/gcc/linux/gl [...] discards 5efdf74673e 33: onsuccess: #540: 1: Success after binutils/gcc/linux/gl [...] discards 3954d2e74c4 32: onsuccess: #539: 1: Success after binutils/gcc/linux/gd [...] discards 30030057191 31: onsuccess: #538: 1: Success after binutils/gcc/linux/gl [...] discards 112c3e5e307 30: onsuccess: #537: 1: Success after binutils/gcc/linux/gl [...] discards 7df6326604c 29: onsuccess: #536: 1: Success after binutils/gcc/glibc/gd [...] discards d7d91c6fb9e 28: onsuccess: #535: 1: Success after binutils/gcc/linux/gl [...] discards e06ccb1b89f 27: onsuccess: #534: 1: Success after binutils/gcc/linux/gl [...] discards 37366a5ce18 26: onsuccess: #533: 1: Success after binutils/gcc/linux/gd [...] discards 9d18f211bf0 25: onsuccess: #532: 1: Success after binutils/gcc/linux/gd [...] discards 10a6b899125 24: onsuccess: 1: Success after binutils/gcc/linux/gdb: 216 [...] discards 6d53903a50f 23: onsuccess: 1: Success after binutils/gcc/linux/gdb: 129 [...] discards 660d1b92eed 22: onsuccess: 1: Success after binutils/gcc/linux/glibc/gd [...] discards a3731e34b3b 21: onsuccess: 1: Successful build after binutils/gcc/linux [...] discards f59b2fb3a07 20: onsuccess: 1: Successful build after binutils/gcc/linux [...] discards 34b6e404ee9 19: onsuccess: 1: Successful build after binutils/gcc/linux [...] discards 82f29b4e747 18: onsuccess: 1: Successful build after binutils/gcc/linux [...] discards 68dd93df2f2 17: onsuccess: 1: Successful build after binutils/gcc/glibc [...] discards 91178a9c6ca 16: onsuccess: 1: Successful build after binutils/gcc/linux [...] discards a25c73ca26f 15: onsuccess: 1: Successful build after binutils/gcc/linux [...] discards b57e0cbf4ff 14: onsuccess: 1: Successful build after binutils/gcc/linux [...] discards e7a38778d60 13: onsuccess: 1: Successful build after binutils/gcc/linux [...] discards 62e8c3c343c 12: onsuccess: 1: Successful build after binutils/gcc/linux [...] new 3b27055936f 12: onsuccess: 1: Successful build after binutils/gcc/linux [...] new 4a68ed3e53b 13: onsuccess: 1: Successful build after binutils/gcc/linux [...] new 7e136f60087 14: onsuccess: 1: Successful build after binutils/gcc/linux [...] new e710d1881c2 15: onsuccess: 1: Successful build after binutils/gcc/linux [...] new 2a5566e8137 16: onsuccess: 1: Successful build after binutils/gcc/linux [...] new 378bf86c498 17: onsuccess: 1: Successful build after binutils/gcc/glibc [...] new e3de6f36a56 18: onsuccess: 1: Successful build after binutils/gcc/linux [...] new 4917cbf9c58 19: onsuccess: 1: Successful build after binutils/gcc/linux [...] new cacaf36b718 20: onsuccess: 1: Successful build after binutils/gcc/linux [...] new 01315dc877a 21: onsuccess: 1: Successful build after binutils/gcc/linux [...] new e2c79dee38a 22: onsuccess: 1: Success after binutils/gcc/linux/glibc/gd [...] new 6c028a7d634 23: onsuccess: 1: Success after binutils/gcc/linux/gdb: 129 [...] new 2348308f51e 24: onsuccess: 1: Success after binutils/gcc/linux/gdb: 216 [...] new 22f03520744 25: onsuccess: #532: 1: Success after binutils/gcc/linux/gd [...] new 7ee75d746b6 26: onsuccess: #533: 1: Success after binutils/gcc/linux/gd [...] new 5502da83dc5 27: onsuccess: #534: 1: Success after binutils/gcc/linux/gl [...] new 9719ea2b8a4 28: onsuccess: #535: 1: Success after binutils/gcc/linux/gl [...] new 70cc1a46511 29: onsuccess: #536: 1: Success after binutils/gcc/glibc/gd [...] new 23105e32714 30: onsuccess: #537: 1: Success after binutils/gcc/linux/gl [...] new dbeebf28817 31: onsuccess: #538: 1: Success after binutils/gcc/linux/gl [...] new c313d41aea9 32: onsuccess: #539: 1: Success after binutils/gcc/linux/gd [...] new 8e91229b7c3 33: onsuccess: #540: 1: Success after binutils/gcc/linux/gl [...] new 01f0ee7850a 34: onsuccess: #541: 1: Success after binutils/gcc/linux/gl [...] new fc7bedc0899 35: onsuccess: #542: 1: Success after binutils/gcc/linux/gl [...] new 1ca0f50ea6d 36: onsuccess: #543: 1: Success after binutils/gcc/linux/gl [...] new 689d6c913a2 37: onsuccess: #544: 1: Success after binutils/gcc/glibc/gd [...] new c941b896236 38: onsuccess: #545: 1: Success after binutils/gcc/linux/gl [...] new e56693d1ac8 39: onsuccess: #546: 1: Success after binutils/gcc/glibc/gd [...] new 57642415099 40: onsuccess: #547: 1: Success after binutils/gcc/linux/gd [...] new 3c0cb0e60d0 41: onsuccess: #548: 1: Success after binutils/gcc/glibc/gd [...] new 97eec47d9c8 42: onsuccess: #549: 1: Success after binutils/gcc/linux/gl [...] new cfe29dae29a 43: onsuccess: #550: 1: Success after binutils/gcc/linux/gl [...] new 616de4e47d1 44: onsuccess: #552: 1: Success after binutils/gcc/linux/gl [...] new 346091567f5 45: onsuccess: #553: 1: Success after binutils/gcc/linux/gd [...] new afea37a5099 46: onsuccess: #554: 1: Success after binutils/gcc/linux/gd [...] new 12ba67fa5f0 47: onsuccess: #556: 1: Success after binutils: 12 commits new 2c6ef7682e9 48: onsuccess: #559: 1: Success after binutils: 6 commits new f2ea97975b1 49: onsuccess: #562: 1: Success after binutils: 9 commits new ff8bf40dd4e 50: onsuccess: #564: 1: Success after binutils/gcc/linux/gl [...] new 1a4f96db6d3 51: onsuccess: #565: 1: Success after binutils/gcc/linux/gl [...] new 2700f0d707d 52: onsuccess: #566: 1: Success after binutils/gcc/linux/gl [...] new dc83376614a 53: onsuccess: #567: 1: Success after binutils/gcc/linux/gd [...] new ce775644268 54: onsuccess: #568: 1: Success after binutils/gcc/linux/gl [...] new b1c3e3c1675 55: onsuccess: #569: 1: Success after binutils/gcc/linux/gl [...] new 33aae499f5f 56: onsuccess: #570: 1: Success after binutils/gcc/linux/gl [...] new 019249b7c55 57: onsuccess: #571: 1: Success after binutils/gcc/linux/gl [...] new 9b5923505e7 58: onsuccess: #572: 1: Success after binutils/gcc/linux/gl [...] new 42c634aa1a5 59: onsuccess: #573: 1: Success after binutils/gcc/linux/gl [...] new 0bbc5fad06b 60: onsuccess: #574: 1: Success after binutils/gcc/linux/gl [...] new bb0ddc7d985 61: onsuccess: #575: 1: Success after binutils/gcc/linux/gl [...] new ba9ca7a56a5 62: onsuccess: #576: 1: Success after binutils/gcc/linux/gd [...] new e18393e91ba 63: onsuccess: #577: 1: Success after binutils/gcc/linux/gl [...] new 86bbdde7db6 64: onsuccess: #579: 1: Success after binutils/gcc/linux/gl [...] new 7417f3b1de0 65: onsuccess: #580: 1: Success after binutils/gcc/linux/gd [...] new 3b77b613e89 66: onsuccess: #581: 1: Success after binutils/gcc/linux/gl [...] new f4469ce39bd 67: onsuccess: #582: 1: Success after binutils/gcc/linux/gd [...] new f794963bd2a 68: onsuccess: #583: 1: Success after binutils/gcc/linux/gl [...] new 953f62e5948 69: onsuccess: #584: 1: Success after binutils/gcc/glibc/gd [...] new 56b770996db 70: onsuccess: #585: 1: Success after binutils/gcc/linux/gl [...] new 56ae8e84084 71: onsuccess: #586: 1: Success after binutils/gcc/linux/gd [...] new a46076ccc32 72: onsuccess: #587: 1: Success after binutils/gcc/linux/gd [...] new 978cc103cf3 73: onsuccess: #588: 1: Success after binutils/gcc/linux/gd [...] new a3ae4f8946f 74: onsuccess: #590: 1: Success after binutils: 16 commits new d32c1114ed3 75: onsuccess: #591: 1: Success after gcc: 25 commits new e09b0fb472d 76: onsuccess: #592: 1: Success after linux: 63 commits new b9f6e42dd48 77: onsuccess: #593: 1: Success after binutils/gcc/linux/gl [...] new 4a8505ed4ab 78: onsuccess: #594: 1: Success after binutils/gcc/linux/gl [...] new ba1b336f096 79: onsuccess: #595: 1: Success after binutils/gcc/linux/gl [...] new 95043eace45 80: onsuccess: #596: 1: Success after binutils/gcc/linux/gl [...] new 9102292f58f 81: onsuccess: #597: 1: Success after binutils/gcc/linux/gd [...] new fe78238ffae 82: onsuccess: #598: 1: Success after binutils/gcc/linux/gl [...] new b643bc2c62d 83: onsuccess: #599: 1: Success after binutils/gcc/linux/gl [...] new bed2aaf8be3 84: onsuccess: #600: 1: Success after binutils/gcc/linux/gl [...] new f8f7de1a6d1 85: onsuccess: #601: 1: Success after binutils/gcc/linux/gl [...] new 649331d9db6 86: onsuccess: #602: 1: Success after binutils/gcc/linux/gl [...] new 3bd0a10ca14 87: onsuccess: #603: 1: Success after binutils/gcc/linux/gl [...] new 56678ce16f5 88: onsuccess: #604: 1: Success after binutils/gcc/linux/gd [...] new 5be8258e436 89: onsuccess: #605: 1: Success after binutils/gcc/linux/gd [...] new 4e8a9ba22ad 90: onsuccess: #606: 1: Success after binutils/gcc/linux/gl [...] new f1891f1b4f8 91: onsuccess: #610: 1: Success after binutils/gcc/linux/gl [...] new f7e305cc6e7 92: onsuccess: #611: 1: Success after binutils/gcc/linux/gl [...] new 30485e780fe 93: onsuccess: #613: 1: Success after binutils: 19 commits new 3d0965a8871 94: onsuccess: #616: 1: Success after binutils: 2 commits new 93213d137d1 95: onsuccess: #619: 1: Success after binutils: 5 commits new b32e7c43e6b 96: onsuccess: #621: 1: Success after binutils/gcc/linux/gl [...] new 033b9fef068 97: onsuccess: #622: 1: Success after binutils/gcc/gdb: 8 commits new bc1764e74ca 98: onsuccess: #623: 1: Success after binutils/gcc/linux/gd [...] new fc132e5fec9 99: onsuccess: #624: 1: Success after binutils/gcc/linux/gl [...] new 7a03956ea99 100: onsuccess: #625: 1: Success after binutils/gcc/linux/g [...] new 5b39eebad14 101: onsuccess: #627: 1: Success after binutils/gcc/linux/g [...] new 14cf356cd6f 102: onsuccess: #628: 1: Success after binutils/gcc/glibc/g [...] new 522b70735dd 103: onsuccess: #629: 1: Success after binutils/gcc/gdb: 68 [...] new 3ed511e55b7 104: onsuccess: #630: 1: Success after binutils/gcc/linux/g [...] new 57ba8206629 105: onsuccess: #631: 1: Success after binutils/gcc/linux/g [...] new c51067d5815 106: onsuccess: #635: 1: Success after binutils/gcc/linux/g [...] new d109077280b 107: onsuccess: #636: 1: Success after binutils/gcc/linux/g [...] new c28c0ebacc8 108: onsuccess: #637: 1: Success after binutils/gcc/linux/g [...] new f65a58a4a96 109: onsuccess: #638: 1: Success after binutils/gcc/linux/g [...] new 24765eda344 110: onsuccess: #639: 1: Success after binutils/gcc/linux/g [...] new 3e3e3e5a98c 111: onsuccess: #640: 1: Success after binutils/gcc/linux/g [...] new ebfc0463555 112: onsuccess: #641: 1: Success after binutils/gcc/linux/g [...] new 8f98712ee88 113: onsuccess: #642: 1: Success after binutils/gcc/linux/g [...]

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 (319556d762f) \ 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 -> 1768 bytes 02-prepare_abe/console.log.xz | Bin 2760 -> 2744 bytes 03-build_abe-binutils/console.log.xz | Bin 39848 -> 39096 bytes 04-build_abe-gcc/console.log.xz | Bin 216316 -> 212144 bytes 05-clean_sysroot/console.log.xz | Bin 312 -> 312 bytes 06-build_abe-linux/console.log.xz | Bin 8516 -> 8596 bytes 07-build_abe-glibc/console.log.xz | Bin 244552 -> 244256 bytes 08-build_abe-gdb/console.log.xz | Bin 38508 -> 38976 bytes 09-build_abe-dejagnu/console.log.xz | Bin 3832 -> 3848 bytes 10-build_abe-check_binutils/console.log.xz | Bin 2060 -> 2160 bytes 11-check_regression/console.log.xz | Bin 6152 -> 5544 bytes 11-check_regression/results.compare | 8 +- 11-check_regression/results.compare2 | 6 +- 12-update_baseline/console.log | 38 ++-- 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 63124 -> 63056 bytes sumfiles/binutils.sum | 62 +++--- sumfiles/gas.log.xz | Bin 81768 -> 81832 bytes sumfiles/gas.sum | 272 +++++++++++------------ sumfiles/ld.log.xz | Bin 121928 -> 121756 bytes sumfiles/ld.sum | 346 ++++++++++++++--------------- 29 files changed, 390 insertions(+), 390 deletions(-)