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 4cbba57de7d3 262: onsuccess: #2078: 1: Success after binutils/gcc/linux [...] discards 3c0794735ae3 261: onsuccess: #2077: 1: Success after binutils/gcc/linux [...] discards 4044a55242b9 260: onsuccess: #2076: 1: Success after binutils/gcc/glibc [...] discards 45b68b7acf14 259: onsuccess: #2075: 1: Success after glibc: 2 commits discards b939887bddd2 258: onsuccess: #2074: 1: Success after binutils/gcc/glibc [...] discards 21129e7a3b90 257: onsuccess: #2073: 1: Success after v7.2.0-211-g562d4a [...] discards 1bf7ef45084d 256: onsuccess: #2072: 1: Success after binutils/gcc/gdb: [...] discards 1ef383591eb7 255: onsuccess: #2071: 1: Success after binutils/gcc/gdb: [...] discards 7e31934ce9d6 254: onsuccess: #2070: 1: Success after binutils/gcc/gdb/q [...] discards c2201a011842 253: onsuccess: #2069: 1: Success after gcc/linux: 109 commits discards 70e7a6973b5d 252: onsuccess: #2068: 1: Success after binutils/gdb: 6 commits discards 34bbc5be0cf6 251: onsuccess: #2067: 1: Success after binutils/gcc/gdb: [...] discards 999940d372c4 250: onsuccess: #2066: 1: Success after binutils/gcc/linux [...] discards d850e92f788c 249: onsuccess: #2065: 1: Success after binutils/gcc/linux [...] discards 6978ce351d69 248: onsuccess: #2064: 1: Success after binutils/gcc/gdb/q [...] discards 83ca901d5f16 247: onsuccess: #2063: 1: Success after binutils/gcc/linux [...] discards 9b16a6036ecf 246: onsuccess: #2062: 1: Success after binutils/gcc/linux [...] discards ba74d3454fb8 245: onsuccess: #2061: 1: Success after binutils/gcc/linux [...] discards 8c6aca8da9d0 244: onsuccess: #2060: 1: Success after binutils/gcc/gdb/q [...] discards c4d4c5f5633b 243: onsuccess: #2059: 1: Success after basepoints/gcc-13- [...] discards bd8c58502fa2 242: onsuccess: #2058: 1: Success after binutils/gcc/linux [...] discards bf46e71625fd 241: onsuccess: #2057: 1: Success after binutils/gcc/linux [...] discards 7c3f15417252 240: onsuccess: #2056: 1: Success after binutils/gcc/gdb: [...] discards df729fe13b59 239: onsuccess: #2055: 1: Success after binutils/gcc/linux [...] discards e2e7a154d5d3 238: onsuccess: #2054: 1: Success after binutils/gcc/linux [...] discards eddd493760fd 237: onsuccess: #2053: 1: Success after binutils/gcc/linux [...] discards 9edb93435e3d 236: onsuccess: #2052: 1: Success after binutils/gcc/gdb: [...] discards d6d497abf479 235: onsuccess: #2051: 1: Success after binutils/linux/gdb [...] discards 3769a7412cd6 234: onsuccess: #2050: 1: Success after binutils/gcc/linux [...] discards 3270e2bd0d36 233: onsuccess: #2049: 1: Success after binutils/gcc/linux [...] discards 27dfe2bf72ee 232: onsuccess: #2048: 1: Success after glibc: 2 commits discards 72aa1d188f43 231: onsuccess: #2047: 1: Success after gcc: 4 commits discards e936c6ece367 230: onsuccess: #2044: 1: Success after binutils/gcc/linux [...] discards 4c1828a409ee 229: onsuccess: #2043: 1: Success after binutils/gcc/linux [...] discards dd10d2482379 228: onsuccess: #2042: 1: Success after basepoints/gcc-13- [...] discards a73966e88299 227: onsuccess: #2041: 1: Success after binutils/gcc/linux [...] discards eb455c3b1bb1 226: onsuccess: #2040: 1: Success after binutils/gcc/gdb: [...] discards 513652e7f00d 225: onsuccess: #2039: 1: Success after binutils/linux/gli [...] discards 4223010f5699 224: onsuccess: #2038: 1: Success after binutils/gcc/linux [...] discards d72c2686d888 223: onsuccess: #2036: 1: Success after binutils/gcc/linux [...] discards 253ed7d688f6 222: onsuccess: #2035: 1: Success after binutils/gcc/glibc [...] discards 3215808c1f68 221: onsuccess: #2033: 1: Success after binutils/gdb: 2 commits discards a488eef91a68 220: onsuccess: #2032: 1: Success after binutils/gcc/linux [...] discards 05b5f39dd43a 219: onsuccess: #2031: 1: Success after binutils/gcc/glibc [...] discards 115445641038 218: onsuccess: #2030: 1: Success after gcc: 5 commits discards b63373f2e042 217: onsuccess: #2029: 1: Success after binutils/gcc/glibc [...] discards 2ea9dedc1cb8 216: onsuccess: #2028: 1: Success after binutils/gcc/linux [...] discards e3adeda0c438 215: onsuccess: #2027: 1: Success after binutils/gcc/glibc [...] discards 055718d3558e 214: onsuccess: #2026: 1: Success after binutils/gcc/gdb/q [...] discards 63ca4b101893 213: onsuccess: #2024: 1: Success after binutils: 3 commits discards 4044950ff12c 212: onsuccess: #2022: 1: Success after linux: 3 commits discards 22eca23b0350 211: onsuccess: #2020: 1: Success after binutils: 10 commits discards 7b9868ed0068 210: onsuccess: #2017: 1: Success after binutils: 6 commits discards 8b21681b6535 209: onsuccess: #2014: 1: Success after binutils: 12 commits discards cff84f7d1dc0 208: onsuccess: #2012: 1: Success after linux: 12 commits discards feb92b916a23 207: onsuccess: #2010: 1: Success after gcc: 4 commits discards 5004688fb720 206: onsuccess: #2007: 1: Success after gcc: 2 commits discards 8be432d18b63 205: onsuccess: #2006: 1: Success after gcc: 3 commits discards 7ac131054e9f 204: onsuccess: #2005: 1: Success after binutils/gcc/linux [...] discards 59d4a9a28e69 203: onsuccess: #2004: 1: Success after binutils/gcc/gdb: [...] discards 588750b2725e 202: onsuccess: #2003: 1: Success after binutils/gcc/linux [...] discards 2fdacd8ff1e3 201: onsuccess: #2002: 1: Success after gcc/glibc: 5 commits discards c7aadd737162 200: onsuccess: #2001: 1: Success after binutils/gcc/gdb: [...] discards d0a5fa7fda55 199: onsuccess: #2000: 1: Success after gcc: 5 commits discards 1c33f2d97dac 198: onsuccess: #1999: 1: Success after binutils/gcc/linux [...] discards 976e66f40434 197: onsuccess: #1998: 1: Success after binutils/gcc/gdb: [...] discards 67ecbcd4ccd9 196: onsuccess: #1997: 1: Success after binutils/gcc/gdb: [...] discards 89331b2439d8 195: onsuccess: #1996: 1: Success after binutils/gcc/glibc [...] discards 1fa3145f65b1 194: onsuccess: #1995: 1: Success after linux: 517 commits discards 4861724d1fb4 193: onsuccess: #1992: 1: Success after binutils: 151 commits discards dcf8c22cd659 192: onsuccess: #1951: 1: Success after binutils/gcc/gdb: [...] discards 3d6ac1270692 191: onsuccess: #1949: 1: Success after binutils/gcc/linux [...] discards a36b3228957a 190: onsuccess: #1913: 1: Success after binutils/gcc/linux [...] discards 27b3f4aa793a 189: onsuccess: #1912: 1: Success after binutils/gcc/linux [...] discards dff21db8153a 188: onsuccess: #1909: 1: Success after binutils/gcc/gdb: [...] discards 341eb5a4637c 187: onsuccess: #1908: 1: Success after binutils/gcc/linux [...] discards 279e8a7b5cc5 186: onsuccess: #1907: 1: Success after binutils/gcc/gdb: [...] discards 277ec1c779e1 185: onsuccess: #1906: 1: Success after binutils/gcc/linux [...] discards 75281ff687a2 184: onsuccess: #1898: 1: Success after binutils/gcc/gdb: [...] discards 9661504be325 183: onsuccess: #1897: 1: Success after binutils/gcc/linux [...] discards 984b5fcb17b5 182: onsuccess: #1860: 1: Success after binutils/gcc/linux [...] discards 65dcbee153c8 181: onsuccess: #1857: 1: Success after binutils/gcc/linux [...] discards 768139445723 180: onsuccess: #1831: 1: Success after binutils/gcc/linux [...] discards 85de1d4fa604 179: onsuccess: #1810: 1: Success after binutils/gcc/linux [...] discards acfe470e801e 178: onsuccess: #1799: 1: Success after binutils/gcc/linux [...] discards 778f09be6523 177: onsuccess: #1793: 1: Success after binutils/gcc/linux [...] discards e045bea8419c 176: onsuccess: #1791: 1: Success after binutils/gcc/linux [...] discards b25bbee023d4 175: onsuccess: #1776: 1: Success after binutils/gcc/linux [...] discards 8ef35b60ab1f 174: onsuccess: #1775: 1: Success after binutils/gcc/linux [...] discards 9da47b3c35b1 173: onsuccess: #1774: 1: Success after binutils/gcc/glibc [...] discards 500311c31c65 172: onsuccess: #1773: 1: Success after binutils/gcc/glibc [...] discards d2150fb839a7 171: onsuccess: #1772: 1: Success after binutils/gcc/gdb: [...] discards a64306f73563 170: onsuccess: #1771: 1: Success after binutils/gcc/linux [...] discards 6318cca6e152 169: onsuccess: #1770: 1: Success after gcc/linux/glibc/qe [...] discards 46686bb998e8 168: onsuccess: #1769: 1: Success after binutils/gcc/gdb: [...] discards 43e6cb01a217 167: onsuccess: #1768: 1: Success after binutils/gcc/linux [...] discards 990dd7790ce2 166: onsuccess: #1767: 1: Success after binutils/gcc/linux [...] discards 279c4773396c 165: onsuccess: #1766: 1: Success after binutils/gcc/linux [...] discards 31151be724f6 164: onsuccess: #1765: 1: Success after binutils/gcc/gdb: [...] discards d0d613b23ef2 163: onsuccess: #1764: 1: Success after gcc/linux: 141 commits discards 743766e8d5a8 162: onsuccess: #1763: 1: Success after binutils/gcc/linux [...] new 3ca1f69a45ba 162: onsuccess: #1763: 1: Success after binutils/gcc/linux [...] new 8001247fdd52 163: onsuccess: #1764: 1: Success after gcc/linux: 141 commits new 88d713a0b485 164: onsuccess: #1765: 1: Success after binutils/gcc/gdb: [...] new 8ef2dd080b19 165: onsuccess: #1766: 1: Success after binutils/gcc/linux [...] new 63747928634e 166: onsuccess: #1767: 1: Success after binutils/gcc/linux [...] new f23b71934b98 167: onsuccess: #1768: 1: Success after binutils/gcc/linux [...] new dd526e59f021 168: onsuccess: #1769: 1: Success after binutils/gcc/gdb: [...] new e49f2e428a9c 169: onsuccess: #1770: 1: Success after gcc/linux/glibc/qe [...] new 78f1fdab48d1 170: onsuccess: #1771: 1: Success after binutils/gcc/linux [...] new 397fc95a7d7d 171: onsuccess: #1772: 1: Success after binutils/gcc/gdb: [...] new 1d7ba1735c45 172: onsuccess: #1773: 1: Success after binutils/gcc/glibc [...] new 3945fd6d0342 173: onsuccess: #1774: 1: Success after binutils/gcc/glibc [...] new 623fdb5009e6 174: onsuccess: #1775: 1: Success after binutils/gcc/linux [...] new 7348ae9eb5ea 175: onsuccess: #1776: 1: Success after binutils/gcc/linux [...] new 813e71a80c0c 176: onsuccess: #1791: 1: Success after binutils/gcc/linux [...] new 10a119e913ba 177: onsuccess: #1793: 1: Success after binutils/gcc/linux [...] new 47ca10db0992 178: onsuccess: #1799: 1: Success after binutils/gcc/linux [...] new 00f6356de04f 179: onsuccess: #1810: 1: Success after binutils/gcc/linux [...] new f06f7b678338 180: onsuccess: #1831: 1: Success after binutils/gcc/linux [...] new d1cd54583eef 181: onsuccess: #1857: 1: Success after binutils/gcc/linux [...] new 393e6e5517a4 182: onsuccess: #1860: 1: Success after binutils/gcc/linux [...] new 7d96c529f3c9 183: onsuccess: #1897: 1: Success after binutils/gcc/linux [...] new ca1e0ba5f33b 184: onsuccess: #1898: 1: Success after binutils/gcc/gdb: [...] new 6f53500b8a99 185: onsuccess: #1906: 1: Success after binutils/gcc/linux [...] new 27ca640e2b4d 186: onsuccess: #1907: 1: Success after binutils/gcc/gdb: [...] new c28300526abe 187: onsuccess: #1908: 1: Success after binutils/gcc/linux [...] new d4cdf1b3d402 188: onsuccess: #1909: 1: Success after binutils/gcc/gdb: [...] new 4ab98230e2bc 189: onsuccess: #1912: 1: Success after binutils/gcc/linux [...] new 21b9f15b3dd9 190: onsuccess: #1913: 1: Success after binutils/gcc/linux [...] new f696d2f2cbee 191: onsuccess: #1949: 1: Success after binutils/gcc/linux [...] new 83f52e0a7ac8 192: onsuccess: #1951: 1: Success after binutils/gcc/gdb: [...] new 9bbf1f7dfe42 193: onsuccess: #1992: 1: Success after binutils: 151 commits new c78c498594ac 194: onsuccess: #1995: 1: Success after linux: 517 commits new 44c0b7554674 195: onsuccess: #1996: 1: Success after binutils/gcc/glibc [...] new fd1b2eb997e2 196: onsuccess: #1997: 1: Success after binutils/gcc/gdb: [...] new 49432efd3896 197: onsuccess: #1998: 1: Success after binutils/gcc/gdb: [...] new c40461b98c48 198: onsuccess: #1999: 1: Success after binutils/gcc/linux [...] new 1975716838b1 199: onsuccess: #2000: 1: Success after gcc: 5 commits new a2fb9428a139 200: onsuccess: #2001: 1: Success after binutils/gcc/gdb: [...] new b00c79027a0f 201: onsuccess: #2002: 1: Success after gcc/glibc: 5 commits new 6add64085e1f 202: onsuccess: #2003: 1: Success after binutils/gcc/linux [...] new 2799ae5d9f03 203: onsuccess: #2004: 1: Success after binutils/gcc/gdb: [...] new 24af50bf4aa1 204: onsuccess: #2005: 1: Success after binutils/gcc/linux [...] new 17b95498132e 205: onsuccess: #2006: 1: Success after gcc: 3 commits new 25f12be41b65 206: onsuccess: #2007: 1: Success after gcc: 2 commits new a2efd213938b 207: onsuccess: #2010: 1: Success after gcc: 4 commits new 6fcc464bdab5 208: onsuccess: #2012: 1: Success after linux: 12 commits new cdac899720b0 209: onsuccess: #2014: 1: Success after binutils: 12 commits new 7cede4f1e7f5 210: onsuccess: #2017: 1: Success after binutils: 6 commits new 18134e5b6a84 211: onsuccess: #2020: 1: Success after binutils: 10 commits new 772ed211fc5a 212: onsuccess: #2022: 1: Success after linux: 3 commits new 4f6267ab8722 213: onsuccess: #2024: 1: Success after binutils: 3 commits new be7adae18a0f 214: onsuccess: #2026: 1: Success after binutils/gcc/gdb/q [...] new 5c9aea790f0a 215: onsuccess: #2027: 1: Success after binutils/gcc/glibc [...] new 7b7e6d48ffd8 216: onsuccess: #2028: 1: Success after binutils/gcc/linux [...] new c643f31197bb 217: onsuccess: #2029: 1: Success after binutils/gcc/glibc [...] new e2dd23dadb33 218: onsuccess: #2030: 1: Success after gcc: 5 commits new 88bb5aeba80e 219: onsuccess: #2031: 1: Success after binutils/gcc/glibc [...] new fe58ce9642ec 220: onsuccess: #2032: 1: Success after binutils/gcc/linux [...] new 11a2d6a79edb 221: onsuccess: #2033: 1: Success after binutils/gdb: 2 commits new 15edb61dd5c3 222: onsuccess: #2035: 1: Success after binutils/gcc/glibc [...] new e23345300af1 223: onsuccess: #2036: 1: Success after binutils/gcc/linux [...] new 107f09769b09 224: onsuccess: #2038: 1: Success after binutils/gcc/linux [...] new b158112e50b0 225: onsuccess: #2039: 1: Success after binutils/linux/gli [...] new c3e6968ad634 226: onsuccess: #2040: 1: Success after binutils/gcc/gdb: [...] new adc1112e4544 227: onsuccess: #2041: 1: Success after binutils/gcc/linux [...] new 63458fd80ce5 228: onsuccess: #2042: 1: Success after basepoints/gcc-13- [...] new e46ade7344e8 229: onsuccess: #2043: 1: Success after binutils/gcc/linux [...] new 4036938de0f8 230: onsuccess: #2044: 1: Success after binutils/gcc/linux [...] new 0611aff54d6c 231: onsuccess: #2047: 1: Success after gcc: 4 commits new e68ac7af0699 232: onsuccess: #2048: 1: Success after glibc: 2 commits new 535ac7dcc25e 233: onsuccess: #2049: 1: Success after binutils/gcc/linux [...] new d61c6ddd9827 234: onsuccess: #2050: 1: Success after binutils/gcc/linux [...] new afca2948ac69 235: onsuccess: #2051: 1: Success after binutils/linux/gdb [...] new e662a23c60ef 236: onsuccess: #2052: 1: Success after binutils/gcc/gdb: [...] new 227ed58e31fa 237: onsuccess: #2053: 1: Success after binutils/gcc/linux [...] new 4b410fa456b6 238: onsuccess: #2054: 1: Success after binutils/gcc/linux [...] new 5ea6db8bcf2c 239: onsuccess: #2055: 1: Success after binutils/gcc/linux [...] new 3ad112dd93cd 240: onsuccess: #2056: 1: Success after binutils/gcc/gdb: [...] new 1be99e1c47da 241: onsuccess: #2057: 1: Success after binutils/gcc/linux [...] new 9ea40d7214d0 242: onsuccess: #2058: 1: Success after binutils/gcc/linux [...] new 72c2e1692a31 243: onsuccess: #2059: 1: Success after basepoints/gcc-13- [...] new a461d4aba473 244: onsuccess: #2060: 1: Success after binutils/gcc/gdb/q [...] new 0e65dc6cbab8 245: onsuccess: #2061: 1: Success after binutils/gcc/linux [...] new 5b31d6b7edd2 246: onsuccess: #2062: 1: Success after binutils/gcc/linux [...] new 8525eabb8bf3 247: onsuccess: #2063: 1: Success after binutils/gcc/linux [...] new 99878e815061 248: onsuccess: #2064: 1: Success after binutils/gcc/gdb/q [...] new 6617ad46dbff 249: onsuccess: #2065: 1: Success after binutils/gcc/linux [...] new 56a7a31f2186 250: onsuccess: #2066: 1: Success after binutils/gcc/linux [...] new 3b5fe8869081 251: onsuccess: #2067: 1: Success after binutils/gcc/gdb: [...] new 240c5d033abb 252: onsuccess: #2068: 1: Success after binutils/gdb: 6 commits new 641ce7f59168 253: onsuccess: #2069: 1: Success after gcc/linux: 109 commits new 7a3baba2b923 254: onsuccess: #2070: 1: Success after binutils/gcc/gdb/q [...] new d3fb5ee0c0ec 255: onsuccess: #2071: 1: Success after binutils/gcc/gdb: [...] new 61586e97e8de 256: onsuccess: #2072: 1: Success after binutils/gcc/gdb: [...] new 10e37d322156 257: onsuccess: #2073: 1: Success after v7.2.0-211-g562d4a [...] new b1345cdd40b1 258: onsuccess: #2074: 1: Success after binutils/gcc/glibc [...] new 976bf5cf9653 259: onsuccess: #2075: 1: Success after glibc: 2 commits new f37bee922763 260: onsuccess: #2076: 1: Success after binutils/gcc/glibc [...] new b26c9c8dc3ef 261: onsuccess: #2077: 1: Success after binutils/gcc/linux [...] new fb2c01bef3ee 262: onsuccess: #2078: 1: Success after binutils/gcc/linux [...] new d2972e5ed009 263: onsuccess: #2079: 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 (4cbba57de7d3) \ 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 1772 -> 1796 bytes 02-prepare_abe/console.log.xz | Bin 2800 -> 2792 bytes 03-build_abe-binutils/console.log.xz | Bin 32016 -> 31984 bytes 04-build_abe-stage1/console.log.xz | Bin 92028 -> 92892 bytes 06-build_abe-linux/console.log.xz | Bin 9260 -> 9224 bytes 07-build_abe-glibc/console.log.xz | Bin 237024 -> 236440 bytes 08-build_abe-stage2/console.log.xz | Bin 225160 -> 226256 bytes 09-build_abe-gdb/console.log.xz | Bin 40120 -> 38952 bytes 10-build_abe-qemu/console.log.xz | Bin 31004 -> 30684 bytes 11-build_abe-dejagnu/console.log.xz | Bin 3940 -> 3872 bytes 12-build_abe-check_gcc/console.log.xz | Bin 2508 -> 3072 bytes 13-check_regression/console.log.xz | Bin 6256 -> 5736 bytes 13-check_regression/mail-body.txt | 30 - 13-check_regression/results.compare | 26 +- 13-check_regression/results.compare2 | 41 +- 14-update_baseline/console.log | 66 +- 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 | 32 +- mail/mail-subject.txt | 2 +- manifest.sh | 34 +- sumfiles/g++.log.xz | Bin 2660828 -> 2682368 bytes sumfiles/g++.sum | 18 +- sumfiles/gcc.log.xz | Bin 2267784 -> 2233816 bytes sumfiles/gcc.sum | 2430 ++++++++++++++++----------------- sumfiles/gfortran.log.xz | Bin 895956 -> 890476 bytes sumfiles/gfortran.sum | 2 +- sumfiles/libatomic.log.xz | Bin 2260 -> 2260 bytes sumfiles/libatomic.sum | 2 +- sumfiles/libgomp.log.xz | Bin 214020 -> 214036 bytes sumfiles/libgomp.sum | 2 +- sumfiles/libitm.log.xz | Bin 2668 -> 2664 bytes sumfiles/libitm.sum | 2 +- sumfiles/libstdc++.log.xz | Bin 444692 -> 425724 bytes sumfiles/libstdc++.sum | 8 +- 38 files changed, 1321 insertions(+), 1384 deletions(-)