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 6af1bfb0601a 264: onsuccess: #2080: 1: Success after binutils/gcc/gdb: [...] discards 8aaaadc3da42 263: onsuccess: #2079: 1: Success after binutils/gcc/gdb: [...] discards 29aae136b0b4 262: onsuccess: #2078: 1: Success after binutils/gcc/linux [...] discards fa43fdc7aa5c 261: onsuccess: #2077: 1: Success after binutils/gcc/linux [...] discards fd322ec46f23 260: onsuccess: #2076: 1: Success after binutils/gcc/glibc [...] discards 804d58991000 259: onsuccess: #2075: 1: Success after glibc: 2 commits discards c165db2acb6a 258: onsuccess: #2074: 1: Success after binutils/gcc/glibc [...] discards 4a378529691c 257: onsuccess: #2073: 1: Success after v7.2.0-211-g562d4a [...] discards 9f27b2f68d7b 256: onsuccess: #2072: 1: Success after binutils/gcc/gdb: [...] discards d02e8dbaae2d 255: onsuccess: #2071: 1: Success after binutils/gcc/gdb: [...] discards 482d61606ace 254: onsuccess: #2070: 1: Success after binutils/gcc/gdb/q [...] discards 7353ca11c2fd 253: onsuccess: #2069: 1: Success after gcc/linux: 109 commits discards 1bc1d5445dcc 252: onsuccess: #2068: 1: Success after binutils/gdb: 6 commits discards e3e6d36e2052 251: onsuccess: #2067: 1: Success after binutils/gcc/gdb: [...] discards 008276d03e4f 250: onsuccess: #2066: 1: Success after binutils/gcc/linux [...] discards 5b6d50e7b996 249: onsuccess: #2065: 1: Success after binutils/gcc/linux [...] discards 5d4fa79cec29 248: onsuccess: #2064: 1: Success after binutils/gcc/gdb/q [...] discards dfbaa54db459 247: onsuccess: #2063: 1: Success after binutils/gcc/linux [...] discards f04c8d9cb62e 246: onsuccess: #2062: 1: Success after binutils/gcc/linux [...] discards 4a7380338449 245: onsuccess: #2061: 1: Success after binutils/gcc/linux [...] discards ece67097840a 244: onsuccess: #2060: 1: Success after binutils/gcc/gdb/q [...] discards 8ff61fa7db1d 243: onsuccess: #2059: 1: Success after basepoints/gcc-13- [...] discards 62dc3359ecc1 242: onsuccess: #2058: 1: Success after binutils/gcc/linux [...] discards 5139a9a3eee5 241: onsuccess: #2057: 1: Success after binutils/gcc/linux [...] discards cef21c90934d 240: onsuccess: #2056: 1: Success after binutils/gcc/gdb: [...] discards a4268ac06760 239: onsuccess: #2055: 1: Success after binutils/gcc/linux [...] discards 5d87560ebce9 238: onsuccess: #2054: 1: Success after binutils/gcc/linux [...] discards 72eb4f9008dd 237: onsuccess: #2053: 1: Success after binutils/gcc/linux [...] discards 214b7592b5ff 236: onsuccess: #2052: 1: Success after binutils/gcc/gdb: [...] discards a52b4f337a4e 235: onsuccess: #2051: 1: Success after binutils/linux/gdb [...] discards 44a9fd5d047f 234: onsuccess: #2050: 1: Success after binutils/gcc/linux [...] discards 99663b79112f 233: onsuccess: #2049: 1: Success after binutils/gcc/linux [...] discards b4ba1d5a90a5 232: onsuccess: #2048: 1: Success after glibc: 2 commits discards 4aaee5387afc 231: onsuccess: #2047: 1: Success after gcc: 4 commits discards 5930aa804c66 230: onsuccess: #2044: 1: Success after binutils/gcc/linux [...] discards 68a31bc50264 229: onsuccess: #2043: 1: Success after binutils/gcc/linux [...] discards 8946e0c79e67 228: onsuccess: #2042: 1: Success after basepoints/gcc-13- [...] discards 59e28369a227 227: onsuccess: #2041: 1: Success after binutils/gcc/linux [...] discards 0967f0eca425 226: onsuccess: #2040: 1: Success after binutils/gcc/gdb: [...] discards a7057ec26c89 225: onsuccess: #2039: 1: Success after binutils/linux/gli [...] discards a0d88ed0d6e2 224: onsuccess: #2038: 1: Success after binutils/gcc/linux [...] discards ee60809ef3ac 223: onsuccess: #2036: 1: Success after binutils/gcc/linux [...] discards 8f7334bb3db5 222: onsuccess: #2035: 1: Success after binutils/gcc/glibc [...] discards 52feb55cf7fb 221: onsuccess: #2033: 1: Success after binutils/gdb: 2 commits discards 2d12518d8c35 220: onsuccess: #2032: 1: Success after binutils/gcc/linux [...] discards 7c436ddaebc0 219: onsuccess: #2031: 1: Success after binutils/gcc/glibc [...] discards 565f4294b70a 218: onsuccess: #2030: 1: Success after gcc: 5 commits discards eda613274b56 217: onsuccess: #2029: 1: Success after binutils/gcc/glibc [...] discards 1d830ecfc546 216: onsuccess: #2028: 1: Success after binutils/gcc/linux [...] discards 9b7e659e35ee 215: onsuccess: #2027: 1: Success after binutils/gcc/glibc [...] discards f73a3e156667 214: onsuccess: #2026: 1: Success after binutils/gcc/gdb/q [...] discards 8062c6e1b740 213: onsuccess: #2024: 1: Success after binutils: 3 commits discards 24f69be1711a 212: onsuccess: #2022: 1: Success after linux: 3 commits discards c457ee6fc2b2 211: onsuccess: #2020: 1: Success after binutils: 10 commits discards 0560bf6f22e1 210: onsuccess: #2017: 1: Success after binutils: 6 commits discards 27d5673e6740 209: onsuccess: #2014: 1: Success after binutils: 12 commits discards e591c42d7066 208: onsuccess: #2012: 1: Success after linux: 12 commits discards 26509e8e2b77 207: onsuccess: #2010: 1: Success after gcc: 4 commits discards b34d69507c9b 206: onsuccess: #2007: 1: Success after gcc: 2 commits discards b3f8d4c7478a 205: onsuccess: #2006: 1: Success after gcc: 3 commits discards 2a1cbf2e33ff 204: onsuccess: #2005: 1: Success after binutils/gcc/linux [...] discards 4442466f38e8 203: onsuccess: #2004: 1: Success after binutils/gcc/gdb: [...] discards 49000883f62a 202: onsuccess: #2003: 1: Success after binutils/gcc/linux [...] discards 26e4a93eab8d 201: onsuccess: #2002: 1: Success after gcc/glibc: 5 commits discards ecd22a2825a1 200: onsuccess: #2001: 1: Success after binutils/gcc/gdb: [...] discards 59a7511b9949 199: onsuccess: #2000: 1: Success after gcc: 5 commits discards 46ff526bf027 198: onsuccess: #1999: 1: Success after binutils/gcc/linux [...] discards fcd9f55f1f8f 197: onsuccess: #1998: 1: Success after binutils/gcc/gdb: [...] discards d483182f6636 196: onsuccess: #1997: 1: Success after binutils/gcc/gdb: [...] discards 889df6e6fcd0 195: onsuccess: #1996: 1: Success after binutils/gcc/glibc [...] discards dc2096b3ffd4 194: onsuccess: #1995: 1: Success after linux: 517 commits discards 0a1e6a8a3c76 193: onsuccess: #1992: 1: Success after binutils: 151 commits discards e1d4b9eb2418 192: onsuccess: #1951: 1: Success after binutils/gcc/gdb: [...] discards c8a2710c493c 191: onsuccess: #1949: 1: Success after binutils/gcc/linux [...] discards 888e4974e41a 190: onsuccess: #1913: 1: Success after binutils/gcc/linux [...] discards 93bdb0e7dae9 189: onsuccess: #1912: 1: Success after binutils/gcc/linux [...] discards 63c0248a969c 188: onsuccess: #1909: 1: Success after binutils/gcc/gdb: [...] discards 428000dfa7ad 187: onsuccess: #1908: 1: Success after binutils/gcc/linux [...] discards d8367496b445 186: onsuccess: #1907: 1: Success after binutils/gcc/gdb: [...] discards 7dc88ad6712a 185: onsuccess: #1906: 1: Success after binutils/gcc/linux [...] discards 61d081f79de2 184: onsuccess: #1898: 1: Success after binutils/gcc/gdb: [...] discards 8dfe9f57694d 183: onsuccess: #1897: 1: Success after binutils/gcc/linux [...] discards 29c29671a77f 182: onsuccess: #1860: 1: Success after binutils/gcc/linux [...] discards faa390cdc7c7 181: onsuccess: #1857: 1: Success after binutils/gcc/linux [...] discards d119030ce51d 180: onsuccess: #1831: 1: Success after binutils/gcc/linux [...] discards 12f1dca33226 179: onsuccess: #1810: 1: Success after binutils/gcc/linux [...] discards 6953b0b61fb6 178: onsuccess: #1799: 1: Success after binutils/gcc/linux [...] discards b9de9d52b3cf 177: onsuccess: #1793: 1: Success after binutils/gcc/linux [...] discards 969918467f03 176: onsuccess: #1791: 1: Success after binutils/gcc/linux [...] discards e233a3e51234 175: onsuccess: #1776: 1: Success after binutils/gcc/linux [...] discards ff372a46c5d4 174: onsuccess: #1775: 1: Success after binutils/gcc/linux [...] discards dae122149f70 173: onsuccess: #1774: 1: Success after binutils/gcc/glibc [...] discards ac3aef2fcb5d 172: onsuccess: #1773: 1: Success after binutils/gcc/glibc [...] discards 52d7c0aeeed2 171: onsuccess: #1772: 1: Success after binutils/gcc/gdb: [...] discards 6be7602e4bab 170: onsuccess: #1771: 1: Success after binutils/gcc/linux [...] discards 4c42377d1750 169: onsuccess: #1770: 1: Success after gcc/linux/glibc/qe [...] discards 7a7bd6431dfb 168: onsuccess: #1769: 1: Success after binutils/gcc/gdb: [...] discards ad868496607b 167: onsuccess: #1768: 1: Success after binutils/gcc/linux [...] discards fc24f8267a5a 166: onsuccess: #1767: 1: Success after binutils/gcc/linux [...] discards eba85c20b736 165: onsuccess: #1766: 1: Success after binutils/gcc/linux [...] discards 6cfa18f5f8ef 164: onsuccess: #1765: 1: Success after binutils/gcc/gdb: [...] new 92fb97ac987a 164: onsuccess: #1765: 1: Success after binutils/gcc/gdb: [...] new 221c1816397a 165: onsuccess: #1766: 1: Success after binutils/gcc/linux [...] new 755fee5f79f4 166: onsuccess: #1767: 1: Success after binutils/gcc/linux [...] new b7a6539efe6a 167: onsuccess: #1768: 1: Success after binutils/gcc/linux [...] new a710336658a2 168: onsuccess: #1769: 1: Success after binutils/gcc/gdb: [...] new da60c1016d14 169: onsuccess: #1770: 1: Success after gcc/linux/glibc/qe [...] new f957c3c10958 170: onsuccess: #1771: 1: Success after binutils/gcc/linux [...] new 00b4ac95c2f7 171: onsuccess: #1772: 1: Success after binutils/gcc/gdb: [...] new 4a5377179a14 172: onsuccess: #1773: 1: Success after binutils/gcc/glibc [...] new 9ff42175590e 173: onsuccess: #1774: 1: Success after binutils/gcc/glibc [...] new 5edc588661cd 174: onsuccess: #1775: 1: Success after binutils/gcc/linux [...] new cdbc150f8187 175: onsuccess: #1776: 1: Success after binutils/gcc/linux [...] new 3ab6c741dcd9 176: onsuccess: #1791: 1: Success after binutils/gcc/linux [...] new 453d023edacd 177: onsuccess: #1793: 1: Success after binutils/gcc/linux [...] new 0ac672e15ed1 178: onsuccess: #1799: 1: Success after binutils/gcc/linux [...] new 83d6f60e78f8 179: onsuccess: #1810: 1: Success after binutils/gcc/linux [...] new 7af1cb888d21 180: onsuccess: #1831: 1: Success after binutils/gcc/linux [...] new a41d4bb36f76 181: onsuccess: #1857: 1: Success after binutils/gcc/linux [...] new 6896a34046ef 182: onsuccess: #1860: 1: Success after binutils/gcc/linux [...] new 2cbfee77f419 183: onsuccess: #1897: 1: Success after binutils/gcc/linux [...] new 8c6d3f0548ea 184: onsuccess: #1898: 1: Success after binutils/gcc/gdb: [...] new 97ac92d53967 185: onsuccess: #1906: 1: Success after binutils/gcc/linux [...] new 62382ad03512 186: onsuccess: #1907: 1: Success after binutils/gcc/gdb: [...] new 53ab9bedfc0f 187: onsuccess: #1908: 1: Success after binutils/gcc/linux [...] new 9333a235dd6a 188: onsuccess: #1909: 1: Success after binutils/gcc/gdb: [...] new 10b1e896d3f6 189: onsuccess: #1912: 1: Success after binutils/gcc/linux [...] new 269f4f79b1aa 190: onsuccess: #1913: 1: Success after binutils/gcc/linux [...] new 7024afa181e5 191: onsuccess: #1949: 1: Success after binutils/gcc/linux [...] new ff433e8d1c3f 192: onsuccess: #1951: 1: Success after binutils/gcc/gdb: [...] new 479cfd2c0b2f 193: onsuccess: #1992: 1: Success after binutils: 151 commits new 563e56bf4d90 194: onsuccess: #1995: 1: Success after linux: 517 commits new 0037e1e12872 195: onsuccess: #1996: 1: Success after binutils/gcc/glibc [...] new 68313d43db66 196: onsuccess: #1997: 1: Success after binutils/gcc/gdb: [...] new be1e7794a8d5 197: onsuccess: #1998: 1: Success after binutils/gcc/gdb: [...] new 53ab24de4443 198: onsuccess: #1999: 1: Success after binutils/gcc/linux [...] new c8c1592d541c 199: onsuccess: #2000: 1: Success after gcc: 5 commits new 72d26660ddfc 200: onsuccess: #2001: 1: Success after binutils/gcc/gdb: [...] new c34fa302e4d6 201: onsuccess: #2002: 1: Success after gcc/glibc: 5 commits new fe44435a74ab 202: onsuccess: #2003: 1: Success after binutils/gcc/linux [...] new bfed67d6b7b8 203: onsuccess: #2004: 1: Success after binutils/gcc/gdb: [...] new e399e7693cf6 204: onsuccess: #2005: 1: Success after binutils/gcc/linux [...] new 01d0432e9cb2 205: onsuccess: #2006: 1: Success after gcc: 3 commits new 55308e1b0886 206: onsuccess: #2007: 1: Success after gcc: 2 commits new f8c9d1936bae 207: onsuccess: #2010: 1: Success after gcc: 4 commits new 67a2ef3894d7 208: onsuccess: #2012: 1: Success after linux: 12 commits new 2f583c48c6a5 209: onsuccess: #2014: 1: Success after binutils: 12 commits new b1d8ea8be3bd 210: onsuccess: #2017: 1: Success after binutils: 6 commits new 07f7d0eb661f 211: onsuccess: #2020: 1: Success after binutils: 10 commits new 7cd49c0b86ce 212: onsuccess: #2022: 1: Success after linux: 3 commits new 4c46db9fad50 213: onsuccess: #2024: 1: Success after binutils: 3 commits new ec8ecc1f2ac0 214: onsuccess: #2026: 1: Success after binutils/gcc/gdb/q [...] new aba4c53a3320 215: onsuccess: #2027: 1: Success after binutils/gcc/glibc [...] new 2bb5260cfdd3 216: onsuccess: #2028: 1: Success after binutils/gcc/linux [...] new eaf0cd4d88eb 217: onsuccess: #2029: 1: Success after binutils/gcc/glibc [...] new a807813bd79c 218: onsuccess: #2030: 1: Success after gcc: 5 commits new d8c875783bee 219: onsuccess: #2031: 1: Success after binutils/gcc/glibc [...] new 2068fae55d6d 220: onsuccess: #2032: 1: Success after binutils/gcc/linux [...] new 6b6f4e623ea5 221: onsuccess: #2033: 1: Success after binutils/gdb: 2 commits new 4a6ad8741669 222: onsuccess: #2035: 1: Success after binutils/gcc/glibc [...] new e66a2afb1826 223: onsuccess: #2036: 1: Success after binutils/gcc/linux [...] new 7ae758cff252 224: onsuccess: #2038: 1: Success after binutils/gcc/linux [...] new 0e39671f99e5 225: onsuccess: #2039: 1: Success after binutils/linux/gli [...] new 7b110a871065 226: onsuccess: #2040: 1: Success after binutils/gcc/gdb: [...] new a398c8035581 227: onsuccess: #2041: 1: Success after binutils/gcc/linux [...] new 5ffa6dd86b65 228: onsuccess: #2042: 1: Success after basepoints/gcc-13- [...] new dec23f50aba5 229: onsuccess: #2043: 1: Success after binutils/gcc/linux [...] new 0a4ba0f1daa6 230: onsuccess: #2044: 1: Success after binutils/gcc/linux [...] new 6fd993fc65de 231: onsuccess: #2047: 1: Success after gcc: 4 commits new 40c12ab45417 232: onsuccess: #2048: 1: Success after glibc: 2 commits new 590333ebae61 233: onsuccess: #2049: 1: Success after binutils/gcc/linux [...] new 569119705fc2 234: onsuccess: #2050: 1: Success after binutils/gcc/linux [...] new bf2544077657 235: onsuccess: #2051: 1: Success after binutils/linux/gdb [...] new 9722880bdf98 236: onsuccess: #2052: 1: Success after binutils/gcc/gdb: [...] new 753f1b1d2e29 237: onsuccess: #2053: 1: Success after binutils/gcc/linux [...] new d197da01de9a 238: onsuccess: #2054: 1: Success after binutils/gcc/linux [...] new ce8060c5b3f2 239: onsuccess: #2055: 1: Success after binutils/gcc/linux [...] new 3b665ebf3cb6 240: onsuccess: #2056: 1: Success after binutils/gcc/gdb: [...] new b87d3b80955c 241: onsuccess: #2057: 1: Success after binutils/gcc/linux [...] new 82d15db5b859 242: onsuccess: #2058: 1: Success after binutils/gcc/linux [...] new 4154110f0ba2 243: onsuccess: #2059: 1: Success after basepoints/gcc-13- [...] new 23299804e3ca 244: onsuccess: #2060: 1: Success after binutils/gcc/gdb/q [...] new 37e22d2b49d6 245: onsuccess: #2061: 1: Success after binutils/gcc/linux [...] new 42f3a9ed7784 246: onsuccess: #2062: 1: Success after binutils/gcc/linux [...] new af74004031a8 247: onsuccess: #2063: 1: Success after binutils/gcc/linux [...] new 45ea130994c5 248: onsuccess: #2064: 1: Success after binutils/gcc/gdb/q [...] new 5b283db447d5 249: onsuccess: #2065: 1: Success after binutils/gcc/linux [...] new a0af8e8150af 250: onsuccess: #2066: 1: Success after binutils/gcc/linux [...] new bedfbfc95cc0 251: onsuccess: #2067: 1: Success after binutils/gcc/gdb: [...] new 1b42cfeea992 252: onsuccess: #2068: 1: Success after binutils/gdb: 6 commits new ebac41eee04d 253: onsuccess: #2069: 1: Success after gcc/linux: 109 commits new 6aad49ff4a4d 254: onsuccess: #2070: 1: Success after binutils/gcc/gdb/q [...] new c6d030af3ea4 255: onsuccess: #2071: 1: Success after binutils/gcc/gdb: [...] new b97791554802 256: onsuccess: #2072: 1: Success after binutils/gcc/gdb: [...] new a6ef1666b25e 257: onsuccess: #2073: 1: Success after v7.2.0-211-g562d4a [...] new 1e450c16622e 258: onsuccess: #2074: 1: Success after binutils/gcc/glibc [...] new 62ef64021b27 259: onsuccess: #2075: 1: Success after glibc: 2 commits new 42aaef467d1a 260: onsuccess: #2076: 1: Success after binutils/gcc/glibc [...] new e212f2769853 261: onsuccess: #2077: 1: Success after binutils/gcc/linux [...] new 0ba44380b6fd 262: onsuccess: #2078: 1: Success after binutils/gcc/linux [...] new 0466d64f1539 263: onsuccess: #2079: 1: Success after binutils/gcc/gdb: [...] new 2dafbd656fe6 264: onsuccess: #2080: 1: Success after binutils/gcc/gdb: [...] new 4c0bf76a4841 265: onsuccess: #2081: 1: Success after gcc/linux/glibc/qe [...]

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 (6af1bfb0601a) \ 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 1776 -> 1796 bytes 02-prepare_abe/console.log.xz | Bin 2804 -> 2776 bytes 03-build_abe-binutils/console.log.xz | Bin 32332 -> 31920 bytes 04-build_abe-stage1/console.log.xz | Bin 92320 -> 92180 bytes 05-clean_sysroot/console.log.xz | Bin 332 -> 332 bytes 06-build_abe-linux/console.log.xz | Bin 9256 -> 8536 bytes 07-build_abe-glibc/console.log.xz | Bin 238404 -> 235820 bytes 08-build_abe-stage2/console.log.xz | Bin 226772 -> 225444 bytes 09-build_abe-gdb/console.log.xz | Bin 39484 -> 39248 bytes 10-build_abe-qemu/console.log.xz | Bin 30940 -> 30812 bytes 11-build_abe-dejagnu/console.log.xz | Bin 3884 -> 3868 bytes 12-build_abe-check_gcc/console.log.xz | Bin 2668 -> 3352 bytes 13-check_regression/console.log.xz | Bin 5916 -> 6300 bytes 13-check_regression/extra-bisect-params | 1 - 13-check_regression/fails.sum | 6 - 13-check_regression/mail-body.txt | 42 +- 13-check_regression/results.compare | 33 +- 13-check_regression/results.compare2 | 61 +- 13-check_regression/results.regressions | 26 - 14-update_baseline/console.log | 66 +- dashboard/dashboard-generate.sh | 2 +- git/gcc_rev | 2 +- git/glibc_rev | 2 +- git/linux_rev | 2 +- git/qemu_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 44 +- mail/mail-subject.txt | 2 +- manifest.sh | 38 +- results | 26 - sumfiles/g++.log.xz | Bin 2678088 -> 2689020 bytes sumfiles/g++.sum | 148 +- sumfiles/gcc.log.xz | Bin 2246924 -> 2232244 bytes sumfiles/gcc.sum | 2793 ++++++++++++++++--------------- sumfiles/gfortran.log.xz | Bin 895960 -> 890528 bytes sumfiles/gfortran.sum | 40 +- sumfiles/libatomic.log.xz | Bin 2260 -> 2264 bytes sumfiles/libatomic.sum | 4 +- sumfiles/libgomp.log.xz | Bin 214012 -> 214068 bytes sumfiles/libgomp.sum | 16 +- sumfiles/libitm.log.xz | Bin 2676 -> 2668 bytes sumfiles/libitm.sum | 6 +- sumfiles/libstdc++.log.xz | Bin 437856 -> 432180 bytes sumfiles/libstdc++.sum | 10 +- 44 files changed, 1674 insertions(+), 1700 deletions(-) delete mode 100644 13-check_regression/extra-bisect-params delete mode 100644 13-check_regression/fails.sum delete mode 100644 13-check_regression/results.regressions