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 f9d08db32f 401: onsuccess: #2222: 1: Success after binutils/gcc/gdb: 10 [...] discards 6db31ac8cb 400: onsuccess: #2221: 1: Success after binutils/gcc/linux/g [...] discards 10b45ba136 399: onsuccess: #2220: 1: Success after binutils/gcc/linux/g [...] discards 07d3cc149d 398: onsuccess: #2219: 1: Success after binutils/gcc/gdb/qem [...] discards 5be34860ae 397: onsuccess: #2218: 1: Success after binutils/gcc/linux/g [...] discards 847218eb42 396: onsuccess: #2217: 1: Success after binutils/gcc/linux/g [...] discards 7740306d8d 395: onsuccess: #2216: 1: Success after binutils/gcc/linux/g [...] discards 1b74efcc73 394: onsuccess: #2215: 1: Success after binutils/gcc/gdb: 8 commits discards 4d1f24dff6 393: onsuccess: #2214: 1: Success after binutils/gcc/gdb: 12 [...] discards 362b531089 392: onsuccess: #2213: 1: Success after binutils/gcc/glibc/g [...] discards 63ed5dd5c9 391: onsuccess: #2212: 1: Success after binutils/gcc/gdb/qem [...] discards e75d6b04e9 390: onsuccess: #2211: 1: Success after binutils/gcc/linux/g [...] discards bde1dd38d1 389: onsuccess: #2210: 1: Success after binutils/gcc/linux/g [...] discards b2ba1032cf 388: onsuccess: #2209: 1: Success after binutils/gcc/glibc/g [...] discards b3e88f0c73 387: onsuccess: #2208: 1: Success after gcc: 2 commits discards fb6e9b1ed4 386: onsuccess: #2207: 1: Success after binutils/gcc/linux/g [...] discards 69a8e3a0c7 385: onsuccess: #2206: 1: Success after binutils/gcc/glibc/g [...] discards 6ba8cf8d74 384: onsuccess: #2205: 1: Success after gcc: 2 commits discards 0f06c36570 383: onsuccess: #2204: 1: Success after binutils/gcc/linux/g [...] discards 02f82bbf15 382: onsuccess: #2203: 1: Success after gcc/qemu: 42 commits discards 33e6e61055 381: onsuccess: #2202: 1: Success after glibc-2.37.9000-17-g [...] discards 058b4d7e92 380: onsuccess: #2201: 1: Success after binutils/gcc/linux/g [...] discards b45b181a22 379: onsuccess: #2200: 1: Success after binutils/gcc/linux/g [...] discards 75e42f1a19 378: onsuccess: #2199: 1: Success after binutils/gdb: 4 commits discards b984179c27 377: onsuccess: #2198: 1: Success after binutils/gcc/gdb: 3 commits discards c8e19fa665 376: onsuccess: #2197: 1: Success after binutils/gcc/linux/g [...] discards 8f8ccc3ea2 375: onsuccess: #2195: 1: Success after binutils/gcc/gdb/qem [...] discards e6615d460d 374: onsuccess: #2194: 1: Success after binutils/gcc/linux/g [...] discards 80947b1f93 373: onsuccess: #2193: 1: Success after binutils/gcc/glibc/g [...] discards 7556a39bc2 372: onsuccess: #2192: 1: Success after binutils/gcc/linux/g [...] discards 334d5ea8ac 371: onsuccess: #2191: 1: Success after binutils/gcc/gdb: 10 [...] discards 7c87c86442 370: onsuccess: #2190: 1: Success after binutils/gcc/linux/g [...] discards 877c197a66 369: onsuccess: #2189: 1: Success after binutils/gcc/linux/g [...] discards 603f2f2ce5 368: onsuccess: #2188: 1: Success after binutils/gcc/linux/g [...] discards d5e2397407 367: onsuccess: #2187: 1: Success after binutils/gcc/gdb: 14 [...] discards bd1d573fb6 366: onsuccess: #2186: 1: Success after binutils/gcc/linux/g [...] discards 3c46bb665f 365: onsuccess: #2185: 1: Success after binutils/gcc/linux/g [...] discards b5036c4368 364: onsuccess: #2184: 1: Success after binutils/gcc/linux/g [...] discards f37c2f63de 363: onsuccess: #2183: 1: Success after binutils/gcc/linux/g [...] discards 2448e39848 362: onsuccess: #2182: 1: Success after binutils/gcc/linux/g [...] discards 93cfac5e8d 361: onsuccess: #2181: 1: Success after binutils/gcc/linux/g [...] discards c950f9a14a 360: onsuccess: #2180: 1: Success after binutils/gcc/linux/g [...] discards 0e0cb01d49 359: onsuccess: #2179: 1: Success after binutils/gcc/glibc/g [...] discards 471a46cf6f 358: onsuccess: #2178: 1: Success after binutils/gcc/linux/g [...] discards 1cfc6770d3 357: onsuccess: #2177: 1: Success after binutils/gcc/linux/g [...] discards b4e86010db 356: onsuccess: #2176: 1: Success after binutils/gcc/linux/g [...] discards 5f4493111f 355: onsuccess: #2175: 1: Success after binutils/gcc/linux/g [...] discards ac8b8741a3 354: onsuccess: #2174: 1: Success after binutils/gcc/linux/g [...] discards 8a67a7d2bf 353: onsuccess: #2173: 1: Success after binutils/gcc/gdb: 27 [...] discards b2b3cdf853 352: onsuccess: #2172: 1: Success after binutils/gcc/linux/g [...] discards 05f346151a 351: onsuccess: #2171: 1: Success after gcc/linux: 15 commits discards 4c65ff4d3d 350: onsuccess: #2170: 1: Success after binutils/gcc/linux/g [...] discards 10a10f04dc 349: onsuccess: #2169: 1: Success after binutils/gcc/linux/g [...] discards c5565a64f9 348: onsuccess: #2168: 1: Success after binutils/gcc/gdb: 9 commits discards 4dd5277e5b 347: onsuccess: #2167: 1: Success after basepoints/gcc-13-51 [...] discards 543f253a80 346: onsuccess: #2166: 1: Success after binutils/gcc/linux/g [...] discards e875973e91 345: onsuccess: #2165: 1: Success after binutils/gcc/glibc/g [...] discards 905f794c7c 344: onsuccess: #2164: 1: Success after gcc/linux/glibc: 37 commits discards 3a3de64bf5 343: onsuccess: #2163: 1: Success after binutils/gcc/gdb: 7 commits discards c9f0941737 342: onsuccess: #2162: 1: Success after binutils/gcc/linux/g [...] discards 38216abecf 341: onsuccess: #2161: 1: Success after binutils/gcc/gdb: 11 [...] discards 89bf080abc 340: onsuccess: #2160: 1: Success after binutils/gcc/gdb: 15 [...] discards 6c2a50619d 339: onsuccess: #2159: 1: Success after binutils/gcc/gdb: 4 commits discards 03a6a42ab1 338: onsuccess: #2158: 1: Success after binutils/gcc/linux/g [...] discards e4eae75d0f 337: onsuccess: #2157: 1: Success after binutils/gcc/glibc/g [...] discards c127bfcd7f 336: onsuccess: #2156: 1: Success after binutils/gcc/linux/g [...] discards e77183d773 335: onsuccess: #2155: 1: Success after binutils/gdb: 146 commits discards 94ada4ee3f 334: onsuccess: #2154: 1: Success after binutils/gcc/linux/g [...] discards 1b3d258880 333: onsuccess: #2153: 1: Success after binutils/gcc/gdb/qem [...] discards 9eaca46cd6 332: onsuccess: #2152: 1: Success after binutils/gcc/gdb/qem [...] discards 82af91c9fa 331: onsuccess: #2151: 1: Success after binutils/gcc/linux/g [...] discards ecc9ec7041 330: onsuccess: #2150: 1: Success after linux/qemu: 36 commits discards 490e340270 329: onsuccess: #2149: 1: Success after binutils/gcc/gdb/qem [...] discards 9ac8986940 328: onsuccess: #2148: 1: Success after gcc/linux/qemu: 78 commits discards 86baaa0fbc 327: onsuccess: #2147: 1: Success after basepoints/gcc-13-50 [...] discards b6fc63f452 326: onsuccess: #2146: 1: Success after binutils/gcc/linux/g [...] discards 556eebe40b 325: onsuccess: #2145: 1: Success after binutils/gcc/glibc/g [...] discards 4ba5bacc9c 324: onsuccess: #2144: 1: Success after binutils/gcc/gdb/qem [...] discards b9ae571470 323: onsuccess: #2143: 1: Success after basepoints/gcc-13-50 [...] discards 4fcd049065 322: onsuccess: #2142: 1: Success after binutils/gcc/linux/g [...] discards 548fbd8e7e 321: onsuccess: #2141: 1: Success after binutils/gcc/linux/g [...] discards ba054116a5 320: onsuccess: #2140: 1: Success after binutils/gcc/gdb: 6 commits discards 6384730c85 319: onsuccess: #2139: 1: Success after binutils/gcc/gdb: 11 [...] discards 7fdafefdb8 318: onsuccess: #2138: 1: Success after binutils/gcc/linux/g [...] discards fa0bf5ce39 317: onsuccess: #2137: 1: Success after binutils/gcc/linux/g [...] discards c0a0ca2c10 316: onsuccess: #2136: 1: Success after binutils/gcc/gdb: 26 [...] discards 7a502cfd5d 315: onsuccess: #2135: 1: Success after binutils/gcc/gdb: 11 [...] discards e49a95df5f 314: onsuccess: #2134: 1: Success after binutils/gcc/glibc/g [...] discards 4f49043abd 313: onsuccess: #2133: 1: Success after binutils/gcc/linux/g [...] discards a3ef1c33c8 312: onsuccess: #2132: 1: Success after glibc-2.36.9000-416- [...] discards 4ab63c3883 311: onsuccess: #2130: 1: Success after gcc: 4 commits discards 82e6cd1660 310: onsuccess: #2129: 1: Success after binutils: 4 commits discards 43fbfbeb20 309: onsuccess: #2127: 1: Success after binutils/gcc/glibc/g [...] discards 45b0ffc5b5 308: onsuccess: #2126: 1: Success after binutils/gcc/linux/g [...] discards e478b3e9e8 307: onsuccess: #2124: 1: Success after gcc: 2 commits discards 5e913be280 306: onsuccess: #2123: 1: Success after binutils/gcc/gdb: 15 [...] discards 3b99ad3f29 305: onsuccess: #2122: 1: Success after binutils/gcc/gdb: 4 commits discards 6d9571027c 304: onsuccess: #2121: 1: Success after gcc/linux: 13 commits discards b99bfb77c0 303: onsuccess: #2120: 1: Success after binutils/gdb: 20 commits discards 1f9fa48c46 302: onsuccess: #2119: 1: Success after binutils/gdb: 7 commits discards 883dbeeffb 301: onsuccess: #2118: 1: Success after linux: 16 commits new 7190953111 301: onsuccess: #2118: 1: Success after linux: 16 commits new 65a30d976f 302: onsuccess: #2119: 1: Success after binutils/gdb: 7 commits new b281c93bbc 303: onsuccess: #2120: 1: Success after binutils/gdb: 20 commits new cfabbd56b1 304: onsuccess: #2121: 1: Success after gcc/linux: 13 commits new 702a78e81d 305: onsuccess: #2122: 1: Success after binutils/gcc/gdb: 4 commits new c2b3e32c00 306: onsuccess: #2123: 1: Success after binutils/gcc/gdb: 15 [...] new 2914af2698 307: onsuccess: #2124: 1: Success after gcc: 2 commits new 874ac88b5d 308: onsuccess: #2126: 1: Success after binutils/gcc/linux/g [...] new 72b39b6c8a 309: onsuccess: #2127: 1: Success after binutils/gcc/glibc/g [...] new cc38b93833 310: onsuccess: #2129: 1: Success after binutils: 4 commits new 46854e63d1 311: onsuccess: #2130: 1: Success after gcc: 4 commits new 6cdeb91b58 312: onsuccess: #2132: 1: Success after glibc-2.36.9000-416- [...] new 23a3dbda90 313: onsuccess: #2133: 1: Success after binutils/gcc/linux/g [...] new 2e8d5bdb20 314: onsuccess: #2134: 1: Success after binutils/gcc/glibc/g [...] new 6ca7d02c56 315: onsuccess: #2135: 1: Success after binutils/gcc/gdb: 11 [...] new 17b4d9d1a8 316: onsuccess: #2136: 1: Success after binutils/gcc/gdb: 26 [...] new dde06dcaf2 317: onsuccess: #2137: 1: Success after binutils/gcc/linux/g [...] new 283d756f44 318: onsuccess: #2138: 1: Success after binutils/gcc/linux/g [...] new d566aad47d 319: onsuccess: #2139: 1: Success after binutils/gcc/gdb: 11 [...] new 69abcf57be 320: onsuccess: #2140: 1: Success after binutils/gcc/gdb: 6 commits new 776b256544 321: onsuccess: #2141: 1: Success after binutils/gcc/linux/g [...] new a317e8dd71 322: onsuccess: #2142: 1: Success after binutils/gcc/linux/g [...] new 821bd8efa1 323: onsuccess: #2143: 1: Success after basepoints/gcc-13-50 [...] new b3823f2595 324: onsuccess: #2144: 1: Success after binutils/gcc/gdb/qem [...] new 312cc00e82 325: onsuccess: #2145: 1: Success after binutils/gcc/glibc/g [...] new 906ae77951 326: onsuccess: #2146: 1: Success after binutils/gcc/linux/g [...] new 856641fcef 327: onsuccess: #2147: 1: Success after basepoints/gcc-13-50 [...] new c0479dfc06 328: onsuccess: #2148: 1: Success after gcc/linux/qemu: 78 commits new d07207250c 329: onsuccess: #2149: 1: Success after binutils/gcc/gdb/qem [...] new bf415be353 330: onsuccess: #2150: 1: Success after linux/qemu: 36 commits new fde3049be4 331: onsuccess: #2151: 1: Success after binutils/gcc/linux/g [...] new 39a6636db2 332: onsuccess: #2152: 1: Success after binutils/gcc/gdb/qem [...] new fc38989d05 333: onsuccess: #2153: 1: Success after binutils/gcc/gdb/qem [...] new a17b3f5a35 334: onsuccess: #2154: 1: Success after binutils/gcc/linux/g [...] new 1836070e58 335: onsuccess: #2155: 1: Success after binutils/gdb: 146 commits new 27dbd23bdc 336: onsuccess: #2156: 1: Success after binutils/gcc/linux/g [...] new 5440cb5590 337: onsuccess: #2157: 1: Success after binutils/gcc/glibc/g [...] new 4a89af0be7 338: onsuccess: #2158: 1: Success after binutils/gcc/linux/g [...] new 6b57f3d1f2 339: onsuccess: #2159: 1: Success after binutils/gcc/gdb: 4 commits new bb616ad66e 340: onsuccess: #2160: 1: Success after binutils/gcc/gdb: 15 [...] new e0cfa45bb8 341: onsuccess: #2161: 1: Success after binutils/gcc/gdb: 11 [...] new b9e011d636 342: onsuccess: #2162: 1: Success after binutils/gcc/linux/g [...] new fbeeb822dd 343: onsuccess: #2163: 1: Success after binutils/gcc/gdb: 7 commits new 48f9da01d6 344: onsuccess: #2164: 1: Success after gcc/linux/glibc: 37 commits new 7a7c8e56a7 345: onsuccess: #2165: 1: Success after binutils/gcc/glibc/g [...] new 05e92e2a06 346: onsuccess: #2166: 1: Success after binutils/gcc/linux/g [...] new babbc3fbca 347: onsuccess: #2167: 1: Success after basepoints/gcc-13-51 [...] new 93f8241a5d 348: onsuccess: #2168: 1: Success after binutils/gcc/gdb: 9 commits new 05a26acad4 349: onsuccess: #2169: 1: Success after binutils/gcc/linux/g [...] new 32564940cd 350: onsuccess: #2170: 1: Success after binutils/gcc/linux/g [...] new 6e447b4a0b 351: onsuccess: #2171: 1: Success after gcc/linux: 15 commits new 8524eeab49 352: onsuccess: #2172: 1: Success after binutils/gcc/linux/g [...] new c7975b0098 353: onsuccess: #2173: 1: Success after binutils/gcc/gdb: 27 [...] new 723cebb09c 354: onsuccess: #2174: 1: Success after binutils/gcc/linux/g [...] new a323bd8826 355: onsuccess: #2175: 1: Success after binutils/gcc/linux/g [...] new ed52f5f2c8 356: onsuccess: #2176: 1: Success after binutils/gcc/linux/g [...] new 18e007267c 357: onsuccess: #2177: 1: Success after binutils/gcc/linux/g [...] new f6e3fc81ab 358: onsuccess: #2178: 1: Success after binutils/gcc/linux/g [...] new 434915d084 359: onsuccess: #2179: 1: Success after binutils/gcc/glibc/g [...] new 3a35c7e361 360: onsuccess: #2180: 1: Success after binutils/gcc/linux/g [...] new d744339096 361: onsuccess: #2181: 1: Success after binutils/gcc/linux/g [...] new 4b5da78bf9 362: onsuccess: #2182: 1: Success after binutils/gcc/linux/g [...] new 8e4f435964 363: onsuccess: #2183: 1: Success after binutils/gcc/linux/g [...] new 93dff1ae58 364: onsuccess: #2184: 1: Success after binutils/gcc/linux/g [...] new 3cb08a5dce 365: onsuccess: #2185: 1: Success after binutils/gcc/linux/g [...] new 21c05e6fe0 366: onsuccess: #2186: 1: Success after binutils/gcc/linux/g [...] new f225a67d1f 367: onsuccess: #2187: 1: Success after binutils/gcc/gdb: 14 [...] new a0741f1110 368: onsuccess: #2188: 1: Success after binutils/gcc/linux/g [...] new e40f33023c 369: onsuccess: #2189: 1: Success after binutils/gcc/linux/g [...] new df9b31e1e6 370: onsuccess: #2190: 1: Success after binutils/gcc/linux/g [...] new b66d38abda 371: onsuccess: #2191: 1: Success after binutils/gcc/gdb: 10 [...] new fb7c57e96f 372: onsuccess: #2192: 1: Success after binutils/gcc/linux/g [...] new c5824f9375 373: onsuccess: #2193: 1: Success after binutils/gcc/glibc/g [...] new 4a32ef7bc7 374: onsuccess: #2194: 1: Success after binutils/gcc/linux/g [...] new e5548f3e52 375: onsuccess: #2195: 1: Success after binutils/gcc/gdb/qem [...] new 47acdad76e 376: onsuccess: #2197: 1: Success after binutils/gcc/linux/g [...] new f6b90eaa82 377: onsuccess: #2198: 1: Success after binutils/gcc/gdb: 3 commits new f76c9ce120 378: onsuccess: #2199: 1: Success after binutils/gdb: 4 commits new 1d8a5c2e70 379: onsuccess: #2200: 1: Success after binutils/gcc/linux/g [...] new c458998721 380: onsuccess: #2201: 1: Success after binutils/gcc/linux/g [...] new 0d9c57ca1e 381: onsuccess: #2202: 1: Success after glibc-2.37.9000-17-g [...] new 0114ffdd8d 382: onsuccess: #2203: 1: Success after gcc/qemu: 42 commits new 2a5c124204 383: onsuccess: #2204: 1: Success after binutils/gcc/linux/g [...] new 771451b59d 384: onsuccess: #2205: 1: Success after gcc: 2 commits new 160539f592 385: onsuccess: #2206: 1: Success after binutils/gcc/glibc/g [...] new b9dbd0f28c 386: onsuccess: #2207: 1: Success after binutils/gcc/linux/g [...] new db067f62bc 387: onsuccess: #2208: 1: Success after gcc: 2 commits new beedb21874 388: onsuccess: #2209: 1: Success after binutils/gcc/glibc/g [...] new b3598513e2 389: onsuccess: #2210: 1: Success after binutils/gcc/linux/g [...] new 167a60c234 390: onsuccess: #2211: 1: Success after binutils/gcc/linux/g [...] new 26915e5a23 391: onsuccess: #2212: 1: Success after binutils/gcc/gdb/qem [...] new 7f82085320 392: onsuccess: #2213: 1: Success after binutils/gcc/glibc/g [...] new 235a5ed6e4 393: onsuccess: #2214: 1: Success after binutils/gcc/gdb: 12 [...] new 151c0c2674 394: onsuccess: #2215: 1: Success after binutils/gcc/gdb: 8 commits new 73ef6d35a1 395: onsuccess: #2216: 1: Success after binutils/gcc/linux/g [...] new c7ccda5757 396: onsuccess: #2217: 1: Success after binutils/gcc/linux/g [...] new 11a838da0c 397: onsuccess: #2218: 1: Success after binutils/gcc/linux/g [...] new 6a9d47c77f 398: onsuccess: #2219: 1: Success after binutils/gcc/gdb/qem [...] new 08c5b03a9b 399: onsuccess: #2220: 1: Success after binutils/gcc/linux/g [...] new b78d317e17 400: onsuccess: #2221: 1: Success after binutils/gcc/linux/g [...] new d1b5dc062d 401: onsuccess: #2222: 1: Success after binutils/gcc/gdb: 10 [...] new 9989ee8697 402: onsuccess: #2223: 1: Success after binutils/gcc/gdb: 10 [...]

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 (f9d08db32f) \ 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 1816 -> 1792 bytes 02-prepare_abe/console.log.xz | Bin 2764 -> 2768 bytes 03-build_abe-binutils/console.log.xz | Bin 31748 -> 31092 bytes 04-build_abe-stage1/console.log.xz | Bin 91584 -> 92164 bytes 06-build_abe-linux/console.log.xz | Bin 8700 -> 8692 bytes 07-build_abe-glibc/console.log.xz | Bin 237012 -> 236900 bytes 08-build_abe-stage2/console.log.xz | Bin 228148 -> 228820 bytes 09-build_abe-gdb/console.log.xz | Bin 38936 -> 38324 bytes 10-build_abe-qemu/console.log.xz | Bin 31720 -> 31704 bytes 11-build_abe-dejagnu/console.log.xz | Bin 3864 -> 3860 bytes 12-build_abe-check_gcc/console.log.xz | Bin 2700 -> 3328 bytes 13-check_regression/console.log.xz | Bin 6004 -> 6124 bytes 13-check_regression/fails.sum | 2 +- 13-check_regression/mail-body.txt | 18 +- 13-check_regression/results.compare | 4 +- 13-check_regression/results.compare2 | 35 +- 13-check_regression/results.regressions | 4 +- 14-update_baseline/console.log | 64 +- dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- git/gdb_rev | 2 +- mail/mail-body.txt | 18 +- manifest.sh | 32 +- results | 4 +- sumfiles/g++.log.xz | Bin 2674916 -> 2649700 bytes sumfiles/g++.sum | 40 +- sumfiles/gcc.log.xz | Bin 2212024 -> 2196944 bytes sumfiles/gcc.sum | 2309 ++++++++++++++++--------------- sumfiles/gfortran.log.xz | Bin 893512 -> 893548 bytes sumfiles/gfortran.sum | 6 +- sumfiles/libatomic.log.xz | Bin 2256 -> 2260 bytes sumfiles/libatomic.sum | 2 +- sumfiles/libgomp.log.xz | Bin 216904 -> 216928 bytes sumfiles/libgomp.sum | 2 +- sumfiles/libitm.log.xz | Bin 2664 -> 2664 bytes sumfiles/libitm.sum | 2 +- sumfiles/libstdc++.log.xz | Bin 444656 -> 433996 bytes sumfiles/libstdc++.sum | 32 +- 39 files changed, 1313 insertions(+), 1269 deletions(-)