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 79ec3880fb 360: onsuccess: #2180: 1: Success after binutils/gcc/linux/g [...] discards 4aabcd9a11 359: onsuccess: #2179: 1: Success after binutils/gcc/glibc/g [...] discards 27d8c65251 358: onsuccess: #2178: 1: Success after binutils/gcc/linux/g [...] discards b9f688a74f 357: onsuccess: #2177: 1: Success after binutils/gcc/linux/g [...] discards 601c2a2991 356: onsuccess: #2176: 1: Success after binutils/gcc/linux/g [...] discards 09f4db3b9d 355: onsuccess: #2175: 1: Success after binutils/gcc/linux/g [...] discards 8255fbc9d1 354: onsuccess: #2174: 1: Success after binutils/gcc/linux/g [...] discards 923fef0e23 353: onsuccess: #2173: 1: Success after binutils/gcc/gdb: 27 [...] discards 01df53e78b 352: onsuccess: #2172: 1: Success after binutils/gcc/linux/g [...] discards 76a598e198 351: onsuccess: #2171: 1: Success after gcc/linux: 15 commits discards 2e9ddbfda2 350: onsuccess: #2170: 1: Success after binutils/gcc/linux/g [...] discards 7cefa9b54d 349: onsuccess: #2169: 1: Success after binutils/gcc/linux/g [...] discards d6f0662599 348: onsuccess: #2168: 1: Success after binutils/gcc/gdb: 9 commits discards 1d66ea12e7 347: onsuccess: #2167: 1: Success after basepoints/gcc-13-51 [...] discards 0fe3072387 346: onsuccess: #2166: 1: Success after binutils/gcc/linux/g [...] discards 2e918baefb 345: onsuccess: #2165: 1: Success after binutils/gcc/glibc/g [...] discards a50f2c95c9 344: onsuccess: #2164: 1: Success after gcc/linux/glibc: 37 commits discards 8152277730 343: onsuccess: #2163: 1: Success after binutils/gcc/gdb: 7 commits discards feee2aed1c 342: onsuccess: #2162: 1: Success after binutils/gcc/linux/g [...] discards a9c99e5559 341: onsuccess: #2161: 1: Success after binutils/gcc/gdb: 11 [...] discards b4ce71bb88 340: onsuccess: #2160: 1: Success after binutils/gcc/gdb: 15 [...] discards 2ce81de3f1 339: onsuccess: #2159: 1: Success after binutils/gcc/gdb: 4 commits discards 088e362488 338: onsuccess: #2158: 1: Success after binutils/gcc/linux/g [...] discards a985ba53d7 337: onsuccess: #2157: 1: Success after binutils/gcc/glibc/g [...] discards a30b2cd39d 336: onsuccess: #2156: 1: Success after binutils/gcc/linux/g [...] discards 329af198b1 335: onsuccess: #2155: 1: Success after binutils/gdb: 146 commits discards adc90b4a2b 334: onsuccess: #2154: 1: Success after binutils/gcc/linux/g [...] discards 5543e3edd7 333: onsuccess: #2153: 1: Success after binutils/gcc/gdb/qem [...] discards c452d6ab5d 332: onsuccess: #2152: 1: Success after binutils/gcc/gdb/qem [...] discards 2bd2d84c49 331: onsuccess: #2151: 1: Success after binutils/gcc/linux/g [...] discards bb1ddf68b7 330: onsuccess: #2150: 1: Success after linux/qemu: 36 commits discards 47dbc20e2d 329: onsuccess: #2149: 1: Success after binutils/gcc/gdb/qem [...] discards ff89dffe81 328: onsuccess: #2148: 1: Success after gcc/linux/qemu: 78 commits discards e4f8920487 327: onsuccess: #2147: 1: Success after basepoints/gcc-13-50 [...] discards 30136cea47 326: onsuccess: #2146: 1: Success after binutils/gcc/linux/g [...] discards 7151bf96de 325: onsuccess: #2145: 1: Success after binutils/gcc/glibc/g [...] discards 93b526a28c 324: onsuccess: #2144: 1: Success after binutils/gcc/gdb/qem [...] discards 9a39bda479 323: onsuccess: #2143: 1: Success after basepoints/gcc-13-50 [...] discards 61e7420364 322: onsuccess: #2142: 1: Success after binutils/gcc/linux/g [...] discards 62b0cd628f 321: onsuccess: #2141: 1: Success after binutils/gcc/linux/g [...] discards 1e3b2c9417 320: onsuccess: #2140: 1: Success after binutils/gcc/gdb: 6 commits discards 6a95731006 319: onsuccess: #2139: 1: Success after binutils/gcc/gdb: 11 [...] discards e80bbafb29 318: onsuccess: #2138: 1: Success after binutils/gcc/linux/g [...] discards 6f8b86f896 317: onsuccess: #2137: 1: Success after binutils/gcc/linux/g [...] discards 4971be5368 316: onsuccess: #2136: 1: Success after binutils/gcc/gdb: 26 [...] discards 86d06a3fcb 315: onsuccess: #2135: 1: Success after binutils/gcc/gdb: 11 [...] discards 145678a3aa 314: onsuccess: #2134: 1: Success after binutils/gcc/glibc/g [...] discards a38dfe4568 313: onsuccess: #2133: 1: Success after binutils/gcc/linux/g [...] discards 04c213fb34 312: onsuccess: #2132: 1: Success after glibc-2.36.9000-416- [...] discards a49e035aa6 311: onsuccess: #2130: 1: Success after gcc: 4 commits discards 6f0440c2b9 310: onsuccess: #2129: 1: Success after binutils: 4 commits discards f70c209f5a 309: onsuccess: #2127: 1: Success after binutils/gcc/glibc/g [...] discards f0c5861033 308: onsuccess: #2126: 1: Success after binutils/gcc/linux/g [...] discards 02f85a451b 307: onsuccess: #2124: 1: Success after gcc: 2 commits discards efaad5d145 306: onsuccess: #2123: 1: Success after binutils/gcc/gdb: 15 [...] discards 0a8f7c0c57 305: onsuccess: #2122: 1: Success after binutils/gcc/gdb: 4 commits discards 205b3314e8 304: onsuccess: #2121: 1: Success after gcc/linux: 13 commits discards ce6bbab01b 303: onsuccess: #2120: 1: Success after binutils/gdb: 20 commits discards c835eec30c 302: onsuccess: #2119: 1: Success after binutils/gdb: 7 commits discards 6ae4649127 301: onsuccess: #2118: 1: Success after linux: 16 commits discards 0a61b8bef1 300: onsuccess: #2117: 1: Success after basepoints/gcc-13-49 [...] discards ceb09de022 299: onsuccess: #2116: 1: Success after gdb-13-branchpoint-2 [...] discards 23f6cddec9 298: onsuccess: #2114: 1: Success after binutils/gcc/gdb: 6 commits discards c76a8d6380 297: onsuccess: #2113: 1: Success after binutils/gcc/gdb: 7 commits discards 11a567e903 296: onsuccess: #2112: 1: Success after gcc/linux: 26 commits discards 0ab2cfd49b 295: onsuccess: #2111: 1: Success after binutils/gcc/linux/g [...] discards 434595a379 294: onsuccess: #2110: 1: Success after gcc: 17 commits discards 6b37ac610c 293: onsuccess: #2109: 1: Success after binutils/gdb: 2 commits discards 53a79c548e 292: onsuccess: #2108: 1: Success after binutils/gcc/gdb: 3 commits discards fd503c288c 291: onsuccess: #2107: 1: Success after binutils/gcc/gdb: 6 commits discards 8c379538f4 290: onsuccess: #2106: 1: Success after gcc: 2 commits discards 033824a05f 289: onsuccess: #2105: 1: Success after binutils/gcc/gdb: 6 commits discards abf335f8e2 288: onsuccess: #2104: 1: Success after binutils/gcc/gdb: 10 [...] discards 17f0b39aee 287: onsuccess: #2103: 1: Success after gcc: 9 commits discards 7ae9a96594 286: onsuccess: #2102: 1: Success after binutils/gdb: 18 commits discards e4264467db 285: onsuccess: #2101: 1: Success after binutils/gcc/gdb: 5 commits discards a6494db78b 284: onsuccess: #2100: 1: Success after basepoints/gcc-13-48 [...] discards 8c1c5a87a7 283: onsuccess: #2099: 1: Success after binutils/gdb: 4 commits discards 0961e8c8d4 282: onsuccess: #2098: 1: Success after binutils/gcc/linux/g [...] discards 979abd611a 281: onsuccess: #2097: 1: Success after binutils/gcc/gdb: 23 [...] discards e1bdc8c3c5 280: onsuccess: #2096: 1: Success after binutils/gcc/gdb: 21 [...] discards 9d7c42837d 279: onsuccess: #2095: 1: Success after binutils/gcc/gdb: 5 commits discards 2903ac2a49 278: onsuccess: #2094: 1: Success after binutils/gcc/linux/g [...] discards bcf473f6f0 277: onsuccess: #2093: 1: Success after binutils/gcc/linux/g [...] discards d2bd30972d 276: onsuccess: #2092: 1: Success after binutils/gcc/gdb: 69 [...] discards 62f5675995 275: onsuccess: #2091: 1: Success after binutils/gcc/gdb: 42 [...] discards 3edc305c15 274: onsuccess: #2090: 1: Success after binutils/gcc/linux/g [...] discards e5c1f05a7e 273: onsuccess: #2089: 1: Success after binutils/gcc/glibc/g [...] discards 148f948052 272: onsuccess: #2088: 1: Success after binutils/gcc/gdb: 28 [...] discards 77d0a93925 271: onsuccess: #2087: 1: Success after binutils/gcc/linux/g [...] discards 8f6fb11d48 270: onsuccess: #2086: 1: Success after binutils/gcc/glibc/g [...] discards 2c2b95f459 269: onsuccess: #2085: 1: Success after binutils/gcc/linux/g [...] discards c9f1ff5cac 268: onsuccess: #2084: 1: Success after binutils/gcc/gdb/qem [...] discards 4c3d17947b 267: onsuccess: #2083: 1: Success after binutils/gcc/gdb: 64 [...] discards fc401a7d21 266: onsuccess: #2082: 1: Success after binutils/gcc/gdb: 8 commits discards 39ed6dc79b 265: onsuccess: #2081: 1: Success after gcc/linux/glibc/qemu [...] discards 79bb62328d 264: onsuccess: #2080: 1: Success after binutils/gcc/gdb: 7 commits discards 5871ed8d08 263: onsuccess: #2079: 1: Success after binutils/gcc/gdb: 7 commits discards 1de0f40efe 262: onsuccess: #2078: 1: Success after binutils/gcc/linux/g [...] discards bddff4a042 261: onsuccess: #2077: 1: Success after binutils/gcc/linux/g [...] discards 631459d4ed 260: onsuccess: #2076: 1: Success after binutils/gcc/glibc/g [...] new 91f2754a6f 260: onsuccess: #2076: 1: Success after binutils/gcc/glibc/g [...] new a4b2b4a160 261: onsuccess: #2077: 1: Success after binutils/gcc/linux/g [...] new 68f4a89ab1 262: onsuccess: #2078: 1: Success after binutils/gcc/linux/g [...] new 4e459ac294 263: onsuccess: #2079: 1: Success after binutils/gcc/gdb: 7 commits new 40a0f55df4 264: onsuccess: #2080: 1: Success after binutils/gcc/gdb: 7 commits new f633cc3d38 265: onsuccess: #2081: 1: Success after gcc/linux/glibc/qemu [...] new 19052820e4 266: onsuccess: #2082: 1: Success after binutils/gcc/gdb: 8 commits new 0d4914546c 267: onsuccess: #2083: 1: Success after binutils/gcc/gdb: 64 [...] new cb72c8771b 268: onsuccess: #2084: 1: Success after binutils/gcc/gdb/qem [...] new 2a6a24ee74 269: onsuccess: #2085: 1: Success after binutils/gcc/linux/g [...] new 39d73c794c 270: onsuccess: #2086: 1: Success after binutils/gcc/glibc/g [...] new 20e1218a61 271: onsuccess: #2087: 1: Success after binutils/gcc/linux/g [...] new f9cb11620f 272: onsuccess: #2088: 1: Success after binutils/gcc/gdb: 28 [...] new 5ea153dc22 273: onsuccess: #2089: 1: Success after binutils/gcc/glibc/g [...] new 8aae2351e3 274: onsuccess: #2090: 1: Success after binutils/gcc/linux/g [...] new 6902a72b17 275: onsuccess: #2091: 1: Success after binutils/gcc/gdb: 42 [...] new 0da7b5c0ff 276: onsuccess: #2092: 1: Success after binutils/gcc/gdb: 69 [...] new dd555a6164 277: onsuccess: #2093: 1: Success after binutils/gcc/linux/g [...] new 379f896e68 278: onsuccess: #2094: 1: Success after binutils/gcc/linux/g [...] new 2e7aa6bc0e 279: onsuccess: #2095: 1: Success after binutils/gcc/gdb: 5 commits new 6bb3bb838f 280: onsuccess: #2096: 1: Success after binutils/gcc/gdb: 21 [...] new af0287ca51 281: onsuccess: #2097: 1: Success after binutils/gcc/gdb: 23 [...] new ff326ba180 282: onsuccess: #2098: 1: Success after binutils/gcc/linux/g [...] new 75d81c276f 283: onsuccess: #2099: 1: Success after binutils/gdb: 4 commits new 8d76ce7b63 284: onsuccess: #2100: 1: Success after basepoints/gcc-13-48 [...] new fa64e4c699 285: onsuccess: #2101: 1: Success after binutils/gcc/gdb: 5 commits new 3b29d379d0 286: onsuccess: #2102: 1: Success after binutils/gdb: 18 commits new 317be00c5b 287: onsuccess: #2103: 1: Success after gcc: 9 commits new f7cd5e6fb9 288: onsuccess: #2104: 1: Success after binutils/gcc/gdb: 10 [...] new 595aa23508 289: onsuccess: #2105: 1: Success after binutils/gcc/gdb: 6 commits new 8f89f4f338 290: onsuccess: #2106: 1: Success after gcc: 2 commits new 086ab55107 291: onsuccess: #2107: 1: Success after binutils/gcc/gdb: 6 commits new c899fbef99 292: onsuccess: #2108: 1: Success after binutils/gcc/gdb: 3 commits new ecf85aedf3 293: onsuccess: #2109: 1: Success after binutils/gdb: 2 commits new 1fc7a07780 294: onsuccess: #2110: 1: Success after gcc: 17 commits new baefbc1e17 295: onsuccess: #2111: 1: Success after binutils/gcc/linux/g [...] new 559a0f1af1 296: onsuccess: #2112: 1: Success after gcc/linux: 26 commits new 02c1cb79a1 297: onsuccess: #2113: 1: Success after binutils/gcc/gdb: 7 commits new 3b9eec2572 298: onsuccess: #2114: 1: Success after binutils/gcc/gdb: 6 commits new db31bfb19a 299: onsuccess: #2116: 1: Success after gdb-13-branchpoint-2 [...] new d81f8e12bd 300: onsuccess: #2117: 1: Success after basepoints/gcc-13-49 [...] new 33d297356b 301: onsuccess: #2118: 1: Success after linux: 16 commits new 4a6ce8c28e 302: onsuccess: #2119: 1: Success after binutils/gdb: 7 commits new d05c5032aa 303: onsuccess: #2120: 1: Success after binutils/gdb: 20 commits new 3a384cca1c 304: onsuccess: #2121: 1: Success after gcc/linux: 13 commits new 4d824a89c9 305: onsuccess: #2122: 1: Success after binutils/gcc/gdb: 4 commits new e36333ef18 306: onsuccess: #2123: 1: Success after binutils/gcc/gdb: 15 [...] new e86ba8efd5 307: onsuccess: #2124: 1: Success after gcc: 2 commits new e7899fe96d 308: onsuccess: #2126: 1: Success after binutils/gcc/linux/g [...] new 13421508e6 309: onsuccess: #2127: 1: Success after binutils/gcc/glibc/g [...] new 27e31fc002 310: onsuccess: #2129: 1: Success after binutils: 4 commits new 1932682c18 311: onsuccess: #2130: 1: Success after gcc: 4 commits new 8255587d74 312: onsuccess: #2132: 1: Success after glibc-2.36.9000-416- [...] new 9ce4606eaa 313: onsuccess: #2133: 1: Success after binutils/gcc/linux/g [...] new 642cf72e88 314: onsuccess: #2134: 1: Success after binutils/gcc/glibc/g [...] new b1d80441e6 315: onsuccess: #2135: 1: Success after binutils/gcc/gdb: 11 [...] new c1d86045c2 316: onsuccess: #2136: 1: Success after binutils/gcc/gdb: 26 [...] new beebaf3dcd 317: onsuccess: #2137: 1: Success after binutils/gcc/linux/g [...] new ed53ad0854 318: onsuccess: #2138: 1: Success after binutils/gcc/linux/g [...] new 6a9a27526a 319: onsuccess: #2139: 1: Success after binutils/gcc/gdb: 11 [...] new 99ab22b28a 320: onsuccess: #2140: 1: Success after binutils/gcc/gdb: 6 commits new 66570240c5 321: onsuccess: #2141: 1: Success after binutils/gcc/linux/g [...] new f8685f0d8e 322: onsuccess: #2142: 1: Success after binutils/gcc/linux/g [...] new b5a0fad1fe 323: onsuccess: #2143: 1: Success after basepoints/gcc-13-50 [...] new 0de8ffa76c 324: onsuccess: #2144: 1: Success after binutils/gcc/gdb/qem [...] new cce12f9e5b 325: onsuccess: #2145: 1: Success after binutils/gcc/glibc/g [...] new 7d8d5891a0 326: onsuccess: #2146: 1: Success after binutils/gcc/linux/g [...] new d0fb160fae 327: onsuccess: #2147: 1: Success after basepoints/gcc-13-50 [...] new 05732d0066 328: onsuccess: #2148: 1: Success after gcc/linux/qemu: 78 commits new 1960cdefb3 329: onsuccess: #2149: 1: Success after binutils/gcc/gdb/qem [...] new 27296b0e08 330: onsuccess: #2150: 1: Success after linux/qemu: 36 commits new 4908fa1987 331: onsuccess: #2151: 1: Success after binutils/gcc/linux/g [...] new 928a8e1e41 332: onsuccess: #2152: 1: Success after binutils/gcc/gdb/qem [...] new 852a39cb94 333: onsuccess: #2153: 1: Success after binutils/gcc/gdb/qem [...] new 3392e7fecd 334: onsuccess: #2154: 1: Success after binutils/gcc/linux/g [...] new caad3d413c 335: onsuccess: #2155: 1: Success after binutils/gdb: 146 commits new 793459b701 336: onsuccess: #2156: 1: Success after binutils/gcc/linux/g [...] new 432e605567 337: onsuccess: #2157: 1: Success after binutils/gcc/glibc/g [...] new c8fe5ef9b1 338: onsuccess: #2158: 1: Success after binutils/gcc/linux/g [...] new e16299c1f8 339: onsuccess: #2159: 1: Success after binutils/gcc/gdb: 4 commits new 59e8098dad 340: onsuccess: #2160: 1: Success after binutils/gcc/gdb: 15 [...] new db52176f88 341: onsuccess: #2161: 1: Success after binutils/gcc/gdb: 11 [...] new 5e1b00b37a 342: onsuccess: #2162: 1: Success after binutils/gcc/linux/g [...] new b9f57894aa 343: onsuccess: #2163: 1: Success after binutils/gcc/gdb: 7 commits new 215016e107 344: onsuccess: #2164: 1: Success after gcc/linux/glibc: 37 commits new 8bb1303802 345: onsuccess: #2165: 1: Success after binutils/gcc/glibc/g [...] new f2809c1e49 346: onsuccess: #2166: 1: Success after binutils/gcc/linux/g [...] new a1c1594b8e 347: onsuccess: #2167: 1: Success after basepoints/gcc-13-51 [...] new 726b5b2e7c 348: onsuccess: #2168: 1: Success after binutils/gcc/gdb: 9 commits new c370aafdf7 349: onsuccess: #2169: 1: Success after binutils/gcc/linux/g [...] new dc9a893eae 350: onsuccess: #2170: 1: Success after binutils/gcc/linux/g [...] new a616b3eb97 351: onsuccess: #2171: 1: Success after gcc/linux: 15 commits new d1e5c28949 352: onsuccess: #2172: 1: Success after binutils/gcc/linux/g [...] new 21634d8b3c 353: onsuccess: #2173: 1: Success after binutils/gcc/gdb: 27 [...] new 23058ddc05 354: onsuccess: #2174: 1: Success after binutils/gcc/linux/g [...] new 3b45afc837 355: onsuccess: #2175: 1: Success after binutils/gcc/linux/g [...] new 53fa614519 356: onsuccess: #2176: 1: Success after binutils/gcc/linux/g [...] new cdb93e7f2c 357: onsuccess: #2177: 1: Success after binutils/gcc/linux/g [...] new 4e0b90a191 358: onsuccess: #2178: 1: Success after binutils/gcc/linux/g [...] new f8ceb12f85 359: onsuccess: #2179: 1: Success after binutils/gcc/glibc/g [...] new fa745d572e 360: onsuccess: #2180: 1: Success after binutils/gcc/linux/g [...] new 9c0986dbf3 361: onsuccess: #2181: 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 (79ec3880fb) \ 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 1764 -> 1808 bytes 02-prepare_abe/console.log.xz | Bin 2776 -> 2764 bytes 03-build_abe-binutils/console.log.xz | Bin 32664 -> 30976 bytes 04-build_abe-stage1/console.log.xz | Bin 93428 -> 91940 bytes 06-build_abe-linux/console.log.xz | Bin 8924 -> 8564 bytes 07-build_abe-glibc/console.log.xz | Bin 236892 -> 236228 bytes 08-build_abe-stage2/console.log.xz | Bin 229504 -> 229412 bytes 09-build_abe-gdb/console.log.xz | Bin 39380 -> 38192 bytes 10-build_abe-qemu/console.log.xz | Bin 31608 -> 31960 bytes 11-build_abe-dejagnu/console.log.xz | Bin 3888 -> 3868 bytes 12-build_abe-check_gcc/console.log.xz | Bin 2760 -> 3024 bytes 13-check_regression/console.log.xz | Bin 7384 -> 7204 bytes 13-check_regression/mail-body.txt | 26 - 13-check_regression/results.compare | 34 +- 13-check_regression/results.compare2 | 86 +- 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 +- git/qemu_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 28 +- mail/mail-subject.txt | 2 +- manifest.sh | 44 +- sumfiles/g++.log.xz | Bin 2687472 -> 2636952 bytes sumfiles/g++.sum | 48 +- sumfiles/gcc.log.xz | Bin 2213592 -> 2213260 bytes sumfiles/gcc.sum | 1937 +++++++++++++++++---------------- sumfiles/gfortran.log.xz | Bin 891808 -> 892124 bytes sumfiles/gfortran.sum | 10 +- sumfiles/libatomic.log.xz | Bin 2260 -> 2260 bytes sumfiles/libatomic.sum | 2 +- sumfiles/libgomp.log.xz | Bin 213904 -> 214252 bytes sumfiles/libgomp.sum | 6 +- sumfiles/libitm.log.xz | Bin 2664 -> 2664 bytes sumfiles/libitm.sum | 2 +- sumfiles/libstdc++.log.xz | Bin 443708 -> 434576 bytes sumfiles/libstdc++.sum | 42 +- 40 files changed, 1144 insertions(+), 1203 deletions(-)