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-aarch64 in repository toolchain/ci/base-artifacts.

discards af1a875236 318: onsuccess: #2568: 1: Success after binutils/gdb: 142 commits discards 51c1f81b15 317: onsuccess: #2567: 1: Success after binutils/gcc/linux/g [...] discards c13e19695f 316: onsuccess: #2566: 1: Success after binutils/gcc/gdb/qem [...] discards 8e8b06080c 315: onsuccess: #2565: 1: Success after binutils/gcc/gdb/qem [...] discards 47647e4ed8 314: onsuccess: #2564: 1: Success after binutils/gcc/gdb: 5 commits discards 8c58a92436 313: onsuccess: #2563: 1: Success after linux/qemu: 44 commits discards bbf4b68801 312: onsuccess: #2562: 1: Success after binutils/gdb: 2 commits discards 809c5e9a07 311: onsuccess: #2561: 1: Success after binutils/gcc/linux/g [...] discards 752911b509 310: onsuccess: #2560: 1: Success after v7.2.0-493-g052e6534 [...] discards a7c11c6ed5 309: onsuccess: #2559: 1: Success after binutils/gcc/linux/g [...] discards a50aa760fe 308: onsuccess: #2558: 1: Success after binutils/gcc/linux/g [...] discards bf0af3d6b0 307: onsuccess: #2557: 1: Success after binutils/gcc/gdb/qem [...] discards 1ff8daea1c 306: onsuccess: #2556: 1: Success after binutils/gcc/gdb: 5 commits discards a8e1e45d13 305: onsuccess: #2555: 1: Success after binutils/gcc/gdb: 3 commits discards 9ea88e469a 304: onsuccess: #2554: 1: Success after binutils/gcc/linux/g [...] discards 9e71720586 303: onsuccess: #2553: 1: Success after binutils/gcc/gdb/qem [...] discards 2e9d20684f 302: onsuccess: #2552: 1: Success after binutils/gcc/gdb: 8 commits discards d158e8df34 301: onsuccess: #2551: 1: Success after binutils/gcc/linux/g [...] discards aafa0f4f6a 300: onsuccess: #2550: 1: Success after binutils/gcc/linux/g [...] discards 744cd33508 299: onsuccess: #2549: 1: Success after binutils/gcc/gdb/qem [...] discards 00d82a2e4d 298: onsuccess: #2548: 1: Success after binutils/gdb: 6 commits discards 125d98785e 297: onsuccess: #2547: 1: Success after binutils/gcc/glibc/g [...] discards 0338c434c0 296: onsuccess: #2546: 1: Success after binutils/gcc/gdb: 79 [...] discards 5b550a5bcd 295: onsuccess: #2545: 1: Success after linux: 10 commits discards 861d201a23 294: onsuccess: #2544: 1: Success after glibc-2.36.9000-416- [...] discards 80073e4a4e 293: onsuccess: #2542: 1: Success after gcc: 5 commits discards f80d6b7429 292: onsuccess: #2541: 1: Success after binutils: 13 commits discards d4771978ec 291: onsuccess: #2539: 1: Success after binutils/gcc/glibc/g [...] discards 6ad903976a 290: onsuccess: #2538: 1: Success after binutils/gcc/glibc/g [...] discards 951f64b4ae 289: onsuccess: #2537: 1: Success after binutils/gcc/linux/g [...] discards 24753cbed6 288: onsuccess: #2536: 1: Success after binutils/gcc/linux/g [...] discards d7c56cdd81 287: onsuccess: #2535: 1: Success after binutils/gcc/gdb: 15 [...] discards 476cfbf07b 286: onsuccess: #2534: 1: Success after binutils/gcc/gdb: 4 commits discards dc3fb2ab78 285: onsuccess: #2533: 1: Success after gcc/linux: 13 commits discards 33f831a4a4 284: onsuccess: #2532: 1: Success after binutils/gdb: 10 commits discards 6e7b326a94 283: onsuccess: #2531: 1: Success after binutils/gdb: 16 commits discards 1039c686a0 282: onsuccess: #2530: 1: Success after binutils/gcc/gdb: 3 commits discards 15bb63134e 281: onsuccess: #2529: 1: Success after binutils/gcc/linux/g [...] discards 3c0ad7c9f4 280: onsuccess: #2528: 1: Success after binutils/gcc/gdb: 7 commits discards 771c3d50a9 279: onsuccess: #2527: 1: Success after basepoints/gcc-13-49 [...] discards 0caeda47c2 278: onsuccess: #2526: 1: Success after binutils/gcc/linux/g [...] discards afd2c9b6e5 277: onsuccess: #2525: 1: Success after gcc/linux: 60 commits discards fa7a72d0a6 276: onsuccess: #2524: 1: Success after binutils/gdb: 2 commits discards be32bbc2f0 275: onsuccess: #2523: 1: Success after basepoints/gcc-13-49 [...] discards 3b6e2cceb3 274: onsuccess: #2522: 1: Success after binutils/gcc/gdb: 8 commits discards 8165f83e61 273: onsuccess: #2521: 1: Success after gcc: 2 commits discards 6c57fcb648 272: onsuccess: #2520: 1: Success after basepoints/gcc-13-49 [...] discards d7ad8a1d9e 271: onsuccess: #2519: 1: Success after binutils/gcc/gdb: 23 [...] discards c38632b436 270: onsuccess: #2518: 1: Success after binutils/gcc/gdb: 19 [...] discards 149744ca23 269: onsuccess: #2517: 1: Success after binutils/gcc/gdb: 3 commits discards 3257957ebc 268: onsuccess: #2516: 1: Success after binutils/gcc/gdb: 3 commits discards 43e5211921 267: onsuccess: #2515: 1: Success after binutils/gdb: 4 commits discards 335e3e3faa 266: onsuccess: #2514: 1: Success after binutils/gcc/linux/g [...] discards 77594aadc3 265: onsuccess: #2513: 1: Success after binutils/gdb: 4 commits discards 2eb364b450 264: onsuccess: #2512: 1: Success after binutils/gcc/gdb: 21 [...] discards 492095e398 263: onsuccess: #2511: 1: Success after binutils/gdb: 16 commits discards 3c0f2ce79d 262: onsuccess: #2510: 1: Success after binutils/gcc/gdb: 10 [...] discards 0198cd97c3 261: onsuccess: #2509: 1: Success after binutils/gcc/gdb: 3 commits discards 8dcb92dbd7 260: onsuccess: #2508: 1: Success after binutils/gcc/linux/g [...] discards c065fa83e3 259: onsuccess: #2507: 1: Success after binutils/gcc/gdb: 49 [...] discards d136dfb54d 258: onsuccess: #2506: 1: Success after binutils/gcc/gdb: 49 [...] discards 68f9b5bf12 257: onsuccess: #2505: 1: Success after binutils/gcc/gdb: 47 [...] discards 48c2ad6147 256: onsuccess: #2504: 1: Success after binutils/gcc/linux/g [...] discards b741f98923 255: onsuccess: #2503: 1: Success after binutils/gcc/glibc/g [...] discards 915cbdb54b 254: onsuccess: #2502: 1: Success after binutils/gcc/gdb: 37 [...] discards 2fe835a4ba 253: onsuccess: #2501: 1: Success after binutils/gcc/linux/g [...] discards 281882c045 252: onsuccess: #2500: 1: Success after binutils/gcc/linux/g [...] discards 5cbff4b11d 251: onsuccess: #2499: 1: Success after binutils/gcc/gdb/qem [...] discards 18261da0bf 250: onsuccess: #2498: 1: Success after binutils/gcc/gdb: 68 [...] discards 2418777f6c 249: onsuccess: #2497: 1: Success after binutils/gcc/gdb: 16 [...] discards 06dcd50f5c 248: onsuccess: #2496: 1: Success after binutils/gcc/glibc/g [...] discards dee92e82a9 247: onsuccess: #2495: 1: Success after binutils/gcc/linux/g [...] discards 17044d4e23 246: onsuccess: #2494: 1: Success after binutils/gcc/gdb: 6 commits discards a7ab120ea1 245: onsuccess: #2493: 1: Success after binutils/gcc/gdb: 9 commits discards d81240649a 244: onsuccess: #2492: 1: Success after binutils/gcc/linux/g [...] discards 82a0bd94ac 243: onsuccess: #2491: 1: Success after binutils/gcc/linux/g [...] discards e23dbec789 242: onsuccess: #2490: 1: Success after binutils/gcc/gdb: 16 [...] discards f4bfc91994 241: onsuccess: #2489: 1: Success after binutils/gcc/glibc/g [...] discards 5b880aa051 240: onsuccess: #2488: 1: Success after gcc/qemu: 3 commits discards c5d3a46c10 239: onsuccess: #2487: 1: Success after binutils/gcc/gdb: 5 commits discards 5b1b7bb053 238: onsuccess: #2486: 1: Success after binutils/gcc/gdb: 5 commits discards eb4d57e3c2 237: onsuccess: #2485: 1: Success after binutils/gcc/gdb/qem [...] discards 163e80c9aa 236: onsuccess: #2484: 1: Success after gcc: 2 commits discards 5128482de5 235: onsuccess: #2483: 1: Success after linux: 108 commits discards 7ee9e14722 234: onsuccess: #2482: 1: Success after binutils/gdb: 18 commits discards f5b5635605 233: onsuccess: #2481: 1: Success after binutils/gcc/gdb/qem [...] discards 7880cd5e5d 232: onsuccess: #2480: 1: Success after binutils/gcc/linux/g [...] discards 6bec1e1b0e 231: onsuccess: #2479: 1: Success after binutils/gcc/gdb/qem [...] discards f05d9367da 230: onsuccess: #2477: 1: Success after binutils/gcc/linux/g [...] discards 56c680b7fe 229: onsuccess: #2476: 1: Success after binutils/gcc/linux/g [...] discards 841b7c5572 228: onsuccess: #2475: 1: Success after binutils/gcc/gdb/qem [...] discards 73fe2b20b5 227: onsuccess: #2474: 1: Success after gcc: 2 commits discards 19b3dc2795 226: onsuccess: #2473: 1: Success after binutils/gcc/linux/g [...] discards fb0794df88 225: onsuccess: #2472: 1: Success after gcc/linux: 532 commits discards ee2f5b33be 224: onsuccess: #2471: 1: Success after binutils/gcc/gdb: 34 [...] discards 2462803077 223: onsuccess: #2470: 1: Success after binutils/gcc/linux/g [...] discards adada62d3b 222: onsuccess: #2469: 1: Success after binutils/gcc/linux/g [...] discards 359eb85615 221: onsuccess: #2467: 1: Success after binutils: 3 commits discards eaf0c5c683 220: onsuccess: #2465: 1: Success after linux: 572 commits discards 30d3ef79dc 219: onsuccess: #2463: 1: Success after binutils: 3 commits discards 766de876df 218: onsuccess: #2461: 1: Success after linux: 916 commits new 543abcacfc 218: onsuccess: #2461: 1: Success after linux: 916 commits new 9c2a53fb4c 219: onsuccess: #2463: 1: Success after binutils: 3 commits new 15aff42065 220: onsuccess: #2465: 1: Success after linux: 572 commits new c6e30b27a7 221: onsuccess: #2467: 1: Success after binutils: 3 commits new 198297d958 222: onsuccess: #2469: 1: Success after binutils/gcc/linux/g [...] new edf3a54c1a 223: onsuccess: #2470: 1: Success after binutils/gcc/linux/g [...] new 574fabe8ff 224: onsuccess: #2471: 1: Success after binutils/gcc/gdb: 34 [...] new a3a8b04e89 225: onsuccess: #2472: 1: Success after gcc/linux: 532 commits new 88f3304b3a 226: onsuccess: #2473: 1: Success after binutils/gcc/linux/g [...] new 981f7ffb79 227: onsuccess: #2474: 1: Success after gcc: 2 commits new c010cffeb7 228: onsuccess: #2475: 1: Success after binutils/gcc/gdb/qem [...] new 013d1665d3 229: onsuccess: #2476: 1: Success after binutils/gcc/linux/g [...] new 8530f1bede 230: onsuccess: #2477: 1: Success after binutils/gcc/linux/g [...] new 9ed88d0db7 231: onsuccess: #2479: 1: Success after binutils/gcc/gdb/qem [...] new c2400cb40c 232: onsuccess: #2480: 1: Success after binutils/gcc/linux/g [...] new 394216dfc6 233: onsuccess: #2481: 1: Success after binutils/gcc/gdb/qem [...] new 823e6aa001 234: onsuccess: #2482: 1: Success after binutils/gdb: 18 commits new a873cd6fbe 235: onsuccess: #2483: 1: Success after linux: 108 commits new 0868bb2058 236: onsuccess: #2484: 1: Success after gcc: 2 commits new d54166c5ed 237: onsuccess: #2485: 1: Success after binutils/gcc/gdb/qem [...] new e4a56a294b 238: onsuccess: #2486: 1: Success after binutils/gcc/gdb: 5 commits new a1bb928fd1 239: onsuccess: #2487: 1: Success after binutils/gcc/gdb: 5 commits new 34883abeef 240: onsuccess: #2488: 1: Success after gcc/qemu: 3 commits new 66b4ce9860 241: onsuccess: #2489: 1: Success after binutils/gcc/glibc/g [...] new 737409c507 242: onsuccess: #2490: 1: Success after binutils/gcc/gdb: 16 [...] new bf2cd98de2 243: onsuccess: #2491: 1: Success after binutils/gcc/linux/g [...] new 9e7eddc48c 244: onsuccess: #2492: 1: Success after binutils/gcc/linux/g [...] new 02eec532fa 245: onsuccess: #2493: 1: Success after binutils/gcc/gdb: 9 commits new 3be15f4539 246: onsuccess: #2494: 1: Success after binutils/gcc/gdb: 6 commits new 471a753fd9 247: onsuccess: #2495: 1: Success after binutils/gcc/linux/g [...] new a7696a9c2d 248: onsuccess: #2496: 1: Success after binutils/gcc/glibc/g [...] new 7d20209c8c 249: onsuccess: #2497: 1: Success after binutils/gcc/gdb: 16 [...] new bdb0342264 250: onsuccess: #2498: 1: Success after binutils/gcc/gdb: 68 [...] new 6751edf019 251: onsuccess: #2499: 1: Success after binutils/gcc/gdb/qem [...] new 0ea0d5abd6 252: onsuccess: #2500: 1: Success after binutils/gcc/linux/g [...] new 7c59ec406e 253: onsuccess: #2501: 1: Success after binutils/gcc/linux/g [...] new dbf09d9881 254: onsuccess: #2502: 1: Success after binutils/gcc/gdb: 37 [...] new 0a51f879c1 255: onsuccess: #2503: 1: Success after binutils/gcc/glibc/g [...] new da0e3a7468 256: onsuccess: #2504: 1: Success after binutils/gcc/linux/g [...] new ad09c106f5 257: onsuccess: #2505: 1: Success after binutils/gcc/gdb: 47 [...] new ac4e80df9e 258: onsuccess: #2506: 1: Success after binutils/gcc/gdb: 49 [...] new d47afe1c42 259: onsuccess: #2507: 1: Success after binutils/gcc/gdb: 49 [...] new d6cfa955f7 260: onsuccess: #2508: 1: Success after binutils/gcc/linux/g [...] new 4f8c885529 261: onsuccess: #2509: 1: Success after binutils/gcc/gdb: 3 commits new f7a00b4afc 262: onsuccess: #2510: 1: Success after binutils/gcc/gdb: 10 [...] new b34f3ec0d7 263: onsuccess: #2511: 1: Success after binutils/gdb: 16 commits new 9fcf230e68 264: onsuccess: #2512: 1: Success after binutils/gcc/gdb: 21 [...] new 7d9f8d100d 265: onsuccess: #2513: 1: Success after binutils/gdb: 4 commits new 30d5c56797 266: onsuccess: #2514: 1: Success after binutils/gcc/linux/g [...] new 597d8ed7ad 267: onsuccess: #2515: 1: Success after binutils/gdb: 4 commits new baabea02c5 268: onsuccess: #2516: 1: Success after binutils/gcc/gdb: 3 commits new 8040199828 269: onsuccess: #2517: 1: Success after binutils/gcc/gdb: 3 commits new 4a96d31f94 270: onsuccess: #2518: 1: Success after binutils/gcc/gdb: 19 [...] new 4d6020e621 271: onsuccess: #2519: 1: Success after binutils/gcc/gdb: 23 [...] new c67128322b 272: onsuccess: #2520: 1: Success after basepoints/gcc-13-49 [...] new bdfd59cc5c 273: onsuccess: #2521: 1: Success after gcc: 2 commits new 08be78bf88 274: onsuccess: #2522: 1: Success after binutils/gcc/gdb: 8 commits new 3ceb6ade38 275: onsuccess: #2523: 1: Success after basepoints/gcc-13-49 [...] new 6b4b6910b1 276: onsuccess: #2524: 1: Success after binutils/gdb: 2 commits new 7b2467367d 277: onsuccess: #2525: 1: Success after gcc/linux: 60 commits new 6086cac353 278: onsuccess: #2526: 1: Success after binutils/gcc/linux/g [...] new e7c5123089 279: onsuccess: #2527: 1: Success after basepoints/gcc-13-49 [...] new d6d4b47395 280: onsuccess: #2528: 1: Success after binutils/gcc/gdb: 7 commits new d219b0879a 281: onsuccess: #2529: 1: Success after binutils/gcc/linux/g [...] new ede1afc48d 282: onsuccess: #2530: 1: Success after binutils/gcc/gdb: 3 commits new 62e56ff525 283: onsuccess: #2531: 1: Success after binutils/gdb: 16 commits new 83b5b3716a 284: onsuccess: #2532: 1: Success after binutils/gdb: 10 commits new be40b987cd 285: onsuccess: #2533: 1: Success after gcc/linux: 13 commits new 45ceb11048 286: onsuccess: #2534: 1: Success after binutils/gcc/gdb: 4 commits new c5a18cf55f 287: onsuccess: #2535: 1: Success after binutils/gcc/gdb: 15 [...] new 60740a212c 288: onsuccess: #2536: 1: Success after binutils/gcc/linux/g [...] new 75d2ea6ffa 289: onsuccess: #2537: 1: Success after binutils/gcc/linux/g [...] new ecfe85eb6c 290: onsuccess: #2538: 1: Success after binutils/gcc/glibc/g [...] new 85d57fb2fc 291: onsuccess: #2539: 1: Success after binutils/gcc/glibc/g [...] new 2ebb9797f4 292: onsuccess: #2541: 1: Success after binutils: 13 commits new ba8e867e16 293: onsuccess: #2542: 1: Success after gcc: 5 commits new ea8df6d29f 294: onsuccess: #2544: 1: Success after glibc-2.36.9000-416- [...] new 22ee4087cf 295: onsuccess: #2545: 1: Success after linux: 10 commits new 1f190ce0f7 296: onsuccess: #2546: 1: Success after binutils/gcc/gdb: 79 [...] new abcbd798bd 297: onsuccess: #2547: 1: Success after binutils/gcc/glibc/g [...] new 50fa715081 298: onsuccess: #2548: 1: Success after binutils/gdb: 6 commits new ef357d2679 299: onsuccess: #2549: 1: Success after binutils/gcc/gdb/qem [...] new fb3d86d8b9 300: onsuccess: #2550: 1: Success after binutils/gcc/linux/g [...] new 17295f7178 301: onsuccess: #2551: 1: Success after binutils/gcc/linux/g [...] new beac10c6c1 302: onsuccess: #2552: 1: Success after binutils/gcc/gdb: 8 commits new 1c772e68e6 303: onsuccess: #2553: 1: Success after binutils/gcc/gdb/qem [...] new 75ff9650ad 304: onsuccess: #2554: 1: Success after binutils/gcc/linux/g [...] new 144e6ad8e4 305: onsuccess: #2555: 1: Success after binutils/gcc/gdb: 3 commits new 983bb3f09d 306: onsuccess: #2556: 1: Success after binutils/gcc/gdb: 5 commits new bda2f77fd3 307: onsuccess: #2557: 1: Success after binutils/gcc/gdb/qem [...] new cc3d319658 308: onsuccess: #2558: 1: Success after binutils/gcc/linux/g [...] new fd45233ee7 309: onsuccess: #2559: 1: Success after binutils/gcc/linux/g [...] new 51bc1df023 310: onsuccess: #2560: 1: Success after v7.2.0-493-g052e6534 [...] new ae1ae8ed80 311: onsuccess: #2561: 1: Success after binutils/gcc/linux/g [...] new 81303f4e12 312: onsuccess: #2562: 1: Success after binutils/gdb: 2 commits new 2118ac187b 313: onsuccess: #2563: 1: Success after linux/qemu: 44 commits new 305ade2d1c 314: onsuccess: #2564: 1: Success after binutils/gcc/gdb: 5 commits new 103a470705 315: onsuccess: #2565: 1: Success after binutils/gcc/gdb/qem [...] new 1242e43237 316: onsuccess: #2566: 1: Success after binutils/gcc/gdb/qem [...] new 42d4b97ebd 317: onsuccess: #2567: 1: Success after binutils/gcc/linux/g [...] new f7720aa5f1 318: onsuccess: #2568: 1: Success after binutils/gdb: 142 commits new e0170e96cd 319: onsuccess: #2569: 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 (af1a875236) \ 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 1780 -> 1760 bytes 02-prepare_abe/console.log.xz | Bin 2764 -> 2756 bytes 03-build_abe-binutils/console.log.xz | Bin 32128 -> 32224 bytes 04-build_abe-stage1/console.log.xz | Bin 72984 -> 73156 bytes 06-build_abe-linux/console.log.xz | Bin 8752 -> 8620 bytes 07-build_abe-glibc/console.log.xz | Bin 244460 -> 244228 bytes 08-build_abe-stage2/console.log.xz | Bin 204184 -> 204192 bytes 09-build_abe-gdb/console.log.xz | Bin 39684 -> 39628 bytes 10-build_abe-qemu/console.log.xz | Bin 31504 -> 31540 bytes 11-build_abe-dejagnu/console.log.xz | Bin 3876 -> 3884 bytes 12-build_abe-check_gcc/console.log.xz | Bin 2628 -> 2912 bytes 13-check_regression/console.log.xz | Bin 6036 -> 7156 bytes 13-check_regression/extra-bisect-params | 2 +- 13-check_regression/fails.sum | 26 +- 13-check_regression/mail-body.txt | 127 +- 13-check_regression/results.compare | 64 +- 13-check_regression/results.compare2 | 81 +- 13-check_regression/results.regressions | 64 +- 14-update_baseline/console.log | 40 +- 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 | 129 +- mail/mail-subject.txt | 2 +- manifest.sh | 38 +- results | 64 +- sumfiles/g++.log.xz | Bin 3407620 -> 3420976 bytes sumfiles/g++.sum | 26 +- sumfiles/gcc.log.xz | Bin 3033448 -> 3039544 bytes sumfiles/gcc.sum | 3951 ++++++++++++++++--------------- sumfiles/gfortran.log.xz | Bin 1038640 -> 1039508 bytes sumfiles/gfortran.sum | 2 +- sumfiles/libatomic.log.xz | Bin 2296 -> 2288 bytes sumfiles/libatomic.sum | 2 +- sumfiles/libgomp.log.xz | Bin 214780 -> 214788 bytes sumfiles/libgomp.sum | 2 +- sumfiles/libitm.log.xz | Bin 2700 -> 2700 bytes sumfiles/libitm.sum | 2 +- sumfiles/libstdc++.log.xz | Bin 431500 -> 434264 bytes sumfiles/libstdc++.sum | 6 +- 43 files changed, 2272 insertions(+), 2368 deletions(-)