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 c67b1150470 127: onsuccess: #660: 1: Success after binutils/gcc/linux/g [...] discards 8a3ad720d9f 126: onsuccess: #659: 1: Success after binutils/gcc/linux/g [...] discards 351227966e2 125: onsuccess: #658: 1: Success after linux: 3224 commits discards 996b7f7e91c 124: onsuccess: #657: 1: Success after glibc: 2 commits discards 4ad7abdfe76 123: onsuccess: #655: 1: Success after binutils: 22 commits discards d4c0baf795d 122: onsuccess: #653: 1: Success after binutils/gcc/linux/g [...] discards b24d3ef58d9 121: onsuccess: #652: 1: Success after binutils/gcc/linux/g [...] discards 35b255d5cb2 120: onsuccess: #651: 1: Success after binutils/gcc/linux/g [...] discards 615dc8adc7e 119: onsuccess: #650: 1: Success after binutils/gcc/linux/g [...] discards 5aafd8572e8 118: onsuccess: #649: 1: Success after binutils/gcc/linux/g [...] discards ddcfa3421c3 117: onsuccess: #648: 1: Success after binutils/gcc/linux/g [...] discards 019d58d73aa 116: onsuccess: #647: 1: Success after linux: 3 commits discards abedcd7f0da 115: onsuccess: #645: 1: Success after binutils: 27 commits discards 204508ab9aa 114: onsuccess: #643: 1: Success after binutils/gcc/linux/g [...] discards 1b49732051b 113: onsuccess: #642: 1: Success after binutils/gcc/linux/g [...] discards 174bfd9dc9e 112: onsuccess: #641: 1: Success after binutils/gcc/linux/g [...] discards 0686484ed4b 111: onsuccess: #640: 1: Success after binutils/gcc/linux/g [...] discards 82b97d69f26 110: onsuccess: #639: 1: Success after binutils/gcc/linux/g [...] discards e0d55f41dab 109: onsuccess: #638: 1: Success after binutils/gcc/linux/g [...] discards 7c638c4f0dc 108: onsuccess: #637: 1: Success after binutils/gcc/linux/g [...] discards dfc9438443a 107: onsuccess: #636: 1: Success after binutils/gcc/linux/g [...] discards d963317831a 106: onsuccess: #635: 1: Success after binutils/gcc/linux/g [...] discards 5b1563da32b 105: onsuccess: #631: 1: Success after binutils/gcc/linux/g [...] discards a5efbed07f0 104: onsuccess: #630: 1: Success after binutils/gcc/linux/g [...] discards 7689a3e9d58 103: onsuccess: #629: 1: Success after binutils/gcc/gdb: 68 [...] discards 0df5d8862ff 102: onsuccess: #628: 1: Success after binutils/gcc/glibc/g [...] discards 1c9199870a5 101: onsuccess: #627: 1: Success after binutils/gcc/linux/g [...] discards d65198a2cd8 100: onsuccess: #625: 1: Success after binutils/gcc/linux/g [...] discards 8e10834dd8f 99: onsuccess: #624: 1: Success after binutils/gcc/linux/gl [...] discards 0f8ff8334a5 98: onsuccess: #623: 1: Success after binutils/gcc/linux/gd [...] discards c95cf7157d9 97: onsuccess: #622: 1: Success after binutils/gcc/gdb: 8 commits discards 49f1794ad6a 96: onsuccess: #621: 1: Success after binutils/gcc/linux/gl [...] discards 3943a5cc918 95: onsuccess: #619: 1: Success after binutils: 5 commits discards 83f36ad3929 94: onsuccess: #616: 1: Success after binutils: 2 commits discards e22a71b7020 93: onsuccess: #613: 1: Success after binutils: 19 commits discards 250b569b3ac 92: onsuccess: #611: 1: Success after binutils/gcc/linux/gl [...] discards b9598d064b9 91: onsuccess: #610: 1: Success after binutils/gcc/linux/gl [...] discards 1563d755372 90: onsuccess: #606: 1: Success after binutils/gcc/linux/gl [...] discards bbb04cc50ce 89: onsuccess: #605: 1: Success after binutils/gcc/linux/gd [...] discards fa335b56430 88: onsuccess: #604: 1: Success after binutils/gcc/linux/gd [...] discards f2854511236 87: onsuccess: #603: 1: Success after binutils/gcc/linux/gl [...] discards 4e1fb93c063 86: onsuccess: #602: 1: Success after binutils/gcc/linux/gl [...] discards 452075c2f96 85: onsuccess: #601: 1: Success after binutils/gcc/linux/gl [...] discards ba19d856e00 84: onsuccess: #600: 1: Success after binutils/gcc/linux/gl [...] discards 02b9b20aea8 83: onsuccess: #599: 1: Success after binutils/gcc/linux/gl [...] discards 30c4d9dd6a5 82: onsuccess: #598: 1: Success after binutils/gcc/linux/gl [...] discards 214a605ad57 81: onsuccess: #597: 1: Success after binutils/gcc/linux/gd [...] discards e7795503eec 80: onsuccess: #596: 1: Success after binutils/gcc/linux/gl [...] discards 953109cf7d2 79: onsuccess: #595: 1: Success after binutils/gcc/linux/gl [...] discards ca6bf6cb5e3 78: onsuccess: #594: 1: Success after binutils/gcc/linux/gl [...] discards c55866a0ae1 77: onsuccess: #593: 1: Success after binutils/gcc/linux/gl [...] discards fad769eaf16 76: onsuccess: #592: 1: Success after linux: 63 commits discards 11bcd54ca30 75: onsuccess: #591: 1: Success after gcc: 25 commits discards 1f9da13fda8 74: onsuccess: #590: 1: Success after binutils: 16 commits discards 2730dbf6bc2 73: onsuccess: #588: 1: Success after binutils/gcc/linux/gd [...] discards 53d9f00e0e8 72: onsuccess: #587: 1: Success after binutils/gcc/linux/gd [...] discards b657afd3780 71: onsuccess: #586: 1: Success after binutils/gcc/linux/gd [...] discards 80922de5368 70: onsuccess: #585: 1: Success after binutils/gcc/linux/gl [...] discards 843d48a6dca 69: onsuccess: #584: 1: Success after binutils/gcc/glibc/gd [...] discards e8f0d4eb08e 68: onsuccess: #583: 1: Success after binutils/gcc/linux/gl [...] discards 963770e57d3 67: onsuccess: #582: 1: Success after binutils/gcc/linux/gd [...] discards 7a1973b47bb 66: onsuccess: #581: 1: Success after binutils/gcc/linux/gl [...] discards bde0d957ec7 65: onsuccess: #580: 1: Success after binutils/gcc/linux/gd [...] discards 92c1605557a 64: onsuccess: #579: 1: Success after binutils/gcc/linux/gl [...] discards 64d0e3e4144 63: onsuccess: #577: 1: Success after binutils/gcc/linux/gl [...] discards 5fea9b7e2ee 62: onsuccess: #576: 1: Success after binutils/gcc/linux/gd [...] discards 3a3e21dc6af 61: onsuccess: #575: 1: Success after binutils/gcc/linux/gl [...] discards 3403a6c2fe8 60: onsuccess: #574: 1: Success after binutils/gcc/linux/gl [...] discards 80e7c2d30be 59: onsuccess: #573: 1: Success after binutils/gcc/linux/gl [...] discards bf30cc57bb9 58: onsuccess: #572: 1: Success after binutils/gcc/linux/gl [...] discards c66a8430f9d 57: onsuccess: #571: 1: Success after binutils/gcc/linux/gl [...] discards ac37499b7e4 56: onsuccess: #570: 1: Success after binutils/gcc/linux/gl [...] discards a472dead2ed 55: onsuccess: #569: 1: Success after binutils/gcc/linux/gl [...] discards e0ddb6bfb06 54: onsuccess: #568: 1: Success after binutils/gcc/linux/gl [...] discards a123ac2470d 53: onsuccess: #567: 1: Success after binutils/gcc/linux/gd [...] discards 99c0378e7cf 52: onsuccess: #566: 1: Success after binutils/gcc/linux/gl [...] discards 32eba690aeb 51: onsuccess: #565: 1: Success after binutils/gcc/linux/gl [...] discards 46fc307dd81 50: onsuccess: #564: 1: Success after binutils/gcc/linux/gl [...] discards 33d49daf6a1 49: onsuccess: #562: 1: Success after binutils: 9 commits discards 3362886f95d 48: onsuccess: #559: 1: Success after binutils: 6 commits discards 73b167e12b8 47: onsuccess: #556: 1: Success after binutils: 12 commits discards aaa2351ccb1 46: onsuccess: #554: 1: Success after binutils/gcc/linux/gd [...] discards 853ed9cc5fd 45: onsuccess: #553: 1: Success after binutils/gcc/linux/gd [...] discards 60311c91676 44: onsuccess: #552: 1: Success after binutils/gcc/linux/gl [...] discards baf5aa4496d 43: onsuccess: #550: 1: Success after binutils/gcc/linux/gl [...] discards 79c34c0ca69 42: onsuccess: #549: 1: Success after binutils/gcc/linux/gl [...] discards b3775b1dc85 41: onsuccess: #548: 1: Success after binutils/gcc/glibc/gd [...] discards e0908dc46ee 40: onsuccess: #547: 1: Success after binutils/gcc/linux/gd [...] discards d9e1dd72c57 39: onsuccess: #546: 1: Success after binutils/gcc/glibc/gd [...] discards 46ac1de77da 38: onsuccess: #545: 1: Success after binutils/gcc/linux/gl [...] discards ea5736397cd 37: onsuccess: #544: 1: Success after binutils/gcc/glibc/gd [...] discards 0519794ac13 36: onsuccess: #543: 1: Success after binutils/gcc/linux/gl [...] discards 73ec37193e8 35: onsuccess: #542: 1: Success after binutils/gcc/linux/gl [...] discards a7144b816a6 34: onsuccess: #541: 1: Success after binutils/gcc/linux/gl [...] discards 9c86bdbd1e7 33: onsuccess: #540: 1: Success after binutils/gcc/linux/gl [...] discards f1fe3bccbd0 32: onsuccess: #539: 1: Success after binutils/gcc/linux/gd [...] discards 64ef89d78c6 31: onsuccess: #538: 1: Success after binutils/gcc/linux/gl [...] discards 468af33b31b 30: onsuccess: #537: 1: Success after binutils/gcc/linux/gl [...] discards 2bd7554b046 29: onsuccess: #536: 1: Success after binutils/gcc/glibc/gd [...] discards ca5ebc34402 28: onsuccess: #535: 1: Success after binutils/gcc/linux/gl [...] discards 6f9fc90ac59 27: onsuccess: #534: 1: Success after binutils/gcc/linux/gl [...] new 3b928772b73 27: onsuccess: #534: 1: Success after binutils/gcc/linux/gl [...] new 7205ecd3dca 28: onsuccess: #535: 1: Success after binutils/gcc/linux/gl [...] new 76a41a08c34 29: onsuccess: #536: 1: Success after binutils/gcc/glibc/gd [...] new 57711f95b20 30: onsuccess: #537: 1: Success after binutils/gcc/linux/gl [...] new 838ac1bfc85 31: onsuccess: #538: 1: Success after binutils/gcc/linux/gl [...] new c86c96ef481 32: onsuccess: #539: 1: Success after binutils/gcc/linux/gd [...] new 6cead925b53 33: onsuccess: #540: 1: Success after binutils/gcc/linux/gl [...] new 439cf73d0e1 34: onsuccess: #541: 1: Success after binutils/gcc/linux/gl [...] new f59fda3e808 35: onsuccess: #542: 1: Success after binutils/gcc/linux/gl [...] new e5f09b32538 36: onsuccess: #543: 1: Success after binutils/gcc/linux/gl [...] new 36782a686c2 37: onsuccess: #544: 1: Success after binutils/gcc/glibc/gd [...] new 743432f434b 38: onsuccess: #545: 1: Success after binutils/gcc/linux/gl [...] new ab9ede92130 39: onsuccess: #546: 1: Success after binutils/gcc/glibc/gd [...] new 714af9ba3b6 40: onsuccess: #547: 1: Success after binutils/gcc/linux/gd [...] new 445ce749a0a 41: onsuccess: #548: 1: Success after binutils/gcc/glibc/gd [...] new 4474675a156 42: onsuccess: #549: 1: Success after binutils/gcc/linux/gl [...] new 33818566a6d 43: onsuccess: #550: 1: Success after binutils/gcc/linux/gl [...] new 4ab9984b90c 44: onsuccess: #552: 1: Success after binutils/gcc/linux/gl [...] new 95b63acc9ca 45: onsuccess: #553: 1: Success after binutils/gcc/linux/gd [...] new 8ed342c0707 46: onsuccess: #554: 1: Success after binutils/gcc/linux/gd [...] new 80cc5a89b70 47: onsuccess: #556: 1: Success after binutils: 12 commits new 0949683d9b1 48: onsuccess: #559: 1: Success after binutils: 6 commits new 148a018b263 49: onsuccess: #562: 1: Success after binutils: 9 commits new 375c19daae4 50: onsuccess: #564: 1: Success after binutils/gcc/linux/gl [...] new d6d3d2d260d 51: onsuccess: #565: 1: Success after binutils/gcc/linux/gl [...] new c90bd4fc03e 52: onsuccess: #566: 1: Success after binutils/gcc/linux/gl [...] new 664f8c8b383 53: onsuccess: #567: 1: Success after binutils/gcc/linux/gd [...] new b4f0d4a6a56 54: onsuccess: #568: 1: Success after binutils/gcc/linux/gl [...] new 154c1b6333d 55: onsuccess: #569: 1: Success after binutils/gcc/linux/gl [...] new bc48fd7b9a2 56: onsuccess: #570: 1: Success after binutils/gcc/linux/gl [...] new 3e9cc160710 57: onsuccess: #571: 1: Success after binutils/gcc/linux/gl [...] new 26b1bdca79c 58: onsuccess: #572: 1: Success after binutils/gcc/linux/gl [...] new e10779461e9 59: onsuccess: #573: 1: Success after binutils/gcc/linux/gl [...] new f7704efe86d 60: onsuccess: #574: 1: Success after binutils/gcc/linux/gl [...] new da789fc1669 61: onsuccess: #575: 1: Success after binutils/gcc/linux/gl [...] new 26eca6349d2 62: onsuccess: #576: 1: Success after binutils/gcc/linux/gd [...] new dba9b0d0f79 63: onsuccess: #577: 1: Success after binutils/gcc/linux/gl [...] new a334ac89185 64: onsuccess: #579: 1: Success after binutils/gcc/linux/gl [...] new fe1400f967a 65: onsuccess: #580: 1: Success after binutils/gcc/linux/gd [...] new 3eaa7df5029 66: onsuccess: #581: 1: Success after binutils/gcc/linux/gl [...] new 8369e1e7af9 67: onsuccess: #582: 1: Success after binutils/gcc/linux/gd [...] new 867f12fc213 68: onsuccess: #583: 1: Success after binutils/gcc/linux/gl [...] new 7651b3b05d2 69: onsuccess: #584: 1: Success after binutils/gcc/glibc/gd [...] new 92e38ae037d 70: onsuccess: #585: 1: Success after binutils/gcc/linux/gl [...] new df36f01c858 71: onsuccess: #586: 1: Success after binutils/gcc/linux/gd [...] new c5b5f591371 72: onsuccess: #587: 1: Success after binutils/gcc/linux/gd [...] new 9c3b2d34fd5 73: onsuccess: #588: 1: Success after binutils/gcc/linux/gd [...] new 2f3a80af5ee 74: onsuccess: #590: 1: Success after binutils: 16 commits new 9e3f93ffe43 75: onsuccess: #591: 1: Success after gcc: 25 commits new ffcce32d4ef 76: onsuccess: #592: 1: Success after linux: 63 commits new 8cf9a09b682 77: onsuccess: #593: 1: Success after binutils/gcc/linux/gl [...] new 42e03cd9534 78: onsuccess: #594: 1: Success after binutils/gcc/linux/gl [...] new 92143c1944e 79: onsuccess: #595: 1: Success after binutils/gcc/linux/gl [...] new 1e591f58713 80: onsuccess: #596: 1: Success after binutils/gcc/linux/gl [...] new 98434079438 81: onsuccess: #597: 1: Success after binutils/gcc/linux/gd [...] new ee5c80e473b 82: onsuccess: #598: 1: Success after binutils/gcc/linux/gl [...] new 5c2d445925e 83: onsuccess: #599: 1: Success after binutils/gcc/linux/gl [...] new bd3ba3728da 84: onsuccess: #600: 1: Success after binutils/gcc/linux/gl [...] new 1f9ce9baebe 85: onsuccess: #601: 1: Success after binutils/gcc/linux/gl [...] new 0a316359595 86: onsuccess: #602: 1: Success after binutils/gcc/linux/gl [...] new 9ff4fdae7ee 87: onsuccess: #603: 1: Success after binutils/gcc/linux/gl [...] new 18a5f688b77 88: onsuccess: #604: 1: Success after binutils/gcc/linux/gd [...] new 832620739bc 89: onsuccess: #605: 1: Success after binutils/gcc/linux/gd [...] new e8e4d062209 90: onsuccess: #606: 1: Success after binutils/gcc/linux/gl [...] new cb0d25a038b 91: onsuccess: #610: 1: Success after binutils/gcc/linux/gl [...] new bf12d2fad1b 92: onsuccess: #611: 1: Success after binutils/gcc/linux/gl [...] new 612a2bc5ee9 93: onsuccess: #613: 1: Success after binutils: 19 commits new a07be42185b 94: onsuccess: #616: 1: Success after binutils: 2 commits new 485707054d9 95: onsuccess: #619: 1: Success after binutils: 5 commits new 4349d9f4688 96: onsuccess: #621: 1: Success after binutils/gcc/linux/gl [...] new 1e8f2eae7c1 97: onsuccess: #622: 1: Success after binutils/gcc/gdb: 8 commits new db5519d83df 98: onsuccess: #623: 1: Success after binutils/gcc/linux/gd [...] new 0ea70a7dab1 99: onsuccess: #624: 1: Success after binutils/gcc/linux/gl [...] new dc22c40e629 100: onsuccess: #625: 1: Success after binutils/gcc/linux/g [...] new 1f77a59c646 101: onsuccess: #627: 1: Success after binutils/gcc/linux/g [...] new b870974e029 102: onsuccess: #628: 1: Success after binutils/gcc/glibc/g [...] new 6165fac1e63 103: onsuccess: #629: 1: Success after binutils/gcc/gdb: 68 [...] new 3e1db567f58 104: onsuccess: #630: 1: Success after binutils/gcc/linux/g [...] new 7f81f884c1e 105: onsuccess: #631: 1: Success after binutils/gcc/linux/g [...] new b851a109a69 106: onsuccess: #635: 1: Success after binutils/gcc/linux/g [...] new 14a01c4b22f 107: onsuccess: #636: 1: Success after binutils/gcc/linux/g [...] new 9b0876512ec 108: onsuccess: #637: 1: Success after binutils/gcc/linux/g [...] new 4147d4938cb 109: onsuccess: #638: 1: Success after binutils/gcc/linux/g [...] new 0c4d9d0b9b8 110: onsuccess: #639: 1: Success after binutils/gcc/linux/g [...] new ed84fbe53c5 111: onsuccess: #640: 1: Success after binutils/gcc/linux/g [...] new 2387d4da28b 112: onsuccess: #641: 1: Success after binutils/gcc/linux/g [...] new b194f5ddb53 113: onsuccess: #642: 1: Success after binutils/gcc/linux/g [...] new 9059b3b9172 114: onsuccess: #643: 1: Success after binutils/gcc/linux/g [...] new 801132b1e3e 115: onsuccess: #645: 1: Success after binutils: 27 commits new 463dea14e17 116: onsuccess: #647: 1: Success after linux: 3 commits new 15a164d5785 117: onsuccess: #648: 1: Success after binutils/gcc/linux/g [...] new 55fbc7d720c 118: onsuccess: #649: 1: Success after binutils/gcc/linux/g [...] new 48b0eb3adb2 119: onsuccess: #650: 1: Success after binutils/gcc/linux/g [...] new 78c3b7f7a0f 120: onsuccess: #651: 1: Success after binutils/gcc/linux/g [...] new afb84407bd4 121: onsuccess: #652: 1: Success after binutils/gcc/linux/g [...] new e22a7dcd29d 122: onsuccess: #653: 1: Success after binutils/gcc/linux/g [...] new 905ee3414d9 123: onsuccess: #655: 1: Success after binutils: 22 commits new 7b5b1601be1 124: onsuccess: #657: 1: Success after glibc: 2 commits new 55a39b9f2a1 125: onsuccess: #658: 1: Success after linux: 3224 commits new 2f9dc38fbdc 126: onsuccess: #659: 1: Success after binutils/gcc/linux/g [...] new 7b7feddcba9 127: onsuccess: #660: 1: Success after binutils/gcc/linux/g [...] new e26de80a863 128: onsuccess: #661: 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 (c67b1150470) \ 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 1740 -> 1768 bytes 02-prepare_abe/console.log.xz | Bin 2768 -> 2780 bytes 03-build_abe-binutils/console.log.xz | Bin 40248 -> 40360 bytes 04-build_abe-gcc/console.log.xz | Bin 216904 -> 215972 bytes 05-clean_sysroot/console.log.xz | Bin 312 -> 312 bytes 06-build_abe-linux/console.log.xz | Bin 9564 -> 8824 bytes 07-build_abe-glibc/console.log.xz | Bin 243444 -> 243968 bytes 08-build_abe-gdb/console.log.xz | Bin 39420 -> 40464 bytes 09-build_abe-dejagnu/console.log.xz | Bin 3896 -> 3912 bytes 10-build_abe-check_binutils/console.log.xz | Bin 2068 -> 2484 bytes 11-check_regression/console.log.xz | Bin 5876 -> 6436 bytes 11-check_regression/results.compare | 8 +- 11-check_regression/results.compare2 | 20 +- 12-update_baseline/console.log | 40 ++-- 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 63008 -> 63136 bytes sumfiles/binutils.sum | 62 +++--- sumfiles/gas.log.xz | Bin 83748 -> 83804 bytes sumfiles/gas.sum | 275 +++++++++++------------ sumfiles/ld.log.xz | Bin 121772 -> 121740 bytes sumfiles/ld.sum | 344 ++++++++++++++--------------- 30 files changed, 406 insertions(+), 397 deletions(-)