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 c30464c1ac 423: onsuccess: #2247: 1: Success after gcc/linux: 8 commits discards 18b32a2eae 422: onsuccess: #2246: 1: Success after binutils/gcc/linux/g [...] discards 9c094787ae 421: onsuccess: #2245: 1: Success after binutils/gcc/glibc/g [...] discards 0260af5139 420: onsuccess: #2244: 1: Success after gcc/glibc: 5 commits discards a43ea83183 419: onsuccess: #2243: 1: Success after binutils/gcc/linux/g [...] discards 55b4f7c0f6 418: onsuccess: #2239: 1: Success after binutils/gcc/gdb: 5 commits discards 289b4af259 417: onsuccess: #2238: 1: Success after binutils/gcc/linux/g [...] discards 72d27a5b04 416: onsuccess: #2237: 1: Success after binutils/gcc/glibc/g [...] discards d7a52989ed 415: onsuccess: #2236: 1: Success after binutils/gcc/gdb: 14 [...] discards a0fabdffb0 414: onsuccess: #2235: 1: Success after binutils/gcc/gdb: 13 [...] discards 61d03201d6 413: onsuccess: #2234: 1: Success after binutils/gcc/linux/g [...] discards 05b521bda3 412: onsuccess: #2233: 1: Success after binutils/gcc/glibc/g [...] discards 21b266ee91 411: onsuccess: #2232: 1: Success after gcc: 3 commits discards 8e61524e49 410: onsuccess: #2231: 1: Success after binutils/gcc/linux/g [...] discards f04d0b1c5f 409: onsuccess: #2230: 1: Success after binutils/gcc/glibc/g [...] discards 8f243c1936 408: onsuccess: #2229: 1: Success after binutils/gcc/gdb: 26 [...] discards c7bea5bd9e 407: onsuccess: #2228: 1: Success after binutils/gcc/linux/g [...] discards 6686c544bc 406: onsuccess: #2227: 1: Success after binutils/linux/glibc [...] discards 2969a13de1 405: onsuccess: #2226: 1: Success after gcc/glibc: 39 commits discards a84b5311e1 404: onsuccess: #2225: 1: Success after binutils/gcc/gdb: 10 [...] discards 072dee5d81 403: onsuccess: #2224: 1: Success after binutils/gcc/linux/g [...] discards c4d4642073 402: onsuccess: #2223: 1: Success after binutils/gcc/gdb: 10 [...] discards 2be38235ff 401: onsuccess: #2222: 1: Success after binutils/gcc/gdb: 10 [...] discards cbd1c82e3d 400: onsuccess: #2221: 1: Success after binutils/gcc/linux/g [...] discards cc3fbaaedd 399: onsuccess: #2220: 1: Success after binutils/gcc/linux/g [...] discards 5c38447f45 398: onsuccess: #2219: 1: Success after binutils/gcc/gdb/qem [...] discards 180d929fc7 397: onsuccess: #2218: 1: Success after binutils/gcc/linux/g [...] discards 357fb40c14 396: onsuccess: #2217: 1: Success after binutils/gcc/linux/g [...] discards 04efeebfd4 395: onsuccess: #2216: 1: Success after binutils/gcc/linux/g [...] discards e2972879b8 394: onsuccess: #2215: 1: Success after binutils/gcc/gdb: 8 commits discards c17fa89192 393: onsuccess: #2214: 1: Success after binutils/gcc/gdb: 12 [...] discards 24dcf8ef01 392: onsuccess: #2213: 1: Success after binutils/gcc/glibc/g [...] discards 214f627c91 391: onsuccess: #2212: 1: Success after binutils/gcc/gdb/qem [...] discards a132ddc667 390: onsuccess: #2211: 1: Success after binutils/gcc/linux/g [...] discards 52c0146cea 389: onsuccess: #2210: 1: Success after binutils/gcc/linux/g [...] discards ddb04c387c 388: onsuccess: #2209: 1: Success after binutils/gcc/glibc/g [...] discards 85c785af73 387: onsuccess: #2208: 1: Success after gcc: 2 commits discards 0aa80bde40 386: onsuccess: #2207: 1: Success after binutils/gcc/linux/g [...] discards 417222a869 385: onsuccess: #2206: 1: Success after binutils/gcc/glibc/g [...] discards d50fef421d 384: onsuccess: #2205: 1: Success after gcc: 2 commits discards a732679554 383: onsuccess: #2204: 1: Success after binutils/gcc/linux/g [...] discards ba09026320 382: onsuccess: #2203: 1: Success after gcc/qemu: 42 commits discards e1245a177b 381: onsuccess: #2202: 1: Success after glibc-2.37.9000-17-g [...] discards cf39573304 380: onsuccess: #2201: 1: Success after binutils/gcc/linux/g [...] discards 57823d2647 379: onsuccess: #2200: 1: Success after binutils/gcc/linux/g [...] discards eac6cc9f8e 378: onsuccess: #2199: 1: Success after binutils/gdb: 4 commits discards 3059c65c56 377: onsuccess: #2198: 1: Success after binutils/gcc/gdb: 3 commits discards d0bae5395f 376: onsuccess: #2197: 1: Success after binutils/gcc/linux/g [...] discards dbf24ea1ca 375: onsuccess: #2195: 1: Success after binutils/gcc/gdb/qem [...] discards a3e757cd71 374: onsuccess: #2194: 1: Success after binutils/gcc/linux/g [...] discards a295d91c7b 373: onsuccess: #2193: 1: Success after binutils/gcc/glibc/g [...] discards 12a8dfaf91 372: onsuccess: #2192: 1: Success after binutils/gcc/linux/g [...] discards f59158bf8b 371: onsuccess: #2191: 1: Success after binutils/gcc/gdb: 10 [...] discards 26e4872d9b 370: onsuccess: #2190: 1: Success after binutils/gcc/linux/g [...] discards 7aaa0a0556 369: onsuccess: #2189: 1: Success after binutils/gcc/linux/g [...] discards 67c9ed3f4c 368: onsuccess: #2188: 1: Success after binutils/gcc/linux/g [...] discards a90cd72b88 367: onsuccess: #2187: 1: Success after binutils/gcc/gdb: 14 [...] discards 1c35ba2caf 366: onsuccess: #2186: 1: Success after binutils/gcc/linux/g [...] discards bc10f13ce8 365: onsuccess: #2185: 1: Success after binutils/gcc/linux/g [...] discards 558b94e5a3 364: onsuccess: #2184: 1: Success after binutils/gcc/linux/g [...] discards 8f39c53bc1 363: onsuccess: #2183: 1: Success after binutils/gcc/linux/g [...] discards 125494add0 362: onsuccess: #2182: 1: Success after binutils/gcc/linux/g [...] discards 270086e057 361: onsuccess: #2181: 1: Success after binutils/gcc/linux/g [...] discards 44995109f1 360: onsuccess: #2180: 1: Success after binutils/gcc/linux/g [...] discards a611ff72b3 359: onsuccess: #2179: 1: Success after binutils/gcc/glibc/g [...] discards 8fa938d69b 358: onsuccess: #2178: 1: Success after binutils/gcc/linux/g [...] discards b60d2fda2b 357: onsuccess: #2177: 1: Success after binutils/gcc/linux/g [...] discards 64181f75b1 356: onsuccess: #2176: 1: Success after binutils/gcc/linux/g [...] discards d9c3d4489a 355: onsuccess: #2175: 1: Success after binutils/gcc/linux/g [...] discards 84beba3168 354: onsuccess: #2174: 1: Success after binutils/gcc/linux/g [...] discards ae66052c26 353: onsuccess: #2173: 1: Success after binutils/gcc/gdb: 27 [...] discards 4ee388a376 352: onsuccess: #2172: 1: Success after binutils/gcc/linux/g [...] discards b7777f3990 351: onsuccess: #2171: 1: Success after gcc/linux: 15 commits discards cae530f5cb 350: onsuccess: #2170: 1: Success after binutils/gcc/linux/g [...] discards ee54b0f2af 349: onsuccess: #2169: 1: Success after binutils/gcc/linux/g [...] discards 52e4f1f257 348: onsuccess: #2168: 1: Success after binutils/gcc/gdb: 9 commits discards 43cab14ef4 347: onsuccess: #2167: 1: Success after basepoints/gcc-13-51 [...] discards 7e90a4fc26 346: onsuccess: #2166: 1: Success after binutils/gcc/linux/g [...] discards 3b545b8f73 345: onsuccess: #2165: 1: Success after binutils/gcc/glibc/g [...] discards 593999f2cc 344: onsuccess: #2164: 1: Success after gcc/linux/glibc: 37 commits discards 26951b6c5b 343: onsuccess: #2163: 1: Success after binutils/gcc/gdb: 7 commits discards fae56356d8 342: onsuccess: #2162: 1: Success after binutils/gcc/linux/g [...] discards dbf2cb0cf1 341: onsuccess: #2161: 1: Success after binutils/gcc/gdb: 11 [...] discards b86d537283 340: onsuccess: #2160: 1: Success after binutils/gcc/gdb: 15 [...] discards 542f87335a 339: onsuccess: #2159: 1: Success after binutils/gcc/gdb: 4 commits discards 99290eb2f7 338: onsuccess: #2158: 1: Success after binutils/gcc/linux/g [...] discards ee5eec3d90 337: onsuccess: #2157: 1: Success after binutils/gcc/glibc/g [...] discards fd825d4ce1 336: onsuccess: #2156: 1: Success after binutils/gcc/linux/g [...] discards c70e2e5f2f 335: onsuccess: #2155: 1: Success after binutils/gdb: 146 commits discards 9d212e178c 334: onsuccess: #2154: 1: Success after binutils/gcc/linux/g [...] discards 5531fa081e 333: onsuccess: #2153: 1: Success after binutils/gcc/gdb/qem [...] discards 84d0762c22 332: onsuccess: #2152: 1: Success after binutils/gcc/gdb/qem [...] discards 5b38ad7844 331: onsuccess: #2151: 1: Success after binutils/gcc/linux/g [...] discards 08b906abe2 330: onsuccess: #2150: 1: Success after linux/qemu: 36 commits discards 43434fa445 329: onsuccess: #2149: 1: Success after binutils/gcc/gdb/qem [...] discards 6c9a6a98c1 328: onsuccess: #2148: 1: Success after gcc/linux/qemu: 78 commits discards ab34105c35 327: onsuccess: #2147: 1: Success after basepoints/gcc-13-50 [...] discards aab7b0a544 326: onsuccess: #2146: 1: Success after binutils/gcc/linux/g [...] discards 0d80668a09 325: onsuccess: #2145: 1: Success after binutils/gcc/glibc/g [...] discards de119468d0 324: onsuccess: #2144: 1: Success after binutils/gcc/gdb/qem [...] discards 330bfd8aee 323: onsuccess: #2143: 1: Success after basepoints/gcc-13-50 [...] new 905b76b802 323: onsuccess: #2143: 1: Success after basepoints/gcc-13-50 [...] new 64e1a40072 324: onsuccess: #2144: 1: Success after binutils/gcc/gdb/qem [...] new c1ed945d38 325: onsuccess: #2145: 1: Success after binutils/gcc/glibc/g [...] new 060b9a8770 326: onsuccess: #2146: 1: Success after binutils/gcc/linux/g [...] new 7e895c7292 327: onsuccess: #2147: 1: Success after basepoints/gcc-13-50 [...] new 0c0495cb3c 328: onsuccess: #2148: 1: Success after gcc/linux/qemu: 78 commits new b5e9312f62 329: onsuccess: #2149: 1: Success after binutils/gcc/gdb/qem [...] new af51cce7fe 330: onsuccess: #2150: 1: Success after linux/qemu: 36 commits new b9f140ae30 331: onsuccess: #2151: 1: Success after binutils/gcc/linux/g [...] new 7ca406c7da 332: onsuccess: #2152: 1: Success after binutils/gcc/gdb/qem [...] new 9eb0be03fb 333: onsuccess: #2153: 1: Success after binutils/gcc/gdb/qem [...] new da69099a6e 334: onsuccess: #2154: 1: Success after binutils/gcc/linux/g [...] new 4e2ca812da 335: onsuccess: #2155: 1: Success after binutils/gdb: 146 commits new 382ee61bf5 336: onsuccess: #2156: 1: Success after binutils/gcc/linux/g [...] new a3c9f909e5 337: onsuccess: #2157: 1: Success after binutils/gcc/glibc/g [...] new f7359fc310 338: onsuccess: #2158: 1: Success after binutils/gcc/linux/g [...] new 89af15edb8 339: onsuccess: #2159: 1: Success after binutils/gcc/gdb: 4 commits new 984c6b2bb0 340: onsuccess: #2160: 1: Success after binutils/gcc/gdb: 15 [...] new f4b46e6b77 341: onsuccess: #2161: 1: Success after binutils/gcc/gdb: 11 [...] new 764ca283e9 342: onsuccess: #2162: 1: Success after binutils/gcc/linux/g [...] new c1c57cd32c 343: onsuccess: #2163: 1: Success after binutils/gcc/gdb: 7 commits new 00a10096c0 344: onsuccess: #2164: 1: Success after gcc/linux/glibc: 37 commits new f3e821edd1 345: onsuccess: #2165: 1: Success after binutils/gcc/glibc/g [...] new 078b56b01d 346: onsuccess: #2166: 1: Success after binutils/gcc/linux/g [...] new 641f1c2f66 347: onsuccess: #2167: 1: Success after basepoints/gcc-13-51 [...] new ff2fa29e2a 348: onsuccess: #2168: 1: Success after binutils/gcc/gdb: 9 commits new 4de10e42e9 349: onsuccess: #2169: 1: Success after binutils/gcc/linux/g [...] new 0bba164d0c 350: onsuccess: #2170: 1: Success after binutils/gcc/linux/g [...] new a212173448 351: onsuccess: #2171: 1: Success after gcc/linux: 15 commits new 2ac05b8bdb 352: onsuccess: #2172: 1: Success after binutils/gcc/linux/g [...] new b36d28e420 353: onsuccess: #2173: 1: Success after binutils/gcc/gdb: 27 [...] new 5af6fe8a11 354: onsuccess: #2174: 1: Success after binutils/gcc/linux/g [...] new 903b26a5d0 355: onsuccess: #2175: 1: Success after binutils/gcc/linux/g [...] new a4dc00e2ed 356: onsuccess: #2176: 1: Success after binutils/gcc/linux/g [...] new a4091c92b5 357: onsuccess: #2177: 1: Success after binutils/gcc/linux/g [...] new 9763145da0 358: onsuccess: #2178: 1: Success after binutils/gcc/linux/g [...] new b6a12b423e 359: onsuccess: #2179: 1: Success after binutils/gcc/glibc/g [...] new f2c1e2321e 360: onsuccess: #2180: 1: Success after binutils/gcc/linux/g [...] new 596c59f14a 361: onsuccess: #2181: 1: Success after binutils/gcc/linux/g [...] new 3eb667295d 362: onsuccess: #2182: 1: Success after binutils/gcc/linux/g [...] new 3d5c2a70c4 363: onsuccess: #2183: 1: Success after binutils/gcc/linux/g [...] new a1ffa8b1db 364: onsuccess: #2184: 1: Success after binutils/gcc/linux/g [...] new 819b8d9ed8 365: onsuccess: #2185: 1: Success after binutils/gcc/linux/g [...] new f056f80b6d 366: onsuccess: #2186: 1: Success after binutils/gcc/linux/g [...] new b8ae3d6b30 367: onsuccess: #2187: 1: Success after binutils/gcc/gdb: 14 [...] new fb2947dda8 368: onsuccess: #2188: 1: Success after binutils/gcc/linux/g [...] new 2bedb599f4 369: onsuccess: #2189: 1: Success after binutils/gcc/linux/g [...] new 3d1000a218 370: onsuccess: #2190: 1: Success after binutils/gcc/linux/g [...] new d4e80de6cd 371: onsuccess: #2191: 1: Success after binutils/gcc/gdb: 10 [...] new 323ddb73a4 372: onsuccess: #2192: 1: Success after binutils/gcc/linux/g [...] new 6cde27a9b4 373: onsuccess: #2193: 1: Success after binutils/gcc/glibc/g [...] new 46e609cc74 374: onsuccess: #2194: 1: Success after binutils/gcc/linux/g [...] new 40f4d100be 375: onsuccess: #2195: 1: Success after binutils/gcc/gdb/qem [...] new 5e10f0ffa2 376: onsuccess: #2197: 1: Success after binutils/gcc/linux/g [...] new a4a356a39c 377: onsuccess: #2198: 1: Success after binutils/gcc/gdb: 3 commits new 8ee0c0ef47 378: onsuccess: #2199: 1: Success after binutils/gdb: 4 commits new 9c9cd030b6 379: onsuccess: #2200: 1: Success after binutils/gcc/linux/g [...] new 8507156890 380: onsuccess: #2201: 1: Success after binutils/gcc/linux/g [...] new ce74eff733 381: onsuccess: #2202: 1: Success after glibc-2.37.9000-17-g [...] new a820b0f42f 382: onsuccess: #2203: 1: Success after gcc/qemu: 42 commits new 39899d527a 383: onsuccess: #2204: 1: Success after binutils/gcc/linux/g [...] new 1d32976ac8 384: onsuccess: #2205: 1: Success after gcc: 2 commits new cea935a0a8 385: onsuccess: #2206: 1: Success after binutils/gcc/glibc/g [...] new 98e7e46caf 386: onsuccess: #2207: 1: Success after binutils/gcc/linux/g [...] new b30ddba791 387: onsuccess: #2208: 1: Success after gcc: 2 commits new bc60716d34 388: onsuccess: #2209: 1: Success after binutils/gcc/glibc/g [...] new 02d8ad7c38 389: onsuccess: #2210: 1: Success after binutils/gcc/linux/g [...] new e6aeb4b611 390: onsuccess: #2211: 1: Success after binutils/gcc/linux/g [...] new 418ea6cb6c 391: onsuccess: #2212: 1: Success after binutils/gcc/gdb/qem [...] new cb0a4f9bc1 392: onsuccess: #2213: 1: Success after binutils/gcc/glibc/g [...] new 0ac880b344 393: onsuccess: #2214: 1: Success after binutils/gcc/gdb: 12 [...] new 9e1e71a28f 394: onsuccess: #2215: 1: Success after binutils/gcc/gdb: 8 commits new e5fe39b22e 395: onsuccess: #2216: 1: Success after binutils/gcc/linux/g [...] new 8dee548d60 396: onsuccess: #2217: 1: Success after binutils/gcc/linux/g [...] new e91ecb298e 397: onsuccess: #2218: 1: Success after binutils/gcc/linux/g [...] new ee5448abf8 398: onsuccess: #2219: 1: Success after binutils/gcc/gdb/qem [...] new a322d9bb94 399: onsuccess: #2220: 1: Success after binutils/gcc/linux/g [...] new e7189193ae 400: onsuccess: #2221: 1: Success after binutils/gcc/linux/g [...] new 74f1ed7ae8 401: onsuccess: #2222: 1: Success after binutils/gcc/gdb: 10 [...] new df15115940 402: onsuccess: #2223: 1: Success after binutils/gcc/gdb: 10 [...] new 2c9881b7cd 403: onsuccess: #2224: 1: Success after binutils/gcc/linux/g [...] new 7dc487011c 404: onsuccess: #2225: 1: Success after binutils/gcc/gdb: 10 [...] new 47f1776e5b 405: onsuccess: #2226: 1: Success after gcc/glibc: 39 commits new ab9b423ce6 406: onsuccess: #2227: 1: Success after binutils/linux/glibc [...] new c2517c0fce 407: onsuccess: #2228: 1: Success after binutils/gcc/linux/g [...] new f2f6366d8a 408: onsuccess: #2229: 1: Success after binutils/gcc/gdb: 26 [...] new 76c14c0819 409: onsuccess: #2230: 1: Success after binutils/gcc/glibc/g [...] new 8bb8d1acb6 410: onsuccess: #2231: 1: Success after binutils/gcc/linux/g [...] new f6adf29adc 411: onsuccess: #2232: 1: Success after gcc: 3 commits new 13cd2eb188 412: onsuccess: #2233: 1: Success after binutils/gcc/glibc/g [...] new 7a3753ba43 413: onsuccess: #2234: 1: Success after binutils/gcc/linux/g [...] new 3fe298acc6 414: onsuccess: #2235: 1: Success after binutils/gcc/gdb: 13 [...] new 943ba40e7a 415: onsuccess: #2236: 1: Success after binutils/gcc/gdb: 14 [...] new b5db90b142 416: onsuccess: #2237: 1: Success after binutils/gcc/glibc/g [...] new ddeb7e9d32 417: onsuccess: #2238: 1: Success after binutils/gcc/linux/g [...] new 79a9337f30 418: onsuccess: #2239: 1: Success after binutils/gcc/gdb: 5 commits new 77631c4723 419: onsuccess: #2243: 1: Success after binutils/gcc/linux/g [...] new 688f55b878 420: onsuccess: #2244: 1: Success after gcc/glibc: 5 commits new bd027a4df4 421: onsuccess: #2245: 1: Success after binutils/gcc/glibc/g [...] new 0d9606d111 422: onsuccess: #2246: 1: Success after binutils/gcc/linux/g [...] new f361da03b7 423: onsuccess: #2247: 1: Success after gcc/linux: 8 commits new 4ce9722951 424: onsuccess: #2248: 1: Success after gcc: 6 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 (c30464c1ac) \ 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 -> 1744 bytes 02-prepare_abe/console.log.xz | Bin 2756 -> 2764 bytes 03-build_abe-binutils/console.log.xz | Bin 30720 -> 30812 bytes 04-build_abe-stage1/console.log.xz | Bin 89584 -> 88664 bytes 06-build_abe-linux/console.log.xz | Bin 8664 -> 8688 bytes 07-build_abe-glibc/console.log.xz | Bin 235544 -> 235608 bytes 08-build_abe-stage2/console.log.xz | Bin 225832 -> 225568 bytes 09-build_abe-gdb/console.log.xz | Bin 38612 -> 38564 bytes 10-build_abe-qemu/console.log.xz | Bin 31352 -> 31064 bytes 11-build_abe-dejagnu/console.log.xz | Bin 3800 -> 3804 bytes 12-build_abe-check_gcc/console.log.xz | Bin 3272 -> 3000 bytes 13-check_regression/console.log.xz | Bin 5476 -> 5436 bytes 13-check_regression/results.compare | 16 ++++----- 13-check_regression/results.compare2 | 47 +++++++++++++++--------- 14-update_baseline/console.log | 66 +++++++++++++++++----------------- dashboard/dashboard-generate.sh | 2 +- git/gcc_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 2 +- mail/mail-subject.txt | 2 +- manifest.sh | 24 ++++++------- sumfiles/g++.log.xz | Bin 2672356 -> 2635752 bytes sumfiles/gcc.log.xz | Bin 2202868 -> 2219068 bytes sumfiles/gcc.sum | 9 ++++- sumfiles/gfortran.log.xz | Bin 896992 -> 893748 bytes sumfiles/libatomic.log.xz | Bin 2260 -> 2268 bytes sumfiles/libatomic.sum | 2 +- sumfiles/libgomp.log.xz | Bin 217024 -> 217028 bytes sumfiles/libgomp.sum | 2 +- sumfiles/libitm.log.xz | Bin 2664 -> 2664 bytes sumfiles/libitm.sum | 2 +- sumfiles/libstdc++.log.xz | Bin 443108 -> 435540 bytes sumfiles/libstdc++.sum | 28 +++++---------- 33 files changed, 108 insertions(+), 98 deletions(-)