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 155086031f9 220: onsuccess: #17: 1: Success after binutils/gcc/linux/gl [...] discards a27f7931661 219: onsuccess: #16: 1: Success after binutils/gcc/linux/gl [...] discards 6a62d93b99f 218: onsuccess: #15: 1: Success after binutils/gcc/linux/gl [...] discards bef38b070b5 217: onsuccess: #14: 1: Success after binutils/gcc/linux/gl [...] discards 2228ee3ccc8 216: onsuccess: #12: 1: Success after binutils/gcc/linux/gl [...] discards fe30e2af731 215: onsuccess: #11: 1: Success after binutils/gcc/linux/gd [...] discards 0729c9dd2ee 214: onsuccess: #10: 1: Success after binutils/gcc/linux/gd [...] discards 2349063dc4b 213: onsuccess: #9: 1: Success after binutils/gcc/linux/gli [...] discards 6fe857d06c7 212: onsuccess: #8: 1: Success after binutils/gcc/linux/gli [...] discards 0137c182009 211: onsuccess: #7: 1: Success after binutils/gcc/linux/gdb [...] discards 2c30dbd0b84 210: onsuccess: #6: 1: Success after binutils/gcc/linux/gli [...] discards dbca5f37dc0 209: onsuccess: #5: 1: Success after binutils/gcc/linux/gli [...] discards 333bdacf924 208: onsuccess: #4: 1: Success after binutils/gcc/linux/gli [...] discards 3513fc14b88 207: onsuccess: #3: 1: Success after binutils/gcc/linux/gdb [...] discards 61bc28819d8 206: onsuccess: #2: 1: Success after binutils/gcc/linux/gli [...] discards 5c1c866909b 205: onsuccess: #1: 1: Success after binutils/gcc/linux/gli [...] discards fa1f8ca049f 204: onsuccess: #672: 1: Success after binutils/gcc/linux/g [...] discards c8d122e89e2 203: onsuccess: #671: 1: Success after binutils/gcc/linux/g [...] discards ab43cfad7fd 202: onsuccess: #670: 1: Success after binutils/gcc/linux/g [...] discards 194f844c9a1 201: onsuccess: #664: 1: Success after binutils/gcc/glibc/g [...] discards 583ab404478 200: onsuccess: #663: 1: Success after binutils/gcc/linux/g [...] discards 346b3ae23a3 199: onsuccess: #662: 1: Success after binutils/gcc/linux/g [...] discards 9f8fb8358bb 198: onsuccess: #661: 1: Success after binutils/gcc/linux/g [...] discards 94392ec19d3 197: onsuccess: #660: 1: Success after binutils/gcc/linux/g [...] discards b94d21fee54 196: onsuccess: #659: 1: Success after binutils/gcc/linux/g [...] discards 2a8671627af 195: onsuccess: #657: 1: Success after binutils/gcc/linux/g [...] discards c78a686e12a 194: onsuccess: #656: 1: Success after binutils/gcc/linux/g [...] discards 16b25664e89 193: onsuccess: #655: 1: Success after binutils/gcc/linux/g [...] discards 906e3677d0c 192: onsuccess: #654: 1: Success after binutils/gcc/linux/g [...] discards 8dd77ad2552 191: onsuccess: #653: 1: Success after binutils/gcc/linux/g [...] discards 1b3b1977ade 190: onsuccess: #652: 1: Success after binutils/gcc/linux/g [...] discards f58eef350c2 189: onsuccess: #651: 1: Success after binutils/gcc/linux/g [...] discards 25cfceb35ab 188: onsuccess: #650: 1: Success after binutils/gcc/linux/g [...] discards 6785e861b55 187: onsuccess: #649: 1: Success after binutils/gcc/linux/g [...] discards 8753d754345 186: onsuccess: #648: 1: Success after binutils/gcc/linux/g [...] discards 255f9f74a2e 185: onsuccess: #647: 1: Success after binutils/gcc/linux/g [...] discards 4fa2e8254b3 184: onsuccess: #646: 1: Success after binutils/gcc/linux/g [...] discards 505fbe7d2a5 183: onsuccess: #645: 1: Success after binutils/gcc/gdb: 20 [...] discards 3a0dd644d28 182: onsuccess: #644: 1: Success after binutils/gcc/gdb: 30 [...] discards ee8c89cb74c 181: onsuccess: #643: 1: Success after binutils/gcc/linux/g [...] discards 76383c84cfd 180: onsuccess: #642: 1: Success after binutils/gcc/linux/g [...] discards 7b4691e55e3 179: onsuccess: #641: 1: Success after binutils/gcc/linux/g [...] discards d83a8fe5ec7 178: onsuccess: #640: 1: Success after binutils/gcc/linux/g [...] discards f41c3333cee 177: onsuccess: #639: 1: Success after binutils/gcc/linux/g [...] discards aab591cf5df 176: onsuccess: #638: 1: Success after binutils/gcc/linux/g [...] discards 5204ca8ba52 175: onsuccess: #637: 1: Success after binutils/gcc/linux/g [...] discards ac9984af711 174: onsuccess: #636: 1: Success after binutils/gcc/linux/g [...] discards b50776e0326 173: onsuccess: #635: 1: Success after binutils/gcc/linux/g [...] discards 3b9d785841b 172: onsuccess: #634: 1: Success after binutils/gcc/linux/g [...] discards dabcf90de07 171: onsuccess: #633: 1: Success after binutils/gcc/linux/g [...] discards 38e8f874b98 170: onsuccess: #632: 1: Success after binutils/gcc/linux/g [...] discards 796a473f317 169: onsuccess: #631: 1: Success after binutils/gcc/linux/g [...] discards 679fc8a58b7 168: onsuccess: #630: 1: Success after binutils/gcc/linux/g [...] discards 3cad2557940 167: onsuccess: #629: 1: Success after binutils/gcc/linux/g [...] discards 17a0ffbb4dd 166: onsuccess: #628: 1: Success after binutils/gcc/linux/g [...] discards 7e87e443470 165: onsuccess: #627: 1: Success after binutils/gcc/linux/g [...] discards 8c94a3ebee6 164: onsuccess: #626: 1: Success after binutils/gcc/linux/g [...] discards 9c1b8baf85f 163: onsuccess: #625: 1: Success after binutils/gcc/glibc/g [...] discards 8749e34df75 162: onsuccess: #624: 1: Success after linux: 10 commits discards 3915ad462dc 161: onsuccess: #623: 1: Success after glibc: 9 commits discards bded6cb177c 160: onsuccess: #621: 1: Success after gcc: 11 commits discards e6cc2352c8b 159: onsuccess: #620: 1: Success after binutils: 12 commits discards b6b17da4e1a 158: onsuccess: #618: 1: Success after binutils/gcc/linux/g [...] discards e63a02e8b1b 157: onsuccess: #617: 1: Success after binutils/gcc/linux/g [...] discards f1e0a624349 156: onsuccess: #616: 1: Success after binutils/gcc/linux/g [...] discards d1598da0fa1 155: onsuccess: #615: 1: Success after binutils/gcc/linux/g [...] discards 26e78c9ec1f 154: onsuccess: #614: 1: Success after binutils/gcc/gdb: 14 [...] discards f02dddfac25 153: onsuccess: #613: 1: Success after binutils/gcc/gdb: 40 [...] discards a579b75528e 152: onsuccess: #612: 1: Success after binutils/gcc/gdb: 11 [...] discards 6ef161d9b70 151: onsuccess: #611: 1: Success after binutils/gcc/linux/g [...] discards d4abe1d7bf0 150: onsuccess: #610: 1: Success after binutils/gcc/linux/g [...] discards 572d0ae14dd 149: onsuccess: #609: 1: Success after binutils/gcc/linux/g [...] discards 35fb69c46cc 148: onsuccess: #608: 1: Success after binutils/gcc/linux/g [...] discards a79bd57570b 147: onsuccess: #607: 1: Success after binutils/gcc/linux/g [...] discards 5aa210b658d 146: onsuccess: #606: 1: Success after binutils/gcc/linux/g [...] discards fe3f94dfbb1 145: onsuccess: #605: 1: Success after binutils/gcc/linux/g [...] discards ec60844263e 144: onsuccess: #604: 1: Success after binutils/gcc/gdb: 14 [...] discards 3947070511f 143: onsuccess: #603: 1: Success after binutils/gcc/linux/g [...] discards 20e2d191a75 142: onsuccess: #602: 1: Success after binutils/gcc/linux/g [...] discards 85cb926bbcf 141: onsuccess: #601: 1: Success after linux: 794 commits discards 77c06816b58 140: onsuccess: #600: 1: Success after gcc: 23 commits discards 292d9781203 139: onsuccess: #599: 1: Success after binutils: 10 commits discards 0e8f608f667 138: onsuccess: #597: 1: Success after binutils/gcc/linux/g [...] discards f657cd7c273 137: onsuccess: #596: 1: Success after binutils/gcc/linux/g [...] discards 5a6bc9a5a04 136: onsuccess: #595: 1: Success after binutils/gcc/linux/g [...] discards 7fe484fe112 135: onsuccess: #594: 1: Success after binutils/gcc/linux/g [...] discards 9c4936483c6 134: onsuccess: #593: 1: Success after binutils/gcc/linux/g [...] discards 8261c72a094 133: onsuccess: #592: 1: Success after binutils/gcc/linux/g [...] discards 5014af5cf86 132: onsuccess: #591: 1: Success after binutils/gcc/linux/g [...] discards 9e38e964ca3 131: onsuccess: #590: 1: Success after binutils/gcc/linux/g [...] discards ecfcd27af40 130: onsuccess: #589: 1: Success after binutils/gcc/linux/g [...] discards 0d53937b9f9 129: onsuccess: #588: 1: Success after linux: 4 commits discards 97b4ea0d1c3 128: onsuccess: #586: 1: Success after binutils: 22 commits discards 6deb1030c9f 127: onsuccess: #584: 1: Success after linux: 21 commits discards 8e25dc50225 126: onsuccess: #582: 1: Success after gcc: 9 commits discards dc9851cc02a 125: onsuccess: #581: 1: Success after binutils: 4 commits discards e020894a0f2 124: onsuccess: #579: 1: Success after binutils/gcc/linux/g [...] discards e755cba3c37 123: onsuccess: #578: 1: Success after binutils/gcc/linux/g [...] discards 7d99e77b5f1 122: onsuccess: #577: 1: Success after binutils/gcc/linux/g [...] discards e721e19a8e0 121: onsuccess: #576: 1: Success after binutils/gcc/linux/g [...] discards 8a553e51a44 120: onsuccess: #575: 1: Success after binutils/gcc/linux/g [...] new 9f5b87389c9 120: onsuccess: #575: 1: Success after binutils/gcc/linux/g [...] new 394db57dfe7 121: onsuccess: #576: 1: Success after binutils/gcc/linux/g [...] new 532751927de 122: onsuccess: #577: 1: Success after binutils/gcc/linux/g [...] new 525400d30f4 123: onsuccess: #578: 1: Success after binutils/gcc/linux/g [...] new f10bfcbb9e5 124: onsuccess: #579: 1: Success after binutils/gcc/linux/g [...] new 2bb7683c9bc 125: onsuccess: #581: 1: Success after binutils: 4 commits new 6293dcc56c4 126: onsuccess: #582: 1: Success after gcc: 9 commits new d906b0158a5 127: onsuccess: #584: 1: Success after linux: 21 commits new 8256a8402a1 128: onsuccess: #586: 1: Success after binutils: 22 commits new 037fdf281cd 129: onsuccess: #588: 1: Success after linux: 4 commits new 000b2ec6068 130: onsuccess: #589: 1: Success after binutils/gcc/linux/g [...] new cf019f47d42 131: onsuccess: #590: 1: Success after binutils/gcc/linux/g [...] new 92df92e83fd 132: onsuccess: #591: 1: Success after binutils/gcc/linux/g [...] new ce60fa72d85 133: onsuccess: #592: 1: Success after binutils/gcc/linux/g [...] new e6c4a214b86 134: onsuccess: #593: 1: Success after binutils/gcc/linux/g [...] new 58fad518146 135: onsuccess: #594: 1: Success after binutils/gcc/linux/g [...] new a3bd9f5751c 136: onsuccess: #595: 1: Success after binutils/gcc/linux/g [...] new 07d7cb9acec 137: onsuccess: #596: 1: Success after binutils/gcc/linux/g [...] new e4ea349fb82 138: onsuccess: #597: 1: Success after binutils/gcc/linux/g [...] new f1d643a4b4b 139: onsuccess: #599: 1: Success after binutils: 10 commits new 1061c4925e8 140: onsuccess: #600: 1: Success after gcc: 23 commits new 7535f6aa078 141: onsuccess: #601: 1: Success after linux: 794 commits new 166f90e48b3 142: onsuccess: #602: 1: Success after binutils/gcc/linux/g [...] new 4f627023b26 143: onsuccess: #603: 1: Success after binutils/gcc/linux/g [...] new 4622df71f6e 144: onsuccess: #604: 1: Success after binutils/gcc/gdb: 14 [...] new d182059e96e 145: onsuccess: #605: 1: Success after binutils/gcc/linux/g [...] new 5563d915481 146: onsuccess: #606: 1: Success after binutils/gcc/linux/g [...] new e9908c81abe 147: onsuccess: #607: 1: Success after binutils/gcc/linux/g [...] new 1024f55b5dd 148: onsuccess: #608: 1: Success after binutils/gcc/linux/g [...] new 730e56f2976 149: onsuccess: #609: 1: Success after binutils/gcc/linux/g [...] new d9af29bf50e 150: onsuccess: #610: 1: Success after binutils/gcc/linux/g [...] new b163930ed51 151: onsuccess: #611: 1: Success after binutils/gcc/linux/g [...] new 0a5d3b27652 152: onsuccess: #612: 1: Success after binutils/gcc/gdb: 11 [...] new c82375f6793 153: onsuccess: #613: 1: Success after binutils/gcc/gdb: 40 [...] new 5e5d733cbe4 154: onsuccess: #614: 1: Success after binutils/gcc/gdb: 14 [...] new b0ed6f94f73 155: onsuccess: #615: 1: Success after binutils/gcc/linux/g [...] new eea73e8d8dd 156: onsuccess: #616: 1: Success after binutils/gcc/linux/g [...] new 35b8b9c0ff7 157: onsuccess: #617: 1: Success after binutils/gcc/linux/g [...] new 7b477f79a75 158: onsuccess: #618: 1: Success after binutils/gcc/linux/g [...] new dbb330bbe1a 159: onsuccess: #620: 1: Success after binutils: 12 commits new 26d08e1bf37 160: onsuccess: #621: 1: Success after gcc: 11 commits new 2d98d9aed2b 161: onsuccess: #623: 1: Success after glibc: 9 commits new c8551931a10 162: onsuccess: #624: 1: Success after linux: 10 commits new c7c64594959 163: onsuccess: #625: 1: Success after binutils/gcc/glibc/g [...] new c3f69eb8674 164: onsuccess: #626: 1: Success after binutils/gcc/linux/g [...] new be1048c69af 165: onsuccess: #627: 1: Success after binutils/gcc/linux/g [...] new 12b697b6212 166: onsuccess: #628: 1: Success after binutils/gcc/linux/g [...] new af6880e8c39 167: onsuccess: #629: 1: Success after binutils/gcc/linux/g [...] new b858003a326 168: onsuccess: #630: 1: Success after binutils/gcc/linux/g [...] new 243335bb55e 169: onsuccess: #631: 1: Success after binutils/gcc/linux/g [...] new 57f47854f89 170: onsuccess: #632: 1: Success after binutils/gcc/linux/g [...] new 3eba04f43e6 171: onsuccess: #633: 1: Success after binutils/gcc/linux/g [...] new 8c40255fa7e 172: onsuccess: #634: 1: Success after binutils/gcc/linux/g [...] new 13de028dc00 173: onsuccess: #635: 1: Success after binutils/gcc/linux/g [...] new aeab41f8f9f 174: onsuccess: #636: 1: Success after binutils/gcc/linux/g [...] new ba871bc142d 175: onsuccess: #637: 1: Success after binutils/gcc/linux/g [...] new 2737e447fff 176: onsuccess: #638: 1: Success after binutils/gcc/linux/g [...] new b3b9420b87f 177: onsuccess: #639: 1: Success after binutils/gcc/linux/g [...] new c78af9a1bfd 178: onsuccess: #640: 1: Success after binutils/gcc/linux/g [...] new 6fe4dc6f08f 179: onsuccess: #641: 1: Success after binutils/gcc/linux/g [...] new 5baf0994bbf 180: onsuccess: #642: 1: Success after binutils/gcc/linux/g [...] new ea1b7845968 181: onsuccess: #643: 1: Success after binutils/gcc/linux/g [...] new 82717ee9b12 182: onsuccess: #644: 1: Success after binutils/gcc/gdb: 30 [...] new 15bd62006b0 183: onsuccess: #645: 1: Success after binutils/gcc/gdb: 20 [...] new 9234af26b57 184: onsuccess: #646: 1: Success after binutils/gcc/linux/g [...] new 5aaae497f2c 185: onsuccess: #647: 1: Success after binutils/gcc/linux/g [...] new 72122b3c279 186: onsuccess: #648: 1: Success after binutils/gcc/linux/g [...] new 20c0caaae18 187: onsuccess: #649: 1: Success after binutils/gcc/linux/g [...] new 20c083eb902 188: onsuccess: #650: 1: Success after binutils/gcc/linux/g [...] new d03a3e6c630 189: onsuccess: #651: 1: Success after binutils/gcc/linux/g [...] new e0082fe6392 190: onsuccess: #652: 1: Success after binutils/gcc/linux/g [...] new 8c0689b205f 191: onsuccess: #653: 1: Success after binutils/gcc/linux/g [...] new 98921baa001 192: onsuccess: #654: 1: Success after binutils/gcc/linux/g [...] new cdb7eac0d86 193: onsuccess: #655: 1: Success after binutils/gcc/linux/g [...] new 9b48762ca5b 194: onsuccess: #656: 1: Success after binutils/gcc/linux/g [...] new 13817fd698a 195: onsuccess: #657: 1: Success after binutils/gcc/linux/g [...] new 753e017e84e 196: onsuccess: #659: 1: Success after binutils/gcc/linux/g [...] new 9d6675601cb 197: onsuccess: #660: 1: Success after binutils/gcc/linux/g [...] new 6a3fb2cd5db 198: onsuccess: #661: 1: Success after binutils/gcc/linux/g [...] new 94e396de706 199: onsuccess: #662: 1: Success after binutils/gcc/linux/g [...] new 0533882953d 200: onsuccess: #663: 1: Success after binutils/gcc/linux/g [...] new 5280b69656a 201: onsuccess: #664: 1: Success after binutils/gcc/glibc/g [...] new 0e5d2e1b3d9 202: onsuccess: #670: 1: Success after binutils/gcc/linux/g [...] new 105ff778a0a 203: onsuccess: #671: 1: Success after binutils/gcc/linux/g [...] new 3ba4ec9e18d 204: onsuccess: #672: 1: Success after binutils/gcc/linux/g [...] new f6a6b7f0e85 205: onsuccess: #1: 1: Success after binutils/gcc/linux/gli [...] new 6c80135832b 206: onsuccess: #2: 1: Success after binutils/gcc/linux/gli [...] new 67e0e7df045 207: onsuccess: #3: 1: Success after binutils/gcc/linux/gdb [...] new 96bb61506ce 208: onsuccess: #4: 1: Success after binutils/gcc/linux/gli [...] new 4c199cde8c3 209: onsuccess: #5: 1: Success after binutils/gcc/linux/gli [...] new 56dec98c1fc 210: onsuccess: #6: 1: Success after binutils/gcc/linux/gli [...] new 42aefab7bee 211: onsuccess: #7: 1: Success after binutils/gcc/linux/gdb [...] new 264de065b07 212: onsuccess: #8: 1: Success after binutils/gcc/linux/gli [...] new c6ee421b86c 213: onsuccess: #9: 1: Success after binutils/gcc/linux/gli [...] new 84ee57739bf 214: onsuccess: #10: 1: Success after binutils/gcc/linux/gd [...] new 436edc4e589 215: onsuccess: #11: 1: Success after binutils/gcc/linux/gd [...] new 8fcaf951bc3 216: onsuccess: #12: 1: Success after binutils/gcc/linux/gl [...] new 56814ea7227 217: onsuccess: #14: 1: Success after binutils/gcc/linux/gl [...] new ec2bc3913bd 218: onsuccess: #15: 1: Success after binutils/gcc/linux/gl [...] new c5c5af2a2e0 219: onsuccess: #16: 1: Success after binutils/gcc/linux/gl [...] new 0865a2574ea 220: onsuccess: #17: 1: Success after binutils/gcc/linux/gl [...] new 9eba0786858 221: onsuccess: #18: 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 (155086031f9) \ 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 1748 -> 1756 bytes 02-prepare_abe/console.log.xz | Bin 2772 -> 2772 bytes 03-build_abe-binutils/console.log.xz | Bin 52312 -> 52840 bytes 04-build_abe-gcc/console.log.xz | Bin 236040 -> 237428 bytes 05-clean_sysroot/console.log.xz | Bin 316 -> 316 bytes 06-build_abe-linux/console.log.xz | Bin 8780 -> 8520 bytes 07-build_abe-glibc/console.log.xz | Bin 236308 -> 235572 bytes 08-build_abe-gdb/console.log.xz | Bin 51032 -> 51164 bytes 09-build_abe-dejagnu/console.log.xz | Bin 3764 -> 3748 bytes 10-build_abe-check_gcc/console.log.xz | Bin 2560 -> 3812 bytes 11-check_regression/console.log.xz | Bin 7508 -> 5884 bytes 11-check_regression/extra-bisect-params | 1 - 11-check_regression/fails.sum | 8 - 11-check_regression/mail-body.txt | 34 ++-- 11-check_regression/results.compare | 27 +-- 11-check_regression/results.compare2 | 237 +--------------------- 11-check_regression/results.regressions | 28 --- 12-update_baseline/console.log | 66 +++--- 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 | 36 ++-- mail/mail-subject.txt | 2 +- manifest.sh | 32 +-- results | 28 --- sumfiles/g++.log.xz | Bin 2906556 -> 2907112 bytes sumfiles/g++.sum | 106 +++++----- sumfiles/gcc.log.xz | Bin 2482004 -> 2495892 bytes sumfiles/gcc.sum | 342 ++++++++++++++++---------------- sumfiles/gfortran.log.xz | Bin 950240 -> 952564 bytes sumfiles/gfortran.sum | 38 ++-- sumfiles/libatomic.log.xz | Bin 2276 -> 2276 bytes sumfiles/libatomic.sum | 4 +- sumfiles/libgomp.log.xz | Bin 233940 -> 233952 bytes sumfiles/libgomp.sum | 16 +- sumfiles/libitm.log.xz | Bin 2692 -> 2692 bytes sumfiles/libitm.sum | 6 +- sumfiles/libstdc++.log.xz | Bin 468620 -> 476848 bytes sumfiles/libstdc++.sum | 8 +- 42 files changed, 371 insertions(+), 660 deletions(-) delete mode 100644 11-check_regression/extra-bisect-params delete mode 100644 11-check_regression/fails.sum delete mode 100644 11-check_regression/results.regressions