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

discards 9eba0786858 221: onsuccess: #18: 1: Success after binutils/gcc/linux/gd [...] discards 0865a2574ea 220: onsuccess: #17: 1: Success after binutils/gcc/linux/gl [...] discards c5c5af2a2e0 219: onsuccess: #16: 1: Success after binutils/gcc/linux/gl [...] discards ec2bc3913bd 218: onsuccess: #15: 1: Success after binutils/gcc/linux/gl [...] discards 56814ea7227 217: onsuccess: #14: 1: Success after binutils/gcc/linux/gl [...] discards 8fcaf951bc3 216: onsuccess: #12: 1: Success after binutils/gcc/linux/gl [...] discards 436edc4e589 215: onsuccess: #11: 1: Success after binutils/gcc/linux/gd [...] discards 84ee57739bf 214: onsuccess: #10: 1: Success after binutils/gcc/linux/gd [...] discards c6ee421b86c 213: onsuccess: #9: 1: Success after binutils/gcc/linux/gli [...] discards 264de065b07 212: onsuccess: #8: 1: Success after binutils/gcc/linux/gli [...] discards 42aefab7bee 211: onsuccess: #7: 1: Success after binutils/gcc/linux/gdb [...] discards 56dec98c1fc 210: onsuccess: #6: 1: Success after binutils/gcc/linux/gli [...] discards 4c199cde8c3 209: onsuccess: #5: 1: Success after binutils/gcc/linux/gli [...] discards 96bb61506ce 208: onsuccess: #4: 1: Success after binutils/gcc/linux/gli [...] discards 67e0e7df045 207: onsuccess: #3: 1: Success after binutils/gcc/linux/gdb [...] discards 6c80135832b 206: onsuccess: #2: 1: Success after binutils/gcc/linux/gli [...] discards f6a6b7f0e85 205: onsuccess: #1: 1: Success after binutils/gcc/linux/gli [...] discards 3ba4ec9e18d 204: onsuccess: #672: 1: Success after binutils/gcc/linux/g [...] discards 105ff778a0a 203: onsuccess: #671: 1: Success after binutils/gcc/linux/g [...] discards 0e5d2e1b3d9 202: onsuccess: #670: 1: Success after binutils/gcc/linux/g [...] discards 5280b69656a 201: onsuccess: #664: 1: Success after binutils/gcc/glibc/g [...] discards 0533882953d 200: onsuccess: #663: 1: Success after binutils/gcc/linux/g [...] discards 94e396de706 199: onsuccess: #662: 1: Success after binutils/gcc/linux/g [...] discards 6a3fb2cd5db 198: onsuccess: #661: 1: Success after binutils/gcc/linux/g [...] discards 9d6675601cb 197: onsuccess: #660: 1: Success after binutils/gcc/linux/g [...] discards 753e017e84e 196: onsuccess: #659: 1: Success after binutils/gcc/linux/g [...] discards 13817fd698a 195: onsuccess: #657: 1: Success after binutils/gcc/linux/g [...] discards 9b48762ca5b 194: onsuccess: #656: 1: Success after binutils/gcc/linux/g [...] discards cdb7eac0d86 193: onsuccess: #655: 1: Success after binutils/gcc/linux/g [...] discards 98921baa001 192: onsuccess: #654: 1: Success after binutils/gcc/linux/g [...] discards 8c0689b205f 191: onsuccess: #653: 1: Success after binutils/gcc/linux/g [...] discards e0082fe6392 190: onsuccess: #652: 1: Success after binutils/gcc/linux/g [...] discards d03a3e6c630 189: onsuccess: #651: 1: Success after binutils/gcc/linux/g [...] discards 20c083eb902 188: onsuccess: #650: 1: Success after binutils/gcc/linux/g [...] discards 20c0caaae18 187: onsuccess: #649: 1: Success after binutils/gcc/linux/g [...] discards 72122b3c279 186: onsuccess: #648: 1: Success after binutils/gcc/linux/g [...] discards 5aaae497f2c 185: onsuccess: #647: 1: Success after binutils/gcc/linux/g [...] discards 9234af26b57 184: onsuccess: #646: 1: Success after binutils/gcc/linux/g [...] discards 15bd62006b0 183: onsuccess: #645: 1: Success after binutils/gcc/gdb: 20 [...] discards 82717ee9b12 182: onsuccess: #644: 1: Success after binutils/gcc/gdb: 30 [...] discards ea1b7845968 181: onsuccess: #643: 1: Success after binutils/gcc/linux/g [...] discards 5baf0994bbf 180: onsuccess: #642: 1: Success after binutils/gcc/linux/g [...] discards 6fe4dc6f08f 179: onsuccess: #641: 1: Success after binutils/gcc/linux/g [...] discards c78af9a1bfd 178: onsuccess: #640: 1: Success after binutils/gcc/linux/g [...] discards b3b9420b87f 177: onsuccess: #639: 1: Success after binutils/gcc/linux/g [...] discards 2737e447fff 176: onsuccess: #638: 1: Success after binutils/gcc/linux/g [...] discards ba871bc142d 175: onsuccess: #637: 1: Success after binutils/gcc/linux/g [...] discards aeab41f8f9f 174: onsuccess: #636: 1: Success after binutils/gcc/linux/g [...] discards 13de028dc00 173: onsuccess: #635: 1: Success after binutils/gcc/linux/g [...] discards 8c40255fa7e 172: onsuccess: #634: 1: Success after binutils/gcc/linux/g [...] discards 3eba04f43e6 171: onsuccess: #633: 1: Success after binutils/gcc/linux/g [...] discards 57f47854f89 170: onsuccess: #632: 1: Success after binutils/gcc/linux/g [...] discards 243335bb55e 169: onsuccess: #631: 1: Success after binutils/gcc/linux/g [...] discards b858003a326 168: onsuccess: #630: 1: Success after binutils/gcc/linux/g [...] discards af6880e8c39 167: onsuccess: #629: 1: Success after binutils/gcc/linux/g [...] discards 12b697b6212 166: onsuccess: #628: 1: Success after binutils/gcc/linux/g [...] discards be1048c69af 165: onsuccess: #627: 1: Success after binutils/gcc/linux/g [...] discards c3f69eb8674 164: onsuccess: #626: 1: Success after binutils/gcc/linux/g [...] discards c7c64594959 163: onsuccess: #625: 1: Success after binutils/gcc/glibc/g [...] discards c8551931a10 162: onsuccess: #624: 1: Success after linux: 10 commits discards 2d98d9aed2b 161: onsuccess: #623: 1: Success after glibc: 9 commits discards 26d08e1bf37 160: onsuccess: #621: 1: Success after gcc: 11 commits discards dbb330bbe1a 159: onsuccess: #620: 1: Success after binutils: 12 commits discards 7b477f79a75 158: onsuccess: #618: 1: Success after binutils/gcc/linux/g [...] discards 35b8b9c0ff7 157: onsuccess: #617: 1: Success after binutils/gcc/linux/g [...] discards eea73e8d8dd 156: onsuccess: #616: 1: Success after binutils/gcc/linux/g [...] discards b0ed6f94f73 155: onsuccess: #615: 1: Success after binutils/gcc/linux/g [...] discards 5e5d733cbe4 154: onsuccess: #614: 1: Success after binutils/gcc/gdb: 14 [...] discards c82375f6793 153: onsuccess: #613: 1: Success after binutils/gcc/gdb: 40 [...] discards 0a5d3b27652 152: onsuccess: #612: 1: Success after binutils/gcc/gdb: 11 [...] discards b163930ed51 151: onsuccess: #611: 1: Success after binutils/gcc/linux/g [...] discards d9af29bf50e 150: onsuccess: #610: 1: Success after binutils/gcc/linux/g [...] discards 730e56f2976 149: onsuccess: #609: 1: Success after binutils/gcc/linux/g [...] discards 1024f55b5dd 148: onsuccess: #608: 1: Success after binutils/gcc/linux/g [...] discards e9908c81abe 147: onsuccess: #607: 1: Success after binutils/gcc/linux/g [...] discards 5563d915481 146: onsuccess: #606: 1: Success after binutils/gcc/linux/g [...] discards d182059e96e 145: onsuccess: #605: 1: Success after binutils/gcc/linux/g [...] discards 4622df71f6e 144: onsuccess: #604: 1: Success after binutils/gcc/gdb: 14 [...] discards 4f627023b26 143: onsuccess: #603: 1: Success after binutils/gcc/linux/g [...] discards 166f90e48b3 142: onsuccess: #602: 1: Success after binutils/gcc/linux/g [...] discards 7535f6aa078 141: onsuccess: #601: 1: Success after linux: 794 commits discards 1061c4925e8 140: onsuccess: #600: 1: Success after gcc: 23 commits discards f1d643a4b4b 139: onsuccess: #599: 1: Success after binutils: 10 commits discards e4ea349fb82 138: onsuccess: #597: 1: Success after binutils/gcc/linux/g [...] discards 07d7cb9acec 137: onsuccess: #596: 1: Success after binutils/gcc/linux/g [...] discards a3bd9f5751c 136: onsuccess: #595: 1: Success after binutils/gcc/linux/g [...] discards 58fad518146 135: onsuccess: #594: 1: Success after binutils/gcc/linux/g [...] discards e6c4a214b86 134: onsuccess: #593: 1: Success after binutils/gcc/linux/g [...] discards ce60fa72d85 133: onsuccess: #592: 1: Success after binutils/gcc/linux/g [...] discards 92df92e83fd 132: onsuccess: #591: 1: Success after binutils/gcc/linux/g [...] discards cf019f47d42 131: onsuccess: #590: 1: Success after binutils/gcc/linux/g [...] discards 000b2ec6068 130: onsuccess: #589: 1: Success after binutils/gcc/linux/g [...] discards 037fdf281cd 129: onsuccess: #588: 1: Success after linux: 4 commits discards 8256a8402a1 128: onsuccess: #586: 1: Success after binutils: 22 commits discards d906b0158a5 127: onsuccess: #584: 1: Success after linux: 21 commits discards 6293dcc56c4 126: onsuccess: #582: 1: Success after gcc: 9 commits discards 2bb7683c9bc 125: onsuccess: #581: 1: Success after binutils: 4 commits discards f10bfcbb9e5 124: onsuccess: #579: 1: Success after binutils/gcc/linux/g [...] discards 525400d30f4 123: onsuccess: #578: 1: Success after binutils/gcc/linux/g [...] discards 532751927de 122: onsuccess: #577: 1: Success after binutils/gcc/linux/g [...] discards 394db57dfe7 121: onsuccess: #576: 1: Success after binutils/gcc/linux/g [...] new f71328cfd35 121: onsuccess: #576: 1: Success after binutils/gcc/linux/g [...] new 7264176f163 122: onsuccess: #577: 1: Success after binutils/gcc/linux/g [...] new 1e7fc9e02cb 123: onsuccess: #578: 1: Success after binutils/gcc/linux/g [...] new 2e86a033bcf 124: onsuccess: #579: 1: Success after binutils/gcc/linux/g [...] new 4a3410132f5 125: onsuccess: #581: 1: Success after binutils: 4 commits new 07acbbbc987 126: onsuccess: #582: 1: Success after gcc: 9 commits new c2e1657319d 127: onsuccess: #584: 1: Success after linux: 21 commits new 445afa3e651 128: onsuccess: #586: 1: Success after binutils: 22 commits new e988bec1365 129: onsuccess: #588: 1: Success after linux: 4 commits new c6d681c3326 130: onsuccess: #589: 1: Success after binutils/gcc/linux/g [...] new 83bc4a5032c 131: onsuccess: #590: 1: Success after binutils/gcc/linux/g [...] new 2afa1d5e88b 132: onsuccess: #591: 1: Success after binutils/gcc/linux/g [...] new 135d7c76b26 133: onsuccess: #592: 1: Success after binutils/gcc/linux/g [...] new cebe12c29ff 134: onsuccess: #593: 1: Success after binutils/gcc/linux/g [...] new 296387481be 135: onsuccess: #594: 1: Success after binutils/gcc/linux/g [...] new c23003abaad 136: onsuccess: #595: 1: Success after binutils/gcc/linux/g [...] new 35a9cf9725c 137: onsuccess: #596: 1: Success after binutils/gcc/linux/g [...] new 64e42c5f4b2 138: onsuccess: #597: 1: Success after binutils/gcc/linux/g [...] new 8ddaa780728 139: onsuccess: #599: 1: Success after binutils: 10 commits new c108a1b82a2 140: onsuccess: #600: 1: Success after gcc: 23 commits new 5d4b8973bf8 141: onsuccess: #601: 1: Success after linux: 794 commits new 9a7635192e1 142: onsuccess: #602: 1: Success after binutils/gcc/linux/g [...] new 6c90840b02e 143: onsuccess: #603: 1: Success after binutils/gcc/linux/g [...] new 54e9fb21d47 144: onsuccess: #604: 1: Success after binutils/gcc/gdb: 14 [...] new 624b5d70bd7 145: onsuccess: #605: 1: Success after binutils/gcc/linux/g [...] new 03af869af42 146: onsuccess: #606: 1: Success after binutils/gcc/linux/g [...] new 14b6e1bad51 147: onsuccess: #607: 1: Success after binutils/gcc/linux/g [...] new 22e103e2da3 148: onsuccess: #608: 1: Success after binutils/gcc/linux/g [...] new a4fa651c870 149: onsuccess: #609: 1: Success after binutils/gcc/linux/g [...] new 6b82e20f299 150: onsuccess: #610: 1: Success after binutils/gcc/linux/g [...] new 2d96c373717 151: onsuccess: #611: 1: Success after binutils/gcc/linux/g [...] new 8bfc35e04b1 152: onsuccess: #612: 1: Success after binutils/gcc/gdb: 11 [...] new 6d6d8c41ca8 153: onsuccess: #613: 1: Success after binutils/gcc/gdb: 40 [...] new ab229be65e3 154: onsuccess: #614: 1: Success after binutils/gcc/gdb: 14 [...] new 68851d6d643 155: onsuccess: #615: 1: Success after binutils/gcc/linux/g [...] new a5821473bfe 156: onsuccess: #616: 1: Success after binutils/gcc/linux/g [...] new 489118db965 157: onsuccess: #617: 1: Success after binutils/gcc/linux/g [...] new 16a44a69156 158: onsuccess: #618: 1: Success after binutils/gcc/linux/g [...] new 149a95f9ed2 159: onsuccess: #620: 1: Success after binutils: 12 commits new 1f0d67be324 160: onsuccess: #621: 1: Success after gcc: 11 commits new 1e23a0b19ba 161: onsuccess: #623: 1: Success after glibc: 9 commits new 544750e9a7c 162: onsuccess: #624: 1: Success after linux: 10 commits new 4b82226050a 163: onsuccess: #625: 1: Success after binutils/gcc/glibc/g [...] new a04262bbaee 164: onsuccess: #626: 1: Success after binutils/gcc/linux/g [...] new c6555379db6 165: onsuccess: #627: 1: Success after binutils/gcc/linux/g [...] new 095b1bff3e2 166: onsuccess: #628: 1: Success after binutils/gcc/linux/g [...] new 36e30fddacd 167: onsuccess: #629: 1: Success after binutils/gcc/linux/g [...] new b670559f634 168: onsuccess: #630: 1: Success after binutils/gcc/linux/g [...] new 3860f2d1980 169: onsuccess: #631: 1: Success after binutils/gcc/linux/g [...] new fc7f0748d18 170: onsuccess: #632: 1: Success after binutils/gcc/linux/g [...] new 7ac02325c5a 171: onsuccess: #633: 1: Success after binutils/gcc/linux/g [...] new d9a316f1d7e 172: onsuccess: #634: 1: Success after binutils/gcc/linux/g [...] new 450349bec94 173: onsuccess: #635: 1: Success after binutils/gcc/linux/g [...] new 903f4f0abdc 174: onsuccess: #636: 1: Success after binutils/gcc/linux/g [...] new 6e09665fef9 175: onsuccess: #637: 1: Success after binutils/gcc/linux/g [...] new 180fdff387a 176: onsuccess: #638: 1: Success after binutils/gcc/linux/g [...] new 76e631fb684 177: onsuccess: #639: 1: Success after binutils/gcc/linux/g [...] new d8efbb62d5a 178: onsuccess: #640: 1: Success after binutils/gcc/linux/g [...] new 8942872ba94 179: onsuccess: #641: 1: Success after binutils/gcc/linux/g [...] new 61e89d003a2 180: onsuccess: #642: 1: Success after binutils/gcc/linux/g [...] new 3eeed93ec1d 181: onsuccess: #643: 1: Success after binutils/gcc/linux/g [...] new 8ff534c29dc 182: onsuccess: #644: 1: Success after binutils/gcc/gdb: 30 [...] new 6e0eaaad83c 183: onsuccess: #645: 1: Success after binutils/gcc/gdb: 20 [...] new 2e062922ecf 184: onsuccess: #646: 1: Success after binutils/gcc/linux/g [...] new 4caabf32173 185: onsuccess: #647: 1: Success after binutils/gcc/linux/g [...] new 24d6734a657 186: onsuccess: #648: 1: Success after binutils/gcc/linux/g [...] new b951b694db1 187: onsuccess: #649: 1: Success after binutils/gcc/linux/g [...] new 1db3feedc8b 188: onsuccess: #650: 1: Success after binutils/gcc/linux/g [...] new 95c582ee6b4 189: onsuccess: #651: 1: Success after binutils/gcc/linux/g [...] new 2a2a44bcd97 190: onsuccess: #652: 1: Success after binutils/gcc/linux/g [...] new c1300bcf7bc 191: onsuccess: #653: 1: Success after binutils/gcc/linux/g [...] new 70dd5a71a2b 192: onsuccess: #654: 1: Success after binutils/gcc/linux/g [...] new 5c20cfd0a05 193: onsuccess: #655: 1: Success after binutils/gcc/linux/g [...] new 7c7ffe9e1f7 194: onsuccess: #656: 1: Success after binutils/gcc/linux/g [...] new 9246f817db7 195: onsuccess: #657: 1: Success after binutils/gcc/linux/g [...] new 5b0a25dd873 196: onsuccess: #659: 1: Success after binutils/gcc/linux/g [...] new eea0b6550aa 197: onsuccess: #660: 1: Success after binutils/gcc/linux/g [...] new 4b11cb36701 198: onsuccess: #661: 1: Success after binutils/gcc/linux/g [...] new 20789c535d5 199: onsuccess: #662: 1: Success after binutils/gcc/linux/g [...] new 677aae9325b 200: onsuccess: #663: 1: Success after binutils/gcc/linux/g [...] new f2a84b53c56 201: onsuccess: #664: 1: Success after binutils/gcc/glibc/g [...] new 74e0ef15e76 202: onsuccess: #670: 1: Success after binutils/gcc/linux/g [...] new d9a5d4b77d5 203: onsuccess: #671: 1: Success after binutils/gcc/linux/g [...] new 7b7eb8abe74 204: onsuccess: #672: 1: Success after binutils/gcc/linux/g [...] new c4438505ab7 205: onsuccess: #1: 1: Success after binutils/gcc/linux/gli [...] new 81283c18878 206: onsuccess: #2: 1: Success after binutils/gcc/linux/gli [...] new 8099d95243a 207: onsuccess: #3: 1: Success after binutils/gcc/linux/gdb [...] new 7c4fa887058 208: onsuccess: #4: 1: Success after binutils/gcc/linux/gli [...] new 13f2ca4d4d0 209: onsuccess: #5: 1: Success after binutils/gcc/linux/gli [...] new 57c898cd113 210: onsuccess: #6: 1: Success after binutils/gcc/linux/gli [...] new 7dc84be3176 211: onsuccess: #7: 1: Success after binutils/gcc/linux/gdb [...] new f73c4710bc8 212: onsuccess: #8: 1: Success after binutils/gcc/linux/gli [...] new 618931e195e 213: onsuccess: #9: 1: Success after binutils/gcc/linux/gli [...] new 9ec2df28faf 214: onsuccess: #10: 1: Success after binutils/gcc/linux/gd [...] new af8f7ff3bca 215: onsuccess: #11: 1: Success after binutils/gcc/linux/gd [...] new 8bdcc52f6d5 216: onsuccess: #12: 1: Success after binutils/gcc/linux/gl [...] new 1b4e9821d6a 217: onsuccess: #14: 1: Success after binutils/gcc/linux/gl [...] new b141cb3f372 218: onsuccess: #15: 1: Success after binutils/gcc/linux/gl [...] new b07e6959cbd 219: onsuccess: #16: 1: Success after binutils/gcc/linux/gl [...] new 47e746f7ebf 220: onsuccess: #17: 1: Success after binutils/gcc/linux/gl [...] new ed2f4f05971 221: onsuccess: #18: 1: Success after binutils/gcc/linux/gd [...] new 89e82856564 222: onsuccess: #19: 1: Success after binutils/gcc/linux/gl [...]

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 (9eba0786858) \ N -- N -- N refs/heads/linaro-local/ci/tcwg_gnu_native_check_gcc/mas [...]

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 1756 -> 1764 bytes 02-prepare_abe/console.log.xz | Bin 2772 -> 2780 bytes 03-build_abe-binutils/console.log.xz | Bin 52840 -> 52644 bytes 04-build_abe-gcc/console.log.xz | Bin 237428 -> 238228 bytes 05-clean_sysroot/console.log.xz | Bin 316 -> 316 bytes 06-build_abe-linux/console.log.xz | Bin 8520 -> 8352 bytes 07-build_abe-glibc/console.log.xz | Bin 235572 -> 237316 bytes 08-build_abe-gdb/console.log.xz | Bin 51164 -> 51332 bytes 09-build_abe-dejagnu/console.log.xz | Bin 3748 -> 3832 bytes 10-build_abe-check_gcc/console.log.xz | Bin 3812 -> 2664 bytes 11-check_regression/console.log.xz | Bin 5884 -> 6956 bytes 11-check_regression/extra-bisect-params | 1 + 11-check_regression/fails.sum | 6 + 11-check_regression/mail-body.txt | 54 +++-- 11-check_regression/results.compare | 25 ++- 11-check_regression/results.compare2 | 68 +++++- 11-check_regression/results.regressions | 26 +++ 12-update_baseline/console.log | 64 +++--- 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 | 56 +++-- mail/mail-subject.txt | 2 +- manifest.sh | 38 ++-- results | 26 +++ sumfiles/g++.log.xz | Bin 2907112 -> 2888232 bytes sumfiles/g++.sum | 119 ++++++----- sumfiles/gcc.log.xz | Bin 2495892 -> 2482528 bytes sumfiles/gcc.sum | 363 +++++++++++++++++--------------- sumfiles/gfortran.log.xz | Bin 952564 -> 957196 bytes sumfiles/gfortran.sum | 38 ++-- sumfiles/libatomic.log.xz | Bin 2276 -> 2276 bytes sumfiles/libatomic.sum | 4 +- sumfiles/libgomp.log.xz | Bin 233952 -> 234256 bytes sumfiles/libgomp.sum | 16 +- sumfiles/libitm.log.xz | Bin 2692 -> 2696 bytes sumfiles/libitm.sum | 6 +- sumfiles/libstdc++.log.xz | Bin 476848 -> 469440 bytes sumfiles/libstdc++.sum | 8 +- 43 files changed, 535 insertions(+), 399 deletions(-) create mode 100644 11-check_regression/extra-bisect-params create mode 100644 11-check_regression/fails.sum create mode 100644 11-check_regression/results.regressions