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 9989ee8697 402: onsuccess: #2223: 1: Success after binutils/gcc/gdb: 10 [...] discards d1b5dc062d 401: onsuccess: #2222: 1: Success after binutils/gcc/gdb: 10 [...] discards b78d317e17 400: onsuccess: #2221: 1: Success after binutils/gcc/linux/g [...] discards 08c5b03a9b 399: onsuccess: #2220: 1: Success after binutils/gcc/linux/g [...] discards 6a9d47c77f 398: onsuccess: #2219: 1: Success after binutils/gcc/gdb/qem [...] discards 11a838da0c 397: onsuccess: #2218: 1: Success after binutils/gcc/linux/g [...] discards c7ccda5757 396: onsuccess: #2217: 1: Success after binutils/gcc/linux/g [...] discards 73ef6d35a1 395: onsuccess: #2216: 1: Success after binutils/gcc/linux/g [...] discards 151c0c2674 394: onsuccess: #2215: 1: Success after binutils/gcc/gdb: 8 commits discards 235a5ed6e4 393: onsuccess: #2214: 1: Success after binutils/gcc/gdb: 12 [...] discards 7f82085320 392: onsuccess: #2213: 1: Success after binutils/gcc/glibc/g [...] discards 26915e5a23 391: onsuccess: #2212: 1: Success after binutils/gcc/gdb/qem [...] discards 167a60c234 390: onsuccess: #2211: 1: Success after binutils/gcc/linux/g [...] discards b3598513e2 389: onsuccess: #2210: 1: Success after binutils/gcc/linux/g [...] discards beedb21874 388: onsuccess: #2209: 1: Success after binutils/gcc/glibc/g [...] discards db067f62bc 387: onsuccess: #2208: 1: Success after gcc: 2 commits discards b9dbd0f28c 386: onsuccess: #2207: 1: Success after binutils/gcc/linux/g [...] discards 160539f592 385: onsuccess: #2206: 1: Success after binutils/gcc/glibc/g [...] discards 771451b59d 384: onsuccess: #2205: 1: Success after gcc: 2 commits discards 2a5c124204 383: onsuccess: #2204: 1: Success after binutils/gcc/linux/g [...] discards 0114ffdd8d 382: onsuccess: #2203: 1: Success after gcc/qemu: 42 commits discards 0d9c57ca1e 381: onsuccess: #2202: 1: Success after glibc-2.37.9000-17-g [...] discards c458998721 380: onsuccess: #2201: 1: Success after binutils/gcc/linux/g [...] discards 1d8a5c2e70 379: onsuccess: #2200: 1: Success after binutils/gcc/linux/g [...] discards f76c9ce120 378: onsuccess: #2199: 1: Success after binutils/gdb: 4 commits discards f6b90eaa82 377: onsuccess: #2198: 1: Success after binutils/gcc/gdb: 3 commits discards 47acdad76e 376: onsuccess: #2197: 1: Success after binutils/gcc/linux/g [...] discards e5548f3e52 375: onsuccess: #2195: 1: Success after binutils/gcc/gdb/qem [...] discards 4a32ef7bc7 374: onsuccess: #2194: 1: Success after binutils/gcc/linux/g [...] discards c5824f9375 373: onsuccess: #2193: 1: Success after binutils/gcc/glibc/g [...] discards fb7c57e96f 372: onsuccess: #2192: 1: Success after binutils/gcc/linux/g [...] discards b66d38abda 371: onsuccess: #2191: 1: Success after binutils/gcc/gdb: 10 [...] discards df9b31e1e6 370: onsuccess: #2190: 1: Success after binutils/gcc/linux/g [...] discards e40f33023c 369: onsuccess: #2189: 1: Success after binutils/gcc/linux/g [...] discards a0741f1110 368: onsuccess: #2188: 1: Success after binutils/gcc/linux/g [...] discards f225a67d1f 367: onsuccess: #2187: 1: Success after binutils/gcc/gdb: 14 [...] discards 21c05e6fe0 366: onsuccess: #2186: 1: Success after binutils/gcc/linux/g [...] discards 3cb08a5dce 365: onsuccess: #2185: 1: Success after binutils/gcc/linux/g [...] discards 93dff1ae58 364: onsuccess: #2184: 1: Success after binutils/gcc/linux/g [...] discards 8e4f435964 363: onsuccess: #2183: 1: Success after binutils/gcc/linux/g [...] discards 4b5da78bf9 362: onsuccess: #2182: 1: Success after binutils/gcc/linux/g [...] discards d744339096 361: onsuccess: #2181: 1: Success after binutils/gcc/linux/g [...] discards 3a35c7e361 360: onsuccess: #2180: 1: Success after binutils/gcc/linux/g [...] discards 434915d084 359: onsuccess: #2179: 1: Success after binutils/gcc/glibc/g [...] discards f6e3fc81ab 358: onsuccess: #2178: 1: Success after binutils/gcc/linux/g [...] discards 18e007267c 357: onsuccess: #2177: 1: Success after binutils/gcc/linux/g [...] discards ed52f5f2c8 356: onsuccess: #2176: 1: Success after binutils/gcc/linux/g [...] discards a323bd8826 355: onsuccess: #2175: 1: Success after binutils/gcc/linux/g [...] discards 723cebb09c 354: onsuccess: #2174: 1: Success after binutils/gcc/linux/g [...] discards c7975b0098 353: onsuccess: #2173: 1: Success after binutils/gcc/gdb: 27 [...] discards 8524eeab49 352: onsuccess: #2172: 1: Success after binutils/gcc/linux/g [...] discards 6e447b4a0b 351: onsuccess: #2171: 1: Success after gcc/linux: 15 commits discards 32564940cd 350: onsuccess: #2170: 1: Success after binutils/gcc/linux/g [...] discards 05a26acad4 349: onsuccess: #2169: 1: Success after binutils/gcc/linux/g [...] discards 93f8241a5d 348: onsuccess: #2168: 1: Success after binutils/gcc/gdb: 9 commits discards babbc3fbca 347: onsuccess: #2167: 1: Success after basepoints/gcc-13-51 [...] discards 05e92e2a06 346: onsuccess: #2166: 1: Success after binutils/gcc/linux/g [...] discards 7a7c8e56a7 345: onsuccess: #2165: 1: Success after binutils/gcc/glibc/g [...] discards 48f9da01d6 344: onsuccess: #2164: 1: Success after gcc/linux/glibc: 37 commits discards fbeeb822dd 343: onsuccess: #2163: 1: Success after binutils/gcc/gdb: 7 commits discards b9e011d636 342: onsuccess: #2162: 1: Success after binutils/gcc/linux/g [...] discards e0cfa45bb8 341: onsuccess: #2161: 1: Success after binutils/gcc/gdb: 11 [...] discards bb616ad66e 340: onsuccess: #2160: 1: Success after binutils/gcc/gdb: 15 [...] discards 6b57f3d1f2 339: onsuccess: #2159: 1: Success after binutils/gcc/gdb: 4 commits discards 4a89af0be7 338: onsuccess: #2158: 1: Success after binutils/gcc/linux/g [...] discards 5440cb5590 337: onsuccess: #2157: 1: Success after binutils/gcc/glibc/g [...] discards 27dbd23bdc 336: onsuccess: #2156: 1: Success after binutils/gcc/linux/g [...] discards 1836070e58 335: onsuccess: #2155: 1: Success after binutils/gdb: 146 commits discards a17b3f5a35 334: onsuccess: #2154: 1: Success after binutils/gcc/linux/g [...] discards fc38989d05 333: onsuccess: #2153: 1: Success after binutils/gcc/gdb/qem [...] discards 39a6636db2 332: onsuccess: #2152: 1: Success after binutils/gcc/gdb/qem [...] discards fde3049be4 331: onsuccess: #2151: 1: Success after binutils/gcc/linux/g [...] discards bf415be353 330: onsuccess: #2150: 1: Success after linux/qemu: 36 commits discards d07207250c 329: onsuccess: #2149: 1: Success after binutils/gcc/gdb/qem [...] discards c0479dfc06 328: onsuccess: #2148: 1: Success after gcc/linux/qemu: 78 commits discards 856641fcef 327: onsuccess: #2147: 1: Success after basepoints/gcc-13-50 [...] discards 906ae77951 326: onsuccess: #2146: 1: Success after binutils/gcc/linux/g [...] discards 312cc00e82 325: onsuccess: #2145: 1: Success after binutils/gcc/glibc/g [...] discards b3823f2595 324: onsuccess: #2144: 1: Success after binutils/gcc/gdb/qem [...] discards 821bd8efa1 323: onsuccess: #2143: 1: Success after basepoints/gcc-13-50 [...] discards a317e8dd71 322: onsuccess: #2142: 1: Success after binutils/gcc/linux/g [...] discards 776b256544 321: onsuccess: #2141: 1: Success after binutils/gcc/linux/g [...] discards 69abcf57be 320: onsuccess: #2140: 1: Success after binutils/gcc/gdb: 6 commits discards d566aad47d 319: onsuccess: #2139: 1: Success after binutils/gcc/gdb: 11 [...] discards 283d756f44 318: onsuccess: #2138: 1: Success after binutils/gcc/linux/g [...] discards dde06dcaf2 317: onsuccess: #2137: 1: Success after binutils/gcc/linux/g [...] discards 17b4d9d1a8 316: onsuccess: #2136: 1: Success after binutils/gcc/gdb: 26 [...] discards 6ca7d02c56 315: onsuccess: #2135: 1: Success after binutils/gcc/gdb: 11 [...] discards 2e8d5bdb20 314: onsuccess: #2134: 1: Success after binutils/gcc/glibc/g [...] discards 23a3dbda90 313: onsuccess: #2133: 1: Success after binutils/gcc/linux/g [...] discards 6cdeb91b58 312: onsuccess: #2132: 1: Success after glibc-2.36.9000-416- [...] discards 46854e63d1 311: onsuccess: #2130: 1: Success after gcc: 4 commits discards cc38b93833 310: onsuccess: #2129: 1: Success after binutils: 4 commits discards 72b39b6c8a 309: onsuccess: #2127: 1: Success after binutils/gcc/glibc/g [...] discards 874ac88b5d 308: onsuccess: #2126: 1: Success after binutils/gcc/linux/g [...] discards 2914af2698 307: onsuccess: #2124: 1: Success after gcc: 2 commits discards c2b3e32c00 306: onsuccess: #2123: 1: Success after binutils/gcc/gdb: 15 [...] discards 702a78e81d 305: onsuccess: #2122: 1: Success after binutils/gcc/gdb: 4 commits discards cfabbd56b1 304: onsuccess: #2121: 1: Success after gcc/linux: 13 commits discards b281c93bbc 303: onsuccess: #2120: 1: Success after binutils/gdb: 20 commits discards 65a30d976f 302: onsuccess: #2119: 1: Success after binutils/gdb: 7 commits new 6375d6389d 302: onsuccess: #2119: 1: Success after binutils/gdb: 7 commits new 7dc3eb6d7b 303: onsuccess: #2120: 1: Success after binutils/gdb: 20 commits new 48f3c5f47c 304: onsuccess: #2121: 1: Success after gcc/linux: 13 commits new c197e7abc3 305: onsuccess: #2122: 1: Success after binutils/gcc/gdb: 4 commits new 06f089a07d 306: onsuccess: #2123: 1: Success after binutils/gcc/gdb: 15 [...] new 0d24ee050d 307: onsuccess: #2124: 1: Success after gcc: 2 commits new 8c17a7c653 308: onsuccess: #2126: 1: Success after binutils/gcc/linux/g [...] new e6d4995242 309: onsuccess: #2127: 1: Success after binutils/gcc/glibc/g [...] new 9c17eb74b0 310: onsuccess: #2129: 1: Success after binutils: 4 commits new 6c73a73cf5 311: onsuccess: #2130: 1: Success after gcc: 4 commits new f83d16a0d2 312: onsuccess: #2132: 1: Success after glibc-2.36.9000-416- [...] new c6fc858d6a 313: onsuccess: #2133: 1: Success after binutils/gcc/linux/g [...] new 4c5e69a95e 314: onsuccess: #2134: 1: Success after binutils/gcc/glibc/g [...] new 1e253daf79 315: onsuccess: #2135: 1: Success after binutils/gcc/gdb: 11 [...] new 154bbf2a73 316: onsuccess: #2136: 1: Success after binutils/gcc/gdb: 26 [...] new e971ffc8ca 317: onsuccess: #2137: 1: Success after binutils/gcc/linux/g [...] new 02864561cc 318: onsuccess: #2138: 1: Success after binutils/gcc/linux/g [...] new abc3d28d34 319: onsuccess: #2139: 1: Success after binutils/gcc/gdb: 11 [...] new 4ef8be6641 320: onsuccess: #2140: 1: Success after binutils/gcc/gdb: 6 commits new 30ef48cfd2 321: onsuccess: #2141: 1: Success after binutils/gcc/linux/g [...] new 85efb500f7 322: onsuccess: #2142: 1: Success after binutils/gcc/linux/g [...] new 0b11c6af9b 323: onsuccess: #2143: 1: Success after basepoints/gcc-13-50 [...] new 355fea3f38 324: onsuccess: #2144: 1: Success after binutils/gcc/gdb/qem [...] new 9028e63c45 325: onsuccess: #2145: 1: Success after binutils/gcc/glibc/g [...] new f7da10850b 326: onsuccess: #2146: 1: Success after binutils/gcc/linux/g [...] new 5fac55d7c0 327: onsuccess: #2147: 1: Success after basepoints/gcc-13-50 [...] new 194ddba350 328: onsuccess: #2148: 1: Success after gcc/linux/qemu: 78 commits new c4357f2ed2 329: onsuccess: #2149: 1: Success after binutils/gcc/gdb/qem [...] new 0bacfb836e 330: onsuccess: #2150: 1: Success after linux/qemu: 36 commits new 6db582d983 331: onsuccess: #2151: 1: Success after binutils/gcc/linux/g [...] new 237f2656cf 332: onsuccess: #2152: 1: Success after binutils/gcc/gdb/qem [...] new 5d19733f15 333: onsuccess: #2153: 1: Success after binutils/gcc/gdb/qem [...] new 266b495a2d 334: onsuccess: #2154: 1: Success after binutils/gcc/linux/g [...] new fd7caa0084 335: onsuccess: #2155: 1: Success after binutils/gdb: 146 commits new 2d0795c2bd 336: onsuccess: #2156: 1: Success after binutils/gcc/linux/g [...] new cc58160ad2 337: onsuccess: #2157: 1: Success after binutils/gcc/glibc/g [...] new 5b9576a404 338: onsuccess: #2158: 1: Success after binutils/gcc/linux/g [...] new def6929902 339: onsuccess: #2159: 1: Success after binutils/gcc/gdb: 4 commits new 9b70cc34df 340: onsuccess: #2160: 1: Success after binutils/gcc/gdb: 15 [...] new 8be1cd72c0 341: onsuccess: #2161: 1: Success after binutils/gcc/gdb: 11 [...] new aeeb0a2b6a 342: onsuccess: #2162: 1: Success after binutils/gcc/linux/g [...] new 7b9bdc3e20 343: onsuccess: #2163: 1: Success after binutils/gcc/gdb: 7 commits new 9c3a5de508 344: onsuccess: #2164: 1: Success after gcc/linux/glibc: 37 commits new 4f11ef3cf5 345: onsuccess: #2165: 1: Success after binutils/gcc/glibc/g [...] new 6b85320fe8 346: onsuccess: #2166: 1: Success after binutils/gcc/linux/g [...] new bac431bc78 347: onsuccess: #2167: 1: Success after basepoints/gcc-13-51 [...] new c6ce6ae42c 348: onsuccess: #2168: 1: Success after binutils/gcc/gdb: 9 commits new 0a932b520a 349: onsuccess: #2169: 1: Success after binutils/gcc/linux/g [...] new d1f3638550 350: onsuccess: #2170: 1: Success after binutils/gcc/linux/g [...] new 345582d9c2 351: onsuccess: #2171: 1: Success after gcc/linux: 15 commits new 7ee1837f90 352: onsuccess: #2172: 1: Success after binutils/gcc/linux/g [...] new 721a09ec7a 353: onsuccess: #2173: 1: Success after binutils/gcc/gdb: 27 [...] new 082d208c0a 354: onsuccess: #2174: 1: Success after binutils/gcc/linux/g [...] new 0b7f076969 355: onsuccess: #2175: 1: Success after binutils/gcc/linux/g [...] new f35d9b8d72 356: onsuccess: #2176: 1: Success after binutils/gcc/linux/g [...] new 65834babc3 357: onsuccess: #2177: 1: Success after binutils/gcc/linux/g [...] new 7d58d931df 358: onsuccess: #2178: 1: Success after binutils/gcc/linux/g [...] new 74942d1f6d 359: onsuccess: #2179: 1: Success after binutils/gcc/glibc/g [...] new 51ccc60b17 360: onsuccess: #2180: 1: Success after binutils/gcc/linux/g [...] new 14ad5af409 361: onsuccess: #2181: 1: Success after binutils/gcc/linux/g [...] new 63da53dcdd 362: onsuccess: #2182: 1: Success after binutils/gcc/linux/g [...] new d154600b12 363: onsuccess: #2183: 1: Success after binutils/gcc/linux/g [...] new d29b439b94 364: onsuccess: #2184: 1: Success after binutils/gcc/linux/g [...] new 384dface6c 365: onsuccess: #2185: 1: Success after binutils/gcc/linux/g [...] new 9381ea4671 366: onsuccess: #2186: 1: Success after binutils/gcc/linux/g [...] new a4dc09cae5 367: onsuccess: #2187: 1: Success after binutils/gcc/gdb: 14 [...] new 59c605f8a3 368: onsuccess: #2188: 1: Success after binutils/gcc/linux/g [...] new bb404da8b9 369: onsuccess: #2189: 1: Success after binutils/gcc/linux/g [...] new 1c77504c4c 370: onsuccess: #2190: 1: Success after binutils/gcc/linux/g [...] new f0276ee534 371: onsuccess: #2191: 1: Success after binutils/gcc/gdb: 10 [...] new 3671d086e8 372: onsuccess: #2192: 1: Success after binutils/gcc/linux/g [...] new 31c5966e32 373: onsuccess: #2193: 1: Success after binutils/gcc/glibc/g [...] new 165f5ea8dc 374: onsuccess: #2194: 1: Success after binutils/gcc/linux/g [...] new cfa7060c12 375: onsuccess: #2195: 1: Success after binutils/gcc/gdb/qem [...] new 47455750d7 376: onsuccess: #2197: 1: Success after binutils/gcc/linux/g [...] new 3a8545972e 377: onsuccess: #2198: 1: Success after binutils/gcc/gdb: 3 commits new 52d3cec15b 378: onsuccess: #2199: 1: Success after binutils/gdb: 4 commits new 80a4cc5d42 379: onsuccess: #2200: 1: Success after binutils/gcc/linux/g [...] new f8569f70ed 380: onsuccess: #2201: 1: Success after binutils/gcc/linux/g [...] new 58d3bec070 381: onsuccess: #2202: 1: Success after glibc-2.37.9000-17-g [...] new f07bc324be 382: onsuccess: #2203: 1: Success after gcc/qemu: 42 commits new 9c5cf39d7f 383: onsuccess: #2204: 1: Success after binutils/gcc/linux/g [...] new 40f39aee9e 384: onsuccess: #2205: 1: Success after gcc: 2 commits new ccae250b0a 385: onsuccess: #2206: 1: Success after binutils/gcc/glibc/g [...] new 9dee344351 386: onsuccess: #2207: 1: Success after binutils/gcc/linux/g [...] new a81db0e926 387: onsuccess: #2208: 1: Success after gcc: 2 commits new 6b33afe3a4 388: onsuccess: #2209: 1: Success after binutils/gcc/glibc/g [...] new e70ac8f759 389: onsuccess: #2210: 1: Success after binutils/gcc/linux/g [...] new 14bb8c8833 390: onsuccess: #2211: 1: Success after binutils/gcc/linux/g [...] new a0bd1d699c 391: onsuccess: #2212: 1: Success after binutils/gcc/gdb/qem [...] new 710a3d3354 392: onsuccess: #2213: 1: Success after binutils/gcc/glibc/g [...] new 7e57119117 393: onsuccess: #2214: 1: Success after binutils/gcc/gdb: 12 [...] new 84934f1745 394: onsuccess: #2215: 1: Success after binutils/gcc/gdb: 8 commits new bb93b0e255 395: onsuccess: #2216: 1: Success after binutils/gcc/linux/g [...] new 94e9fcea9e 396: onsuccess: #2217: 1: Success after binutils/gcc/linux/g [...] new edf00440f2 397: onsuccess: #2218: 1: Success after binutils/gcc/linux/g [...] new e0eb53e51d 398: onsuccess: #2219: 1: Success after binutils/gcc/gdb/qem [...] new 9b4efe2648 399: onsuccess: #2220: 1: Success after binutils/gcc/linux/g [...] new d3d3a522b2 400: onsuccess: #2221: 1: Success after binutils/gcc/linux/g [...] new 816c0a1853 401: onsuccess: #2222: 1: Success after binutils/gcc/gdb: 10 [...] new d2a3501833 402: onsuccess: #2223: 1: Success after binutils/gcc/gdb: 10 [...] new 31580f8a4a 403: onsuccess: #2224: 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 (9989ee8697) \ 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 1792 -> 1800 bytes 02-prepare_abe/console.log.xz | Bin 2768 -> 2768 bytes 03-build_abe-binutils/console.log.xz | Bin 31092 -> 30932 bytes 04-build_abe-stage1/console.log.xz | Bin 92164 -> 91424 bytes 06-build_abe-linux/console.log.xz | Bin 8692 -> 8656 bytes 07-build_abe-glibc/console.log.xz | Bin 236900 -> 236892 bytes 08-build_abe-stage2/console.log.xz | Bin 228820 -> 227612 bytes 09-build_abe-gdb/console.log.xz | Bin 38324 -> 38168 bytes 10-build_abe-qemu/console.log.xz | Bin 31704 -> 31108 bytes 11-build_abe-dejagnu/console.log.xz | Bin 3860 -> 3864 bytes 12-build_abe-check_gcc/console.log.xz | Bin 3328 -> 2640 bytes 13-check_regression/console.log.xz | Bin 6124 -> 6108 bytes 13-check_regression/fails.sum | 2 +- 13-check_regression/mail-body.txt | 24 +- 13-check_regression/results.compare | 20 +- 13-check_regression/results.compare2 | 40 +- 13-check_regression/results.regressions | 20 +- 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 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 26 +- mail/mail-subject.txt | 2 +- manifest.sh | 36 +- results | 20 +- sumfiles/g++.log.xz | Bin 2649700 -> 2655284 bytes sumfiles/g++.sum | 38 +- sumfiles/gcc.log.xz | Bin 2196944 -> 2220492 bytes sumfiles/gcc.sum | 2150 +++++++++++++++---------------- sumfiles/gfortran.log.xz | Bin 893548 -> 895356 bytes sumfiles/gfortran.sum | 6 +- sumfiles/libatomic.log.xz | Bin 2260 -> 2264 bytes sumfiles/libatomic.sum | 2 +- sumfiles/libgomp.log.xz | Bin 216928 -> 216944 bytes sumfiles/libgomp.sum | 2 +- sumfiles/libitm.log.xz | Bin 2664 -> 2664 bytes sumfiles/libitm.sum | 2 +- sumfiles/libstdc++.log.xz | Bin 433996 -> 443648 bytes sumfiles/libstdc++.sum | 30 +- 42 files changed, 1245 insertions(+), 1253 deletions(-)