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 e0611710ad 254: onsuccess: #58: 1: [TCWG CI] https://ci.linaro.org/job/ [...] discards b4cf01029e 253: onsuccess: #56: 1: [TCWG CI] https://ci.linaro.org/job/ [...] discards eccaee545e 252: onsuccess: #55: 1: [TCWG CI] https://ci.linaro.org/job/ [...] discards 3ecdcbbc96 251: onsuccess: #54: 1: [TCWG CI] https://ci.linaro.org/job/ [...] discards 0178a35eac 250: onsuccess: #53: 1: [TCWG CI] https://ci.linaro.org/job/ [...] discards 234b91abca 249: onsuccess: #52: 1: [TCWG CI] https://ci.linaro.org/job/ [...] discards 7cf0b2b22a 248: onsuccess: #51: 1: [TCWG CI] https://ci.linaro.org/job/ [...] discards af573d98be 247: onsuccess: #50: 1: [TCWG CI] https://ci.linaro.org/job/ [...] discards 36337fb602 246: onsuccess: #49: 1: [TCWG CI] https://ci.linaro.org/job/ [...] discards 15efba4095 245: onsuccess: #48: 1: [TCWG CI] https://ci.linaro.org/job/ [...] discards 271bcd5044 244: onsuccess: #46: 1: [TCWG CI] Success after binutils/gcc [...] discards 1f84739193 243: onsuccess: #45: 1: [TCWG CI] Success after binutils/gcc [...] discards 213d2309b1 242: onsuccess: #44: 1: [TCWG CI] Success after binutils/gcc [...] discards abf0c171bd 241: onsuccess: #42: 1: [TCWG CI] Success after binutils/gcc [...] discards f190be6b48 240: onsuccess: #41: 1: [TCWG CI] Success after binutils/gcc [...] discards e428d2cac0 239: onsuccess: #40: 1: [TCWG CI] Success after binutils/gcc [...] discards ab758b866b 238: onsuccess: #39: 1: [TCWG CI] Success after binutils/gcc [...] discards e1ff8e1586 237: onsuccess: #38: 1: [TCWG CI] Success after binutils/gcc [...] discards 4d2bc90641 236: onsuccess: #37: 1: [TCWG CI] Success after binutils/gcc [...] discards 9ed87c4a62 235: onsuccess: #36: 1: [TCWG CI] Success after binutils/gcc [...] discards e5a7007985 234: onsuccess: #35: 1: [TCWG CI] Success after binutils/gcc [...] discards d825e6743e 233: onsuccess: #34: 1: [TCWG CI] Success after binutils/gcc [...] discards 7cbcee02c5 232: onsuccess: #32: 1: Success after binutils/gcc/linux/gli [...] discards bebef760cb 231: onsuccess: #31: 1: Success after binutils/gcc/linux/gdb [...] discards 0906b2a887 230: onsuccess: #30: 1: Success after binutils/gcc/linux/gdb [...] discards 2bc40e7d68 229: onsuccess: #29: 1: Success after binutils/gcc/linux/gdb [...] discards 46cdd5a96e 228: onsuccess: #28: 1: Success after binutils/gcc/linux/gli [...] discards 167f0411f1 227: onsuccess: #27: 1: Success after binutils/gcc/linux/gdb [...] discards 08185bafba 226: onsuccess: #26: 1: Success after binutils/gcc/linux/gdb [...] discards 89eb59260e 225: onsuccess: #25: 1: Success after binutils/gcc/linux/gdb [...] discards 3ad4642456 224: onsuccess: #21: 1: Success after binutils/gcc/linux/gli [...] discards 70e8875241 223: onsuccess: #20: 1: Success after binutils/gcc/linux/gli [...] discards 3ef70e6819 222: onsuccess: #19: 1: Success after binutils/gcc/linux/gli [...] discards da4cf1a4b2 221: onsuccess: #18: 1: Success after binutils/gcc/linux/gdb [...] discards 68de43f800 220: onsuccess: #17: 1: Success after binutils/gcc/linux/gli [...] discards c1f35d0544 219: onsuccess: #16: 1: Success after binutils/gcc/linux/gli [...] discards 0aa4c2dbfa 218: onsuccess: #15: 1: Success after binutils/gcc/linux/gli [...] discards 65d78ee939 217: onsuccess: #14: 1: Success after binutils/gcc/linux/gli [...] discards d72921d5e5 216: onsuccess: #12: 1: Success after binutils/gcc/linux/gli [...] discards 0ea1c6e767 215: onsuccess: #11: 1: Success after binutils/gcc/linux/gdb [...] discards 855e3fb6b3 214: onsuccess: #10: 1: Success after binutils/gcc/linux/gdb [...] discards a6a296551e 213: onsuccess: #9: 1: Success after binutils/gcc/linux/glib [...] discards 93a3887b0e 212: onsuccess: #8: 1: Success after binutils/gcc/linux/glib [...] discards f7cb154ff4 211: onsuccess: #7: 1: Success after binutils/gcc/linux/gdb: [...] discards 57036bf09c 210: onsuccess: #6: 1: Success after binutils/gcc/linux/glib [...] discards e2dcc127b1 209: onsuccess: #5: 1: Success after binutils/gcc/linux/glib [...] discards dc39167082 208: onsuccess: #4: 1: Success after binutils/gcc/linux/glib [...] discards 9bc00e417f 207: onsuccess: #3: 1: Success after binutils/gcc/linux/gdb: [...] discards f707ae1521 206: onsuccess: #2: 1: Success after binutils/gcc/linux/glib [...] discards 4acc46c5be 205: onsuccess: #1: 1: Success after binutils/gcc/linux/glib [...] discards dca317e61f 204: onsuccess: #672: 1: Success after binutils/gcc/linux/gl [...] discards 59784e1727 203: onsuccess: #671: 1: Success after binutils/gcc/linux/gd [...] discards 50d5be92d4 202: onsuccess: #670: 1: Success after binutils/gcc/linux/gl [...] discards dcfd8f8440 201: onsuccess: #664: 1: Success after binutils/gcc/glibc/gd [...] discards 14cdf4f753 200: onsuccess: #663: 1: Success after binutils/gcc/linux/gl [...] discards 0ad912456b 199: onsuccess: #662: 1: Success after binutils/gcc/linux/gl [...] discards 0594cee297 198: onsuccess: #661: 1: Success after binutils/gcc/linux/gd [...] discards 2550773e96 197: onsuccess: #660: 1: Success after binutils/gcc/linux/gl [...] discards e7366d3400 196: onsuccess: #659: 1: Success after binutils/gcc/linux/gl [...] discards ce0e4fe11e 195: onsuccess: #657: 1: Success after binutils/gcc/linux/gl [...] discards a11bfbab30 194: onsuccess: #656: 1: Success after binutils/gcc/linux/gl [...] discards ab8303e8b8 193: onsuccess: #655: 1: Success after binutils/gcc/linux/gd [...] discards 9114a389d7 192: onsuccess: #654: 1: Success after binutils/gcc/linux/gl [...] discards b2295b8a59 191: onsuccess: #653: 1: Success after binutils/gcc/linux/gl [...] discards b9eb38f4b7 190: onsuccess: #652: 1: Success after binutils/gcc/linux/gl [...] discards 74527e5c8e 189: onsuccess: #651: 1: Success after binutils/gcc/linux/gl [...] discards 0fc48a8c10 188: onsuccess: #650: 1: Success after binutils/gcc/linux/gl [...] discards 741376cca7 187: onsuccess: #649: 1: Success after binutils/gcc/linux/gl [...] discards 4427a5040c 186: onsuccess: #648: 1: Success after binutils/gcc/linux/gd [...] discards 19dc2d7e96 185: onsuccess: #647: 1: Success after binutils/gcc/linux/gd [...] discards 996cc03275 184: onsuccess: #646: 1: Success after binutils/gcc/linux/gl [...] discards b9868ae4ce 183: onsuccess: #645: 1: Success after binutils/gcc/gdb: 203 [...] discards e391797353 182: onsuccess: #644: 1: Success after binutils/gcc/gdb: 30 commits discards 487b8ed6af 181: onsuccess: #643: 1: Success after binutils/gcc/linux/gl [...] discards b711be134a 180: onsuccess: #642: 1: Success after binutils/gcc/linux/gl [...] discards ac4f90938b 179: onsuccess: #641: 1: Success after binutils/gcc/linux/gd [...] discards bc3de439f2 178: onsuccess: #640: 1: Success after binutils/gcc/linux/gd [...] discards 23418e5f81 177: onsuccess: #639: 1: Success after binutils/gcc/linux/gd [...] discards 287488eacf 176: onsuccess: #638: 1: Success after binutils/gcc/linux/gd [...] discards 02033b13d3 175: onsuccess: #637: 1: Success after binutils/gcc/linux/gl [...] discards b8a5d6043c 174: onsuccess: #636: 1: Success after binutils/gcc/linux/gl [...] discards ec635f8fa8 173: onsuccess: #635: 1: Success after binutils/gcc/linux/gl [...] discards c483417fc6 172: onsuccess: #634: 1: Success after binutils/gcc/linux/gd [...] discards 18a4231274 171: onsuccess: #633: 1: Success after binutils/gcc/linux/gl [...] discards 74d906ef94 170: onsuccess: #632: 1: Success after binutils/gcc/linux/gl [...] discards 3fa682e38c 169: onsuccess: #631: 1: Success after binutils/gcc/linux/gd [...] discards 275901611e 168: onsuccess: #630: 1: Success after binutils/gcc/linux/gd [...] discards d9e78743af 167: onsuccess: #629: 1: Success after binutils/gcc/linux/gd [...] discards 22fc65138f 166: onsuccess: #628: 1: Success after binutils/gcc/linux/gl [...] discards 76856aebe9 165: onsuccess: #627: 1: Success after binutils/gcc/linux/gl [...] discards dcf1fc9e61 164: onsuccess: #626: 1: Success after binutils/gcc/linux/gd [...] discards 3bc0c6e861 163: onsuccess: #625: 1: Success after binutils/gcc/glibc/gd [...] discards 8f28b21f9b 162: onsuccess: #624: 1: Success after linux: 10 commits discards 74b2fdfef5 161: onsuccess: #623: 1: Success after glibc: 9 commits discards 96d9311186 160: onsuccess: #621: 1: Success after gcc: 11 commits discards 37da9f1546 159: onsuccess: #620: 1: Success after binutils: 12 commits discards dc8808e1b7 158: onsuccess: #618: 1: Success after binutils/gcc/linux/gd [...] discards 161c323d5f 157: onsuccess: #617: 1: Success after binutils/gcc/linux/gd [...] discards 95184da4cc 156: onsuccess: #616: 1: Success after binutils/gcc/linux/gl [...] discards ed929b959d 155: onsuccess: #615: 1: Success after binutils/gcc/linux/gd [...] discards 3a02809279 154: onsuccess: #614: 1: Success after binutils/gcc/gdb: 14 commits new 8c94359a4e 154: onsuccess: #614: 1: Success after binutils/gcc/gdb: 14 commits new 24354c8a19 155: onsuccess: #615: 1: Success after binutils/gcc/linux/gd [...] new eda929dd97 156: onsuccess: #616: 1: Success after binutils/gcc/linux/gl [...] new b38368e826 157: onsuccess: #617: 1: Success after binutils/gcc/linux/gd [...] new 0a2312bf70 158: onsuccess: #618: 1: Success after binutils/gcc/linux/gd [...] new c57dc98e22 159: onsuccess: #620: 1: Success after binutils: 12 commits new 9eadc9438f 160: onsuccess: #621: 1: Success after gcc: 11 commits new d116a733a9 161: onsuccess: #623: 1: Success after glibc: 9 commits new b0e702866d 162: onsuccess: #624: 1: Success after linux: 10 commits new e051fdc8eb 163: onsuccess: #625: 1: Success after binutils/gcc/glibc/gd [...] new 89b55d6b68 164: onsuccess: #626: 1: Success after binutils/gcc/linux/gd [...] new c13b3eb3e6 165: onsuccess: #627: 1: Success after binutils/gcc/linux/gl [...] new ff561c8802 166: onsuccess: #628: 1: Success after binutils/gcc/linux/gl [...] new 81c9687ae2 167: onsuccess: #629: 1: Success after binutils/gcc/linux/gd [...] new d400a2a7e6 168: onsuccess: #630: 1: Success after binutils/gcc/linux/gd [...] new e6dc668d33 169: onsuccess: #631: 1: Success after binutils/gcc/linux/gd [...] new f8d5a2214e 170: onsuccess: #632: 1: Success after binutils/gcc/linux/gl [...] new 232ea63f62 171: onsuccess: #633: 1: Success after binutils/gcc/linux/gl [...] new f542a12bb3 172: onsuccess: #634: 1: Success after binutils/gcc/linux/gd [...] new 7b603c7788 173: onsuccess: #635: 1: Success after binutils/gcc/linux/gl [...] new a600bfcf64 174: onsuccess: #636: 1: Success after binutils/gcc/linux/gl [...] new 0e74be04a6 175: onsuccess: #637: 1: Success after binutils/gcc/linux/gl [...] new 724fc53faf 176: onsuccess: #638: 1: Success after binutils/gcc/linux/gd [...] new a2b2ca690b 177: onsuccess: #639: 1: Success after binutils/gcc/linux/gd [...] new 2171996e74 178: onsuccess: #640: 1: Success after binutils/gcc/linux/gd [...] new 305bfbe976 179: onsuccess: #641: 1: Success after binutils/gcc/linux/gd [...] new 126843a85c 180: onsuccess: #642: 1: Success after binutils/gcc/linux/gl [...] new d76e227b89 181: onsuccess: #643: 1: Success after binutils/gcc/linux/gl [...] new acd56246f9 182: onsuccess: #644: 1: Success after binutils/gcc/gdb: 30 commits new 5bb1af9ebb 183: onsuccess: #645: 1: Success after binutils/gcc/gdb: 203 [...] new 9f56a699db 184: onsuccess: #646: 1: Success after binutils/gcc/linux/gl [...] new d6c461e7f6 185: onsuccess: #647: 1: Success after binutils/gcc/linux/gd [...] new 645e165b37 186: onsuccess: #648: 1: Success after binutils/gcc/linux/gd [...] new 0094fe6854 187: onsuccess: #649: 1: Success after binutils/gcc/linux/gl [...] new a3246ed437 188: onsuccess: #650: 1: Success after binutils/gcc/linux/gl [...] new 32600a03e7 189: onsuccess: #651: 1: Success after binutils/gcc/linux/gl [...] new 98fab832fb 190: onsuccess: #652: 1: Success after binutils/gcc/linux/gl [...] new c75edafdfc 191: onsuccess: #653: 1: Success after binutils/gcc/linux/gl [...] new 7bd2cc5450 192: onsuccess: #654: 1: Success after binutils/gcc/linux/gl [...] new 363ace29cd 193: onsuccess: #655: 1: Success after binutils/gcc/linux/gd [...] new 912aafcb85 194: onsuccess: #656: 1: Success after binutils/gcc/linux/gl [...] new a5c5ed0387 195: onsuccess: #657: 1: Success after binutils/gcc/linux/gl [...] new 73817e4b04 196: onsuccess: #659: 1: Success after binutils/gcc/linux/gl [...] new 5480a54591 197: onsuccess: #660: 1: Success after binutils/gcc/linux/gl [...] new 021f905f3d 198: onsuccess: #661: 1: Success after binutils/gcc/linux/gd [...] new fadc0f2ad6 199: onsuccess: #662: 1: Success after binutils/gcc/linux/gl [...] new 3e1a153d91 200: onsuccess: #663: 1: Success after binutils/gcc/linux/gl [...] new 658e845d9d 201: onsuccess: #664: 1: Success after binutils/gcc/glibc/gd [...] new d330ce5e58 202: onsuccess: #670: 1: Success after binutils/gcc/linux/gl [...] new 61c57ffb5f 203: onsuccess: #671: 1: Success after binutils/gcc/linux/gd [...] new a7be22cb96 204: onsuccess: #672: 1: Success after binutils/gcc/linux/gl [...] new a60a4d1071 205: onsuccess: #1: 1: Success after binutils/gcc/linux/glib [...] new 804c170036 206: onsuccess: #2: 1: Success after binutils/gcc/linux/glib [...] new e70709e51f 207: onsuccess: #3: 1: Success after binutils/gcc/linux/gdb: [...] new 630205cd34 208: onsuccess: #4: 1: Success after binutils/gcc/linux/glib [...] new d9cff7ade8 209: onsuccess: #5: 1: Success after binutils/gcc/linux/glib [...] new 68dda73d63 210: onsuccess: #6: 1: Success after binutils/gcc/linux/glib [...] new 6846e7ef82 211: onsuccess: #7: 1: Success after binutils/gcc/linux/gdb: [...] new 25a1cf0cef 212: onsuccess: #8: 1: Success after binutils/gcc/linux/glib [...] new f6efd8fa25 213: onsuccess: #9: 1: Success after binutils/gcc/linux/glib [...] new 0c454a0de3 214: onsuccess: #10: 1: Success after binutils/gcc/linux/gdb [...] new 1d24a4e7b5 215: onsuccess: #11: 1: Success after binutils/gcc/linux/gdb [...] new dfcd47a0a9 216: onsuccess: #12: 1: Success after binutils/gcc/linux/gli [...] new 8e1ff3daa1 217: onsuccess: #14: 1: Success after binutils/gcc/linux/gli [...] new a545a02327 218: onsuccess: #15: 1: Success after binutils/gcc/linux/gli [...] new bd6b3d8540 219: onsuccess: #16: 1: Success after binutils/gcc/linux/gli [...] new 604286e7f7 220: onsuccess: #17: 1: Success after binutils/gcc/linux/gli [...] new 1e786318c9 221: onsuccess: #18: 1: Success after binutils/gcc/linux/gdb [...] new e330ffad84 222: onsuccess: #19: 1: Success after binutils/gcc/linux/gli [...] new d6a04fe409 223: onsuccess: #20: 1: Success after binutils/gcc/linux/gli [...] new 79694f4884 224: onsuccess: #21: 1: Success after binutils/gcc/linux/gli [...] new c008d7ee06 225: onsuccess: #25: 1: Success after binutils/gcc/linux/gdb [...] new fa24b75c16 226: onsuccess: #26: 1: Success after binutils/gcc/linux/gdb [...] new 060d7d1818 227: onsuccess: #27: 1: Success after binutils/gcc/linux/gdb [...] new a34f088022 228: onsuccess: #28: 1: Success after binutils/gcc/linux/gli [...] new caf8bb822d 229: onsuccess: #29: 1: Success after binutils/gcc/linux/gdb [...] new 07adfe9aaa 230: onsuccess: #30: 1: Success after binutils/gcc/linux/gdb [...] new 0cbd86d496 231: onsuccess: #31: 1: Success after binutils/gcc/linux/gdb [...] new 9dfbb4f5be 232: onsuccess: #32: 1: Success after binutils/gcc/linux/gli [...] new 667a76cbe0 233: onsuccess: #34: 1: [TCWG CI] Success after binutils/gcc [...] new 255abc9901 234: onsuccess: #35: 1: [TCWG CI] Success after binutils/gcc [...] new d55f880c3e 235: onsuccess: #36: 1: [TCWG CI] Success after binutils/gcc [...] new 0c3bda027a 236: onsuccess: #37: 1: [TCWG CI] Success after binutils/gcc [...] new 501b1acd4c 237: onsuccess: #38: 1: [TCWG CI] Success after binutils/gcc [...] new e63a6a1798 238: onsuccess: #39: 1: [TCWG CI] Success after binutils/gcc [...] new 1b5909cb8e 239: onsuccess: #40: 1: [TCWG CI] Success after binutils/gcc [...] new b1bb5b6de8 240: onsuccess: #41: 1: [TCWG CI] Success after binutils/gcc [...] new 1b60dc38ce 241: onsuccess: #42: 1: [TCWG CI] Success after binutils/gcc [...] new f7946b2315 242: onsuccess: #44: 1: [TCWG CI] Success after binutils/gcc [...] new dc0c5422c4 243: onsuccess: #45: 1: [TCWG CI] Success after binutils/gcc [...] new 03a034bc03 244: onsuccess: #46: 1: [TCWG CI] Success after binutils/gcc [...] new 332d9f6cae 245: onsuccess: #48: 1: [TCWG CI] https://ci.linaro.org/job/ [...] new 486da7a7b5 246: onsuccess: #49: 1: [TCWG CI] https://ci.linaro.org/job/ [...] new fad7d905dc 247: onsuccess: #50: 1: [TCWG CI] https://ci.linaro.org/job/ [...] new 1ad82c510f 248: onsuccess: #51: 1: [TCWG CI] https://ci.linaro.org/job/ [...] new 023aa7f562 249: onsuccess: #52: 1: [TCWG CI] https://ci.linaro.org/job/ [...] new c6ca978794 250: onsuccess: #53: 1: [TCWG CI] https://ci.linaro.org/job/ [...] new 6dabd9dd7d 251: onsuccess: #54: 1: [TCWG CI] https://ci.linaro.org/job/ [...] new fd749a1db4 252: onsuccess: #55: 1: [TCWG CI] https://ci.linaro.org/job/ [...] new 092b800666 253: onsuccess: #56: 1: [TCWG CI] https://ci.linaro.org/job/ [...] new 2653352f32 254: onsuccess: #58: 1: [TCWG CI] https://ci.linaro.org/job/ [...] new 56070be82f 255: force: #61: 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 (e0611710ad) \ 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.xz | Bin 2879628 -> 2920008 bytes 00-sumfiles/gcc.log.xz | Bin 2492296 -> 2496280 bytes 00-sumfiles/gfortran.log.xz | Bin 962320 -> 970864 bytes 00-sumfiles/libatomic.log.xz | Bin 2292 -> 2280 bytes 00-sumfiles/libgomp.log.xz | Bin 233952 -> 233920 bytes 00-sumfiles/libitm.log.xz | Bin 2688 -> 2684 bytes 00-sumfiles/libstdc++.log.xz | Bin 471360 -> 482252 bytes 01-reset_artifacts/console.log.xz | Bin 1960 -> 2196 bytes 02-prepare_abe/console.log.xz | Bin 2444 -> 2460 bytes 03-build_abe-binutils/console.log.xz | Bin 49480 -> 49512 bytes 04-build_abe-gcc/console.log.xz | Bin 239704 -> 237096 bytes 05-clean_sysroot/console.log.xz | Bin 316 -> 316 bytes 06-build_abe-linux/console.log.xz | Bin 8624 -> 8744 bytes 07-build_abe-glibc/console.log.xz | Bin 234580 -> 234572 bytes 08-build_abe-gdb/console.log.xz | Bin 47264 -> 47560 bytes 09-build_abe-dejagnu/console.log.xz | Bin 3816 -> 3828 bytes 10-build_abe-check_gcc/console.log.xz | Bin 7884 -> 8664 bytes 10-build_abe-check_gcc/flaky.xfail | 2 +- 11-check_regression/console.log.xz | Bin 1276 -> 1280 bytes 11-check_regression/results.compare | 18 +++++++------- 11-check_regression/results.compare2 | 6 ++--- 12-update_baseline/console.log | 44 +++++++++++++++++----------------- git/gcc_rev | 2 +- jenkins/notify.sh | 2 +- mail/results.compare | 18 +++++++------- manifest.sh | 22 ++++++++--------- sumfiles/g++.sum | 2 +- sumfiles/gcc.sum | 2 +- sumfiles/gfortran.sum | 2 +- sumfiles/libatomic.sum | 2 +- sumfiles/libgomp.sum | 2 +- sumfiles/libitm.sum | 2 +- 32 files changed, 62 insertions(+), 64 deletions(-)