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 bbf8cbdfea 428: onsuccess: #2252: 1: Success after binutils/gdb: 2 commits discards 96253ab246 427: onsuccess: #2251: 1: Success after binutils/gcc/linux/g [...] discards ce782c59e6 426: onsuccess: #2250: 1: Success after binutils/linux/gdb: [...] discards 727dd23534 425: onsuccess: #2249: 1: Success after binutils/gcc/linux/g [...] discards cfb9cacff6 424: onsuccess: #2248: 1: Success after gcc: 6 commits discards aa4ce2b37b 423: onsuccess: #2247: 1: Success after gcc/linux: 8 commits discards d56f8d3e6f 422: onsuccess: #2246: 1: Success after binutils/gcc/linux/g [...] discards b0a3a30f73 421: onsuccess: #2245: 1: Success after binutils/gcc/glibc/g [...] discards f1c4e5276f 420: onsuccess: #2244: 1: Success after gcc/glibc: 5 commits discards 3d1e8252d4 419: onsuccess: #2243: 1: Success after binutils/gcc/linux/g [...] discards 7cfef2999a 418: onsuccess: #2239: 1: Success after binutils/gcc/gdb: 5 commits discards c512be3484 417: onsuccess: #2238: 1: Success after binutils/gcc/linux/g [...] discards b2be8ae410 416: onsuccess: #2237: 1: Success after binutils/gcc/glibc/g [...] discards 50c60f7a09 415: onsuccess: #2236: 1: Success after binutils/gcc/gdb: 14 [...] discards cc9e5d8e40 414: onsuccess: #2235: 1: Success after binutils/gcc/gdb: 13 [...] discards 1b785e992e 413: onsuccess: #2234: 1: Success after binutils/gcc/linux/g [...] discards ee6089377f 412: onsuccess: #2233: 1: Success after binutils/gcc/glibc/g [...] discards c3736da325 411: onsuccess: #2232: 1: Success after gcc: 3 commits discards be78490dd7 410: onsuccess: #2231: 1: Success after binutils/gcc/linux/g [...] discards 37e73e2762 409: onsuccess: #2230: 1: Success after binutils/gcc/glibc/g [...] discards 506f91ca3a 408: onsuccess: #2229: 1: Success after binutils/gcc/gdb: 26 [...] discards 3dacfbed12 407: onsuccess: #2228: 1: Success after binutils/gcc/linux/g [...] discards 7fbad68494 406: onsuccess: #2227: 1: Success after binutils/linux/glibc [...] discards cd4c655179 405: onsuccess: #2226: 1: Success after gcc/glibc: 39 commits discards b39ac52f0a 404: onsuccess: #2225: 1: Success after binutils/gcc/gdb: 10 [...] discards 898d8263a7 403: onsuccess: #2224: 1: Success after binutils/gcc/linux/g [...] discards 57da335f9b 402: onsuccess: #2223: 1: Success after binutils/gcc/gdb: 10 [...] discards d48367b17d 401: onsuccess: #2222: 1: Success after binutils/gcc/gdb: 10 [...] discards 405fd9020b 400: onsuccess: #2221: 1: Success after binutils/gcc/linux/g [...] discards b50882014b 399: onsuccess: #2220: 1: Success after binutils/gcc/linux/g [...] discards c113a615ec 398: onsuccess: #2219: 1: Success after binutils/gcc/gdb/qem [...] discards 9276a36ff3 397: onsuccess: #2218: 1: Success after binutils/gcc/linux/g [...] discards c876017183 396: onsuccess: #2217: 1: Success after binutils/gcc/linux/g [...] discards 8dee2450dd 395: onsuccess: #2216: 1: Success after binutils/gcc/linux/g [...] discards 540f3a5cdc 394: onsuccess: #2215: 1: Success after binutils/gcc/gdb: 8 commits discards 15ca0dc372 393: onsuccess: #2214: 1: Success after binutils/gcc/gdb: 12 [...] discards 7831b06a9a 392: onsuccess: #2213: 1: Success after binutils/gcc/glibc/g [...] discards 38b288d722 391: onsuccess: #2212: 1: Success after binutils/gcc/gdb/qem [...] discards 06291346be 390: onsuccess: #2211: 1: Success after binutils/gcc/linux/g [...] discards 196061adf2 389: onsuccess: #2210: 1: Success after binutils/gcc/linux/g [...] discards d378a46269 388: onsuccess: #2209: 1: Success after binutils/gcc/glibc/g [...] discards 196caca953 387: onsuccess: #2208: 1: Success after gcc: 2 commits discards 841a3decc0 386: onsuccess: #2207: 1: Success after binutils/gcc/linux/g [...] discards 35cbbe9372 385: onsuccess: #2206: 1: Success after binutils/gcc/glibc/g [...] discards b92b3a401d 384: onsuccess: #2205: 1: Success after gcc: 2 commits discards 6db28a839a 383: onsuccess: #2204: 1: Success after binutils/gcc/linux/g [...] discards 747a8ff4d1 382: onsuccess: #2203: 1: Success after gcc/qemu: 42 commits discards 9b5a493928 381: onsuccess: #2202: 1: Success after glibc-2.37.9000-17-g [...] discards 828414e29d 380: onsuccess: #2201: 1: Success after binutils/gcc/linux/g [...] discards 35d1b8dca5 379: onsuccess: #2200: 1: Success after binutils/gcc/linux/g [...] discards d6d82b6a58 378: onsuccess: #2199: 1: Success after binutils/gdb: 4 commits discards ea1d724ee8 377: onsuccess: #2198: 1: Success after binutils/gcc/gdb: 3 commits discards 91b8ed1e4c 376: onsuccess: #2197: 1: Success after binutils/gcc/linux/g [...] discards 25664c49e2 375: onsuccess: #2195: 1: Success after binutils/gcc/gdb/qem [...] discards 4045ab9548 374: onsuccess: #2194: 1: Success after binutils/gcc/linux/g [...] discards e59acdc369 373: onsuccess: #2193: 1: Success after binutils/gcc/glibc/g [...] discards afbfdf0970 372: onsuccess: #2192: 1: Success after binutils/gcc/linux/g [...] discards af1f0d58df 371: onsuccess: #2191: 1: Success after binutils/gcc/gdb: 10 [...] discards a8493034e2 370: onsuccess: #2190: 1: Success after binutils/gcc/linux/g [...] discards 2f55a02e3d 369: onsuccess: #2189: 1: Success after binutils/gcc/linux/g [...] discards 26b3f52ed9 368: onsuccess: #2188: 1: Success after binutils/gcc/linux/g [...] discards 9e2aee68a5 367: onsuccess: #2187: 1: Success after binutils/gcc/gdb: 14 [...] discards ca06fc61ae 366: onsuccess: #2186: 1: Success after binutils/gcc/linux/g [...] discards 3d184a4595 365: onsuccess: #2185: 1: Success after binutils/gcc/linux/g [...] discards af0ae8b992 364: onsuccess: #2184: 1: Success after binutils/gcc/linux/g [...] discards e681163761 363: onsuccess: #2183: 1: Success after binutils/gcc/linux/g [...] discards 4a89658140 362: onsuccess: #2182: 1: Success after binutils/gcc/linux/g [...] discards 59b1f2852c 361: onsuccess: #2181: 1: Success after binutils/gcc/linux/g [...] discards 4e68786cf6 360: onsuccess: #2180: 1: Success after binutils/gcc/linux/g [...] discards 2014b1e445 359: onsuccess: #2179: 1: Success after binutils/gcc/glibc/g [...] discards e0dcc54756 358: onsuccess: #2178: 1: Success after binutils/gcc/linux/g [...] discards 8463ded4b1 357: onsuccess: #2177: 1: Success after binutils/gcc/linux/g [...] discards 5029db062d 356: onsuccess: #2176: 1: Success after binutils/gcc/linux/g [...] discards f6fdbc927a 355: onsuccess: #2175: 1: Success after binutils/gcc/linux/g [...] discards db22889148 354: onsuccess: #2174: 1: Success after binutils/gcc/linux/g [...] discards 3f20a13d84 353: onsuccess: #2173: 1: Success after binutils/gcc/gdb: 27 [...] discards a220ba30e0 352: onsuccess: #2172: 1: Success after binutils/gcc/linux/g [...] discards 73b085e09d 351: onsuccess: #2171: 1: Success after gcc/linux: 15 commits discards ae3e374d0f 350: onsuccess: #2170: 1: Success after binutils/gcc/linux/g [...] discards 39497d97e3 349: onsuccess: #2169: 1: Success after binutils/gcc/linux/g [...] discards 80bf8dc419 348: onsuccess: #2168: 1: Success after binutils/gcc/gdb: 9 commits discards 07e07cd8c5 347: onsuccess: #2167: 1: Success after basepoints/gcc-13-51 [...] discards 7e14f22dea 346: onsuccess: #2166: 1: Success after binutils/gcc/linux/g [...] discards d10f7168c4 345: onsuccess: #2165: 1: Success after binutils/gcc/glibc/g [...] discards 32614c66b3 344: onsuccess: #2164: 1: Success after gcc/linux/glibc: 37 commits discards b6f5bb29e2 343: onsuccess: #2163: 1: Success after binutils/gcc/gdb: 7 commits discards 604de967df 342: onsuccess: #2162: 1: Success after binutils/gcc/linux/g [...] discards 4dfff7e902 341: onsuccess: #2161: 1: Success after binutils/gcc/gdb: 11 [...] discards 32fa4f9d42 340: onsuccess: #2160: 1: Success after binutils/gcc/gdb: 15 [...] discards 46bd214196 339: onsuccess: #2159: 1: Success after binutils/gcc/gdb: 4 commits discards fd75b0dced 338: onsuccess: #2158: 1: Success after binutils/gcc/linux/g [...] discards 698966ef97 337: onsuccess: #2157: 1: Success after binutils/gcc/glibc/g [...] discards cf12aed45b 336: onsuccess: #2156: 1: Success after binutils/gcc/linux/g [...] discards 3c931a7658 335: onsuccess: #2155: 1: Success after binutils/gdb: 146 commits discards 878e5ea794 334: onsuccess: #2154: 1: Success after binutils/gcc/linux/g [...] discards ae7358c681 333: onsuccess: #2153: 1: Success after binutils/gcc/gdb/qem [...] discards c350f41d41 332: onsuccess: #2152: 1: Success after binutils/gcc/gdb/qem [...] discards 446ff0e8a8 331: onsuccess: #2151: 1: Success after binutils/gcc/linux/g [...] discards e182c635d6 330: onsuccess: #2150: 1: Success after linux/qemu: 36 commits discards 8d8147fa91 329: onsuccess: #2149: 1: Success after binutils/gcc/gdb/qem [...] discards dcf62d31cc 328: onsuccess: #2148: 1: Success after gcc/linux/qemu: 78 commits new ec909cbc95 328: onsuccess: #2148: 1: Success after gcc/linux/qemu: 78 commits new 19b7a686d1 329: onsuccess: #2149: 1: Success after binutils/gcc/gdb/qem [...] new a0c2647c48 330: onsuccess: #2150: 1: Success after linux/qemu: 36 commits new f0e92c6745 331: onsuccess: #2151: 1: Success after binutils/gcc/linux/g [...] new 3ec13dd294 332: onsuccess: #2152: 1: Success after binutils/gcc/gdb/qem [...] new 00fc439e21 333: onsuccess: #2153: 1: Success after binutils/gcc/gdb/qem [...] new 90bba5c69c 334: onsuccess: #2154: 1: Success after binutils/gcc/linux/g [...] new b2a722e8b8 335: onsuccess: #2155: 1: Success after binutils/gdb: 146 commits new 745bb9fc84 336: onsuccess: #2156: 1: Success after binutils/gcc/linux/g [...] new f76ae54cfe 337: onsuccess: #2157: 1: Success after binutils/gcc/glibc/g [...] new 7c0091a1ae 338: onsuccess: #2158: 1: Success after binutils/gcc/linux/g [...] new 76de231bb3 339: onsuccess: #2159: 1: Success after binutils/gcc/gdb: 4 commits new fccc854437 340: onsuccess: #2160: 1: Success after binutils/gcc/gdb: 15 [...] new 8cd5729942 341: onsuccess: #2161: 1: Success after binutils/gcc/gdb: 11 [...] new 4312a0d053 342: onsuccess: #2162: 1: Success after binutils/gcc/linux/g [...] new 71fe91a322 343: onsuccess: #2163: 1: Success after binutils/gcc/gdb: 7 commits new 5381a31d57 344: onsuccess: #2164: 1: Success after gcc/linux/glibc: 37 commits new b9257841af 345: onsuccess: #2165: 1: Success after binutils/gcc/glibc/g [...] new ce5d6d915c 346: onsuccess: #2166: 1: Success after binutils/gcc/linux/g [...] new 8bb3350ce8 347: onsuccess: #2167: 1: Success after basepoints/gcc-13-51 [...] new 7f8cc87b11 348: onsuccess: #2168: 1: Success after binutils/gcc/gdb: 9 commits new 43250b8efa 349: onsuccess: #2169: 1: Success after binutils/gcc/linux/g [...] new cc1218f433 350: onsuccess: #2170: 1: Success after binutils/gcc/linux/g [...] new f693716dd6 351: onsuccess: #2171: 1: Success after gcc/linux: 15 commits new 5f9017f4f0 352: onsuccess: #2172: 1: Success after binutils/gcc/linux/g [...] new 38ce7075e8 353: onsuccess: #2173: 1: Success after binutils/gcc/gdb: 27 [...] new 51005c1aa7 354: onsuccess: #2174: 1: Success after binutils/gcc/linux/g [...] new d8aa083fa9 355: onsuccess: #2175: 1: Success after binutils/gcc/linux/g [...] new 0766bbd912 356: onsuccess: #2176: 1: Success after binutils/gcc/linux/g [...] new 27c40ff6d4 357: onsuccess: #2177: 1: Success after binutils/gcc/linux/g [...] new 45ac4625e9 358: onsuccess: #2178: 1: Success after binutils/gcc/linux/g [...] new acaeeb4134 359: onsuccess: #2179: 1: Success after binutils/gcc/glibc/g [...] new a3ace3acaa 360: onsuccess: #2180: 1: Success after binutils/gcc/linux/g [...] new 9a071355b4 361: onsuccess: #2181: 1: Success after binutils/gcc/linux/g [...] new 1aa4f46f78 362: onsuccess: #2182: 1: Success after binutils/gcc/linux/g [...] new 06c8b876cf 363: onsuccess: #2183: 1: Success after binutils/gcc/linux/g [...] new 17c6b856de 364: onsuccess: #2184: 1: Success after binutils/gcc/linux/g [...] new b9f7e5be07 365: onsuccess: #2185: 1: Success after binutils/gcc/linux/g [...] new 75007e3943 366: onsuccess: #2186: 1: Success after binutils/gcc/linux/g [...] new 80ddaa36ff 367: onsuccess: #2187: 1: Success after binutils/gcc/gdb: 14 [...] new fc9efe59cb 368: onsuccess: #2188: 1: Success after binutils/gcc/linux/g [...] new ac9e9a7a3d 369: onsuccess: #2189: 1: Success after binutils/gcc/linux/g [...] new 50e81a3355 370: onsuccess: #2190: 1: Success after binutils/gcc/linux/g [...] new 2e55f067ee 371: onsuccess: #2191: 1: Success after binutils/gcc/gdb: 10 [...] new 45a8c1b1ed 372: onsuccess: #2192: 1: Success after binutils/gcc/linux/g [...] new e52db4ec12 373: onsuccess: #2193: 1: Success after binutils/gcc/glibc/g [...] new fb3fc81d3d 374: onsuccess: #2194: 1: Success after binutils/gcc/linux/g [...] new b7eaaab026 375: onsuccess: #2195: 1: Success after binutils/gcc/gdb/qem [...] new ecbe6691dd 376: onsuccess: #2197: 1: Success after binutils/gcc/linux/g [...] new 66ddb0f1f3 377: onsuccess: #2198: 1: Success after binutils/gcc/gdb: 3 commits new 6fcd91f143 378: onsuccess: #2199: 1: Success after binutils/gdb: 4 commits new e88389ba0c 379: onsuccess: #2200: 1: Success after binutils/gcc/linux/g [...] new bdd2721405 380: onsuccess: #2201: 1: Success after binutils/gcc/linux/g [...] new 3c0e542fb2 381: onsuccess: #2202: 1: Success after glibc-2.37.9000-17-g [...] new 58df7280cb 382: onsuccess: #2203: 1: Success after gcc/qemu: 42 commits new 908c26ad30 383: onsuccess: #2204: 1: Success after binutils/gcc/linux/g [...] new d32595b01a 384: onsuccess: #2205: 1: Success after gcc: 2 commits new e1a2098c78 385: onsuccess: #2206: 1: Success after binutils/gcc/glibc/g [...] new 3cee86c8d7 386: onsuccess: #2207: 1: Success after binutils/gcc/linux/g [...] new b508bc3331 387: onsuccess: #2208: 1: Success after gcc: 2 commits new 2dcc2c55dc 388: onsuccess: #2209: 1: Success after binutils/gcc/glibc/g [...] new 59c54a702e 389: onsuccess: #2210: 1: Success after binutils/gcc/linux/g [...] new d284ec9977 390: onsuccess: #2211: 1: Success after binutils/gcc/linux/g [...] new b76536c67f 391: onsuccess: #2212: 1: Success after binutils/gcc/gdb/qem [...] new ee4260917c 392: onsuccess: #2213: 1: Success after binutils/gcc/glibc/g [...] new 5102304b74 393: onsuccess: #2214: 1: Success after binutils/gcc/gdb: 12 [...] new fb4997bb24 394: onsuccess: #2215: 1: Success after binutils/gcc/gdb: 8 commits new 9fd40cb8a0 395: onsuccess: #2216: 1: Success after binutils/gcc/linux/g [...] new 6b07ec372e 396: onsuccess: #2217: 1: Success after binutils/gcc/linux/g [...] new 1ded06039c 397: onsuccess: #2218: 1: Success after binutils/gcc/linux/g [...] new 2c07d109cf 398: onsuccess: #2219: 1: Success after binutils/gcc/gdb/qem [...] new 03a87029d1 399: onsuccess: #2220: 1: Success after binutils/gcc/linux/g [...] new f8d90a4dcf 400: onsuccess: #2221: 1: Success after binutils/gcc/linux/g [...] new 859a026acf 401: onsuccess: #2222: 1: Success after binutils/gcc/gdb: 10 [...] new fcdf578a29 402: onsuccess: #2223: 1: Success after binutils/gcc/gdb: 10 [...] new 060d8d1b8b 403: onsuccess: #2224: 1: Success after binutils/gcc/linux/g [...] new f8b7616bca 404: onsuccess: #2225: 1: Success after binutils/gcc/gdb: 10 [...] new 4ad8f672bd 405: onsuccess: #2226: 1: Success after gcc/glibc: 39 commits new 4240f08b20 406: onsuccess: #2227: 1: Success after binutils/linux/glibc [...] new 076ad94e72 407: onsuccess: #2228: 1: Success after binutils/gcc/linux/g [...] new 44db632fab 408: onsuccess: #2229: 1: Success after binutils/gcc/gdb: 26 [...] new 9381ee9204 409: onsuccess: #2230: 1: Success after binutils/gcc/glibc/g [...] new 5cbd8b1461 410: onsuccess: #2231: 1: Success after binutils/gcc/linux/g [...] new 6e8653d754 411: onsuccess: #2232: 1: Success after gcc: 3 commits new 4477b2a552 412: onsuccess: #2233: 1: Success after binutils/gcc/glibc/g [...] new fb276c9c89 413: onsuccess: #2234: 1: Success after binutils/gcc/linux/g [...] new 2f6b5e6c14 414: onsuccess: #2235: 1: Success after binutils/gcc/gdb: 13 [...] new 13ce17e391 415: onsuccess: #2236: 1: Success after binutils/gcc/gdb: 14 [...] new 8c27d90051 416: onsuccess: #2237: 1: Success after binutils/gcc/glibc/g [...] new 6dde73b467 417: onsuccess: #2238: 1: Success after binutils/gcc/linux/g [...] new ace6656682 418: onsuccess: #2239: 1: Success after binutils/gcc/gdb: 5 commits new f1cb68759b 419: onsuccess: #2243: 1: Success after binutils/gcc/linux/g [...] new 27d68f331a 420: onsuccess: #2244: 1: Success after gcc/glibc: 5 commits new 52e4c947dd 421: onsuccess: #2245: 1: Success after binutils/gcc/glibc/g [...] new 57aa625ec8 422: onsuccess: #2246: 1: Success after binutils/gcc/linux/g [...] new ae63a21510 423: onsuccess: #2247: 1: Success after gcc/linux: 8 commits new 1f84815235 424: onsuccess: #2248: 1: Success after gcc: 6 commits new 289d0d238c 425: onsuccess: #2249: 1: Success after binutils/gcc/linux/g [...] new 42d4817506 426: onsuccess: #2250: 1: Success after binutils/linux/gdb: [...] new 7ec7fadd2d 427: onsuccess: #2251: 1: Success after binutils/gcc/linux/g [...] new 7604afda5b 428: onsuccess: #2252: 1: Success after binutils/gdb: 2 commits new 11b69f6a19 429: onsuccess: #2253: 1: Success after binutils/gcc/glibc/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 (bbf8cbdfea) \ 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 1820 -> 1752 bytes 02-prepare_abe/console.log.xz | Bin 2768 -> 2772 bytes 03-build_abe-binutils/console.log.xz | Bin 30696 -> 30652 bytes 04-build_abe-stage1/console.log.xz | Bin 88660 -> 88872 bytes 06-build_abe-linux/console.log.xz | Bin 8324 -> 8316 bytes 07-build_abe-glibc/console.log.xz | Bin 235344 -> 235608 bytes 08-build_abe-stage2/console.log.xz | Bin 225084 -> 225532 bytes 09-build_abe-gdb/console.log.xz | Bin 38580 -> 38616 bytes 10-build_abe-qemu/console.log.xz | Bin 31596 -> 31964 bytes 11-build_abe-dejagnu/console.log.xz | Bin 3800 -> 3816 bytes 12-build_abe-check_gcc/console.log.xz | Bin 2584 -> 3080 bytes 13-check_regression/console.log.xz | Bin 4956 -> 7116 bytes 13-check_regression/results.compare | 16 ++++----- 13-check_regression/results.compare2 | 56 +++++++++++++++++++++++++---- 14-update_baseline/console.log | 64 +++++++++++++++++----------------- dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- git/gdb_rev | 2 +- git/glibc_rev | 2 +- git/qemu_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 2 +- mail/mail-subject.txt | 2 +- manifest.sh | 44 +++++++++++------------ sumfiles/g++.log.xz | Bin 2664680 -> 2653840 bytes sumfiles/g++.sum | 18 ++++++++-- sumfiles/gcc.log.xz | Bin 2204656 -> 2216976 bytes sumfiles/gcc.sum | 18 +++++++++- sumfiles/gfortran.log.xz | Bin 891288 -> 892560 bytes sumfiles/libatomic.log.xz | Bin 2264 -> 2260 bytes sumfiles/libatomic.sum | 2 +- sumfiles/libgomp.log.xz | Bin 216972 -> 217072 bytes sumfiles/libgomp.sum | 2 +- sumfiles/libitm.log.xz | Bin 2664 -> 2672 bytes sumfiles/libitm.sum | 2 +- sumfiles/libstdc++.log.xz | Bin 442784 -> 436008 bytes sumfiles/libstdc++.sum | 21 ++++------- 38 files changed, 163 insertions(+), 98 deletions(-)