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 2cee3e4e42 361: onsuccess: #2611: 1: Success after binutils/gcc/linux/g [...] discards fe13930652 360: onsuccess: #2610: 1: Success after binutils/gcc/gdb/qem [...] discards 7070ef7746 359: onsuccess: #2609: 1: Success after binutils/gcc/linux/g [...] discards c593148616 358: onsuccess: #2608: 1: Success after binutils/gcc/glibc/g [...] discards afc6569387 357: onsuccess: #2607: 1: Success after binutils/gcc/linux/g [...] discards 4ef8778d3f 356: onsuccess: #2606: 1: Success after binutils/gcc/linux/g [...] discards 3f6964891e 355: onsuccess: #2605: 1: Success after binutils/gcc/linux/g [...] discards 4b910e17de 354: onsuccess: #2604: 1: Success after binutils/gcc/glibc/g [...] discards 74cf406cbf 353: onsuccess: #2603: 1: Success after binutils/gcc/linux/g [...] discards eddc8cb2d0 352: onsuccess: #2602: 1: Success after binutils/gcc/linux/g [...] discards 98bfd94f06 351: onsuccess: #2601: 1: Success after binutils/gcc/gdb: 17 [...] discards 6462d63181 350: onsuccess: #2600: 1: Success after binutils/gcc/linux/g [...] discards c44fc7c203 349: onsuccess: #2599: 1: Success after binutils/gcc/linux/g [...] discards e25818683a 348: onsuccess: #2598: 1: Success after binutils/gcc/linux/g [...] discards 6e87d11791 347: onsuccess: #2597: 1: Success after binutils/gcc/linux/g [...] discards e70a486d03 346: onsuccess: #2596: 1: Success after binutils/gcc/linux/g [...] discards b7a1535e04 345: onsuccess: #2595: 1: Success after binutils/gcc/linux/g [...] discards 2e5e6f1d12 344: onsuccess: #2594: 1: Success after binutils/gcc/linux/g [...] discards a7a286c1e8 343: onsuccess: #2593: 1: Success after binutils/gcc/glibc/g [...] discards 214d64aa8b 342: onsuccess: #2592: 1: Success after binutils/gcc/linux/g [...] discards 12457734e9 341: onsuccess: #2591: 1: Success after binutils/gcc/linux/g [...] discards 9cc7b851a6 340: onsuccess: #2590: 1: Success after binutils/gcc/gdb/qem [...] discards 8cb99e6e15 339: onsuccess: #2589: 1: Success after binutils/gcc/glibc/g [...] discards 89fbaea43b 338: onsuccess: #2588: 1: Success after binutils/gcc/linux/g [...] discards 9516bc8f0d 337: onsuccess: #2587: 1: Success after binutils/gdb: 4 commits discards b318567084 336: onsuccess: #2586: 1: Success after binutils/gcc/gdb: 22 [...] discards b59512aa3b 335: onsuccess: #2585: 1: Success after binutils/gcc/linux/g [...] discards 4f70e51d24 334: onsuccess: #2584: 1: Success after gcc/linux: 15 commits discards aafaa08496 333: onsuccess: #2583: 1: Success after binutils/gcc/linux/g [...] discards 4673500cb2 332: onsuccess: #2582: 1: Success after binutils/gcc/linux/g [...] discards 2bd0196276 331: onsuccess: #2581: 1: Success after binutils/gcc/linux/g [...] discards 1ffb9b4ab5 330: onsuccess: #2580: 1: Success after basepoints/gcc-13-51 [...] discards 6a3ec9e172 329: onsuccess: #2579: 1: Success after binutils/gcc/linux/g [...] discards ef6d2b437f 328: onsuccess: #2578: 1: Success after binutils/gcc/glibc/g [...] discards bcc8564b40 327: onsuccess: #2577: 1: Success after binutils/gcc/linux/g [...] discards ea3ab8a648 326: onsuccess: #2576: 1: Success after binutils/gdb: 6 commits discards 8cefb53f1f 325: onsuccess: #2575: 1: Success after binutils/gcc/linux/g [...] discards eb93949b39 324: onsuccess: #2574: 1: Success after binutils/gcc/glibc/g [...] discards 31cc0c8f2d 323: onsuccess: #2573: 1: Success after binutils/gcc/gdb: 18 [...] discards e998fcdd7c 322: onsuccess: #2572: 1: Success after binutils/gcc/gdb: 6 commits discards 04733f7b88 321: onsuccess: #2571: 1: Success after binutils/gcc/gdb: 19 [...] discards ed7d857279 320: onsuccess: #2570: 1: Success after binutils/gcc/linux/g [...] discards db889c54d8 319: onsuccess: #2569: 1: Success after binutils/gcc/linux/g [...] discards de396175a9 318: onsuccess: #2568: 1: Success after binutils/gdb: 142 commits discards 58fca178f3 317: onsuccess: #2567: 1: Success after binutils/gcc/linux/g [...] discards 04340573ad 316: onsuccess: #2566: 1: Success after binutils/gcc/gdb/qem [...] discards c224df5cea 315: onsuccess: #2565: 1: Success after binutils/gcc/gdb/qem [...] discards d506dd3510 314: onsuccess: #2564: 1: Success after binutils/gcc/gdb: 5 commits discards 013ba78b8b 313: onsuccess: #2563: 1: Success after linux/qemu: 44 commits discards 31f1c170f4 312: onsuccess: #2562: 1: Success after binutils/gdb: 2 commits discards d9723501b1 311: onsuccess: #2561: 1: Success after binutils/gcc/linux/g [...] discards 7727c4af8f 310: onsuccess: #2560: 1: Success after v7.2.0-493-g052e6534 [...] discards 1d3945ae3a 309: onsuccess: #2559: 1: Success after binutils/gcc/linux/g [...] discards 740396e9a6 308: onsuccess: #2558: 1: Success after binutils/gcc/linux/g [...] discards 660452b106 307: onsuccess: #2557: 1: Success after binutils/gcc/gdb/qem [...] discards 393b538219 306: onsuccess: #2556: 1: Success after binutils/gcc/gdb: 5 commits discards 4c21113434 305: onsuccess: #2555: 1: Success after binutils/gcc/gdb: 3 commits discards 57f581dd6a 304: onsuccess: #2554: 1: Success after binutils/gcc/linux/g [...] discards b0c0dde150 303: onsuccess: #2553: 1: Success after binutils/gcc/gdb/qem [...] discards 113f1a886d 302: onsuccess: #2552: 1: Success after binutils/gcc/gdb: 8 commits discards 55b8a490b9 301: onsuccess: #2551: 1: Success after binutils/gcc/linux/g [...] discards 055d258c3f 300: onsuccess: #2550: 1: Success after binutils/gcc/linux/g [...] discards 697e959622 299: onsuccess: #2549: 1: Success after binutils/gcc/gdb/qem [...] discards 9a9e1aa4b4 298: onsuccess: #2548: 1: Success after binutils/gdb: 6 commits discards 5223338869 297: onsuccess: #2547: 1: Success after binutils/gcc/glibc/g [...] discards 01e7b4b0d9 296: onsuccess: #2546: 1: Success after binutils/gcc/gdb: 79 [...] discards 2d93b541b6 295: onsuccess: #2545: 1: Success after linux: 10 commits discards 2fb62d1b4c 294: onsuccess: #2544: 1: Success after glibc-2.36.9000-416- [...] discards 7172291842 293: onsuccess: #2542: 1: Success after gcc: 5 commits discards 09ba784db3 292: onsuccess: #2541: 1: Success after binutils: 13 commits discards 48c8cf03d9 291: onsuccess: #2539: 1: Success after binutils/gcc/glibc/g [...] discards de0077b1f0 290: onsuccess: #2538: 1: Success after binutils/gcc/glibc/g [...] discards 0ed4ce9bd2 289: onsuccess: #2537: 1: Success after binutils/gcc/linux/g [...] discards d669ae3fe5 288: onsuccess: #2536: 1: Success after binutils/gcc/linux/g [...] discards 5cfe35c38c 287: onsuccess: #2535: 1: Success after binutils/gcc/gdb: 15 [...] discards cd59f432a4 286: onsuccess: #2534: 1: Success after binutils/gcc/gdb: 4 commits discards c8415a5d8b 285: onsuccess: #2533: 1: Success after gcc/linux: 13 commits discards 68e9a27b32 284: onsuccess: #2532: 1: Success after binutils/gdb: 10 commits discards 8284d5ff22 283: onsuccess: #2531: 1: Success after binutils/gdb: 16 commits discards 32efe5f66b 282: onsuccess: #2530: 1: Success after binutils/gcc/gdb: 3 commits discards e3bbe72c5b 281: onsuccess: #2529: 1: Success after binutils/gcc/linux/g [...] discards 035fd31150 280: onsuccess: #2528: 1: Success after binutils/gcc/gdb: 7 commits discards 3e0458b799 279: onsuccess: #2527: 1: Success after basepoints/gcc-13-49 [...] discards d3a4ea9814 278: onsuccess: #2526: 1: Success after binutils/gcc/linux/g [...] discards 8fdf2a6229 277: onsuccess: #2525: 1: Success after gcc/linux: 60 commits discards 8e3798162d 276: onsuccess: #2524: 1: Success after binutils/gdb: 2 commits discards 03b0907687 275: onsuccess: #2523: 1: Success after basepoints/gcc-13-49 [...] discards fade5b650f 274: onsuccess: #2522: 1: Success after binutils/gcc/gdb: 8 commits discards 5fb94dcf57 273: onsuccess: #2521: 1: Success after gcc: 2 commits discards 9aa1db66a6 272: onsuccess: #2520: 1: Success after basepoints/gcc-13-49 [...] discards f0e9f52587 271: onsuccess: #2519: 1: Success after binutils/gcc/gdb: 23 [...] discards 556e190717 270: onsuccess: #2518: 1: Success after binutils/gcc/gdb: 19 [...] discards 119e9d69e1 269: onsuccess: #2517: 1: Success after binutils/gcc/gdb: 3 commits discards 0392451f59 268: onsuccess: #2516: 1: Success after binutils/gcc/gdb: 3 commits discards e028661863 267: onsuccess: #2515: 1: Success after binutils/gdb: 4 commits discards da910096d4 266: onsuccess: #2514: 1: Success after binutils/gcc/linux/g [...] discards fbfc5363d0 265: onsuccess: #2513: 1: Success after binutils/gdb: 4 commits discards a7c9afaebe 264: onsuccess: #2512: 1: Success after binutils/gcc/gdb: 21 [...] discards d1d08b110c 263: onsuccess: #2511: 1: Success after binutils/gdb: 16 commits discards 6d507ae23a 262: onsuccess: #2510: 1: Success after binutils/gcc/gdb: 10 [...] discards 4de55374a1 261: onsuccess: #2509: 1: Success after binutils/gcc/gdb: 3 commits new 4bbd8737ed 261: onsuccess: #2509: 1: Success after binutils/gcc/gdb: 3 commits new e2373e7ff2 262: onsuccess: #2510: 1: Success after binutils/gcc/gdb: 10 [...] new 8b2bb73183 263: onsuccess: #2511: 1: Success after binutils/gdb: 16 commits new 1013d6636d 264: onsuccess: #2512: 1: Success after binutils/gcc/gdb: 21 [...] new 3c54bdbd28 265: onsuccess: #2513: 1: Success after binutils/gdb: 4 commits new 24ae570b0b 266: onsuccess: #2514: 1: Success after binutils/gcc/linux/g [...] new 15ed3034c3 267: onsuccess: #2515: 1: Success after binutils/gdb: 4 commits new 4b34231fb4 268: onsuccess: #2516: 1: Success after binutils/gcc/gdb: 3 commits new 9bfee03ddc 269: onsuccess: #2517: 1: Success after binutils/gcc/gdb: 3 commits new 1613402a72 270: onsuccess: #2518: 1: Success after binutils/gcc/gdb: 19 [...] new d3d391c042 271: onsuccess: #2519: 1: Success after binutils/gcc/gdb: 23 [...] new 4cb74f7813 272: onsuccess: #2520: 1: Success after basepoints/gcc-13-49 [...] new 1061560c5a 273: onsuccess: #2521: 1: Success after gcc: 2 commits new 2b534f7b2c 274: onsuccess: #2522: 1: Success after binutils/gcc/gdb: 8 commits new 1a33864775 275: onsuccess: #2523: 1: Success after basepoints/gcc-13-49 [...] new 7d4fe615b6 276: onsuccess: #2524: 1: Success after binutils/gdb: 2 commits new f9932181f2 277: onsuccess: #2525: 1: Success after gcc/linux: 60 commits new c4b5216d19 278: onsuccess: #2526: 1: Success after binutils/gcc/linux/g [...] new d7101daf3d 279: onsuccess: #2527: 1: Success after basepoints/gcc-13-49 [...] new c7dad99cf1 280: onsuccess: #2528: 1: Success after binutils/gcc/gdb: 7 commits new 4cf8f7faca 281: onsuccess: #2529: 1: Success after binutils/gcc/linux/g [...] new 78b1453683 282: onsuccess: #2530: 1: Success after binutils/gcc/gdb: 3 commits new 1efa0f74e1 283: onsuccess: #2531: 1: Success after binutils/gdb: 16 commits new dee16addd6 284: onsuccess: #2532: 1: Success after binutils/gdb: 10 commits new b98136a0c5 285: onsuccess: #2533: 1: Success after gcc/linux: 13 commits new ac2fc52990 286: onsuccess: #2534: 1: Success after binutils/gcc/gdb: 4 commits new 649885d07a 287: onsuccess: #2535: 1: Success after binutils/gcc/gdb: 15 [...] new ef9e53d0c8 288: onsuccess: #2536: 1: Success after binutils/gcc/linux/g [...] new 83be1e8160 289: onsuccess: #2537: 1: Success after binutils/gcc/linux/g [...] new 961cd10529 290: onsuccess: #2538: 1: Success after binutils/gcc/glibc/g [...] new 5442e7cb44 291: onsuccess: #2539: 1: Success after binutils/gcc/glibc/g [...] new f1b8bbcd94 292: onsuccess: #2541: 1: Success after binutils: 13 commits new 1c5cbd3ad0 293: onsuccess: #2542: 1: Success after gcc: 5 commits new 38c85a879b 294: onsuccess: #2544: 1: Success after glibc-2.36.9000-416- [...] new 9dca4c9210 295: onsuccess: #2545: 1: Success after linux: 10 commits new ff97c96e90 296: onsuccess: #2546: 1: Success after binutils/gcc/gdb: 79 [...] new 5aa99f64b3 297: onsuccess: #2547: 1: Success after binutils/gcc/glibc/g [...] new 4ee9d2cce1 298: onsuccess: #2548: 1: Success after binutils/gdb: 6 commits new 7131c037d9 299: onsuccess: #2549: 1: Success after binutils/gcc/gdb/qem [...] new 0645f54bcb 300: onsuccess: #2550: 1: Success after binutils/gcc/linux/g [...] new b1246fe3a1 301: onsuccess: #2551: 1: Success after binutils/gcc/linux/g [...] new f934b63687 302: onsuccess: #2552: 1: Success after binutils/gcc/gdb: 8 commits new a7e1b2c250 303: onsuccess: #2553: 1: Success after binutils/gcc/gdb/qem [...] new f86cfffd37 304: onsuccess: #2554: 1: Success after binutils/gcc/linux/g [...] new af707abb9f 305: onsuccess: #2555: 1: Success after binutils/gcc/gdb: 3 commits new 8c829b000d 306: onsuccess: #2556: 1: Success after binutils/gcc/gdb: 5 commits new df2c019c55 307: onsuccess: #2557: 1: Success after binutils/gcc/gdb/qem [...] new 4e02dacd31 308: onsuccess: #2558: 1: Success after binutils/gcc/linux/g [...] new 8e946bb334 309: onsuccess: #2559: 1: Success after binutils/gcc/linux/g [...] new 3cf51c4439 310: onsuccess: #2560: 1: Success after v7.2.0-493-g052e6534 [...] new ca3306a43b 311: onsuccess: #2561: 1: Success after binutils/gcc/linux/g [...] new ad21c29d08 312: onsuccess: #2562: 1: Success after binutils/gdb: 2 commits new f0b08df90d 313: onsuccess: #2563: 1: Success after linux/qemu: 44 commits new 53cadf092a 314: onsuccess: #2564: 1: Success after binutils/gcc/gdb: 5 commits new 6e8c804457 315: onsuccess: #2565: 1: Success after binutils/gcc/gdb/qem [...] new 51d03d5ead 316: onsuccess: #2566: 1: Success after binutils/gcc/gdb/qem [...] new 9363d68c81 317: onsuccess: #2567: 1: Success after binutils/gcc/linux/g [...] new 7687bc569a 318: onsuccess: #2568: 1: Success after binutils/gdb: 142 commits new 68d9d835a4 319: onsuccess: #2569: 1: Success after binutils/gcc/linux/g [...] new bbf1b13c7f 320: onsuccess: #2570: 1: Success after binutils/gcc/linux/g [...] new 3c8cc41bc4 321: onsuccess: #2571: 1: Success after binutils/gcc/gdb: 19 [...] new 627430534a 322: onsuccess: #2572: 1: Success after binutils/gcc/gdb: 6 commits new a7dc6577f4 323: onsuccess: #2573: 1: Success after binutils/gcc/gdb: 18 [...] new 04b2d5da76 324: onsuccess: #2574: 1: Success after binutils/gcc/glibc/g [...] new 809df0c5f7 325: onsuccess: #2575: 1: Success after binutils/gcc/linux/g [...] new b5eb653398 326: onsuccess: #2576: 1: Success after binutils/gdb: 6 commits new 969feafeb1 327: onsuccess: #2577: 1: Success after binutils/gcc/linux/g [...] new 1b1a45bcb6 328: onsuccess: #2578: 1: Success after binutils/gcc/glibc/g [...] new 51d9dc7168 329: onsuccess: #2579: 1: Success after binutils/gcc/linux/g [...] new a3ab261af8 330: onsuccess: #2580: 1: Success after basepoints/gcc-13-51 [...] new ab0604caec 331: onsuccess: #2581: 1: Success after binutils/gcc/linux/g [...] new b48ccc5880 332: onsuccess: #2582: 1: Success after binutils/gcc/linux/g [...] new 342c32aff9 333: onsuccess: #2583: 1: Success after binutils/gcc/linux/g [...] new 3a04b227a6 334: onsuccess: #2584: 1: Success after gcc/linux: 15 commits new 87ba5016ba 335: onsuccess: #2585: 1: Success after binutils/gcc/linux/g [...] new 961fafd4cf 336: onsuccess: #2586: 1: Success after binutils/gcc/gdb: 22 [...] new eb23db6a6d 337: onsuccess: #2587: 1: Success after binutils/gdb: 4 commits new a404eac385 338: onsuccess: #2588: 1: Success after binutils/gcc/linux/g [...] new 45b0907198 339: onsuccess: #2589: 1: Success after binutils/gcc/glibc/g [...] new 10bace5932 340: onsuccess: #2590: 1: Success after binutils/gcc/gdb/qem [...] new f7465a4abb 341: onsuccess: #2591: 1: Success after binutils/gcc/linux/g [...] new fc16299986 342: onsuccess: #2592: 1: Success after binutils/gcc/linux/g [...] new 487dc580f5 343: onsuccess: #2593: 1: Success after binutils/gcc/glibc/g [...] new 2f0e5792fa 344: onsuccess: #2594: 1: Success after binutils/gcc/linux/g [...] new 1aa1e8b768 345: onsuccess: #2595: 1: Success after binutils/gcc/linux/g [...] new ddf1283a7a 346: onsuccess: #2596: 1: Success after binutils/gcc/linux/g [...] new 95df05f01c 347: onsuccess: #2597: 1: Success after binutils/gcc/linux/g [...] new 14ea407a47 348: onsuccess: #2598: 1: Success after binutils/gcc/linux/g [...] new 5ec20c747c 349: onsuccess: #2599: 1: Success after binutils/gcc/linux/g [...] new 1face48555 350: onsuccess: #2600: 1: Success after binutils/gcc/linux/g [...] new 421d04f2e0 351: onsuccess: #2601: 1: Success after binutils/gcc/gdb: 17 [...] new 36ff6210e6 352: onsuccess: #2602: 1: Success after binutils/gcc/linux/g [...] new 9f0d01a048 353: onsuccess: #2603: 1: Success after binutils/gcc/linux/g [...] new 953a8752e6 354: onsuccess: #2604: 1: Success after binutils/gcc/glibc/g [...] new f5af229e47 355: onsuccess: #2605: 1: Success after binutils/gcc/linux/g [...] new 3b23f9970e 356: onsuccess: #2606: 1: Success after binutils/gcc/linux/g [...] new 74565d2159 357: onsuccess: #2607: 1: Success after binutils/gcc/linux/g [...] new 7f6e122b59 358: onsuccess: #2608: 1: Success after binutils/gcc/glibc/g [...] new 17e76218f7 359: onsuccess: #2609: 1: Success after binutils/gcc/linux/g [...] new 8542fbc50d 360: onsuccess: #2610: 1: Success after binutils/gcc/gdb/qem [...] new 8e07f5ebf2 361: onsuccess: #2611: 1: Success after binutils/gcc/linux/g [...] new d8c84dc13a 362: onsuccess: #2612: 1: Success after binutils/gcc/gdb: 3 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 (2cee3e4e42) \ 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 -> 1772 bytes 02-prepare_abe/console.log.xz | Bin 2764 -> 2756 bytes 03-build_abe-binutils/console.log.xz | Bin 31536 -> 31032 bytes 04-build_abe-stage1/console.log.xz | Bin 73232 -> 73028 bytes 06-build_abe-linux/console.log.xz | Bin 8868 -> 8864 bytes 07-build_abe-glibc/console.log.xz | Bin 244596 -> 244692 bytes 08-build_abe-stage2/console.log.xz | Bin 204800 -> 204076 bytes 09-build_abe-gdb/console.log.xz | Bin 38928 -> 38464 bytes 10-build_abe-qemu/console.log.xz | Bin 32320 -> 31960 bytes 11-build_abe-dejagnu/console.log.xz | Bin 3912 -> 3884 bytes 12-build_abe-check_gcc/console.log.xz | Bin 3024 -> 2656 bytes 13-check_regression/console.log.xz | Bin 7988 -> 5784 bytes 13-check_regression/fails.sum | 8 +- 13-check_regression/mail-body.txt | 30 +- 13-check_regression/results.compare | 13 +- 13-check_regression/results.compare2 | 101 +- 13-check_regression/results.regressions | 13 +- 14-update_baseline/console.log | 66 +- dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- git/gdb_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 32 +- mail/mail-subject.txt | 2 +- manifest.sh | 34 +- results | 13 +- sumfiles/g++.log.xz | Bin 3383556 -> 3399592 bytes sumfiles/g++.sum | 38 +- sumfiles/gcc.log.xz | Bin 3022068 -> 3023404 bytes sumfiles/gcc.sum | 4536 +++++++++++++++---------------- sumfiles/gfortran.log.xz | Bin 1037960 -> 1040948 bytes sumfiles/gfortran.sum | 58 +- sumfiles/libatomic.log.xz | Bin 2292 -> 2288 bytes sumfiles/libatomic.sum | 2 +- sumfiles/libgomp.log.xz | Bin 215176 -> 215216 bytes sumfiles/libgomp.sum | 2 +- sumfiles/libitm.log.xz | Bin 2656 -> 2652 bytes sumfiles/libitm.sum | 2 +- sumfiles/libstdc++.log.xz | Bin 434856 -> 438148 bytes sumfiles/libstdc++.sum | 69 +- 41 files changed, 2484 insertions(+), 2545 deletions(-)