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 cd61d2cf6c 282: onsuccess: #2098: 1: Success after binutils/gcc/linux/g [...] discards 6fbc40c530 281: onsuccess: #2097: 1: Success after binutils/gcc/gdb: 23 [...] discards 456fc5d116 280: onsuccess: #2096: 1: Success after binutils/gcc/gdb: 21 [...] discards 45084967fb 279: onsuccess: #2095: 1: Success after binutils/gcc/gdb: 5 commits discards a8b5f22414 278: onsuccess: #2094: 1: Success after binutils/gcc/linux/g [...] discards a838b9eb2d 277: onsuccess: #2093: 1: Success after binutils/gcc/linux/g [...] discards 7b89370f82 276: onsuccess: #2092: 1: Success after binutils/gcc/gdb: 69 [...] discards 12280155c4 275: onsuccess: #2091: 1: Success after binutils/gcc/gdb: 42 [...] discards 28ff786a13 274: onsuccess: #2090: 1: Success after binutils/gcc/linux/g [...] discards 7af390addf 273: onsuccess: #2089: 1: Success after binutils/gcc/glibc/g [...] discards 16c83bd11e 272: onsuccess: #2088: 1: Success after binutils/gcc/gdb: 28 [...] discards 5aea800195 271: onsuccess: #2087: 1: Success after binutils/gcc/linux/g [...] discards 427b7492f8 270: onsuccess: #2086: 1: Success after binutils/gcc/glibc/g [...] discards 251a5e0a1f 269: onsuccess: #2085: 1: Success after binutils/gcc/linux/g [...] discards c0b98523fe 268: onsuccess: #2084: 1: Success after binutils/gcc/gdb/qem [...] discards 58492201b0 267: onsuccess: #2083: 1: Success after binutils/gcc/gdb: 64 [...] discards fec539ced7 266: onsuccess: #2082: 1: Success after binutils/gcc/gdb: 8 commits discards 22f3e08bc4 265: onsuccess: #2081: 1: Success after gcc/linux/glibc/qemu [...] discards 84c0392c50 264: onsuccess: #2080: 1: Success after binutils/gcc/gdb: 7 commits discards 56c4da3010 263: onsuccess: #2079: 1: Success after binutils/gcc/gdb: 7 commits discards 64ad8f9c75 262: onsuccess: #2078: 1: Success after binutils/gcc/linux/g [...] discards 813ef5578e 261: onsuccess: #2077: 1: Success after binutils/gcc/linux/g [...] discards 9326a00238 260: onsuccess: #2076: 1: Success after binutils/gcc/glibc/g [...] discards 8cfaea8e53 259: onsuccess: #2075: 1: Success after glibc: 2 commits discards 5a8afef904 258: onsuccess: #2074: 1: Success after binutils/gcc/glibc/g [...] discards 3476fd3113 257: onsuccess: #2073: 1: Success after v7.2.0-211-g562d4af3 [...] discards 5da63dc591 256: onsuccess: #2072: 1: Success after binutils/gcc/gdb: 5 commits discards 2860960185 255: onsuccess: #2071: 1: Success after binutils/gcc/gdb: 5 commits discards b86e8bb2c5 254: onsuccess: #2070: 1: Success after binutils/gcc/gdb/qem [...] discards 7e601348b7 253: onsuccess: #2069: 1: Success after gcc/linux: 109 commits discards 563c4ecc33 252: onsuccess: #2068: 1: Success after binutils/gdb: 6 commits discards c81117f594 251: onsuccess: #2067: 1: Success after binutils/gcc/gdb: 13 [...] discards 529e616cd3 250: onsuccess: #2066: 1: Success after binutils/gcc/linux/g [...] discards fbecca46a3 249: onsuccess: #2065: 1: Success after binutils/gcc/linux/g [...] discards 400aded449 248: onsuccess: #2064: 1: Success after binutils/gcc/gdb/qem [...] discards 5d6a6bbf87 247: onsuccess: #2063: 1: Success after binutils/gcc/linux/g [...] discards 143b88e4b2 246: onsuccess: #2062: 1: Success after binutils/gcc/linux/g [...] discards df7fcaf847 245: onsuccess: #2061: 1: Success after binutils/gcc/linux/g [...] discards 3079880aba 244: onsuccess: #2060: 1: Success after binutils/gcc/gdb/qem [...] discards 729d204abe 243: onsuccess: #2059: 1: Success after basepoints/gcc-13-47 [...] discards df58e7641a 242: onsuccess: #2058: 1: Success after binutils/gcc/linux/g [...] discards b170e2ac10 241: onsuccess: #2057: 1: Success after binutils/gcc/linux/g [...] discards 489a7b5ae5 240: onsuccess: #2056: 1: Success after binutils/gcc/gdb: 22 [...] discards dfb5137073 239: onsuccess: #2055: 1: Success after binutils/gcc/linux/g [...] discards 7ddb60f546 238: onsuccess: #2054: 1: Success after binutils/gcc/linux/g [...] discards b53d1663c1 237: onsuccess: #2053: 1: Success after binutils/gcc/linux/g [...] discards 55b163073e 236: onsuccess: #2052: 1: Success after binutils/gcc/gdb: 10 [...] discards 006cd66831 235: onsuccess: #2051: 1: Success after binutils/linux/gdb: [...] discards ad74b599c1 234: onsuccess: #2050: 1: Success after binutils/gcc/linux/g [...] discards 6431a400a1 233: onsuccess: #2049: 1: Success after binutils/gcc/linux/g [...] discards da1b4d46f0 232: onsuccess: #2048: 1: Success after glibc: 2 commits discards 9da924cfde 231: onsuccess: #2047: 1: Success after gcc: 4 commits discards 5a9ece2e50 230: onsuccess: #2044: 1: Success after binutils/gcc/linux/g [...] discards 15ebba5cac 229: onsuccess: #2043: 1: Success after binutils/gcc/linux/g [...] discards 76cc801b8d 228: onsuccess: #2042: 1: Success after basepoints/gcc-13-45 [...] discards cc1f104a7e 227: onsuccess: #2041: 1: Success after binutils/gcc/linux/g [...] discards 9fe4f8f9df 226: onsuccess: #2040: 1: Success after binutils/gcc/gdb: 15 [...] discards 5ba89582f5 225: onsuccess: #2039: 1: Success after binutils/linux/glibc [...] discards 812e243efc 224: onsuccess: #2038: 1: Success after binutils/gcc/linux/g [...] discards 1d5dcdffa0 223: onsuccess: #2036: 1: Success after binutils/gcc/linux/g [...] discards e8d4cdf32a 222: onsuccess: #2035: 1: Success after binutils/gcc/glibc/g [...] discards 349140c489 221: onsuccess: #2033: 1: Success after binutils/gdb: 2 commits discards e3b0a7b736 220: onsuccess: #2032: 1: Success after binutils/gcc/linux/g [...] discards fab81681f6 219: onsuccess: #2031: 1: Success after binutils/gcc/glibc/g [...] discards b55014cc37 218: onsuccess: #2030: 1: Success after gcc: 5 commits discards 360196e12b 217: onsuccess: #2029: 1: Success after binutils/gcc/glibc/g [...] discards 9560bf4b16 216: onsuccess: #2028: 1: Success after binutils/gcc/linux/g [...] discards 1486fb91af 215: onsuccess: #2027: 1: Success after binutils/gcc/glibc/g [...] discards ff1a9fefc2 214: onsuccess: #2026: 1: Success after binutils/gcc/gdb/qem [...] discards 10a3be4b78 213: onsuccess: #2024: 1: Success after binutils: 3 commits discards ae431a8062 212: onsuccess: #2022: 1: Success after linux: 3 commits discards 7bf5585c58 211: onsuccess: #2020: 1: Success after binutils: 10 commits discards 2cc48c998f 210: onsuccess: #2017: 1: Success after binutils: 6 commits discards 47c76c5dda 209: onsuccess: #2014: 1: Success after binutils: 12 commits discards 5beab9f283 208: onsuccess: #2012: 1: Success after linux: 12 commits discards 34041478a3 207: onsuccess: #2010: 1: Success after gcc: 4 commits discards 30ea29fed8 206: onsuccess: #2007: 1: Success after gcc: 2 commits discards bc125e73bf 205: onsuccess: #2006: 1: Success after gcc: 3 commits discards 9cd130a06c 204: onsuccess: #2005: 1: Success after binutils/gcc/linux/g [...] discards 87f7c553c8 203: onsuccess: #2004: 1: Success after binutils/gcc/gdb: 7 commits discards 72f668f9c9 202: onsuccess: #2003: 1: Success after binutils/gcc/linux/g [...] discards 96ca744ba6 201: onsuccess: #2002: 1: Success after gcc/glibc: 5 commits discards facdbb725a 200: onsuccess: #2001: 1: Success after binutils/gcc/gdb: 18 [...] discards 4c9c807d68 199: onsuccess: #2000: 1: Success after gcc: 5 commits discards e2cd45ddbd 198: onsuccess: #1999: 1: Success after binutils/gcc/linux/g [...] discards 5217abfcfd 197: onsuccess: #1998: 1: Success after binutils/gcc/gdb: 42 [...] discards 4aa89ad966 196: onsuccess: #1997: 1: Success after binutils/gcc/gdb: 11 [...] discards b003fe191c 195: onsuccess: #1996: 1: Success after binutils/gcc/glibc/g [...] discards e94ddbd43c 194: onsuccess: #1995: 1: Success after linux: 517 commits discards f44716bdfe 193: onsuccess: #1992: 1: Success after binutils: 151 commits discards 07dee69e9d 192: onsuccess: #1951: 1: Success after binutils/gcc/gdb: 8 commits discards 8e641e7d47 191: onsuccess: #1949: 1: Success after binutils/gcc/linux/g [...] discards 60d974d0cb 190: onsuccess: #1913: 1: Success after binutils/gcc/linux/g [...] discards 1091b07300 189: onsuccess: #1912: 1: Success after binutils/gcc/linux/g [...] discards 466737242b 188: onsuccess: #1909: 1: Success after binutils/gcc/gdb: 5 commits discards a3716f73f9 187: onsuccess: #1908: 1: Success after binutils/gcc/linux/g [...] discards 46dcad17f3 186: onsuccess: #1907: 1: Success after binutils/gcc/gdb: 22 [...] discards 65ded5b39a 185: onsuccess: #1906: 1: Success after binutils/gcc/linux/g [...] discards a2140ee938 184: onsuccess: #1898: 1: Success after binutils/gcc/gdb: 13 [...] discards d298003e89 183: onsuccess: #1897: 1: Success after binutils/gcc/linux/g [...] discards 7861141667 182: onsuccess: #1860: 1: Success after binutils/gcc/linux/g [...] new bdbfb7900c 182: onsuccess: #1860: 1: Success after binutils/gcc/linux/g [...] new 2a0a63b828 183: onsuccess: #1897: 1: Success after binutils/gcc/linux/g [...] new 894c740f72 184: onsuccess: #1898: 1: Success after binutils/gcc/gdb: 13 [...] new 856f2ce46a 185: onsuccess: #1906: 1: Success after binutils/gcc/linux/g [...] new 275bc34d18 186: onsuccess: #1907: 1: Success after binutils/gcc/gdb: 22 [...] new 7fc8e9ba5d 187: onsuccess: #1908: 1: Success after binutils/gcc/linux/g [...] new 8e7eb7746a 188: onsuccess: #1909: 1: Success after binutils/gcc/gdb: 5 commits new d538d57fcb 189: onsuccess: #1912: 1: Success after binutils/gcc/linux/g [...] new ecfe764190 190: onsuccess: #1913: 1: Success after binutils/gcc/linux/g [...] new b354ee3667 191: onsuccess: #1949: 1: Success after binutils/gcc/linux/g [...] new 9eb6dc529e 192: onsuccess: #1951: 1: Success after binutils/gcc/gdb: 8 commits new 9bff6b6e89 193: onsuccess: #1992: 1: Success after binutils: 151 commits new 4c6cc836e3 194: onsuccess: #1995: 1: Success after linux: 517 commits new f911e85d4c 195: onsuccess: #1996: 1: Success after binutils/gcc/glibc/g [...] new d3f75cbbb0 196: onsuccess: #1997: 1: Success after binutils/gcc/gdb: 11 [...] new 0d3c7d8bd3 197: onsuccess: #1998: 1: Success after binutils/gcc/gdb: 42 [...] new 2e5cd970d9 198: onsuccess: #1999: 1: Success after binutils/gcc/linux/g [...] new 759a8c3b05 199: onsuccess: #2000: 1: Success after gcc: 5 commits new 7d542fb453 200: onsuccess: #2001: 1: Success after binutils/gcc/gdb: 18 [...] new 4efbbd5876 201: onsuccess: #2002: 1: Success after gcc/glibc: 5 commits new 7605c312b4 202: onsuccess: #2003: 1: Success after binutils/gcc/linux/g [...] new cd9e561d1d 203: onsuccess: #2004: 1: Success after binutils/gcc/gdb: 7 commits new 613fa804d9 204: onsuccess: #2005: 1: Success after binutils/gcc/linux/g [...] new 281935ae4a 205: onsuccess: #2006: 1: Success after gcc: 3 commits new afaeb5ba85 206: onsuccess: #2007: 1: Success after gcc: 2 commits new bf8c930ac0 207: onsuccess: #2010: 1: Success after gcc: 4 commits new 1413cda999 208: onsuccess: #2012: 1: Success after linux: 12 commits new 966e664259 209: onsuccess: #2014: 1: Success after binutils: 12 commits new fce9a416b2 210: onsuccess: #2017: 1: Success after binutils: 6 commits new 40e5462978 211: onsuccess: #2020: 1: Success after binutils: 10 commits new deb905273e 212: onsuccess: #2022: 1: Success after linux: 3 commits new 88d968deed 213: onsuccess: #2024: 1: Success after binutils: 3 commits new f305398cc6 214: onsuccess: #2026: 1: Success after binutils/gcc/gdb/qem [...] new 98a4b53b04 215: onsuccess: #2027: 1: Success after binutils/gcc/glibc/g [...] new 3a9269cf57 216: onsuccess: #2028: 1: Success after binutils/gcc/linux/g [...] new d233299d86 217: onsuccess: #2029: 1: Success after binutils/gcc/glibc/g [...] new 8264936576 218: onsuccess: #2030: 1: Success after gcc: 5 commits new 895bc9bb95 219: onsuccess: #2031: 1: Success after binutils/gcc/glibc/g [...] new 266edc3741 220: onsuccess: #2032: 1: Success after binutils/gcc/linux/g [...] new 6d6f73a61a 221: onsuccess: #2033: 1: Success after binutils/gdb: 2 commits new 093a59e86d 222: onsuccess: #2035: 1: Success after binutils/gcc/glibc/g [...] new 3645ebcebf 223: onsuccess: #2036: 1: Success after binutils/gcc/linux/g [...] new 934b312ab3 224: onsuccess: #2038: 1: Success after binutils/gcc/linux/g [...] new 82a1eff8dc 225: onsuccess: #2039: 1: Success after binutils/linux/glibc [...] new e80d6c342e 226: onsuccess: #2040: 1: Success after binutils/gcc/gdb: 15 [...] new 25e5dfe251 227: onsuccess: #2041: 1: Success after binutils/gcc/linux/g [...] new 1b54401175 228: onsuccess: #2042: 1: Success after basepoints/gcc-13-45 [...] new a7f4cd342c 229: onsuccess: #2043: 1: Success after binutils/gcc/linux/g [...] new cde5b2eb62 230: onsuccess: #2044: 1: Success after binutils/gcc/linux/g [...] new 3d402be068 231: onsuccess: #2047: 1: Success after gcc: 4 commits new 7a9fb447de 232: onsuccess: #2048: 1: Success after glibc: 2 commits new c69c620a86 233: onsuccess: #2049: 1: Success after binutils/gcc/linux/g [...] new 31610e33ae 234: onsuccess: #2050: 1: Success after binutils/gcc/linux/g [...] new 1af22f6258 235: onsuccess: #2051: 1: Success after binutils/linux/gdb: [...] new 5ace509c76 236: onsuccess: #2052: 1: Success after binutils/gcc/gdb: 10 [...] new 4a92ee4df4 237: onsuccess: #2053: 1: Success after binutils/gcc/linux/g [...] new 5d9183f64f 238: onsuccess: #2054: 1: Success after binutils/gcc/linux/g [...] new d94531648b 239: onsuccess: #2055: 1: Success after binutils/gcc/linux/g [...] new ceda12a531 240: onsuccess: #2056: 1: Success after binutils/gcc/gdb: 22 [...] new 3ce6129bd3 241: onsuccess: #2057: 1: Success after binutils/gcc/linux/g [...] new 0a3d839eb4 242: onsuccess: #2058: 1: Success after binutils/gcc/linux/g [...] new 074d84578e 243: onsuccess: #2059: 1: Success after basepoints/gcc-13-47 [...] new 38673073d6 244: onsuccess: #2060: 1: Success after binutils/gcc/gdb/qem [...] new e02c1fcf1f 245: onsuccess: #2061: 1: Success after binutils/gcc/linux/g [...] new ea1fb208e0 246: onsuccess: #2062: 1: Success after binutils/gcc/linux/g [...] new 14b343806c 247: onsuccess: #2063: 1: Success after binutils/gcc/linux/g [...] new 264a2dc7f1 248: onsuccess: #2064: 1: Success after binutils/gcc/gdb/qem [...] new 96e2fdaf94 249: onsuccess: #2065: 1: Success after binutils/gcc/linux/g [...] new 51060b5545 250: onsuccess: #2066: 1: Success after binutils/gcc/linux/g [...] new d007b8f42c 251: onsuccess: #2067: 1: Success after binutils/gcc/gdb: 13 [...] new 3e42c5b138 252: onsuccess: #2068: 1: Success after binutils/gdb: 6 commits new 9e97b7da93 253: onsuccess: #2069: 1: Success after gcc/linux: 109 commits new 2e10e75358 254: onsuccess: #2070: 1: Success after binutils/gcc/gdb/qem [...] new 46831be7a4 255: onsuccess: #2071: 1: Success after binutils/gcc/gdb: 5 commits new a566afaf17 256: onsuccess: #2072: 1: Success after binutils/gcc/gdb: 5 commits new 144b8339f7 257: onsuccess: #2073: 1: Success after v7.2.0-211-g562d4af3 [...] new a968d64489 258: onsuccess: #2074: 1: Success after binutils/gcc/glibc/g [...] new b136ae038b 259: onsuccess: #2075: 1: Success after glibc: 2 commits new f072a91ca2 260: onsuccess: #2076: 1: Success after binutils/gcc/glibc/g [...] new 4fcaa36007 261: onsuccess: #2077: 1: Success after binutils/gcc/linux/g [...] new 36114d6146 262: onsuccess: #2078: 1: Success after binutils/gcc/linux/g [...] new eba9dea928 263: onsuccess: #2079: 1: Success after binutils/gcc/gdb: 7 commits new 98f60bfc37 264: onsuccess: #2080: 1: Success after binutils/gcc/gdb: 7 commits new fa07fddada 265: onsuccess: #2081: 1: Success after gcc/linux/glibc/qemu [...] new a201cb4792 266: onsuccess: #2082: 1: Success after binutils/gcc/gdb: 8 commits new b6a6b0ec04 267: onsuccess: #2083: 1: Success after binutils/gcc/gdb: 64 [...] new fad873106a 268: onsuccess: #2084: 1: Success after binutils/gcc/gdb/qem [...] new 2d82445700 269: onsuccess: #2085: 1: Success after binutils/gcc/linux/g [...] new 9a4d9c400c 270: onsuccess: #2086: 1: Success after binutils/gcc/glibc/g [...] new f0639057af 271: onsuccess: #2087: 1: Success after binutils/gcc/linux/g [...] new a05f8863a6 272: onsuccess: #2088: 1: Success after binutils/gcc/gdb: 28 [...] new 65a0bb5ff7 273: onsuccess: #2089: 1: Success after binutils/gcc/glibc/g [...] new bf17506bd6 274: onsuccess: #2090: 1: Success after binutils/gcc/linux/g [...] new b9587c45cb 275: onsuccess: #2091: 1: Success after binutils/gcc/gdb: 42 [...] new bcd9d973c5 276: onsuccess: #2092: 1: Success after binutils/gcc/gdb: 69 [...] new 20a8d15349 277: onsuccess: #2093: 1: Success after binutils/gcc/linux/g [...] new 88d50cac5e 278: onsuccess: #2094: 1: Success after binutils/gcc/linux/g [...] new 85f9f9540f 279: onsuccess: #2095: 1: Success after binutils/gcc/gdb: 5 commits new 6a02f5be01 280: onsuccess: #2096: 1: Success after binutils/gcc/gdb: 21 [...] new fa2c343581 281: onsuccess: #2097: 1: Success after binutils/gcc/gdb: 23 [...] new fbe323866f 282: onsuccess: #2098: 1: Success after binutils/gcc/linux/g [...] new 565c1665b5 283: onsuccess: #2099: 1: Success after binutils/gdb: 4 commits

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 (cd61d2cf6c) \ 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 1740 -> 1740 bytes 02-prepare_abe/console.log.xz | Bin 2788 -> 2776 bytes 03-build_abe-binutils/console.log.xz | Bin 32076 -> 32008 bytes 04-build_abe-stage1/console.log.xz | Bin 92280 -> 92376 bytes 06-build_abe-linux/console.log.xz | Bin 8580 -> 8368 bytes 07-build_abe-glibc/console.log.xz | Bin 238600 -> 237128 bytes 08-build_abe-stage2/console.log.xz | Bin 229288 -> 228488 bytes 09-build_abe-gdb/console.log.xz | Bin 39408 -> 39440 bytes 10-build_abe-qemu/console.log.xz | Bin 31572 -> 31732 bytes 11-build_abe-dejagnu/console.log.xz | Bin 3892 -> 3860 bytes 12-build_abe-check_gcc/console.log.xz | Bin 2828 -> 2764 bytes 13-check_regression/console.log.xz | Bin 6224 -> 5360 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 | 26 +- 13-check_regression/results.compare2 | 36 +- 13-check_regression/results.regressions | 26 - 14-update_baseline/console.log | 66 +- dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gdb_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 44 +- mail/mail-subject.txt | 2 +- manifest.sh | 28 +- results | 26 - sumfiles/g++.log.xz | Bin 2664240 -> 2661404 bytes sumfiles/g++.sum | 22 +- sumfiles/gcc.log.xz | Bin 2271372 -> 2243132 bytes sumfiles/gcc.sum | 2592 +++++++++++++++---------------- sumfiles/gfortran.log.xz | Bin 894780 -> 893956 bytes sumfiles/gfortran.sum | 8 +- sumfiles/libatomic.log.xz | Bin 2264 -> 2260 bytes sumfiles/libatomic.sum | 2 +- sumfiles/libgomp.log.xz | Bin 213956 -> 214012 bytes sumfiles/libgomp.sum | 2 +- sumfiles/libitm.log.xz | Bin 2668 -> 2664 bytes sumfiles/libitm.sum | 2 +- sumfiles/libstdc++.log.xz | Bin 435308 -> 439764 bytes sumfiles/libstdc++.sum | 10 +- 41 files changed, 1446 insertions(+), 1503 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