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 ab95e55f42 345: onsuccess: #2165: 1: Success after binutils/gcc/glibc/g [...] discards 2d980d0e49 344: onsuccess: #2164: 1: Success after gcc/linux/glibc: 37 commits discards 3b7552770e 343: onsuccess: #2163: 1: Success after binutils/gcc/gdb: 7 commits discards 26deb62f5c 342: onsuccess: #2162: 1: Success after binutils/gcc/linux/g [...] discards f30dc6f794 341: onsuccess: #2161: 1: Success after binutils/gcc/gdb: 11 [...] discards 49705fafa0 340: onsuccess: #2160: 1: Success after binutils/gcc/gdb: 15 [...] discards ef11600bfc 339: onsuccess: #2159: 1: Success after binutils/gcc/gdb: 4 commits discards d767712c7b 338: onsuccess: #2158: 1: Success after binutils/gcc/linux/g [...] discards 40b8de3c4f 337: onsuccess: #2157: 1: Success after binutils/gcc/glibc/g [...] discards d1e180fa6e 336: onsuccess: #2156: 1: Success after binutils/gcc/linux/g [...] discards fd737d46b9 335: onsuccess: #2155: 1: Success after binutils/gdb: 146 commits discards 9edada8131 334: onsuccess: #2154: 1: Success after binutils/gcc/linux/g [...] discards 587febeba1 333: onsuccess: #2153: 1: Success after binutils/gcc/gdb/qem [...] discards 6ed9229005 332: onsuccess: #2152: 1: Success after binutils/gcc/gdb/qem [...] discards 1e0b3ab099 331: onsuccess: #2151: 1: Success after binutils/gcc/linux/g [...] discards a736a49048 330: onsuccess: #2150: 1: Success after linux/qemu: 36 commits discards 032e033940 329: onsuccess: #2149: 1: Success after binutils/gcc/gdb/qem [...] discards 9d7709e5c5 328: onsuccess: #2148: 1: Success after gcc/linux/qemu: 78 commits discards 83a94c809e 327: onsuccess: #2147: 1: Success after basepoints/gcc-13-50 [...] discards 9db15a8a7e 326: onsuccess: #2146: 1: Success after binutils/gcc/linux/g [...] discards b7d45cd91b 325: onsuccess: #2145: 1: Success after binutils/gcc/glibc/g [...] discards d5109f89a0 324: onsuccess: #2144: 1: Success after binutils/gcc/gdb/qem [...] discards 67a054e287 323: onsuccess: #2143: 1: Success after basepoints/gcc-13-50 [...] discards f8770a71d1 322: onsuccess: #2142: 1: Success after binutils/gcc/linux/g [...] discards bab9c44a03 321: onsuccess: #2141: 1: Success after binutils/gcc/linux/g [...] discards 1e03739f07 320: onsuccess: #2140: 1: Success after binutils/gcc/gdb: 6 commits discards 5a9186c9c1 319: onsuccess: #2139: 1: Success after binutils/gcc/gdb: 11 [...] discards 6ee8dc20f6 318: onsuccess: #2138: 1: Success after binutils/gcc/linux/g [...] discards 72e9db421f 317: onsuccess: #2137: 1: Success after binutils/gcc/linux/g [...] discards 1035d43f3f 316: onsuccess: #2136: 1: Success after binutils/gcc/gdb: 26 [...] discards 785d8c036d 315: onsuccess: #2135: 1: Success after binutils/gcc/gdb: 11 [...] discards c5021542fe 314: onsuccess: #2134: 1: Success after binutils/gcc/glibc/g [...] discards 13f52ffb91 313: onsuccess: #2133: 1: Success after binutils/gcc/linux/g [...] discards d613c405e7 312: onsuccess: #2132: 1: Success after glibc-2.36.9000-416- [...] discards 72ac057ba3 311: onsuccess: #2130: 1: Success after gcc: 4 commits discards 8231f8dc63 310: onsuccess: #2129: 1: Success after binutils: 4 commits discards 1207b2aae7 309: onsuccess: #2127: 1: Success after binutils/gcc/glibc/g [...] discards 82aa6c2990 308: onsuccess: #2126: 1: Success after binutils/gcc/linux/g [...] discards 41114194ae 307: onsuccess: #2124: 1: Success after gcc: 2 commits discards 3aaf967a0f 306: onsuccess: #2123: 1: Success after binutils/gcc/gdb: 15 [...] discards eb0c9bfd38 305: onsuccess: #2122: 1: Success after binutils/gcc/gdb: 4 commits discards 1427901711 304: onsuccess: #2121: 1: Success after gcc/linux: 13 commits discards 1e5f7b9f8f 303: onsuccess: #2120: 1: Success after binutils/gdb: 20 commits discards 9d5393bda7 302: onsuccess: #2119: 1: Success after binutils/gdb: 7 commits discards bea3c3be16 301: onsuccess: #2118: 1: Success after linux: 16 commits discards 48bdc754f5 300: onsuccess: #2117: 1: Success after basepoints/gcc-13-49 [...] discards baeeb3023b 299: onsuccess: #2116: 1: Success after gdb-13-branchpoint-2 [...] discards a613cc0e77 298: onsuccess: #2114: 1: Success after binutils/gcc/gdb: 6 commits discards 8c23d07a9a 297: onsuccess: #2113: 1: Success after binutils/gcc/gdb: 7 commits discards 3f5ffa9761 296: onsuccess: #2112: 1: Success after gcc/linux: 26 commits discards e3ed82b7e9 295: onsuccess: #2111: 1: Success after binutils/gcc/linux/g [...] discards bab087299d 294: onsuccess: #2110: 1: Success after gcc: 17 commits discards bf88f9e9fa 293: onsuccess: #2109: 1: Success after binutils/gdb: 2 commits discards ddcf752596 292: onsuccess: #2108: 1: Success after binutils/gcc/gdb: 3 commits discards 142f72b8a6 291: onsuccess: #2107: 1: Success after binutils/gcc/gdb: 6 commits discards dbc2a2e62e 290: onsuccess: #2106: 1: Success after gcc: 2 commits discards 164aec2343 289: onsuccess: #2105: 1: Success after binutils/gcc/gdb: 6 commits discards 4302423792 288: onsuccess: #2104: 1: Success after binutils/gcc/gdb: 10 [...] discards 1623689bee 287: onsuccess: #2103: 1: Success after gcc: 9 commits discards cc3fb68c7e 286: onsuccess: #2102: 1: Success after binutils/gdb: 18 commits discards 77a4f9d330 285: onsuccess: #2101: 1: Success after binutils/gcc/gdb: 5 commits discards 8d80e05ff9 284: onsuccess: #2100: 1: Success after basepoints/gcc-13-48 [...] discards c0a10dce34 283: onsuccess: #2099: 1: Success after binutils/gdb: 4 commits discards 0a0f54729a 282: onsuccess: #2098: 1: Success after binutils/gcc/linux/g [...] discards ef9179a330 281: onsuccess: #2097: 1: Success after binutils/gcc/gdb: 23 [...] discards 22c8c3387c 280: onsuccess: #2096: 1: Success after binutils/gcc/gdb: 21 [...] discards bb0f55ffe5 279: onsuccess: #2095: 1: Success after binutils/gcc/gdb: 5 commits discards 56b59467da 278: onsuccess: #2094: 1: Success after binutils/gcc/linux/g [...] discards c4f1551751 277: onsuccess: #2093: 1: Success after binutils/gcc/linux/g [...] discards bcbd6088b6 276: onsuccess: #2092: 1: Success after binutils/gcc/gdb: 69 [...] discards 2d018ad732 275: onsuccess: #2091: 1: Success after binutils/gcc/gdb: 42 [...] discards 1096996c2a 274: onsuccess: #2090: 1: Success after binutils/gcc/linux/g [...] discards 86d24b971e 273: onsuccess: #2089: 1: Success after binutils/gcc/glibc/g [...] discards 963b4cf54d 272: onsuccess: #2088: 1: Success after binutils/gcc/gdb: 28 [...] discards 25dece8ecf 271: onsuccess: #2087: 1: Success after binutils/gcc/linux/g [...] discards ca74113ba9 270: onsuccess: #2086: 1: Success after binutils/gcc/glibc/g [...] discards 9e29e9a38f 269: onsuccess: #2085: 1: Success after binutils/gcc/linux/g [...] discards f8fca80fca 268: onsuccess: #2084: 1: Success after binutils/gcc/gdb/qem [...] discards 081bb49e3b 267: onsuccess: #2083: 1: Success after binutils/gcc/gdb: 64 [...] discards d64641a1e9 266: onsuccess: #2082: 1: Success after binutils/gcc/gdb: 8 commits discards 8d93f6fed6 265: onsuccess: #2081: 1: Success after gcc/linux/glibc/qemu [...] discards c210749b50 264: onsuccess: #2080: 1: Success after binutils/gcc/gdb: 7 commits discards 10826bc70e 263: onsuccess: #2079: 1: Success after binutils/gcc/gdb: 7 commits discards 87ac41ca23 262: onsuccess: #2078: 1: Success after binutils/gcc/linux/g [...] discards a54a6c3906 261: onsuccess: #2077: 1: Success after binutils/gcc/linux/g [...] discards 900aa2fb18 260: onsuccess: #2076: 1: Success after binutils/gcc/glibc/g [...] discards 3c89f5b9c2 259: onsuccess: #2075: 1: Success after glibc: 2 commits discards b7fd6db9d1 258: onsuccess: #2074: 1: Success after binutils/gcc/glibc/g [...] discards 093370902f 257: onsuccess: #2073: 1: Success after v7.2.0-211-g562d4af3 [...] discards 644b425f35 256: onsuccess: #2072: 1: Success after binutils/gcc/gdb: 5 commits discards 07a5e2722c 255: onsuccess: #2071: 1: Success after binutils/gcc/gdb: 5 commits discards 72a93466b2 254: onsuccess: #2070: 1: Success after binutils/gcc/gdb/qem [...] discards 6328f481a0 253: onsuccess: #2069: 1: Success after gcc/linux: 109 commits discards 05b15245a7 252: onsuccess: #2068: 1: Success after binutils/gdb: 6 commits discards c738568e07 251: onsuccess: #2067: 1: Success after binutils/gcc/gdb: 13 [...] discards 6be5e35b60 250: onsuccess: #2066: 1: Success after binutils/gcc/linux/g [...] discards 2f7a17e382 249: onsuccess: #2065: 1: Success after binutils/gcc/linux/g [...] discards 788ffd7668 248: onsuccess: #2064: 1: Success after binutils/gcc/gdb/qem [...] discards 997acf8933 247: onsuccess: #2063: 1: Success after binutils/gcc/linux/g [...] discards 0c50ebd18f 246: onsuccess: #2062: 1: Success after binutils/gcc/linux/g [...] discards bfd6791009 245: onsuccess: #2061: 1: Success after binutils/gcc/linux/g [...] new 38043b5e3b 245: onsuccess: #2061: 1: Success after binutils/gcc/linux/g [...] new 98b39166e4 246: onsuccess: #2062: 1: Success after binutils/gcc/linux/g [...] new 1492e7d152 247: onsuccess: #2063: 1: Success after binutils/gcc/linux/g [...] new 488a687f3d 248: onsuccess: #2064: 1: Success after binutils/gcc/gdb/qem [...] new 5f91ecb485 249: onsuccess: #2065: 1: Success after binutils/gcc/linux/g [...] new 4290834da2 250: onsuccess: #2066: 1: Success after binutils/gcc/linux/g [...] new 4830deb053 251: onsuccess: #2067: 1: Success after binutils/gcc/gdb: 13 [...] new f9de18ef49 252: onsuccess: #2068: 1: Success after binutils/gdb: 6 commits new f1eb5228bc 253: onsuccess: #2069: 1: Success after gcc/linux: 109 commits new 8e8a34e892 254: onsuccess: #2070: 1: Success after binutils/gcc/gdb/qem [...] new ea3e4e2b74 255: onsuccess: #2071: 1: Success after binutils/gcc/gdb: 5 commits new ee6d6b5631 256: onsuccess: #2072: 1: Success after binutils/gcc/gdb: 5 commits new 0580834284 257: onsuccess: #2073: 1: Success after v7.2.0-211-g562d4af3 [...] new 047e2a5688 258: onsuccess: #2074: 1: Success after binutils/gcc/glibc/g [...] new fafd5e5d2b 259: onsuccess: #2075: 1: Success after glibc: 2 commits new 4da5e12cce 260: onsuccess: #2076: 1: Success after binutils/gcc/glibc/g [...] new dee711f99c 261: onsuccess: #2077: 1: Success after binutils/gcc/linux/g [...] new 6ffaadf6ba 262: onsuccess: #2078: 1: Success after binutils/gcc/linux/g [...] new 13b28028be 263: onsuccess: #2079: 1: Success after binutils/gcc/gdb: 7 commits new 564bcca12b 264: onsuccess: #2080: 1: Success after binutils/gcc/gdb: 7 commits new c5eb67ae41 265: onsuccess: #2081: 1: Success after gcc/linux/glibc/qemu [...] new de8e713499 266: onsuccess: #2082: 1: Success after binutils/gcc/gdb: 8 commits new 29cd1d40f4 267: onsuccess: #2083: 1: Success after binutils/gcc/gdb: 64 [...] new 7ece853457 268: onsuccess: #2084: 1: Success after binutils/gcc/gdb/qem [...] new 2624e0bba3 269: onsuccess: #2085: 1: Success after binutils/gcc/linux/g [...] new fdd556501c 270: onsuccess: #2086: 1: Success after binutils/gcc/glibc/g [...] new 7f34d695b7 271: onsuccess: #2087: 1: Success after binutils/gcc/linux/g [...] new a5f129140b 272: onsuccess: #2088: 1: Success after binutils/gcc/gdb: 28 [...] new b0741a61c1 273: onsuccess: #2089: 1: Success after binutils/gcc/glibc/g [...] new 09a5465ef8 274: onsuccess: #2090: 1: Success after binutils/gcc/linux/g [...] new 8582db2722 275: onsuccess: #2091: 1: Success after binutils/gcc/gdb: 42 [...] new 55aa4ba33a 276: onsuccess: #2092: 1: Success after binutils/gcc/gdb: 69 [...] new 275870e58b 277: onsuccess: #2093: 1: Success after binutils/gcc/linux/g [...] new 734d9b48d6 278: onsuccess: #2094: 1: Success after binutils/gcc/linux/g [...] new 9375cee6f6 279: onsuccess: #2095: 1: Success after binutils/gcc/gdb: 5 commits new e98eede53b 280: onsuccess: #2096: 1: Success after binutils/gcc/gdb: 21 [...] new 5af0f77026 281: onsuccess: #2097: 1: Success after binutils/gcc/gdb: 23 [...] new b39ff44eec 282: onsuccess: #2098: 1: Success after binutils/gcc/linux/g [...] new c4456fc6b9 283: onsuccess: #2099: 1: Success after binutils/gdb: 4 commits new bba97b521c 284: onsuccess: #2100: 1: Success after basepoints/gcc-13-48 [...] new 124a25e7ac 285: onsuccess: #2101: 1: Success after binutils/gcc/gdb: 5 commits new 813f64184b 286: onsuccess: #2102: 1: Success after binutils/gdb: 18 commits new 1588e22d75 287: onsuccess: #2103: 1: Success after gcc: 9 commits new 771fc3d7d4 288: onsuccess: #2104: 1: Success after binutils/gcc/gdb: 10 [...] new a26782c022 289: onsuccess: #2105: 1: Success after binutils/gcc/gdb: 6 commits new eedfefb0b8 290: onsuccess: #2106: 1: Success after gcc: 2 commits new b037deb5c5 291: onsuccess: #2107: 1: Success after binutils/gcc/gdb: 6 commits new c2e5ade83d 292: onsuccess: #2108: 1: Success after binutils/gcc/gdb: 3 commits new 33f70281d4 293: onsuccess: #2109: 1: Success after binutils/gdb: 2 commits new c5def12f7e 294: onsuccess: #2110: 1: Success after gcc: 17 commits new 8b2b14eab8 295: onsuccess: #2111: 1: Success after binutils/gcc/linux/g [...] new 7b96933d63 296: onsuccess: #2112: 1: Success after gcc/linux: 26 commits new 8bb3f20680 297: onsuccess: #2113: 1: Success after binutils/gcc/gdb: 7 commits new 937ef2d9e8 298: onsuccess: #2114: 1: Success after binutils/gcc/gdb: 6 commits new 1d930b5a5d 299: onsuccess: #2116: 1: Success after gdb-13-branchpoint-2 [...] new 2f417a39f5 300: onsuccess: #2117: 1: Success after basepoints/gcc-13-49 [...] new bb79069d0b 301: onsuccess: #2118: 1: Success after linux: 16 commits new 5f0e5fd2ad 302: onsuccess: #2119: 1: Success after binutils/gdb: 7 commits new b4537da7f4 303: onsuccess: #2120: 1: Success after binutils/gdb: 20 commits new a82bfec1d1 304: onsuccess: #2121: 1: Success after gcc/linux: 13 commits new 291f8bbe40 305: onsuccess: #2122: 1: Success after binutils/gcc/gdb: 4 commits new 369e42ccec 306: onsuccess: #2123: 1: Success after binutils/gcc/gdb: 15 [...] new ea5f563cb6 307: onsuccess: #2124: 1: Success after gcc: 2 commits new 1167ad895d 308: onsuccess: #2126: 1: Success after binutils/gcc/linux/g [...] new fd1b03d57a 309: onsuccess: #2127: 1: Success after binutils/gcc/glibc/g [...] new fa273820b4 310: onsuccess: #2129: 1: Success after binutils: 4 commits new f5b7b1df14 311: onsuccess: #2130: 1: Success after gcc: 4 commits new aa0e5d4d56 312: onsuccess: #2132: 1: Success after glibc-2.36.9000-416- [...] new 1e7c802c84 313: onsuccess: #2133: 1: Success after binutils/gcc/linux/g [...] new f1ea7314a3 314: onsuccess: #2134: 1: Success after binutils/gcc/glibc/g [...] new 0ce39ba5b6 315: onsuccess: #2135: 1: Success after binutils/gcc/gdb: 11 [...] new c887e52834 316: onsuccess: #2136: 1: Success after binutils/gcc/gdb: 26 [...] new 5289f7dd42 317: onsuccess: #2137: 1: Success after binutils/gcc/linux/g [...] new df5cd1e91d 318: onsuccess: #2138: 1: Success after binutils/gcc/linux/g [...] new 55327714b7 319: onsuccess: #2139: 1: Success after binutils/gcc/gdb: 11 [...] new 9b4f52cea7 320: onsuccess: #2140: 1: Success after binutils/gcc/gdb: 6 commits new 5bbf98aae8 321: onsuccess: #2141: 1: Success after binutils/gcc/linux/g [...] new 44f0e08e96 322: onsuccess: #2142: 1: Success after binutils/gcc/linux/g [...] new 004af1ebbb 323: onsuccess: #2143: 1: Success after basepoints/gcc-13-50 [...] new 129b5a8b1c 324: onsuccess: #2144: 1: Success after binutils/gcc/gdb/qem [...] new 248b2a0c19 325: onsuccess: #2145: 1: Success after binutils/gcc/glibc/g [...] new b0f587b61a 326: onsuccess: #2146: 1: Success after binutils/gcc/linux/g [...] new 87e8273c9e 327: onsuccess: #2147: 1: Success after basepoints/gcc-13-50 [...] new fe8c8b13ac 328: onsuccess: #2148: 1: Success after gcc/linux/qemu: 78 commits new 6337f47844 329: onsuccess: #2149: 1: Success after binutils/gcc/gdb/qem [...] new b030f23afb 330: onsuccess: #2150: 1: Success after linux/qemu: 36 commits new ca14f79858 331: onsuccess: #2151: 1: Success after binutils/gcc/linux/g [...] new eb2d99cfcf 332: onsuccess: #2152: 1: Success after binutils/gcc/gdb/qem [...] new 240b7bc6a8 333: onsuccess: #2153: 1: Success after binutils/gcc/gdb/qem [...] new e2d2ffd2c5 334: onsuccess: #2154: 1: Success after binutils/gcc/linux/g [...] new bde7fb1ffe 335: onsuccess: #2155: 1: Success after binutils/gdb: 146 commits new 38ad6eb7be 336: onsuccess: #2156: 1: Success after binutils/gcc/linux/g [...] new e5e7de6500 337: onsuccess: #2157: 1: Success after binutils/gcc/glibc/g [...] new a4bbbdccc3 338: onsuccess: #2158: 1: Success after binutils/gcc/linux/g [...] new 12a28bbea5 339: onsuccess: #2159: 1: Success after binutils/gcc/gdb: 4 commits new d5f4bbca36 340: onsuccess: #2160: 1: Success after binutils/gcc/gdb: 15 [...] new f7f9a24f56 341: onsuccess: #2161: 1: Success after binutils/gcc/gdb: 11 [...] new 0c2f7c4dc1 342: onsuccess: #2162: 1: Success after binutils/gcc/linux/g [...] new 6e0ddca995 343: onsuccess: #2163: 1: Success after binutils/gcc/gdb: 7 commits new 8062a8095b 344: onsuccess: #2164: 1: Success after gcc/linux/glibc: 37 commits new af768508cf 345: onsuccess: #2165: 1: Success after binutils/gcc/glibc/g [...] new cdb45e1f23 346: onsuccess: #2166: 1: Success after binutils/gcc/linux/g [...]

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 (ab95e55f42) \ 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 1804 -> 1780 bytes 02-prepare_abe/console.log.xz | Bin 2776 -> 2796 bytes 03-build_abe-binutils/console.log.xz | Bin 31784 -> 32288 bytes 04-build_abe-stage1/console.log.xz | Bin 91688 -> 92688 bytes 06-build_abe-linux/console.log.xz | Bin 8748 -> 9508 bytes 07-build_abe-glibc/console.log.xz | Bin 236644 -> 238552 bytes 08-build_abe-stage2/console.log.xz | Bin 227796 -> 229728 bytes 09-build_abe-gdb/console.log.xz | Bin 39384 -> 39376 bytes 10-build_abe-qemu/console.log.xz | Bin 31572 -> 32340 bytes 11-build_abe-dejagnu/console.log.xz | Bin 3872 -> 3888 bytes 12-build_abe-check_gcc/console.log.xz | Bin 2624 -> 2540 bytes 13-check_regression/console.log.xz | Bin 6536 -> 6384 bytes 13-check_regression/results.compare | 12 +- 13-check_regression/results.compare2 | 51 +- 14-update_baseline/console.log | 66 +- dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- git/gdb_rev | 2 +- git/linux_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 2 +- mail/mail-subject.txt | 2 +- manifest.sh | 38 +- sumfiles/g++.log.xz | Bin 2662784 -> 2686892 bytes sumfiles/g++.sum | 36 +- sumfiles/gcc.log.xz | Bin 2269268 -> 2239296 bytes sumfiles/gcc.sum | 2406 +++++++++++++++++---------------- sumfiles/gfortran.log.xz | Bin 896916 -> 897004 bytes sumfiles/gfortran.sum | 4 +- sumfiles/libatomic.log.xz | Bin 2264 -> 2260 bytes sumfiles/libatomic.sum | 2 +- sumfiles/libgomp.log.xz | Bin 214072 -> 214136 bytes sumfiles/libgomp.sum | 2 +- sumfiles/libitm.log.xz | Bin 2664 -> 2668 bytes sumfiles/libitm.sum | 2 +- sumfiles/libstdc++.log.xz | Bin 439500 -> 442204 bytes sumfiles/libstdc++.sum | 8 +- 38 files changed, 1328 insertions(+), 1315 deletions(-)