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 edaaf326a2 367: onsuccess: #2617: 1: Success after gcc/linux/qemu: 107 commits discards 44d0ee8a4b 366: onsuccess: #2616: 1: Success after glibc-2.37.9000-17-g [...] discards 894f66ccea 365: onsuccess: #2615: 1: Success after binutils/gcc/linux/g [...] discards b5fabd00a3 364: onsuccess: #2614: 1: Success after binutils/gcc/linux/g [...] discards 955551e177 363: onsuccess: #2613: 1: Success after binutils/gcc/gdb/qem [...] discards 0b41297312 362: onsuccess: #2612: 1: Success after binutils/gcc/gdb: 3 commits discards f86257b9bd 361: onsuccess: #2611: 1: Success after binutils/gcc/linux/g [...] discards 959e79d8b0 360: onsuccess: #2610: 1: Success after binutils/gcc/gdb/qem [...] discards 1b1239f83b 359: onsuccess: #2609: 1: Success after binutils/gcc/linux/g [...] discards a37000439c 358: onsuccess: #2608: 1: Success after binutils/gcc/glibc/g [...] discards c0840f6abc 357: onsuccess: #2607: 1: Success after binutils/gcc/linux/g [...] discards cf2bd45468 356: onsuccess: #2606: 1: Success after binutils/gcc/linux/g [...] discards 541d7103a2 355: onsuccess: #2605: 1: Success after binutils/gcc/linux/g [...] discards 148aabfcd8 354: onsuccess: #2604: 1: Success after binutils/gcc/glibc/g [...] discards 4b317613f2 353: onsuccess: #2603: 1: Success after binutils/gcc/linux/g [...] discards 3089d64b83 352: onsuccess: #2602: 1: Success after binutils/gcc/linux/g [...] discards 517f0b0bfb 351: onsuccess: #2601: 1: Success after binutils/gcc/gdb: 17 [...] discards 50ac4f1f51 350: onsuccess: #2600: 1: Success after binutils/gcc/linux/g [...] discards 965d67dd56 349: onsuccess: #2599: 1: Success after binutils/gcc/linux/g [...] discards 1414072b47 348: onsuccess: #2598: 1: Success after binutils/gcc/linux/g [...] discards 7091609600 347: onsuccess: #2597: 1: Success after binutils/gcc/linux/g [...] discards 1c33fe8285 346: onsuccess: #2596: 1: Success after binutils/gcc/linux/g [...] discards 77c56de7a2 345: onsuccess: #2595: 1: Success after binutils/gcc/linux/g [...] discards 490b8df7cb 344: onsuccess: #2594: 1: Success after binutils/gcc/linux/g [...] discards 811e8fd3c7 343: onsuccess: #2593: 1: Success after binutils/gcc/glibc/g [...] discards 39628bc63d 342: onsuccess: #2592: 1: Success after binutils/gcc/linux/g [...] discards 486c40dfb4 341: onsuccess: #2591: 1: Success after binutils/gcc/linux/g [...] discards d6e8be334a 340: onsuccess: #2590: 1: Success after binutils/gcc/gdb/qem [...] discards ae616a234f 339: onsuccess: #2589: 1: Success after binutils/gcc/glibc/g [...] discards dba8a2b78e 338: onsuccess: #2588: 1: Success after binutils/gcc/linux/g [...] discards aa75f70b83 337: onsuccess: #2587: 1: Success after binutils/gdb: 4 commits discards 58f441bf00 336: onsuccess: #2586: 1: Success after binutils/gcc/gdb: 22 [...] discards 55374fc788 335: onsuccess: #2585: 1: Success after binutils/gcc/linux/g [...] discards d52935a390 334: onsuccess: #2584: 1: Success after gcc/linux: 15 commits discards e8032627fd 333: onsuccess: #2583: 1: Success after binutils/gcc/linux/g [...] discards edb6041721 332: onsuccess: #2582: 1: Success after binutils/gcc/linux/g [...] discards e0929e62de 331: onsuccess: #2581: 1: Success after binutils/gcc/linux/g [...] discards 4423746035 330: onsuccess: #2580: 1: Success after basepoints/gcc-13-51 [...] discards 055e77c547 329: onsuccess: #2579: 1: Success after binutils/gcc/linux/g [...] discards f374c77bc0 328: onsuccess: #2578: 1: Success after binutils/gcc/glibc/g [...] discards 02b5f9d8f6 327: onsuccess: #2577: 1: Success after binutils/gcc/linux/g [...] discards 15f72c2c46 326: onsuccess: #2576: 1: Success after binutils/gdb: 6 commits discards c8c64a380c 325: onsuccess: #2575: 1: Success after binutils/gcc/linux/g [...] discards 53786bad30 324: onsuccess: #2574: 1: Success after binutils/gcc/glibc/g [...] discards 2e89d5dcbe 323: onsuccess: #2573: 1: Success after binutils/gcc/gdb: 18 [...] discards 2f51c82ce7 322: onsuccess: #2572: 1: Success after binutils/gcc/gdb: 6 commits discards 6eaccd4f63 321: onsuccess: #2571: 1: Success after binutils/gcc/gdb: 19 [...] discards 08f9e66515 320: onsuccess: #2570: 1: Success after binutils/gcc/linux/g [...] discards a57dcb236b 319: onsuccess: #2569: 1: Success after binutils/gcc/linux/g [...] discards e8b8ba723e 318: onsuccess: #2568: 1: Success after binutils/gdb: 142 commits discards 53fe9841fa 317: onsuccess: #2567: 1: Success after binutils/gcc/linux/g [...] discards 910b69a593 316: onsuccess: #2566: 1: Success after binutils/gcc/gdb/qem [...] discards 13711f7794 315: onsuccess: #2565: 1: Success after binutils/gcc/gdb/qem [...] discards edb4cbab05 314: onsuccess: #2564: 1: Success after binutils/gcc/gdb: 5 commits discards a89c6afe92 313: onsuccess: #2563: 1: Success after linux/qemu: 44 commits discards 026e72700f 312: onsuccess: #2562: 1: Success after binutils/gdb: 2 commits discards e59df08f90 311: onsuccess: #2561: 1: Success after binutils/gcc/linux/g [...] discards f3bd6cc825 310: onsuccess: #2560: 1: Success after v7.2.0-493-g052e6534 [...] discards e66d0dbb98 309: onsuccess: #2559: 1: Success after binutils/gcc/linux/g [...] discards 632a73230e 308: onsuccess: #2558: 1: Success after binutils/gcc/linux/g [...] discards 0acc3efeb1 307: onsuccess: #2557: 1: Success after binutils/gcc/gdb/qem [...] discards 18e047d16f 306: onsuccess: #2556: 1: Success after binutils/gcc/gdb: 5 commits discards ace93e0495 305: onsuccess: #2555: 1: Success after binutils/gcc/gdb: 3 commits discards 1c85069cb4 304: onsuccess: #2554: 1: Success after binutils/gcc/linux/g [...] discards bd064c5767 303: onsuccess: #2553: 1: Success after binutils/gcc/gdb/qem [...] discards 0d7b11d6ea 302: onsuccess: #2552: 1: Success after binutils/gcc/gdb: 8 commits discards ea26126ba8 301: onsuccess: #2551: 1: Success after binutils/gcc/linux/g [...] discards 2b75fea674 300: onsuccess: #2550: 1: Success after binutils/gcc/linux/g [...] discards 2a516479b2 299: onsuccess: #2549: 1: Success after binutils/gcc/gdb/qem [...] discards 7c9f6707b9 298: onsuccess: #2548: 1: Success after binutils/gdb: 6 commits discards edc8248c5d 297: onsuccess: #2547: 1: Success after binutils/gcc/glibc/g [...] discards 1bef30a2bf 296: onsuccess: #2546: 1: Success after binutils/gcc/gdb: 79 [...] discards ec4970c2e1 295: onsuccess: #2545: 1: Success after linux: 10 commits discards dd84a08a53 294: onsuccess: #2544: 1: Success after glibc-2.36.9000-416- [...] discards 08f5763c72 293: onsuccess: #2542: 1: Success after gcc: 5 commits discards 536af120a5 292: onsuccess: #2541: 1: Success after binutils: 13 commits discards afa344a2bd 291: onsuccess: #2539: 1: Success after binutils/gcc/glibc/g [...] discards c3e12d231b 290: onsuccess: #2538: 1: Success after binutils/gcc/glibc/g [...] discards 5c9feda291 289: onsuccess: #2537: 1: Success after binutils/gcc/linux/g [...] discards a087d44965 288: onsuccess: #2536: 1: Success after binutils/gcc/linux/g [...] discards ac5ab539dc 287: onsuccess: #2535: 1: Success after binutils/gcc/gdb: 15 [...] discards f8503eaab9 286: onsuccess: #2534: 1: Success after binutils/gcc/gdb: 4 commits discards 812d408c8d 285: onsuccess: #2533: 1: Success after gcc/linux: 13 commits discards 682d8c07f9 284: onsuccess: #2532: 1: Success after binutils/gdb: 10 commits discards 7790f17b10 283: onsuccess: #2531: 1: Success after binutils/gdb: 16 commits discards b208ca0071 282: onsuccess: #2530: 1: Success after binutils/gcc/gdb: 3 commits discards 9d335e6ce2 281: onsuccess: #2529: 1: Success after binutils/gcc/linux/g [...] discards 77836fcec7 280: onsuccess: #2528: 1: Success after binutils/gcc/gdb: 7 commits discards 42a2493397 279: onsuccess: #2527: 1: Success after basepoints/gcc-13-49 [...] discards 9a534f18ef 278: onsuccess: #2526: 1: Success after binutils/gcc/linux/g [...] discards faf4bfd930 277: onsuccess: #2525: 1: Success after gcc/linux: 60 commits discards 38b60f2420 276: onsuccess: #2524: 1: Success after binutils/gdb: 2 commits discards 384cc6b71b 275: onsuccess: #2523: 1: Success after basepoints/gcc-13-49 [...] discards 8a40ab6cc0 274: onsuccess: #2522: 1: Success after binutils/gcc/gdb: 8 commits discards 98eae9c21d 273: onsuccess: #2521: 1: Success after gcc: 2 commits discards 0207af601a 272: onsuccess: #2520: 1: Success after basepoints/gcc-13-49 [...] discards 7abc0e5ad7 271: onsuccess: #2519: 1: Success after binutils/gcc/gdb: 23 [...] discards 01c44959a9 270: onsuccess: #2518: 1: Success after binutils/gcc/gdb: 19 [...] discards a93ede66b8 269: onsuccess: #2517: 1: Success after binutils/gcc/gdb: 3 commits discards 5d9ec1a180 268: onsuccess: #2516: 1: Success after binutils/gcc/gdb: 3 commits discards 9ca2a906d9 267: onsuccess: #2515: 1: Success after binutils/gdb: 4 commits new a16d7ac76d 267: onsuccess: #2515: 1: Success after binutils/gdb: 4 commits new 2b57602293 268: onsuccess: #2516: 1: Success after binutils/gcc/gdb: 3 commits new 4a5757e62c 269: onsuccess: #2517: 1: Success after binutils/gcc/gdb: 3 commits new bfbde87326 270: onsuccess: #2518: 1: Success after binutils/gcc/gdb: 19 [...] new 58c4da79b8 271: onsuccess: #2519: 1: Success after binutils/gcc/gdb: 23 [...] new f028bc5624 272: onsuccess: #2520: 1: Success after basepoints/gcc-13-49 [...] new e978683d27 273: onsuccess: #2521: 1: Success after gcc: 2 commits new ac01d1584f 274: onsuccess: #2522: 1: Success after binutils/gcc/gdb: 8 commits new 4f52e281ac 275: onsuccess: #2523: 1: Success after basepoints/gcc-13-49 [...] new de9dc1e066 276: onsuccess: #2524: 1: Success after binutils/gdb: 2 commits new fc13d16ba0 277: onsuccess: #2525: 1: Success after gcc/linux: 60 commits new 53c802b6b1 278: onsuccess: #2526: 1: Success after binutils/gcc/linux/g [...] new 844de7f97c 279: onsuccess: #2527: 1: Success after basepoints/gcc-13-49 [...] new cb7833200d 280: onsuccess: #2528: 1: Success after binutils/gcc/gdb: 7 commits new cd21c5a54e 281: onsuccess: #2529: 1: Success after binutils/gcc/linux/g [...] new b3cc646dde 282: onsuccess: #2530: 1: Success after binutils/gcc/gdb: 3 commits new d09ea8c13e 283: onsuccess: #2531: 1: Success after binutils/gdb: 16 commits new 9242130a2a 284: onsuccess: #2532: 1: Success after binutils/gdb: 10 commits new fce27e171d 285: onsuccess: #2533: 1: Success after gcc/linux: 13 commits new df167ff6df 286: onsuccess: #2534: 1: Success after binutils/gcc/gdb: 4 commits new 9e1df0d334 287: onsuccess: #2535: 1: Success after binutils/gcc/gdb: 15 [...] new 818c19e133 288: onsuccess: #2536: 1: Success after binutils/gcc/linux/g [...] new bdaa384fcb 289: onsuccess: #2537: 1: Success after binutils/gcc/linux/g [...] new 92c0ae3834 290: onsuccess: #2538: 1: Success after binutils/gcc/glibc/g [...] new d7c113b087 291: onsuccess: #2539: 1: Success after binutils/gcc/glibc/g [...] new 6d6421a2ec 292: onsuccess: #2541: 1: Success after binutils: 13 commits new 85a3b2ea8e 293: onsuccess: #2542: 1: Success after gcc: 5 commits new ac90e6614e 294: onsuccess: #2544: 1: Success after glibc-2.36.9000-416- [...] new d16b1026c3 295: onsuccess: #2545: 1: Success after linux: 10 commits new 63127a6d5e 296: onsuccess: #2546: 1: Success after binutils/gcc/gdb: 79 [...] new 4392d893e0 297: onsuccess: #2547: 1: Success after binutils/gcc/glibc/g [...] new 7fdf4c0f11 298: onsuccess: #2548: 1: Success after binutils/gdb: 6 commits new b1a6c9916e 299: onsuccess: #2549: 1: Success after binutils/gcc/gdb/qem [...] new 186d1ae708 300: onsuccess: #2550: 1: Success after binutils/gcc/linux/g [...] new e91a1481be 301: onsuccess: #2551: 1: Success after binutils/gcc/linux/g [...] new d09d6c3880 302: onsuccess: #2552: 1: Success after binutils/gcc/gdb: 8 commits new 737f785987 303: onsuccess: #2553: 1: Success after binutils/gcc/gdb/qem [...] new cf8860fb25 304: onsuccess: #2554: 1: Success after binutils/gcc/linux/g [...] new 431d095df0 305: onsuccess: #2555: 1: Success after binutils/gcc/gdb: 3 commits new 0d9f321dbe 306: onsuccess: #2556: 1: Success after binutils/gcc/gdb: 5 commits new 2309caac43 307: onsuccess: #2557: 1: Success after binutils/gcc/gdb/qem [...] new 7fe7a731d5 308: onsuccess: #2558: 1: Success after binutils/gcc/linux/g [...] new 24ecdc78b7 309: onsuccess: #2559: 1: Success after binutils/gcc/linux/g [...] new 338957461e 310: onsuccess: #2560: 1: Success after v7.2.0-493-g052e6534 [...] new c3842a8a61 311: onsuccess: #2561: 1: Success after binutils/gcc/linux/g [...] new c69ba3e65c 312: onsuccess: #2562: 1: Success after binutils/gdb: 2 commits new 0f0a0aadbe 313: onsuccess: #2563: 1: Success after linux/qemu: 44 commits new 710ca800df 314: onsuccess: #2564: 1: Success after binutils/gcc/gdb: 5 commits new 2021795ba1 315: onsuccess: #2565: 1: Success after binutils/gcc/gdb/qem [...] new 955cbb6c60 316: onsuccess: #2566: 1: Success after binutils/gcc/gdb/qem [...] new c6b5af2aed 317: onsuccess: #2567: 1: Success after binutils/gcc/linux/g [...] new 60168f6f7b 318: onsuccess: #2568: 1: Success after binutils/gdb: 142 commits new 85a9906965 319: onsuccess: #2569: 1: Success after binutils/gcc/linux/g [...] new de13d8374e 320: onsuccess: #2570: 1: Success after binutils/gcc/linux/g [...] new 6244234a02 321: onsuccess: #2571: 1: Success after binutils/gcc/gdb: 19 [...] new 99b671002a 322: onsuccess: #2572: 1: Success after binutils/gcc/gdb: 6 commits new 90fe0e9a60 323: onsuccess: #2573: 1: Success after binutils/gcc/gdb: 18 [...] new f844ee9e4c 324: onsuccess: #2574: 1: Success after binutils/gcc/glibc/g [...] new 5b23cc49af 325: onsuccess: #2575: 1: Success after binutils/gcc/linux/g [...] new 009716124a 326: onsuccess: #2576: 1: Success after binutils/gdb: 6 commits new 699dd419a9 327: onsuccess: #2577: 1: Success after binutils/gcc/linux/g [...] new 27babdf080 328: onsuccess: #2578: 1: Success after binutils/gcc/glibc/g [...] new 273be05a50 329: onsuccess: #2579: 1: Success after binutils/gcc/linux/g [...] new 333bcebe7b 330: onsuccess: #2580: 1: Success after basepoints/gcc-13-51 [...] new 0e0e3aa507 331: onsuccess: #2581: 1: Success after binutils/gcc/linux/g [...] new 717ab629ac 332: onsuccess: #2582: 1: Success after binutils/gcc/linux/g [...] new 9ab341c9a6 333: onsuccess: #2583: 1: Success after binutils/gcc/linux/g [...] new db2aa9d298 334: onsuccess: #2584: 1: Success after gcc/linux: 15 commits new 2c1c1ea389 335: onsuccess: #2585: 1: Success after binutils/gcc/linux/g [...] new 6c6f4e7398 336: onsuccess: #2586: 1: Success after binutils/gcc/gdb: 22 [...] new baa769ea1f 337: onsuccess: #2587: 1: Success after binutils/gdb: 4 commits new e40fed89e1 338: onsuccess: #2588: 1: Success after binutils/gcc/linux/g [...] new cc0edd5484 339: onsuccess: #2589: 1: Success after binutils/gcc/glibc/g [...] new a50e2b36c4 340: onsuccess: #2590: 1: Success after binutils/gcc/gdb/qem [...] new 63380fa55f 341: onsuccess: #2591: 1: Success after binutils/gcc/linux/g [...] new b29de23bed 342: onsuccess: #2592: 1: Success after binutils/gcc/linux/g [...] new 4b62b63188 343: onsuccess: #2593: 1: Success after binutils/gcc/glibc/g [...] new 9550713da4 344: onsuccess: #2594: 1: Success after binutils/gcc/linux/g [...] new c71e93c1e5 345: onsuccess: #2595: 1: Success after binutils/gcc/linux/g [...] new 64ae96ce91 346: onsuccess: #2596: 1: Success after binutils/gcc/linux/g [...] new 607c04e9a3 347: onsuccess: #2597: 1: Success after binutils/gcc/linux/g [...] new 980b7c2b99 348: onsuccess: #2598: 1: Success after binutils/gcc/linux/g [...] new 547dd6323c 349: onsuccess: #2599: 1: Success after binutils/gcc/linux/g [...] new 3f764e2a41 350: onsuccess: #2600: 1: Success after binutils/gcc/linux/g [...] new 8e8febf81f 351: onsuccess: #2601: 1: Success after binutils/gcc/gdb: 17 [...] new 6b233fb265 352: onsuccess: #2602: 1: Success after binutils/gcc/linux/g [...] new 0d82c53eaa 353: onsuccess: #2603: 1: Success after binutils/gcc/linux/g [...] new 65690d9c48 354: onsuccess: #2604: 1: Success after binutils/gcc/glibc/g [...] new c3e379898a 355: onsuccess: #2605: 1: Success after binutils/gcc/linux/g [...] new 8594c7f266 356: onsuccess: #2606: 1: Success after binutils/gcc/linux/g [...] new b16d9afded 357: onsuccess: #2607: 1: Success after binutils/gcc/linux/g [...] new cfc9cd0a03 358: onsuccess: #2608: 1: Success after binutils/gcc/glibc/g [...] new 8907d71ce1 359: onsuccess: #2609: 1: Success after binutils/gcc/linux/g [...] new 3ddd60fb5f 360: onsuccess: #2610: 1: Success after binutils/gcc/gdb/qem [...] new 46db13624b 361: onsuccess: #2611: 1: Success after binutils/gcc/linux/g [...] new 71dc9e2471 362: onsuccess: #2612: 1: Success after binutils/gcc/gdb: 3 commits new 2d9547134b 363: onsuccess: #2613: 1: Success after binutils/gcc/gdb/qem [...] new 471877307c 364: onsuccess: #2614: 1: Success after binutils/gcc/linux/g [...] new 9a3437c20c 365: onsuccess: #2615: 1: Success after binutils/gcc/linux/g [...] new 8ca65b601b 366: onsuccess: #2616: 1: Success after glibc-2.37.9000-17-g [...] new e2f3454492 367: onsuccess: #2617: 1: Success after gcc/linux/qemu: 107 commits new 6f629834fe 368: onsuccess: #2618: 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 (edaaf326a2) \ 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 -> 1820 bytes 02-prepare_abe/console.log.xz | Bin 2780 -> 2792 bytes 03-build_abe-binutils/console.log.xz | Bin 31612 -> 31404 bytes 04-build_abe-stage1/console.log.xz | Bin 73744 -> 74484 bytes 06-build_abe-linux/console.log.xz | Bin 8360 -> 8740 bytes 07-build_abe-glibc/console.log.xz | Bin 245628 -> 247580 bytes 08-build_abe-stage2/console.log.xz | Bin 205368 -> 206940 bytes 09-build_abe-gdb/console.log.xz | Bin 38568 -> 39272 bytes 10-build_abe-qemu/console.log.xz | Bin 32524 -> 31260 bytes 11-build_abe-dejagnu/console.log.xz | Bin 3912 -> 3952 bytes 12-build_abe-check_gcc/console.log.xz | Bin 2728 -> 3460 bytes 13-check_regression/console.log.xz | Bin 7468 -> 7504 bytes 13-check_regression/extra-bisect-params | 2 +- 13-check_regression/fails.sum | 32 +- 13-check_regression/mail-body.txt | 112 +- 13-check_regression/results.compare | 48 +- 13-check_regression/results.compare2 | 162 +- 13-check_regression/results.regressions | 48 +- 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 | 114 +- mail/mail-subject.txt | 2 +- manifest.sh | 38 +- results | 48 +- sumfiles/g++.log.xz | Bin 3401080 -> 3414424 bytes sumfiles/g++.sum | 35 +- sumfiles/gcc.log.xz | Bin 3034708 -> 3018416 bytes sumfiles/gcc.sum | 4246 +++++++++++++++---------------- sumfiles/gfortran.log.xz | Bin 1042600 -> 1037712 bytes sumfiles/gfortran.sum | 13 +- sumfiles/libatomic.log.xz | Bin 2292 -> 2292 bytes sumfiles/libatomic.sum | 2 +- sumfiles/libgomp.log.xz | Bin 215088 -> 215000 bytes sumfiles/libgomp.sum | 2 +- sumfiles/libitm.log.xz | Bin 2656 -> 2652 bytes sumfiles/libitm.sum | 2 +- sumfiles/libstdc++.log.xz | Bin 436292 -> 435884 bytes sumfiles/libstdc++.sum | 619 +---- 43 files changed, 2605 insertions(+), 2998 deletions(-)