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 6720fdf801a 217: onsuccess: #28: 1: Success after binutils/gcc/linux/gd [...] discards ad374716eb7 216: onsuccess: #27: 1: Success after binutils/gcc/linux/gd [...] discards 8f8eb7c66d9 215: onsuccess: #26: 1: Success after binutils: 10 commits discards 15b05c91d4c 214: force: #25: 1: Failure after gdb-13-branchpoint-1445-g [...] discards 2d6cdb45a69 213: force: #24: 1: Success after binutils: 2 commits discards 9c5fe080036 212: onsuccess: #23: 1: Success after gcc/linux/gdb: 40 commits discards 7ef36df70e7 211: onsuccess: #20: 1: Success after binutils/gcc/linux/gl [...] discards 42eca74e78a 210: onsuccess: #19: 1: Success after binutils/gcc/linux/gl [...] discards fde1e3f6e33 209: onsuccess: #18: 1: Success after binutils/gcc/linux/gl [...] discards 3fa47fba262 208: onsuccess: #17: 1: Success after binutils/gcc/linux/gd [...] discards 3946e7e7ce0 207: onsuccess: #16: 1: Success after binutils/gcc/linux/gl [...] discards 6471cc9f1ae 206: onsuccess: #15: 1: Success after binutils/gcc/linux/gd [...] discards 51cc47d8479 205: onsuccess: #14: 1: Success after binutils/gcc/linux/gl [...] discards a5eba888bdb 204: onsuccess: #12: 1: Success after binutils/gcc/linux/gl [...] discards 0df1b125ba0 203: onsuccess: #11: 1: Success after binutils/gcc/linux/gd [...] discards f4a59ba2363 202: onsuccess: #10: 1: Success after binutils/gcc/linux/gd [...] discards 78cdb252b43 201: onsuccess: #9: 1: Success after binutils/gcc/linux/gdb [...] discards 435ac013fae 200: onsuccess: #8: 1: Success after binutils/gcc/linux/gli [...] discards 7a871e5fbc0 199: onsuccess: #7: 1: Success after binutils/gcc/linux/gli [...] discards 474952f2eba 198: onsuccess: #6: 1: Success after binutils/gcc/linux/gli [...] discards faf286e8b48 197: onsuccess: #5: 1: Success after binutils/gcc/linux/gli [...] discards 588658a8477 196: onsuccess: #4: 1: Success after binutils/gcc/linux/gdb [...] discards 35f082a25ee 195: onsuccess: #3: 1: Success after binutils/gcc/linux/gli [...] discards 01c9cd7694f 194: onsuccess: #2: 1: Success after binutils/gcc/linux/gdb [...] discards a789304a9e2 193: onsuccess: #1: 1: Success after binutils/gcc/linux/gli [...] discards 284072c1173 192: onsuccess: #627: 1: Success after binutils/gcc/linux/g [...] discards 0ab09c82e91 191: onsuccess: #626: 1: Success after binutils/gcc/linux/g [...] discards a065e5782a1 190: onsuccess: #625: 1: Success after binutils/gcc/linux/g [...] discards 28ea978ab5b 189: onsuccess: #619: 1: Success after binutils/gcc/linux/g [...] discards f5a90777563 188: onsuccess: #618: 1: Success after binutils/gcc/linux/g [...] discards 540b946f7fa 187: onsuccess: #617: 1: Success after binutils/gcc/linux/g [...] discards 33fcb45a541 186: onsuccess: #616: 1: Success after binutils/gcc/linux/g [...] discards 3162e6d3c4c 185: onsuccess: #615: 1: Success after binutils/gcc/linux/g [...] discards ad86c0b0903 184: onsuccess: #614: 1: Success after binutils/gcc/linux/g [...] discards b468eb10111 183: onsuccess: #612: 1: Success after binutils/gcc/glibc/g [...] discards 676653ce3be 182: onsuccess: #611: 1: Success after binutils/gcc/linux/g [...] discards b286678b17a 181: onsuccess: #610: 1: Success after binutils/gcc/linux/g [...] discards f68b5127613 180: onsuccess: #609: 1: Success after binutils/gcc/linux/g [...] discards 0c06aab21bd 179: onsuccess: #608: 1: Success after binutils/gcc/linux/g [...] discards 84165dd07a0 178: onsuccess: #607: 1: Success after binutils/gcc/linux/g [...] discards af7ee660b2c 177: onsuccess: #606: 1: Success after binutils/gcc/linux/g [...] discards 8ed42dabc27 176: onsuccess: #605: 1: Success after binutils/gcc/linux/g [...] discards cb9a104bf61 175: onsuccess: #604: 1: Success after binutils/gcc/glibc/g [...] discards 70659b1bd44 174: onsuccess: #603: 1: Success after binutils/gcc/linux/g [...] discards 21f43130e30 173: onsuccess: #602: 1: Success after binutils/gcc/linux/g [...] discards c6957ad5c96 172: onsuccess: #601: 1: Success after binutils/gcc/linux/g [...] discards bf33283a4ef 171: onsuccess: #600: 1: Success after binutils/gcc/linux/g [...] discards da3a1ad1c1f 170: onsuccess: #599: 1: Success after binutils/gcc/linux/g [...] discards 41bc5d102b1 169: onsuccess: #598: 1: Success after binutils/gcc/linux/g [...] discards f4ffab407f6 168: onsuccess: #597: 1: Success after binutils/gcc/linux/g [...] discards 7345086d2f9 167: onsuccess: #596: 1: Success after binutils/gcc/linux/g [...] discards ffd1728e8ce 166: onsuccess: #595: 1: Success after binutils/gcc/linux/g [...] discards df6ea40ebf1 165: onsuccess: #594: 1: Success after binutils/gcc/linux/g [...] discards 993eff5a2f7 164: onsuccess: #593: 1: Success after binutils/gcc/linux/g [...] discards 91e955e0c28 163: onsuccess: #592: 1: Success after binutils/gcc/linux/g [...] discards 30a77c2dd05 162: onsuccess: #591: 1: Success after binutils/gcc/linux/g [...] discards e86adf896cf 161: onsuccess: #590: 1: Success after binutils/gcc/linux/g [...] discards 07a1453359e 160: onsuccess: #589: 1: Success after binutils/gcc/linux/g [...] discards 9b163a70051 159: onsuccess: #588: 1: Success after binutils/gcc/linux/g [...] discards 21e40db2e05 158: onsuccess: #587: 1: Success after binutils/gcc/linux/g [...] discards a1d3828c2f4 157: onsuccess: #586: 1: Success after binutils/gcc/linux/g [...] discards b8e7c40b3b8 156: onsuccess: #585: 1: Success after binutils/gcc/linux/g [...] discards 2fee2974381 155: onsuccess: #584: 1: Success after binutils/gcc/glibc/g [...] discards 19aa6924f85 154: onsuccess: #583: 1: Success after linux: 10 commits discards 264704846e1 153: onsuccess: #582: 1: Success after glibc: 9 commits discards 37db674672d 152: onsuccess: #580: 1: Success after gcc: 6 commits discards d0b18dc9ac5 151: onsuccess: #579: 1: Success after binutils: 21 commits discards 46c8415d2c4 150: onsuccess: #577: 1: Success after binutils/gcc/linux/g [...] discards cc65863d589 149: onsuccess: #576: 1: Success after binutils/gcc/linux/g [...] discards a1f3fc955fc 148: onsuccess: #575: 1: Success after binutils/gcc/linux/g [...] discards ca8d626ffdc 147: onsuccess: #574: 1: Success after binutils/gcc/linux/g [...] discards a1d8df65f01 146: onsuccess: #573: 1: Success after binutils/gcc/gdb: 11 [...] discards 47fe9698d6a 145: onsuccess: #572: 1: Success after binutils/gcc/gdb: 27 [...] discards f89241a2949 144: onsuccess: #571: 1: Success after binutils/gcc/gdb: 28 [...] discards 8304c7f0923 143: onsuccess: #570: 1: Success after binutils/gcc/linux/g [...] discards 8f4eb5d33f9 142: onsuccess: #569: 1: Success after binutils/gcc/gdb: 46 [...] discards a171fdc57eb 141: onsuccess: #568: 1: Success after binutils/gcc/linux/g [...] discards 999d74f4c5c 140: onsuccess: #567: 1: Success after binutils/gcc/linux/g [...] discards f7ca202204a 139: onsuccess: #566: 1: Success after binutils/gcc/linux/g [...] discards 218c85bb966 138: onsuccess: #565: 1: Success after binutils/gcc/linux/g [...] discards 2d49d097609 137: onsuccess: #564: 1: Success after binutils/gcc/linux/g [...] discards 6faa4ef9950 136: onsuccess: #563: 1: Success after binutils/gcc/glibc/g [...] discards 3faa03e8871 135: onsuccess: #562: 1: Success after binutils/gcc/linux/g [...] discards 250cbaa5cf0 134: onsuccess: #561: 1: Success after binutils/gcc/linux/g [...] discards 139ba3bbfa1 133: onsuccess: #560: 1: Success after binutils/gcc/linux/g [...] discards 8296451eee4 132: onsuccess: #559: 1: Success after binutils/gcc/linux/g [...] discards 1971ab238a4 131: onsuccess: #558: 1: Success after binutils/gcc/linux/g [...] discards 6e6215ebc83 130: onsuccess: #557: 1: Success after binutils/gcc/linux/g [...] discards e5541dea43a 129: onsuccess: #556: 1: Success after binutils/gcc/linux/g [...] discards d86162fe3e9 128: onsuccess: #555: 1: Success after binutils/gcc/linux/g [...] discards 25efdaa46ce 127: onsuccess: #554: 1: Success after binutils/gcc/linux/g [...] discards 93ed7686f1c 126: onsuccess: #553: 1: Success after binutils/gcc/linux/g [...] discards eb27a776134 125: onsuccess: #552: 1: Success after binutils/gcc/linux/g [...] discards ad6e0be2c74 124: onsuccess: #551: 1: Success after binutils/gcc/linux/g [...] discards 740f7d2528f 123: onsuccess: #550: 1: Success after binutils/gcc/linux/g [...] discards dd00247e80e 122: onsuccess: #549: 1: Success after binutils/gcc/linux/g [...] discards 9ba979236ca 121: onsuccess: #548: 1: Success after binutils/gcc/linux/g [...] discards 0d2859a21d5 120: onsuccess: #547: 1: Success after binutils/gcc/linux/g [...] discards 16e09c2f304 119: onsuccess: #546: 1: Success after binutils/gcc/linux/g [...] discards 68401c8df37 118: onsuccess: #545: 1: Success after binutils/gcc/linux/g [...] discards 62383428b60 117: onsuccess: #544: 1: Success after binutils/gcc/linux/g [...] new 55088de991b 117: onsuccess: #544: 1: Success after binutils/gcc/linux/g [...] new bd20d1c0399 118: onsuccess: #545: 1: Success after binutils/gcc/linux/g [...] new 13e9e9af043 119: onsuccess: #546: 1: Success after binutils/gcc/linux/g [...] new f0e00de53cf 120: onsuccess: #547: 1: Success after binutils/gcc/linux/g [...] new 149ac29b5b2 121: onsuccess: #548: 1: Success after binutils/gcc/linux/g [...] new 0ed14b8b223 122: onsuccess: #549: 1: Success after binutils/gcc/linux/g [...] new 2a5c0aff1d0 123: onsuccess: #550: 1: Success after binutils/gcc/linux/g [...] new f4e05ae974d 124: onsuccess: #551: 1: Success after binutils/gcc/linux/g [...] new dbac86b8ea7 125: onsuccess: #552: 1: Success after binutils/gcc/linux/g [...] new 2bc85c0bbcf 126: onsuccess: #553: 1: Success after binutils/gcc/linux/g [...] new e98fbc67616 127: onsuccess: #554: 1: Success after binutils/gcc/linux/g [...] new 556ffd7f9fa 128: onsuccess: #555: 1: Success after binutils/gcc/linux/g [...] new 9550b3671a5 129: onsuccess: #556: 1: Success after binutils/gcc/linux/g [...] new 8e8bf7ce5d2 130: onsuccess: #557: 1: Success after binutils/gcc/linux/g [...] new 7ecb852e651 131: onsuccess: #558: 1: Success after binutils/gcc/linux/g [...] new 3429d23108e 132: onsuccess: #559: 1: Success after binutils/gcc/linux/g [...] new b1cc4c86b69 133: onsuccess: #560: 1: Success after binutils/gcc/linux/g [...] new 4816b12ef3a 134: onsuccess: #561: 1: Success after binutils/gcc/linux/g [...] new 80ad56c4e0c 135: onsuccess: #562: 1: Success after binutils/gcc/linux/g [...] new 985d9f75886 136: onsuccess: #563: 1: Success after binutils/gcc/glibc/g [...] new 6a0f0a9328f 137: onsuccess: #564: 1: Success after binutils/gcc/linux/g [...] new e88103de367 138: onsuccess: #565: 1: Success after binutils/gcc/linux/g [...] new ef0d2480d71 139: onsuccess: #566: 1: Success after binutils/gcc/linux/g [...] new 2e94cc61b59 140: onsuccess: #567: 1: Success after binutils/gcc/linux/g [...] new ac272d6b9b7 141: onsuccess: #568: 1: Success after binutils/gcc/linux/g [...] new a2210677d24 142: onsuccess: #569: 1: Success after binutils/gcc/gdb: 46 [...] new 13181dc1bed 143: onsuccess: #570: 1: Success after binutils/gcc/linux/g [...] new b2e7c6298c2 144: onsuccess: #571: 1: Success after binutils/gcc/gdb: 28 [...] new e1629752b77 145: onsuccess: #572: 1: Success after binutils/gcc/gdb: 27 [...] new 640ecbf56fb 146: onsuccess: #573: 1: Success after binutils/gcc/gdb: 11 [...] new 0432ffe3426 147: onsuccess: #574: 1: Success after binutils/gcc/linux/g [...] new 6161f6d8ead 148: onsuccess: #575: 1: Success after binutils/gcc/linux/g [...] new 38b165f5f1f 149: onsuccess: #576: 1: Success after binutils/gcc/linux/g [...] new 66fe224c395 150: onsuccess: #577: 1: Success after binutils/gcc/linux/g [...] new 097791d1a55 151: onsuccess: #579: 1: Success after binutils: 21 commits new 4a21787fe75 152: onsuccess: #580: 1: Success after gcc: 6 commits new 7341707c8bb 153: onsuccess: #582: 1: Success after glibc: 9 commits new b7ef001ecc4 154: onsuccess: #583: 1: Success after linux: 10 commits new 60c066c0e47 155: onsuccess: #584: 1: Success after binutils/gcc/glibc/g [...] new 15d249f7637 156: onsuccess: #585: 1: Success after binutils/gcc/linux/g [...] new 97794cb5fce 157: onsuccess: #586: 1: Success after binutils/gcc/linux/g [...] new 4ad0a519fee 158: onsuccess: #587: 1: Success after binutils/gcc/linux/g [...] new 72b399647d7 159: onsuccess: #588: 1: Success after binutils/gcc/linux/g [...] new 58a805c1fc1 160: onsuccess: #589: 1: Success after binutils/gcc/linux/g [...] new 0dfcf19b47f 161: onsuccess: #590: 1: Success after binutils/gcc/linux/g [...] new df01ff5511f 162: onsuccess: #591: 1: Success after binutils/gcc/linux/g [...] new d53d56b5de9 163: onsuccess: #592: 1: Success after binutils/gcc/linux/g [...] new 0ea00e096fa 164: onsuccess: #593: 1: Success after binutils/gcc/linux/g [...] new f0c1a4d584c 165: onsuccess: #594: 1: Success after binutils/gcc/linux/g [...] new 67446f7d376 166: onsuccess: #595: 1: Success after binutils/gcc/linux/g [...] new c4a9f8be602 167: onsuccess: #596: 1: Success after binutils/gcc/linux/g [...] new 1df952d213e 168: onsuccess: #597: 1: Success after binutils/gcc/linux/g [...] new bf517869265 169: onsuccess: #598: 1: Success after binutils/gcc/linux/g [...] new 54bc0065635 170: onsuccess: #599: 1: Success after binutils/gcc/linux/g [...] new ad9603a4abb 171: onsuccess: #600: 1: Success after binutils/gcc/linux/g [...] new 600d7d4f847 172: onsuccess: #601: 1: Success after binutils/gcc/linux/g [...] new 416cb56bf12 173: onsuccess: #602: 1: Success after binutils/gcc/linux/g [...] new c49e43cc2c7 174: onsuccess: #603: 1: Success after binutils/gcc/linux/g [...] new d4ec86cf97a 175: onsuccess: #604: 1: Success after binutils/gcc/glibc/g [...] new b2da90c2054 176: onsuccess: #605: 1: Success after binutils/gcc/linux/g [...] new 6537745051e 177: onsuccess: #606: 1: Success after binutils/gcc/linux/g [...] new 3bb02b5d760 178: onsuccess: #607: 1: Success after binutils/gcc/linux/g [...] new 18f4ea783cb 179: onsuccess: #608: 1: Success after binutils/gcc/linux/g [...] new d6da09311e2 180: onsuccess: #609: 1: Success after binutils/gcc/linux/g [...] new 1fc316a2e96 181: onsuccess: #610: 1: Success after binutils/gcc/linux/g [...] new bff7e6fec39 182: onsuccess: #611: 1: Success after binutils/gcc/linux/g [...] new 2f876a2787a 183: onsuccess: #612: 1: Success after binutils/gcc/glibc/g [...] new df2b54d3b27 184: onsuccess: #614: 1: Success after binutils/gcc/linux/g [...] new 51aecefbeb4 185: onsuccess: #615: 1: Success after binutils/gcc/linux/g [...] new 63b72d0aa68 186: onsuccess: #616: 1: Success after binutils/gcc/linux/g [...] new bb286927cdf 187: onsuccess: #617: 1: Success after binutils/gcc/linux/g [...] new 9469e33adb8 188: onsuccess: #618: 1: Success after binutils/gcc/linux/g [...] new 35652a37852 189: onsuccess: #619: 1: Success after binutils/gcc/linux/g [...] new f2cb3bbc948 190: onsuccess: #625: 1: Success after binutils/gcc/linux/g [...] new a83c5d5d01f 191: onsuccess: #626: 1: Success after binutils/gcc/linux/g [...] new d4001dd83bb 192: onsuccess: #627: 1: Success after binutils/gcc/linux/g [...] new 4b881173798 193: onsuccess: #1: 1: Success after binutils/gcc/linux/gli [...] new a11c13dbf4a 194: onsuccess: #2: 1: Success after binutils/gcc/linux/gdb [...] new afeac59bbaf 195: onsuccess: #3: 1: Success after binutils/gcc/linux/gli [...] new 7eb454d9359 196: onsuccess: #4: 1: Success after binutils/gcc/linux/gdb [...] new bb3c0189370 197: onsuccess: #5: 1: Success after binutils/gcc/linux/gli [...] new 2ed464622a0 198: onsuccess: #6: 1: Success after binutils/gcc/linux/gli [...] new 3906038d51e 199: onsuccess: #7: 1: Success after binutils/gcc/linux/gli [...] new 182a901fca1 200: onsuccess: #8: 1: Success after binutils/gcc/linux/gli [...] new 3dfd2845934 201: onsuccess: #9: 1: Success after binutils/gcc/linux/gdb [...] new 18fab158fdc 202: onsuccess: #10: 1: Success after binutils/gcc/linux/gd [...] new 95f844ad542 203: onsuccess: #11: 1: Success after binutils/gcc/linux/gd [...] new f708efd2474 204: onsuccess: #12: 1: Success after binutils/gcc/linux/gl [...] new 495a22e5a5e 205: onsuccess: #14: 1: Success after binutils/gcc/linux/gl [...] new 73e52606b30 206: onsuccess: #15: 1: Success after binutils/gcc/linux/gd [...] new 73a90d502e9 207: onsuccess: #16: 1: Success after binutils/gcc/linux/gl [...] new abae98ed674 208: onsuccess: #17: 1: Success after binutils/gcc/linux/gd [...] new 03d8dec96f3 209: onsuccess: #18: 1: Success after binutils/gcc/linux/gl [...] new 0d46e61ad4a 210: onsuccess: #19: 1: Success after binutils/gcc/linux/gl [...] new af8aefc04cd 211: onsuccess: #20: 1: Success after binutils/gcc/linux/gl [...] new ec9e3409c22 212: onsuccess: #23: 1: Success after gcc/linux/gdb: 40 commits new d4ed5c8cc5f 213: force: #24: 1: Success after binutils: 2 commits new fd592ba8e3b 214: force: #25: 1: Failure after gdb-13-branchpoint-1445-g [...] new e05e661a687 215: onsuccess: #26: 1: Success after binutils: 10 commits new fa8a288b49e 216: onsuccess: #27: 1: Success after binutils/gcc/linux/gd [...] new a89975fc6fe 217: onsuccess: #28: 1: Success after binutils/gcc/linux/gd [...] new 7d32e776a1f 218: onsuccess: #29: 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 (6720fdf801a) \ 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 -> 1792 bytes 02-prepare_abe/console.log.xz | Bin 2452 -> 2516 bytes 03-build_abe-binutils/console.log.xz | Bin 48744 -> 48868 bytes 04-build_abe-gcc/console.log.xz | Bin 236332 -> 234804 bytes 05-clean_sysroot/console.log.xz | Bin 316 -> 316 bytes 06-build_abe-linux/console.log.xz | Bin 9912 -> 8856 bytes 07-build_abe-glibc/console.log.xz | Bin 232884 -> 233584 bytes 08-build_abe-gdb/console.log.xz | Bin 47364 -> 47008 bytes 09-build_abe-dejagnu/console.log.xz | Bin 3820 -> 3788 bytes 10-build_abe-check_binutils/console.log.xz | Bin 2116 -> 2112 bytes 11-check_regression/console.log.xz | Bin 4760 -> 4704 bytes 11-check_regression/results.compare | 10 +++---- 11-check_regression/results.compare2 | 6 ++--- 12-update_baseline/console.log | 42 ++++++++++++++--------------- 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 62800 -> 62396 bytes sumfiles/binutils.sum | 2 +- sumfiles/gas.log.xz | Bin 100596 -> 100592 bytes sumfiles/gas.sum | 4 +-- sumfiles/ld.log.xz | Bin 132192 -> 132240 bytes sumfiles/ld.sum | 4 +-- 29 files changed, 58 insertions(+), 58 deletions(-)