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 5b4a66efcee0 239: onsuccess: #40: 1: [TCWG CI] Success after binutils/g [...] discards 124a73dc5090 238: onsuccess: #39: 1: [TCWG CI] Success after binutils/g [...] discards a37cca09ccc3 237: onsuccess: #38: 1: [TCWG CI] Success after binutils/g [...] discards 079eb44ca9c0 236: onsuccess: #37: 1: [TCWG CI] Success after binutils/g [...] discards 6bb68e2cc6a9 235: onsuccess: #36: 1: [TCWG CI] Success after binutils/g [...] discards 56ca3e733b52 234: onsuccess: #35: 1: [TCWG CI] Success after binutils/g [...] discards 7c1a088166ea 233: onsuccess: #34: 1: [TCWG CI] Success after binutils/g [...] discards 99d5595682e6 232: onsuccess: #32: 1: Success after binutils/gcc/linux/g [...] discards 6838a7bf5956 231: onsuccess: #31: 1: Success after binutils/gcc/linux/g [...] discards 9bd5a4c32a23 230: onsuccess: #30: 1: Success after binutils/gcc/linux/g [...] discards 0479050ca31f 229: onsuccess: #29: 1: Success after binutils/gcc/linux/g [...] discards 7f94124a78ba 228: onsuccess: #28: 1: Success after binutils/gcc/linux/g [...] discards 2d9b951987bb 227: onsuccess: #27: 1: Success after binutils/gcc/linux/g [...] discards 576a9d3c9772 226: onsuccess: #26: 1: Success after binutils/gcc/linux/g [...] discards 75913f06a3e8 225: onsuccess: #25: 1: Success after binutils/gcc/linux/g [...] discards aeb674169737 224: onsuccess: #21: 1: Success after binutils/gcc/linux/g [...] discards 585caa1eaf40 223: onsuccess: #20: 1: Success after binutils/gcc/linux/g [...] discards 49e0752f5d72 222: onsuccess: #19: 1: Success after binutils/gcc/linux/g [...] discards 05ce68ace0e8 221: onsuccess: #18: 1: Success after binutils/gcc/linux/g [...] discards 84ba766e0e35 220: onsuccess: #17: 1: Success after binutils/gcc/linux/g [...] discards ebc012a86ebf 219: onsuccess: #16: 1: Success after binutils/gcc/linux/g [...] discards be7b88284d9e 218: onsuccess: #15: 1: Success after binutils/gcc/linux/g [...] discards bfccee4ea6da 217: onsuccess: #14: 1: Success after binutils/gcc/linux/g [...] discards f51afc4ddc18 216: onsuccess: #12: 1: Success after binutils/gcc/linux/g [...] discards b3b6f010ddc7 215: onsuccess: #11: 1: Success after binutils/gcc/linux/g [...] discards 130e4dd8706f 214: onsuccess: #10: 1: Success after binutils/gcc/linux/g [...] discards 7c1fe90b6093 213: onsuccess: #9: 1: Success after binutils/gcc/linux/gl [...] discards 8a5d670d160d 212: onsuccess: #8: 1: Success after binutils/gcc/linux/gl [...] discards e0c4eff0d3dd 211: onsuccess: #7: 1: Success after binutils/gcc/linux/gd [...] discards a3975145c545 210: onsuccess: #6: 1: Success after binutils/gcc/linux/gl [...] discards 25a598caa100 209: onsuccess: #5: 1: Success after binutils/gcc/linux/gl [...] discards 9f82d25a70f7 208: onsuccess: #4: 1: Success after binutils/gcc/linux/gl [...] discards 9ab46434488e 207: onsuccess: #3: 1: Success after binutils/gcc/linux/gd [...] discards dab36602bbe4 206: onsuccess: #2: 1: Success after binutils/gcc/linux/gl [...] discards 17fe587fe461 205: onsuccess: #1: 1: Success after binutils/gcc/linux/gl [...] discards 09cf2b5733a9 204: onsuccess: #672: 1: Success after binutils/gcc/linux/ [...] discards 08f5d115e6d5 203: onsuccess: #671: 1: Success after binutils/gcc/linux/ [...] discards 3bbb8afe142c 202: onsuccess: #670: 1: Success after binutils/gcc/linux/ [...] discards 4ca6c7ed9c8d 201: onsuccess: #664: 1: Success after binutils/gcc/glibc/ [...] discards f62bb7c9bf2e 200: onsuccess: #663: 1: Success after binutils/gcc/linux/ [...] discards 5868ca35e52f 199: onsuccess: #662: 1: Success after binutils/gcc/linux/ [...] discards c1bf61bcd298 198: onsuccess: #661: 1: Success after binutils/gcc/linux/ [...] discards c573edc12c54 197: onsuccess: #660: 1: Success after binutils/gcc/linux/ [...] discards 38fabe42dbf7 196: onsuccess: #659: 1: Success after binutils/gcc/linux/ [...] discards 581289d028a0 195: onsuccess: #657: 1: Success after binutils/gcc/linux/ [...] discards e801787ce7a3 194: onsuccess: #656: 1: Success after binutils/gcc/linux/ [...] discards 1ca5af1209ba 193: onsuccess: #655: 1: Success after binutils/gcc/linux/ [...] discards 90ec0b55ff05 192: onsuccess: #654: 1: Success after binutils/gcc/linux/ [...] discards b05531a42682 191: onsuccess: #653: 1: Success after binutils/gcc/linux/ [...] discards fcfcea3b8cbc 190: onsuccess: #652: 1: Success after binutils/gcc/linux/ [...] discards 40718368413c 189: onsuccess: #651: 1: Success after binutils/gcc/linux/ [...] discards bd0b49fe2949 188: onsuccess: #650: 1: Success after binutils/gcc/linux/ [...] discards 29b888266b81 187: onsuccess: #649: 1: Success after binutils/gcc/linux/ [...] discards daf4227b9eef 186: onsuccess: #648: 1: Success after binutils/gcc/linux/ [...] discards 46b4004d581c 185: onsuccess: #647: 1: Success after binutils/gcc/linux/ [...] discards f766580b37f5 184: onsuccess: #646: 1: Success after binutils/gcc/linux/ [...] discards 8297890c99d6 183: onsuccess: #645: 1: Success after binutils/gcc/gdb: 2 [...] discards 21b9383db257 182: onsuccess: #644: 1: Success after binutils/gcc/gdb: 3 [...] discards bf4d1f948ee0 181: onsuccess: #643: 1: Success after binutils/gcc/linux/ [...] discards f00434110329 180: onsuccess: #642: 1: Success after binutils/gcc/linux/ [...] discards 7572e4a0765e 179: onsuccess: #641: 1: Success after binutils/gcc/linux/ [...] discards 8285f2126d18 178: onsuccess: #640: 1: Success after binutils/gcc/linux/ [...] discards 2a343c8a0ab1 177: onsuccess: #639: 1: Success after binutils/gcc/linux/ [...] discards 5956ae31d6a5 176: onsuccess: #638: 1: Success after binutils/gcc/linux/ [...] discards 6cd25332aa48 175: onsuccess: #637: 1: Success after binutils/gcc/linux/ [...] discards f8fd2f8d3163 174: onsuccess: #636: 1: Success after binutils/gcc/linux/ [...] discards e9b67ee839a7 173: onsuccess: #635: 1: Success after binutils/gcc/linux/ [...] discards f8a0e4e2ac60 172: onsuccess: #634: 1: Success after binutils/gcc/linux/ [...] discards bdde4fad3de7 171: onsuccess: #633: 1: Success after binutils/gcc/linux/ [...] discards 4b5ec7cf5109 170: onsuccess: #632: 1: Success after binutils/gcc/linux/ [...] discards 49641f1ff2f1 169: onsuccess: #631: 1: Success after binutils/gcc/linux/ [...] discards e35ba065af79 168: onsuccess: #630: 1: Success after binutils/gcc/linux/ [...] discards e04ad265045c 167: onsuccess: #629: 1: Success after binutils/gcc/linux/ [...] discards 8a776f496880 166: onsuccess: #628: 1: Success after binutils/gcc/linux/ [...] discards b1c311640860 165: onsuccess: #627: 1: Success after binutils/gcc/linux/ [...] discards e14878867543 164: onsuccess: #626: 1: Success after binutils/gcc/linux/ [...] discards 4207d2c84b3d 163: onsuccess: #625: 1: Success after binutils/gcc/glibc/ [...] discards c7b77f6a0359 162: onsuccess: #624: 1: Success after linux: 10 commits discards bcb82fa95617 161: onsuccess: #623: 1: Success after glibc: 9 commits discards fc5b1ecf4653 160: onsuccess: #621: 1: Success after gcc: 11 commits discards 0d9cd388780c 159: onsuccess: #620: 1: Success after binutils: 12 commits discards be3a6b96de9a 158: onsuccess: #618: 1: Success after binutils/gcc/linux/ [...] discards 2e44bfa41fef 157: onsuccess: #617: 1: Success after binutils/gcc/linux/ [...] discards 63221123f50c 156: onsuccess: #616: 1: Success after binutils/gcc/linux/ [...] discards 2d583180108e 155: onsuccess: #615: 1: Success after binutils/gcc/linux/ [...] discards ee2066320e0f 154: onsuccess: #614: 1: Success after binutils/gcc/gdb: 1 [...] discards 8f3b4e263453 153: onsuccess: #613: 1: Success after binutils/gcc/gdb: 4 [...] discards 91da68dd657b 152: onsuccess: #612: 1: Success after binutils/gcc/gdb: 1 [...] discards 16721e25cd7c 151: onsuccess: #611: 1: Success after binutils/gcc/linux/ [...] discards 611b60aa52c0 150: onsuccess: #610: 1: Success after binutils/gcc/linux/ [...] discards 6730aa6911a9 149: onsuccess: #609: 1: Success after binutils/gcc/linux/ [...] discards 6f1d176f6a3f 148: onsuccess: #608: 1: Success after binutils/gcc/linux/ [...] discards 68412e38bf25 147: onsuccess: #607: 1: Success after binutils/gcc/linux/ [...] discards 0356e7163675 146: onsuccess: #606: 1: Success after binutils/gcc/linux/ [...] discards 7d51140f69f4 145: onsuccess: #605: 1: Success after binutils/gcc/linux/ [...] discards cfc77fefbd37 144: onsuccess: #604: 1: Success after binutils/gcc/gdb: 1 [...] discards 8940503b092b 143: onsuccess: #603: 1: Success after binutils/gcc/linux/ [...] discards 0ff4df883e26 142: onsuccess: #602: 1: Success after binutils/gcc/linux/ [...] discards 68758b4f8d41 141: onsuccess: #601: 1: Success after linux: 794 commits discards 719a8603d96a 140: onsuccess: #600: 1: Success after gcc: 23 commits discards 4a946a123f72 139: onsuccess: #599: 1: Success after binutils: 10 commits new 2e937201b12f 139: onsuccess: #599: 1: Success after binutils: 10 commits new 67317dfc5e4e 140: onsuccess: #600: 1: Success after gcc: 23 commits new 8ae1511a0bdf 141: onsuccess: #601: 1: Success after linux: 794 commits new 47b680b53052 142: onsuccess: #602: 1: Success after binutils/gcc/linux/ [...] new 00f22a0cab3b 143: onsuccess: #603: 1: Success after binutils/gcc/linux/ [...] new 364bdc2eb443 144: onsuccess: #604: 1: Success after binutils/gcc/gdb: 1 [...] new 88e72c8893b4 145: onsuccess: #605: 1: Success after binutils/gcc/linux/ [...] new a743c9f4648b 146: onsuccess: #606: 1: Success after binutils/gcc/linux/ [...] new e6598406ca00 147: onsuccess: #607: 1: Success after binutils/gcc/linux/ [...] new d8fc9d9cb382 148: onsuccess: #608: 1: Success after binutils/gcc/linux/ [...] new 86721285f0be 149: onsuccess: #609: 1: Success after binutils/gcc/linux/ [...] new 3905dc2ca442 150: onsuccess: #610: 1: Success after binutils/gcc/linux/ [...] new b1641cc09262 151: onsuccess: #611: 1: Success after binutils/gcc/linux/ [...] new 2d79e927620d 152: onsuccess: #612: 1: Success after binutils/gcc/gdb: 1 [...] new 9ff3ec9b904d 153: onsuccess: #613: 1: Success after binutils/gcc/gdb: 4 [...] new 9a664a6d58a7 154: onsuccess: #614: 1: Success after binutils/gcc/gdb: 1 [...] new 9dcd29caaf48 155: onsuccess: #615: 1: Success after binutils/gcc/linux/ [...] new 2c50eae3a0c4 156: onsuccess: #616: 1: Success after binutils/gcc/linux/ [...] new 481734bc5aa8 157: onsuccess: #617: 1: Success after binutils/gcc/linux/ [...] new 1b03004a7843 158: onsuccess: #618: 1: Success after binutils/gcc/linux/ [...] new 35d2b8ed5511 159: onsuccess: #620: 1: Success after binutils: 12 commits new 9aa70d6680a5 160: onsuccess: #621: 1: Success after gcc: 11 commits new 36c108bd360e 161: onsuccess: #623: 1: Success after glibc: 9 commits new 193a288fa53b 162: onsuccess: #624: 1: Success after linux: 10 commits new 7a7e0d69d441 163: onsuccess: #625: 1: Success after binutils/gcc/glibc/ [...] new 51c931e6aac8 164: onsuccess: #626: 1: Success after binutils/gcc/linux/ [...] new 1d58eeb15295 165: onsuccess: #627: 1: Success after binutils/gcc/linux/ [...] new d7580cf115fe 166: onsuccess: #628: 1: Success after binutils/gcc/linux/ [...] new 8b06f0baa589 167: onsuccess: #629: 1: Success after binutils/gcc/linux/ [...] new 32c7c926b1ae 168: onsuccess: #630: 1: Success after binutils/gcc/linux/ [...] new 169c96357906 169: onsuccess: #631: 1: Success after binutils/gcc/linux/ [...] new da6ce2670959 170: onsuccess: #632: 1: Success after binutils/gcc/linux/ [...] new e8dcf091704b 171: onsuccess: #633: 1: Success after binutils/gcc/linux/ [...] new 8765e5342325 172: onsuccess: #634: 1: Success after binutils/gcc/linux/ [...] new 5205adae30fd 173: onsuccess: #635: 1: Success after binutils/gcc/linux/ [...] new 8a81edd017b9 174: onsuccess: #636: 1: Success after binutils/gcc/linux/ [...] new 45b437afdf31 175: onsuccess: #637: 1: Success after binutils/gcc/linux/ [...] new fd40ffb57cc7 176: onsuccess: #638: 1: Success after binutils/gcc/linux/ [...] new 6879c7c3fa2f 177: onsuccess: #639: 1: Success after binutils/gcc/linux/ [...] new 87ef4d39bead 178: onsuccess: #640: 1: Success after binutils/gcc/linux/ [...] new 5d2b0dd61729 179: onsuccess: #641: 1: Success after binutils/gcc/linux/ [...] new 1b844bbd87be 180: onsuccess: #642: 1: Success after binutils/gcc/linux/ [...] new 398f4498c9e3 181: onsuccess: #643: 1: Success after binutils/gcc/linux/ [...] new ea01c5f1541b 182: onsuccess: #644: 1: Success after binutils/gcc/gdb: 3 [...] new 5e4678482636 183: onsuccess: #645: 1: Success after binutils/gcc/gdb: 2 [...] new beed4df70436 184: onsuccess: #646: 1: Success after binutils/gcc/linux/ [...] new 9084d8de7d6d 185: onsuccess: #647: 1: Success after binutils/gcc/linux/ [...] new 3d1dffe92c79 186: onsuccess: #648: 1: Success after binutils/gcc/linux/ [...] new 2c64ec37811d 187: onsuccess: #649: 1: Success after binutils/gcc/linux/ [...] new bddd8e6bb1ae 188: onsuccess: #650: 1: Success after binutils/gcc/linux/ [...] new 3c34d0cb54fb 189: onsuccess: #651: 1: Success after binutils/gcc/linux/ [...] new b4f2dde24192 190: onsuccess: #652: 1: Success after binutils/gcc/linux/ [...] new 00f740981563 191: onsuccess: #653: 1: Success after binutils/gcc/linux/ [...] new ac7a3c2ee5b4 192: onsuccess: #654: 1: Success after binutils/gcc/linux/ [...] new d5a4290e82db 193: onsuccess: #655: 1: Success after binutils/gcc/linux/ [...] new 80afca26282e 194: onsuccess: #656: 1: Success after binutils/gcc/linux/ [...] new 24dd421731d5 195: onsuccess: #657: 1: Success after binutils/gcc/linux/ [...] new a918937522d1 196: onsuccess: #659: 1: Success after binutils/gcc/linux/ [...] new bfb611f17e19 197: onsuccess: #660: 1: Success after binutils/gcc/linux/ [...] new 64ec2ebe0e08 198: onsuccess: #661: 1: Success after binutils/gcc/linux/ [...] new 97814c39c93c 199: onsuccess: #662: 1: Success after binutils/gcc/linux/ [...] new 1e66341af22c 200: onsuccess: #663: 1: Success after binutils/gcc/linux/ [...] new 435a14fdd754 201: onsuccess: #664: 1: Success after binutils/gcc/glibc/ [...] new e9262d7909c6 202: onsuccess: #670: 1: Success after binutils/gcc/linux/ [...] new ef660c81c02c 203: onsuccess: #671: 1: Success after binutils/gcc/linux/ [...] new 5c7e71193827 204: onsuccess: #672: 1: Success after binutils/gcc/linux/ [...] new f87878f0c126 205: onsuccess: #1: 1: Success after binutils/gcc/linux/gl [...] new d71aa8c90023 206: onsuccess: #2: 1: Success after binutils/gcc/linux/gl [...] new ce9fe23eba2d 207: onsuccess: #3: 1: Success after binutils/gcc/linux/gd [...] new 1e2e4fa926a2 208: onsuccess: #4: 1: Success after binutils/gcc/linux/gl [...] new 079d467b22a2 209: onsuccess: #5: 1: Success after binutils/gcc/linux/gl [...] new dbc0c96b71ba 210: onsuccess: #6: 1: Success after binutils/gcc/linux/gl [...] new 96416e09fcb2 211: onsuccess: #7: 1: Success after binutils/gcc/linux/gd [...] new 23a717a2339c 212: onsuccess: #8: 1: Success after binutils/gcc/linux/gl [...] new 1aa266002ffd 213: onsuccess: #9: 1: Success after binutils/gcc/linux/gl [...] new eaa085b71cfa 214: onsuccess: #10: 1: Success after binutils/gcc/linux/g [...] new c14d4558e8c3 215: onsuccess: #11: 1: Success after binutils/gcc/linux/g [...] new 4e10773db892 216: onsuccess: #12: 1: Success after binutils/gcc/linux/g [...] new 041120cadebc 217: onsuccess: #14: 1: Success after binutils/gcc/linux/g [...] new f4abf5ea00d8 218: onsuccess: #15: 1: Success after binutils/gcc/linux/g [...] new fa19e6bd78af 219: onsuccess: #16: 1: Success after binutils/gcc/linux/g [...] new d61a884c4d28 220: onsuccess: #17: 1: Success after binutils/gcc/linux/g [...] new 4636b84ca12b 221: onsuccess: #18: 1: Success after binutils/gcc/linux/g [...] new 9db94627906a 222: onsuccess: #19: 1: Success after binutils/gcc/linux/g [...] new efbbef257f1b 223: onsuccess: #20: 1: Success after binutils/gcc/linux/g [...] new 7f3e37eba264 224: onsuccess: #21: 1: Success after binutils/gcc/linux/g [...] new a5e2c08b949a 225: onsuccess: #25: 1: Success after binutils/gcc/linux/g [...] new 54433cab4ad0 226: onsuccess: #26: 1: Success after binutils/gcc/linux/g [...] new a9e88fabc268 227: onsuccess: #27: 1: Success after binutils/gcc/linux/g [...] new f03b99967a76 228: onsuccess: #28: 1: Success after binutils/gcc/linux/g [...] new 7237d2c6e2d3 229: onsuccess: #29: 1: Success after binutils/gcc/linux/g [...] new afed723bfacf 230: onsuccess: #30: 1: Success after binutils/gcc/linux/g [...] new 22f85df4013c 231: onsuccess: #31: 1: Success after binutils/gcc/linux/g [...] new a059a222486c 232: onsuccess: #32: 1: Success after binutils/gcc/linux/g [...] new 908183c8cd57 233: onsuccess: #34: 1: [TCWG CI] Success after binutils/g [...] new 4116028211ad 234: onsuccess: #35: 1: [TCWG CI] Success after binutils/g [...] new e01279d4a8f1 235: onsuccess: #36: 1: [TCWG CI] Success after binutils/g [...] new dbf1c6cd4ea6 236: onsuccess: #37: 1: [TCWG CI] Success after binutils/g [...] new 52720a7980ff 237: onsuccess: #38: 1: [TCWG CI] Success after binutils/g [...] new 24a81d2112a4 238: onsuccess: #39: 1: [TCWG CI] Success after binutils/g [...] new 57639bb15978 239: onsuccess: #40: 1: [TCWG CI] Success after binutils/g [...] new 0ad21a41bfe5 240: onsuccess: #41: 1: [TCWG CI] Success after binutils/g [...]
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 (5b4a66efcee0) \ 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 2052 -> 2096 bytes 02-prepare_abe/console.log.xz | Bin 2512 -> 2552 bytes 03-build_abe-binutils/console.log.xz | Bin 49100 -> 49684 bytes 04-build_abe-gcc/console.log.xz | Bin 237568 -> 234420 bytes 05-clean_sysroot/console.log.xz | Bin 316 -> 316 bytes 06-build_abe-linux/console.log.xz | Bin 8760 -> 8728 bytes 07-build_abe-glibc/console.log.xz | Bin 233416 -> 232660 bytes 08-build_abe-gdb/console.log.xz | Bin 46540 -> 46944 bytes 09-build_abe-dejagnu/console.log.xz | Bin 3772 -> 3776 bytes 10-build_abe-check_gcc/console.log.xz | Bin 10664 -> 9292 bytes 11-check_regression/console.log.xz | Bin 5744 -> 5644 bytes 11-check_regression/extra-bisect-params | 1 - 11-check_regression/fails.sum | 6 - 11-check_regression/results.compare | 25 +- 11-check_regression/results.compare2 | 219 +- 11-check_regression/results.regressions | 26 - 12-update_baseline/console.log | 42 +- dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- git/gdb_rev | 2 +- git/glibc_rev | 2 +- mail/changes-list-long.txt | 50 +- mail/changes-list-short.txt | 2 +- mail/last_good.sh | 38 +- manifest.sh | 34 +- results | 26 - sumfiles/g++.log.sep.xz | Bin 71100 -> 106092 bytes sumfiles/g++.log.xz | Bin 2915836 -> 2888448 bytes sumfiles/g++.sum | 69 +- sumfiles/g++.sum.sep | 7050 +++++++++++++------------------ sumfiles/gcc.log.sep.xz | Bin 75968 -> 75828 bytes sumfiles/gcc.log.xz | Bin 2471712 -> 2454620 bytes sumfiles/gcc.sum | 105 +- sumfiles/gcc.sum.sep | 3419 +++++---------- sumfiles/gfortran.log.sep.xz | Bin 37696 -> 25752 bytes sumfiles/gfortran.log.xz | Bin 971148 -> 955728 bytes sumfiles/gfortran.sum | 7 +- sumfiles/gfortran.sum.sep | 1638 +++++-- sumfiles/libatomic.log.xz | Bin 2284 -> 2284 bytes sumfiles/libatomic.sum | 2 +- sumfiles/libgomp.log.xz | Bin 230592 -> 230724 bytes sumfiles/libgomp.sum | 8 +- sumfiles/libitm.log.xz | Bin 2688 -> 2692 bytes sumfiles/libitm.sum | 2 +- sumfiles/libstdc++.log.sep.xz | Bin 14904 -> 20848 bytes sumfiles/libstdc++.log.xz | Bin 480724 -> 466044 bytes sumfiles/libstdc++.sum.sep | 331 +- 48 files changed, 5853 insertions(+), 7257 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