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 389be4e5fdc7 254: onsuccess: #2070: 1: Success after binutils/gcc/gdb/q [...] discards 4c8b3d82ac8f 253: onsuccess: #2069: 1: Success after gcc/linux: 109 commits discards 690b372a9b04 252: onsuccess: #2068: 1: Success after binutils/gdb: 6 commits discards 78536669889b 251: onsuccess: #2067: 1: Success after binutils/gcc/gdb: [...] discards 16ff98c2ee33 250: onsuccess: #2066: 1: Success after binutils/gcc/linux [...] discards 4801cfd96956 249: onsuccess: #2065: 1: Success after binutils/gcc/linux [...] discards ce23c28598eb 248: onsuccess: #2064: 1: Success after binutils/gcc/gdb/q [...] discards 831fb92d0807 247: onsuccess: #2063: 1: Success after binutils/gcc/linux [...] discards 6ffdc3001efb 246: onsuccess: #2062: 1: Success after binutils/gcc/linux [...] discards 0ad7c30035ef 245: onsuccess: #2061: 1: Success after binutils/gcc/linux [...] discards 8a9e7663a437 244: onsuccess: #2060: 1: Success after binutils/gcc/gdb/q [...] discards 74b76193d977 243: onsuccess: #2059: 1: Success after basepoints/gcc-13- [...] discards d233ba726f51 242: onsuccess: #2058: 1: Success after binutils/gcc/linux [...] discards 7bff5e067fb0 241: onsuccess: #2057: 1: Success after binutils/gcc/linux [...] discards 5fa715192293 240: onsuccess: #2056: 1: Success after binutils/gcc/gdb: [...] discards 9505f1fe111e 239: onsuccess: #2055: 1: Success after binutils/gcc/linux [...] discards bc93d7d63cdd 238: onsuccess: #2054: 1: Success after binutils/gcc/linux [...] discards 4730a8d5c32e 237: onsuccess: #2053: 1: Success after binutils/gcc/linux [...] discards fd64b7bcb324 236: onsuccess: #2052: 1: Success after binutils/gcc/gdb: [...] discards 68ea60206077 235: onsuccess: #2051: 1: Success after binutils/linux/gdb [...] discards 7d798bf40529 234: onsuccess: #2050: 1: Success after binutils/gcc/linux [...] discards dcb2399a7619 233: onsuccess: #2049: 1: Success after binutils/gcc/linux [...] discards 2a0d1c323b5b 232: onsuccess: #2048: 1: Success after glibc: 2 commits discards 43ed2a445f7e 231: onsuccess: #2047: 1: Success after gcc: 4 commits discards 82096e68740b 230: onsuccess: #2044: 1: Success after binutils/gcc/linux [...] discards f81902565df3 229: onsuccess: #2043: 1: Success after binutils/gcc/linux [...] discards eddee0477684 228: onsuccess: #2042: 1: Success after basepoints/gcc-13- [...] discards 9ed44aee82ce 227: onsuccess: #2041: 1: Success after binutils/gcc/linux [...] discards a8c374c5d695 226: onsuccess: #2040: 1: Success after binutils/gcc/gdb: [...] discards 1cf22a7720d2 225: onsuccess: #2039: 1: Success after binutils/linux/gli [...] discards c340dbd5323a 224: onsuccess: #2038: 1: Success after binutils/gcc/linux [...] discards 291ecf63102a 223: onsuccess: #2036: 1: Success after binutils/gcc/linux [...] discards dbce49caa73e 222: onsuccess: #2035: 1: Success after binutils/gcc/glibc [...] discards 4f160da579ab 221: onsuccess: #2033: 1: Success after binutils/gdb: 2 commits discards 710a7e8ba7f0 220: onsuccess: #2032: 1: Success after binutils/gcc/linux [...] discards e9f0231daa0c 219: onsuccess: #2031: 1: Success after binutils/gcc/glibc [...] discards 25b91dd81676 218: onsuccess: #2030: 1: Success after gcc: 5 commits discards b2eccc331121 217: onsuccess: #2029: 1: Success after binutils/gcc/glibc [...] discards 806904a73680 216: onsuccess: #2028: 1: Success after binutils/gcc/linux [...] discards f6e4e798881c 215: onsuccess: #2027: 1: Success after binutils/gcc/glibc [...] discards 74f5d8245a37 214: onsuccess: #2026: 1: Success after binutils/gcc/gdb/q [...] discards d5d3dce433fa 213: onsuccess: #2024: 1: Success after binutils: 3 commits discards 3cdd7127f081 212: onsuccess: #2022: 1: Success after linux: 3 commits discards 938b5ade6d31 211: onsuccess: #2020: 1: Success after binutils: 10 commits discards ee8cda9636d7 210: onsuccess: #2017: 1: Success after binutils: 6 commits discards 9fae6161d046 209: onsuccess: #2014: 1: Success after binutils: 12 commits discards f0f94c5b8ffa 208: onsuccess: #2012: 1: Success after linux: 12 commits discards 2e5946785826 207: onsuccess: #2010: 1: Success after gcc: 4 commits discards 150b79713175 206: onsuccess: #2007: 1: Success after gcc: 2 commits discards 509c701acc71 205: onsuccess: #2006: 1: Success after gcc: 3 commits discards b066c1f1d8fc 204: onsuccess: #2005: 1: Success after binutils/gcc/linux [...] discards 6b4c91b46d46 203: onsuccess: #2004: 1: Success after binutils/gcc/gdb: [...] discards 0ed5450dceaa 202: onsuccess: #2003: 1: Success after binutils/gcc/linux [...] discards f8c4304cb2e2 201: onsuccess: #2002: 1: Success after gcc/glibc: 5 commits discards 2f92baa63bf3 200: onsuccess: #2001: 1: Success after binutils/gcc/gdb: [...] discards 7ec465be41f7 199: onsuccess: #2000: 1: Success after gcc: 5 commits discards a0cb6ca26ba3 198: onsuccess: #1999: 1: Success after binutils/gcc/linux [...] discards a72d15fb4f2f 197: onsuccess: #1998: 1: Success after binutils/gcc/gdb: [...] discards 04792caca8f9 196: onsuccess: #1997: 1: Success after binutils/gcc/gdb: [...] discards 6f8008938eb0 195: onsuccess: #1996: 1: Success after binutils/gcc/glibc [...] discards 324e7a5c6e8a 194: onsuccess: #1995: 1: Success after linux: 517 commits discards b4e43e6ab05f 193: onsuccess: #1992: 1: Success after binutils: 151 commits discards b6970b507021 192: onsuccess: #1951: 1: Success after binutils/gcc/gdb: [...] discards 0375a80b1cb4 191: onsuccess: #1949: 1: Success after binutils/gcc/linux [...] discards 4c4b73d3b859 190: onsuccess: #1913: 1: Success after binutils/gcc/linux [...] discards 2c30cdc57b8c 189: onsuccess: #1912: 1: Success after binutils/gcc/linux [...] discards f80658e6d6c7 188: onsuccess: #1909: 1: Success after binutils/gcc/gdb: [...] discards ee243dff2c09 187: onsuccess: #1908: 1: Success after binutils/gcc/linux [...] discards 97d8c49766eb 186: onsuccess: #1907: 1: Success after binutils/gcc/gdb: [...] discards c943dc4e986d 185: onsuccess: #1906: 1: Success after binutils/gcc/linux [...] discards badc310383a5 184: onsuccess: #1898: 1: Success after binutils/gcc/gdb: [...] discards a9dad2577d6f 183: onsuccess: #1897: 1: Success after binutils/gcc/linux [...] discards 2f2fb7fdf2d6 182: onsuccess: #1860: 1: Success after binutils/gcc/linux [...] discards 8e0f0d5cfba7 181: onsuccess: #1857: 1: Success after binutils/gcc/linux [...] discards eef56e1a59e0 180: onsuccess: #1831: 1: Success after binutils/gcc/linux [...] discards 7afb32c0d417 179: onsuccess: #1810: 1: Success after binutils/gcc/linux [...] discards 91e41451ad6e 178: onsuccess: #1799: 1: Success after binutils/gcc/linux [...] discards 5221df41f95b 177: onsuccess: #1793: 1: Success after binutils/gcc/linux [...] discards a49e95c8fc7f 176: onsuccess: #1791: 1: Success after binutils/gcc/linux [...] discards 24e9423fb294 175: onsuccess: #1776: 1: Success after binutils/gcc/linux [...] discards 262afb9393d4 174: onsuccess: #1775: 1: Success after binutils/gcc/linux [...] discards ee454b5dcb15 173: onsuccess: #1774: 1: Success after binutils/gcc/glibc [...] discards 48ed51670070 172: onsuccess: #1773: 1: Success after binutils/gcc/glibc [...] discards 03ffa447eb4e 171: onsuccess: #1772: 1: Success after binutils/gcc/gdb: [...] discards 6d661f6575f9 170: onsuccess: #1771: 1: Success after binutils/gcc/linux [...] discards 1720c08edb7a 169: onsuccess: #1770: 1: Success after gcc/linux/glibc/qe [...] discards 191078908178 168: onsuccess: #1769: 1: Success after binutils/gcc/gdb: [...] discards 3f905b7a2b8e 167: onsuccess: #1768: 1: Success after binutils/gcc/linux [...] discards 17279a8e4fe8 166: onsuccess: #1767: 1: Success after binutils/gcc/linux [...] discards d2dcb7c32b71 165: onsuccess: #1766: 1: Success after binutils/gcc/linux [...] discards 6008ddbeaeee 164: onsuccess: #1765: 1: Success after binutils/gcc/gdb: [...] discards 8fe0d5119671 163: onsuccess: #1764: 1: Success after gcc/linux: 141 commits discards 6bdde449b5e1 162: onsuccess: #1763: 1: Success after binutils/gcc/linux [...] discards f4e98a656dc4 161: onsuccess: #1762: 1: Success after binutils/gcc/linux [...] discards e8ececdab702 160: onsuccess: #1761: 1: Success after binutils/gcc/gdb: [...] discards ab5b8913c74d 159: onsuccess: #1760: 1: Success after binutils/gcc/gdb: [...] discards b4aebfac1eed 158: onsuccess: #1759: 1: Success after binutils/gcc/linux [...] discards 0d28e622e146 157: onsuccess: #1758: 1: Success after binutils/gcc/linux [...] discards 04b4aef3ddf5 156: onsuccess: #1757: 1: Success after gcc: 4 commits discards d6fd331e47a2 155: onsuccess: #1756: 1: Success after binutils/gcc/glibc [...] discards 2c239248b1e2 154: onsuccess: #1755: 1: Success after gcc/linux: 21 commits new 2dbf120ac9a6 154: onsuccess: #1755: 1: Success after gcc/linux: 21 commits new d8c817a6333f 155: onsuccess: #1756: 1: Success after binutils/gcc/glibc [...] new 2686f80dc11e 156: onsuccess: #1757: 1: Success after gcc: 4 commits new 33c87cc47fcd 157: onsuccess: #1758: 1: Success after binutils/gcc/linux [...] new 429e293454e9 158: onsuccess: #1759: 1: Success after binutils/gcc/linux [...] new 4930241c2213 159: onsuccess: #1760: 1: Success after binutils/gcc/gdb: [...] new df71bdda597c 160: onsuccess: #1761: 1: Success after binutils/gcc/gdb: [...] new f990947cb909 161: onsuccess: #1762: 1: Success after binutils/gcc/linux [...] new 4c240fd123f9 162: onsuccess: #1763: 1: Success after binutils/gcc/linux [...] new 17205032a3cc 163: onsuccess: #1764: 1: Success after gcc/linux: 141 commits new 00c9181bffdb 164: onsuccess: #1765: 1: Success after binutils/gcc/gdb: [...] new 949518218a48 165: onsuccess: #1766: 1: Success after binutils/gcc/linux [...] new 075d643c09f4 166: onsuccess: #1767: 1: Success after binutils/gcc/linux [...] new fb9b0fe870c3 167: onsuccess: #1768: 1: Success after binutils/gcc/linux [...] new 01b4910422d0 168: onsuccess: #1769: 1: Success after binutils/gcc/gdb: [...] new d7d3e2509332 169: onsuccess: #1770: 1: Success after gcc/linux/glibc/qe [...] new c7c583895ee0 170: onsuccess: #1771: 1: Success after binutils/gcc/linux [...] new efef3a8b93ea 171: onsuccess: #1772: 1: Success after binutils/gcc/gdb: [...] new 0e90695b3af7 172: onsuccess: #1773: 1: Success after binutils/gcc/glibc [...] new 575bfb514d59 173: onsuccess: #1774: 1: Success after binutils/gcc/glibc [...] new 5e6c04c5bbff 174: onsuccess: #1775: 1: Success after binutils/gcc/linux [...] new 8820d5ce21fb 175: onsuccess: #1776: 1: Success after binutils/gcc/linux [...] new 4396c982c3dd 176: onsuccess: #1791: 1: Success after binutils/gcc/linux [...] new c78619c57b8a 177: onsuccess: #1793: 1: Success after binutils/gcc/linux [...] new 5eff1709fdfe 178: onsuccess: #1799: 1: Success after binutils/gcc/linux [...] new d679ba6c9ac9 179: onsuccess: #1810: 1: Success after binutils/gcc/linux [...] new 2477940e67e5 180: onsuccess: #1831: 1: Success after binutils/gcc/linux [...] new 28161794777a 181: onsuccess: #1857: 1: Success after binutils/gcc/linux [...] new d3af6d9d736e 182: onsuccess: #1860: 1: Success after binutils/gcc/linux [...] new 90985cb032dd 183: onsuccess: #1897: 1: Success after binutils/gcc/linux [...] new 0596d2aaa515 184: onsuccess: #1898: 1: Success after binutils/gcc/gdb: [...] new f05d8f601649 185: onsuccess: #1906: 1: Success after binutils/gcc/linux [...] new be2a80386d25 186: onsuccess: #1907: 1: Success after binutils/gcc/gdb: [...] new b4f4b885d448 187: onsuccess: #1908: 1: Success after binutils/gcc/linux [...] new 2c67ac0c3ed8 188: onsuccess: #1909: 1: Success after binutils/gcc/gdb: [...] new a9a3ebb1bc02 189: onsuccess: #1912: 1: Success after binutils/gcc/linux [...] new 28de57a7e7cc 190: onsuccess: #1913: 1: Success after binutils/gcc/linux [...] new fb0794d97834 191: onsuccess: #1949: 1: Success after binutils/gcc/linux [...] new af39bcf7b2d8 192: onsuccess: #1951: 1: Success after binutils/gcc/gdb: [...] new f8126c177823 193: onsuccess: #1992: 1: Success after binutils: 151 commits new bf029dd02d6c 194: onsuccess: #1995: 1: Success after linux: 517 commits new 751f6db1570e 195: onsuccess: #1996: 1: Success after binutils/gcc/glibc [...] new 90bcc58d4b1d 196: onsuccess: #1997: 1: Success after binutils/gcc/gdb: [...] new 130e0a8d97a5 197: onsuccess: #1998: 1: Success after binutils/gcc/gdb: [...] new 07db7bd26725 198: onsuccess: #1999: 1: Success after binutils/gcc/linux [...] new c9b9b43c8ad8 199: onsuccess: #2000: 1: Success after gcc: 5 commits new 528836545d51 200: onsuccess: #2001: 1: Success after binutils/gcc/gdb: [...] new cd7fe9f042de 201: onsuccess: #2002: 1: Success after gcc/glibc: 5 commits new b3b567d9b2e1 202: onsuccess: #2003: 1: Success after binutils/gcc/linux [...] new 768c35b38c4d 203: onsuccess: #2004: 1: Success after binutils/gcc/gdb: [...] new 819a585cfbfc 204: onsuccess: #2005: 1: Success after binutils/gcc/linux [...] new 9000bd9cba30 205: onsuccess: #2006: 1: Success after gcc: 3 commits new ab17fe5e6b52 206: onsuccess: #2007: 1: Success after gcc: 2 commits new 2a3b3f783812 207: onsuccess: #2010: 1: Success after gcc: 4 commits new aafa2ef3420e 208: onsuccess: #2012: 1: Success after linux: 12 commits new 17b8b148eede 209: onsuccess: #2014: 1: Success after binutils: 12 commits new e29706e5cf88 210: onsuccess: #2017: 1: Success after binutils: 6 commits new a8099fc04a91 211: onsuccess: #2020: 1: Success after binutils: 10 commits new 84e9e4bbbf72 212: onsuccess: #2022: 1: Success after linux: 3 commits new b45beddf7b69 213: onsuccess: #2024: 1: Success after binutils: 3 commits new 14760e879e93 214: onsuccess: #2026: 1: Success after binutils/gcc/gdb/q [...] new 5a1c9e164012 215: onsuccess: #2027: 1: Success after binutils/gcc/glibc [...] new 0bb4be89a83d 216: onsuccess: #2028: 1: Success after binutils/gcc/linux [...] new 58f281f9caa0 217: onsuccess: #2029: 1: Success after binutils/gcc/glibc [...] new 39ffc521d828 218: onsuccess: #2030: 1: Success after gcc: 5 commits new 178ef0f715b8 219: onsuccess: #2031: 1: Success after binutils/gcc/glibc [...] new 741c10442db5 220: onsuccess: #2032: 1: Success after binutils/gcc/linux [...] new c3548de42589 221: onsuccess: #2033: 1: Success after binutils/gdb: 2 commits new 91729603b1c7 222: onsuccess: #2035: 1: Success after binutils/gcc/glibc [...] new 1cbe038e2444 223: onsuccess: #2036: 1: Success after binutils/gcc/linux [...] new f8e5f83734c1 224: onsuccess: #2038: 1: Success after binutils/gcc/linux [...] new 38deaad878f7 225: onsuccess: #2039: 1: Success after binutils/linux/gli [...] new 71066a57083f 226: onsuccess: #2040: 1: Success after binutils/gcc/gdb: [...] new bfd8bd5bafe4 227: onsuccess: #2041: 1: Success after binutils/gcc/linux [...] new 9292f7471281 228: onsuccess: #2042: 1: Success after basepoints/gcc-13- [...] new 6f6ece3a39c1 229: onsuccess: #2043: 1: Success after binutils/gcc/linux [...] new 1328fe82ef4c 230: onsuccess: #2044: 1: Success after binutils/gcc/linux [...] new e730819cd47f 231: onsuccess: #2047: 1: Success after gcc: 4 commits new 372b2bd6500c 232: onsuccess: #2048: 1: Success after glibc: 2 commits new 1c4934721078 233: onsuccess: #2049: 1: Success after binutils/gcc/linux [...] new a1cc19d6d2e6 234: onsuccess: #2050: 1: Success after binutils/gcc/linux [...] new 4c66599f046f 235: onsuccess: #2051: 1: Success after binutils/linux/gdb [...] new e47b32f61d6b 236: onsuccess: #2052: 1: Success after binutils/gcc/gdb: [...] new cb8174a674a8 237: onsuccess: #2053: 1: Success after binutils/gcc/linux [...] new 8d5e4ccda9de 238: onsuccess: #2054: 1: Success after binutils/gcc/linux [...] new 09ff80d9c62a 239: onsuccess: #2055: 1: Success after binutils/gcc/linux [...] new bead4acfaf44 240: onsuccess: #2056: 1: Success after binutils/gcc/gdb: [...] new 5bb4a92b391c 241: onsuccess: #2057: 1: Success after binutils/gcc/linux [...] new fe481a147ff7 242: onsuccess: #2058: 1: Success after binutils/gcc/linux [...] new 45780b31913f 243: onsuccess: #2059: 1: Success after basepoints/gcc-13- [...] new 3bba4a02b633 244: onsuccess: #2060: 1: Success after binutils/gcc/gdb/q [...] new 0bf749ff234b 245: onsuccess: #2061: 1: Success after binutils/gcc/linux [...] new 68aab529e61c 246: onsuccess: #2062: 1: Success after binutils/gcc/linux [...] new 3e0a3f071736 247: onsuccess: #2063: 1: Success after binutils/gcc/linux [...] new 675e2cb5d351 248: onsuccess: #2064: 1: Success after binutils/gcc/gdb/q [...] new 42f7d1c56b9e 249: onsuccess: #2065: 1: Success after binutils/gcc/linux [...] new b4f4e558d582 250: onsuccess: #2066: 1: Success after binutils/gcc/linux [...] new 070d6a4bab21 251: onsuccess: #2067: 1: Success after binutils/gcc/gdb: [...] new ac7b5d517da9 252: onsuccess: #2068: 1: Success after binutils/gdb: 6 commits new 4c08fa794bd1 253: onsuccess: #2069: 1: Success after gcc/linux: 109 commits new d40da9a3a212 254: onsuccess: #2070: 1: Success after binutils/gcc/gdb/q [...] new f7033e5e9239 255: onsuccess: #2071: 1: Success after binutils/gcc/gdb: [...]
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 (389be4e5fdc7) \ 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 1796 -> 1792 bytes 02-prepare_abe/console.log.xz | Bin 2792 -> 2768 bytes 03-build_abe-binutils/console.log.xz | Bin 31940 -> 31848 bytes 04-build_abe-stage1/console.log.xz | Bin 91996 -> 91348 bytes 05-clean_sysroot/console.log.xz | Bin 332 -> 332 bytes 06-build_abe-linux/console.log.xz | Bin 8668 -> 8632 bytes 07-build_abe-glibc/console.log.xz | Bin 236460 -> 234980 bytes 08-build_abe-stage2/console.log.xz | Bin 227764 -> 223856 bytes 09-build_abe-gdb/console.log.xz | Bin 39056 -> 38956 bytes 10-build_abe-qemu/console.log.xz | Bin 31388 -> 30944 bytes 11-build_abe-dejagnu/console.log.xz | Bin 3888 -> 3872 bytes 12-build_abe-check_gcc/console.log.xz | Bin 2512 -> 2612 bytes 13-check_regression/console.log.xz | Bin 5868 -> 5592 bytes 13-check_regression/extra-bisect-params | 1 + 13-check_regression/fails.sum | 7 + 13-check_regression/mail-body.txt | 27 + 13-check_regression/results.compare | 32 +- 13-check_regression/results.compare2 | 37 +- 13-check_regression/results.regressions | 27 + 14-update_baseline/console.log | 70 +- dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- git/gdb_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 29 +- mail/mail-subject.txt | 2 +- manifest.sh | 32 +- results | 27 + sumfiles/g++.log.xz | Bin 2692756 -> 2684072 bytes sumfiles/g++.sum | 122 +- sumfiles/gcc.log.xz | Bin 2246300 -> 2244992 bytes sumfiles/gcc.sum | 2246 +++++++++++++++---------------- sumfiles/gfortran.log.xz | Bin 897972 -> 895012 bytes sumfiles/gfortran.sum | 44 +- sumfiles/libatomic.log.xz | Bin 2260 -> 2260 bytes sumfiles/libatomic.sum | 4 +- sumfiles/libgomp.log.xz | Bin 213964 -> 214008 bytes sumfiles/libgomp.sum | 16 +- sumfiles/libitm.log.xz | Bin 2672 -> 2676 bytes sumfiles/libitm.sum | 6 +- sumfiles/libstdc++.log.xz | Bin 443384 -> 428496 bytes sumfiles/libstdc++.sum | 10 +- 43 files changed, 1438 insertions(+), 1311 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