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 d25c633887 256: force: #62: 1: [TCWG CI] https://ci.linaro.org/job/tcwg [...] discards 3d2201e5e4 255: force: #61: 1: [TCWG CI] https://ci.linaro.org/job/tcwg [...] discards eaa7cd2a33 254: onsuccess: #58: 1: [TCWG CI] https://ci.linaro.org/job/ [...] discards d6744cc206 253: onsuccess: #56: 1: [TCWG CI] https://ci.linaro.org/job/ [...] discards dddbebcf88 252: onsuccess: #55: 1: [TCWG CI] https://ci.linaro.org/job/ [...] discards abbbf7fa37 251: onsuccess: #54: 1: [TCWG CI] https://ci.linaro.org/job/ [...] discards fb30da706b 250: onsuccess: #53: 1: [TCWG CI] https://ci.linaro.org/job/ [...] discards 5ffd0ca884 249: onsuccess: #52: 1: [TCWG CI] https://ci.linaro.org/job/ [...] discards d718d0cc35 248: onsuccess: #51: 1: [TCWG CI] https://ci.linaro.org/job/ [...] discards 5984c602ac 247: onsuccess: #50: 1: [TCWG CI] https://ci.linaro.org/job/ [...] discards ecfd46fcbb 246: onsuccess: #49: 1: [TCWG CI] https://ci.linaro.org/job/ [...] discards bd86cbfd92 245: onsuccess: #48: 1: [TCWG CI] https://ci.linaro.org/job/ [...] discards 6539861d19 244: onsuccess: #46: 1: [TCWG CI] Success after binutils/gcc [...] discards 10b2420f01 243: onsuccess: #45: 1: [TCWG CI] Success after binutils/gcc [...] discards 62578f22ac 242: onsuccess: #44: 1: [TCWG CI] Success after binutils/gcc [...] discards e651944249 241: onsuccess: #42: 1: [TCWG CI] Success after binutils/gcc [...] discards ffc38e0234 240: onsuccess: #41: 1: [TCWG CI] Success after binutils/gcc [...] discards 1fb4a4ddc6 239: onsuccess: #40: 1: [TCWG CI] Success after binutils/gcc [...] discards ba56e2a0fb 238: onsuccess: #39: 1: [TCWG CI] Success after binutils/gcc [...] discards 0f089363c9 237: onsuccess: #38: 1: [TCWG CI] Success after binutils/gcc [...] discards 5212452f8b 236: onsuccess: #37: 1: [TCWG CI] Success after binutils/gcc [...] discards 7ef54f36c7 235: onsuccess: #36: 1: [TCWG CI] Success after binutils/gcc [...] discards e36874899d 234: onsuccess: #35: 1: [TCWG CI] Success after binutils/gcc [...] discards f2d4056a01 233: onsuccess: #34: 1: [TCWG CI] Success after binutils/gcc [...] discards 07b46ad0c7 232: onsuccess: #32: 1: Success after binutils/gcc/linux/gli [...] discards 8831ddb4ed 231: onsuccess: #31: 1: Success after binutils/gcc/linux/gdb [...] discards 93a0a937f7 230: onsuccess: #30: 1: Success after binutils/gcc/linux/gdb [...] discards aa3199aa8a 229: onsuccess: #29: 1: Success after binutils/gcc/linux/gdb [...] discards 4039e20942 228: onsuccess: #28: 1: Success after binutils/gcc/linux/gli [...] discards 5990f5ea85 227: onsuccess: #27: 1: Success after binutils/gcc/linux/gdb [...] discards 3bdd0deaf3 226: onsuccess: #26: 1: Success after binutils/gcc/linux/gdb [...] discards f014dd5a48 225: onsuccess: #25: 1: Success after binutils/gcc/linux/gdb [...] discards bf3d580d0f 224: onsuccess: #21: 1: Success after binutils/gcc/linux/gli [...] discards 3e8091d323 223: onsuccess: #20: 1: Success after binutils/gcc/linux/gli [...] discards 9662a7496e 222: onsuccess: #19: 1: Success after binutils/gcc/linux/gli [...] discards b24eb9d5ad 221: onsuccess: #18: 1: Success after binutils/gcc/linux/gdb [...] discards 7ed0d8fa91 220: onsuccess: #17: 1: Success after binutils/gcc/linux/gli [...] discards 64c87dc370 219: onsuccess: #16: 1: Success after binutils/gcc/linux/gli [...] discards 15ebff2187 218: onsuccess: #15: 1: Success after binutils/gcc/linux/gli [...] discards f2cf036241 217: onsuccess: #14: 1: Success after binutils/gcc/linux/gli [...] discards ac95e7c45c 216: onsuccess: #12: 1: Success after binutils/gcc/linux/gli [...] discards 0bac340289 215: onsuccess: #11: 1: Success after binutils/gcc/linux/gdb [...] discards 4d7c2eefed 214: onsuccess: #10: 1: Success after binutils/gcc/linux/gdb [...] discards 9d674633a6 213: onsuccess: #9: 1: Success after binutils/gcc/linux/glib [...] discards de2e16add9 212: onsuccess: #8: 1: Success after binutils/gcc/linux/glib [...] discards b487449529 211: onsuccess: #7: 1: Success after binutils/gcc/linux/gdb: [...] discards 5fd19d654e 210: onsuccess: #6: 1: Success after binutils/gcc/linux/glib [...] discards 47a66a791a 209: onsuccess: #5: 1: Success after binutils/gcc/linux/glib [...] discards d4a95349ce 208: onsuccess: #4: 1: Success after binutils/gcc/linux/glib [...] discards 9095773652 207: onsuccess: #3: 1: Success after binutils/gcc/linux/gdb: [...] discards 0e1df82ea4 206: onsuccess: #2: 1: Success after binutils/gcc/linux/glib [...] discards f3cccaa05f 205: onsuccess: #1: 1: Success after binutils/gcc/linux/glib [...] discards 65594cd3a9 204: onsuccess: #672: 1: Success after binutils/gcc/linux/gl [...] discards 3034408f55 203: onsuccess: #671: 1: Success after binutils/gcc/linux/gd [...] discards 1d01b7e743 202: onsuccess: #670: 1: Success after binutils/gcc/linux/gl [...] discards 2ab967f537 201: onsuccess: #664: 1: Success after binutils/gcc/glibc/gd [...] discards 8800e53309 200: onsuccess: #663: 1: Success after binutils/gcc/linux/gl [...] discards 07e43ae73a 199: onsuccess: #662: 1: Success after binutils/gcc/linux/gl [...] discards ad5fa5b9a3 198: onsuccess: #661: 1: Success after binutils/gcc/linux/gd [...] discards ce6260e001 197: onsuccess: #660: 1: Success after binutils/gcc/linux/gl [...] discards 12ce250c6a 196: onsuccess: #659: 1: Success after binutils/gcc/linux/gl [...] discards 0204b66910 195: onsuccess: #657: 1: Success after binutils/gcc/linux/gl [...] discards 2bb0fa94c2 194: onsuccess: #656: 1: Success after binutils/gcc/linux/gl [...] discards 96fed4b2f8 193: onsuccess: #655: 1: Success after binutils/gcc/linux/gd [...] discards 9b1af96c71 192: onsuccess: #654: 1: Success after binutils/gcc/linux/gl [...] discards f14699a84a 191: onsuccess: #653: 1: Success after binutils/gcc/linux/gl [...] discards 92cd0e968c 190: onsuccess: #652: 1: Success after binutils/gcc/linux/gl [...] discards 2ffe41812d 189: onsuccess: #651: 1: Success after binutils/gcc/linux/gl [...] discards 4c46b86949 188: onsuccess: #650: 1: Success after binutils/gcc/linux/gl [...] discards 4f2e5fd104 187: onsuccess: #649: 1: Success after binutils/gcc/linux/gl [...] discards 5724910c28 186: onsuccess: #648: 1: Success after binutils/gcc/linux/gd [...] discards 517a04f7d0 185: onsuccess: #647: 1: Success after binutils/gcc/linux/gd [...] discards 27dccfd5c8 184: onsuccess: #646: 1: Success after binutils/gcc/linux/gl [...] discards fb299e5271 183: onsuccess: #645: 1: Success after binutils/gcc/gdb: 203 [...] discards 2d7a8562f7 182: onsuccess: #644: 1: Success after binutils/gcc/gdb: 30 commits discards a545d81032 181: onsuccess: #643: 1: Success after binutils/gcc/linux/gl [...] discards 7b16dc4b21 180: onsuccess: #642: 1: Success after binutils/gcc/linux/gl [...] discards 421301b219 179: onsuccess: #641: 1: Success after binutils/gcc/linux/gd [...] discards 6edfa1f48e 178: onsuccess: #640: 1: Success after binutils/gcc/linux/gd [...] discards 4d6a7af6b7 177: onsuccess: #639: 1: Success after binutils/gcc/linux/gd [...] discards 3f27e3a85f 176: onsuccess: #638: 1: Success after binutils/gcc/linux/gd [...] discards 08aed8612f 175: onsuccess: #637: 1: Success after binutils/gcc/linux/gl [...] discards 7b22d2bad2 174: onsuccess: #636: 1: Success after binutils/gcc/linux/gl [...] discards a4d2758793 173: onsuccess: #635: 1: Success after binutils/gcc/linux/gl [...] discards a3201b59b6 172: onsuccess: #634: 1: Success after binutils/gcc/linux/gd [...] discards 03c5fe99dc 171: onsuccess: #633: 1: Success after binutils/gcc/linux/gl [...] discards 6964b4cadb 170: onsuccess: #632: 1: Success after binutils/gcc/linux/gl [...] discards 07c13dc104 169: onsuccess: #631: 1: Success after binutils/gcc/linux/gd [...] discards f0449a9e75 168: onsuccess: #630: 1: Success after binutils/gcc/linux/gd [...] discards e2e462d8f9 167: onsuccess: #629: 1: Success after binutils/gcc/linux/gd [...] discards 56c0eb010b 166: onsuccess: #628: 1: Success after binutils/gcc/linux/gl [...] discards 5f9aec0a82 165: onsuccess: #627: 1: Success after binutils/gcc/linux/gl [...] discards 0cc613d78f 164: onsuccess: #626: 1: Success after binutils/gcc/linux/gd [...] discards 7b38e86cdc 163: onsuccess: #625: 1: Success after binutils/gcc/glibc/gd [...] discards 796d064ee5 162: onsuccess: #624: 1: Success after linux: 10 commits discards 8e60bdd613 161: onsuccess: #623: 1: Success after glibc: 9 commits discards 9faf402549 160: onsuccess: #621: 1: Success after gcc: 11 commits discards 9ee1761774 159: onsuccess: #620: 1: Success after binutils: 12 commits discards 58a1c7c0e5 158: onsuccess: #618: 1: Success after binutils/gcc/linux/gd [...] discards 7b1125dc67 157: onsuccess: #617: 1: Success after binutils/gcc/linux/gd [...] discards 3bacb8455f 156: onsuccess: #616: 1: Success after binutils/gcc/linux/gl [...] new c72c2c3afd 156: onsuccess: #616: 1: Success after binutils/gcc/linux/gl [...] new ee568258f5 157: onsuccess: #617: 1: Success after binutils/gcc/linux/gd [...] new 5f58849101 158: onsuccess: #618: 1: Success after binutils/gcc/linux/gd [...] new e09bfb5bff 159: onsuccess: #620: 1: Success after binutils: 12 commits new 6b0f683982 160: onsuccess: #621: 1: Success after gcc: 11 commits new 366f7d1903 161: onsuccess: #623: 1: Success after glibc: 9 commits new 376b34e4eb 162: onsuccess: #624: 1: Success after linux: 10 commits new 93b6ecd6f4 163: onsuccess: #625: 1: Success after binutils/gcc/glibc/gd [...] new e65ba89da7 164: onsuccess: #626: 1: Success after binutils/gcc/linux/gd [...] new 90b8c38904 165: onsuccess: #627: 1: Success after binutils/gcc/linux/gl [...] new 8a58e1ffe1 166: onsuccess: #628: 1: Success after binutils/gcc/linux/gl [...] new 0c112f909c 167: onsuccess: #629: 1: Success after binutils/gcc/linux/gd [...] new 5463b2cb6e 168: onsuccess: #630: 1: Success after binutils/gcc/linux/gd [...] new 710ac02688 169: onsuccess: #631: 1: Success after binutils/gcc/linux/gd [...] new 3e94897128 170: onsuccess: #632: 1: Success after binutils/gcc/linux/gl [...] new b611e818c6 171: onsuccess: #633: 1: Success after binutils/gcc/linux/gl [...] new c6cc1b3f93 172: onsuccess: #634: 1: Success after binutils/gcc/linux/gd [...] new 36f67f66d6 173: onsuccess: #635: 1: Success after binutils/gcc/linux/gl [...] new 6bc3077c89 174: onsuccess: #636: 1: Success after binutils/gcc/linux/gl [...] new 5be8598f5e 175: onsuccess: #637: 1: Success after binutils/gcc/linux/gl [...] new f5aef5c848 176: onsuccess: #638: 1: Success after binutils/gcc/linux/gd [...] new ad5f8a3865 177: onsuccess: #639: 1: Success after binutils/gcc/linux/gd [...] new 2007c4fa07 178: onsuccess: #640: 1: Success after binutils/gcc/linux/gd [...] new a8a6b087db 179: onsuccess: #641: 1: Success after binutils/gcc/linux/gd [...] new 5dc4d6c6e8 180: onsuccess: #642: 1: Success after binutils/gcc/linux/gl [...] new 11206fce48 181: onsuccess: #643: 1: Success after binutils/gcc/linux/gl [...] new eeaac198a1 182: onsuccess: #644: 1: Success after binutils/gcc/gdb: 30 commits new 80cf0d6212 183: onsuccess: #645: 1: Success after binutils/gcc/gdb: 203 [...] new 0fdf57e0a9 184: onsuccess: #646: 1: Success after binutils/gcc/linux/gl [...] new 3d799f18db 185: onsuccess: #647: 1: Success after binutils/gcc/linux/gd [...] new b28da36530 186: onsuccess: #648: 1: Success after binutils/gcc/linux/gd [...] new f8a9ae4c0c 187: onsuccess: #649: 1: Success after binutils/gcc/linux/gl [...] new 3485c3cf30 188: onsuccess: #650: 1: Success after binutils/gcc/linux/gl [...] new 823e6d2e03 189: onsuccess: #651: 1: Success after binutils/gcc/linux/gl [...] new 1260ffe703 190: onsuccess: #652: 1: Success after binutils/gcc/linux/gl [...] new 0012040f4d 191: onsuccess: #653: 1: Success after binutils/gcc/linux/gl [...] new d1416bdbb3 192: onsuccess: #654: 1: Success after binutils/gcc/linux/gl [...] new 0493ffa79a 193: onsuccess: #655: 1: Success after binutils/gcc/linux/gd [...] new c739563a50 194: onsuccess: #656: 1: Success after binutils/gcc/linux/gl [...] new 99dac1a671 195: onsuccess: #657: 1: Success after binutils/gcc/linux/gl [...] new c5c7431395 196: onsuccess: #659: 1: Success after binutils/gcc/linux/gl [...] new d1e669234d 197: onsuccess: #660: 1: Success after binutils/gcc/linux/gl [...] new 3cb2aa4da7 198: onsuccess: #661: 1: Success after binutils/gcc/linux/gd [...] new c0d763945a 199: onsuccess: #662: 1: Success after binutils/gcc/linux/gl [...] new 2c5d319430 200: onsuccess: #663: 1: Success after binutils/gcc/linux/gl [...] new 4099700ec5 201: onsuccess: #664: 1: Success after binutils/gcc/glibc/gd [...] new d7f0a22245 202: onsuccess: #670: 1: Success after binutils/gcc/linux/gl [...] new 559c947de3 203: onsuccess: #671: 1: Success after binutils/gcc/linux/gd [...] new 1a4d724c15 204: onsuccess: #672: 1: Success after binutils/gcc/linux/gl [...] new 4e6aea7a20 205: onsuccess: #1: 1: Success after binutils/gcc/linux/glib [...] new eaeff9d4a7 206: onsuccess: #2: 1: Success after binutils/gcc/linux/glib [...] new 2a2261ebd7 207: onsuccess: #3: 1: Success after binutils/gcc/linux/gdb: [...] new 6a25439d58 208: onsuccess: #4: 1: Success after binutils/gcc/linux/glib [...] new dce68a944f 209: onsuccess: #5: 1: Success after binutils/gcc/linux/glib [...] new 8038d1137f 210: onsuccess: #6: 1: Success after binutils/gcc/linux/glib [...] new 9ee03e349f 211: onsuccess: #7: 1: Success after binutils/gcc/linux/gdb: [...] new 63d06f2830 212: onsuccess: #8: 1: Success after binutils/gcc/linux/glib [...] new e12f22da88 213: onsuccess: #9: 1: Success after binutils/gcc/linux/glib [...] new b8f094f1ed 214: onsuccess: #10: 1: Success after binutils/gcc/linux/gdb [...] new 4d66debb08 215: onsuccess: #11: 1: Success after binutils/gcc/linux/gdb [...] new 74a3e4c6d0 216: onsuccess: #12: 1: Success after binutils/gcc/linux/gli [...] new fd70c3d2ca 217: onsuccess: #14: 1: Success after binutils/gcc/linux/gli [...] new 811df5d82b 218: onsuccess: #15: 1: Success after binutils/gcc/linux/gli [...] new 4b6180a398 219: onsuccess: #16: 1: Success after binutils/gcc/linux/gli [...] new 465582386d 220: onsuccess: #17: 1: Success after binutils/gcc/linux/gli [...] new 1a0007c578 221: onsuccess: #18: 1: Success after binutils/gcc/linux/gdb [...] new 1571478897 222: onsuccess: #19: 1: Success after binutils/gcc/linux/gli [...] new d2c8b5fc71 223: onsuccess: #20: 1: Success after binutils/gcc/linux/gli [...] new 16270c57ce 224: onsuccess: #21: 1: Success after binutils/gcc/linux/gli [...] new 716772cabb 225: onsuccess: #25: 1: Success after binutils/gcc/linux/gdb [...] new aee10d9cac 226: onsuccess: #26: 1: Success after binutils/gcc/linux/gdb [...] new 861a014190 227: onsuccess: #27: 1: Success after binutils/gcc/linux/gdb [...] new f275957e4b 228: onsuccess: #28: 1: Success after binutils/gcc/linux/gli [...] new 778d19605e 229: onsuccess: #29: 1: Success after binutils/gcc/linux/gdb [...] new c0b0a98a65 230: onsuccess: #30: 1: Success after binutils/gcc/linux/gdb [...] new 834c8fb358 231: onsuccess: #31: 1: Success after binutils/gcc/linux/gdb [...] new 362ee1c784 232: onsuccess: #32: 1: Success after binutils/gcc/linux/gli [...] new ac4405beae 233: onsuccess: #34: 1: [TCWG CI] Success after binutils/gcc [...] new 86ac501b7f 234: onsuccess: #35: 1: [TCWG CI] Success after binutils/gcc [...] new bb313d4e26 235: onsuccess: #36: 1: [TCWG CI] Success after binutils/gcc [...] new 58a8f8a206 236: onsuccess: #37: 1: [TCWG CI] Success after binutils/gcc [...] new 1cde2cbb80 237: onsuccess: #38: 1: [TCWG CI] Success after binutils/gcc [...] new ee74426886 238: onsuccess: #39: 1: [TCWG CI] Success after binutils/gcc [...] new e4e38045a9 239: onsuccess: #40: 1: [TCWG CI] Success after binutils/gcc [...] new 0e77e9e692 240: onsuccess: #41: 1: [TCWG CI] Success after binutils/gcc [...] new 51ceaaaa4c 241: onsuccess: #42: 1: [TCWG CI] Success after binutils/gcc [...] new 38f99c7fb7 242: onsuccess: #44: 1: [TCWG CI] Success after binutils/gcc [...] new c85977ed2b 243: onsuccess: #45: 1: [TCWG CI] Success after binutils/gcc [...] new ae56a15bf1 244: onsuccess: #46: 1: [TCWG CI] Success after binutils/gcc [...] new acf4c69eea 245: onsuccess: #48: 1: [TCWG CI] https://ci.linaro.org/job/ [...] new 00186cd87e 246: onsuccess: #49: 1: [TCWG CI] https://ci.linaro.org/job/ [...] new 9224c36afa 247: onsuccess: #50: 1: [TCWG CI] https://ci.linaro.org/job/ [...] new e9002014f7 248: onsuccess: #51: 1: [TCWG CI] https://ci.linaro.org/job/ [...] new c67325ed9e 249: onsuccess: #52: 1: [TCWG CI] https://ci.linaro.org/job/ [...] new cb0c4058d6 250: onsuccess: #53: 1: [TCWG CI] https://ci.linaro.org/job/ [...] new 874c925aac 251: onsuccess: #54: 1: [TCWG CI] https://ci.linaro.org/job/ [...] new 55ced848c6 252: onsuccess: #55: 1: [TCWG CI] https://ci.linaro.org/job/ [...] new b3f3e83461 253: onsuccess: #56: 1: [TCWG CI] https://ci.linaro.org/job/ [...] new 3b399ba1d5 254: onsuccess: #58: 1: [TCWG CI] https://ci.linaro.org/job/ [...] new d4ab1b0447 255: force: #61: 1: [TCWG CI] https://ci.linaro.org/job/tcwg [...] new 924bd27eec 256: force: #62: 1: [TCWG CI] https://ci.linaro.org/job/tcwg [...] new cd3a4febd5 257: onsuccess: #63: 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 (d25c633887) \ 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: 00-sumfiles/g++.log.0.xz | Bin 2919876 -> 0 bytes 00-sumfiles/g++.log.1.xz | Bin 1700884 -> 0 bytes 00-sumfiles/g++.log.xz | Bin 0 -> 2887568 bytes 00-sumfiles/g++.sum.0 | 252204 ----------------------------- 00-sumfiles/g++.sum.1 | 149387 ----------------- 00-sumfiles/gcc.log.0.xz | Bin 2485700 -> 0 bytes 00-sumfiles/gcc.log.xz | Bin 0 -> 2517984 bytes 00-sumfiles/gcc.sum.0 | 184724 --------------------- 00-sumfiles/gfortran.log.0.xz | Bin 962264 -> 0 bytes 00-sumfiles/gfortran.log.xz | Bin 0 -> 956624 bytes 00-sumfiles/gfortran.sum.0 | 67080 -------- 00-sumfiles/libatomic.log.0.xz | Bin 2284 -> 0 bytes 00-sumfiles/libatomic.log.xz | Bin 0 -> 2280 bytes 00-sumfiles/libatomic.sum.0 | 64 - 00-sumfiles/libgomp.log.0.xz | Bin 233812 -> 0 bytes 00-sumfiles/libgomp.log.xz | Bin 0 -> 234296 bytes 00-sumfiles/libgomp.sum.0 | 16021 -- 00-sumfiles/libitm.log.0.xz | Bin 2688 -> 0 bytes 00-sumfiles/libitm.log.xz | Bin 0 -> 2688 bytes 00-sumfiles/libitm.sum.0 | 65 - 00-sumfiles/libstdc++.log.0.xz | Bin 480568 -> 0 bytes 00-sumfiles/libstdc++.log.xz | Bin 0 -> 479756 bytes 00-sumfiles/libstdc++.sum.0 | 16507 -- 01-reset_artifacts/console.log.xz | Bin 2200 -> 2180 bytes 02-prepare_abe/console.log.xz | Bin 2404 -> 2452 bytes 03-build_abe-binutils/console.log.xz | Bin 49236 -> 49344 bytes 04-build_abe-gcc/console.log.xz | Bin 236352 -> 235480 bytes 05-clean_sysroot/console.log.xz | Bin 316 -> 316 bytes 06-build_abe-linux/console.log.xz | Bin 8592 -> 8616 bytes 07-build_abe-glibc/console.log.xz | Bin 232936 -> 233636 bytes 08-build_abe-gdb/console.log.xz | Bin 46588 -> 46748 bytes 09-build_abe-dejagnu/console.log.xz | Bin 3804 -> 3864 bytes 10-build_abe-check_gcc/console.log.xz | Bin 8076 -> 8016 bytes 10-build_abe-check_gcc/flaky.xfail | 2 +- 11-check_regression/console.log.xz | Bin 2448 -> 1664 bytes 11-check_regression/extra-bisect-params | 1 - 11-check_regression/fails.sum | 8 - 11-check_regression/results.compare | 31 +- 11-check_regression/results.compare2 | 73 +- 11-check_regression/results.regressions | 20 - 11-check_regression/trigger-bisect | 3 - 11-check_regression/trigger-notify | 0 12-update_baseline/console.log | 54 +- git/gcc_rev | 2 +- jenkins/notify.sh | 2 +- mail/check-regression-status.txt | 2 +- mail/results.compare | 31 +- mail/results.regressions | 20 - manifest.sh | 18 +- results | 20 - sumfiles/g++.sum | 14 +- sumfiles/gcc.sum | 6 +- sumfiles/gfortran.sum | 20 +- sumfiles/libatomic.sum | 6 +- sumfiles/libgomp.sum | 6 +- sumfiles/libitm.sum | 6 +- sumfiles/libstdc++.sum | 4 - sumfiles/xfails.xfail | 3 + 58 files changed, 125 insertions(+), 686279 deletions(-) delete mode 100644 00-sumfiles/g++.log.0.xz delete mode 100644 00-sumfiles/g++.log.1.xz create mode 100644 00-sumfiles/g++.log.xz delete mode 100644 00-sumfiles/g++.sum.0 delete mode 100644 00-sumfiles/g++.sum.1 delete mode 100644 00-sumfiles/gcc.log.0.xz create mode 100644 00-sumfiles/gcc.log.xz delete mode 100644 00-sumfiles/gcc.sum.0 delete mode 100644 00-sumfiles/gfortran.log.0.xz create mode 100644 00-sumfiles/gfortran.log.xz delete mode 100644 00-sumfiles/gfortran.sum.0 delete mode 100644 00-sumfiles/libatomic.log.0.xz create mode 100644 00-sumfiles/libatomic.log.xz delete mode 100644 00-sumfiles/libatomic.sum.0 delete mode 100644 00-sumfiles/libgomp.log.0.xz create mode 100644 00-sumfiles/libgomp.log.xz delete mode 100644 00-sumfiles/libgomp.sum.0 delete mode 100644 00-sumfiles/libitm.log.0.xz create mode 100644 00-sumfiles/libitm.log.xz delete mode 100644 00-sumfiles/libitm.sum.0 delete mode 100644 00-sumfiles/libstdc++.log.0.xz create mode 100644 00-sumfiles/libstdc++.log.xz delete mode 100644 00-sumfiles/libstdc++.sum.0 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 delete mode 100644 11-check_regression/trigger-bisect delete mode 100644 11-check_regression/trigger-notify delete mode 100644 mail/results.regressions