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 3fdda773d3 427: onsuccess: #2251: 1: Success after binutils/gcc/linux/g [...] discards f537c2af48 426: onsuccess: #2250: 1: Success after binutils/linux/gdb: [...] discards 96c70e9df3 425: onsuccess: #2249: 1: Success after binutils/gcc/linux/g [...] discards a2bf8cc8cd 424: onsuccess: #2248: 1: Success after gcc: 6 commits discards 240e3b7c82 423: onsuccess: #2247: 1: Success after gcc/linux: 8 commits discards 68cbf638c3 422: onsuccess: #2246: 1: Success after binutils/gcc/linux/g [...] discards 227aa04eb9 421: onsuccess: #2245: 1: Success after binutils/gcc/glibc/g [...] discards 9580b81949 420: onsuccess: #2244: 1: Success after gcc/glibc: 5 commits discards fee23fe151 419: onsuccess: #2243: 1: Success after binutils/gcc/linux/g [...] discards a521170cc4 418: onsuccess: #2239: 1: Success after binutils/gcc/gdb: 5 commits discards 648699fa2f 417: onsuccess: #2238: 1: Success after binutils/gcc/linux/g [...] discards d3ad529295 416: onsuccess: #2237: 1: Success after binutils/gcc/glibc/g [...] discards f11d292374 415: onsuccess: #2236: 1: Success after binutils/gcc/gdb: 14 [...] discards 1e6397cfe2 414: onsuccess: #2235: 1: Success after binutils/gcc/gdb: 13 [...] discards 2f4a54d3e5 413: onsuccess: #2234: 1: Success after binutils/gcc/linux/g [...] discards 2f54888e80 412: onsuccess: #2233: 1: Success after binutils/gcc/glibc/g [...] discards 091823fe4c 411: onsuccess: #2232: 1: Success after gcc: 3 commits discards d86bef0fb5 410: onsuccess: #2231: 1: Success after binutils/gcc/linux/g [...] discards e69e2052c7 409: onsuccess: #2230: 1: Success after binutils/gcc/glibc/g [...] discards 4bb25cdc8b 408: onsuccess: #2229: 1: Success after binutils/gcc/gdb: 26 [...] discards db0d74e36e 407: onsuccess: #2228: 1: Success after binutils/gcc/linux/g [...] discards 355ad79297 406: onsuccess: #2227: 1: Success after binutils/linux/glibc [...] discards 227198fda1 405: onsuccess: #2226: 1: Success after gcc/glibc: 39 commits discards 674a211f33 404: onsuccess: #2225: 1: Success after binutils/gcc/gdb: 10 [...] discards 4395a91675 403: onsuccess: #2224: 1: Success after binutils/gcc/linux/g [...] discards 65f73d3184 402: onsuccess: #2223: 1: Success after binutils/gcc/gdb: 10 [...] discards 42826521a2 401: onsuccess: #2222: 1: Success after binutils/gcc/gdb: 10 [...] discards 9d997f617a 400: onsuccess: #2221: 1: Success after binutils/gcc/linux/g [...] discards 2fad72807e 399: onsuccess: #2220: 1: Success after binutils/gcc/linux/g [...] discards 339ceafe74 398: onsuccess: #2219: 1: Success after binutils/gcc/gdb/qem [...] discards 2e292fcbc3 397: onsuccess: #2218: 1: Success after binutils/gcc/linux/g [...] discards 33591268f7 396: onsuccess: #2217: 1: Success after binutils/gcc/linux/g [...] discards b83b1815ab 395: onsuccess: #2216: 1: Success after binutils/gcc/linux/g [...] discards 07c66844fb 394: onsuccess: #2215: 1: Success after binutils/gcc/gdb: 8 commits discards 5ce086d5d6 393: onsuccess: #2214: 1: Success after binutils/gcc/gdb: 12 [...] discards 1462017b1c 392: onsuccess: #2213: 1: Success after binutils/gcc/glibc/g [...] discards 1e03c005a3 391: onsuccess: #2212: 1: Success after binutils/gcc/gdb/qem [...] discards 5dc3c9097e 390: onsuccess: #2211: 1: Success after binutils/gcc/linux/g [...] discards e6649edbef 389: onsuccess: #2210: 1: Success after binutils/gcc/linux/g [...] discards 4f28059d78 388: onsuccess: #2209: 1: Success after binutils/gcc/glibc/g [...] discards 5eaa13f25f 387: onsuccess: #2208: 1: Success after gcc: 2 commits discards a97a3bbba5 386: onsuccess: #2207: 1: Success after binutils/gcc/linux/g [...] discards d7111f3da4 385: onsuccess: #2206: 1: Success after binutils/gcc/glibc/g [...] discards ea884d4687 384: onsuccess: #2205: 1: Success after gcc: 2 commits discards 75218691ac 383: onsuccess: #2204: 1: Success after binutils/gcc/linux/g [...] discards 610667e4cb 382: onsuccess: #2203: 1: Success after gcc/qemu: 42 commits discards b0dd8a5a05 381: onsuccess: #2202: 1: Success after glibc-2.37.9000-17-g [...] discards c215786a79 380: onsuccess: #2201: 1: Success after binutils/gcc/linux/g [...] discards 1a51dd44d5 379: onsuccess: #2200: 1: Success after binutils/gcc/linux/g [...] discards d2bcbc9e64 378: onsuccess: #2199: 1: Success after binutils/gdb: 4 commits discards 8ca7fe31cb 377: onsuccess: #2198: 1: Success after binutils/gcc/gdb: 3 commits discards cf7d83cef1 376: onsuccess: #2197: 1: Success after binutils/gcc/linux/g [...] discards a148fee59c 375: onsuccess: #2195: 1: Success after binutils/gcc/gdb/qem [...] discards 932a4b25d2 374: onsuccess: #2194: 1: Success after binutils/gcc/linux/g [...] discards 8ba0df1370 373: onsuccess: #2193: 1: Success after binutils/gcc/glibc/g [...] discards e483d6c700 372: onsuccess: #2192: 1: Success after binutils/gcc/linux/g [...] discards c87d5dbc94 371: onsuccess: #2191: 1: Success after binutils/gcc/gdb: 10 [...] discards 2e827b0f49 370: onsuccess: #2190: 1: Success after binutils/gcc/linux/g [...] discards 32a3fc3036 369: onsuccess: #2189: 1: Success after binutils/gcc/linux/g [...] discards f7eb2e492b 368: onsuccess: #2188: 1: Success after binutils/gcc/linux/g [...] discards 3c404f5bdf 367: onsuccess: #2187: 1: Success after binutils/gcc/gdb: 14 [...] discards 87fa8ebfe9 366: onsuccess: #2186: 1: Success after binutils/gcc/linux/g [...] discards 34847a7460 365: onsuccess: #2185: 1: Success after binutils/gcc/linux/g [...] discards c83369e737 364: onsuccess: #2184: 1: Success after binutils/gcc/linux/g [...] discards 2cb1c56b3b 363: onsuccess: #2183: 1: Success after binutils/gcc/linux/g [...] discards 54ed244aab 362: onsuccess: #2182: 1: Success after binutils/gcc/linux/g [...] discards cc8df7897e 361: onsuccess: #2181: 1: Success after binutils/gcc/linux/g [...] discards d758d6fcfb 360: onsuccess: #2180: 1: Success after binutils/gcc/linux/g [...] discards 97ccc2b46e 359: onsuccess: #2179: 1: Success after binutils/gcc/glibc/g [...] discards bfd03db8e2 358: onsuccess: #2178: 1: Success after binutils/gcc/linux/g [...] discards 389d30bdd9 357: onsuccess: #2177: 1: Success after binutils/gcc/linux/g [...] discards f413adf802 356: onsuccess: #2176: 1: Success after binutils/gcc/linux/g [...] discards 0690aec9fd 355: onsuccess: #2175: 1: Success after binutils/gcc/linux/g [...] discards d6dc2155cc 354: onsuccess: #2174: 1: Success after binutils/gcc/linux/g [...] discards af9f8c5050 353: onsuccess: #2173: 1: Success after binutils/gcc/gdb: 27 [...] discards 72c0062f93 352: onsuccess: #2172: 1: Success after binutils/gcc/linux/g [...] discards 5b8996a6e0 351: onsuccess: #2171: 1: Success after gcc/linux: 15 commits discards 9034b80852 350: onsuccess: #2170: 1: Success after binutils/gcc/linux/g [...] discards 9289d77205 349: onsuccess: #2169: 1: Success after binutils/gcc/linux/g [...] discards 15e7523b06 348: onsuccess: #2168: 1: Success after binutils/gcc/gdb: 9 commits discards bfa57252da 347: onsuccess: #2167: 1: Success after basepoints/gcc-13-51 [...] discards 1c1e18b8c1 346: onsuccess: #2166: 1: Success after binutils/gcc/linux/g [...] discards 962022df09 345: onsuccess: #2165: 1: Success after binutils/gcc/glibc/g [...] discards 3c8f61725f 344: onsuccess: #2164: 1: Success after gcc/linux/glibc: 37 commits discards 5c7e84d1c6 343: onsuccess: #2163: 1: Success after binutils/gcc/gdb: 7 commits discards b147861759 342: onsuccess: #2162: 1: Success after binutils/gcc/linux/g [...] discards 9b20a01fbf 341: onsuccess: #2161: 1: Success after binutils/gcc/gdb: 11 [...] discards a609ff637e 340: onsuccess: #2160: 1: Success after binutils/gcc/gdb: 15 [...] discards 4f44842512 339: onsuccess: #2159: 1: Success after binutils/gcc/gdb: 4 commits discards 5b12cf99f6 338: onsuccess: #2158: 1: Success after binutils/gcc/linux/g [...] discards 5553a73710 337: onsuccess: #2157: 1: Success after binutils/gcc/glibc/g [...] discards 5e0ea3e833 336: onsuccess: #2156: 1: Success after binutils/gcc/linux/g [...] discards aab67a70ef 335: onsuccess: #2155: 1: Success after binutils/gdb: 146 commits discards 6ea30ee067 334: onsuccess: #2154: 1: Success after binutils/gcc/linux/g [...] discards ab60f959e9 333: onsuccess: #2153: 1: Success after binutils/gcc/gdb/qem [...] discards 51806a06ff 332: onsuccess: #2152: 1: Success after binutils/gcc/gdb/qem [...] discards 8b68acb420 331: onsuccess: #2151: 1: Success after binutils/gcc/linux/g [...] discards fd348e88e5 330: onsuccess: #2150: 1: Success after linux/qemu: 36 commits discards 9478e9e440 329: onsuccess: #2149: 1: Success after binutils/gcc/gdb/qem [...] discards 3418d9655c 328: onsuccess: #2148: 1: Success after gcc/linux/qemu: 78 commits discards 4232eba27f 327: onsuccess: #2147: 1: Success after basepoints/gcc-13-50 [...] new f2aaa1a916 327: onsuccess: #2147: 1: Success after basepoints/gcc-13-50 [...] new dcf62d31cc 328: onsuccess: #2148: 1: Success after gcc/linux/qemu: 78 commits new 8d8147fa91 329: onsuccess: #2149: 1: Success after binutils/gcc/gdb/qem [...] new e182c635d6 330: onsuccess: #2150: 1: Success after linux/qemu: 36 commits new 446ff0e8a8 331: onsuccess: #2151: 1: Success after binutils/gcc/linux/g [...] new c350f41d41 332: onsuccess: #2152: 1: Success after binutils/gcc/gdb/qem [...] new ae7358c681 333: onsuccess: #2153: 1: Success after binutils/gcc/gdb/qem [...] new 878e5ea794 334: onsuccess: #2154: 1: Success after binutils/gcc/linux/g [...] new 3c931a7658 335: onsuccess: #2155: 1: Success after binutils/gdb: 146 commits new cf12aed45b 336: onsuccess: #2156: 1: Success after binutils/gcc/linux/g [...] new 698966ef97 337: onsuccess: #2157: 1: Success after binutils/gcc/glibc/g [...] new fd75b0dced 338: onsuccess: #2158: 1: Success after binutils/gcc/linux/g [...] new 46bd214196 339: onsuccess: #2159: 1: Success after binutils/gcc/gdb: 4 commits new 32fa4f9d42 340: onsuccess: #2160: 1: Success after binutils/gcc/gdb: 15 [...] new 4dfff7e902 341: onsuccess: #2161: 1: Success after binutils/gcc/gdb: 11 [...] new 604de967df 342: onsuccess: #2162: 1: Success after binutils/gcc/linux/g [...] new b6f5bb29e2 343: onsuccess: #2163: 1: Success after binutils/gcc/gdb: 7 commits new 32614c66b3 344: onsuccess: #2164: 1: Success after gcc/linux/glibc: 37 commits new d10f7168c4 345: onsuccess: #2165: 1: Success after binutils/gcc/glibc/g [...] new 7e14f22dea 346: onsuccess: #2166: 1: Success after binutils/gcc/linux/g [...] new 07e07cd8c5 347: onsuccess: #2167: 1: Success after basepoints/gcc-13-51 [...] new 80bf8dc419 348: onsuccess: #2168: 1: Success after binutils/gcc/gdb: 9 commits new 39497d97e3 349: onsuccess: #2169: 1: Success after binutils/gcc/linux/g [...] new ae3e374d0f 350: onsuccess: #2170: 1: Success after binutils/gcc/linux/g [...] new 73b085e09d 351: onsuccess: #2171: 1: Success after gcc/linux: 15 commits new a220ba30e0 352: onsuccess: #2172: 1: Success after binutils/gcc/linux/g [...] new 3f20a13d84 353: onsuccess: #2173: 1: Success after binutils/gcc/gdb: 27 [...] new db22889148 354: onsuccess: #2174: 1: Success after binutils/gcc/linux/g [...] new f6fdbc927a 355: onsuccess: #2175: 1: Success after binutils/gcc/linux/g [...] new 5029db062d 356: onsuccess: #2176: 1: Success after binutils/gcc/linux/g [...] new 8463ded4b1 357: onsuccess: #2177: 1: Success after binutils/gcc/linux/g [...] new e0dcc54756 358: onsuccess: #2178: 1: Success after binutils/gcc/linux/g [...] new 2014b1e445 359: onsuccess: #2179: 1: Success after binutils/gcc/glibc/g [...] new 4e68786cf6 360: onsuccess: #2180: 1: Success after binutils/gcc/linux/g [...] new 59b1f2852c 361: onsuccess: #2181: 1: Success after binutils/gcc/linux/g [...] new 4a89658140 362: onsuccess: #2182: 1: Success after binutils/gcc/linux/g [...] new e681163761 363: onsuccess: #2183: 1: Success after binutils/gcc/linux/g [...] new af0ae8b992 364: onsuccess: #2184: 1: Success after binutils/gcc/linux/g [...] new 3d184a4595 365: onsuccess: #2185: 1: Success after binutils/gcc/linux/g [...] new ca06fc61ae 366: onsuccess: #2186: 1: Success after binutils/gcc/linux/g [...] new 9e2aee68a5 367: onsuccess: #2187: 1: Success after binutils/gcc/gdb: 14 [...] new 26b3f52ed9 368: onsuccess: #2188: 1: Success after binutils/gcc/linux/g [...] new 2f55a02e3d 369: onsuccess: #2189: 1: Success after binutils/gcc/linux/g [...] new a8493034e2 370: onsuccess: #2190: 1: Success after binutils/gcc/linux/g [...] new af1f0d58df 371: onsuccess: #2191: 1: Success after binutils/gcc/gdb: 10 [...] new afbfdf0970 372: onsuccess: #2192: 1: Success after binutils/gcc/linux/g [...] new e59acdc369 373: onsuccess: #2193: 1: Success after binutils/gcc/glibc/g [...] new 4045ab9548 374: onsuccess: #2194: 1: Success after binutils/gcc/linux/g [...] new 25664c49e2 375: onsuccess: #2195: 1: Success after binutils/gcc/gdb/qem [...] new 91b8ed1e4c 376: onsuccess: #2197: 1: Success after binutils/gcc/linux/g [...] new ea1d724ee8 377: onsuccess: #2198: 1: Success after binutils/gcc/gdb: 3 commits new d6d82b6a58 378: onsuccess: #2199: 1: Success after binutils/gdb: 4 commits new 35d1b8dca5 379: onsuccess: #2200: 1: Success after binutils/gcc/linux/g [...] new 828414e29d 380: onsuccess: #2201: 1: Success after binutils/gcc/linux/g [...] new 9b5a493928 381: onsuccess: #2202: 1: Success after glibc-2.37.9000-17-g [...] new 747a8ff4d1 382: onsuccess: #2203: 1: Success after gcc/qemu: 42 commits new 6db28a839a 383: onsuccess: #2204: 1: Success after binutils/gcc/linux/g [...] new b92b3a401d 384: onsuccess: #2205: 1: Success after gcc: 2 commits new 35cbbe9372 385: onsuccess: #2206: 1: Success after binutils/gcc/glibc/g [...] new 841a3decc0 386: onsuccess: #2207: 1: Success after binutils/gcc/linux/g [...] new 196caca953 387: onsuccess: #2208: 1: Success after gcc: 2 commits new d378a46269 388: onsuccess: #2209: 1: Success after binutils/gcc/glibc/g [...] new 196061adf2 389: onsuccess: #2210: 1: Success after binutils/gcc/linux/g [...] new 06291346be 390: onsuccess: #2211: 1: Success after binutils/gcc/linux/g [...] new 38b288d722 391: onsuccess: #2212: 1: Success after binutils/gcc/gdb/qem [...] new 7831b06a9a 392: onsuccess: #2213: 1: Success after binutils/gcc/glibc/g [...] new 15ca0dc372 393: onsuccess: #2214: 1: Success after binutils/gcc/gdb: 12 [...] new 540f3a5cdc 394: onsuccess: #2215: 1: Success after binutils/gcc/gdb: 8 commits new 8dee2450dd 395: onsuccess: #2216: 1: Success after binutils/gcc/linux/g [...] new c876017183 396: onsuccess: #2217: 1: Success after binutils/gcc/linux/g [...] new 9276a36ff3 397: onsuccess: #2218: 1: Success after binutils/gcc/linux/g [...] new c113a615ec 398: onsuccess: #2219: 1: Success after binutils/gcc/gdb/qem [...] new b50882014b 399: onsuccess: #2220: 1: Success after binutils/gcc/linux/g [...] new 405fd9020b 400: onsuccess: #2221: 1: Success after binutils/gcc/linux/g [...] new d48367b17d 401: onsuccess: #2222: 1: Success after binutils/gcc/gdb: 10 [...] new 57da335f9b 402: onsuccess: #2223: 1: Success after binutils/gcc/gdb: 10 [...] new 898d8263a7 403: onsuccess: #2224: 1: Success after binutils/gcc/linux/g [...] new b39ac52f0a 404: onsuccess: #2225: 1: Success after binutils/gcc/gdb: 10 [...] new cd4c655179 405: onsuccess: #2226: 1: Success after gcc/glibc: 39 commits new 7fbad68494 406: onsuccess: #2227: 1: Success after binutils/linux/glibc [...] new 3dacfbed12 407: onsuccess: #2228: 1: Success after binutils/gcc/linux/g [...] new 506f91ca3a 408: onsuccess: #2229: 1: Success after binutils/gcc/gdb: 26 [...] new 37e73e2762 409: onsuccess: #2230: 1: Success after binutils/gcc/glibc/g [...] new be78490dd7 410: onsuccess: #2231: 1: Success after binutils/gcc/linux/g [...] new c3736da325 411: onsuccess: #2232: 1: Success after gcc: 3 commits new ee6089377f 412: onsuccess: #2233: 1: Success after binutils/gcc/glibc/g [...] new 1b785e992e 413: onsuccess: #2234: 1: Success after binutils/gcc/linux/g [...] new cc9e5d8e40 414: onsuccess: #2235: 1: Success after binutils/gcc/gdb: 13 [...] new 50c60f7a09 415: onsuccess: #2236: 1: Success after binutils/gcc/gdb: 14 [...] new b2be8ae410 416: onsuccess: #2237: 1: Success after binutils/gcc/glibc/g [...] new c512be3484 417: onsuccess: #2238: 1: Success after binutils/gcc/linux/g [...] new 7cfef2999a 418: onsuccess: #2239: 1: Success after binutils/gcc/gdb: 5 commits new 3d1e8252d4 419: onsuccess: #2243: 1: Success after binutils/gcc/linux/g [...] new f1c4e5276f 420: onsuccess: #2244: 1: Success after gcc/glibc: 5 commits new b0a3a30f73 421: onsuccess: #2245: 1: Success after binutils/gcc/glibc/g [...] new d56f8d3e6f 422: onsuccess: #2246: 1: Success after binutils/gcc/linux/g [...] new aa4ce2b37b 423: onsuccess: #2247: 1: Success after gcc/linux: 8 commits new cfb9cacff6 424: onsuccess: #2248: 1: Success after gcc: 6 commits new 727dd23534 425: onsuccess: #2249: 1: Success after binutils/gcc/linux/g [...] new ce782c59e6 426: onsuccess: #2250: 1: Success after binutils/linux/gdb: [...] new 96253ab246 427: onsuccess: #2251: 1: Success after binutils/gcc/linux/g [...] new bbf8cbdfea 428: onsuccess: #2252: 1: Success after binutils/gdb: 2 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 (3fdda773d3) \ 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 1800 -> 1820 bytes 02-prepare_abe/console.log.xz | Bin 2768 -> 2768 bytes 03-build_abe-binutils/console.log.xz | Bin 30716 -> 30696 bytes 04-build_abe-stage1/console.log.xz | Bin 88560 -> 88660 bytes 06-build_abe-linux/console.log.xz | Bin 8344 -> 8324 bytes 07-build_abe-glibc/console.log.xz | Bin 236132 -> 235344 bytes 08-build_abe-stage2/console.log.xz | Bin 225080 -> 225084 bytes 09-build_abe-gdb/console.log.xz | Bin 38524 -> 38580 bytes 10-build_abe-qemu/console.log.xz | Bin 31532 -> 31596 bytes 11-build_abe-dejagnu/console.log.xz | Bin 3816 -> 3800 bytes 12-build_abe-check_gcc/console.log.xz | Bin 2584 -> 2584 bytes 13-check_regression/console.log.xz | Bin 6320 -> 4956 bytes 13-check_regression/results.compare2 | 22 ++++++------------- 14-update_baseline/console.log | 40 +++++++++++++++++----------------- dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gdb_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 2 +- mail/mail-subject.txt | 2 +- manifest.sh | 28 ++++++++++++------------ sumfiles/g++.log.xz | Bin 2653540 -> 2664680 bytes sumfiles/gcc.log.xz | Bin 2220584 -> 2204656 bytes sumfiles/gfortran.log.xz | Bin 895152 -> 891288 bytes sumfiles/libatomic.log.xz | Bin 2260 -> 2264 bytes sumfiles/libatomic.sum | 2 +- sumfiles/libgomp.log.xz | Bin 217024 -> 216972 bytes sumfiles/libgomp.sum | 2 +- sumfiles/libitm.log.xz | Bin 2664 -> 2664 bytes sumfiles/libitm.sum | 2 +- sumfiles/libstdc++.log.xz | Bin 444092 -> 442784 bytes sumfiles/libstdc++.sum | 27 +++++++++++++---------- 32 files changed, 66 insertions(+), 69 deletions(-)