This is an automated email from the git hooks/post-receive script.
tcwg-buildslave pushed a change to branch linaro-local/ci/tcwg_gnu_cross_check_gcc/master-arm in repository toolchain/ci/base-artifacts.
discards 34f0e05581 303: onsuccess: #2120: 1: Success after binutils/gdb: 20 commits discards 648baa29d8 302: onsuccess: #2119: 1: Success after binutils/gdb: 7 commits discards bc55972ba7 301: onsuccess: #2118: 1: Success after linux: 16 commits discards 176d281f7c 300: onsuccess: #2117: 1: Success after basepoints/gcc-13-49 [...] discards 040cc17381 299: onsuccess: #2116: 1: Success after gdb-13-branchpoint-2 [...] discards c873cad3ec 298: onsuccess: #2114: 1: Success after binutils/gcc/gdb: 6 commits discards 04f3b2d97d 297: onsuccess: #2113: 1: Success after binutils/gcc/gdb: 7 commits discards 8177706aa8 296: onsuccess: #2112: 1: Success after gcc/linux: 26 commits discards 6f020e290a 295: onsuccess: #2111: 1: Success after binutils/gcc/linux/g [...] discards 7e95ca4d95 294: onsuccess: #2110: 1: Success after gcc: 17 commits discards eaa50f05c8 293: onsuccess: #2109: 1: Success after binutils/gdb: 2 commits discards a637e3e9ac 292: onsuccess: #2108: 1: Success after binutils/gcc/gdb: 3 commits discards 31c0922f25 291: onsuccess: #2107: 1: Success after binutils/gcc/gdb: 6 commits discards a30970553a 290: onsuccess: #2106: 1: Success after gcc: 2 commits discards 868920080f 289: onsuccess: #2105: 1: Success after binutils/gcc/gdb: 6 commits discards 56bc36a199 288: onsuccess: #2104: 1: Success after binutils/gcc/gdb: 10 [...] discards 9443038452 287: onsuccess: #2103: 1: Success after gcc: 9 commits discards f7b304f259 286: onsuccess: #2102: 1: Success after binutils/gdb: 18 commits discards 241362b366 285: onsuccess: #2101: 1: Success after binutils/gcc/gdb: 5 commits discards 6c884921d1 284: onsuccess: #2100: 1: Success after basepoints/gcc-13-48 [...] discards 95789c4880 283: onsuccess: #2099: 1: Success after binutils/gdb: 4 commits discards 0c5eb0d426 282: onsuccess: #2098: 1: Success after binutils/gcc/linux/g [...] discards c345e415e0 281: onsuccess: #2097: 1: Success after binutils/gcc/gdb: 23 [...] discards ade089a2e1 280: onsuccess: #2096: 1: Success after binutils/gcc/gdb: 21 [...] discards d9d56a83d9 279: onsuccess: #2095: 1: Success after binutils/gcc/gdb: 5 commits discards 000bf3297f 278: onsuccess: #2094: 1: Success after binutils/gcc/linux/g [...] discards 8584678567 277: onsuccess: #2093: 1: Success after binutils/gcc/linux/g [...] discards 59ac783bcd 276: onsuccess: #2092: 1: Success after binutils/gcc/gdb: 69 [...] discards 1cde065112 275: onsuccess: #2091: 1: Success after binutils/gcc/gdb: 42 [...] discards 03f0d663ca 274: onsuccess: #2090: 1: Success after binutils/gcc/linux/g [...] discards a5af2110d4 273: onsuccess: #2089: 1: Success after binutils/gcc/glibc/g [...] discards 051bc20efe 272: onsuccess: #2088: 1: Success after binutils/gcc/gdb: 28 [...] discards a8eba42cc0 271: onsuccess: #2087: 1: Success after binutils/gcc/linux/g [...] discards 0ad791aff3 270: onsuccess: #2086: 1: Success after binutils/gcc/glibc/g [...] discards 3d650b7379 269: onsuccess: #2085: 1: Success after binutils/gcc/linux/g [...] discards 8fda01cb26 268: onsuccess: #2084: 1: Success after binutils/gcc/gdb/qem [...] discards 101154519a 267: onsuccess: #2083: 1: Success after binutils/gcc/gdb: 64 [...] discards 15ae8c0a25 266: onsuccess: #2082: 1: Success after binutils/gcc/gdb: 8 commits discards ef2b78eaab 265: onsuccess: #2081: 1: Success after gcc/linux/glibc/qemu [...] discards 2d57feffd4 264: onsuccess: #2080: 1: Success after binutils/gcc/gdb: 7 commits discards 809535e3d5 263: onsuccess: #2079: 1: Success after binutils/gcc/gdb: 7 commits discards bb6a7b5882 262: onsuccess: #2078: 1: Success after binutils/gcc/linux/g [...] discards 8dcf5ecf47 261: onsuccess: #2077: 1: Success after binutils/gcc/linux/g [...] discards b518fec336 260: onsuccess: #2076: 1: Success after binutils/gcc/glibc/g [...] discards a194b34c50 259: onsuccess: #2075: 1: Success after glibc: 2 commits discards b4d8490057 258: onsuccess: #2074: 1: Success after binutils/gcc/glibc/g [...] discards a3de066305 257: onsuccess: #2073: 1: Success after v7.2.0-211-g562d4af3 [...] discards 8fb5fac13a 256: onsuccess: #2072: 1: Success after binutils/gcc/gdb: 5 commits discards af0e2968e7 255: onsuccess: #2071: 1: Success after binutils/gcc/gdb: 5 commits discards ee655ccb99 254: onsuccess: #2070: 1: Success after binutils/gcc/gdb/qem [...] discards 7db85f73aa 253: onsuccess: #2069: 1: Success after gcc/linux: 109 commits discards 7504d07d59 252: onsuccess: #2068: 1: Success after binutils/gdb: 6 commits discards fca6474d8e 251: onsuccess: #2067: 1: Success after binutils/gcc/gdb: 13 [...] discards 1dbe90bb8f 250: onsuccess: #2066: 1: Success after binutils/gcc/linux/g [...] discards 21c46777aa 249: onsuccess: #2065: 1: Success after binutils/gcc/linux/g [...] discards 24b9356ccb 248: onsuccess: #2064: 1: Success after binutils/gcc/gdb/qem [...] discards a86e932296 247: onsuccess: #2063: 1: Success after binutils/gcc/linux/g [...] discards 21f9f1a808 246: onsuccess: #2062: 1: Success after binutils/gcc/linux/g [...] discards b15de33e27 245: onsuccess: #2061: 1: Success after binutils/gcc/linux/g [...] discards 2e2097c1a0 244: onsuccess: #2060: 1: Success after binutils/gcc/gdb/qem [...] discards e9c1b780bc 243: onsuccess: #2059: 1: Success after basepoints/gcc-13-47 [...] discards 9b20aabb57 242: onsuccess: #2058: 1: Success after binutils/gcc/linux/g [...] discards dc41485e15 241: onsuccess: #2057: 1: Success after binutils/gcc/linux/g [...] discards 66c9996e6d 240: onsuccess: #2056: 1: Success after binutils/gcc/gdb: 22 [...] discards 526db76fa5 239: onsuccess: #2055: 1: Success after binutils/gcc/linux/g [...] discards 550d07cfbf 238: onsuccess: #2054: 1: Success after binutils/gcc/linux/g [...] discards 177c2a0799 237: onsuccess: #2053: 1: Success after binutils/gcc/linux/g [...] discards 6c82de17cc 236: onsuccess: #2052: 1: Success after binutils/gcc/gdb: 10 [...] discards 0722cd31d8 235: onsuccess: #2051: 1: Success after binutils/linux/gdb: [...] discards 2c1fe754fd 234: onsuccess: #2050: 1: Success after binutils/gcc/linux/g [...] discards 3a762a48a4 233: onsuccess: #2049: 1: Success after binutils/gcc/linux/g [...] discards 65ffa20ba1 232: onsuccess: #2048: 1: Success after glibc: 2 commits discards ea711a6686 231: onsuccess: #2047: 1: Success after gcc: 4 commits discards c6e93f9ae2 230: onsuccess: #2044: 1: Success after binutils/gcc/linux/g [...] discards 5088330642 229: onsuccess: #2043: 1: Success after binutils/gcc/linux/g [...] discards 2f7fb834eb 228: onsuccess: #2042: 1: Success after basepoints/gcc-13-45 [...] discards 5f8644a9df 227: onsuccess: #2041: 1: Success after binutils/gcc/linux/g [...] discards ad172a400d 226: onsuccess: #2040: 1: Success after binutils/gcc/gdb: 15 [...] discards ec93c9d1db 225: onsuccess: #2039: 1: Success after binutils/linux/glibc [...] discards bdf2eee786 224: onsuccess: #2038: 1: Success after binutils/gcc/linux/g [...] discards c90474acec 223: onsuccess: #2036: 1: Success after binutils/gcc/linux/g [...] discards 499591cad1 222: onsuccess: #2035: 1: Success after binutils/gcc/glibc/g [...] discards 263085dbda 221: onsuccess: #2033: 1: Success after binutils/gdb: 2 commits discards 40c03de5c2 220: onsuccess: #2032: 1: Success after binutils/gcc/linux/g [...] discards 90cbc6285d 219: onsuccess: #2031: 1: Success after binutils/gcc/glibc/g [...] discards 2cc65364cf 218: onsuccess: #2030: 1: Success after gcc: 5 commits discards 9f571c85c9 217: onsuccess: #2029: 1: Success after binutils/gcc/glibc/g [...] discards 4bae47fbdb 216: onsuccess: #2028: 1: Success after binutils/gcc/linux/g [...] discards 4a74a06724 215: onsuccess: #2027: 1: Success after binutils/gcc/glibc/g [...] discards 682c707c30 214: onsuccess: #2026: 1: Success after binutils/gcc/gdb/qem [...] discards e19084a367 213: onsuccess: #2024: 1: Success after binutils: 3 commits discards 47e5578309 212: onsuccess: #2022: 1: Success after linux: 3 commits discards 572fe9aaee 211: onsuccess: #2020: 1: Success after binutils: 10 commits discards ef49d3f9f7 210: onsuccess: #2017: 1: Success after binutils: 6 commits discards ddfe6da0f9 209: onsuccess: #2014: 1: Success after binutils: 12 commits discards d7fb23ab7f 208: onsuccess: #2012: 1: Success after linux: 12 commits discards e777d08f88 207: onsuccess: #2010: 1: Success after gcc: 4 commits discards df33b22995 206: onsuccess: #2007: 1: Success after gcc: 2 commits discards da7fbaa1f9 205: onsuccess: #2006: 1: Success after gcc: 3 commits discards 58bef29271 204: onsuccess: #2005: 1: Success after binutils/gcc/linux/g [...] discards ddc0f4a8bd 203: onsuccess: #2004: 1: Success after binutils/gcc/gdb: 7 commits new 0c97f1facd 203: onsuccess: #2004: 1: Success after binutils/gcc/gdb: 7 commits new 776de724cb 204: onsuccess: #2005: 1: Success after binutils/gcc/linux/g [...] new 4c50908678 205: onsuccess: #2006: 1: Success after gcc: 3 commits new 14577ec116 206: onsuccess: #2007: 1: Success after gcc: 2 commits new 4a37438782 207: onsuccess: #2010: 1: Success after gcc: 4 commits new 66c0acd051 208: onsuccess: #2012: 1: Success after linux: 12 commits new b372874166 209: onsuccess: #2014: 1: Success after binutils: 12 commits new 92e8d19aad 210: onsuccess: #2017: 1: Success after binutils: 6 commits new bebfb91064 211: onsuccess: #2020: 1: Success after binutils: 10 commits new 6869f6280c 212: onsuccess: #2022: 1: Success after linux: 3 commits new 44a1e2f4e8 213: onsuccess: #2024: 1: Success after binutils: 3 commits new ca9460f882 214: onsuccess: #2026: 1: Success after binutils/gcc/gdb/qem [...] new 7743167c9c 215: onsuccess: #2027: 1: Success after binutils/gcc/glibc/g [...] new 5e0affd850 216: onsuccess: #2028: 1: Success after binutils/gcc/linux/g [...] new 2962b2e6bf 217: onsuccess: #2029: 1: Success after binutils/gcc/glibc/g [...] new 2341be47ec 218: onsuccess: #2030: 1: Success after gcc: 5 commits new 9a363b8637 219: onsuccess: #2031: 1: Success after binutils/gcc/glibc/g [...] new a7cde79483 220: onsuccess: #2032: 1: Success after binutils/gcc/linux/g [...] new 63c920f507 221: onsuccess: #2033: 1: Success after binutils/gdb: 2 commits new 38beae3146 222: onsuccess: #2035: 1: Success after binutils/gcc/glibc/g [...] new b3cfc21b31 223: onsuccess: #2036: 1: Success after binutils/gcc/linux/g [...] new 4a505853d4 224: onsuccess: #2038: 1: Success after binutils/gcc/linux/g [...] new 0b923e524a 225: onsuccess: #2039: 1: Success after binutils/linux/glibc [...] new 038b29e707 226: onsuccess: #2040: 1: Success after binutils/gcc/gdb: 15 [...] new 9e7433094b 227: onsuccess: #2041: 1: Success after binutils/gcc/linux/g [...] new 0d96d71b14 228: onsuccess: #2042: 1: Success after basepoints/gcc-13-45 [...] new 9d1e6ce4f6 229: onsuccess: #2043: 1: Success after binutils/gcc/linux/g [...] new 69999f28be 230: onsuccess: #2044: 1: Success after binutils/gcc/linux/g [...] new 2e0f55f548 231: onsuccess: #2047: 1: Success after gcc: 4 commits new 483ae48a8b 232: onsuccess: #2048: 1: Success after glibc: 2 commits new 899d0badbc 233: onsuccess: #2049: 1: Success after binutils/gcc/linux/g [...] new 50a93d90d9 234: onsuccess: #2050: 1: Success after binutils/gcc/linux/g [...] new bcc849b978 235: onsuccess: #2051: 1: Success after binutils/linux/gdb: [...] new 6b887d185a 236: onsuccess: #2052: 1: Success after binutils/gcc/gdb: 10 [...] new d9a58eb639 237: onsuccess: #2053: 1: Success after binutils/gcc/linux/g [...] new 9d5626a9b7 238: onsuccess: #2054: 1: Success after binutils/gcc/linux/g [...] new 6b72379c4d 239: onsuccess: #2055: 1: Success after binutils/gcc/linux/g [...] new ddf8f715ba 240: onsuccess: #2056: 1: Success after binutils/gcc/gdb: 22 [...] new 4c1b0453fd 241: onsuccess: #2057: 1: Success after binutils/gcc/linux/g [...] new cb7002a198 242: onsuccess: #2058: 1: Success after binutils/gcc/linux/g [...] new eb867944ea 243: onsuccess: #2059: 1: Success after basepoints/gcc-13-47 [...] new 35316f1970 244: onsuccess: #2060: 1: Success after binutils/gcc/gdb/qem [...] new 8084220ade 245: onsuccess: #2061: 1: Success after binutils/gcc/linux/g [...] new 7a35a3eb62 246: onsuccess: #2062: 1: Success after binutils/gcc/linux/g [...] new 3657ae9755 247: onsuccess: #2063: 1: Success after binutils/gcc/linux/g [...] new a301b27d7e 248: onsuccess: #2064: 1: Success after binutils/gcc/gdb/qem [...] new f69080b686 249: onsuccess: #2065: 1: Success after binutils/gcc/linux/g [...] new 22dd8f3c0f 250: onsuccess: #2066: 1: Success after binutils/gcc/linux/g [...] new 5643f63c32 251: onsuccess: #2067: 1: Success after binutils/gcc/gdb: 13 [...] new 2b59448cb9 252: onsuccess: #2068: 1: Success after binutils/gdb: 6 commits new bbc5a6eba8 253: onsuccess: #2069: 1: Success after gcc/linux: 109 commits new dd68cef2c5 254: onsuccess: #2070: 1: Success after binutils/gcc/gdb/qem [...] new 5136b5169e 255: onsuccess: #2071: 1: Success after binutils/gcc/gdb: 5 commits new 33de84b28c 256: onsuccess: #2072: 1: Success after binutils/gcc/gdb: 5 commits new c177098a28 257: onsuccess: #2073: 1: Success after v7.2.0-211-g562d4af3 [...] new a6865771c5 258: onsuccess: #2074: 1: Success after binutils/gcc/glibc/g [...] new 36be839ce8 259: onsuccess: #2075: 1: Success after glibc: 2 commits new f7c5209149 260: onsuccess: #2076: 1: Success after binutils/gcc/glibc/g [...] new cf2e9c52b8 261: onsuccess: #2077: 1: Success after binutils/gcc/linux/g [...] new a676142e59 262: onsuccess: #2078: 1: Success after binutils/gcc/linux/g [...] new 9dc643c77e 263: onsuccess: #2079: 1: Success after binutils/gcc/gdb: 7 commits new cc4eda166f 264: onsuccess: #2080: 1: Success after binutils/gcc/gdb: 7 commits new c702602473 265: onsuccess: #2081: 1: Success after gcc/linux/glibc/qemu [...] new 97cf37950a 266: onsuccess: #2082: 1: Success after binutils/gcc/gdb: 8 commits new 143c61d4c9 267: onsuccess: #2083: 1: Success after binutils/gcc/gdb: 64 [...] new e74d21ac79 268: onsuccess: #2084: 1: Success after binutils/gcc/gdb/qem [...] new 7de9ad37cc 269: onsuccess: #2085: 1: Success after binutils/gcc/linux/g [...] new e25ab84981 270: onsuccess: #2086: 1: Success after binutils/gcc/glibc/g [...] new e848ea4eb0 271: onsuccess: #2087: 1: Success after binutils/gcc/linux/g [...] new a1b0d1a693 272: onsuccess: #2088: 1: Success after binutils/gcc/gdb: 28 [...] new cc33b82df0 273: onsuccess: #2089: 1: Success after binutils/gcc/glibc/g [...] new acf70af727 274: onsuccess: #2090: 1: Success after binutils/gcc/linux/g [...] new 8953bd6282 275: onsuccess: #2091: 1: Success after binutils/gcc/gdb: 42 [...] new 19e0fb8af3 276: onsuccess: #2092: 1: Success after binutils/gcc/gdb: 69 [...] new 5940a8e5f7 277: onsuccess: #2093: 1: Success after binutils/gcc/linux/g [...] new 1bccdc360c 278: onsuccess: #2094: 1: Success after binutils/gcc/linux/g [...] new 0f791b5531 279: onsuccess: #2095: 1: Success after binutils/gcc/gdb: 5 commits new 066c47e4c0 280: onsuccess: #2096: 1: Success after binutils/gcc/gdb: 21 [...] new fb427a589e 281: onsuccess: #2097: 1: Success after binutils/gcc/gdb: 23 [...] new bac7f01a42 282: onsuccess: #2098: 1: Success after binutils/gcc/linux/g [...] new 23cde0c3db 283: onsuccess: #2099: 1: Success after binutils/gdb: 4 commits new a7e0f0f9b8 284: onsuccess: #2100: 1: Success after basepoints/gcc-13-48 [...] new c66693c6d2 285: onsuccess: #2101: 1: Success after binutils/gcc/gdb: 5 commits new 7e38634b69 286: onsuccess: #2102: 1: Success after binutils/gdb: 18 commits new e97d4e04e6 287: onsuccess: #2103: 1: Success after gcc: 9 commits new b5c08ace9e 288: onsuccess: #2104: 1: Success after binutils/gcc/gdb: 10 [...] new f39006145a 289: onsuccess: #2105: 1: Success after binutils/gcc/gdb: 6 commits new ca772cc234 290: onsuccess: #2106: 1: Success after gcc: 2 commits new 1178476063 291: onsuccess: #2107: 1: Success after binutils/gcc/gdb: 6 commits new 1858e4d0ca 292: onsuccess: #2108: 1: Success after binutils/gcc/gdb: 3 commits new e8a3305627 293: onsuccess: #2109: 1: Success after binutils/gdb: 2 commits new 2ced84ddc6 294: onsuccess: #2110: 1: Success after gcc: 17 commits new 56722e982e 295: onsuccess: #2111: 1: Success after binutils/gcc/linux/g [...] new d9c38682a6 296: onsuccess: #2112: 1: Success after gcc/linux: 26 commits new 4e0ba1c81d 297: onsuccess: #2113: 1: Success after binutils/gcc/gdb: 7 commits new 7aea24b6f0 298: onsuccess: #2114: 1: Success after binutils/gcc/gdb: 6 commits new ffb7ecf316 299: onsuccess: #2116: 1: Success after gdb-13-branchpoint-2 [...] new 998b24266c 300: onsuccess: #2117: 1: Success after basepoints/gcc-13-49 [...] new 1d3541dcf5 301: onsuccess: #2118: 1: Success after linux: 16 commits new 91545df563 302: onsuccess: #2119: 1: Success after binutils/gdb: 7 commits new bbff43f43b 303: onsuccess: #2120: 1: Success after binutils/gdb: 20 commits new dbfda23c30 304: onsuccess: #2121: 1: Success after gcc/linux: 13 commits
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 (34f0e05581) \ N -- N -- N refs/heads/linaro-local/ci/tcwg_gnu_cross_check_gcc/mast [...]
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 1728 -> 1788 bytes 02-prepare_abe/console.log.xz | Bin 2768 -> 2776 bytes 03-build_abe-binutils/console.log.xz | Bin 31876 -> 31868 bytes 04-build_abe-stage1/console.log.xz | Bin 91028 -> 92008 bytes 06-build_abe-linux/console.log.xz | Bin 9040 -> 8748 bytes 07-build_abe-glibc/console.log.xz | Bin 236608 -> 236520 bytes 08-build_abe-stage2/console.log.xz | Bin 228284 -> 228320 bytes 09-build_abe-gdb/console.log.xz | Bin 39188 -> 39124 bytes 10-build_abe-qemu/console.log.xz | Bin 31548 -> 31484 bytes 11-build_abe-dejagnu/console.log.xz | Bin 3860 -> 3860 bytes 12-build_abe-check_gcc/console.log.xz | Bin 2492 -> 2896 bytes 13-check_regression/console.log.xz | Bin 5300 -> 5860 bytes 13-check_regression/extra-bisect-params | 1 + 13-check_regression/fails.sum | 6 + 13-check_regression/mail-body.txt | 26 + 13-check_regression/results.compare | 9 +- 13-check_regression/results.compare2 | 22 +- 13-check_regression/results.regressions | 26 + 14-update_baseline/console.log | 40 +- dashboard/dashboard-generate.sh | 2 +- git/gcc_rev | 2 +- git/linux_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 28 +- mail/mail-subject.txt | 2 +- manifest.sh | 26 +- results | 26 + sumfiles/g++.log.xz | Bin 2652648 -> 2661816 bytes sumfiles/g++.sum | 2 +- sumfiles/gcc.log.xz | Bin 2246308 -> 2264912 bytes sumfiles/gcc.sum | 2204 +++++++++++++++---------------- sumfiles/gfortran.log.xz | Bin 896020 -> 895396 bytes sumfiles/gfortran.sum | 6 +- sumfiles/libatomic.log.xz | Bin 2264 -> 2260 bytes sumfiles/libatomic.sum | 2 +- sumfiles/libgomp.log.xz | Bin 214120 -> 214016 bytes sumfiles/libgomp.sum | 2 +- sumfiles/libitm.log.xz | Bin 2668 -> 2668 bytes sumfiles/libitm.sum | 2 +- sumfiles/libstdc++.log.xz | Bin 432644 -> 434392 bytes sumfiles/libstdc++.sum | 8 +- 41 files changed, 1286 insertions(+), 1160 deletions(-) create mode 100644 13-check_regression/extra-bisect-params create mode 100644 13-check_regression/fails.sum create mode 100644 13-check_regression/results.regressions