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-arm in repository toolchain/ci/base-artifacts.

discards 7e2d96c92f 150: onsuccess: #577: 1: Success after binutils/gcc/linux/gd [...] discards d42fbee223 149: onsuccess: #576: 1: Success after binutils/gcc/linux/gd [...] discards c94cfcfd07 148: onsuccess: #575: 1: Success after binutils/gcc/linux/gd [...] discards 9f3db1d35a 147: onsuccess: #574: 1: Success after binutils/gcc/linux/gl [...] discards be62a855a9 146: onsuccess: #573: 1: Success after binutils/gcc/gdb: 11 commits discards 23417dd913 145: onsuccess: #572: 1: Success after binutils/gcc/gdb: 27 commits discards ff04d48667 144: onsuccess: #571: 1: Success after binutils/gcc/gdb: 28 commits discards 8f5016b554 143: onsuccess: #570: 1: Success after binutils/gcc/linux/gd [...] discards 465a35b24e 142: onsuccess: #569: 1: Success after binutils/gcc/gdb: 46 commits discards 91001093b3 141: onsuccess: #568: 1: Success after binutils/gcc/linux/gd [...] discards 1d69a1c235 140: onsuccess: #567: 1: Success after binutils/gcc/linux/gl [...] discards f4903d65b2 139: onsuccess: #566: 1: Success after binutils/gcc/linux/gl [...] discards b84f440724 138: onsuccess: #565: 1: Success after binutils/gcc/linux/gl [...] discards 89b77677f0 137: onsuccess: #564: 1: Success after binutils/gcc/linux/gl [...] discards f05cca9b2f 136: onsuccess: #563: 1: Success after binutils/gcc/glibc/gd [...] discards 7404eb9ae8 135: onsuccess: #562: 1: Success after binutils/gcc/linux/gd [...] discards 4207133f4d 134: onsuccess: #561: 1: Success after binutils/gcc/linux/gd [...] discards c6acea4e5f 133: onsuccess: #560: 1: Success after binutils/gcc/linux/gl [...] discards 2ef66fed89 132: onsuccess: #559: 1: Success after binutils/gcc/linux/gd [...] discards 7329eb23a2 131: onsuccess: #558: 1: Success after binutils/gcc/linux/gl [...] discards 56fde29991 130: onsuccess: #557: 1: Success after binutils/gcc/linux/gl [...] discards e43ea109ac 129: onsuccess: #556: 1: Success after binutils/gcc/linux/gd [...] discards 01900a0641 128: onsuccess: #555: 1: Success after binutils/gcc/linux/gd [...] discards 31d9973c51 127: onsuccess: #554: 1: Success after binutils/gcc/linux/gl [...] discards a8defd5851 126: onsuccess: #553: 1: Success after binutils/gcc/linux/gl [...] discards 80ca52244b 125: onsuccess: #552: 1: Success after binutils/gcc/linux/gl [...] discards 996fb38d74 124: onsuccess: #551: 1: Success after binutils/gcc/linux/gl [...] discards 2b6a4b64ca 123: onsuccess: #550: 1: Success after binutils/gcc/linux/gd [...] discards 37679decce 122: onsuccess: #549: 1: Success after binutils/gcc/linux/gd [...] discards ef6b6be60f 121: onsuccess: #548: 1: Success after binutils/gcc/linux/gd [...] discards d9038c0256 120: onsuccess: #547: 1: Success after binutils/gcc/linux/gl [...] discards 7184062ea4 119: onsuccess: #546: 1: Success after binutils/gcc/linux/gd [...] discards 11b203ea8e 118: onsuccess: #545: 1: Success after binutils/gcc/linux/gd [...] discards 79b7818ec9 117: onsuccess: #544: 1: Success after binutils/gcc/linux/gl [...] discards 4d2f2ada0b 116: onsuccess: #543: 1: Success after binutils/gcc/linux/gl [...] discards 257dc1bf2a 115: onsuccess: #542: 1: Success after binutils/gcc/linux/gl [...] discards 48c297d29e 114: onsuccess: #541: 1: Success after binutils/gcc/linux/gd [...] discards ef281b10a4 113: onsuccess: #539: 1: Success after binutils/gcc/linux/gd [...] discards aa487e7ef4 112: onsuccess: #538: 1: Success after binutils/gcc/linux/gd [...] discards 015ef3e74d 111: onsuccess: #537: 1: Success after binutils/gcc/gdb: 69 commits discards 3ba4b7e1a4 110: onsuccess: #536: 1: Success after binutils/gcc/glibc/gd [...] discards 55a94c8e39 109: onsuccess: #535: 1: Success after binutils/gcc/linux/gd [...] discards 9765f51fd5 108: onsuccess: #534: 1: Success after binutils/gcc/linux/gd [...] discards 8c9d2cbb09 107: onsuccess: #533: 1: Success after binutils/gcc/linux/gd [...] discards 902211bdb5 106: onsuccess: #532: 1: Success after binutils/gcc/linux/gl [...] discards 157a7de388 105: onsuccess: #531: 1: Success after binutils/gcc/linux/gd [...] discards 79bb132488 104: onsuccess: #530: 1: Success after gcc: 7 commits discards 3888aa789e 103: onsuccess: #529: 1: Success after binutils/gcc/linux/gl [...] discards 21d88d2ace 102: onsuccess: #527: 1: Success after binutils: 5 commits discards d02a974f46 101: onsuccess: #524: 1: Success after binutils: 2 commits discards 6afaf8ff6e 100: onsuccess: #521: 1: Success after binutils: 10 commits discards eb4a0e3428 99: onsuccess: #519: 1: Success after binutils/gcc/linux/gli [...] discards 8f96a3551e 98: onsuccess: #518: 1: Success after binutils/gcc/linux/gli [...] discards e0a0ac5ed1 97: onsuccess: #517: 1: Success after binutils/gcc/linux/gli [...] discards 72bd2775e4 96: onsuccess: #516: 1: Success after binutils/gcc/linux/gli [...] discards d8d6925f39 95: onsuccess: #515: 1: Success after binutils/gcc/linux/gdb [...] discards d54a344cda 94: onsuccess: #514: 1: Success after binutils/gcc/linux/gdb [...] discards 387e562bf6 93: onsuccess: #513: 1: Success after binutils/gcc/linux/gli [...] discards d90a4812a8 92: onsuccess: #512: 1: Success after binutils/gcc/linux/gli [...] discards 9e2163bff4 91: onsuccess: #511: 1: Success after linux: 27 commits discards 000ea56693 90: onsuccess: #510: 1: Success after glibc: 5 commits discards 9b2c1bd6d2 89: onsuccess: #508: 1: Success after binutils: 12 commits discards c07a2b9740 88: onsuccess: #506: 1: Success after linux: 34 commits discards 24aaa2f2e7 87: onsuccess: #505: 1: Success after glibc: 7 commits discards c4ef0ad55d 86: onsuccess: #503: 1: Success after binutils: 12 commits discards 55cd3e9a92 85: onsuccess: #501: 1: Success after binutils/gcc/linux/gli [...] discards 18379529f2 84: onsuccess: #500: 1: Success after binutils/gcc/linux/gli [...] discards fc787a9d9a 83: onsuccess: #499: 1: Success after binutils/gcc/linux/gdb [...] discards 1478c3fc0f 82: onsuccess: #498: 1: Success after binutils/gcc/linux/gli [...] discards 785aea605c 81: onsuccess: #497: 1: Success after binutils/gcc/linux/gli [...] discards 5d232ff22a 80: onsuccess: #496: 1: Success after binutils/gcc/linux/gli [...] discards ac03f4d9d1 79: onsuccess: #495: 1: Success after binutils/gcc/linux/gli [...] discards 042b7bf973 78: onsuccess: #494: 1: Success after binutils/gcc/linux/gli [...] discards 5f4469769d 77: onsuccess: #493: 1: Success after binutils/gcc/linux/gdb [...] discards a1d0d41e90 76: onsuccess: #492: 1: Success after binutils/gcc/linux/gdb [...] discards 283c9dc3d8 75: onsuccess: #491: 1: Success after binutils/gcc/linux/gdb [...] discards 5cc1676af9 74: onsuccess: #490: 1: Success after binutils/gcc/linux/gli [...] discards af1ef45c0e 73: onsuccess: #489: 1: Success after binutils/gcc/glibc/gdb [...] discards f72dd15324 72: onsuccess: #488: 1: Success after binutils/gcc/linux/gli [...] discards dd309f6277 71: onsuccess: #487: 1: Success after binutils/gcc/linux/gdb [...] discards 5aaa293034 70: onsuccess: #486: 1: Success after binutils/gcc/linux/gli [...] discards a6d68aea51 69: onsuccess: #485: 1: Success after binutils/gcc/linux/gdb [...] discards 3a3b054733 68: onsuccess: #484: 1: Success after binutils/gcc/linux/gli [...] discards 276feb22bf 67: onsuccess: #483: 1: Success after binutils/gcc/linux/gli [...] discards 4dfd1b7cae 66: onsuccess: #482: 1: Success after binutils/gcc/linux/gli [...] discards 55ab9a7379 65: onsuccess: #481: 1: Success after binutils/gcc/linux/gdb [...] discards 03055cd1a6 64: onsuccess: #480: 1: Success after binutils/gcc/linux/gli [...] discards db71640bbe 63: onsuccess: #479: 1: Success after binutils/gcc/linux/gli [...] discards 9b65c16230 62: onsuccess: #478: 1: Success after binutils/gcc/linux/gli [...] discards 06cd6bd0da 61: onsuccess: #477: 1: Success after binutils/gcc/linux/gli [...] discards 9d06588e07 60: onsuccess: #476: 1: Success after binutils/gcc/linux/gli [...] discards ef6746d002 59: onsuccess: #475: 1: Success after binutils/gcc/linux/gli [...] discards ccd72917d6 58: onsuccess: #474: 1: Success after binutils/gcc/linux/gli [...] discards 76d40a4894 57: onsuccess: #473: 1: Success after binutils/gcc/linux/gli [...] discards 32aa934778 56: onsuccess: #472: 1: Success after binutils/gcc/linux/gdb [...] discards a31e99a39e 55: onsuccess: #471: 1: Success after binutils/gcc/linux/gli [...] discards 2d54c8d7a5 54: onsuccess: #470: 1: Success after binutils/gcc/linux/gli [...] discards 03438754ed 53: onsuccess: #469: 1: Success after binutils/gcc/linux/gli [...] discards 946507a7fe 52: onsuccess: #467: 1: Success after binutils: 9 commits discards 4b980d1ff3 51: onsuccess: #464: 1: Success after binutils: 6 commits discards 2f8a5b98a6 50: onsuccess: #461: 1: Success after binutils: 12 commits new afa18542bd 50: onsuccess: #461: 1: Success after binutils: 12 commits new a97c8a3c10 51: onsuccess: #464: 1: Success after binutils: 6 commits new a476de794b 52: onsuccess: #467: 1: Success after binutils: 9 commits new 88ab033f24 53: onsuccess: #469: 1: Success after binutils/gcc/linux/gli [...] new 33dfc98f84 54: onsuccess: #470: 1: Success after binutils/gcc/linux/gli [...] new 619f9df9d7 55: onsuccess: #471: 1: Success after binutils/gcc/linux/gli [...] new 9046e058ce 56: onsuccess: #472: 1: Success after binutils/gcc/linux/gdb [...] new 1456d04a7c 57: onsuccess: #473: 1: Success after binutils/gcc/linux/gli [...] new 70e5213358 58: onsuccess: #474: 1: Success after binutils/gcc/linux/gli [...] new d71bbe382f 59: onsuccess: #475: 1: Success after binutils/gcc/linux/gli [...] new 6227653263 60: onsuccess: #476: 1: Success after binutils/gcc/linux/gli [...] new 8ae8739f6d 61: onsuccess: #477: 1: Success after binutils/gcc/linux/gli [...] new ff8250d91f 62: onsuccess: #478: 1: Success after binutils/gcc/linux/gli [...] new c2895aa094 63: onsuccess: #479: 1: Success after binutils/gcc/linux/gli [...] new f1a50a0b12 64: onsuccess: #480: 1: Success after binutils/gcc/linux/gli [...] new b78e41fa14 65: onsuccess: #481: 1: Success after binutils/gcc/linux/gdb [...] new 552313d8dc 66: onsuccess: #482: 1: Success after binutils/gcc/linux/gli [...] new a2ab5aab38 67: onsuccess: #483: 1: Success after binutils/gcc/linux/gli [...] new 3ae0d24de6 68: onsuccess: #484: 1: Success after binutils/gcc/linux/gli [...] new cdbcc06509 69: onsuccess: #485: 1: Success after binutils/gcc/linux/gdb [...] new 74a5df3382 70: onsuccess: #486: 1: Success after binutils/gcc/linux/gli [...] new 618fb26fb0 71: onsuccess: #487: 1: Success after binutils/gcc/linux/gdb [...] new a3a6d98257 72: onsuccess: #488: 1: Success after binutils/gcc/linux/gli [...] new a8836a624c 73: onsuccess: #489: 1: Success after binutils/gcc/glibc/gdb [...] new ba36805a27 74: onsuccess: #490: 1: Success after binutils/gcc/linux/gli [...] new 9149d72fa5 75: onsuccess: #491: 1: Success after binutils/gcc/linux/gdb [...] new 7ccd198715 76: onsuccess: #492: 1: Success after binutils/gcc/linux/gdb [...] new 304e3653ba 77: onsuccess: #493: 1: Success after binutils/gcc/linux/gdb [...] new 264e413f9f 78: onsuccess: #494: 1: Success after binutils/gcc/linux/gli [...] new 22156b8ed7 79: onsuccess: #495: 1: Success after binutils/gcc/linux/gli [...] new da85553bff 80: onsuccess: #496: 1: Success after binutils/gcc/linux/gli [...] new 7238e95434 81: onsuccess: #497: 1: Success after binutils/gcc/linux/gli [...] new 838811925d 82: onsuccess: #498: 1: Success after binutils/gcc/linux/gli [...] new c74645e41d 83: onsuccess: #499: 1: Success after binutils/gcc/linux/gdb [...] new 8a5f7d8ef3 84: onsuccess: #500: 1: Success after binutils/gcc/linux/gli [...] new 9f68af69a3 85: onsuccess: #501: 1: Success after binutils/gcc/linux/gli [...] new 2f024f0062 86: onsuccess: #503: 1: Success after binutils: 12 commits new 7bc02763d0 87: onsuccess: #505: 1: Success after glibc: 7 commits new e3d1df8921 88: onsuccess: #506: 1: Success after linux: 34 commits new 0e3ee5c260 89: onsuccess: #508: 1: Success after binutils: 12 commits new 92d76e6220 90: onsuccess: #510: 1: Success after glibc: 5 commits new 31dd9c9375 91: onsuccess: #511: 1: Success after linux: 27 commits new 5d6b502e67 92: onsuccess: #512: 1: Success after binutils/gcc/linux/gli [...] new 89bb44b443 93: onsuccess: #513: 1: Success after binutils/gcc/linux/gli [...] new 929b73f3d2 94: onsuccess: #514: 1: Success after binutils/gcc/linux/gdb [...] new 010c7a9268 95: onsuccess: #515: 1: Success after binutils/gcc/linux/gdb [...] new 0dcd440898 96: onsuccess: #516: 1: Success after binutils/gcc/linux/gli [...] new 2673b35d1e 97: onsuccess: #517: 1: Success after binutils/gcc/linux/gli [...] new dc90e0adcd 98: onsuccess: #518: 1: Success after binutils/gcc/linux/gli [...] new 7766f04292 99: onsuccess: #519: 1: Success after binutils/gcc/linux/gli [...] new 0d032ef7c5 100: onsuccess: #521: 1: Success after binutils: 10 commits new 0a5486bbbd 101: onsuccess: #524: 1: Success after binutils: 2 commits new fca2bc4066 102: onsuccess: #527: 1: Success after binutils: 5 commits new cb3ec0e347 103: onsuccess: #529: 1: Success after binutils/gcc/linux/gl [...] new d67cf0e4fd 104: onsuccess: #530: 1: Success after gcc: 7 commits new 76a142fee1 105: onsuccess: #531: 1: Success after binutils/gcc/linux/gd [...] new abef5c937d 106: onsuccess: #532: 1: Success after binutils/gcc/linux/gl [...] new 299a3f2f6f 107: onsuccess: #533: 1: Success after binutils/gcc/linux/gd [...] new 2968d67126 108: onsuccess: #534: 1: Success after binutils/gcc/linux/gd [...] new a7ae0fb04a 109: onsuccess: #535: 1: Success after binutils/gcc/linux/gd [...] new aa22619e05 110: onsuccess: #536: 1: Success after binutils/gcc/glibc/gd [...] new 9587975d63 111: onsuccess: #537: 1: Success after binutils/gcc/gdb: 69 commits new 819b36bd5e 112: onsuccess: #538: 1: Success after binutils/gcc/linux/gd [...] new c575b2233c 113: onsuccess: #539: 1: Success after binutils/gcc/linux/gd [...] new 0de0b1feed 114: onsuccess: #541: 1: Success after binutils/gcc/linux/gd [...] new 0c5e0df77f 115: onsuccess: #542: 1: Success after binutils/gcc/linux/gl [...] new dd2f60f82b 116: onsuccess: #543: 1: Success after binutils/gcc/linux/gl [...] new ab56093aae 117: onsuccess: #544: 1: Success after binutils/gcc/linux/gl [...] new be4821e31b 118: onsuccess: #545: 1: Success after binutils/gcc/linux/gd [...] new b60d21973d 119: onsuccess: #546: 1: Success after binutils/gcc/linux/gd [...] new bad92de5e4 120: onsuccess: #547: 1: Success after binutils/gcc/linux/gl [...] new 692e8dcb75 121: onsuccess: #548: 1: Success after binutils/gcc/linux/gd [...] new 659a4bdc88 122: onsuccess: #549: 1: Success after binutils/gcc/linux/gd [...] new e7d54e77c7 123: onsuccess: #550: 1: Success after binutils/gcc/linux/gd [...] new a35630bc74 124: onsuccess: #551: 1: Success after binutils/gcc/linux/gl [...] new c1a445f3cf 125: onsuccess: #552: 1: Success after binutils/gcc/linux/gl [...] new 097b8357e8 126: onsuccess: #553: 1: Success after binutils/gcc/linux/gl [...] new 8937ec58a8 127: onsuccess: #554: 1: Success after binutils/gcc/linux/gl [...] new a782e8a688 128: onsuccess: #555: 1: Success after binutils/gcc/linux/gd [...] new 750a760dfd 129: onsuccess: #556: 1: Success after binutils/gcc/linux/gd [...] new 1de2020f6c 130: onsuccess: #557: 1: Success after binutils/gcc/linux/gl [...] new 963ffe3324 131: onsuccess: #558: 1: Success after binutils/gcc/linux/gl [...] new 1606d19f8e 132: onsuccess: #559: 1: Success after binutils/gcc/linux/gd [...] new 31a0adb943 133: onsuccess: #560: 1: Success after binutils/gcc/linux/gl [...] new 404428e5f8 134: onsuccess: #561: 1: Success after binutils/gcc/linux/gd [...] new 81baf3fb24 135: onsuccess: #562: 1: Success after binutils/gcc/linux/gd [...] new 3a74f60b9a 136: onsuccess: #563: 1: Success after binutils/gcc/glibc/gd [...] new 03681b3e35 137: onsuccess: #564: 1: Success after binutils/gcc/linux/gl [...] new bae6299243 138: onsuccess: #565: 1: Success after binutils/gcc/linux/gl [...] new 60b0501c70 139: onsuccess: #566: 1: Success after binutils/gcc/linux/gl [...] new 29044edbd9 140: onsuccess: #567: 1: Success after binutils/gcc/linux/gl [...] new 2e31e3ded1 141: onsuccess: #568: 1: Success after binutils/gcc/linux/gd [...] new 20b509cfd7 142: onsuccess: #569: 1: Success after binutils/gcc/gdb: 46 commits new eb29263f7c 143: onsuccess: #570: 1: Success after binutils/gcc/linux/gd [...] new 5ed474cd86 144: onsuccess: #571: 1: Success after binutils/gcc/gdb: 28 commits new 5560616bd1 145: onsuccess: #572: 1: Success after binutils/gcc/gdb: 27 commits new 6e9d7b9219 146: onsuccess: #573: 1: Success after binutils/gcc/gdb: 11 commits new 084e94bdb8 147: onsuccess: #574: 1: Success after binutils/gcc/linux/gl [...] new ddbf7af160 148: onsuccess: #575: 1: Success after binutils/gcc/linux/gd [...] new cc436ed5d3 149: onsuccess: #576: 1: Success after binutils/gcc/linux/gd [...] new ef74a04229 150: onsuccess: #577: 1: Success after binutils/gcc/linux/gd [...] new bc816971bf 151: onsuccess: #579: 1: Success after binutils: 21 commits

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 (7e2d96c92f) \ 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 1776 -> 1680 bytes 02-prepare_abe/console.log.xz | Bin 2748 -> 2756 bytes 03-build_abe-binutils/console.log.xz | Bin 52608 -> 53352 bytes 04-build_abe-gcc/console.log.xz | Bin 238256 -> 238156 bytes 05-clean_sysroot/console.log.xz | Bin 316 -> 316 bytes 06-build_abe-linux/console.log.xz | Bin 8364 -> 8512 bytes 07-build_abe-glibc/console.log.xz | Bin 236492 -> 236916 bytes 08-build_abe-gdb/console.log.xz | Bin 52012 -> 51228 bytes 09-build_abe-dejagnu/console.log.xz | Bin 3840 -> 3824 bytes 10-build_abe-check_binutils/console.log.xz | Bin 2188 -> 2704 bytes 11-check_regression/console.log.xz | Bin 5660 -> 4708 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 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 2 +- mail/mail-subject.txt | 2 +- manifest.sh | 28 +-- sumfiles/binutils.log.xz | Bin 62656 -> 62756 bytes sumfiles/binutils.sum | 62 +++--- sumfiles/gas.log.xz | Bin 100352 -> 100508 bytes sumfiles/gas.sum | 272 +++++++++++------------ sumfiles/ld.log.xz | Bin 132176 -> 132292 bytes sumfiles/ld.sum | 344 ++++++++++++++--------------- 26 files changed, 395 insertions(+), 399 deletions(-)