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 8f98712ee88 113: onsuccess: #642: 1: Success after binutils/gcc/linux/g [...] discards ebfc0463555 112: onsuccess: #641: 1: Success after binutils/gcc/linux/g [...] discards 3e3e3e5a98c 111: onsuccess: #640: 1: Success after binutils/gcc/linux/g [...] discards 24765eda344 110: onsuccess: #639: 1: Success after binutils/gcc/linux/g [...] discards f65a58a4a96 109: onsuccess: #638: 1: Success after binutils/gcc/linux/g [...] discards c28c0ebacc8 108: onsuccess: #637: 1: Success after binutils/gcc/linux/g [...] discards d109077280b 107: onsuccess: #636: 1: Success after binutils/gcc/linux/g [...] discards c51067d5815 106: onsuccess: #635: 1: Success after binutils/gcc/linux/g [...] discards 57ba8206629 105: onsuccess: #631: 1: Success after binutils/gcc/linux/g [...] discards 3ed511e55b7 104: onsuccess: #630: 1: Success after binutils/gcc/linux/g [...] discards 522b70735dd 103: onsuccess: #629: 1: Success after binutils/gcc/gdb: 68 [...] discards 14cf356cd6f 102: onsuccess: #628: 1: Success after binutils/gcc/glibc/g [...] discards 5b39eebad14 101: onsuccess: #627: 1: Success after binutils/gcc/linux/g [...] discards 7a03956ea99 100: onsuccess: #625: 1: Success after binutils/gcc/linux/g [...] discards fc132e5fec9 99: onsuccess: #624: 1: Success after binutils/gcc/linux/gl [...] discards bc1764e74ca 98: onsuccess: #623: 1: Success after binutils/gcc/linux/gd [...] discards 033b9fef068 97: onsuccess: #622: 1: Success after binutils/gcc/gdb: 8 commits discards b32e7c43e6b 96: onsuccess: #621: 1: Success after binutils/gcc/linux/gl [...] discards 93213d137d1 95: onsuccess: #619: 1: Success after binutils: 5 commits discards 3d0965a8871 94: onsuccess: #616: 1: Success after binutils: 2 commits discards 30485e780fe 93: onsuccess: #613: 1: Success after binutils: 19 commits discards f7e305cc6e7 92: onsuccess: #611: 1: Success after binutils/gcc/linux/gl [...] discards f1891f1b4f8 91: onsuccess: #610: 1: Success after binutils/gcc/linux/gl [...] discards 4e8a9ba22ad 90: onsuccess: #606: 1: Success after binutils/gcc/linux/gl [...] discards 5be8258e436 89: onsuccess: #605: 1: Success after binutils/gcc/linux/gd [...] discards 56678ce16f5 88: onsuccess: #604: 1: Success after binutils/gcc/linux/gd [...] discards 3bd0a10ca14 87: onsuccess: #603: 1: Success after binutils/gcc/linux/gl [...] discards 649331d9db6 86: onsuccess: #602: 1: Success after binutils/gcc/linux/gl [...] discards f8f7de1a6d1 85: onsuccess: #601: 1: Success after binutils/gcc/linux/gl [...] discards bed2aaf8be3 84: onsuccess: #600: 1: Success after binutils/gcc/linux/gl [...] discards b643bc2c62d 83: onsuccess: #599: 1: Success after binutils/gcc/linux/gl [...] discards fe78238ffae 82: onsuccess: #598: 1: Success after binutils/gcc/linux/gl [...] discards 9102292f58f 81: onsuccess: #597: 1: Success after binutils/gcc/linux/gd [...] discards 95043eace45 80: onsuccess: #596: 1: Success after binutils/gcc/linux/gl [...] discards ba1b336f096 79: onsuccess: #595: 1: Success after binutils/gcc/linux/gl [...] discards 4a8505ed4ab 78: onsuccess: #594: 1: Success after binutils/gcc/linux/gl [...] discards b9f6e42dd48 77: onsuccess: #593: 1: Success after binutils/gcc/linux/gl [...] discards e09b0fb472d 76: onsuccess: #592: 1: Success after linux: 63 commits discards d32c1114ed3 75: onsuccess: #591: 1: Success after gcc: 25 commits discards a3ae4f8946f 74: onsuccess: #590: 1: Success after binutils: 16 commits discards 978cc103cf3 73: onsuccess: #588: 1: Success after binutils/gcc/linux/gd [...] discards a46076ccc32 72: onsuccess: #587: 1: Success after binutils/gcc/linux/gd [...] discards 56ae8e84084 71: onsuccess: #586: 1: Success after binutils/gcc/linux/gd [...] discards 56b770996db 70: onsuccess: #585: 1: Success after binutils/gcc/linux/gl [...] discards 953f62e5948 69: onsuccess: #584: 1: Success after binutils/gcc/glibc/gd [...] discards f794963bd2a 68: onsuccess: #583: 1: Success after binutils/gcc/linux/gl [...] discards f4469ce39bd 67: onsuccess: #582: 1: Success after binutils/gcc/linux/gd [...] discards 3b77b613e89 66: onsuccess: #581: 1: Success after binutils/gcc/linux/gl [...] discards 7417f3b1de0 65: onsuccess: #580: 1: Success after binutils/gcc/linux/gd [...] discards 86bbdde7db6 64: onsuccess: #579: 1: Success after binutils/gcc/linux/gl [...] discards e18393e91ba 63: onsuccess: #577: 1: Success after binutils/gcc/linux/gl [...] discards ba9ca7a56a5 62: onsuccess: #576: 1: Success after binutils/gcc/linux/gd [...] discards bb0ddc7d985 61: onsuccess: #575: 1: Success after binutils/gcc/linux/gl [...] discards 0bbc5fad06b 60: onsuccess: #574: 1: Success after binutils/gcc/linux/gl [...] discards 42c634aa1a5 59: onsuccess: #573: 1: Success after binutils/gcc/linux/gl [...] discards 9b5923505e7 58: onsuccess: #572: 1: Success after binutils/gcc/linux/gl [...] discards 019249b7c55 57: onsuccess: #571: 1: Success after binutils/gcc/linux/gl [...] discards 33aae499f5f 56: onsuccess: #570: 1: Success after binutils/gcc/linux/gl [...] discards b1c3e3c1675 55: onsuccess: #569: 1: Success after binutils/gcc/linux/gl [...] discards ce775644268 54: onsuccess: #568: 1: Success after binutils/gcc/linux/gl [...] discards dc83376614a 53: onsuccess: #567: 1: Success after binutils/gcc/linux/gd [...] discards 2700f0d707d 52: onsuccess: #566: 1: Success after binutils/gcc/linux/gl [...] discards 1a4f96db6d3 51: onsuccess: #565: 1: Success after binutils/gcc/linux/gl [...] discards ff8bf40dd4e 50: onsuccess: #564: 1: Success after binutils/gcc/linux/gl [...] discards f2ea97975b1 49: onsuccess: #562: 1: Success after binutils: 9 commits discards 2c6ef7682e9 48: onsuccess: #559: 1: Success after binutils: 6 commits discards 12ba67fa5f0 47: onsuccess: #556: 1: Success after binutils: 12 commits discards afea37a5099 46: onsuccess: #554: 1: Success after binutils/gcc/linux/gd [...] discards 346091567f5 45: onsuccess: #553: 1: Success after binutils/gcc/linux/gd [...] discards 616de4e47d1 44: onsuccess: #552: 1: Success after binutils/gcc/linux/gl [...] discards cfe29dae29a 43: onsuccess: #550: 1: Success after binutils/gcc/linux/gl [...] discards 97eec47d9c8 42: onsuccess: #549: 1: Success after binutils/gcc/linux/gl [...] discards 3c0cb0e60d0 41: onsuccess: #548: 1: Success after binutils/gcc/glibc/gd [...] discards 57642415099 40: onsuccess: #547: 1: Success after binutils/gcc/linux/gd [...] discards e56693d1ac8 39: onsuccess: #546: 1: Success after binutils/gcc/glibc/gd [...] discards c941b896236 38: onsuccess: #545: 1: Success after binutils/gcc/linux/gl [...] discards 689d6c913a2 37: onsuccess: #544: 1: Success after binutils/gcc/glibc/gd [...] discards 1ca0f50ea6d 36: onsuccess: #543: 1: Success after binutils/gcc/linux/gl [...] discards fc7bedc0899 35: onsuccess: #542: 1: Success after binutils/gcc/linux/gl [...] discards 01f0ee7850a 34: onsuccess: #541: 1: Success after binutils/gcc/linux/gl [...] discards 8e91229b7c3 33: onsuccess: #540: 1: Success after binutils/gcc/linux/gl [...] discards c313d41aea9 32: onsuccess: #539: 1: Success after binutils/gcc/linux/gd [...] discards dbeebf28817 31: onsuccess: #538: 1: Success after binutils/gcc/linux/gl [...] discards 23105e32714 30: onsuccess: #537: 1: Success after binutils/gcc/linux/gl [...] discards 70cc1a46511 29: onsuccess: #536: 1: Success after binutils/gcc/glibc/gd [...] discards 9719ea2b8a4 28: onsuccess: #535: 1: Success after binutils/gcc/linux/gl [...] discards 5502da83dc5 27: onsuccess: #534: 1: Success after binutils/gcc/linux/gl [...] discards 7ee75d746b6 26: onsuccess: #533: 1: Success after binutils/gcc/linux/gd [...] discards 22f03520744 25: onsuccess: #532: 1: Success after binutils/gcc/linux/gd [...] discards 2348308f51e 24: onsuccess: 1: Success after binutils/gcc/linux/gdb: 216 [...] discards 6c028a7d634 23: onsuccess: 1: Success after binutils/gcc/linux/gdb: 129 [...] discards e2c79dee38a 22: onsuccess: 1: Success after binutils/gcc/linux/glibc/gd [...] discards 01315dc877a 21: onsuccess: 1: Successful build after binutils/gcc/linux [...] discards cacaf36b718 20: onsuccess: 1: Successful build after binutils/gcc/linux [...] discards 4917cbf9c58 19: onsuccess: 1: Successful build after binutils/gcc/linux [...] discards e3de6f36a56 18: onsuccess: 1: Successful build after binutils/gcc/linux [...] discards 378bf86c498 17: onsuccess: 1: Successful build after binutils/gcc/glibc [...] discards 2a5566e8137 16: onsuccess: 1: Successful build after binutils/gcc/linux [...] discards e710d1881c2 15: onsuccess: 1: Successful build after binutils/gcc/linux [...] discards 7e136f60087 14: onsuccess: 1: Successful build after binutils/gcc/linux [...] discards 4a68ed3e53b 13: onsuccess: 1: Successful build after binutils/gcc/linux [...] new eec24cabcdf 13: onsuccess: 1: Successful build after binutils/gcc/linux [...] new a7fb1f5a605 14: onsuccess: 1: Successful build after binutils/gcc/linux [...] new 37580b5c40e 15: onsuccess: 1: Successful build after binutils/gcc/linux [...] new 8a84de95fb9 16: onsuccess: 1: Successful build after binutils/gcc/linux [...] new 2daea3b540d 17: onsuccess: 1: Successful build after binutils/gcc/glibc [...] new 92b784d1d9b 18: onsuccess: 1: Successful build after binutils/gcc/linux [...] new fd106c7a27c 19: onsuccess: 1: Successful build after binutils/gcc/linux [...] new 77f991f0390 20: onsuccess: 1: Successful build after binutils/gcc/linux [...] new 93d639b286d 21: onsuccess: 1: Successful build after binutils/gcc/linux [...] new 85d36d94aff 22: onsuccess: 1: Success after binutils/gcc/linux/glibc/gd [...] new 50142837a2d 23: onsuccess: 1: Success after binutils/gcc/linux/gdb: 129 [...] new 9dd9fa1287e 24: onsuccess: 1: Success after binutils/gcc/linux/gdb: 216 [...] new f7a3a147789 25: onsuccess: #532: 1: Success after binutils/gcc/linux/gd [...] new 4c56f2e35e3 26: onsuccess: #533: 1: Success after binutils/gcc/linux/gd [...] new 688e572fec7 27: onsuccess: #534: 1: Success after binutils/gcc/linux/gl [...] new b97d9d0dc49 28: onsuccess: #535: 1: Success after binutils/gcc/linux/gl [...] new 9f8eaa538dd 29: onsuccess: #536: 1: Success after binutils/gcc/glibc/gd [...] new e2fde621ed0 30: onsuccess: #537: 1: Success after binutils/gcc/linux/gl [...] new 4d01ecb4cd6 31: onsuccess: #538: 1: Success after binutils/gcc/linux/gl [...] new 4471feab3bb 32: onsuccess: #539: 1: Success after binutils/gcc/linux/gd [...] new 19e9719f293 33: onsuccess: #540: 1: Success after binutils/gcc/linux/gl [...] new 13ac3dd7530 34: onsuccess: #541: 1: Success after binutils/gcc/linux/gl [...] new 14879c7e528 35: onsuccess: #542: 1: Success after binutils/gcc/linux/gl [...] new f5c89f1ebfa 36: onsuccess: #543: 1: Success after binutils/gcc/linux/gl [...] new 2141497cc20 37: onsuccess: #544: 1: Success after binutils/gcc/glibc/gd [...] new 1ea58947790 38: onsuccess: #545: 1: Success after binutils/gcc/linux/gl [...] new 1d04602db3c 39: onsuccess: #546: 1: Success after binutils/gcc/glibc/gd [...] new 151cbeb160e 40: onsuccess: #547: 1: Success after binutils/gcc/linux/gd [...] new 73e525ab6de 41: onsuccess: #548: 1: Success after binutils/gcc/glibc/gd [...] new f91d1600b54 42: onsuccess: #549: 1: Success after binutils/gcc/linux/gl [...] new d4863855383 43: onsuccess: #550: 1: Success after binutils/gcc/linux/gl [...] new c64bd32acf2 44: onsuccess: #552: 1: Success after binutils/gcc/linux/gl [...] new fcc135d3143 45: onsuccess: #553: 1: Success after binutils/gcc/linux/gd [...] new f6f19396a14 46: onsuccess: #554: 1: Success after binutils/gcc/linux/gd [...] new 78e2061eb64 47: onsuccess: #556: 1: Success after binutils: 12 commits new 03356fbf8ad 48: onsuccess: #559: 1: Success after binutils: 6 commits new 4d991d6d635 49: onsuccess: #562: 1: Success after binutils: 9 commits new 9033a557e5b 50: onsuccess: #564: 1: Success after binutils/gcc/linux/gl [...] new cd46aad4d7b 51: onsuccess: #565: 1: Success after binutils/gcc/linux/gl [...] new e0dcccb9277 52: onsuccess: #566: 1: Success after binutils/gcc/linux/gl [...] new c8365fea811 53: onsuccess: #567: 1: Success after binutils/gcc/linux/gd [...] new 9002ab4920a 54: onsuccess: #568: 1: Success after binutils/gcc/linux/gl [...] new 01a5a7452bd 55: onsuccess: #569: 1: Success after binutils/gcc/linux/gl [...] new a54724f5348 56: onsuccess: #570: 1: Success after binutils/gcc/linux/gl [...] new 4f6c977637e 57: onsuccess: #571: 1: Success after binutils/gcc/linux/gl [...] new b96bf7f88f3 58: onsuccess: #572: 1: Success after binutils/gcc/linux/gl [...] new a922ec5cdef 59: onsuccess: #573: 1: Success after binutils/gcc/linux/gl [...] new 08fe5bee3bb 60: onsuccess: #574: 1: Success after binutils/gcc/linux/gl [...] new bd2421c43c8 61: onsuccess: #575: 1: Success after binutils/gcc/linux/gl [...] new d02bad6dd56 62: onsuccess: #576: 1: Success after binutils/gcc/linux/gd [...] new 5fbe1bf19bb 63: onsuccess: #577: 1: Success after binutils/gcc/linux/gl [...] new a6b39208832 64: onsuccess: #579: 1: Success after binutils/gcc/linux/gl [...] new 1dca5740667 65: onsuccess: #580: 1: Success after binutils/gcc/linux/gd [...] new d70dbb1716a 66: onsuccess: #581: 1: Success after binutils/gcc/linux/gl [...] new f38a9906eb1 67: onsuccess: #582: 1: Success after binutils/gcc/linux/gd [...] new 6465331048c 68: onsuccess: #583: 1: Success after binutils/gcc/linux/gl [...] new af8c8172450 69: onsuccess: #584: 1: Success after binutils/gcc/glibc/gd [...] new 991d4b6e59f 70: onsuccess: #585: 1: Success after binutils/gcc/linux/gl [...] new 1a57e2cdcdf 71: onsuccess: #586: 1: Success after binutils/gcc/linux/gd [...] new 5f33174b893 72: onsuccess: #587: 1: Success after binutils/gcc/linux/gd [...] new b0064b3650f 73: onsuccess: #588: 1: Success after binutils/gcc/linux/gd [...] new 9b636912916 74: onsuccess: #590: 1: Success after binutils: 16 commits new 690b82e75ba 75: onsuccess: #591: 1: Success after gcc: 25 commits new 4d38a601358 76: onsuccess: #592: 1: Success after linux: 63 commits new 5600abe1e91 77: onsuccess: #593: 1: Success after binutils/gcc/linux/gl [...] new 8968987a329 78: onsuccess: #594: 1: Success after binutils/gcc/linux/gl [...] new 309ebf03094 79: onsuccess: #595: 1: Success after binutils/gcc/linux/gl [...] new 190023d5d4f 80: onsuccess: #596: 1: Success after binutils/gcc/linux/gl [...] new a193d721566 81: onsuccess: #597: 1: Success after binutils/gcc/linux/gd [...] new 8a196990b32 82: onsuccess: #598: 1: Success after binutils/gcc/linux/gl [...] new 63b9ad90684 83: onsuccess: #599: 1: Success after binutils/gcc/linux/gl [...] new 7d2e86e3df0 84: onsuccess: #600: 1: Success after binutils/gcc/linux/gl [...] new d978d26f388 85: onsuccess: #601: 1: Success after binutils/gcc/linux/gl [...] new 69ed3bcdc0a 86: onsuccess: #602: 1: Success after binutils/gcc/linux/gl [...] new 4ceaaa371e2 87: onsuccess: #603: 1: Success after binutils/gcc/linux/gl [...] new 04addbf8202 88: onsuccess: #604: 1: Success after binutils/gcc/linux/gd [...] new 5529a4b5839 89: onsuccess: #605: 1: Success after binutils/gcc/linux/gd [...] new 67a1b905a4c 90: onsuccess: #606: 1: Success after binutils/gcc/linux/gl [...] new 9a6e1c0ce7a 91: onsuccess: #610: 1: Success after binutils/gcc/linux/gl [...] new d24932fd238 92: onsuccess: #611: 1: Success after binutils/gcc/linux/gl [...] new fbc8775c85b 93: onsuccess: #613: 1: Success after binutils: 19 commits new 66843fe86e0 94: onsuccess: #616: 1: Success after binutils: 2 commits new e3d62e3ab80 95: onsuccess: #619: 1: Success after binutils: 5 commits new be1289552dd 96: onsuccess: #621: 1: Success after binutils/gcc/linux/gl [...] new b4310633d32 97: onsuccess: #622: 1: Success after binutils/gcc/gdb: 8 commits new 67be1399c39 98: onsuccess: #623: 1: Success after binutils/gcc/linux/gd [...] new cbe6faf68ad 99: onsuccess: #624: 1: Success after binutils/gcc/linux/gl [...] new 2b10c3bfbd2 100: onsuccess: #625: 1: Success after binutils/gcc/linux/g [...] new 6ea6fd70b4f 101: onsuccess: #627: 1: Success after binutils/gcc/linux/g [...] new d372aac77bc 102: onsuccess: #628: 1: Success after binutils/gcc/glibc/g [...] new cc68072c0e7 103: onsuccess: #629: 1: Success after binutils/gcc/gdb: 68 [...] new aab591ef62d 104: onsuccess: #630: 1: Success after binutils/gcc/linux/g [...] new df9b06984df 105: onsuccess: #631: 1: Success after binutils/gcc/linux/g [...] new 4bc2e6ed67d 106: onsuccess: #635: 1: Success after binutils/gcc/linux/g [...] new bbcc57bba86 107: onsuccess: #636: 1: Success after binutils/gcc/linux/g [...] new 90104569448 108: onsuccess: #637: 1: Success after binutils/gcc/linux/g [...] new 86dec16af50 109: onsuccess: #638: 1: Success after binutils/gcc/linux/g [...] new b77603bd55b 110: onsuccess: #639: 1: Success after binutils/gcc/linux/g [...] new ec595061b6a 111: onsuccess: #640: 1: Success after binutils/gcc/linux/g [...] new 9c9728ae0da 112: onsuccess: #641: 1: Success after binutils/gcc/linux/g [...] new 30e55ff723e 113: onsuccess: #642: 1: Success after binutils/gcc/linux/g [...] new 68f64b1f25f 114: onsuccess: #643: 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 (8f98712ee88) \ 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 1768 -> 1736 bytes 02-prepare_abe/console.log.xz | Bin 2744 -> 2752 bytes 03-build_abe-binutils/console.log.xz | Bin 39096 -> 39548 bytes 04-build_abe-gcc/console.log.xz | Bin 212144 -> 214172 bytes 05-clean_sysroot/console.log.xz | Bin 312 -> 312 bytes 06-build_abe-linux/console.log.xz | Bin 8596 -> 8276 bytes 07-build_abe-glibc/console.log.xz | Bin 244256 -> 244944 bytes 08-build_abe-gdb/console.log.xz | Bin 38976 -> 38796 bytes 09-build_abe-dejagnu/console.log.xz | Bin 3848 -> 3848 bytes 10-build_abe-check_binutils/console.log.xz | Bin 2160 -> 2136 bytes 11-check_regression/console.log.xz | Bin 5544 -> 5716 bytes 11-check_regression/results.compare | 8 +- 11-check_regression/results.compare2 | 6 +- 12-update_baseline/console.log | 32 +-- 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 63056 -> 63288 bytes sumfiles/binutils.sum | 62 +++--- sumfiles/gas.log.xz | Bin 81832 -> 81792 bytes sumfiles/gas.sum | 272 +++++++++++------------ sumfiles/ld.log.xz | Bin 121756 -> 121940 bytes sumfiles/ld.sum | 346 ++++++++++++++--------------- 29 files changed, 387 insertions(+), 387 deletions(-)