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 393df78051 251: onsuccess: #54: 1: [TCWG CI] https://ci.linaro.org/job/ [...] discards bcb16d5234 250: onsuccess: #53: 1: [TCWG CI] https://ci.linaro.org/job/ [...] discards ee95ddeaa8 249: onsuccess: #52: 1: [TCWG CI] https://ci.linaro.org/job/ [...] discards 9e2c84d161 248: onsuccess: #51: 1: [TCWG CI] https://ci.linaro.org/job/ [...] discards 072a3c8126 247: onsuccess: #50: 1: [TCWG CI] https://ci.linaro.org/job/ [...] discards a6c9eb0b3c 246: onsuccess: #49: 1: [TCWG CI] https://ci.linaro.org/job/ [...] discards 9830614503 245: onsuccess: #48: 1: [TCWG CI] https://ci.linaro.org/job/ [...] discards 29bbbab800 244: onsuccess: #46: 1: [TCWG CI] Success after binutils/gcc [...] discards 66e44eff45 243: onsuccess: #45: 1: [TCWG CI] Success after binutils/gcc [...] discards 92923a7859 242: onsuccess: #44: 1: [TCWG CI] Success after binutils/gcc [...] discards 7fae98d812 241: onsuccess: #42: 1: [TCWG CI] Success after binutils/gcc [...] discards 3c738582fa 240: onsuccess: #41: 1: [TCWG CI] Success after binutils/gcc [...] discards 117fab4398 239: onsuccess: #40: 1: [TCWG CI] Success after binutils/gcc [...] discards 4f8dd3017e 238: onsuccess: #39: 1: [TCWG CI] Success after binutils/gcc [...] discards a05fe97879 237: onsuccess: #38: 1: [TCWG CI] Success after binutils/gcc [...] discards b8c4c554d6 236: onsuccess: #37: 1: [TCWG CI] Success after binutils/gcc [...] discards 372e6cbe31 235: onsuccess: #36: 1: [TCWG CI] Success after binutils/gcc [...] discards 1345a58709 234: onsuccess: #35: 1: [TCWG CI] Success after binutils/gcc [...] discards e68e73064d 233: onsuccess: #34: 1: [TCWG CI] Success after binutils/gcc [...] discards 3f78d2ea3e 232: onsuccess: #32: 1: Success after binutils/gcc/linux/gli [...] discards d4c0574d79 231: onsuccess: #31: 1: Success after binutils/gcc/linux/gdb [...] discards 29dbcd2f2d 230: onsuccess: #30: 1: Success after binutils/gcc/linux/gdb [...] discards e0ba8d2fd0 229: onsuccess: #29: 1: Success after binutils/gcc/linux/gdb [...] discards 4682e74f0c 228: onsuccess: #28: 1: Success after binutils/gcc/linux/gli [...] discards 65c3fdcb00 227: onsuccess: #27: 1: Success after binutils/gcc/linux/gdb [...] discards f9cd6ed5fa 226: onsuccess: #26: 1: Success after binutils/gcc/linux/gdb [...] discards 447797ae13 225: onsuccess: #25: 1: Success after binutils/gcc/linux/gdb [...] discards 0092df4dfe 224: onsuccess: #21: 1: Success after binutils/gcc/linux/gli [...] discards ba9fd6744f 223: onsuccess: #20: 1: Success after binutils/gcc/linux/gli [...] discards fdbf0762f5 222: onsuccess: #19: 1: Success after binutils/gcc/linux/gli [...] discards aec7a64abf 221: onsuccess: #18: 1: Success after binutils/gcc/linux/gdb [...] discards d5425023d2 220: onsuccess: #17: 1: Success after binutils/gcc/linux/gli [...] discards 922b501af0 219: onsuccess: #16: 1: Success after binutils/gcc/linux/gli [...] discards f0324e9bba 218: onsuccess: #15: 1: Success after binutils/gcc/linux/gli [...] discards a2ec6f3600 217: onsuccess: #14: 1: Success after binutils/gcc/linux/gli [...] discards 6b60758385 216: onsuccess: #12: 1: Success after binutils/gcc/linux/gli [...] discards f09cd729d5 215: onsuccess: #11: 1: Success after binutils/gcc/linux/gdb [...] discards e5e6a45203 214: onsuccess: #10: 1: Success after binutils/gcc/linux/gdb [...] discards deb007da9e 213: onsuccess: #9: 1: Success after binutils/gcc/linux/glib [...] discards 1240ecd1dc 212: onsuccess: #8: 1: Success after binutils/gcc/linux/glib [...] discards 5cab77642d 211: onsuccess: #7: 1: Success after binutils/gcc/linux/gdb: [...] discards 2c8da3702e 210: onsuccess: #6: 1: Success after binutils/gcc/linux/glib [...] discards a899c5cfd0 209: onsuccess: #5: 1: Success after binutils/gcc/linux/glib [...] discards 92ac3927d2 208: onsuccess: #4: 1: Success after binutils/gcc/linux/glib [...] discards d3ae33cd86 207: onsuccess: #3: 1: Success after binutils/gcc/linux/gdb: [...] discards 27e245dc27 206: onsuccess: #2: 1: Success after binutils/gcc/linux/glib [...] discards f5f4beac7e 205: onsuccess: #1: 1: Success after binutils/gcc/linux/glib [...] discards d01f4531c4 204: onsuccess: #672: 1: Success after binutils/gcc/linux/gl [...] discards 5a29a33001 203: onsuccess: #671: 1: Success after binutils/gcc/linux/gd [...] discards 993f999f2f 202: onsuccess: #670: 1: Success after binutils/gcc/linux/gl [...] discards 2f37f16dbe 201: onsuccess: #664: 1: Success after binutils/gcc/glibc/gd [...] discards 9895545c07 200: onsuccess: #663: 1: Success after binutils/gcc/linux/gl [...] discards eca034c9eb 199: onsuccess: #662: 1: Success after binutils/gcc/linux/gl [...] discards b09470ced6 198: onsuccess: #661: 1: Success after binutils/gcc/linux/gd [...] discards b241922eaf 197: onsuccess: #660: 1: Success after binutils/gcc/linux/gl [...] discards f720db93dc 196: onsuccess: #659: 1: Success after binutils/gcc/linux/gl [...] discards 7ed49f3a43 195: onsuccess: #657: 1: Success after binutils/gcc/linux/gl [...] discards d0e4da9324 194: onsuccess: #656: 1: Success after binutils/gcc/linux/gl [...] discards ea5669d6a4 193: onsuccess: #655: 1: Success after binutils/gcc/linux/gd [...] discards b049b93a99 192: onsuccess: #654: 1: Success after binutils/gcc/linux/gl [...] discards 1ee71626a2 191: onsuccess: #653: 1: Success after binutils/gcc/linux/gl [...] discards 562143b213 190: onsuccess: #652: 1: Success after binutils/gcc/linux/gl [...] discards 2d63d8e380 189: onsuccess: #651: 1: Success after binutils/gcc/linux/gl [...] discards cccc8638b7 188: onsuccess: #650: 1: Success after binutils/gcc/linux/gl [...] discards aeaf765393 187: onsuccess: #649: 1: Success after binutils/gcc/linux/gl [...] discards f45d1e1852 186: onsuccess: #648: 1: Success after binutils/gcc/linux/gd [...] discards 54d7461e15 185: onsuccess: #647: 1: Success after binutils/gcc/linux/gd [...] discards 48bd5e2233 184: onsuccess: #646: 1: Success after binutils/gcc/linux/gl [...] discards 26f0ee33d5 183: onsuccess: #645: 1: Success after binutils/gcc/gdb: 203 [...] discards 7bdcd5c107 182: onsuccess: #644: 1: Success after binutils/gcc/gdb: 30 commits discards 5ca62c9437 181: onsuccess: #643: 1: Success after binutils/gcc/linux/gl [...] discards a5a81ac5ee 180: onsuccess: #642: 1: Success after binutils/gcc/linux/gl [...] discards 58f2703587 179: onsuccess: #641: 1: Success after binutils/gcc/linux/gd [...] discards bb32e8d34c 178: onsuccess: #640: 1: Success after binutils/gcc/linux/gd [...] discards 6ebeaacda8 177: onsuccess: #639: 1: Success after binutils/gcc/linux/gd [...] discards ca94c6996c 176: onsuccess: #638: 1: Success after binutils/gcc/linux/gd [...] discards d769b9ef95 175: onsuccess: #637: 1: Success after binutils/gcc/linux/gl [...] discards 81650794b5 174: onsuccess: #636: 1: Success after binutils/gcc/linux/gl [...] discards 78a6beeb14 173: onsuccess: #635: 1: Success after binutils/gcc/linux/gl [...] discards 6f745d2a27 172: onsuccess: #634: 1: Success after binutils/gcc/linux/gd [...] discards 3d31c8f8fd 171: onsuccess: #633: 1: Success after binutils/gcc/linux/gl [...] discards e0c4ab1938 170: onsuccess: #632: 1: Success after binutils/gcc/linux/gl [...] discards 481f62521f 169: onsuccess: #631: 1: Success after binutils/gcc/linux/gd [...] discards 1a63cf7af7 168: onsuccess: #630: 1: Success after binutils/gcc/linux/gd [...] discards 1b800cfa6f 167: onsuccess: #629: 1: Success after binutils/gcc/linux/gd [...] discards b12350560e 166: onsuccess: #628: 1: Success after binutils/gcc/linux/gl [...] discards b17f5ac79f 165: onsuccess: #627: 1: Success after binutils/gcc/linux/gl [...] discards 89db5fce43 164: onsuccess: #626: 1: Success after binutils/gcc/linux/gd [...] discards 7146b75b5e 163: onsuccess: #625: 1: Success after binutils/gcc/glibc/gd [...] discards 57254bca58 162: onsuccess: #624: 1: Success after linux: 10 commits discards e0d3f6d8e2 161: onsuccess: #623: 1: Success after glibc: 9 commits discards 6d42d353f7 160: onsuccess: #621: 1: Success after gcc: 11 commits discards e21ea5a4d5 159: onsuccess: #620: 1: Success after binutils: 12 commits discards b7e8a7dd1c 158: onsuccess: #618: 1: Success after binutils/gcc/linux/gd [...] discards a16968f89c 157: onsuccess: #617: 1: Success after binutils/gcc/linux/gd [...] discards 8629bf94e2 156: onsuccess: #616: 1: Success after binutils/gcc/linux/gl [...] discards 04d3819c9b 155: onsuccess: #615: 1: Success after binutils/gcc/linux/gd [...] discards 664e86fae9 154: onsuccess: #614: 1: Success after binutils/gcc/gdb: 14 commits discards d67c22e41e 153: onsuccess: #613: 1: Success after binutils/gcc/gdb: 40 commits discards cc8cc8cbfe 152: onsuccess: #612: 1: Success after binutils/gcc/gdb: 11 commits discards d1f4bcfd19 151: onsuccess: #611: 1: Success after binutils/gcc/linux/gd [...] new 12a8f8ca25 151: onsuccess: #611: 1: Success after binutils/gcc/linux/gd [...] new 3a2045a452 152: onsuccess: #612: 1: Success after binutils/gcc/gdb: 11 commits new 1d9c24e6c6 153: onsuccess: #613: 1: Success after binutils/gcc/gdb: 40 commits new 0f14afcc2b 154: onsuccess: #614: 1: Success after binutils/gcc/gdb: 14 commits new 500b5fc26a 155: onsuccess: #615: 1: Success after binutils/gcc/linux/gd [...] new 4e8e585562 156: onsuccess: #616: 1: Success after binutils/gcc/linux/gl [...] new 4b72c5abaa 157: onsuccess: #617: 1: Success after binutils/gcc/linux/gd [...] new 8d43ff5bbb 158: onsuccess: #618: 1: Success after binutils/gcc/linux/gd [...] new 22c8e833e4 159: onsuccess: #620: 1: Success after binutils: 12 commits new d0559e44a1 160: onsuccess: #621: 1: Success after gcc: 11 commits new 9a7551ba9b 161: onsuccess: #623: 1: Success after glibc: 9 commits new 45c48345b7 162: onsuccess: #624: 1: Success after linux: 10 commits new ab41e7a8f3 163: onsuccess: #625: 1: Success after binutils/gcc/glibc/gd [...] new 2e52ddfaae 164: onsuccess: #626: 1: Success after binutils/gcc/linux/gd [...] new 4b0cee7e3d 165: onsuccess: #627: 1: Success after binutils/gcc/linux/gl [...] new d58549c7c0 166: onsuccess: #628: 1: Success after binutils/gcc/linux/gl [...] new 4c572eaca5 167: onsuccess: #629: 1: Success after binutils/gcc/linux/gd [...] new eee3c3a755 168: onsuccess: #630: 1: Success after binutils/gcc/linux/gd [...] new 2d7c60e4c1 169: onsuccess: #631: 1: Success after binutils/gcc/linux/gd [...] new 3daeca5ced 170: onsuccess: #632: 1: Success after binutils/gcc/linux/gl [...] new bc2ae6eab8 171: onsuccess: #633: 1: Success after binutils/gcc/linux/gl [...] new a58016cf0d 172: onsuccess: #634: 1: Success after binutils/gcc/linux/gd [...] new 558960e794 173: onsuccess: #635: 1: Success after binutils/gcc/linux/gl [...] new 2cc1d09d95 174: onsuccess: #636: 1: Success after binutils/gcc/linux/gl [...] new 46e93a7e2d 175: onsuccess: #637: 1: Success after binutils/gcc/linux/gl [...] new 57ef7c1aa4 176: onsuccess: #638: 1: Success after binutils/gcc/linux/gd [...] new 88ef6a9905 177: onsuccess: #639: 1: Success after binutils/gcc/linux/gd [...] new 170999c125 178: onsuccess: #640: 1: Success after binutils/gcc/linux/gd [...] new 453d0f8c2f 179: onsuccess: #641: 1: Success after binutils/gcc/linux/gd [...] new ad8250d742 180: onsuccess: #642: 1: Success after binutils/gcc/linux/gl [...] new 4629df4f8a 181: onsuccess: #643: 1: Success after binutils/gcc/linux/gl [...] new d2e0e9b932 182: onsuccess: #644: 1: Success after binutils/gcc/gdb: 30 commits new 0f14cc8048 183: onsuccess: #645: 1: Success after binutils/gcc/gdb: 203 [...] new 656eba0569 184: onsuccess: #646: 1: Success after binutils/gcc/linux/gl [...] new 5cfbecafbc 185: onsuccess: #647: 1: Success after binutils/gcc/linux/gd [...] new 6df748be1a 186: onsuccess: #648: 1: Success after binutils/gcc/linux/gd [...] new b83813e39c 187: onsuccess: #649: 1: Success after binutils/gcc/linux/gl [...] new 9d8e29ef04 188: onsuccess: #650: 1: Success after binutils/gcc/linux/gl [...] new debe7eb86e 189: onsuccess: #651: 1: Success after binutils/gcc/linux/gl [...] new b6ab756963 190: onsuccess: #652: 1: Success after binutils/gcc/linux/gl [...] new 11bd1f8aa3 191: onsuccess: #653: 1: Success after binutils/gcc/linux/gl [...] new 759e2b28c6 192: onsuccess: #654: 1: Success after binutils/gcc/linux/gl [...] new 14a476ffd6 193: onsuccess: #655: 1: Success after binutils/gcc/linux/gd [...] new 023134a1c5 194: onsuccess: #656: 1: Success after binutils/gcc/linux/gl [...] new 4fd4fa8d40 195: onsuccess: #657: 1: Success after binutils/gcc/linux/gl [...] new 5be2a6ae19 196: onsuccess: #659: 1: Success after binutils/gcc/linux/gl [...] new de987426ae 197: onsuccess: #660: 1: Success after binutils/gcc/linux/gl [...] new f3f997bd48 198: onsuccess: #661: 1: Success after binutils/gcc/linux/gd [...] new 1d8c2f9cfc 199: onsuccess: #662: 1: Success after binutils/gcc/linux/gl [...] new 3d7153858a 200: onsuccess: #663: 1: Success after binutils/gcc/linux/gl [...] new 6db02e2a64 201: onsuccess: #664: 1: Success after binutils/gcc/glibc/gd [...] new 36e51dab99 202: onsuccess: #670: 1: Success after binutils/gcc/linux/gl [...] new 9b84651615 203: onsuccess: #671: 1: Success after binutils/gcc/linux/gd [...] new 6588a8419d 204: onsuccess: #672: 1: Success after binutils/gcc/linux/gl [...] new b2ba677e79 205: onsuccess: #1: 1: Success after binutils/gcc/linux/glib [...] new 8a0fb09135 206: onsuccess: #2: 1: Success after binutils/gcc/linux/glib [...] new a923cc7c0b 207: onsuccess: #3: 1: Success after binutils/gcc/linux/gdb: [...] new b88f0acca7 208: onsuccess: #4: 1: Success after binutils/gcc/linux/glib [...] new d1df33ba12 209: onsuccess: #5: 1: Success after binutils/gcc/linux/glib [...] new 6986df84ab 210: onsuccess: #6: 1: Success after binutils/gcc/linux/glib [...] new cf64835357 211: onsuccess: #7: 1: Success after binutils/gcc/linux/gdb: [...] new 185aa042c7 212: onsuccess: #8: 1: Success after binutils/gcc/linux/glib [...] new 066660d7b1 213: onsuccess: #9: 1: Success after binutils/gcc/linux/glib [...] new 4d9380a14a 214: onsuccess: #10: 1: Success after binutils/gcc/linux/gdb [...] new 01f18b19e5 215: onsuccess: #11: 1: Success after binutils/gcc/linux/gdb [...] new d14853bc9f 216: onsuccess: #12: 1: Success after binutils/gcc/linux/gli [...] new 4bb14fbb2d 217: onsuccess: #14: 1: Success after binutils/gcc/linux/gli [...] new 2208f54ef0 218: onsuccess: #15: 1: Success after binutils/gcc/linux/gli [...] new 4eaa2822ba 219: onsuccess: #16: 1: Success after binutils/gcc/linux/gli [...] new c64e064356 220: onsuccess: #17: 1: Success after binutils/gcc/linux/gli [...] new 1f6ff9f823 221: onsuccess: #18: 1: Success after binutils/gcc/linux/gdb [...] new 645ff1dd54 222: onsuccess: #19: 1: Success after binutils/gcc/linux/gli [...] new fdbd5d440f 223: onsuccess: #20: 1: Success after binutils/gcc/linux/gli [...] new 817ce61029 224: onsuccess: #21: 1: Success after binutils/gcc/linux/gli [...] new 02ce7fe984 225: onsuccess: #25: 1: Success after binutils/gcc/linux/gdb [...] new bbe986f1e6 226: onsuccess: #26: 1: Success after binutils/gcc/linux/gdb [...] new a34efacce4 227: onsuccess: #27: 1: Success after binutils/gcc/linux/gdb [...] new 085cf794a0 228: onsuccess: #28: 1: Success after binutils/gcc/linux/gli [...] new 2fce079e69 229: onsuccess: #29: 1: Success after binutils/gcc/linux/gdb [...] new 68aedacb03 230: onsuccess: #30: 1: Success after binutils/gcc/linux/gdb [...] new c3028acfc6 231: onsuccess: #31: 1: Success after binutils/gcc/linux/gdb [...] new b1d3bd33a5 232: onsuccess: #32: 1: Success after binutils/gcc/linux/gli [...] new d413a2bf63 233: onsuccess: #34: 1: [TCWG CI] Success after binutils/gcc [...] new 7badc05836 234: onsuccess: #35: 1: [TCWG CI] Success after binutils/gcc [...] new 741bf1374c 235: onsuccess: #36: 1: [TCWG CI] Success after binutils/gcc [...] new 1621053acc 236: onsuccess: #37: 1: [TCWG CI] Success after binutils/gcc [...] new 78f6123ea0 237: onsuccess: #38: 1: [TCWG CI] Success after binutils/gcc [...] new be88b9d9b6 238: onsuccess: #39: 1: [TCWG CI] Success after binutils/gcc [...] new f30be6dc59 239: onsuccess: #40: 1: [TCWG CI] Success after binutils/gcc [...] new 656d8ec381 240: onsuccess: #41: 1: [TCWG CI] Success after binutils/gcc [...] new 8a693e1f62 241: onsuccess: #42: 1: [TCWG CI] Success after binutils/gcc [...] new 736d6fe5b6 242: onsuccess: #44: 1: [TCWG CI] Success after binutils/gcc [...] new 15f3ed742e 243: onsuccess: #45: 1: [TCWG CI] Success after binutils/gcc [...] new 4a152623f5 244: onsuccess: #46: 1: [TCWG CI] Success after binutils/gcc [...] new 7fdc0abdfc 245: onsuccess: #48: 1: [TCWG CI] https://ci.linaro.org/job/ [...] new 65392ee993 246: onsuccess: #49: 1: [TCWG CI] https://ci.linaro.org/job/ [...] new 18a639f510 247: onsuccess: #50: 1: [TCWG CI] https://ci.linaro.org/job/ [...] new 4ce05a43eb 248: onsuccess: #51: 1: [TCWG CI] https://ci.linaro.org/job/ [...] new d38ea440be 249: onsuccess: #52: 1: [TCWG CI] https://ci.linaro.org/job/ [...] new cf727c23df 250: onsuccess: #53: 1: [TCWG CI] https://ci.linaro.org/job/ [...] new d85d34ae7e 251: onsuccess: #54: 1: [TCWG CI] https://ci.linaro.org/job/ [...] new 977ba87cfa 252: onsuccess: #55: 1: [TCWG CI] https://ci.linaro.org/job/ [...]

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 (393df78051) \ 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 2220 -> 2164 bytes 02-prepare_abe/console.log.xz | Bin 2456 -> 2488 bytes 03-build_abe-binutils/console.log.xz | Bin 50008 -> 48724 bytes 04-build_abe-gcc/console.log.xz | Bin 235756 -> 236040 bytes 05-clean_sysroot/console.log.xz | Bin 316 -> 316 bytes 06-build_abe-linux/console.log.xz | Bin 8300 -> 8288 bytes 07-build_abe-glibc/console.log.xz | Bin 232628 -> 232952 bytes 08-build_abe-gdb/console.log.xz | Bin 48200 -> 46544 bytes 09-build_abe-dejagnu/console.log.xz | Bin 3816 -> 3856 bytes 10-build_abe-check_gcc/console.log.xz | Bin 9640 -> 11544 bytes 11-check_regression/console.log.xz | Bin 1840 -> 2032 bytes 11-check_regression/results.compare | 52 +- 11-check_regression/results.compare2 | 73 +- 11-check_regression/results.regressions | 8 - 12-update_baseline/console.log | 46 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- git/gdb_rev | 2 +- git/glibc_rev | 2 +- jenkins/notify.sh | 2 +- mail/results.compare | 52 +- mail/results.regressions | 8 - manifest.sh | 30 +- results | 8 - sumfiles/g++.log.sep.xz | Bin 71140 -> 41260 bytes sumfiles/g++.log.xz | Bin 2915616 -> 2921388 bytes sumfiles/g++.sum | 18 +- sumfiles/g++.sum.sep | 8123 +++++++++++-------------------- sumfiles/gcc.log.sep.xz | Bin 83000 -> 63256 bytes sumfiles/gcc.log.xz | Bin 2481348 -> 2478844 bytes sumfiles/gcc.sum | 2 +- sumfiles/gcc.sum.sep | 7797 +++++++++++------------------ sumfiles/gfortran.log.sep.xz | Bin 29864 -> 15676 bytes sumfiles/gfortran.log.xz | Bin 953768 -> 954636 bytes sumfiles/gfortran.sum | 2 +- sumfiles/gfortran.sum.sep | 3080 ++++-------- sumfiles/libatomic.log.xz | Bin 2280 -> 2280 bytes sumfiles/libatomic.sum | 2 +- sumfiles/libgomp.log.xz | Bin 231092 -> 234040 bytes sumfiles/libgomp.sum | 25 +- sumfiles/libitm.log.xz | Bin 2688 -> 2696 bytes sumfiles/libitm.sum | 2 +- sumfiles/libstdc++.log.sep.xz | Bin 13568 -> 6604 bytes sumfiles/libstdc++.log.xz | Bin 472456 -> 482532 bytes sumfiles/libstdc++.sum | 4 +- sumfiles/libstdc++.sum.sep | 405 +- sumfiles/xfails.xfail | 0 47 files changed, 7168 insertions(+), 12579 deletions(-) delete mode 100644 11-check_regression/results.regressions delete mode 100644 mail/results.regressions create mode 100644 sumfiles/xfails.xfail