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 d2972e5ed009 263: onsuccess: #2079: 1: Success after binutils/gcc/gdb: [...] discards fb2c01bef3ee 262: onsuccess: #2078: 1: Success after binutils/gcc/linux [...] discards b26c9c8dc3ef 261: onsuccess: #2077: 1: Success after binutils/gcc/linux [...] discards f37bee922763 260: onsuccess: #2076: 1: Success after binutils/gcc/glibc [...] discards 976bf5cf9653 259: onsuccess: #2075: 1: Success after glibc: 2 commits discards b1345cdd40b1 258: onsuccess: #2074: 1: Success after binutils/gcc/glibc [...] discards 10e37d322156 257: onsuccess: #2073: 1: Success after v7.2.0-211-g562d4a [...] discards 61586e97e8de 256: onsuccess: #2072: 1: Success after binutils/gcc/gdb: [...] discards d3fb5ee0c0ec 255: onsuccess: #2071: 1: Success after binutils/gcc/gdb: [...] discards 7a3baba2b923 254: onsuccess: #2070: 1: Success after binutils/gcc/gdb/q [...] discards 641ce7f59168 253: onsuccess: #2069: 1: Success after gcc/linux: 109 commits discards 240c5d033abb 252: onsuccess: #2068: 1: Success after binutils/gdb: 6 commits discards 3b5fe8869081 251: onsuccess: #2067: 1: Success after binutils/gcc/gdb: [...] discards 56a7a31f2186 250: onsuccess: #2066: 1: Success after binutils/gcc/linux [...] discards 6617ad46dbff 249: onsuccess: #2065: 1: Success after binutils/gcc/linux [...] discards 99878e815061 248: onsuccess: #2064: 1: Success after binutils/gcc/gdb/q [...] discards 8525eabb8bf3 247: onsuccess: #2063: 1: Success after binutils/gcc/linux [...] discards 5b31d6b7edd2 246: onsuccess: #2062: 1: Success after binutils/gcc/linux [...] discards 0e65dc6cbab8 245: onsuccess: #2061: 1: Success after binutils/gcc/linux [...] discards a461d4aba473 244: onsuccess: #2060: 1: Success after binutils/gcc/gdb/q [...] discards 72c2e1692a31 243: onsuccess: #2059: 1: Success after basepoints/gcc-13- [...] discards 9ea40d7214d0 242: onsuccess: #2058: 1: Success after binutils/gcc/linux [...] discards 1be99e1c47da 241: onsuccess: #2057: 1: Success after binutils/gcc/linux [...] discards 3ad112dd93cd 240: onsuccess: #2056: 1: Success after binutils/gcc/gdb: [...] discards 5ea6db8bcf2c 239: onsuccess: #2055: 1: Success after binutils/gcc/linux [...] discards 4b410fa456b6 238: onsuccess: #2054: 1: Success after binutils/gcc/linux [...] discards 227ed58e31fa 237: onsuccess: #2053: 1: Success after binutils/gcc/linux [...] discards e662a23c60ef 236: onsuccess: #2052: 1: Success after binutils/gcc/gdb: [...] discards afca2948ac69 235: onsuccess: #2051: 1: Success after binutils/linux/gdb [...] discards d61c6ddd9827 234: onsuccess: #2050: 1: Success after binutils/gcc/linux [...] discards 535ac7dcc25e 233: onsuccess: #2049: 1: Success after binutils/gcc/linux [...] discards e68ac7af0699 232: onsuccess: #2048: 1: Success after glibc: 2 commits discards 0611aff54d6c 231: onsuccess: #2047: 1: Success after gcc: 4 commits discards 4036938de0f8 230: onsuccess: #2044: 1: Success after binutils/gcc/linux [...] discards e46ade7344e8 229: onsuccess: #2043: 1: Success after binutils/gcc/linux [...] discards 63458fd80ce5 228: onsuccess: #2042: 1: Success after basepoints/gcc-13- [...] discards adc1112e4544 227: onsuccess: #2041: 1: Success after binutils/gcc/linux [...] discards c3e6968ad634 226: onsuccess: #2040: 1: Success after binutils/gcc/gdb: [...] discards b158112e50b0 225: onsuccess: #2039: 1: Success after binutils/linux/gli [...] discards 107f09769b09 224: onsuccess: #2038: 1: Success after binutils/gcc/linux [...] discards e23345300af1 223: onsuccess: #2036: 1: Success after binutils/gcc/linux [...] discards 15edb61dd5c3 222: onsuccess: #2035: 1: Success after binutils/gcc/glibc [...] discards 11a2d6a79edb 221: onsuccess: #2033: 1: Success after binutils/gdb: 2 commits discards fe58ce9642ec 220: onsuccess: #2032: 1: Success after binutils/gcc/linux [...] discards 88bb5aeba80e 219: onsuccess: #2031: 1: Success after binutils/gcc/glibc [...] discards e2dd23dadb33 218: onsuccess: #2030: 1: Success after gcc: 5 commits discards c643f31197bb 217: onsuccess: #2029: 1: Success after binutils/gcc/glibc [...] discards 7b7e6d48ffd8 216: onsuccess: #2028: 1: Success after binutils/gcc/linux [...] discards 5c9aea790f0a 215: onsuccess: #2027: 1: Success after binutils/gcc/glibc [...] discards be7adae18a0f 214: onsuccess: #2026: 1: Success after binutils/gcc/gdb/q [...] discards 4f6267ab8722 213: onsuccess: #2024: 1: Success after binutils: 3 commits discards 772ed211fc5a 212: onsuccess: #2022: 1: Success after linux: 3 commits discards 18134e5b6a84 211: onsuccess: #2020: 1: Success after binutils: 10 commits discards 7cede4f1e7f5 210: onsuccess: #2017: 1: Success after binutils: 6 commits discards cdac899720b0 209: onsuccess: #2014: 1: Success after binutils: 12 commits discards 6fcc464bdab5 208: onsuccess: #2012: 1: Success after linux: 12 commits discards a2efd213938b 207: onsuccess: #2010: 1: Success after gcc: 4 commits discards 25f12be41b65 206: onsuccess: #2007: 1: Success after gcc: 2 commits discards 17b95498132e 205: onsuccess: #2006: 1: Success after gcc: 3 commits discards 24af50bf4aa1 204: onsuccess: #2005: 1: Success after binutils/gcc/linux [...] discards 2799ae5d9f03 203: onsuccess: #2004: 1: Success after binutils/gcc/gdb: [...] discards 6add64085e1f 202: onsuccess: #2003: 1: Success after binutils/gcc/linux [...] discards b00c79027a0f 201: onsuccess: #2002: 1: Success after gcc/glibc: 5 commits discards a2fb9428a139 200: onsuccess: #2001: 1: Success after binutils/gcc/gdb: [...] discards 1975716838b1 199: onsuccess: #2000: 1: Success after gcc: 5 commits discards c40461b98c48 198: onsuccess: #1999: 1: Success after binutils/gcc/linux [...] discards 49432efd3896 197: onsuccess: #1998: 1: Success after binutils/gcc/gdb: [...] discards fd1b2eb997e2 196: onsuccess: #1997: 1: Success after binutils/gcc/gdb: [...] discards 44c0b7554674 195: onsuccess: #1996: 1: Success after binutils/gcc/glibc [...] discards c78c498594ac 194: onsuccess: #1995: 1: Success after linux: 517 commits discards 9bbf1f7dfe42 193: onsuccess: #1992: 1: Success after binutils: 151 commits discards 83f52e0a7ac8 192: onsuccess: #1951: 1: Success after binutils/gcc/gdb: [...] discards f696d2f2cbee 191: onsuccess: #1949: 1: Success after binutils/gcc/linux [...] discards 21b9f15b3dd9 190: onsuccess: #1913: 1: Success after binutils/gcc/linux [...] discards 4ab98230e2bc 189: onsuccess: #1912: 1: Success after binutils/gcc/linux [...] discards d4cdf1b3d402 188: onsuccess: #1909: 1: Success after binutils/gcc/gdb: [...] discards c28300526abe 187: onsuccess: #1908: 1: Success after binutils/gcc/linux [...] discards 27ca640e2b4d 186: onsuccess: #1907: 1: Success after binutils/gcc/gdb: [...] discards 6f53500b8a99 185: onsuccess: #1906: 1: Success after binutils/gcc/linux [...] discards ca1e0ba5f33b 184: onsuccess: #1898: 1: Success after binutils/gcc/gdb: [...] discards 7d96c529f3c9 183: onsuccess: #1897: 1: Success after binutils/gcc/linux [...] discards 393e6e5517a4 182: onsuccess: #1860: 1: Success after binutils/gcc/linux [...] discards d1cd54583eef 181: onsuccess: #1857: 1: Success after binutils/gcc/linux [...] discards f06f7b678338 180: onsuccess: #1831: 1: Success after binutils/gcc/linux [...] discards 00f6356de04f 179: onsuccess: #1810: 1: Success after binutils/gcc/linux [...] discards 47ca10db0992 178: onsuccess: #1799: 1: Success after binutils/gcc/linux [...] discards 10a119e913ba 177: onsuccess: #1793: 1: Success after binutils/gcc/linux [...] discards 813e71a80c0c 176: onsuccess: #1791: 1: Success after binutils/gcc/linux [...] discards 7348ae9eb5ea 175: onsuccess: #1776: 1: Success after binutils/gcc/linux [...] discards 623fdb5009e6 174: onsuccess: #1775: 1: Success after binutils/gcc/linux [...] discards 3945fd6d0342 173: onsuccess: #1774: 1: Success after binutils/gcc/glibc [...] discards 1d7ba1735c45 172: onsuccess: #1773: 1: Success after binutils/gcc/glibc [...] discards 397fc95a7d7d 171: onsuccess: #1772: 1: Success after binutils/gcc/gdb: [...] discards 78f1fdab48d1 170: onsuccess: #1771: 1: Success after binutils/gcc/linux [...] discards e49f2e428a9c 169: onsuccess: #1770: 1: Success after gcc/linux/glibc/qe [...] discards dd526e59f021 168: onsuccess: #1769: 1: Success after binutils/gcc/gdb: [...] discards f23b71934b98 167: onsuccess: #1768: 1: Success after binutils/gcc/linux [...] discards 63747928634e 166: onsuccess: #1767: 1: Success after binutils/gcc/linux [...] discards 8ef2dd080b19 165: onsuccess: #1766: 1: Success after binutils/gcc/linux [...] discards 88d713a0b485 164: onsuccess: #1765: 1: Success after binutils/gcc/gdb: [...] discards 8001247fdd52 163: onsuccess: #1764: 1: Success after gcc/linux: 141 commits new bf8a1fea9ea9 163: onsuccess: #1764: 1: Success after gcc/linux: 141 commits new 6cfa18f5f8ef 164: onsuccess: #1765: 1: Success after binutils/gcc/gdb: [...] new eba85c20b736 165: onsuccess: #1766: 1: Success after binutils/gcc/linux [...] new fc24f8267a5a 166: onsuccess: #1767: 1: Success after binutils/gcc/linux [...] new ad868496607b 167: onsuccess: #1768: 1: Success after binutils/gcc/linux [...] new 7a7bd6431dfb 168: onsuccess: #1769: 1: Success after binutils/gcc/gdb: [...] new 4c42377d1750 169: onsuccess: #1770: 1: Success after gcc/linux/glibc/qe [...] new 6be7602e4bab 170: onsuccess: #1771: 1: Success after binutils/gcc/linux [...] new 52d7c0aeeed2 171: onsuccess: #1772: 1: Success after binutils/gcc/gdb: [...] new ac3aef2fcb5d 172: onsuccess: #1773: 1: Success after binutils/gcc/glibc [...] new dae122149f70 173: onsuccess: #1774: 1: Success after binutils/gcc/glibc [...] new ff372a46c5d4 174: onsuccess: #1775: 1: Success after binutils/gcc/linux [...] new e233a3e51234 175: onsuccess: #1776: 1: Success after binutils/gcc/linux [...] new 969918467f03 176: onsuccess: #1791: 1: Success after binutils/gcc/linux [...] new b9de9d52b3cf 177: onsuccess: #1793: 1: Success after binutils/gcc/linux [...] new 6953b0b61fb6 178: onsuccess: #1799: 1: Success after binutils/gcc/linux [...] new 12f1dca33226 179: onsuccess: #1810: 1: Success after binutils/gcc/linux [...] new d119030ce51d 180: onsuccess: #1831: 1: Success after binutils/gcc/linux [...] new faa390cdc7c7 181: onsuccess: #1857: 1: Success after binutils/gcc/linux [...] new 29c29671a77f 182: onsuccess: #1860: 1: Success after binutils/gcc/linux [...] new 8dfe9f57694d 183: onsuccess: #1897: 1: Success after binutils/gcc/linux [...] new 61d081f79de2 184: onsuccess: #1898: 1: Success after binutils/gcc/gdb: [...] new 7dc88ad6712a 185: onsuccess: #1906: 1: Success after binutils/gcc/linux [...] new d8367496b445 186: onsuccess: #1907: 1: Success after binutils/gcc/gdb: [...] new 428000dfa7ad 187: onsuccess: #1908: 1: Success after binutils/gcc/linux [...] new 63c0248a969c 188: onsuccess: #1909: 1: Success after binutils/gcc/gdb: [...] new 93bdb0e7dae9 189: onsuccess: #1912: 1: Success after binutils/gcc/linux [...] new 888e4974e41a 190: onsuccess: #1913: 1: Success after binutils/gcc/linux [...] new c8a2710c493c 191: onsuccess: #1949: 1: Success after binutils/gcc/linux [...] new e1d4b9eb2418 192: onsuccess: #1951: 1: Success after binutils/gcc/gdb: [...] new 0a1e6a8a3c76 193: onsuccess: #1992: 1: Success after binutils: 151 commits new dc2096b3ffd4 194: onsuccess: #1995: 1: Success after linux: 517 commits new 889df6e6fcd0 195: onsuccess: #1996: 1: Success after binutils/gcc/glibc [...] new d483182f6636 196: onsuccess: #1997: 1: Success after binutils/gcc/gdb: [...] new fcd9f55f1f8f 197: onsuccess: #1998: 1: Success after binutils/gcc/gdb: [...] new 46ff526bf027 198: onsuccess: #1999: 1: Success after binutils/gcc/linux [...] new 59a7511b9949 199: onsuccess: #2000: 1: Success after gcc: 5 commits new ecd22a2825a1 200: onsuccess: #2001: 1: Success after binutils/gcc/gdb: [...] new 26e4a93eab8d 201: onsuccess: #2002: 1: Success after gcc/glibc: 5 commits new 49000883f62a 202: onsuccess: #2003: 1: Success after binutils/gcc/linux [...] new 4442466f38e8 203: onsuccess: #2004: 1: Success after binutils/gcc/gdb: [...] new 2a1cbf2e33ff 204: onsuccess: #2005: 1: Success after binutils/gcc/linux [...] new b3f8d4c7478a 205: onsuccess: #2006: 1: Success after gcc: 3 commits new b34d69507c9b 206: onsuccess: #2007: 1: Success after gcc: 2 commits new 26509e8e2b77 207: onsuccess: #2010: 1: Success after gcc: 4 commits new e591c42d7066 208: onsuccess: #2012: 1: Success after linux: 12 commits new 27d5673e6740 209: onsuccess: #2014: 1: Success after binutils: 12 commits new 0560bf6f22e1 210: onsuccess: #2017: 1: Success after binutils: 6 commits new c457ee6fc2b2 211: onsuccess: #2020: 1: Success after binutils: 10 commits new 24f69be1711a 212: onsuccess: #2022: 1: Success after linux: 3 commits new 8062c6e1b740 213: onsuccess: #2024: 1: Success after binutils: 3 commits new f73a3e156667 214: onsuccess: #2026: 1: Success after binutils/gcc/gdb/q [...] new 9b7e659e35ee 215: onsuccess: #2027: 1: Success after binutils/gcc/glibc [...] new 1d830ecfc546 216: onsuccess: #2028: 1: Success after binutils/gcc/linux [...] new eda613274b56 217: onsuccess: #2029: 1: Success after binutils/gcc/glibc [...] new 565f4294b70a 218: onsuccess: #2030: 1: Success after gcc: 5 commits new 7c436ddaebc0 219: onsuccess: #2031: 1: Success after binutils/gcc/glibc [...] new 2d12518d8c35 220: onsuccess: #2032: 1: Success after binutils/gcc/linux [...] new 52feb55cf7fb 221: onsuccess: #2033: 1: Success after binutils/gdb: 2 commits new 8f7334bb3db5 222: onsuccess: #2035: 1: Success after binutils/gcc/glibc [...] new ee60809ef3ac 223: onsuccess: #2036: 1: Success after binutils/gcc/linux [...] new a0d88ed0d6e2 224: onsuccess: #2038: 1: Success after binutils/gcc/linux [...] new a7057ec26c89 225: onsuccess: #2039: 1: Success after binutils/linux/gli [...] new 0967f0eca425 226: onsuccess: #2040: 1: Success after binutils/gcc/gdb: [...] new 59e28369a227 227: onsuccess: #2041: 1: Success after binutils/gcc/linux [...] new 8946e0c79e67 228: onsuccess: #2042: 1: Success after basepoints/gcc-13- [...] new 68a31bc50264 229: onsuccess: #2043: 1: Success after binutils/gcc/linux [...] new 5930aa804c66 230: onsuccess: #2044: 1: Success after binutils/gcc/linux [...] new 4aaee5387afc 231: onsuccess: #2047: 1: Success after gcc: 4 commits new b4ba1d5a90a5 232: onsuccess: #2048: 1: Success after glibc: 2 commits new 99663b79112f 233: onsuccess: #2049: 1: Success after binutils/gcc/linux [...] new 44a9fd5d047f 234: onsuccess: #2050: 1: Success after binutils/gcc/linux [...] new a52b4f337a4e 235: onsuccess: #2051: 1: Success after binutils/linux/gdb [...] new 214b7592b5ff 236: onsuccess: #2052: 1: Success after binutils/gcc/gdb: [...] new 72eb4f9008dd 237: onsuccess: #2053: 1: Success after binutils/gcc/linux [...] new 5d87560ebce9 238: onsuccess: #2054: 1: Success after binutils/gcc/linux [...] new a4268ac06760 239: onsuccess: #2055: 1: Success after binutils/gcc/linux [...] new cef21c90934d 240: onsuccess: #2056: 1: Success after binutils/gcc/gdb: [...] new 5139a9a3eee5 241: onsuccess: #2057: 1: Success after binutils/gcc/linux [...] new 62dc3359ecc1 242: onsuccess: #2058: 1: Success after binutils/gcc/linux [...] new 8ff61fa7db1d 243: onsuccess: #2059: 1: Success after basepoints/gcc-13- [...] new ece67097840a 244: onsuccess: #2060: 1: Success after binutils/gcc/gdb/q [...] new 4a7380338449 245: onsuccess: #2061: 1: Success after binutils/gcc/linux [...] new f04c8d9cb62e 246: onsuccess: #2062: 1: Success after binutils/gcc/linux [...] new dfbaa54db459 247: onsuccess: #2063: 1: Success after binutils/gcc/linux [...] new 5d4fa79cec29 248: onsuccess: #2064: 1: Success after binutils/gcc/gdb/q [...] new 5b6d50e7b996 249: onsuccess: #2065: 1: Success after binutils/gcc/linux [...] new 008276d03e4f 250: onsuccess: #2066: 1: Success after binutils/gcc/linux [...] new e3e6d36e2052 251: onsuccess: #2067: 1: Success after binutils/gcc/gdb: [...] new 1bc1d5445dcc 252: onsuccess: #2068: 1: Success after binutils/gdb: 6 commits new 7353ca11c2fd 253: onsuccess: #2069: 1: Success after gcc/linux: 109 commits new 482d61606ace 254: onsuccess: #2070: 1: Success after binutils/gcc/gdb/q [...] new d02e8dbaae2d 255: onsuccess: #2071: 1: Success after binutils/gcc/gdb: [...] new 9f27b2f68d7b 256: onsuccess: #2072: 1: Success after binutils/gcc/gdb: [...] new 4a378529691c 257: onsuccess: #2073: 1: Success after v7.2.0-211-g562d4a [...] new c165db2acb6a 258: onsuccess: #2074: 1: Success after binutils/gcc/glibc [...] new 804d58991000 259: onsuccess: #2075: 1: Success after glibc: 2 commits new fd322ec46f23 260: onsuccess: #2076: 1: Success after binutils/gcc/glibc [...] new fa43fdc7aa5c 261: onsuccess: #2077: 1: Success after binutils/gcc/linux [...] new 29aae136b0b4 262: onsuccess: #2078: 1: Success after binutils/gcc/linux [...] new 8aaaadc3da42 263: onsuccess: #2079: 1: Success after binutils/gcc/gdb: [...] new 6af1bfb0601a 264: onsuccess: #2080: 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 (d2972e5ed009) \ 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 -> 1776 bytes 02-prepare_abe/console.log.xz | Bin 2792 -> 2804 bytes 03-build_abe-binutils/console.log.xz | Bin 31984 -> 32332 bytes 04-build_abe-stage1/console.log.xz | Bin 92892 -> 92320 bytes 06-build_abe-linux/console.log.xz | Bin 9224 -> 9256 bytes 07-build_abe-glibc/console.log.xz | Bin 236440 -> 238404 bytes 08-build_abe-stage2/console.log.xz | Bin 226256 -> 226772 bytes 09-build_abe-gdb/console.log.xz | Bin 38952 -> 39484 bytes 10-build_abe-qemu/console.log.xz | Bin 30684 -> 30940 bytes 11-build_abe-dejagnu/console.log.xz | Bin 3872 -> 3884 bytes 12-build_abe-check_gcc/console.log.xz | Bin 3072 -> 2668 bytes 13-check_regression/console.log.xz | Bin 5736 -> 5916 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 | 29 +- 13-check_regression/results.compare2 | 34 +- 13-check_regression/results.regressions | 26 + 14-update_baseline/console.log | 70 +- dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- git/gdb_rev | 2 +- mail/mail-body.txt | 26 + manifest.sh | 34 +- results | 26 + sumfiles/g++.log.xz | Bin 2682368 -> 2678088 bytes sumfiles/g++.sum | 22 +- sumfiles/gcc.log.xz | Bin 2233816 -> 2246924 bytes sumfiles/gcc.sum | 2352 +++++++++++++++---------------- sumfiles/gfortran.log.xz | Bin 890476 -> 895960 bytes sumfiles/gfortran.sum | 2 +- sumfiles/libatomic.log.xz | Bin 2260 -> 2260 bytes sumfiles/libatomic.sum | 2 +- sumfiles/libgomp.log.xz | Bin 214036 -> 214012 bytes sumfiles/libgomp.sum | 2 +- sumfiles/libitm.log.xz | Bin 2664 -> 2676 bytes sumfiles/libitm.sum | 2 +- sumfiles/libstdc++.log.xz | Bin 425724 -> 437856 bytes sumfiles/libstdc++.sum | 8 +- 40 files changed, 1390 insertions(+), 1286 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