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 6db522c1d2 365: onsuccess: #2615: 1: Success after binutils/gcc/linux/g [...] discards 79cd224b78 364: onsuccess: #2614: 1: Success after binutils/gcc/linux/g [...] discards 6f70ee0c05 363: onsuccess: #2613: 1: Success after binutils/gcc/gdb/qem [...] discards a196938909 362: onsuccess: #2612: 1: Success after binutils/gcc/gdb: 3 commits discards e9f1568ce7 361: onsuccess: #2611: 1: Success after binutils/gcc/linux/g [...] discards f3f9e31f97 360: onsuccess: #2610: 1: Success after binutils/gcc/gdb/qem [...] discards 069526e6c8 359: onsuccess: #2609: 1: Success after binutils/gcc/linux/g [...] discards e5d675fc3d 358: onsuccess: #2608: 1: Success after binutils/gcc/glibc/g [...] discards 03fafade4f 357: onsuccess: #2607: 1: Success after binutils/gcc/linux/g [...] discards 1a166e8301 356: onsuccess: #2606: 1: Success after binutils/gcc/linux/g [...] discards 3240f38539 355: onsuccess: #2605: 1: Success after binutils/gcc/linux/g [...] discards f4dba3cff2 354: onsuccess: #2604: 1: Success after binutils/gcc/glibc/g [...] discards 4ca428a046 353: onsuccess: #2603: 1: Success after binutils/gcc/linux/g [...] discards f6609634b2 352: onsuccess: #2602: 1: Success after binutils/gcc/linux/g [...] discards b889a1f122 351: onsuccess: #2601: 1: Success after binutils/gcc/gdb: 17 [...] discards 2eaca38290 350: onsuccess: #2600: 1: Success after binutils/gcc/linux/g [...] discards bf2b2a6c9c 349: onsuccess: #2599: 1: Success after binutils/gcc/linux/g [...] discards 35d7362e10 348: onsuccess: #2598: 1: Success after binutils/gcc/linux/g [...] discards eb59917b64 347: onsuccess: #2597: 1: Success after binutils/gcc/linux/g [...] discards a870db33dc 346: onsuccess: #2596: 1: Success after binutils/gcc/linux/g [...] discards 0e223e9f60 345: onsuccess: #2595: 1: Success after binutils/gcc/linux/g [...] discards e1cdb20fb8 344: onsuccess: #2594: 1: Success after binutils/gcc/linux/g [...] discards 8dad320f7a 343: onsuccess: #2593: 1: Success after binutils/gcc/glibc/g [...] discards d307b6b66b 342: onsuccess: #2592: 1: Success after binutils/gcc/linux/g [...] discards 437fa50337 341: onsuccess: #2591: 1: Success after binutils/gcc/linux/g [...] discards c905e3fc5d 340: onsuccess: #2590: 1: Success after binutils/gcc/gdb/qem [...] discards 234d41011e 339: onsuccess: #2589: 1: Success after binutils/gcc/glibc/g [...] discards 37d9285bb4 338: onsuccess: #2588: 1: Success after binutils/gcc/linux/g [...] discards 6524307c46 337: onsuccess: #2587: 1: Success after binutils/gdb: 4 commits discards 5cc0bd821c 336: onsuccess: #2586: 1: Success after binutils/gcc/gdb: 22 [...] discards c86a63cd7d 335: onsuccess: #2585: 1: Success after binutils/gcc/linux/g [...] discards 93c1220327 334: onsuccess: #2584: 1: Success after gcc/linux: 15 commits discards 899851ef1b 333: onsuccess: #2583: 1: Success after binutils/gcc/linux/g [...] discards 9c8acec18d 332: onsuccess: #2582: 1: Success after binutils/gcc/linux/g [...] discards aed6094193 331: onsuccess: #2581: 1: Success after binutils/gcc/linux/g [...] discards eaa5d9340c 330: onsuccess: #2580: 1: Success after basepoints/gcc-13-51 [...] discards 83f7c64589 329: onsuccess: #2579: 1: Success after binutils/gcc/linux/g [...] discards 9e52550086 328: onsuccess: #2578: 1: Success after binutils/gcc/glibc/g [...] discards ed7434107b 327: onsuccess: #2577: 1: Success after binutils/gcc/linux/g [...] discards 6b09475939 326: onsuccess: #2576: 1: Success after binutils/gdb: 6 commits discards 3ca1cecbb4 325: onsuccess: #2575: 1: Success after binutils/gcc/linux/g [...] discards 11bccd5693 324: onsuccess: #2574: 1: Success after binutils/gcc/glibc/g [...] discards 51d9315890 323: onsuccess: #2573: 1: Success after binutils/gcc/gdb: 18 [...] discards 7305354236 322: onsuccess: #2572: 1: Success after binutils/gcc/gdb: 6 commits discards 96001e1c1f 321: onsuccess: #2571: 1: Success after binutils/gcc/gdb: 19 [...] discards b6445fbc43 320: onsuccess: #2570: 1: Success after binutils/gcc/linux/g [...] discards e8a89c8cc3 319: onsuccess: #2569: 1: Success after binutils/gcc/linux/g [...] discards f1033ef8c5 318: onsuccess: #2568: 1: Success after binutils/gdb: 142 commits discards 8be9034b7d 317: onsuccess: #2567: 1: Success after binutils/gcc/linux/g [...] discards 9657199ca5 316: onsuccess: #2566: 1: Success after binutils/gcc/gdb/qem [...] discards 139e243008 315: onsuccess: #2565: 1: Success after binutils/gcc/gdb/qem [...] discards 2916a8c433 314: onsuccess: #2564: 1: Success after binutils/gcc/gdb: 5 commits discards ea76c56652 313: onsuccess: #2563: 1: Success after linux/qemu: 44 commits discards d1de1c8065 312: onsuccess: #2562: 1: Success after binutils/gdb: 2 commits discards f0ef16c4ed 311: onsuccess: #2561: 1: Success after binutils/gcc/linux/g [...] discards e621cdeb23 310: onsuccess: #2560: 1: Success after v7.2.0-493-g052e6534 [...] discards 77efd1605d 309: onsuccess: #2559: 1: Success after binutils/gcc/linux/g [...] discards 8beec4834e 308: onsuccess: #2558: 1: Success after binutils/gcc/linux/g [...] discards 1989c4d06d 307: onsuccess: #2557: 1: Success after binutils/gcc/gdb/qem [...] discards 59a374d9da 306: onsuccess: #2556: 1: Success after binutils/gcc/gdb: 5 commits discards 85d7ed48e9 305: onsuccess: #2555: 1: Success after binutils/gcc/gdb: 3 commits discards 1192b07fbc 304: onsuccess: #2554: 1: Success after binutils/gcc/linux/g [...] discards f7dbf65319 303: onsuccess: #2553: 1: Success after binutils/gcc/gdb/qem [...] discards b5d2933da1 302: onsuccess: #2552: 1: Success after binutils/gcc/gdb: 8 commits discards 16286a9e1e 301: onsuccess: #2551: 1: Success after binutils/gcc/linux/g [...] discards 4e8f7a82d4 300: onsuccess: #2550: 1: Success after binutils/gcc/linux/g [...] discards d4a0ca909d 299: onsuccess: #2549: 1: Success after binutils/gcc/gdb/qem [...] discards 8b64db2c41 298: onsuccess: #2548: 1: Success after binutils/gdb: 6 commits discards 59d6ba6e86 297: onsuccess: #2547: 1: Success after binutils/gcc/glibc/g [...] discards aa49bd3eff 296: onsuccess: #2546: 1: Success after binutils/gcc/gdb: 79 [...] discards b78d9bde39 295: onsuccess: #2545: 1: Success after linux: 10 commits discards 0dd378f9b3 294: onsuccess: #2544: 1: Success after glibc-2.36.9000-416- [...] discards b0c2a6faee 293: onsuccess: #2542: 1: Success after gcc: 5 commits discards 4d2b9aa320 292: onsuccess: #2541: 1: Success after binutils: 13 commits discards 1ae0e32ad5 291: onsuccess: #2539: 1: Success after binutils/gcc/glibc/g [...] discards 531526482b 290: onsuccess: #2538: 1: Success after binutils/gcc/glibc/g [...] discards 3f419ea292 289: onsuccess: #2537: 1: Success after binutils/gcc/linux/g [...] discards 433e8488ab 288: onsuccess: #2536: 1: Success after binutils/gcc/linux/g [...] discards d6fd8eb05c 287: onsuccess: #2535: 1: Success after binutils/gcc/gdb: 15 [...] discards d05738e670 286: onsuccess: #2534: 1: Success after binutils/gcc/gdb: 4 commits discards 9bd58f619a 285: onsuccess: #2533: 1: Success after gcc/linux: 13 commits discards b2e4ae7109 284: onsuccess: #2532: 1: Success after binutils/gdb: 10 commits discards e7c5abea3e 283: onsuccess: #2531: 1: Success after binutils/gdb: 16 commits discards 3cd7ce5e0b 282: onsuccess: #2530: 1: Success after binutils/gcc/gdb: 3 commits discards 4b7c426c5c 281: onsuccess: #2529: 1: Success after binutils/gcc/linux/g [...] discards edb5e65e64 280: onsuccess: #2528: 1: Success after binutils/gcc/gdb: 7 commits discards f294af7fef 279: onsuccess: #2527: 1: Success after basepoints/gcc-13-49 [...] discards 75585f2584 278: onsuccess: #2526: 1: Success after binutils/gcc/linux/g [...] discards dc464b2968 277: onsuccess: #2525: 1: Success after gcc/linux: 60 commits discards 9755a19317 276: onsuccess: #2524: 1: Success after binutils/gdb: 2 commits discards 693ae2686b 275: onsuccess: #2523: 1: Success after basepoints/gcc-13-49 [...] discards 37c67865f0 274: onsuccess: #2522: 1: Success after binutils/gcc/gdb: 8 commits discards 70954e7180 273: onsuccess: #2521: 1: Success after gcc: 2 commits discards f2ae19421f 272: onsuccess: #2520: 1: Success after basepoints/gcc-13-49 [...] discards 8c5a0d895f 271: onsuccess: #2519: 1: Success after binutils/gcc/gdb: 23 [...] discards 88393f1e92 270: onsuccess: #2518: 1: Success after binutils/gcc/gdb: 19 [...] discards 3552ac1c1e 269: onsuccess: #2517: 1: Success after binutils/gcc/gdb: 3 commits discards cf6b8d51e2 268: onsuccess: #2516: 1: Success after binutils/gcc/gdb: 3 commits discards dfc9621a36 267: onsuccess: #2515: 1: Success after binutils/gdb: 4 commits discards 3f608e3ed2 266: onsuccess: #2514: 1: Success after binutils/gcc/linux/g [...] discards 5347492fb4 265: onsuccess: #2513: 1: Success after binutils/gdb: 4 commits new 13a99ff4e6 265: onsuccess: #2513: 1: Success after binutils/gdb: 4 commits new 31c02982d3 266: onsuccess: #2514: 1: Success after binutils/gcc/linux/g [...] new caeb9d7bb3 267: onsuccess: #2515: 1: Success after binutils/gdb: 4 commits new 620c385c36 268: onsuccess: #2516: 1: Success after binutils/gcc/gdb: 3 commits new 980f46516f 269: onsuccess: #2517: 1: Success after binutils/gcc/gdb: 3 commits new 0f20965d56 270: onsuccess: #2518: 1: Success after binutils/gcc/gdb: 19 [...] new cbc1282bb1 271: onsuccess: #2519: 1: Success after binutils/gcc/gdb: 23 [...] new ebfa6ee9a0 272: onsuccess: #2520: 1: Success after basepoints/gcc-13-49 [...] new f9e3d24cf4 273: onsuccess: #2521: 1: Success after gcc: 2 commits new d535607de3 274: onsuccess: #2522: 1: Success after binutils/gcc/gdb: 8 commits new 9693c0bb0f 275: onsuccess: #2523: 1: Success after basepoints/gcc-13-49 [...] new 088629361f 276: onsuccess: #2524: 1: Success after binutils/gdb: 2 commits new d5496b9c53 277: onsuccess: #2525: 1: Success after gcc/linux: 60 commits new a52f502b67 278: onsuccess: #2526: 1: Success after binutils/gcc/linux/g [...] new d72e3d184a 279: onsuccess: #2527: 1: Success after basepoints/gcc-13-49 [...] new 73f83b6a06 280: onsuccess: #2528: 1: Success after binutils/gcc/gdb: 7 commits new b86d339739 281: onsuccess: #2529: 1: Success after binutils/gcc/linux/g [...] new 91b9b503a0 282: onsuccess: #2530: 1: Success after binutils/gcc/gdb: 3 commits new 7bce49929f 283: onsuccess: #2531: 1: Success after binutils/gdb: 16 commits new 47faf6fbc6 284: onsuccess: #2532: 1: Success after binutils/gdb: 10 commits new 37b5d8543c 285: onsuccess: #2533: 1: Success after gcc/linux: 13 commits new 328690c814 286: onsuccess: #2534: 1: Success after binutils/gcc/gdb: 4 commits new c7b7480b43 287: onsuccess: #2535: 1: Success after binutils/gcc/gdb: 15 [...] new 967b2dd7e4 288: onsuccess: #2536: 1: Success after binutils/gcc/linux/g [...] new 82efaf916b 289: onsuccess: #2537: 1: Success after binutils/gcc/linux/g [...] new 79a314a901 290: onsuccess: #2538: 1: Success after binutils/gcc/glibc/g [...] new b414cbfe0b 291: onsuccess: #2539: 1: Success after binutils/gcc/glibc/g [...] new 19e92ff14f 292: onsuccess: #2541: 1: Success after binutils: 13 commits new 7564e1ac7d 293: onsuccess: #2542: 1: Success after gcc: 5 commits new 7dffc805c1 294: onsuccess: #2544: 1: Success after glibc-2.36.9000-416- [...] new e17d12ade6 295: onsuccess: #2545: 1: Success after linux: 10 commits new a1b898f1b1 296: onsuccess: #2546: 1: Success after binutils/gcc/gdb: 79 [...] new 602cc294fc 297: onsuccess: #2547: 1: Success after binutils/gcc/glibc/g [...] new aa158d2f78 298: onsuccess: #2548: 1: Success after binutils/gdb: 6 commits new 83b38ffdd3 299: onsuccess: #2549: 1: Success after binutils/gcc/gdb/qem [...] new 6d9daf7f1a 300: onsuccess: #2550: 1: Success after binutils/gcc/linux/g [...] new 7e616a4f9d 301: onsuccess: #2551: 1: Success after binutils/gcc/linux/g [...] new c94ca044ff 302: onsuccess: #2552: 1: Success after binutils/gcc/gdb: 8 commits new 61159ea233 303: onsuccess: #2553: 1: Success after binutils/gcc/gdb/qem [...] new 2c6ae251b5 304: onsuccess: #2554: 1: Success after binutils/gcc/linux/g [...] new 103dcd0bfd 305: onsuccess: #2555: 1: Success after binutils/gcc/gdb: 3 commits new f87af8513c 306: onsuccess: #2556: 1: Success after binutils/gcc/gdb: 5 commits new f7525a2b68 307: onsuccess: #2557: 1: Success after binutils/gcc/gdb/qem [...] new a38c64c99c 308: onsuccess: #2558: 1: Success after binutils/gcc/linux/g [...] new 2a70a18ac3 309: onsuccess: #2559: 1: Success after binutils/gcc/linux/g [...] new 65aa7dcee2 310: onsuccess: #2560: 1: Success after v7.2.0-493-g052e6534 [...] new ec22f44d52 311: onsuccess: #2561: 1: Success after binutils/gcc/linux/g [...] new bc4be1c426 312: onsuccess: #2562: 1: Success after binutils/gdb: 2 commits new cecd43f41e 313: onsuccess: #2563: 1: Success after linux/qemu: 44 commits new 4e0cace94d 314: onsuccess: #2564: 1: Success after binutils/gcc/gdb: 5 commits new fe62c244f3 315: onsuccess: #2565: 1: Success after binutils/gcc/gdb/qem [...] new 657e2bfeea 316: onsuccess: #2566: 1: Success after binutils/gcc/gdb/qem [...] new 12c629aa54 317: onsuccess: #2567: 1: Success after binutils/gcc/linux/g [...] new d43fd28383 318: onsuccess: #2568: 1: Success after binutils/gdb: 142 commits new a66a9c29a7 319: onsuccess: #2569: 1: Success after binutils/gcc/linux/g [...] new 7cea8ba0c0 320: onsuccess: #2570: 1: Success after binutils/gcc/linux/g [...] new 6a790cb4aa 321: onsuccess: #2571: 1: Success after binutils/gcc/gdb: 19 [...] new 4d9082c622 322: onsuccess: #2572: 1: Success after binutils/gcc/gdb: 6 commits new 2d3f89760f 323: onsuccess: #2573: 1: Success after binutils/gcc/gdb: 18 [...] new 0789719136 324: onsuccess: #2574: 1: Success after binutils/gcc/glibc/g [...] new e9c4dc68ac 325: onsuccess: #2575: 1: Success after binutils/gcc/linux/g [...] new b62210e9ef 326: onsuccess: #2576: 1: Success after binutils/gdb: 6 commits new e1d8c38b08 327: onsuccess: #2577: 1: Success after binutils/gcc/linux/g [...] new 7c902410d8 328: onsuccess: #2578: 1: Success after binutils/gcc/glibc/g [...] new 6aa80e3fca 329: onsuccess: #2579: 1: Success after binutils/gcc/linux/g [...] new 58c74bb442 330: onsuccess: #2580: 1: Success after basepoints/gcc-13-51 [...] new ac4ade9dde 331: onsuccess: #2581: 1: Success after binutils/gcc/linux/g [...] new a9b1b2e839 332: onsuccess: #2582: 1: Success after binutils/gcc/linux/g [...] new aab6a6165d 333: onsuccess: #2583: 1: Success after binutils/gcc/linux/g [...] new 3f4a85844b 334: onsuccess: #2584: 1: Success after gcc/linux: 15 commits new 151f129827 335: onsuccess: #2585: 1: Success after binutils/gcc/linux/g [...] new 251307ffb7 336: onsuccess: #2586: 1: Success after binutils/gcc/gdb: 22 [...] new a55a051fb0 337: onsuccess: #2587: 1: Success after binutils/gdb: 4 commits new b93b13b708 338: onsuccess: #2588: 1: Success after binutils/gcc/linux/g [...] new 83ebdf2487 339: onsuccess: #2589: 1: Success after binutils/gcc/glibc/g [...] new d786ba5f0c 340: onsuccess: #2590: 1: Success after binutils/gcc/gdb/qem [...] new 8b1d22ea6f 341: onsuccess: #2591: 1: Success after binutils/gcc/linux/g [...] new cec7dc749c 342: onsuccess: #2592: 1: Success after binutils/gcc/linux/g [...] new d593d594ff 343: onsuccess: #2593: 1: Success after binutils/gcc/glibc/g [...] new f778c1ebe9 344: onsuccess: #2594: 1: Success after binutils/gcc/linux/g [...] new fc97bdddda 345: onsuccess: #2595: 1: Success after binutils/gcc/linux/g [...] new a42e763cd1 346: onsuccess: #2596: 1: Success after binutils/gcc/linux/g [...] new 2cc990d9d7 347: onsuccess: #2597: 1: Success after binutils/gcc/linux/g [...] new 25d404ff44 348: onsuccess: #2598: 1: Success after binutils/gcc/linux/g [...] new 6a7207caaf 349: onsuccess: #2599: 1: Success after binutils/gcc/linux/g [...] new 9cf6c6e6b6 350: onsuccess: #2600: 1: Success after binutils/gcc/linux/g [...] new a504d83d50 351: onsuccess: #2601: 1: Success after binutils/gcc/gdb: 17 [...] new e6f969f474 352: onsuccess: #2602: 1: Success after binutils/gcc/linux/g [...] new 8ecba244f4 353: onsuccess: #2603: 1: Success after binutils/gcc/linux/g [...] new 924e9245e3 354: onsuccess: #2604: 1: Success after binutils/gcc/glibc/g [...] new 83220d5c93 355: onsuccess: #2605: 1: Success after binutils/gcc/linux/g [...] new a15c8bf243 356: onsuccess: #2606: 1: Success after binutils/gcc/linux/g [...] new 72fd7880b1 357: onsuccess: #2607: 1: Success after binutils/gcc/linux/g [...] new 59dd5e9643 358: onsuccess: #2608: 1: Success after binutils/gcc/glibc/g [...] new 806f1a588a 359: onsuccess: #2609: 1: Success after binutils/gcc/linux/g [...] new 4c6973a4b3 360: onsuccess: #2610: 1: Success after binutils/gcc/gdb/qem [...] new b9803a1a52 361: onsuccess: #2611: 1: Success after binutils/gcc/linux/g [...] new 0637aa9ed2 362: onsuccess: #2612: 1: Success after binutils/gcc/gdb: 3 commits new 4b1f423990 363: onsuccess: #2613: 1: Success after binutils/gcc/gdb/qem [...] new 1d787dde82 364: onsuccess: #2614: 1: Success after binutils/gcc/linux/g [...] new 73b6220748 365: onsuccess: #2615: 1: Success after binutils/gcc/linux/g [...] new 63b4dffbe2 366: onsuccess: #2616: 1: Success after glibc-2.37.9000-17-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 (6db522c1d2) \ 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 1808 -> 1808 bytes 02-prepare_abe/console.log.xz | Bin 2796 -> 2772 bytes 03-build_abe-binutils/console.log.xz | Bin 31400 -> 31112 bytes 04-build_abe-stage1/console.log.xz | Bin 73504 -> 72932 bytes 06-build_abe-linux/console.log.xz | Bin 9044 -> 9012 bytes 07-build_abe-glibc/console.log.xz | Bin 246256 -> 244468 bytes 08-build_abe-stage2/console.log.xz | Bin 205868 -> 203912 bytes 09-build_abe-gdb/console.log.xz | Bin 38816 -> 38244 bytes 10-build_abe-qemu/console.log.xz | Bin 32524 -> 32104 bytes 11-build_abe-dejagnu/console.log.xz | Bin 3900 -> 3896 bytes 12-build_abe-check_gcc/console.log.xz | Bin 2696 -> 2676 bytes 13-check_regression/console.log.xz | Bin 6944 -> 6128 bytes 13-check_regression/extra-bisect-params | 2 +- 13-check_regression/fails.sum | 19 +- 13-check_regression/mail-body.txt | 98 +- 13-check_regression/results.compare | 59 +- 13-check_regression/results.compare2 | 109 +- 13-check_regression/results.regressions | 59 +- 14-update_baseline/console.log | 66 +- dashboard/dashboard-generate.sh | 2 +- git/glibc_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 100 +- mail/mail-subject.txt | 2 +- manifest.sh | 24 +- results | 59 +- sumfiles/g++.log.xz | Bin 3397092 -> 3387504 bytes sumfiles/g++.sum | 2 +- sumfiles/gcc.log.xz | Bin 3037168 -> 2996084 bytes sumfiles/gcc.sum | 4120 +++++++++++++++---------------- sumfiles/gfortran.log.xz | Bin 1049168 -> 1039500 bytes sumfiles/gfortran.sum | 2 +- sumfiles/libatomic.log.xz | Bin 2288 -> 2300 bytes sumfiles/libatomic.sum | 2 +- sumfiles/libgomp.log.xz | Bin 215140 -> 214992 bytes sumfiles/libgomp.sum | 7 +- sumfiles/libitm.log.xz | Bin 2660 -> 2660 bytes sumfiles/libitm.sum | 2 +- sumfiles/libstdc++.log.xz | Bin 439796 -> 431024 bytes sumfiles/libstdc++.sum | 219 +- 40 files changed, 2414 insertions(+), 2543 deletions(-)