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 a86c0ce707c 126: onsuccess: #659: 1: Success after binutils/gcc/linux/g [...] discards c9ba6d98e77 125: onsuccess: #658: 1: Success after linux: 3224 commits discards e654167d121 124: onsuccess: #657: 1: Success after glibc: 2 commits discards 735c49480d9 123: onsuccess: #655: 1: Success after binutils: 22 commits discards 5d8218bebaa 122: onsuccess: #653: 1: Success after binutils/gcc/linux/g [...] discards a8a1e642c93 121: onsuccess: #652: 1: Success after binutils/gcc/linux/g [...] discards 9bcd28c15f9 120: onsuccess: #651: 1: Success after binutils/gcc/linux/g [...] discards 005bc219f7e 119: onsuccess: #650: 1: Success after binutils/gcc/linux/g [...] discards f504aaa89e7 118: onsuccess: #649: 1: Success after binutils/gcc/linux/g [...] discards 8a160e4093c 117: onsuccess: #648: 1: Success after binutils/gcc/linux/g [...] discards 4f50b0df44f 116: onsuccess: #647: 1: Success after linux: 3 commits discards 8aa7018a7c4 115: onsuccess: #645: 1: Success after binutils: 27 commits discards f17f4c7a566 114: onsuccess: #643: 1: Success after binutils/gcc/linux/g [...] discards dc170e29309 113: onsuccess: #642: 1: Success after binutils/gcc/linux/g [...] discards d7ee7c084cb 112: onsuccess: #641: 1: Success after binutils/gcc/linux/g [...] discards fec5989829a 111: onsuccess: #640: 1: Success after binutils/gcc/linux/g [...] discards 9f921bea1d7 110: onsuccess: #639: 1: Success after binutils/gcc/linux/g [...] discards 68aa1d06d4f 109: onsuccess: #638: 1: Success after binutils/gcc/linux/g [...] discards c172b701051 108: onsuccess: #637: 1: Success after binutils/gcc/linux/g [...] discards 7b182079b9f 107: onsuccess: #636: 1: Success after binutils/gcc/linux/g [...] discards 55c15755ed0 106: onsuccess: #635: 1: Success after binutils/gcc/linux/g [...] discards 41f7a677283 105: onsuccess: #631: 1: Success after binutils/gcc/linux/g [...] discards 01197d3af0e 104: onsuccess: #630: 1: Success after binutils/gcc/linux/g [...] discards efc21ebabf5 103: onsuccess: #629: 1: Success after binutils/gcc/gdb: 68 [...] discards 7703bd23c31 102: onsuccess: #628: 1: Success after binutils/gcc/glibc/g [...] discards 643aa3df589 101: onsuccess: #627: 1: Success after binutils/gcc/linux/g [...] discards 59ae0ca86ee 100: onsuccess: #625: 1: Success after binutils/gcc/linux/g [...] discards 6dcba475635 99: onsuccess: #624: 1: Success after binutils/gcc/linux/gl [...] discards 5204d265cc3 98: onsuccess: #623: 1: Success after binutils/gcc/linux/gd [...] discards ce05c855763 97: onsuccess: #622: 1: Success after binutils/gcc/gdb: 8 commits discards 5fd9d58c3a7 96: onsuccess: #621: 1: Success after binutils/gcc/linux/gl [...] discards 8bb35fe9c95 95: onsuccess: #619: 1: Success after binutils: 5 commits discards ac787467223 94: onsuccess: #616: 1: Success after binutils: 2 commits discards 3783bd55276 93: onsuccess: #613: 1: Success after binutils: 19 commits discards 862b5d49f95 92: onsuccess: #611: 1: Success after binutils/gcc/linux/gl [...] discards 95a0df956fe 91: onsuccess: #610: 1: Success after binutils/gcc/linux/gl [...] discards d6e0f292889 90: onsuccess: #606: 1: Success after binutils/gcc/linux/gl [...] discards f3322dd9b7e 89: onsuccess: #605: 1: Success after binutils/gcc/linux/gd [...] discards 5b52df5674b 88: onsuccess: #604: 1: Success after binutils/gcc/linux/gd [...] discards ec97abb0e9e 87: onsuccess: #603: 1: Success after binutils/gcc/linux/gl [...] discards afe3d5d4877 86: onsuccess: #602: 1: Success after binutils/gcc/linux/gl [...] discards 480ed92d635 85: onsuccess: #601: 1: Success after binutils/gcc/linux/gl [...] discards f68777c480e 84: onsuccess: #600: 1: Success after binutils/gcc/linux/gl [...] discards 92f2967e3f8 83: onsuccess: #599: 1: Success after binutils/gcc/linux/gl [...] discards 073d63a425f 82: onsuccess: #598: 1: Success after binutils/gcc/linux/gl [...] discards 69d1a0b361b 81: onsuccess: #597: 1: Success after binutils/gcc/linux/gd [...] discards 8aa44c901f5 80: onsuccess: #596: 1: Success after binutils/gcc/linux/gl [...] discards eb881ca3ffe 79: onsuccess: #595: 1: Success after binutils/gcc/linux/gl [...] discards 728653f2954 78: onsuccess: #594: 1: Success after binutils/gcc/linux/gl [...] discards 4ac5d14589b 77: onsuccess: #593: 1: Success after binutils/gcc/linux/gl [...] discards 02d9127ae13 76: onsuccess: #592: 1: Success after linux: 63 commits discards 18b6d783ebd 75: onsuccess: #591: 1: Success after gcc: 25 commits discards 27f01e229b9 74: onsuccess: #590: 1: Success after binutils: 16 commits discards cec57abf271 73: onsuccess: #588: 1: Success after binutils/gcc/linux/gd [...] discards ecc6a319140 72: onsuccess: #587: 1: Success after binutils/gcc/linux/gd [...] discards 1f4f59fadd7 71: onsuccess: #586: 1: Success after binutils/gcc/linux/gd [...] discards 1fdac068e0a 70: onsuccess: #585: 1: Success after binutils/gcc/linux/gl [...] discards 6a719b8ebab 69: onsuccess: #584: 1: Success after binutils/gcc/glibc/gd [...] discards af43e8e3deb 68: onsuccess: #583: 1: Success after binutils/gcc/linux/gl [...] discards ce988999be1 67: onsuccess: #582: 1: Success after binutils/gcc/linux/gd [...] discards 69b494da2d6 66: onsuccess: #581: 1: Success after binutils/gcc/linux/gl [...] discards 7b49a670a58 65: onsuccess: #580: 1: Success after binutils/gcc/linux/gd [...] discards 2fc96d156a8 64: onsuccess: #579: 1: Success after binutils/gcc/linux/gl [...] discards 2e23db9eecf 63: onsuccess: #577: 1: Success after binutils/gcc/linux/gl [...] discards 7737a4d889e 62: onsuccess: #576: 1: Success after binutils/gcc/linux/gd [...] discards 136a52fb96f 61: onsuccess: #575: 1: Success after binutils/gcc/linux/gl [...] discards 4f6b1083c40 60: onsuccess: #574: 1: Success after binutils/gcc/linux/gl [...] discards dfd92970a05 59: onsuccess: #573: 1: Success after binutils/gcc/linux/gl [...] discards a6b05c7db18 58: onsuccess: #572: 1: Success after binutils/gcc/linux/gl [...] discards 8fc7bdfb784 57: onsuccess: #571: 1: Success after binutils/gcc/linux/gl [...] discards 4142a1185a6 56: onsuccess: #570: 1: Success after binutils/gcc/linux/gl [...] discards 6d60c3bc9c9 55: onsuccess: #569: 1: Success after binutils/gcc/linux/gl [...] discards 6cbf03b6045 54: onsuccess: #568: 1: Success after binutils/gcc/linux/gl [...] discards 0d79c8e1ebe 53: onsuccess: #567: 1: Success after binutils/gcc/linux/gd [...] discards f5254b09664 52: onsuccess: #566: 1: Success after binutils/gcc/linux/gl [...] discards a4299177c7f 51: onsuccess: #565: 1: Success after binutils/gcc/linux/gl [...] discards 7e99ab23a75 50: onsuccess: #564: 1: Success after binutils/gcc/linux/gl [...] discards d0d58c4eda5 49: onsuccess: #562: 1: Success after binutils: 9 commits discards 433c8c6c999 48: onsuccess: #559: 1: Success after binutils: 6 commits discards 7fdeef5e251 47: onsuccess: #556: 1: Success after binutils: 12 commits discards c4ef22e08ce 46: onsuccess: #554: 1: Success after binutils/gcc/linux/gd [...] discards 39260953515 45: onsuccess: #553: 1: Success after binutils/gcc/linux/gd [...] discards 2469111dc9c 44: onsuccess: #552: 1: Success after binutils/gcc/linux/gl [...] discards 1033f993dae 43: onsuccess: #550: 1: Success after binutils/gcc/linux/gl [...] discards c5b01f68727 42: onsuccess: #549: 1: Success after binutils/gcc/linux/gl [...] discards 661239f538e 41: onsuccess: #548: 1: Success after binutils/gcc/glibc/gd [...] discards 549741036fc 40: onsuccess: #547: 1: Success after binutils/gcc/linux/gd [...] discards 51887d26b58 39: onsuccess: #546: 1: Success after binutils/gcc/glibc/gd [...] discards 8a5bed339ec 38: onsuccess: #545: 1: Success after binutils/gcc/linux/gl [...] discards bc86c5a3f11 37: onsuccess: #544: 1: Success after binutils/gcc/glibc/gd [...] discards 059baea8588 36: onsuccess: #543: 1: Success after binutils/gcc/linux/gl [...] discards f103e7d0c34 35: onsuccess: #542: 1: Success after binutils/gcc/linux/gl [...] discards 9f0f7e283ac 34: onsuccess: #541: 1: Success after binutils/gcc/linux/gl [...] discards 90e7ed207c6 33: onsuccess: #540: 1: Success after binutils/gcc/linux/gl [...] discards dd2eb3340af 32: onsuccess: #539: 1: Success after binutils/gcc/linux/gd [...] discards ca6fc62b474 31: onsuccess: #538: 1: Success after binutils/gcc/linux/gl [...] discards 87e3e1938ce 30: onsuccess: #537: 1: Success after binutils/gcc/linux/gl [...] discards fd2d9537614 29: onsuccess: #536: 1: Success after binutils/gcc/glibc/gd [...] discards 90a4441b903 28: onsuccess: #535: 1: Success after binutils/gcc/linux/gl [...] discards a99aa883e9a 27: onsuccess: #534: 1: Success after binutils/gcc/linux/gl [...] discards 8eb6865d86e 26: onsuccess: #533: 1: Success after binutils/gcc/linux/gd [...] new 201315af5a8 26: onsuccess: #533: 1: Success after binutils/gcc/linux/gd [...] new 6f9fc90ac59 27: onsuccess: #534: 1: Success after binutils/gcc/linux/gl [...] new ca5ebc34402 28: onsuccess: #535: 1: Success after binutils/gcc/linux/gl [...] new 2bd7554b046 29: onsuccess: #536: 1: Success after binutils/gcc/glibc/gd [...] new 468af33b31b 30: onsuccess: #537: 1: Success after binutils/gcc/linux/gl [...] new 64ef89d78c6 31: onsuccess: #538: 1: Success after binutils/gcc/linux/gl [...] new f1fe3bccbd0 32: onsuccess: #539: 1: Success after binutils/gcc/linux/gd [...] new 9c86bdbd1e7 33: onsuccess: #540: 1: Success after binutils/gcc/linux/gl [...] new a7144b816a6 34: onsuccess: #541: 1: Success after binutils/gcc/linux/gl [...] new 73ec37193e8 35: onsuccess: #542: 1: Success after binutils/gcc/linux/gl [...] new 0519794ac13 36: onsuccess: #543: 1: Success after binutils/gcc/linux/gl [...] new ea5736397cd 37: onsuccess: #544: 1: Success after binutils/gcc/glibc/gd [...] new 46ac1de77da 38: onsuccess: #545: 1: Success after binutils/gcc/linux/gl [...] new d9e1dd72c57 39: onsuccess: #546: 1: Success after binutils/gcc/glibc/gd [...] new e0908dc46ee 40: onsuccess: #547: 1: Success after binutils/gcc/linux/gd [...] new b3775b1dc85 41: onsuccess: #548: 1: Success after binutils/gcc/glibc/gd [...] new 79c34c0ca69 42: onsuccess: #549: 1: Success after binutils/gcc/linux/gl [...] new baf5aa4496d 43: onsuccess: #550: 1: Success after binutils/gcc/linux/gl [...] new 60311c91676 44: onsuccess: #552: 1: Success after binutils/gcc/linux/gl [...] new 853ed9cc5fd 45: onsuccess: #553: 1: Success after binutils/gcc/linux/gd [...] new aaa2351ccb1 46: onsuccess: #554: 1: Success after binutils/gcc/linux/gd [...] new 73b167e12b8 47: onsuccess: #556: 1: Success after binutils: 12 commits new 3362886f95d 48: onsuccess: #559: 1: Success after binutils: 6 commits new 33d49daf6a1 49: onsuccess: #562: 1: Success after binutils: 9 commits new 46fc307dd81 50: onsuccess: #564: 1: Success after binutils/gcc/linux/gl [...] new 32eba690aeb 51: onsuccess: #565: 1: Success after binutils/gcc/linux/gl [...] new 99c0378e7cf 52: onsuccess: #566: 1: Success after binutils/gcc/linux/gl [...] new a123ac2470d 53: onsuccess: #567: 1: Success after binutils/gcc/linux/gd [...] new e0ddb6bfb06 54: onsuccess: #568: 1: Success after binutils/gcc/linux/gl [...] new a472dead2ed 55: onsuccess: #569: 1: Success after binutils/gcc/linux/gl [...] new ac37499b7e4 56: onsuccess: #570: 1: Success after binutils/gcc/linux/gl [...] new c66a8430f9d 57: onsuccess: #571: 1: Success after binutils/gcc/linux/gl [...] new bf30cc57bb9 58: onsuccess: #572: 1: Success after binutils/gcc/linux/gl [...] new 80e7c2d30be 59: onsuccess: #573: 1: Success after binutils/gcc/linux/gl [...] new 3403a6c2fe8 60: onsuccess: #574: 1: Success after binutils/gcc/linux/gl [...] new 3a3e21dc6af 61: onsuccess: #575: 1: Success after binutils/gcc/linux/gl [...] new 5fea9b7e2ee 62: onsuccess: #576: 1: Success after binutils/gcc/linux/gd [...] new 64d0e3e4144 63: onsuccess: #577: 1: Success after binutils/gcc/linux/gl [...] new 92c1605557a 64: onsuccess: #579: 1: Success after binutils/gcc/linux/gl [...] new bde0d957ec7 65: onsuccess: #580: 1: Success after binutils/gcc/linux/gd [...] new 7a1973b47bb 66: onsuccess: #581: 1: Success after binutils/gcc/linux/gl [...] new 963770e57d3 67: onsuccess: #582: 1: Success after binutils/gcc/linux/gd [...] new e8f0d4eb08e 68: onsuccess: #583: 1: Success after binutils/gcc/linux/gl [...] new 843d48a6dca 69: onsuccess: #584: 1: Success after binutils/gcc/glibc/gd [...] new 80922de5368 70: onsuccess: #585: 1: Success after binutils/gcc/linux/gl [...] new b657afd3780 71: onsuccess: #586: 1: Success after binutils/gcc/linux/gd [...] new 53d9f00e0e8 72: onsuccess: #587: 1: Success after binutils/gcc/linux/gd [...] new 2730dbf6bc2 73: onsuccess: #588: 1: Success after binutils/gcc/linux/gd [...] new 1f9da13fda8 74: onsuccess: #590: 1: Success after binutils: 16 commits new 11bcd54ca30 75: onsuccess: #591: 1: Success after gcc: 25 commits new fad769eaf16 76: onsuccess: #592: 1: Success after linux: 63 commits new c55866a0ae1 77: onsuccess: #593: 1: Success after binutils/gcc/linux/gl [...] new ca6bf6cb5e3 78: onsuccess: #594: 1: Success after binutils/gcc/linux/gl [...] new 953109cf7d2 79: onsuccess: #595: 1: Success after binutils/gcc/linux/gl [...] new e7795503eec 80: onsuccess: #596: 1: Success after binutils/gcc/linux/gl [...] new 214a605ad57 81: onsuccess: #597: 1: Success after binutils/gcc/linux/gd [...] new 30c4d9dd6a5 82: onsuccess: #598: 1: Success after binutils/gcc/linux/gl [...] new 02b9b20aea8 83: onsuccess: #599: 1: Success after binutils/gcc/linux/gl [...] new ba19d856e00 84: onsuccess: #600: 1: Success after binutils/gcc/linux/gl [...] new 452075c2f96 85: onsuccess: #601: 1: Success after binutils/gcc/linux/gl [...] new 4e1fb93c063 86: onsuccess: #602: 1: Success after binutils/gcc/linux/gl [...] new f2854511236 87: onsuccess: #603: 1: Success after binutils/gcc/linux/gl [...] new fa335b56430 88: onsuccess: #604: 1: Success after binutils/gcc/linux/gd [...] new bbb04cc50ce 89: onsuccess: #605: 1: Success after binutils/gcc/linux/gd [...] new 1563d755372 90: onsuccess: #606: 1: Success after binutils/gcc/linux/gl [...] new b9598d064b9 91: onsuccess: #610: 1: Success after binutils/gcc/linux/gl [...] new 250b569b3ac 92: onsuccess: #611: 1: Success after binutils/gcc/linux/gl [...] new e22a71b7020 93: onsuccess: #613: 1: Success after binutils: 19 commits new 83f36ad3929 94: onsuccess: #616: 1: Success after binutils: 2 commits new 3943a5cc918 95: onsuccess: #619: 1: Success after binutils: 5 commits new 49f1794ad6a 96: onsuccess: #621: 1: Success after binutils/gcc/linux/gl [...] new c95cf7157d9 97: onsuccess: #622: 1: Success after binutils/gcc/gdb: 8 commits new 0f8ff8334a5 98: onsuccess: #623: 1: Success after binutils/gcc/linux/gd [...] new 8e10834dd8f 99: onsuccess: #624: 1: Success after binutils/gcc/linux/gl [...] new d65198a2cd8 100: onsuccess: #625: 1: Success after binutils/gcc/linux/g [...] new 1c9199870a5 101: onsuccess: #627: 1: Success after binutils/gcc/linux/g [...] new 0df5d8862ff 102: onsuccess: #628: 1: Success after binutils/gcc/glibc/g [...] new 7689a3e9d58 103: onsuccess: #629: 1: Success after binutils/gcc/gdb: 68 [...] new a5efbed07f0 104: onsuccess: #630: 1: Success after binutils/gcc/linux/g [...] new 5b1563da32b 105: onsuccess: #631: 1: Success after binutils/gcc/linux/g [...] new d963317831a 106: onsuccess: #635: 1: Success after binutils/gcc/linux/g [...] new dfc9438443a 107: onsuccess: #636: 1: Success after binutils/gcc/linux/g [...] new 7c638c4f0dc 108: onsuccess: #637: 1: Success after binutils/gcc/linux/g [...] new e0d55f41dab 109: onsuccess: #638: 1: Success after binutils/gcc/linux/g [...] new 82b97d69f26 110: onsuccess: #639: 1: Success after binutils/gcc/linux/g [...] new 0686484ed4b 111: onsuccess: #640: 1: Success after binutils/gcc/linux/g [...] new 174bfd9dc9e 112: onsuccess: #641: 1: Success after binutils/gcc/linux/g [...] new 1b49732051b 113: onsuccess: #642: 1: Success after binutils/gcc/linux/g [...] new 204508ab9aa 114: onsuccess: #643: 1: Success after binutils/gcc/linux/g [...] new abedcd7f0da 115: onsuccess: #645: 1: Success after binutils: 27 commits new 019d58d73aa 116: onsuccess: #647: 1: Success after linux: 3 commits new ddcfa3421c3 117: onsuccess: #648: 1: Success after binutils/gcc/linux/g [...] new 5aafd8572e8 118: onsuccess: #649: 1: Success after binutils/gcc/linux/g [...] new 615dc8adc7e 119: onsuccess: #650: 1: Success after binutils/gcc/linux/g [...] new 35b255d5cb2 120: onsuccess: #651: 1: Success after binutils/gcc/linux/g [...] new b24d3ef58d9 121: onsuccess: #652: 1: Success after binutils/gcc/linux/g [...] new d4c0baf795d 122: onsuccess: #653: 1: Success after binutils/gcc/linux/g [...] new 4ad7abdfe76 123: onsuccess: #655: 1: Success after binutils: 22 commits new 996b7f7e91c 124: onsuccess: #657: 1: Success after glibc: 2 commits new 351227966e2 125: onsuccess: #658: 1: Success after linux: 3224 commits new 8a3ad720d9f 126: onsuccess: #659: 1: Success after binutils/gcc/linux/g [...] new c67b1150470 127: onsuccess: #660: 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 (a86c0ce707c) \ 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 1720 -> 1740 bytes 02-prepare_abe/console.log.xz | Bin 2756 -> 2768 bytes 03-build_abe-binutils/console.log.xz | Bin 40192 -> 40248 bytes 04-build_abe-gcc/console.log.xz | Bin 215988 -> 216904 bytes 05-clean_sysroot/console.log.xz | Bin 312 -> 312 bytes 06-build_abe-linux/console.log.xz | Bin 10248 -> 9564 bytes 07-build_abe-glibc/console.log.xz | Bin 243612 -> 243444 bytes 08-build_abe-gdb/console.log.xz | Bin 39360 -> 39420 bytes 09-build_abe-dejagnu/console.log.xz | Bin 3836 -> 3896 bytes 10-build_abe-check_binutils/console.log.xz | Bin 2596 -> 2068 bytes 11-check_regression/console.log.xz | Bin 6192 -> 5876 bytes 11-check_regression/results.compare | 8 +- 11-check_regression/results.compare2 | 6 +- 12-update_baseline/console.log | 64 +++--- 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 63240 -> 63008 bytes sumfiles/binutils.sum | 62 +++--- sumfiles/gas.log.xz | Bin 83724 -> 83748 bytes sumfiles/gas.sum | 272 +++++++++++------------ sumfiles/ld.log.xz | Bin 121764 -> 121772 bytes sumfiles/ld.sum | 344 ++++++++++++++--------------- 29 files changed, 402 insertions(+), 402 deletions(-)