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 4c0bf76a4841 265: onsuccess: #2081: 1: Success after gcc/linux/glibc/qe [...] discards 2dafbd656fe6 264: onsuccess: #2080: 1: Success after binutils/gcc/gdb: [...] discards 0466d64f1539 263: onsuccess: #2079: 1: Success after binutils/gcc/gdb: [...] discards 0ba44380b6fd 262: onsuccess: #2078: 1: Success after binutils/gcc/linux [...] discards e212f2769853 261: onsuccess: #2077: 1: Success after binutils/gcc/linux [...] discards 42aaef467d1a 260: onsuccess: #2076: 1: Success after binutils/gcc/glibc [...] discards 62ef64021b27 259: onsuccess: #2075: 1: Success after glibc: 2 commits discards 1e450c16622e 258: onsuccess: #2074: 1: Success after binutils/gcc/glibc [...] discards a6ef1666b25e 257: onsuccess: #2073: 1: Success after v7.2.0-211-g562d4a [...] discards b97791554802 256: onsuccess: #2072: 1: Success after binutils/gcc/gdb: [...] discards c6d030af3ea4 255: onsuccess: #2071: 1: Success after binutils/gcc/gdb: [...] discards 6aad49ff4a4d 254: onsuccess: #2070: 1: Success after binutils/gcc/gdb/q [...] discards ebac41eee04d 253: onsuccess: #2069: 1: Success after gcc/linux: 109 commits discards 1b42cfeea992 252: onsuccess: #2068: 1: Success after binutils/gdb: 6 commits discards bedfbfc95cc0 251: onsuccess: #2067: 1: Success after binutils/gcc/gdb: [...] discards a0af8e8150af 250: onsuccess: #2066: 1: Success after binutils/gcc/linux [...] discards 5b283db447d5 249: onsuccess: #2065: 1: Success after binutils/gcc/linux [...] discards 45ea130994c5 248: onsuccess: #2064: 1: Success after binutils/gcc/gdb/q [...] discards af74004031a8 247: onsuccess: #2063: 1: Success after binutils/gcc/linux [...] discards 42f3a9ed7784 246: onsuccess: #2062: 1: Success after binutils/gcc/linux [...] discards 37e22d2b49d6 245: onsuccess: #2061: 1: Success after binutils/gcc/linux [...] discards 23299804e3ca 244: onsuccess: #2060: 1: Success after binutils/gcc/gdb/q [...] discards 4154110f0ba2 243: onsuccess: #2059: 1: Success after basepoints/gcc-13- [...] discards 82d15db5b859 242: onsuccess: #2058: 1: Success after binutils/gcc/linux [...] discards b87d3b80955c 241: onsuccess: #2057: 1: Success after binutils/gcc/linux [...] discards 3b665ebf3cb6 240: onsuccess: #2056: 1: Success after binutils/gcc/gdb: [...] discards ce8060c5b3f2 239: onsuccess: #2055: 1: Success after binutils/gcc/linux [...] discards d197da01de9a 238: onsuccess: #2054: 1: Success after binutils/gcc/linux [...] discards 753f1b1d2e29 237: onsuccess: #2053: 1: Success after binutils/gcc/linux [...] discards 9722880bdf98 236: onsuccess: #2052: 1: Success after binutils/gcc/gdb: [...] discards bf2544077657 235: onsuccess: #2051: 1: Success after binutils/linux/gdb [...] discards 569119705fc2 234: onsuccess: #2050: 1: Success after binutils/gcc/linux [...] discards 590333ebae61 233: onsuccess: #2049: 1: Success after binutils/gcc/linux [...] discards 40c12ab45417 232: onsuccess: #2048: 1: Success after glibc: 2 commits discards 6fd993fc65de 231: onsuccess: #2047: 1: Success after gcc: 4 commits discards 0a4ba0f1daa6 230: onsuccess: #2044: 1: Success after binutils/gcc/linux [...] discards dec23f50aba5 229: onsuccess: #2043: 1: Success after binutils/gcc/linux [...] discards 5ffa6dd86b65 228: onsuccess: #2042: 1: Success after basepoints/gcc-13- [...] discards a398c8035581 227: onsuccess: #2041: 1: Success after binutils/gcc/linux [...] discards 7b110a871065 226: onsuccess: #2040: 1: Success after binutils/gcc/gdb: [...] discards 0e39671f99e5 225: onsuccess: #2039: 1: Success after binutils/linux/gli [...] discards 7ae758cff252 224: onsuccess: #2038: 1: Success after binutils/gcc/linux [...] discards e66a2afb1826 223: onsuccess: #2036: 1: Success after binutils/gcc/linux [...] discards 4a6ad8741669 222: onsuccess: #2035: 1: Success after binutils/gcc/glibc [...] discards 6b6f4e623ea5 221: onsuccess: #2033: 1: Success after binutils/gdb: 2 commits discards 2068fae55d6d 220: onsuccess: #2032: 1: Success after binutils/gcc/linux [...] discards d8c875783bee 219: onsuccess: #2031: 1: Success after binutils/gcc/glibc [...] discards a807813bd79c 218: onsuccess: #2030: 1: Success after gcc: 5 commits discards eaf0cd4d88eb 217: onsuccess: #2029: 1: Success after binutils/gcc/glibc [...] discards 2bb5260cfdd3 216: onsuccess: #2028: 1: Success after binutils/gcc/linux [...] discards aba4c53a3320 215: onsuccess: #2027: 1: Success after binutils/gcc/glibc [...] discards ec8ecc1f2ac0 214: onsuccess: #2026: 1: Success after binutils/gcc/gdb/q [...] discards 4c46db9fad50 213: onsuccess: #2024: 1: Success after binutils: 3 commits discards 7cd49c0b86ce 212: onsuccess: #2022: 1: Success after linux: 3 commits discards 07f7d0eb661f 211: onsuccess: #2020: 1: Success after binutils: 10 commits discards b1d8ea8be3bd 210: onsuccess: #2017: 1: Success after binutils: 6 commits discards 2f583c48c6a5 209: onsuccess: #2014: 1: Success after binutils: 12 commits discards 67a2ef3894d7 208: onsuccess: #2012: 1: Success after linux: 12 commits discards f8c9d1936bae 207: onsuccess: #2010: 1: Success after gcc: 4 commits discards 55308e1b0886 206: onsuccess: #2007: 1: Success after gcc: 2 commits discards 01d0432e9cb2 205: onsuccess: #2006: 1: Success after gcc: 3 commits discards e399e7693cf6 204: onsuccess: #2005: 1: Success after binutils/gcc/linux [...] discards bfed67d6b7b8 203: onsuccess: #2004: 1: Success after binutils/gcc/gdb: [...] discards fe44435a74ab 202: onsuccess: #2003: 1: Success after binutils/gcc/linux [...] discards c34fa302e4d6 201: onsuccess: #2002: 1: Success after gcc/glibc: 5 commits discards 72d26660ddfc 200: onsuccess: #2001: 1: Success after binutils/gcc/gdb: [...] discards c8c1592d541c 199: onsuccess: #2000: 1: Success after gcc: 5 commits discards 53ab24de4443 198: onsuccess: #1999: 1: Success after binutils/gcc/linux [...] discards be1e7794a8d5 197: onsuccess: #1998: 1: Success after binutils/gcc/gdb: [...] discards 68313d43db66 196: onsuccess: #1997: 1: Success after binutils/gcc/gdb: [...] discards 0037e1e12872 195: onsuccess: #1996: 1: Success after binutils/gcc/glibc [...] discards 563e56bf4d90 194: onsuccess: #1995: 1: Success after linux: 517 commits discards 479cfd2c0b2f 193: onsuccess: #1992: 1: Success after binutils: 151 commits discards ff433e8d1c3f 192: onsuccess: #1951: 1: Success after binutils/gcc/gdb: [...] discards 7024afa181e5 191: onsuccess: #1949: 1: Success after binutils/gcc/linux [...] discards 269f4f79b1aa 190: onsuccess: #1913: 1: Success after binutils/gcc/linux [...] discards 10b1e896d3f6 189: onsuccess: #1912: 1: Success after binutils/gcc/linux [...] discards 9333a235dd6a 188: onsuccess: #1909: 1: Success after binutils/gcc/gdb: [...] discards 53ab9bedfc0f 187: onsuccess: #1908: 1: Success after binutils/gcc/linux [...] discards 62382ad03512 186: onsuccess: #1907: 1: Success after binutils/gcc/gdb: [...] discards 97ac92d53967 185: onsuccess: #1906: 1: Success after binutils/gcc/linux [...] discards 8c6d3f0548ea 184: onsuccess: #1898: 1: Success after binutils/gcc/gdb: [...] discards 2cbfee77f419 183: onsuccess: #1897: 1: Success after binutils/gcc/linux [...] discards 6896a34046ef 182: onsuccess: #1860: 1: Success after binutils/gcc/linux [...] discards a41d4bb36f76 181: onsuccess: #1857: 1: Success after binutils/gcc/linux [...] discards 7af1cb888d21 180: onsuccess: #1831: 1: Success after binutils/gcc/linux [...] discards 83d6f60e78f8 179: onsuccess: #1810: 1: Success after binutils/gcc/linux [...] discards 0ac672e15ed1 178: onsuccess: #1799: 1: Success after binutils/gcc/linux [...] discards 453d023edacd 177: onsuccess: #1793: 1: Success after binutils/gcc/linux [...] discards 3ab6c741dcd9 176: onsuccess: #1791: 1: Success after binutils/gcc/linux [...] discards cdbc150f8187 175: onsuccess: #1776: 1: Success after binutils/gcc/linux [...] discards 5edc588661cd 174: onsuccess: #1775: 1: Success after binutils/gcc/linux [...] discards 9ff42175590e 173: onsuccess: #1774: 1: Success after binutils/gcc/glibc [...] discards 4a5377179a14 172: onsuccess: #1773: 1: Success after binutils/gcc/glibc [...] discards 00b4ac95c2f7 171: onsuccess: #1772: 1: Success after binutils/gcc/gdb: [...] discards f957c3c10958 170: onsuccess: #1771: 1: Success after binutils/gcc/linux [...] discards da60c1016d14 169: onsuccess: #1770: 1: Success after gcc/linux/glibc/qe [...] discards a710336658a2 168: onsuccess: #1769: 1: Success after binutils/gcc/gdb: [...] discards b7a6539efe6a 167: onsuccess: #1768: 1: Success after binutils/gcc/linux [...] discards 755fee5f79f4 166: onsuccess: #1767: 1: Success after binutils/gcc/linux [...] discards 221c1816397a 165: onsuccess: #1766: 1: Success after binutils/gcc/linux [...] new d2ecc30c979a 165: onsuccess: #1766: 1: Success after binutils/gcc/linux [...] new 8dadbe0efd02 166: onsuccess: #1767: 1: Success after binutils/gcc/linux [...] new 1cc29c403757 167: onsuccess: #1768: 1: Success after binutils/gcc/linux [...] new a397bd64f40a 168: onsuccess: #1769: 1: Success after binutils/gcc/gdb: [...] new 2743250bfc79 169: onsuccess: #1770: 1: Success after gcc/linux/glibc/qe [...] new 116c3883a0e1 170: onsuccess: #1771: 1: Success after binutils/gcc/linux [...] new 9638a67fc6b3 171: onsuccess: #1772: 1: Success after binutils/gcc/gdb: [...] new 45c2ad4217cd 172: onsuccess: #1773: 1: Success after binutils/gcc/glibc [...] new 15ba1f669859 173: onsuccess: #1774: 1: Success after binutils/gcc/glibc [...] new 84b1854e7ee6 174: onsuccess: #1775: 1: Success after binutils/gcc/linux [...] new 9e01891abe7a 175: onsuccess: #1776: 1: Success after binutils/gcc/linux [...] new 363ea4d66644 176: onsuccess: #1791: 1: Success after binutils/gcc/linux [...] new 5745b6e8a721 177: onsuccess: #1793: 1: Success after binutils/gcc/linux [...] new d249e39ff799 178: onsuccess: #1799: 1: Success after binutils/gcc/linux [...] new 8ec1bc5596ad 179: onsuccess: #1810: 1: Success after binutils/gcc/linux [...] new 057bf08a4311 180: onsuccess: #1831: 1: Success after binutils/gcc/linux [...] new cc6eb15f0226 181: onsuccess: #1857: 1: Success after binutils/gcc/linux [...] new 766ca8f66ff7 182: onsuccess: #1860: 1: Success after binutils/gcc/linux [...] new fea85f8cfdac 183: onsuccess: #1897: 1: Success after binutils/gcc/linux [...] new 45d13beeb574 184: onsuccess: #1898: 1: Success after binutils/gcc/gdb: [...] new a2c5ac1f9f77 185: onsuccess: #1906: 1: Success after binutils/gcc/linux [...] new bc9fac029f0b 186: onsuccess: #1907: 1: Success after binutils/gcc/gdb: [...] new c4369707dc63 187: onsuccess: #1908: 1: Success after binutils/gcc/linux [...] new fc3b6243da53 188: onsuccess: #1909: 1: Success after binutils/gcc/gdb: [...] new 114dfbda43c9 189: onsuccess: #1912: 1: Success after binutils/gcc/linux [...] new 83fd09f069a8 190: onsuccess: #1913: 1: Success after binutils/gcc/linux [...] new 48cbb8842dd7 191: onsuccess: #1949: 1: Success after binutils/gcc/linux [...] new 731ef4e2284e 192: onsuccess: #1951: 1: Success after binutils/gcc/gdb: [...] new f5221e432093 193: onsuccess: #1992: 1: Success after binutils: 151 commits new a7c6cf96021e 194: onsuccess: #1995: 1: Success after linux: 517 commits new 381aadc47c5a 195: onsuccess: #1996: 1: Success after binutils/gcc/glibc [...] new 257ec693968b 196: onsuccess: #1997: 1: Success after binutils/gcc/gdb: [...] new bce5ea0e7ead 197: onsuccess: #1998: 1: Success after binutils/gcc/gdb: [...] new eb538d287ff9 198: onsuccess: #1999: 1: Success after binutils/gcc/linux [...] new b6085b42ff78 199: onsuccess: #2000: 1: Success after gcc: 5 commits new 95548b4c596e 200: onsuccess: #2001: 1: Success after binutils/gcc/gdb: [...] new a09407afbf06 201: onsuccess: #2002: 1: Success after gcc/glibc: 5 commits new 9ee1ed6dc370 202: onsuccess: #2003: 1: Success after binutils/gcc/linux [...] new 712d514ba515 203: onsuccess: #2004: 1: Success after binutils/gcc/gdb: [...] new a714d63d63be 204: onsuccess: #2005: 1: Success after binutils/gcc/linux [...] new 00c2ea882a31 205: onsuccess: #2006: 1: Success after gcc: 3 commits new e1aaeeb0cecb 206: onsuccess: #2007: 1: Success after gcc: 2 commits new bb15c7b57efc 207: onsuccess: #2010: 1: Success after gcc: 4 commits new bccf42f0c39e 208: onsuccess: #2012: 1: Success after linux: 12 commits new 6a90ede485ec 209: onsuccess: #2014: 1: Success after binutils: 12 commits new 87bba8466956 210: onsuccess: #2017: 1: Success after binutils: 6 commits new 1d5b531ae5b6 211: onsuccess: #2020: 1: Success after binutils: 10 commits new aebe27256072 212: onsuccess: #2022: 1: Success after linux: 3 commits new b126c50e70b6 213: onsuccess: #2024: 1: Success after binutils: 3 commits new 5459a88c85f7 214: onsuccess: #2026: 1: Success after binutils/gcc/gdb/q [...] new 1cfb7b7a82ad 215: onsuccess: #2027: 1: Success after binutils/gcc/glibc [...] new 92b4598564f4 216: onsuccess: #2028: 1: Success after binutils/gcc/linux [...] new b0c203944ed6 217: onsuccess: #2029: 1: Success after binutils/gcc/glibc [...] new 29c433efefc1 218: onsuccess: #2030: 1: Success after gcc: 5 commits new 7628ded43039 219: onsuccess: #2031: 1: Success after binutils/gcc/glibc [...] new 681cab2a1be3 220: onsuccess: #2032: 1: Success after binutils/gcc/linux [...] new 1b9d1fcb52e3 221: onsuccess: #2033: 1: Success after binutils/gdb: 2 commits new 43d375796d38 222: onsuccess: #2035: 1: Success after binutils/gcc/glibc [...] new 981e052a4521 223: onsuccess: #2036: 1: Success after binutils/gcc/linux [...] new 36dccb40504a 224: onsuccess: #2038: 1: Success after binutils/gcc/linux [...] new eef9ea3336d6 225: onsuccess: #2039: 1: Success after binutils/linux/gli [...] new 5d82540f4d78 226: onsuccess: #2040: 1: Success after binutils/gcc/gdb: [...] new 1f61d79c4336 227: onsuccess: #2041: 1: Success after binutils/gcc/linux [...] new 76fb649e7c1b 228: onsuccess: #2042: 1: Success after basepoints/gcc-13- [...] new 0d326c7aef12 229: onsuccess: #2043: 1: Success after binutils/gcc/linux [...] new 5a7e5ef8ef6a 230: onsuccess: #2044: 1: Success after binutils/gcc/linux [...] new a06f5dac7846 231: onsuccess: #2047: 1: Success after gcc: 4 commits new 8fbe29e6dbe6 232: onsuccess: #2048: 1: Success after glibc: 2 commits new 0c7d3f26b971 233: onsuccess: #2049: 1: Success after binutils/gcc/linux [...] new 71d6fcc00807 234: onsuccess: #2050: 1: Success after binutils/gcc/linux [...] new 8e5c63bae867 235: onsuccess: #2051: 1: Success after binutils/linux/gdb [...] new fd164db13a9e 236: onsuccess: #2052: 1: Success after binutils/gcc/gdb: [...] new 645960fcbb6f 237: onsuccess: #2053: 1: Success after binutils/gcc/linux [...] new f20d3fc8da3f 238: onsuccess: #2054: 1: Success after binutils/gcc/linux [...] new 65d9cf18b207 239: onsuccess: #2055: 1: Success after binutils/gcc/linux [...] new 8fd6af54a574 240: onsuccess: #2056: 1: Success after binutils/gcc/gdb: [...] new a7bfe53ef607 241: onsuccess: #2057: 1: Success after binutils/gcc/linux [...] new 4394524f6093 242: onsuccess: #2058: 1: Success after binutils/gcc/linux [...] new 21188444dc3c 243: onsuccess: #2059: 1: Success after basepoints/gcc-13- [...] new a5125b35f250 244: onsuccess: #2060: 1: Success after binutils/gcc/gdb/q [...] new c4699f5db380 245: onsuccess: #2061: 1: Success after binutils/gcc/linux [...] new c8476ffac6a9 246: onsuccess: #2062: 1: Success after binutils/gcc/linux [...] new ab4f89dde179 247: onsuccess: #2063: 1: Success after binutils/gcc/linux [...] new 45e652d1cd52 248: onsuccess: #2064: 1: Success after binutils/gcc/gdb/q [...] new 29812a6dfbf1 249: onsuccess: #2065: 1: Success after binutils/gcc/linux [...] new 8d59c7276852 250: onsuccess: #2066: 1: Success after binutils/gcc/linux [...] new e3b246da3f59 251: onsuccess: #2067: 1: Success after binutils/gcc/gdb: [...] new 1993ca6ee870 252: onsuccess: #2068: 1: Success after binutils/gdb: 6 commits new 7fe87a155359 253: onsuccess: #2069: 1: Success after gcc/linux: 109 commits new b1c0453f90e3 254: onsuccess: #2070: 1: Success after binutils/gcc/gdb/q [...] new 19aec5b83b2c 255: onsuccess: #2071: 1: Success after binutils/gcc/gdb: [...] new 9697ee6d1b37 256: onsuccess: #2072: 1: Success after binutils/gcc/gdb: [...] new d5a169cf675a 257: onsuccess: #2073: 1: Success after v7.2.0-211-g562d4a [...] new b2710840654a 258: onsuccess: #2074: 1: Success after binutils/gcc/glibc [...] new b066a6c6107e 259: onsuccess: #2075: 1: Success after glibc: 2 commits new 987f091a7de2 260: onsuccess: #2076: 1: Success after binutils/gcc/glibc [...] new 42fb8c9d9f56 261: onsuccess: #2077: 1: Success after binutils/gcc/linux [...] new 3041ac44c25e 262: onsuccess: #2078: 1: Success after binutils/gcc/linux [...] new ef9f46305bfe 263: onsuccess: #2079: 1: Success after binutils/gcc/gdb: [...] new bce1995d5d99 264: onsuccess: #2080: 1: Success after binutils/gcc/gdb: [...] new b6861b9abc96 265: onsuccess: #2081: 1: Success after gcc/linux/glibc/qe [...] new 5eae4103a06b 266: onsuccess: #2082: 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 (4c0bf76a4841) \ 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 -> 1772 bytes 02-prepare_abe/console.log.xz | Bin 2776 -> 2796 bytes 03-build_abe-binutils/console.log.xz | Bin 31920 -> 32152 bytes 04-build_abe-stage1/console.log.xz | Bin 92180 -> 92208 bytes 05-clean_sysroot/console.log.xz | Bin 332 -> 332 bytes 06-build_abe-linux/console.log.xz | Bin 8536 -> 8580 bytes 07-build_abe-glibc/console.log.xz | Bin 235820 -> 236940 bytes 08-build_abe-stage2/console.log.xz | Bin 225444 -> 225984 bytes 09-build_abe-gdb/console.log.xz | Bin 39248 -> 40048 bytes 10-build_abe-qemu/console.log.xz | Bin 30812 -> 31092 bytes 11-build_abe-dejagnu/console.log.xz | Bin 3868 -> 3900 bytes 12-build_abe-check_gcc/console.log.xz | Bin 3352 -> 2532 bytes 13-check_regression/console.log.xz | Bin 6300 -> 5988 bytes 13-check_regression/mail-body.txt | 26 - 13-check_regression/results.compare | 20 +- 13-check_regression/results.compare2 | 73 +- 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 | 28 +- mail/mail-subject.txt | 2 +- manifest.sh | 34 +- sumfiles/g++.log.xz | Bin 2689020 -> 2651156 bytes sumfiles/g++.sum | 136 +- sumfiles/gcc.log.xz | Bin 2232244 -> 2253172 bytes sumfiles/gcc.sum | 2562 ++++++++++++++++----------------- sumfiles/gfortran.log.xz | Bin 890528 -> 914704 bytes sumfiles/gfortran.sum | 44 +- sumfiles/libatomic.log.xz | Bin 2264 -> 2260 bytes sumfiles/libatomic.sum | 4 +- sumfiles/libgomp.log.xz | Bin 214068 -> 213896 bytes sumfiles/libgomp.sum | 16 +- sumfiles/libitm.log.xz | Bin 2668 -> 2668 bytes sumfiles/libitm.sum | 6 +- sumfiles/libstdc++.log.xz | Bin 432180 -> 428848 bytes sumfiles/libstdc++.sum | 10 +- 39 files changed, 1508 insertions(+), 1529 deletions(-)