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 02c0e25477 344: onsuccess: #2164: 1: Success after gcc/linux/glibc: 37 commits discards 63eb5dba01 343: onsuccess: #2163: 1: Success after binutils/gcc/gdb: 7 commits discards 9dd844b8c1 342: onsuccess: #2162: 1: Success after binutils/gcc/linux/g [...] discards eb05a81241 341: onsuccess: #2161: 1: Success after binutils/gcc/gdb: 11 [...] discards 365210a19d 340: onsuccess: #2160: 1: Success after binutils/gcc/gdb: 15 [...] discards 7286244547 339: onsuccess: #2159: 1: Success after binutils/gcc/gdb: 4 commits discards 2283646b17 338: onsuccess: #2158: 1: Success after binutils/gcc/linux/g [...] discards 37ea842f74 337: onsuccess: #2157: 1: Success after binutils/gcc/glibc/g [...] discards 63ef871612 336: onsuccess: #2156: 1: Success after binutils/gcc/linux/g [...] discards ea46232a81 335: onsuccess: #2155: 1: Success after binutils/gdb: 146 commits discards 49cbd7eff7 334: onsuccess: #2154: 1: Success after binutils/gcc/linux/g [...] discards 5db98d7f82 333: onsuccess: #2153: 1: Success after binutils/gcc/gdb/qem [...] discards 7565d110bb 332: onsuccess: #2152: 1: Success after binutils/gcc/gdb/qem [...] discards 59649dc5bf 331: onsuccess: #2151: 1: Success after binutils/gcc/linux/g [...] discards 4c2484b532 330: onsuccess: #2150: 1: Success after linux/qemu: 36 commits discards 509598bc9a 329: onsuccess: #2149: 1: Success after binutils/gcc/gdb/qem [...] discards dc32c5e4ed 328: onsuccess: #2148: 1: Success after gcc/linux/qemu: 78 commits discards fc46d42bb2 327: onsuccess: #2147: 1: Success after basepoints/gcc-13-50 [...] discards d39ab7e888 326: onsuccess: #2146: 1: Success after binutils/gcc/linux/g [...] discards 2b3612a2e5 325: onsuccess: #2145: 1: Success after binutils/gcc/glibc/g [...] discards 17f9482136 324: onsuccess: #2144: 1: Success after binutils/gcc/gdb/qem [...] discards 8328e94084 323: onsuccess: #2143: 1: Success after basepoints/gcc-13-50 [...] discards b91d6ff321 322: onsuccess: #2142: 1: Success after binutils/gcc/linux/g [...] discards dc9a37bc30 321: onsuccess: #2141: 1: Success after binutils/gcc/linux/g [...] discards 1ccae392ee 320: onsuccess: #2140: 1: Success after binutils/gcc/gdb: 6 commits discards f408c3d8b9 319: onsuccess: #2139: 1: Success after binutils/gcc/gdb: 11 [...] discards 7a79eb7342 318: onsuccess: #2138: 1: Success after binutils/gcc/linux/g [...] discards 4362733bfe 317: onsuccess: #2137: 1: Success after binutils/gcc/linux/g [...] discards 8b88640f42 316: onsuccess: #2136: 1: Success after binutils/gcc/gdb: 26 [...] discards 3f62da0584 315: onsuccess: #2135: 1: Success after binutils/gcc/gdb: 11 [...] discards 5345756547 314: onsuccess: #2134: 1: Success after binutils/gcc/glibc/g [...] discards 90d5d3b4f9 313: onsuccess: #2133: 1: Success after binutils/gcc/linux/g [...] discards 5f273cfc05 312: onsuccess: #2132: 1: Success after glibc-2.36.9000-416- [...] discards 631e398778 311: onsuccess: #2130: 1: Success after gcc: 4 commits discards 331bbbf28e 310: onsuccess: #2129: 1: Success after binutils: 4 commits discards 3971ce6f6c 309: onsuccess: #2127: 1: Success after binutils/gcc/glibc/g [...] discards cade1e53a8 308: onsuccess: #2126: 1: Success after binutils/gcc/linux/g [...] discards dd409bfa47 307: onsuccess: #2124: 1: Success after gcc: 2 commits discards 706bd6e528 306: onsuccess: #2123: 1: Success after binutils/gcc/gdb: 15 [...] discards bb5056e86b 305: onsuccess: #2122: 1: Success after binutils/gcc/gdb: 4 commits discards acb259daf4 304: onsuccess: #2121: 1: Success after gcc/linux: 13 commits discards e98d5de71f 303: onsuccess: #2120: 1: Success after binutils/gdb: 20 commits discards 8af80c6483 302: onsuccess: #2119: 1: Success after binutils/gdb: 7 commits discards d5092ae76a 301: onsuccess: #2118: 1: Success after linux: 16 commits discards 62514e7a2b 300: onsuccess: #2117: 1: Success after basepoints/gcc-13-49 [...] discards ea4970f00f 299: onsuccess: #2116: 1: Success after gdb-13-branchpoint-2 [...] discards 5fe09ed4bf 298: onsuccess: #2114: 1: Success after binutils/gcc/gdb: 6 commits discards f40e3a08e8 297: onsuccess: #2113: 1: Success after binutils/gcc/gdb: 7 commits discards 91586a6d1b 296: onsuccess: #2112: 1: Success after gcc/linux: 26 commits discards c63845edd7 295: onsuccess: #2111: 1: Success after binutils/gcc/linux/g [...] discards 2ee3a7a32b 294: onsuccess: #2110: 1: Success after gcc: 17 commits discards 2ada35ef5a 293: onsuccess: #2109: 1: Success after binutils/gdb: 2 commits discards b17e865bda 292: onsuccess: #2108: 1: Success after binutils/gcc/gdb: 3 commits discards 4f6f47c31a 291: onsuccess: #2107: 1: Success after binutils/gcc/gdb: 6 commits discards b93d82d7b6 290: onsuccess: #2106: 1: Success after gcc: 2 commits discards 1903ff6ec7 289: onsuccess: #2105: 1: Success after binutils/gcc/gdb: 6 commits discards 2750036f9a 288: onsuccess: #2104: 1: Success after binutils/gcc/gdb: 10 [...] discards 995a26ba23 287: onsuccess: #2103: 1: Success after gcc: 9 commits discards d96a70a05f 286: onsuccess: #2102: 1: Success after binutils/gdb: 18 commits discards a7ee4e035a 285: onsuccess: #2101: 1: Success after binutils/gcc/gdb: 5 commits discards 7891277db1 284: onsuccess: #2100: 1: Success after basepoints/gcc-13-48 [...] discards b8741c7140 283: onsuccess: #2099: 1: Success after binutils/gdb: 4 commits discards 000e74fa19 282: onsuccess: #2098: 1: Success after binutils/gcc/linux/g [...] discards 1d655ad839 281: onsuccess: #2097: 1: Success after binutils/gcc/gdb: 23 [...] discards f51956f217 280: onsuccess: #2096: 1: Success after binutils/gcc/gdb: 21 [...] discards 0f05e0c962 279: onsuccess: #2095: 1: Success after binutils/gcc/gdb: 5 commits discards 3a1d8c9619 278: onsuccess: #2094: 1: Success after binutils/gcc/linux/g [...] discards fbc295bd1e 277: onsuccess: #2093: 1: Success after binutils/gcc/linux/g [...] discards 7bba4fef91 276: onsuccess: #2092: 1: Success after binutils/gcc/gdb: 69 [...] discards 68953a3cd0 275: onsuccess: #2091: 1: Success after binutils/gcc/gdb: 42 [...] discards 182a92c2f3 274: onsuccess: #2090: 1: Success after binutils/gcc/linux/g [...] discards 8e4d648cc6 273: onsuccess: #2089: 1: Success after binutils/gcc/glibc/g [...] discards 23c8ebf66b 272: onsuccess: #2088: 1: Success after binutils/gcc/gdb: 28 [...] discards 9feffa509c 271: onsuccess: #2087: 1: Success after binutils/gcc/linux/g [...] discards 1410411783 270: onsuccess: #2086: 1: Success after binutils/gcc/glibc/g [...] discards 6834f86eef 269: onsuccess: #2085: 1: Success after binutils/gcc/linux/g [...] discards bb9496739b 268: onsuccess: #2084: 1: Success after binutils/gcc/gdb/qem [...] discards 5a139db57c 267: onsuccess: #2083: 1: Success after binutils/gcc/gdb: 64 [...] discards 47e67d19bd 266: onsuccess: #2082: 1: Success after binutils/gcc/gdb: 8 commits discards b873d37ed8 265: onsuccess: #2081: 1: Success after gcc/linux/glibc/qemu [...] discards cd20565550 264: onsuccess: #2080: 1: Success after binutils/gcc/gdb: 7 commits discards 11a521144c 263: onsuccess: #2079: 1: Success after binutils/gcc/gdb: 7 commits discards f3598d5eea 262: onsuccess: #2078: 1: Success after binutils/gcc/linux/g [...] discards 2f8ed2691b 261: onsuccess: #2077: 1: Success after binutils/gcc/linux/g [...] discards 25917ff1e7 260: onsuccess: #2076: 1: Success after binutils/gcc/glibc/g [...] discards 6e65d5e15c 259: onsuccess: #2075: 1: Success after glibc: 2 commits discards cb63b29f79 258: onsuccess: #2074: 1: Success after binutils/gcc/glibc/g [...] discards 13b3a91ff9 257: onsuccess: #2073: 1: Success after v7.2.0-211-g562d4af3 [...] discards d5c269859e 256: onsuccess: #2072: 1: Success after binutils/gcc/gdb: 5 commits discards 05f9e3af16 255: onsuccess: #2071: 1: Success after binutils/gcc/gdb: 5 commits discards 01d3f88f55 254: onsuccess: #2070: 1: Success after binutils/gcc/gdb/qem [...] discards 479a5ccdb0 253: onsuccess: #2069: 1: Success after gcc/linux: 109 commits discards 3543b8fbfd 252: onsuccess: #2068: 1: Success after binutils/gdb: 6 commits discards 391b71a89e 251: onsuccess: #2067: 1: Success after binutils/gcc/gdb: 13 [...] discards e63c73d9e6 250: onsuccess: #2066: 1: Success after binutils/gcc/linux/g [...] discards 3b49915972 249: onsuccess: #2065: 1: Success after binutils/gcc/linux/g [...] discards eebbbefc05 248: onsuccess: #2064: 1: Success after binutils/gcc/gdb/qem [...] discards c26e7934a3 247: onsuccess: #2063: 1: Success after binutils/gcc/linux/g [...] discards 582e5a102e 246: onsuccess: #2062: 1: Success after binutils/gcc/linux/g [...] discards f6c5832dcf 245: onsuccess: #2061: 1: Success after binutils/gcc/linux/g [...] discards 6203907340 244: onsuccess: #2060: 1: Success after binutils/gcc/gdb/qem [...] new 962f4f897d 244: onsuccess: #2060: 1: Success after binutils/gcc/gdb/qem [...] new bfd6791009 245: onsuccess: #2061: 1: Success after binutils/gcc/linux/g [...] new 0c50ebd18f 246: onsuccess: #2062: 1: Success after binutils/gcc/linux/g [...] new 997acf8933 247: onsuccess: #2063: 1: Success after binutils/gcc/linux/g [...] new 788ffd7668 248: onsuccess: #2064: 1: Success after binutils/gcc/gdb/qem [...] new 2f7a17e382 249: onsuccess: #2065: 1: Success after binutils/gcc/linux/g [...] new 6be5e35b60 250: onsuccess: #2066: 1: Success after binutils/gcc/linux/g [...] new c738568e07 251: onsuccess: #2067: 1: Success after binutils/gcc/gdb: 13 [...] new 05b15245a7 252: onsuccess: #2068: 1: Success after binutils/gdb: 6 commits new 6328f481a0 253: onsuccess: #2069: 1: Success after gcc/linux: 109 commits new 72a93466b2 254: onsuccess: #2070: 1: Success after binutils/gcc/gdb/qem [...] new 07a5e2722c 255: onsuccess: #2071: 1: Success after binutils/gcc/gdb: 5 commits new 644b425f35 256: onsuccess: #2072: 1: Success after binutils/gcc/gdb: 5 commits new 093370902f 257: onsuccess: #2073: 1: Success after v7.2.0-211-g562d4af3 [...] new b7fd6db9d1 258: onsuccess: #2074: 1: Success after binutils/gcc/glibc/g [...] new 3c89f5b9c2 259: onsuccess: #2075: 1: Success after glibc: 2 commits new 900aa2fb18 260: onsuccess: #2076: 1: Success after binutils/gcc/glibc/g [...] new a54a6c3906 261: onsuccess: #2077: 1: Success after binutils/gcc/linux/g [...] new 87ac41ca23 262: onsuccess: #2078: 1: Success after binutils/gcc/linux/g [...] new 10826bc70e 263: onsuccess: #2079: 1: Success after binutils/gcc/gdb: 7 commits new c210749b50 264: onsuccess: #2080: 1: Success after binutils/gcc/gdb: 7 commits new 8d93f6fed6 265: onsuccess: #2081: 1: Success after gcc/linux/glibc/qemu [...] new d64641a1e9 266: onsuccess: #2082: 1: Success after binutils/gcc/gdb: 8 commits new 081bb49e3b 267: onsuccess: #2083: 1: Success after binutils/gcc/gdb: 64 [...] new f8fca80fca 268: onsuccess: #2084: 1: Success after binutils/gcc/gdb/qem [...] new 9e29e9a38f 269: onsuccess: #2085: 1: Success after binutils/gcc/linux/g [...] new ca74113ba9 270: onsuccess: #2086: 1: Success after binutils/gcc/glibc/g [...] new 25dece8ecf 271: onsuccess: #2087: 1: Success after binutils/gcc/linux/g [...] new 963b4cf54d 272: onsuccess: #2088: 1: Success after binutils/gcc/gdb: 28 [...] new 86d24b971e 273: onsuccess: #2089: 1: Success after binutils/gcc/glibc/g [...] new 1096996c2a 274: onsuccess: #2090: 1: Success after binutils/gcc/linux/g [...] new 2d018ad732 275: onsuccess: #2091: 1: Success after binutils/gcc/gdb: 42 [...] new bcbd6088b6 276: onsuccess: #2092: 1: Success after binutils/gcc/gdb: 69 [...] new c4f1551751 277: onsuccess: #2093: 1: Success after binutils/gcc/linux/g [...] new 56b59467da 278: onsuccess: #2094: 1: Success after binutils/gcc/linux/g [...] new bb0f55ffe5 279: onsuccess: #2095: 1: Success after binutils/gcc/gdb: 5 commits new 22c8c3387c 280: onsuccess: #2096: 1: Success after binutils/gcc/gdb: 21 [...] new ef9179a330 281: onsuccess: #2097: 1: Success after binutils/gcc/gdb: 23 [...] new 0a0f54729a 282: onsuccess: #2098: 1: Success after binutils/gcc/linux/g [...] new c0a10dce34 283: onsuccess: #2099: 1: Success after binutils/gdb: 4 commits new 8d80e05ff9 284: onsuccess: #2100: 1: Success after basepoints/gcc-13-48 [...] new 77a4f9d330 285: onsuccess: #2101: 1: Success after binutils/gcc/gdb: 5 commits new cc3fb68c7e 286: onsuccess: #2102: 1: Success after binutils/gdb: 18 commits new 1623689bee 287: onsuccess: #2103: 1: Success after gcc: 9 commits new 4302423792 288: onsuccess: #2104: 1: Success after binutils/gcc/gdb: 10 [...] new 164aec2343 289: onsuccess: #2105: 1: Success after binutils/gcc/gdb: 6 commits new dbc2a2e62e 290: onsuccess: #2106: 1: Success after gcc: 2 commits new 142f72b8a6 291: onsuccess: #2107: 1: Success after binutils/gcc/gdb: 6 commits new ddcf752596 292: onsuccess: #2108: 1: Success after binutils/gcc/gdb: 3 commits new bf88f9e9fa 293: onsuccess: #2109: 1: Success after binutils/gdb: 2 commits new bab087299d 294: onsuccess: #2110: 1: Success after gcc: 17 commits new e3ed82b7e9 295: onsuccess: #2111: 1: Success after binutils/gcc/linux/g [...] new 3f5ffa9761 296: onsuccess: #2112: 1: Success after gcc/linux: 26 commits new 8c23d07a9a 297: onsuccess: #2113: 1: Success after binutils/gcc/gdb: 7 commits new a613cc0e77 298: onsuccess: #2114: 1: Success after binutils/gcc/gdb: 6 commits new baeeb3023b 299: onsuccess: #2116: 1: Success after gdb-13-branchpoint-2 [...] new 48bdc754f5 300: onsuccess: #2117: 1: Success after basepoints/gcc-13-49 [...] new bea3c3be16 301: onsuccess: #2118: 1: Success after linux: 16 commits new 9d5393bda7 302: onsuccess: #2119: 1: Success after binutils/gdb: 7 commits new 1e5f7b9f8f 303: onsuccess: #2120: 1: Success after binutils/gdb: 20 commits new 1427901711 304: onsuccess: #2121: 1: Success after gcc/linux: 13 commits new eb0c9bfd38 305: onsuccess: #2122: 1: Success after binutils/gcc/gdb: 4 commits new 3aaf967a0f 306: onsuccess: #2123: 1: Success after binutils/gcc/gdb: 15 [...] new 41114194ae 307: onsuccess: #2124: 1: Success after gcc: 2 commits new 82aa6c2990 308: onsuccess: #2126: 1: Success after binutils/gcc/linux/g [...] new 1207b2aae7 309: onsuccess: #2127: 1: Success after binutils/gcc/glibc/g [...] new 8231f8dc63 310: onsuccess: #2129: 1: Success after binutils: 4 commits new 72ac057ba3 311: onsuccess: #2130: 1: Success after gcc: 4 commits new d613c405e7 312: onsuccess: #2132: 1: Success after glibc-2.36.9000-416- [...] new 13f52ffb91 313: onsuccess: #2133: 1: Success after binutils/gcc/linux/g [...] new c5021542fe 314: onsuccess: #2134: 1: Success after binutils/gcc/glibc/g [...] new 785d8c036d 315: onsuccess: #2135: 1: Success after binutils/gcc/gdb: 11 [...] new 1035d43f3f 316: onsuccess: #2136: 1: Success after binutils/gcc/gdb: 26 [...] new 72e9db421f 317: onsuccess: #2137: 1: Success after binutils/gcc/linux/g [...] new 6ee8dc20f6 318: onsuccess: #2138: 1: Success after binutils/gcc/linux/g [...] new 5a9186c9c1 319: onsuccess: #2139: 1: Success after binutils/gcc/gdb: 11 [...] new 1e03739f07 320: onsuccess: #2140: 1: Success after binutils/gcc/gdb: 6 commits new bab9c44a03 321: onsuccess: #2141: 1: Success after binutils/gcc/linux/g [...] new f8770a71d1 322: onsuccess: #2142: 1: Success after binutils/gcc/linux/g [...] new 67a054e287 323: onsuccess: #2143: 1: Success after basepoints/gcc-13-50 [...] new d5109f89a0 324: onsuccess: #2144: 1: Success after binutils/gcc/gdb/qem [...] new b7d45cd91b 325: onsuccess: #2145: 1: Success after binutils/gcc/glibc/g [...] new 9db15a8a7e 326: onsuccess: #2146: 1: Success after binutils/gcc/linux/g [...] new 83a94c809e 327: onsuccess: #2147: 1: Success after basepoints/gcc-13-50 [...] new 9d7709e5c5 328: onsuccess: #2148: 1: Success after gcc/linux/qemu: 78 commits new 032e033940 329: onsuccess: #2149: 1: Success after binutils/gcc/gdb/qem [...] new a736a49048 330: onsuccess: #2150: 1: Success after linux/qemu: 36 commits new 1e0b3ab099 331: onsuccess: #2151: 1: Success after binutils/gcc/linux/g [...] new 6ed9229005 332: onsuccess: #2152: 1: Success after binutils/gcc/gdb/qem [...] new 587febeba1 333: onsuccess: #2153: 1: Success after binutils/gcc/gdb/qem [...] new 9edada8131 334: onsuccess: #2154: 1: Success after binutils/gcc/linux/g [...] new fd737d46b9 335: onsuccess: #2155: 1: Success after binutils/gdb: 146 commits new d1e180fa6e 336: onsuccess: #2156: 1: Success after binutils/gcc/linux/g [...] new 40b8de3c4f 337: onsuccess: #2157: 1: Success after binutils/gcc/glibc/g [...] new d767712c7b 338: onsuccess: #2158: 1: Success after binutils/gcc/linux/g [...] new ef11600bfc 339: onsuccess: #2159: 1: Success after binutils/gcc/gdb: 4 commits new 49705fafa0 340: onsuccess: #2160: 1: Success after binutils/gcc/gdb: 15 [...] new f30dc6f794 341: onsuccess: #2161: 1: Success after binutils/gcc/gdb: 11 [...] new 26deb62f5c 342: onsuccess: #2162: 1: Success after binutils/gcc/linux/g [...] new 3b7552770e 343: onsuccess: #2163: 1: Success after binutils/gcc/gdb: 7 commits new 2d980d0e49 344: onsuccess: #2164: 1: Success after gcc/linux/glibc: 37 commits new ab95e55f42 345: onsuccess: #2165: 1: Success after binutils/gcc/glibc/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 (02c0e25477) \ 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 -> 1804 bytes 02-prepare_abe/console.log.xz | Bin 2776 -> 2776 bytes 03-build_abe-binutils/console.log.xz | Bin 32128 -> 31784 bytes 04-build_abe-stage1/console.log.xz | Bin 91796 -> 91688 bytes 06-build_abe-linux/console.log.xz | Bin 8736 -> 8748 bytes 07-build_abe-glibc/console.log.xz | Bin 236384 -> 236644 bytes 08-build_abe-stage2/console.log.xz | Bin 228092 -> 227796 bytes 09-build_abe-gdb/console.log.xz | Bin 39572 -> 39384 bytes 10-build_abe-qemu/console.log.xz | Bin 31228 -> 31572 bytes 11-build_abe-dejagnu/console.log.xz | Bin 3876 -> 3872 bytes 12-build_abe-check_gcc/console.log.xz | Bin 2612 -> 2624 bytes 13-check_regression/console.log.xz | Bin 5964 -> 6536 bytes 13-check_regression/results.compare | 20 +- 13-check_regression/results.compare2 | 31 +- 14-update_baseline/console.log | 42 +- dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- git/gdb_rev | 2 +- git/glibc_rev | 2 +- git/qemu_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 2 +- mail/mail-subject.txt | 2 +- manifest.sh | 42 +- sumfiles/g++.log.xz | Bin 2691504 -> 2662784 bytes sumfiles/g++.sum | 22 +- sumfiles/gcc.log.xz | Bin 2253956 -> 2269268 bytes sumfiles/gcc.sum | 2306 ++++++++++++++++----------------- sumfiles/gfortran.log.xz | Bin 891828 -> 896916 bytes sumfiles/gfortran.sum | 2 +- sumfiles/libatomic.log.xz | Bin 2260 -> 2264 bytes sumfiles/libatomic.sum | 2 +- sumfiles/libgomp.log.xz | Bin 214024 -> 214072 bytes sumfiles/libgomp.sum | 2 +- sumfiles/libitm.log.xz | Bin 2672 -> 2664 bytes sumfiles/libitm.sum | 2 +- sumfiles/libstdc++.log.xz | Bin 433640 -> 439500 bytes sumfiles/libstdc++.sum | 2 +- 39 files changed, 1249 insertions(+), 1242 deletions(-)