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 56070be82f 255: force: #61: 1: [TCWG CI] https://ci.linaro.org/job/tcwg [...] discards 2653352f32 254: onsuccess: #58: 1: [TCWG CI] https://ci.linaro.org/job/ [...] discards 092b800666 253: onsuccess: #56: 1: [TCWG CI] https://ci.linaro.org/job/ [...] discards fd749a1db4 252: onsuccess: #55: 1: [TCWG CI] https://ci.linaro.org/job/ [...] discards 6dabd9dd7d 251: onsuccess: #54: 1: [TCWG CI] https://ci.linaro.org/job/ [...] discards c6ca978794 250: onsuccess: #53: 1: [TCWG CI] https://ci.linaro.org/job/ [...] discards 023aa7f562 249: onsuccess: #52: 1: [TCWG CI] https://ci.linaro.org/job/ [...] discards 1ad82c510f 248: onsuccess: #51: 1: [TCWG CI] https://ci.linaro.org/job/ [...] discards fad7d905dc 247: onsuccess: #50: 1: [TCWG CI] https://ci.linaro.org/job/ [...] discards 486da7a7b5 246: onsuccess: #49: 1: [TCWG CI] https://ci.linaro.org/job/ [...] discards 332d9f6cae 245: onsuccess: #48: 1: [TCWG CI] https://ci.linaro.org/job/ [...] discards 03a034bc03 244: onsuccess: #46: 1: [TCWG CI] Success after binutils/gcc [...] discards dc0c5422c4 243: onsuccess: #45: 1: [TCWG CI] Success after binutils/gcc [...] discards f7946b2315 242: onsuccess: #44: 1: [TCWG CI] Success after binutils/gcc [...] discards 1b60dc38ce 241: onsuccess: #42: 1: [TCWG CI] Success after binutils/gcc [...] discards b1bb5b6de8 240: onsuccess: #41: 1: [TCWG CI] Success after binutils/gcc [...] discards 1b5909cb8e 239: onsuccess: #40: 1: [TCWG CI] Success after binutils/gcc [...] discards e63a6a1798 238: onsuccess: #39: 1: [TCWG CI] Success after binutils/gcc [...] discards 501b1acd4c 237: onsuccess: #38: 1: [TCWG CI] Success after binutils/gcc [...] discards 0c3bda027a 236: onsuccess: #37: 1: [TCWG CI] Success after binutils/gcc [...] discards d55f880c3e 235: onsuccess: #36: 1: [TCWG CI] Success after binutils/gcc [...] discards 255abc9901 234: onsuccess: #35: 1: [TCWG CI] Success after binutils/gcc [...] discards 667a76cbe0 233: onsuccess: #34: 1: [TCWG CI] Success after binutils/gcc [...] discards 9dfbb4f5be 232: onsuccess: #32: 1: Success after binutils/gcc/linux/gli [...] discards 0cbd86d496 231: onsuccess: #31: 1: Success after binutils/gcc/linux/gdb [...] discards 07adfe9aaa 230: onsuccess: #30: 1: Success after binutils/gcc/linux/gdb [...] discards caf8bb822d 229: onsuccess: #29: 1: Success after binutils/gcc/linux/gdb [...] discards a34f088022 228: onsuccess: #28: 1: Success after binutils/gcc/linux/gli [...] discards 060d7d1818 227: onsuccess: #27: 1: Success after binutils/gcc/linux/gdb [...] discards fa24b75c16 226: onsuccess: #26: 1: Success after binutils/gcc/linux/gdb [...] discards c008d7ee06 225: onsuccess: #25: 1: Success after binutils/gcc/linux/gdb [...] discards 79694f4884 224: onsuccess: #21: 1: Success after binutils/gcc/linux/gli [...] discards d6a04fe409 223: onsuccess: #20: 1: Success after binutils/gcc/linux/gli [...] discards e330ffad84 222: onsuccess: #19: 1: Success after binutils/gcc/linux/gli [...] discards 1e786318c9 221: onsuccess: #18: 1: Success after binutils/gcc/linux/gdb [...] discards 604286e7f7 220: onsuccess: #17: 1: Success after binutils/gcc/linux/gli [...] discards bd6b3d8540 219: onsuccess: #16: 1: Success after binutils/gcc/linux/gli [...] discards a545a02327 218: onsuccess: #15: 1: Success after binutils/gcc/linux/gli [...] discards 8e1ff3daa1 217: onsuccess: #14: 1: Success after binutils/gcc/linux/gli [...] discards dfcd47a0a9 216: onsuccess: #12: 1: Success after binutils/gcc/linux/gli [...] discards 1d24a4e7b5 215: onsuccess: #11: 1: Success after binutils/gcc/linux/gdb [...] discards 0c454a0de3 214: onsuccess: #10: 1: Success after binutils/gcc/linux/gdb [...] discards f6efd8fa25 213: onsuccess: #9: 1: Success after binutils/gcc/linux/glib [...] discards 25a1cf0cef 212: onsuccess: #8: 1: Success after binutils/gcc/linux/glib [...] discards 6846e7ef82 211: onsuccess: #7: 1: Success after binutils/gcc/linux/gdb: [...] discards 68dda73d63 210: onsuccess: #6: 1: Success after binutils/gcc/linux/glib [...] discards d9cff7ade8 209: onsuccess: #5: 1: Success after binutils/gcc/linux/glib [...] discards 630205cd34 208: onsuccess: #4: 1: Success after binutils/gcc/linux/glib [...] discards e70709e51f 207: onsuccess: #3: 1: Success after binutils/gcc/linux/gdb: [...] discards 804c170036 206: onsuccess: #2: 1: Success after binutils/gcc/linux/glib [...] discards a60a4d1071 205: onsuccess: #1: 1: Success after binutils/gcc/linux/glib [...] discards a7be22cb96 204: onsuccess: #672: 1: Success after binutils/gcc/linux/gl [...] discards 61c57ffb5f 203: onsuccess: #671: 1: Success after binutils/gcc/linux/gd [...] discards d330ce5e58 202: onsuccess: #670: 1: Success after binutils/gcc/linux/gl [...] discards 658e845d9d 201: onsuccess: #664: 1: Success after binutils/gcc/glibc/gd [...] discards 3e1a153d91 200: onsuccess: #663: 1: Success after binutils/gcc/linux/gl [...] discards fadc0f2ad6 199: onsuccess: #662: 1: Success after binutils/gcc/linux/gl [...] discards 021f905f3d 198: onsuccess: #661: 1: Success after binutils/gcc/linux/gd [...] discards 5480a54591 197: onsuccess: #660: 1: Success after binutils/gcc/linux/gl [...] discards 73817e4b04 196: onsuccess: #659: 1: Success after binutils/gcc/linux/gl [...] discards a5c5ed0387 195: onsuccess: #657: 1: Success after binutils/gcc/linux/gl [...] discards 912aafcb85 194: onsuccess: #656: 1: Success after binutils/gcc/linux/gl [...] discards 363ace29cd 193: onsuccess: #655: 1: Success after binutils/gcc/linux/gd [...] discards 7bd2cc5450 192: onsuccess: #654: 1: Success after binutils/gcc/linux/gl [...] discards c75edafdfc 191: onsuccess: #653: 1: Success after binutils/gcc/linux/gl [...] discards 98fab832fb 190: onsuccess: #652: 1: Success after binutils/gcc/linux/gl [...] discards 32600a03e7 189: onsuccess: #651: 1: Success after binutils/gcc/linux/gl [...] discards a3246ed437 188: onsuccess: #650: 1: Success after binutils/gcc/linux/gl [...] discards 0094fe6854 187: onsuccess: #649: 1: Success after binutils/gcc/linux/gl [...] discards 645e165b37 186: onsuccess: #648: 1: Success after binutils/gcc/linux/gd [...] discards d6c461e7f6 185: onsuccess: #647: 1: Success after binutils/gcc/linux/gd [...] discards 9f56a699db 184: onsuccess: #646: 1: Success after binutils/gcc/linux/gl [...] discards 5bb1af9ebb 183: onsuccess: #645: 1: Success after binutils/gcc/gdb: 203 [...] discards acd56246f9 182: onsuccess: #644: 1: Success after binutils/gcc/gdb: 30 commits discards d76e227b89 181: onsuccess: #643: 1: Success after binutils/gcc/linux/gl [...] discards 126843a85c 180: onsuccess: #642: 1: Success after binutils/gcc/linux/gl [...] discards 305bfbe976 179: onsuccess: #641: 1: Success after binutils/gcc/linux/gd [...] discards 2171996e74 178: onsuccess: #640: 1: Success after binutils/gcc/linux/gd [...] discards a2b2ca690b 177: onsuccess: #639: 1: Success after binutils/gcc/linux/gd [...] discards 724fc53faf 176: onsuccess: #638: 1: Success after binutils/gcc/linux/gd [...] discards 0e74be04a6 175: onsuccess: #637: 1: Success after binutils/gcc/linux/gl [...] discards a600bfcf64 174: onsuccess: #636: 1: Success after binutils/gcc/linux/gl [...] discards 7b603c7788 173: onsuccess: #635: 1: Success after binutils/gcc/linux/gl [...] discards f542a12bb3 172: onsuccess: #634: 1: Success after binutils/gcc/linux/gd [...] discards 232ea63f62 171: onsuccess: #633: 1: Success after binutils/gcc/linux/gl [...] discards f8d5a2214e 170: onsuccess: #632: 1: Success after binutils/gcc/linux/gl [...] discards e6dc668d33 169: onsuccess: #631: 1: Success after binutils/gcc/linux/gd [...] discards d400a2a7e6 168: onsuccess: #630: 1: Success after binutils/gcc/linux/gd [...] discards 81c9687ae2 167: onsuccess: #629: 1: Success after binutils/gcc/linux/gd [...] discards ff561c8802 166: onsuccess: #628: 1: Success after binutils/gcc/linux/gl [...] discards c13b3eb3e6 165: onsuccess: #627: 1: Success after binutils/gcc/linux/gl [...] discards 89b55d6b68 164: onsuccess: #626: 1: Success after binutils/gcc/linux/gd [...] discards e051fdc8eb 163: onsuccess: #625: 1: Success after binutils/gcc/glibc/gd [...] discards b0e702866d 162: onsuccess: #624: 1: Success after linux: 10 commits discards d116a733a9 161: onsuccess: #623: 1: Success after glibc: 9 commits discards 9eadc9438f 160: onsuccess: #621: 1: Success after gcc: 11 commits discards c57dc98e22 159: onsuccess: #620: 1: Success after binutils: 12 commits discards 0a2312bf70 158: onsuccess: #618: 1: Success after binutils/gcc/linux/gd [...] discards b38368e826 157: onsuccess: #617: 1: Success after binutils/gcc/linux/gd [...] discards eda929dd97 156: onsuccess: #616: 1: Success after binutils/gcc/linux/gl [...] discards 24354c8a19 155: onsuccess: #615: 1: Success after binutils/gcc/linux/gd [...] new 01a09ebe8d 155: onsuccess: #615: 1: Success after binutils/gcc/linux/gd [...] new 3bacb8455f 156: onsuccess: #616: 1: Success after binutils/gcc/linux/gl [...] new 7b1125dc67 157: onsuccess: #617: 1: Success after binutils/gcc/linux/gd [...] new 58a1c7c0e5 158: onsuccess: #618: 1: Success after binutils/gcc/linux/gd [...] new 9ee1761774 159: onsuccess: #620: 1: Success after binutils: 12 commits new 9faf402549 160: onsuccess: #621: 1: Success after gcc: 11 commits new 8e60bdd613 161: onsuccess: #623: 1: Success after glibc: 9 commits new 796d064ee5 162: onsuccess: #624: 1: Success after linux: 10 commits new 7b38e86cdc 163: onsuccess: #625: 1: Success after binutils/gcc/glibc/gd [...] new 0cc613d78f 164: onsuccess: #626: 1: Success after binutils/gcc/linux/gd [...] new 5f9aec0a82 165: onsuccess: #627: 1: Success after binutils/gcc/linux/gl [...] new 56c0eb010b 166: onsuccess: #628: 1: Success after binutils/gcc/linux/gl [...] new e2e462d8f9 167: onsuccess: #629: 1: Success after binutils/gcc/linux/gd [...] new f0449a9e75 168: onsuccess: #630: 1: Success after binutils/gcc/linux/gd [...] new 07c13dc104 169: onsuccess: #631: 1: Success after binutils/gcc/linux/gd [...] new 6964b4cadb 170: onsuccess: #632: 1: Success after binutils/gcc/linux/gl [...] new 03c5fe99dc 171: onsuccess: #633: 1: Success after binutils/gcc/linux/gl [...] new a3201b59b6 172: onsuccess: #634: 1: Success after binutils/gcc/linux/gd [...] new a4d2758793 173: onsuccess: #635: 1: Success after binutils/gcc/linux/gl [...] new 7b22d2bad2 174: onsuccess: #636: 1: Success after binutils/gcc/linux/gl [...] new 08aed8612f 175: onsuccess: #637: 1: Success after binutils/gcc/linux/gl [...] new 3f27e3a85f 176: onsuccess: #638: 1: Success after binutils/gcc/linux/gd [...] new 4d6a7af6b7 177: onsuccess: #639: 1: Success after binutils/gcc/linux/gd [...] new 6edfa1f48e 178: onsuccess: #640: 1: Success after binutils/gcc/linux/gd [...] new 421301b219 179: onsuccess: #641: 1: Success after binutils/gcc/linux/gd [...] new 7b16dc4b21 180: onsuccess: #642: 1: Success after binutils/gcc/linux/gl [...] new a545d81032 181: onsuccess: #643: 1: Success after binutils/gcc/linux/gl [...] new 2d7a8562f7 182: onsuccess: #644: 1: Success after binutils/gcc/gdb: 30 commits new fb299e5271 183: onsuccess: #645: 1: Success after binutils/gcc/gdb: 203 [...] new 27dccfd5c8 184: onsuccess: #646: 1: Success after binutils/gcc/linux/gl [...] new 517a04f7d0 185: onsuccess: #647: 1: Success after binutils/gcc/linux/gd [...] new 5724910c28 186: onsuccess: #648: 1: Success after binutils/gcc/linux/gd [...] new 4f2e5fd104 187: onsuccess: #649: 1: Success after binutils/gcc/linux/gl [...] new 4c46b86949 188: onsuccess: #650: 1: Success after binutils/gcc/linux/gl [...] new 2ffe41812d 189: onsuccess: #651: 1: Success after binutils/gcc/linux/gl [...] new 92cd0e968c 190: onsuccess: #652: 1: Success after binutils/gcc/linux/gl [...] new f14699a84a 191: onsuccess: #653: 1: Success after binutils/gcc/linux/gl [...] new 9b1af96c71 192: onsuccess: #654: 1: Success after binutils/gcc/linux/gl [...] new 96fed4b2f8 193: onsuccess: #655: 1: Success after binutils/gcc/linux/gd [...] new 2bb0fa94c2 194: onsuccess: #656: 1: Success after binutils/gcc/linux/gl [...] new 0204b66910 195: onsuccess: #657: 1: Success after binutils/gcc/linux/gl [...] new 12ce250c6a 196: onsuccess: #659: 1: Success after binutils/gcc/linux/gl [...] new ce6260e001 197: onsuccess: #660: 1: Success after binutils/gcc/linux/gl [...] new ad5fa5b9a3 198: onsuccess: #661: 1: Success after binutils/gcc/linux/gd [...] new 07e43ae73a 199: onsuccess: #662: 1: Success after binutils/gcc/linux/gl [...] new 8800e53309 200: onsuccess: #663: 1: Success after binutils/gcc/linux/gl [...] new 2ab967f537 201: onsuccess: #664: 1: Success after binutils/gcc/glibc/gd [...] new 1d01b7e743 202: onsuccess: #670: 1: Success after binutils/gcc/linux/gl [...] new 3034408f55 203: onsuccess: #671: 1: Success after binutils/gcc/linux/gd [...] new 65594cd3a9 204: onsuccess: #672: 1: Success after binutils/gcc/linux/gl [...] new f3cccaa05f 205: onsuccess: #1: 1: Success after binutils/gcc/linux/glib [...] new 0e1df82ea4 206: onsuccess: #2: 1: Success after binutils/gcc/linux/glib [...] new 9095773652 207: onsuccess: #3: 1: Success after binutils/gcc/linux/gdb: [...] new d4a95349ce 208: onsuccess: #4: 1: Success after binutils/gcc/linux/glib [...] new 47a66a791a 209: onsuccess: #5: 1: Success after binutils/gcc/linux/glib [...] new 5fd19d654e 210: onsuccess: #6: 1: Success after binutils/gcc/linux/glib [...] new b487449529 211: onsuccess: #7: 1: Success after binutils/gcc/linux/gdb: [...] new de2e16add9 212: onsuccess: #8: 1: Success after binutils/gcc/linux/glib [...] new 9d674633a6 213: onsuccess: #9: 1: Success after binutils/gcc/linux/glib [...] new 4d7c2eefed 214: onsuccess: #10: 1: Success after binutils/gcc/linux/gdb [...] new 0bac340289 215: onsuccess: #11: 1: Success after binutils/gcc/linux/gdb [...] new ac95e7c45c 216: onsuccess: #12: 1: Success after binutils/gcc/linux/gli [...] new f2cf036241 217: onsuccess: #14: 1: Success after binutils/gcc/linux/gli [...] new 15ebff2187 218: onsuccess: #15: 1: Success after binutils/gcc/linux/gli [...] new 64c87dc370 219: onsuccess: #16: 1: Success after binutils/gcc/linux/gli [...] new 7ed0d8fa91 220: onsuccess: #17: 1: Success after binutils/gcc/linux/gli [...] new b24eb9d5ad 221: onsuccess: #18: 1: Success after binutils/gcc/linux/gdb [...] new 9662a7496e 222: onsuccess: #19: 1: Success after binutils/gcc/linux/gli [...] new 3e8091d323 223: onsuccess: #20: 1: Success after binutils/gcc/linux/gli [...] new bf3d580d0f 224: onsuccess: #21: 1: Success after binutils/gcc/linux/gli [...] new f014dd5a48 225: onsuccess: #25: 1: Success after binutils/gcc/linux/gdb [...] new 3bdd0deaf3 226: onsuccess: #26: 1: Success after binutils/gcc/linux/gdb [...] new 5990f5ea85 227: onsuccess: #27: 1: Success after binutils/gcc/linux/gdb [...] new 4039e20942 228: onsuccess: #28: 1: Success after binutils/gcc/linux/gli [...] new aa3199aa8a 229: onsuccess: #29: 1: Success after binutils/gcc/linux/gdb [...] new 93a0a937f7 230: onsuccess: #30: 1: Success after binutils/gcc/linux/gdb [...] new 8831ddb4ed 231: onsuccess: #31: 1: Success after binutils/gcc/linux/gdb [...] new 07b46ad0c7 232: onsuccess: #32: 1: Success after binutils/gcc/linux/gli [...] new f2d4056a01 233: onsuccess: #34: 1: [TCWG CI] Success after binutils/gcc [...] new e36874899d 234: onsuccess: #35: 1: [TCWG CI] Success after binutils/gcc [...] new 7ef54f36c7 235: onsuccess: #36: 1: [TCWG CI] Success after binutils/gcc [...] new 5212452f8b 236: onsuccess: #37: 1: [TCWG CI] Success after binutils/gcc [...] new 0f089363c9 237: onsuccess: #38: 1: [TCWG CI] Success after binutils/gcc [...] new ba56e2a0fb 238: onsuccess: #39: 1: [TCWG CI] Success after binutils/gcc [...] new 1fb4a4ddc6 239: onsuccess: #40: 1: [TCWG CI] Success after binutils/gcc [...] new ffc38e0234 240: onsuccess: #41: 1: [TCWG CI] Success after binutils/gcc [...] new e651944249 241: onsuccess: #42: 1: [TCWG CI] Success after binutils/gcc [...] new 62578f22ac 242: onsuccess: #44: 1: [TCWG CI] Success after binutils/gcc [...] new 10b2420f01 243: onsuccess: #45: 1: [TCWG CI] Success after binutils/gcc [...] new 6539861d19 244: onsuccess: #46: 1: [TCWG CI] Success after binutils/gcc [...] new bd86cbfd92 245: onsuccess: #48: 1: [TCWG CI] https://ci.linaro.org/job/ [...] new ecfd46fcbb 246: onsuccess: #49: 1: [TCWG CI] https://ci.linaro.org/job/ [...] new 5984c602ac 247: onsuccess: #50: 1: [TCWG CI] https://ci.linaro.org/job/ [...] new d718d0cc35 248: onsuccess: #51: 1: [TCWG CI] https://ci.linaro.org/job/ [...] new 5ffd0ca884 249: onsuccess: #52: 1: [TCWG CI] https://ci.linaro.org/job/ [...] new fb30da706b 250: onsuccess: #53: 1: [TCWG CI] https://ci.linaro.org/job/ [...] new abbbf7fa37 251: onsuccess: #54: 1: [TCWG CI] https://ci.linaro.org/job/ [...] new dddbebcf88 252: onsuccess: #55: 1: [TCWG CI] https://ci.linaro.org/job/ [...] new d6744cc206 253: onsuccess: #56: 1: [TCWG CI] https://ci.linaro.org/job/ [...] new eaa7cd2a33 254: onsuccess: #58: 1: [TCWG CI] https://ci.linaro.org/job/ [...] new 3d2201e5e4 255: force: #61: 1: [TCWG CI] https://ci.linaro.org/job/tcwg [...] new d25c633887 256: force: #62: 1: [TCWG CI] https://ci.linaro.org/job/tcwg [...]

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 (56070be82f) \ 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 0 -> 2919876 bytes 00-sumfiles/g++.log.1.xz | Bin 0 -> 1700884 bytes 00-sumfiles/g++.log.xz | Bin 2920008 -> 0 bytes sumfiles/g++.sum => 00-sumfiles/g++.sum.0 | 18 +- sumfiles/g++.sum => 00-sumfiles/g++.sum.1 | 102837 +----------------- 00-sumfiles/gcc.log.0.xz | Bin 0 -> 2485700 bytes 00-sumfiles/gcc.log.xz | Bin 2496280 -> 0 bytes sumfiles/gcc.sum => 00-sumfiles/gcc.sum.0 | 2 +- 00-sumfiles/gfortran.log.0.xz | Bin 0 -> 962264 bytes 00-sumfiles/gfortran.log.xz | Bin 970864 -> 0 bytes .../gfortran.sum => 00-sumfiles/gfortran.sum.0 | 2 +- 00-sumfiles/libatomic.log.0.xz | Bin 0 -> 2284 bytes 00-sumfiles/libatomic.log.xz | Bin 2280 -> 0 bytes .../libatomic.sum => 00-sumfiles/libatomic.sum.0 | 2 +- 00-sumfiles/libgomp.log.0.xz | Bin 0 -> 233812 bytes 00-sumfiles/libgomp.log.xz | Bin 233920 -> 0 bytes sumfiles/libgomp.sum => 00-sumfiles/libgomp.sum.0 | 2 +- 00-sumfiles/libitm.log.0.xz | Bin 0 -> 2688 bytes 00-sumfiles/libitm.log.xz | Bin 2684 -> 0 bytes sumfiles/libitm.sum => 00-sumfiles/libitm.sum.0 | 2 +- 00-sumfiles/libstdc++.log.0.xz | Bin 0 -> 480568 bytes 00-sumfiles/libstdc++.log.xz | Bin 482252 -> 0 bytes .../libstdc++.sum => 00-sumfiles/libstdc++.sum.0 | 0 01-reset_artifacts/console.log.xz | Bin 2196 -> 2200 bytes 02-prepare_abe/console.log.xz | Bin 2460 -> 2404 bytes 03-build_abe-binutils/console.log.xz | Bin 49512 -> 49236 bytes 04-build_abe-gcc/console.log.xz | Bin 237096 -> 236352 bytes 05-clean_sysroot/console.log.xz | Bin 316 -> 316 bytes 06-build_abe-linux/console.log.xz | Bin 8744 -> 8592 bytes 07-build_abe-glibc/console.log.xz | Bin 234572 -> 232936 bytes 08-build_abe-gdb/console.log.xz | Bin 47560 -> 46588 bytes 09-build_abe-dejagnu/console.log.xz | Bin 3828 -> 3804 bytes 10-build_abe-check_gcc/console.log.xz | Bin 8664 -> 8076 bytes 10-build_abe-check_gcc/flaky.xfail | 2 +- 11-check_regression/console.log.xz | Bin 1280 -> 2448 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 | 49 +- 11-check_regression/results.regressions | 20 + 11-check_regression/trigger-bisect | 3 + 11-check_regression/trigger-notify | 0 12-update_baseline/console.log | 52 +- git/gcc_rev | 2 +- jenkins/notify.sh | 2 +- mail/check-regression-status.txt | 2 +- mail/results.compare | 31 +- mail/results.regressions | 20 + manifest.sh | 16 +- results | 20 + sumfiles/g++.sum | 22 +- sumfiles/gcc.sum | 6 +- sumfiles/gfortran.sum | 6 +- sumfiles/libatomic.sum | 6 +- sumfiles/libgomp.sum | 6 +- sumfiles/libitm.sum | 6 +- sumfiles/libstdc++.sum | 4 + 57 files changed, 270 insertions(+), 102910 deletions(-) create mode 100644 00-sumfiles/g++.log.0.xz create mode 100644 00-sumfiles/g++.log.1.xz delete mode 100644 00-sumfiles/g++.log.xz copy sumfiles/g++.sum => 00-sumfiles/g++.sum.0 (99%) copy sumfiles/g++.sum => 00-sumfiles/g++.sum.1 (55%) create mode 100644 00-sumfiles/gcc.log.0.xz delete mode 100644 00-sumfiles/gcc.log.xz copy sumfiles/gcc.sum => 00-sumfiles/gcc.sum.0 (99%) create mode 100644 00-sumfiles/gfortran.log.0.xz delete mode 100644 00-sumfiles/gfortran.log.xz copy sumfiles/gfortran.sum => 00-sumfiles/gfortran.sum.0 (99%) create mode 100644 00-sumfiles/libatomic.log.0.xz delete mode 100644 00-sumfiles/libatomic.log.xz copy sumfiles/libatomic.sum => 00-sumfiles/libatomic.sum.0 (98%) create mode 100644 00-sumfiles/libgomp.log.0.xz delete mode 100644 00-sumfiles/libgomp.log.xz copy sumfiles/libgomp.sum => 00-sumfiles/libgomp.sum.0 (99%) create mode 100644 00-sumfiles/libitm.log.0.xz delete mode 100644 00-sumfiles/libitm.log.xz copy sumfiles/libitm.sum => 00-sumfiles/libitm.sum.0 (97%) create mode 100644 00-sumfiles/libstdc++.log.0.xz delete mode 100644 00-sumfiles/libstdc++.log.xz copy sumfiles/libstdc++.sum => 00-sumfiles/libstdc++.sum.0 (100%) create mode 100644 11-check_regression/extra-bisect-params create mode 100644 11-check_regression/fails.sum create mode 100644 11-check_regression/results.regressions create mode 100644 11-check_regression/trigger-bisect create mode 100644 11-check_regression/trigger-notify create mode 100644 mail/results.regressions