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 89e82856564 222: onsuccess: #19: 1: Success after binutils/gcc/linux/gl [...] discards ed2f4f05971 221: onsuccess: #18: 1: Success after binutils/gcc/linux/gd [...] discards 47e746f7ebf 220: onsuccess: #17: 1: Success after binutils/gcc/linux/gl [...] discards b07e6959cbd 219: onsuccess: #16: 1: Success after binutils/gcc/linux/gl [...] discards b141cb3f372 218: onsuccess: #15: 1: Success after binutils/gcc/linux/gl [...] discards 1b4e9821d6a 217: onsuccess: #14: 1: Success after binutils/gcc/linux/gl [...] discards 8bdcc52f6d5 216: onsuccess: #12: 1: Success after binutils/gcc/linux/gl [...] discards af8f7ff3bca 215: onsuccess: #11: 1: Success after binutils/gcc/linux/gd [...] discards 9ec2df28faf 214: onsuccess: #10: 1: Success after binutils/gcc/linux/gd [...] discards 618931e195e 213: onsuccess: #9: 1: Success after binutils/gcc/linux/gli [...] discards f73c4710bc8 212: onsuccess: #8: 1: Success after binutils/gcc/linux/gli [...] discards 7dc84be3176 211: onsuccess: #7: 1: Success after binutils/gcc/linux/gdb [...] discards 57c898cd113 210: onsuccess: #6: 1: Success after binutils/gcc/linux/gli [...] discards 13f2ca4d4d0 209: onsuccess: #5: 1: Success after binutils/gcc/linux/gli [...] discards 7c4fa887058 208: onsuccess: #4: 1: Success after binutils/gcc/linux/gli [...] discards 8099d95243a 207: onsuccess: #3: 1: Success after binutils/gcc/linux/gdb [...] discards 81283c18878 206: onsuccess: #2: 1: Success after binutils/gcc/linux/gli [...] discards c4438505ab7 205: onsuccess: #1: 1: Success after binutils/gcc/linux/gli [...] discards 7b7eb8abe74 204: onsuccess: #672: 1: Success after binutils/gcc/linux/g [...] discards d9a5d4b77d5 203: onsuccess: #671: 1: Success after binutils/gcc/linux/g [...] discards 74e0ef15e76 202: onsuccess: #670: 1: Success after binutils/gcc/linux/g [...] discards f2a84b53c56 201: onsuccess: #664: 1: Success after binutils/gcc/glibc/g [...] discards 677aae9325b 200: onsuccess: #663: 1: Success after binutils/gcc/linux/g [...] discards 20789c535d5 199: onsuccess: #662: 1: Success after binutils/gcc/linux/g [...] discards 4b11cb36701 198: onsuccess: #661: 1: Success after binutils/gcc/linux/g [...] discards eea0b6550aa 197: onsuccess: #660: 1: Success after binutils/gcc/linux/g [...] discards 5b0a25dd873 196: onsuccess: #659: 1: Success after binutils/gcc/linux/g [...] discards 9246f817db7 195: onsuccess: #657: 1: Success after binutils/gcc/linux/g [...] discards 7c7ffe9e1f7 194: onsuccess: #656: 1: Success after binutils/gcc/linux/g [...] discards 5c20cfd0a05 193: onsuccess: #655: 1: Success after binutils/gcc/linux/g [...] discards 70dd5a71a2b 192: onsuccess: #654: 1: Success after binutils/gcc/linux/g [...] discards c1300bcf7bc 191: onsuccess: #653: 1: Success after binutils/gcc/linux/g [...] discards 2a2a44bcd97 190: onsuccess: #652: 1: Success after binutils/gcc/linux/g [...] discards 95c582ee6b4 189: onsuccess: #651: 1: Success after binutils/gcc/linux/g [...] discards 1db3feedc8b 188: onsuccess: #650: 1: Success after binutils/gcc/linux/g [...] discards b951b694db1 187: onsuccess: #649: 1: Success after binutils/gcc/linux/g [...] discards 24d6734a657 186: onsuccess: #648: 1: Success after binutils/gcc/linux/g [...] discards 4caabf32173 185: onsuccess: #647: 1: Success after binutils/gcc/linux/g [...] discards 2e062922ecf 184: onsuccess: #646: 1: Success after binutils/gcc/linux/g [...] discards 6e0eaaad83c 183: onsuccess: #645: 1: Success after binutils/gcc/gdb: 20 [...] discards 8ff534c29dc 182: onsuccess: #644: 1: Success after binutils/gcc/gdb: 30 [...] discards 3eeed93ec1d 181: onsuccess: #643: 1: Success after binutils/gcc/linux/g [...] discards 61e89d003a2 180: onsuccess: #642: 1: Success after binutils/gcc/linux/g [...] discards 8942872ba94 179: onsuccess: #641: 1: Success after binutils/gcc/linux/g [...] discards d8efbb62d5a 178: onsuccess: #640: 1: Success after binutils/gcc/linux/g [...] discards 76e631fb684 177: onsuccess: #639: 1: Success after binutils/gcc/linux/g [...] discards 180fdff387a 176: onsuccess: #638: 1: Success after binutils/gcc/linux/g [...] discards 6e09665fef9 175: onsuccess: #637: 1: Success after binutils/gcc/linux/g [...] discards 903f4f0abdc 174: onsuccess: #636: 1: Success after binutils/gcc/linux/g [...] discards 450349bec94 173: onsuccess: #635: 1: Success after binutils/gcc/linux/g [...] discards d9a316f1d7e 172: onsuccess: #634: 1: Success after binutils/gcc/linux/g [...] discards 7ac02325c5a 171: onsuccess: #633: 1: Success after binutils/gcc/linux/g [...] discards fc7f0748d18 170: onsuccess: #632: 1: Success after binutils/gcc/linux/g [...] discards 3860f2d1980 169: onsuccess: #631: 1: Success after binutils/gcc/linux/g [...] discards b670559f634 168: onsuccess: #630: 1: Success after binutils/gcc/linux/g [...] discards 36e30fddacd 167: onsuccess: #629: 1: Success after binutils/gcc/linux/g [...] discards 095b1bff3e2 166: onsuccess: #628: 1: Success after binutils/gcc/linux/g [...] discards c6555379db6 165: onsuccess: #627: 1: Success after binutils/gcc/linux/g [...] discards a04262bbaee 164: onsuccess: #626: 1: Success after binutils/gcc/linux/g [...] discards 4b82226050a 163: onsuccess: #625: 1: Success after binutils/gcc/glibc/g [...] discards 544750e9a7c 162: onsuccess: #624: 1: Success after linux: 10 commits discards 1e23a0b19ba 161: onsuccess: #623: 1: Success after glibc: 9 commits discards 1f0d67be324 160: onsuccess: #621: 1: Success after gcc: 11 commits discards 149a95f9ed2 159: onsuccess: #620: 1: Success after binutils: 12 commits discards 16a44a69156 158: onsuccess: #618: 1: Success after binutils/gcc/linux/g [...] discards 489118db965 157: onsuccess: #617: 1: Success after binutils/gcc/linux/g [...] discards a5821473bfe 156: onsuccess: #616: 1: Success after binutils/gcc/linux/g [...] discards 68851d6d643 155: onsuccess: #615: 1: Success after binutils/gcc/linux/g [...] discards ab229be65e3 154: onsuccess: #614: 1: Success after binutils/gcc/gdb: 14 [...] discards 6d6d8c41ca8 153: onsuccess: #613: 1: Success after binutils/gcc/gdb: 40 [...] discards 8bfc35e04b1 152: onsuccess: #612: 1: Success after binutils/gcc/gdb: 11 [...] discards 2d96c373717 151: onsuccess: #611: 1: Success after binutils/gcc/linux/g [...] discards 6b82e20f299 150: onsuccess: #610: 1: Success after binutils/gcc/linux/g [...] discards a4fa651c870 149: onsuccess: #609: 1: Success after binutils/gcc/linux/g [...] discards 22e103e2da3 148: onsuccess: #608: 1: Success after binutils/gcc/linux/g [...] discards 14b6e1bad51 147: onsuccess: #607: 1: Success after binutils/gcc/linux/g [...] discards 03af869af42 146: onsuccess: #606: 1: Success after binutils/gcc/linux/g [...] discards 624b5d70bd7 145: onsuccess: #605: 1: Success after binutils/gcc/linux/g [...] discards 54e9fb21d47 144: onsuccess: #604: 1: Success after binutils/gcc/gdb: 14 [...] discards 6c90840b02e 143: onsuccess: #603: 1: Success after binutils/gcc/linux/g [...] discards 9a7635192e1 142: onsuccess: #602: 1: Success after binutils/gcc/linux/g [...] discards 5d4b8973bf8 141: onsuccess: #601: 1: Success after linux: 794 commits discards c108a1b82a2 140: onsuccess: #600: 1: Success after gcc: 23 commits discards 8ddaa780728 139: onsuccess: #599: 1: Success after binutils: 10 commits discards 64e42c5f4b2 138: onsuccess: #597: 1: Success after binutils/gcc/linux/g [...] discards 35a9cf9725c 137: onsuccess: #596: 1: Success after binutils/gcc/linux/g [...] discards c23003abaad 136: onsuccess: #595: 1: Success after binutils/gcc/linux/g [...] discards 296387481be 135: onsuccess: #594: 1: Success after binutils/gcc/linux/g [...] discards cebe12c29ff 134: onsuccess: #593: 1: Success after binutils/gcc/linux/g [...] discards 135d7c76b26 133: onsuccess: #592: 1: Success after binutils/gcc/linux/g [...] discards 2afa1d5e88b 132: onsuccess: #591: 1: Success after binutils/gcc/linux/g [...] discards 83bc4a5032c 131: onsuccess: #590: 1: Success after binutils/gcc/linux/g [...] discards c6d681c3326 130: onsuccess: #589: 1: Success after binutils/gcc/linux/g [...] discards e988bec1365 129: onsuccess: #588: 1: Success after linux: 4 commits discards 445afa3e651 128: onsuccess: #586: 1: Success after binutils: 22 commits discards c2e1657319d 127: onsuccess: #584: 1: Success after linux: 21 commits discards 07acbbbc987 126: onsuccess: #582: 1: Success after gcc: 9 commits discards 4a3410132f5 125: onsuccess: #581: 1: Success after binutils: 4 commits discards 2e86a033bcf 124: onsuccess: #579: 1: Success after binutils/gcc/linux/g [...] discards 1e7fc9e02cb 123: onsuccess: #578: 1: Success after binutils/gcc/linux/g [...] discards 7264176f163 122: onsuccess: #577: 1: Success after binutils/gcc/linux/g [...] new b327ac5a3f3 122: onsuccess: #577: 1: Success after binutils/gcc/linux/g [...] new 823fc82ff67 123: onsuccess: #578: 1: Success after binutils/gcc/linux/g [...] new a50ece7f311 124: onsuccess: #579: 1: Success after binutils/gcc/linux/g [...] new 4c9fd078263 125: onsuccess: #581: 1: Success after binutils: 4 commits new e9d0e19e197 126: onsuccess: #582: 1: Success after gcc: 9 commits new 1c8fa199d44 127: onsuccess: #584: 1: Success after linux: 21 commits new 540551faade 128: onsuccess: #586: 1: Success after binutils: 22 commits new e8fc4fc6b2f 129: onsuccess: #588: 1: Success after linux: 4 commits new 5b16d51db8f 130: onsuccess: #589: 1: Success after binutils/gcc/linux/g [...] new 55ec7dea78c 131: onsuccess: #590: 1: Success after binutils/gcc/linux/g [...] new 496bddbe3e8 132: onsuccess: #591: 1: Success after binutils/gcc/linux/g [...] new 4b16e0ca744 133: onsuccess: #592: 1: Success after binutils/gcc/linux/g [...] new accc204209b 134: onsuccess: #593: 1: Success after binutils/gcc/linux/g [...] new 657ae8d88c4 135: onsuccess: #594: 1: Success after binutils/gcc/linux/g [...] new e113a165873 136: onsuccess: #595: 1: Success after binutils/gcc/linux/g [...] new 46ec225dc59 137: onsuccess: #596: 1: Success after binutils/gcc/linux/g [...] new 2760b5f4abc 138: onsuccess: #597: 1: Success after binutils/gcc/linux/g [...] new 4e2b110ea42 139: onsuccess: #599: 1: Success after binutils: 10 commits new 041851a1a6e 140: onsuccess: #600: 1: Success after gcc: 23 commits new ea98a1bec4f 141: onsuccess: #601: 1: Success after linux: 794 commits new 56a41c2b492 142: onsuccess: #602: 1: Success after binutils/gcc/linux/g [...] new 3d27b53d3f6 143: onsuccess: #603: 1: Success after binutils/gcc/linux/g [...] new 7cd64ab1173 144: onsuccess: #604: 1: Success after binutils/gcc/gdb: 14 [...] new aaa5239b48d 145: onsuccess: #605: 1: Success after binutils/gcc/linux/g [...] new de40426b303 146: onsuccess: #606: 1: Success after binutils/gcc/linux/g [...] new 5e5230b685e 147: onsuccess: #607: 1: Success after binutils/gcc/linux/g [...] new 4777afde368 148: onsuccess: #608: 1: Success after binutils/gcc/linux/g [...] new 64b2b02b209 149: onsuccess: #609: 1: Success after binutils/gcc/linux/g [...] new 4faf5536884 150: onsuccess: #610: 1: Success after binutils/gcc/linux/g [...] new f9cbb2c0170 151: onsuccess: #611: 1: Success after binutils/gcc/linux/g [...] new d41153dbba3 152: onsuccess: #612: 1: Success after binutils/gcc/gdb: 11 [...] new 1cd0321e212 153: onsuccess: #613: 1: Success after binutils/gcc/gdb: 40 [...] new 4a1bc64dddf 154: onsuccess: #614: 1: Success after binutils/gcc/gdb: 14 [...] new a39c66e3cf9 155: onsuccess: #615: 1: Success after binutils/gcc/linux/g [...] new 7c9d628bfbb 156: onsuccess: #616: 1: Success after binutils/gcc/linux/g [...] new d0c65817654 157: onsuccess: #617: 1: Success after binutils/gcc/linux/g [...] new 4c9c050f425 158: onsuccess: #618: 1: Success after binutils/gcc/linux/g [...] new bffcf1b9633 159: onsuccess: #620: 1: Success after binutils: 12 commits new 8f9fc832434 160: onsuccess: #621: 1: Success after gcc: 11 commits new c64ffc29cf9 161: onsuccess: #623: 1: Success after glibc: 9 commits new ff0b2bb86e3 162: onsuccess: #624: 1: Success after linux: 10 commits new c8c9c90772b 163: onsuccess: #625: 1: Success after binutils/gcc/glibc/g [...] new 873e75be9a3 164: onsuccess: #626: 1: Success after binutils/gcc/linux/g [...] new a5a00bb5511 165: onsuccess: #627: 1: Success after binutils/gcc/linux/g [...] new 0e0756ed483 166: onsuccess: #628: 1: Success after binutils/gcc/linux/g [...] new cd2b51f981a 167: onsuccess: #629: 1: Success after binutils/gcc/linux/g [...] new 61088a58155 168: onsuccess: #630: 1: Success after binutils/gcc/linux/g [...] new a7173375805 169: onsuccess: #631: 1: Success after binutils/gcc/linux/g [...] new 9921f673c83 170: onsuccess: #632: 1: Success after binutils/gcc/linux/g [...] new f1ec5cfaa27 171: onsuccess: #633: 1: Success after binutils/gcc/linux/g [...] new 7b5d09bc756 172: onsuccess: #634: 1: Success after binutils/gcc/linux/g [...] new f85f858756e 173: onsuccess: #635: 1: Success after binutils/gcc/linux/g [...] new b0853fb2ad6 174: onsuccess: #636: 1: Success after binutils/gcc/linux/g [...] new 1426fb4af56 175: onsuccess: #637: 1: Success after binutils/gcc/linux/g [...] new 191487bf84b 176: onsuccess: #638: 1: Success after binutils/gcc/linux/g [...] new 112174d4f30 177: onsuccess: #639: 1: Success after binutils/gcc/linux/g [...] new a32d0f269fe 178: onsuccess: #640: 1: Success after binutils/gcc/linux/g [...] new d5ac15c2fa0 179: onsuccess: #641: 1: Success after binutils/gcc/linux/g [...] new 9f4a783d2d2 180: onsuccess: #642: 1: Success after binutils/gcc/linux/g [...] new 28e30f9ec1b 181: onsuccess: #643: 1: Success after binutils/gcc/linux/g [...] new d3962f34350 182: onsuccess: #644: 1: Success after binutils/gcc/gdb: 30 [...] new bae6c52233d 183: onsuccess: #645: 1: Success after binutils/gcc/gdb: 20 [...] new 9c2fd1f5851 184: onsuccess: #646: 1: Success after binutils/gcc/linux/g [...] new 4aefe0c7d76 185: onsuccess: #647: 1: Success after binutils/gcc/linux/g [...] new efba8e5f5e0 186: onsuccess: #648: 1: Success after binutils/gcc/linux/g [...] new 248a05b9447 187: onsuccess: #649: 1: Success after binutils/gcc/linux/g [...] new f353798c2da 188: onsuccess: #650: 1: Success after binutils/gcc/linux/g [...] new 1ddecba8948 189: onsuccess: #651: 1: Success after binutils/gcc/linux/g [...] new 5bd14a66e81 190: onsuccess: #652: 1: Success after binutils/gcc/linux/g [...] new 142910dd5f3 191: onsuccess: #653: 1: Success after binutils/gcc/linux/g [...] new 1588343fb2a 192: onsuccess: #654: 1: Success after binutils/gcc/linux/g [...] new d261fefe830 193: onsuccess: #655: 1: Success after binutils/gcc/linux/g [...] new 214141c63da 194: onsuccess: #656: 1: Success after binutils/gcc/linux/g [...] new 5602d749c62 195: onsuccess: #657: 1: Success after binutils/gcc/linux/g [...] new 30562c0e053 196: onsuccess: #659: 1: Success after binutils/gcc/linux/g [...] new 2ecfbc9d9d7 197: onsuccess: #660: 1: Success after binutils/gcc/linux/g [...] new 97ff58700ec 198: onsuccess: #661: 1: Success after binutils/gcc/linux/g [...] new 82521605e6a 199: onsuccess: #662: 1: Success after binutils/gcc/linux/g [...] new 45b3e6bd8a7 200: onsuccess: #663: 1: Success after binutils/gcc/linux/g [...] new 667a68aa205 201: onsuccess: #664: 1: Success after binutils/gcc/glibc/g [...] new 927e5f86ec9 202: onsuccess: #670: 1: Success after binutils/gcc/linux/g [...] new e02d23ec5d6 203: onsuccess: #671: 1: Success after binutils/gcc/linux/g [...] new c8c7263767c 204: onsuccess: #672: 1: Success after binutils/gcc/linux/g [...] new 8c37adb2a1a 205: onsuccess: #1: 1: Success after binutils/gcc/linux/gli [...] new 9bcb7aba988 206: onsuccess: #2: 1: Success after binutils/gcc/linux/gli [...] new 43ff048c4b9 207: onsuccess: #3: 1: Success after binutils/gcc/linux/gdb [...] new ae90ebc512b 208: onsuccess: #4: 1: Success after binutils/gcc/linux/gli [...] new d308831038e 209: onsuccess: #5: 1: Success after binutils/gcc/linux/gli [...] new c039be724a7 210: onsuccess: #6: 1: Success after binutils/gcc/linux/gli [...] new c92eb3b9ed1 211: onsuccess: #7: 1: Success after binutils/gcc/linux/gdb [...] new 0948f813ce4 212: onsuccess: #8: 1: Success after binutils/gcc/linux/gli [...] new bfba3c08960 213: onsuccess: #9: 1: Success after binutils/gcc/linux/gli [...] new 30277fa674f 214: onsuccess: #10: 1: Success after binutils/gcc/linux/gd [...] new fe05529bc1a 215: onsuccess: #11: 1: Success after binutils/gcc/linux/gd [...] new 272c4eb97c9 216: onsuccess: #12: 1: Success after binutils/gcc/linux/gl [...] new c2eabd0481c 217: onsuccess: #14: 1: Success after binutils/gcc/linux/gl [...] new 99275e3e0ef 218: onsuccess: #15: 1: Success after binutils/gcc/linux/gl [...] new e75ece85b14 219: onsuccess: #16: 1: Success after binutils/gcc/linux/gl [...] new 7a9a3688307 220: onsuccess: #17: 1: Success after binutils/gcc/linux/gl [...] new 3b4568fd7b0 221: onsuccess: #18: 1: Success after binutils/gcc/linux/gd [...] new e94590712f6 222: onsuccess: #19: 1: Success after binutils/gcc/linux/gl [...] new 1dd450c2ce8 223: onsuccess: #20: 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 (89e82856564) \ 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 1764 -> 1756 bytes 02-prepare_abe/console.log.xz | Bin 2780 -> 2768 bytes 03-build_abe-binutils/console.log.xz | Bin 52644 -> 52912 bytes 04-build_abe-gcc/console.log.xz | Bin 238228 -> 239128 bytes 05-clean_sysroot/console.log.xz | Bin 316 -> 316 bytes 06-build_abe-linux/console.log.xz | Bin 8352 -> 8640 bytes 07-build_abe-glibc/console.log.xz | Bin 237316 -> 237464 bytes 08-build_abe-gdb/console.log.xz | Bin 51332 -> 51628 bytes 09-build_abe-dejagnu/console.log.xz | Bin 3832 -> 3812 bytes 10-build_abe-check_gcc/console.log.xz | Bin 2664 -> 2956 bytes 11-check_regression/console.log.xz | Bin 6956 -> 7216 bytes 11-check_regression/extra-bisect-params | 1 - 11-check_regression/fails.sum | 6 - 11-check_regression/mail-body.txt | 34 +-- 11-check_regression/results.compare | 31 ++- 11-check_regression/results.compare2 | 153 ++++++++----- 11-check_regression/results.regressions | 26 --- 12-update_baseline/console.log | 66 +++--- 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 | 36 ++-- mail/mail-subject.txt | 2 +- manifest.sh | 38 ++-- results | 26 --- sumfiles/g++.log.xz | Bin 2888232 -> 2890876 bytes sumfiles/g++.sum | 139 +++++++----- sumfiles/gcc.log.xz | Bin 2482528 -> 2472616 bytes sumfiles/gcc.sum | 366 +++++++++++++++++--------------- sumfiles/gfortran.log.xz | Bin 957196 -> 957292 bytes sumfiles/gfortran.sum | 38 ++-- sumfiles/libatomic.log.xz | Bin 2276 -> 2276 bytes sumfiles/libatomic.sum | 4 +- sumfiles/libgomp.log.xz | Bin 234256 -> 233976 bytes sumfiles/libgomp.sum | 16 +- sumfiles/libitm.log.xz | Bin 2696 -> 2692 bytes sumfiles/libitm.sum | 6 +- sumfiles/libstdc++.log.xz | Bin 469440 -> 470568 bytes sumfiles/libstdc++.sum | 30 ++- 43 files changed, 546 insertions(+), 486 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