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 7d32e776a1f 218: onsuccess: #29: 1: Success after binutils/gcc/linux/gd [...] discards a89975fc6fe 217: onsuccess: #28: 1: Success after binutils/gcc/linux/gd [...] discards fa8a288b49e 216: onsuccess: #27: 1: Success after binutils/gcc/linux/gd [...] discards e05e661a687 215: onsuccess: #26: 1: Success after binutils: 10 commits discards fd592ba8e3b 214: force: #25: 1: Failure after gdb-13-branchpoint-1445-g [...] discards d4ed5c8cc5f 213: force: #24: 1: Success after binutils: 2 commits discards ec9e3409c22 212: onsuccess: #23: 1: Success after gcc/linux/gdb: 40 commits discards af8aefc04cd 211: onsuccess: #20: 1: Success after binutils/gcc/linux/gl [...] discards 0d46e61ad4a 210: onsuccess: #19: 1: Success after binutils/gcc/linux/gl [...] discards 03d8dec96f3 209: onsuccess: #18: 1: Success after binutils/gcc/linux/gl [...] discards abae98ed674 208: onsuccess: #17: 1: Success after binutils/gcc/linux/gd [...] discards 73a90d502e9 207: onsuccess: #16: 1: Success after binutils/gcc/linux/gl [...] discards 73e52606b30 206: onsuccess: #15: 1: Success after binutils/gcc/linux/gd [...] discards 495a22e5a5e 205: onsuccess: #14: 1: Success after binutils/gcc/linux/gl [...] discards f708efd2474 204: onsuccess: #12: 1: Success after binutils/gcc/linux/gl [...] discards 95f844ad542 203: onsuccess: #11: 1: Success after binutils/gcc/linux/gd [...] discards 18fab158fdc 202: onsuccess: #10: 1: Success after binutils/gcc/linux/gd [...] discards 3dfd2845934 201: onsuccess: #9: 1: Success after binutils/gcc/linux/gdb [...] discards 182a901fca1 200: onsuccess: #8: 1: Success after binutils/gcc/linux/gli [...] discards 3906038d51e 199: onsuccess: #7: 1: Success after binutils/gcc/linux/gli [...] discards 2ed464622a0 198: onsuccess: #6: 1: Success after binutils/gcc/linux/gli [...] discards bb3c0189370 197: onsuccess: #5: 1: Success after binutils/gcc/linux/gli [...] discards 7eb454d9359 196: onsuccess: #4: 1: Success after binutils/gcc/linux/gdb [...] discards afeac59bbaf 195: onsuccess: #3: 1: Success after binutils/gcc/linux/gli [...] discards a11c13dbf4a 194: onsuccess: #2: 1: Success after binutils/gcc/linux/gdb [...] discards 4b881173798 193: onsuccess: #1: 1: Success after binutils/gcc/linux/gli [...] discards d4001dd83bb 192: onsuccess: #627: 1: Success after binutils/gcc/linux/g [...] discards a83c5d5d01f 191: onsuccess: #626: 1: Success after binutils/gcc/linux/g [...] discards f2cb3bbc948 190: onsuccess: #625: 1: Success after binutils/gcc/linux/g [...] discards 35652a37852 189: onsuccess: #619: 1: Success after binutils/gcc/linux/g [...] discards 9469e33adb8 188: onsuccess: #618: 1: Success after binutils/gcc/linux/g [...] discards bb286927cdf 187: onsuccess: #617: 1: Success after binutils/gcc/linux/g [...] discards 63b72d0aa68 186: onsuccess: #616: 1: Success after binutils/gcc/linux/g [...] discards 51aecefbeb4 185: onsuccess: #615: 1: Success after binutils/gcc/linux/g [...] discards df2b54d3b27 184: onsuccess: #614: 1: Success after binutils/gcc/linux/g [...] discards 2f876a2787a 183: onsuccess: #612: 1: Success after binutils/gcc/glibc/g [...] discards bff7e6fec39 182: onsuccess: #611: 1: Success after binutils/gcc/linux/g [...] discards 1fc316a2e96 181: onsuccess: #610: 1: Success after binutils/gcc/linux/g [...] discards d6da09311e2 180: onsuccess: #609: 1: Success after binutils/gcc/linux/g [...] discards 18f4ea783cb 179: onsuccess: #608: 1: Success after binutils/gcc/linux/g [...] discards 3bb02b5d760 178: onsuccess: #607: 1: Success after binutils/gcc/linux/g [...] discards 6537745051e 177: onsuccess: #606: 1: Success after binutils/gcc/linux/g [...] discards b2da90c2054 176: onsuccess: #605: 1: Success after binutils/gcc/linux/g [...] discards d4ec86cf97a 175: onsuccess: #604: 1: Success after binutils/gcc/glibc/g [...] discards c49e43cc2c7 174: onsuccess: #603: 1: Success after binutils/gcc/linux/g [...] discards 416cb56bf12 173: onsuccess: #602: 1: Success after binutils/gcc/linux/g [...] discards 600d7d4f847 172: onsuccess: #601: 1: Success after binutils/gcc/linux/g [...] discards ad9603a4abb 171: onsuccess: #600: 1: Success after binutils/gcc/linux/g [...] discards 54bc0065635 170: onsuccess: #599: 1: Success after binutils/gcc/linux/g [...] discards bf517869265 169: onsuccess: #598: 1: Success after binutils/gcc/linux/g [...] discards 1df952d213e 168: onsuccess: #597: 1: Success after binutils/gcc/linux/g [...] discards c4a9f8be602 167: onsuccess: #596: 1: Success after binutils/gcc/linux/g [...] discards 67446f7d376 166: onsuccess: #595: 1: Success after binutils/gcc/linux/g [...] discards f0c1a4d584c 165: onsuccess: #594: 1: Success after binutils/gcc/linux/g [...] discards 0ea00e096fa 164: onsuccess: #593: 1: Success after binutils/gcc/linux/g [...] discards d53d56b5de9 163: onsuccess: #592: 1: Success after binutils/gcc/linux/g [...] discards df01ff5511f 162: onsuccess: #591: 1: Success after binutils/gcc/linux/g [...] discards 0dfcf19b47f 161: onsuccess: #590: 1: Success after binutils/gcc/linux/g [...] discards 58a805c1fc1 160: onsuccess: #589: 1: Success after binutils/gcc/linux/g [...] discards 72b399647d7 159: onsuccess: #588: 1: Success after binutils/gcc/linux/g [...] discards 4ad0a519fee 158: onsuccess: #587: 1: Success after binutils/gcc/linux/g [...] discards 97794cb5fce 157: onsuccess: #586: 1: Success after binutils/gcc/linux/g [...] discards 15d249f7637 156: onsuccess: #585: 1: Success after binutils/gcc/linux/g [...] discards 60c066c0e47 155: onsuccess: #584: 1: Success after binutils/gcc/glibc/g [...] discards b7ef001ecc4 154: onsuccess: #583: 1: Success after linux: 10 commits discards 7341707c8bb 153: onsuccess: #582: 1: Success after glibc: 9 commits discards 4a21787fe75 152: onsuccess: #580: 1: Success after gcc: 6 commits discards 097791d1a55 151: onsuccess: #579: 1: Success after binutils: 21 commits discards 66fe224c395 150: onsuccess: #577: 1: Success after binutils/gcc/linux/g [...] discards 38b165f5f1f 149: onsuccess: #576: 1: Success after binutils/gcc/linux/g [...] discards 6161f6d8ead 148: onsuccess: #575: 1: Success after binutils/gcc/linux/g [...] discards 0432ffe3426 147: onsuccess: #574: 1: Success after binutils/gcc/linux/g [...] discards 640ecbf56fb 146: onsuccess: #573: 1: Success after binutils/gcc/gdb: 11 [...] discards e1629752b77 145: onsuccess: #572: 1: Success after binutils/gcc/gdb: 27 [...] discards b2e7c6298c2 144: onsuccess: #571: 1: Success after binutils/gcc/gdb: 28 [...] discards 13181dc1bed 143: onsuccess: #570: 1: Success after binutils/gcc/linux/g [...] discards a2210677d24 142: onsuccess: #569: 1: Success after binutils/gcc/gdb: 46 [...] discards ac272d6b9b7 141: onsuccess: #568: 1: Success after binutils/gcc/linux/g [...] discards 2e94cc61b59 140: onsuccess: #567: 1: Success after binutils/gcc/linux/g [...] discards ef0d2480d71 139: onsuccess: #566: 1: Success after binutils/gcc/linux/g [...] discards e88103de367 138: onsuccess: #565: 1: Success after binutils/gcc/linux/g [...] discards 6a0f0a9328f 137: onsuccess: #564: 1: Success after binutils/gcc/linux/g [...] discards 985d9f75886 136: onsuccess: #563: 1: Success after binutils/gcc/glibc/g [...] discards 80ad56c4e0c 135: onsuccess: #562: 1: Success after binutils/gcc/linux/g [...] discards 4816b12ef3a 134: onsuccess: #561: 1: Success after binutils/gcc/linux/g [...] discards b1cc4c86b69 133: onsuccess: #560: 1: Success after binutils/gcc/linux/g [...] discards 3429d23108e 132: onsuccess: #559: 1: Success after binutils/gcc/linux/g [...] discards 7ecb852e651 131: onsuccess: #558: 1: Success after binutils/gcc/linux/g [...] discards 8e8bf7ce5d2 130: onsuccess: #557: 1: Success after binutils/gcc/linux/g [...] discards 9550b3671a5 129: onsuccess: #556: 1: Success after binutils/gcc/linux/g [...] discards 556ffd7f9fa 128: onsuccess: #555: 1: Success after binutils/gcc/linux/g [...] discards e98fbc67616 127: onsuccess: #554: 1: Success after binutils/gcc/linux/g [...] discards 2bc85c0bbcf 126: onsuccess: #553: 1: Success after binutils/gcc/linux/g [...] discards dbac86b8ea7 125: onsuccess: #552: 1: Success after binutils/gcc/linux/g [...] discards f4e05ae974d 124: onsuccess: #551: 1: Success after binutils/gcc/linux/g [...] discards 2a5c0aff1d0 123: onsuccess: #550: 1: Success after binutils/gcc/linux/g [...] discards 0ed14b8b223 122: onsuccess: #549: 1: Success after binutils/gcc/linux/g [...] discards 149ac29b5b2 121: onsuccess: #548: 1: Success after binutils/gcc/linux/g [...] discards f0e00de53cf 120: onsuccess: #547: 1: Success after binutils/gcc/linux/g [...] discards 13e9e9af043 119: onsuccess: #546: 1: Success after binutils/gcc/linux/g [...] discards bd20d1c0399 118: onsuccess: #545: 1: Success after binutils/gcc/linux/g [...] new a92e3542b90 118: onsuccess: #545: 1: Success after binutils/gcc/linux/g [...] new fe2c886ad0a 119: onsuccess: #546: 1: Success after binutils/gcc/linux/g [...] new dfb71afeb40 120: onsuccess: #547: 1: Success after binutils/gcc/linux/g [...] new 4b562fae509 121: onsuccess: #548: 1: Success after binutils/gcc/linux/g [...] new 7c66f9bac7d 122: onsuccess: #549: 1: Success after binutils/gcc/linux/g [...] new 05b5646fbdf 123: onsuccess: #550: 1: Success after binutils/gcc/linux/g [...] new 8919be91ed0 124: onsuccess: #551: 1: Success after binutils/gcc/linux/g [...] new d9426d247cd 125: onsuccess: #552: 1: Success after binutils/gcc/linux/g [...] new 572553a4458 126: onsuccess: #553: 1: Success after binutils/gcc/linux/g [...] new 624c8bc5f17 127: onsuccess: #554: 1: Success after binutils/gcc/linux/g [...] new c493d9f37f5 128: onsuccess: #555: 1: Success after binutils/gcc/linux/g [...] new 2b732399a69 129: onsuccess: #556: 1: Success after binutils/gcc/linux/g [...] new 49cfe0467cc 130: onsuccess: #557: 1: Success after binutils/gcc/linux/g [...] new a693542a3cb 131: onsuccess: #558: 1: Success after binutils/gcc/linux/g [...] new af0c58c575a 132: onsuccess: #559: 1: Success after binutils/gcc/linux/g [...] new 92df6b47e47 133: onsuccess: #560: 1: Success after binutils/gcc/linux/g [...] new 3a6edd5e8db 134: onsuccess: #561: 1: Success after binutils/gcc/linux/g [...] new bb49ecffe2b 135: onsuccess: #562: 1: Success after binutils/gcc/linux/g [...] new 7de4cff5d1a 136: onsuccess: #563: 1: Success after binutils/gcc/glibc/g [...] new f284e8212bf 137: onsuccess: #564: 1: Success after binutils/gcc/linux/g [...] new 2d0e8b0dda1 138: onsuccess: #565: 1: Success after binutils/gcc/linux/g [...] new f4e0fd6588d 139: onsuccess: #566: 1: Success after binutils/gcc/linux/g [...] new b0d83cce7e7 140: onsuccess: #567: 1: Success after binutils/gcc/linux/g [...] new ca5e26726e1 141: onsuccess: #568: 1: Success after binutils/gcc/linux/g [...] new dc72353725f 142: onsuccess: #569: 1: Success after binutils/gcc/gdb: 46 [...] new 80e09b26c91 143: onsuccess: #570: 1: Success after binutils/gcc/linux/g [...] new 370de1dbac3 144: onsuccess: #571: 1: Success after binutils/gcc/gdb: 28 [...] new 574a73c06c4 145: onsuccess: #572: 1: Success after binutils/gcc/gdb: 27 [...] new 3ce7a051e19 146: onsuccess: #573: 1: Success after binutils/gcc/gdb: 11 [...] new 3648e4c28cc 147: onsuccess: #574: 1: Success after binutils/gcc/linux/g [...] new d13b7af2aeb 148: onsuccess: #575: 1: Success after binutils/gcc/linux/g [...] new 4a28cb3c676 149: onsuccess: #576: 1: Success after binutils/gcc/linux/g [...] new 71bc66a48bf 150: onsuccess: #577: 1: Success after binutils/gcc/linux/g [...] new c279e8e82b3 151: onsuccess: #579: 1: Success after binutils: 21 commits new 629af60772f 152: onsuccess: #580: 1: Success after gcc: 6 commits new c5ea03e72ff 153: onsuccess: #582: 1: Success after glibc: 9 commits new 2a5f4682567 154: onsuccess: #583: 1: Success after linux: 10 commits new c77c95cd6bf 155: onsuccess: #584: 1: Success after binutils/gcc/glibc/g [...] new 7aeae383333 156: onsuccess: #585: 1: Success after binutils/gcc/linux/g [...] new 893879d83ef 157: onsuccess: #586: 1: Success after binutils/gcc/linux/g [...] new 91f5bc9708c 158: onsuccess: #587: 1: Success after binutils/gcc/linux/g [...] new 193133d43dd 159: onsuccess: #588: 1: Success after binutils/gcc/linux/g [...] new d906d5c98ca 160: onsuccess: #589: 1: Success after binutils/gcc/linux/g [...] new d681812ed41 161: onsuccess: #590: 1: Success after binutils/gcc/linux/g [...] new d9c3bff9ba2 162: onsuccess: #591: 1: Success after binutils/gcc/linux/g [...] new da2077f97fa 163: onsuccess: #592: 1: Success after binutils/gcc/linux/g [...] new 12a1b13f3ee 164: onsuccess: #593: 1: Success after binutils/gcc/linux/g [...] new d767efc7bce 165: onsuccess: #594: 1: Success after binutils/gcc/linux/g [...] new fb6a826ed0c 166: onsuccess: #595: 1: Success after binutils/gcc/linux/g [...] new d9c2f9b46a3 167: onsuccess: #596: 1: Success after binutils/gcc/linux/g [...] new b9eded0a5c5 168: onsuccess: #597: 1: Success after binutils/gcc/linux/g [...] new d745abe7cf5 169: onsuccess: #598: 1: Success after binutils/gcc/linux/g [...] new 727000d8d44 170: onsuccess: #599: 1: Success after binutils/gcc/linux/g [...] new a501b01ec3e 171: onsuccess: #600: 1: Success after binutils/gcc/linux/g [...] new 482b34dfc99 172: onsuccess: #601: 1: Success after binutils/gcc/linux/g [...] new ece146bb350 173: onsuccess: #602: 1: Success after binutils/gcc/linux/g [...] new c675be56c88 174: onsuccess: #603: 1: Success after binutils/gcc/linux/g [...] new 0d1cc2bff6f 175: onsuccess: #604: 1: Success after binutils/gcc/glibc/g [...] new a382bec921f 176: onsuccess: #605: 1: Success after binutils/gcc/linux/g [...] new fc816e74249 177: onsuccess: #606: 1: Success after binutils/gcc/linux/g [...] new f7b9b80a53b 178: onsuccess: #607: 1: Success after binutils/gcc/linux/g [...] new d62e26a665f 179: onsuccess: #608: 1: Success after binutils/gcc/linux/g [...] new 20452baad4a 180: onsuccess: #609: 1: Success after binutils/gcc/linux/g [...] new 2affe4d7277 181: onsuccess: #610: 1: Success after binutils/gcc/linux/g [...] new 9e8f3e8b216 182: onsuccess: #611: 1: Success after binutils/gcc/linux/g [...] new 928729b879d 183: onsuccess: #612: 1: Success after binutils/gcc/glibc/g [...] new 2f03bfd6935 184: onsuccess: #614: 1: Success after binutils/gcc/linux/g [...] new 5806c4bb590 185: onsuccess: #615: 1: Success after binutils/gcc/linux/g [...] new 46595f27a40 186: onsuccess: #616: 1: Success after binutils/gcc/linux/g [...] new 76472cd63f6 187: onsuccess: #617: 1: Success after binutils/gcc/linux/g [...] new 3dfdeeee854 188: onsuccess: #618: 1: Success after binutils/gcc/linux/g [...] new de74722c9f9 189: onsuccess: #619: 1: Success after binutils/gcc/linux/g [...] new e4c567ed963 190: onsuccess: #625: 1: Success after binutils/gcc/linux/g [...] new 2a397ab6aa8 191: onsuccess: #626: 1: Success after binutils/gcc/linux/g [...] new 1d1c56f06c2 192: onsuccess: #627: 1: Success after binutils/gcc/linux/g [...] new 81c35200949 193: onsuccess: #1: 1: Success after binutils/gcc/linux/gli [...] new 3317461770f 194: onsuccess: #2: 1: Success after binutils/gcc/linux/gdb [...] new ea16e9c2fa1 195: onsuccess: #3: 1: Success after binutils/gcc/linux/gli [...] new 148497f309f 196: onsuccess: #4: 1: Success after binutils/gcc/linux/gdb [...] new ce12635b717 197: onsuccess: #5: 1: Success after binutils/gcc/linux/gli [...] new 00b0b2fa0ed 198: onsuccess: #6: 1: Success after binutils/gcc/linux/gli [...] new cd308924241 199: onsuccess: #7: 1: Success after binutils/gcc/linux/gli [...] new fe010a8dd99 200: onsuccess: #8: 1: Success after binutils/gcc/linux/gli [...] new e66160b9f73 201: onsuccess: #9: 1: Success after binutils/gcc/linux/gdb [...] new 10f224869f3 202: onsuccess: #10: 1: Success after binutils/gcc/linux/gd [...] new 65d40270dc2 203: onsuccess: #11: 1: Success after binutils/gcc/linux/gd [...] new 8eff86aa7eb 204: onsuccess: #12: 1: Success after binutils/gcc/linux/gl [...] new b0e882f612a 205: onsuccess: #14: 1: Success after binutils/gcc/linux/gl [...] new 6734bb95020 206: onsuccess: #15: 1: Success after binutils/gcc/linux/gd [...] new 9b845c9487c 207: onsuccess: #16: 1: Success after binutils/gcc/linux/gl [...] new e1557bc3df9 208: onsuccess: #17: 1: Success after binutils/gcc/linux/gd [...] new 3942cbb69ea 209: onsuccess: #18: 1: Success after binutils/gcc/linux/gl [...] new 0dc35883ac9 210: onsuccess: #19: 1: Success after binutils/gcc/linux/gl [...] new b98453cb6c1 211: onsuccess: #20: 1: Success after binutils/gcc/linux/gl [...] new bcc3ebb2840 212: onsuccess: #23: 1: Success after gcc/linux/gdb: 40 commits new 0c8825270c9 213: force: #24: 1: Success after binutils: 2 commits new 253ef55e994 214: force: #25: 1: Failure after gdb-13-branchpoint-1445-g [...] new 9cec68b0f56 215: onsuccess: #26: 1: Success after binutils: 10 commits new 15d3b8388f7 216: onsuccess: #27: 1: Success after binutils/gcc/linux/gd [...] new b2459ecf987 217: onsuccess: #28: 1: Success after binutils/gcc/linux/gd [...] new 94d1cf1751c 218: onsuccess: #29: 1: Success after binutils/gcc/linux/gd [...] new 7ee9a3327ca 219: onsuccess: #31: 1: Success after binutils/gcc/linux/gd [...]

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 (7d32e776a1f) \ 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 1792 -> 1744 bytes 02-prepare_abe/console.log.xz | Bin 2516 -> 2496 bytes 03-build_abe-binutils/console.log.xz | Bin 48868 -> 48496 bytes 04-build_abe-gcc/console.log.xz | Bin 234804 -> 235160 bytes 05-clean_sysroot/console.log.xz | Bin 316 -> 316 bytes 06-build_abe-linux/console.log.xz | Bin 8856 -> 8404 bytes 07-build_abe-glibc/console.log.xz | Bin 233584 -> 233480 bytes 08-build_abe-gdb/console.log.xz | Bin 47008 -> 47432 bytes 09-build_abe-dejagnu/console.log.xz | Bin 3788 -> 3788 bytes 10-build_abe-check_binutils/console.log.xz | Bin 2112 -> 2108 bytes 11-check_regression/console.log.xz | Bin 4704 -> 4752 bytes 11-check_regression/results.compare | 10 +++---- 11-check_regression/results.compare2 | 6 ++-- 12-update_baseline/console.log | 44 ++++++++++++++--------------- 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 | 34 +++++++++++----------- sumfiles/binutils.log.xz | Bin 62396 -> 62852 bytes sumfiles/binutils.sum | 2 +- sumfiles/gas.log.xz | Bin 100592 -> 100640 bytes sumfiles/gas.sum | 4 +-- sumfiles/ld.log.xz | Bin 132240 -> 132192 bytes sumfiles/ld.sum | 4 +-- 29 files changed, 60 insertions(+), 60 deletions(-)