Tcwg-commits February 2023

tcwg-commits@lists.linaro.org

5 participants
3393 discussions

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_gnu_cross_check_gcc/master-aarch64 updated (8ada807f87 -> dcba9c120f)

by git＠git.linaro.org

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 8ada807f87 390: onsuccess: #2641: 1: Success after binutils/gcc/gdb: 6 commits discards 799d97e32f 389: onsuccess: #2640: 1: Success after binutils/gcc/linux/g [...] discards d6456dc78d 388: onsuccess: #2639: 1: Success after gcc/glibc: 44 commits discards eac8217f48 387: onsuccess: #2638: 1: Success after binutils/gcc/gdb: 11 [...] discards 826653ccb0 386: onsuccess: #2637: 1: Success after binutils/gcc/linux/g [...] discards 328c9499b9 385: onsuccess: #2636: 1: Success after binutils/gcc/gdb: 10 [...] discards 87e09a134b 384: onsuccess: #2635: 1: Success after binutils/gcc/gdb: 10 [...] discards 06e91e9191 383: onsuccess: #2634: 1: Success after binutils/gcc/linux/g [...] discards 4aa7952666 382: onsuccess: #2633: 1: Success after binutils/gcc/linux/g [...] discards 4fd2ec7c9d 381: onsuccess: #2632: 1: Success after binutils/gcc/gdb/qem [...] discards b83141a39a 380: onsuccess: #2631: 1: Success after binutils/gcc/linux/g [...] discards b43ecc74e0 379: onsuccess: #2630: 1: Success after binutils/gcc/linux/g [...] discards d86580a233 378: onsuccess: #2629: 1: Success after binutils/gcc/glibc/g [...] discards 7ae3487672 377: onsuccess: #2627: 1: Success after basepoints/gcc-13-57 [...] discards b891fe0192 376: onsuccess: #2626: 1: Success after binutils/gcc/glibc/g [...] discards b958ab9074 375: onsuccess: #2625: 1: Success after binutils/gcc/gdb/qem [...] discards 2218cab0f2 374: onsuccess: #2624: 1: Success after binutils/gcc/gdb: 6 commits discards 6b566bea71 373: onsuccess: #2623: 1: Success after binutils/gcc/linux/g [...] discards 39ff382a69 372: onsuccess: #2622: 1: Success after binutils/gcc/glibc/g [...] discards 7341cd9e1f 371: onsuccess: #2621: 1: Success after binutils/gcc/linux/g [...] discards 748e80234a 370: onsuccess: #2620: 1: Success after binutils/gcc/glibc/g [...] discards 9f93a0460a 369: onsuccess: #2619: 1: Success after binutils/gcc/gdb/qem [...] discards d879e4321e 368: onsuccess: #2618: 1: Success after binutils/gcc/linux/g [...] discards 649baf8795 367: onsuccess: #2617: 1: Success after gcc/linux/qemu: 107 commits discards e9a8ff4f33 366: onsuccess: #2616: 1: Success after glibc-2.37.9000-17-g [...] discards a2c9394770 365: onsuccess: #2615: 1: Success after binutils/gcc/linux/g [...] discards d525cc7d41 364: onsuccess: #2614: 1: Success after binutils/gcc/linux/g [...] discards 1be5cd37f7 363: onsuccess: #2613: 1: Success after binutils/gcc/gdb/qem [...] discards ea9f7e7e25 362: onsuccess: #2612: 1: Success after binutils/gcc/gdb: 3 commits discards 00d8b6842d 361: onsuccess: #2611: 1: Success after binutils/gcc/linux/g [...] discards fd470b192f 360: onsuccess: #2610: 1: Success after binutils/gcc/gdb/qem [...] discards 705c5c21fd 359: onsuccess: #2609: 1: Success after binutils/gcc/linux/g [...] discards e1ac0eb9d8 358: onsuccess: #2608: 1: Success after binutils/gcc/glibc/g [...] discards 03a2589a9c 357: onsuccess: #2607: 1: Success after binutils/gcc/linux/g [...] discards a2ea60cf5e 356: onsuccess: #2606: 1: Success after binutils/gcc/linux/g [...] discards 21009cf8b4 355: onsuccess: #2605: 1: Success after binutils/gcc/linux/g [...] discards c77ea37082 354: onsuccess: #2604: 1: Success after binutils/gcc/glibc/g [...] discards 9e2b4656b2 353: onsuccess: #2603: 1: Success after binutils/gcc/linux/g [...] discards a87fe70aba 352: onsuccess: #2602: 1: Success after binutils/gcc/linux/g [...] discards 4de93a6d69 351: onsuccess: #2601: 1: Success after binutils/gcc/gdb: 17 [...] discards dc56f9f29b 350: onsuccess: #2600: 1: Success after binutils/gcc/linux/g [...] discards 79a62997d8 349: onsuccess: #2599: 1: Success after binutils/gcc/linux/g [...] discards 74feec7ba4 348: onsuccess: #2598: 1: Success after binutils/gcc/linux/g [...] discards cb005eb599 347: onsuccess: #2597: 1: Success after binutils/gcc/linux/g [...] discards efc17692ee 346: onsuccess: #2596: 1: Success after binutils/gcc/linux/g [...] discards 057623b500 345: onsuccess: #2595: 1: Success after binutils/gcc/linux/g [...] discards c3c6252ffb 344: onsuccess: #2594: 1: Success after binutils/gcc/linux/g [...] discards 63633cf31e 343: onsuccess: #2593: 1: Success after binutils/gcc/glibc/g [...] discards ee89b87926 342: onsuccess: #2592: 1: Success after binutils/gcc/linux/g [...] discards f999cfbc45 341: onsuccess: #2591: 1: Success after binutils/gcc/linux/g [...] discards 3317c14c2c 340: onsuccess: #2590: 1: Success after binutils/gcc/gdb/qem [...] discards cbee9ef73f 339: onsuccess: #2589: 1: Success after binutils/gcc/glibc/g [...] discards 0df4348ac7 338: onsuccess: #2588: 1: Success after binutils/gcc/linux/g [...] discards 1f905d84b4 337: onsuccess: #2587: 1: Success after binutils/gdb: 4 commits discards a4d0f846ce 336: onsuccess: #2586: 1: Success after binutils/gcc/gdb: 22 [...] discards e3a3751e11 335: onsuccess: #2585: 1: Success after binutils/gcc/linux/g [...] discards c8b8ae8401 334: onsuccess: #2584: 1: Success after gcc/linux: 15 commits discards 03cdd40692 333: onsuccess: #2583: 1: Success after binutils/gcc/linux/g [...] discards c96f993569 332: onsuccess: #2582: 1: Success after binutils/gcc/linux/g [...] discards 348e263362 331: onsuccess: #2581: 1: Success after binutils/gcc/linux/g [...] discards d68f8df3b5 330: onsuccess: #2580: 1: Success after basepoints/gcc-13-51 [...] discards 8abbcadfd3 329: onsuccess: #2579: 1: Success after binutils/gcc/linux/g [...] discards 0ba167704d 328: onsuccess: #2578: 1: Success after binutils/gcc/glibc/g [...] discards 7800ba34fd 327: onsuccess: #2577: 1: Success after binutils/gcc/linux/g [...] discards cec431ec20 326: onsuccess: #2576: 1: Success after binutils/gdb: 6 commits discards 1185ccc3dc 325: onsuccess: #2575: 1: Success after binutils/gcc/linux/g [...] discards 8d258b8ca1 324: onsuccess: #2574: 1: Success after binutils/gcc/glibc/g [...] discards b48b6802a7 323: onsuccess: #2573: 1: Success after binutils/gcc/gdb: 18 [...] discards b8d3b6d159 322: onsuccess: #2572: 1: Success after binutils/gcc/gdb: 6 commits discards 3d0b591266 321: onsuccess: #2571: 1: Success after binutils/gcc/gdb: 19 [...] discards 87fb7a44dc 320: onsuccess: #2570: 1: Success after binutils/gcc/linux/g [...] discards 1717b43363 319: onsuccess: #2569: 1: Success after binutils/gcc/linux/g [...] discards 73883025bf 318: onsuccess: #2568: 1: Success after binutils/gdb: 142 commits discards 2a6fdbba48 317: onsuccess: #2567: 1: Success after binutils/gcc/linux/g [...] discards 25e4a27362 316: onsuccess: #2566: 1: Success after binutils/gcc/gdb/qem [...] discards f2cfd16da0 315: onsuccess: #2565: 1: Success after binutils/gcc/gdb/qem [...] discards 9746ffee18 314: onsuccess: #2564: 1: Success after binutils/gcc/gdb: 5 commits discards fffc229a82 313: onsuccess: #2563: 1: Success after linux/qemu: 44 commits discards 737fdf4b04 312: onsuccess: #2562: 1: Success after binutils/gdb: 2 commits discards def0cfa9ec 311: onsuccess: #2561: 1: Success after binutils/gcc/linux/g [...] discards 19b0547edd 310: onsuccess: #2560: 1: Success after v7.2.0-493-g052e6534 [...] discards 4e18e816fc 309: onsuccess: #2559: 1: Success after binutils/gcc/linux/g [...] discards 9710536338 308: onsuccess: #2558: 1: Success after binutils/gcc/linux/g [...] discards 91b32de386 307: onsuccess: #2557: 1: Success after binutils/gcc/gdb/qem [...] discards 962450a72f 306: onsuccess: #2556: 1: Success after binutils/gcc/gdb: 5 commits discards f2fe4c75de 305: onsuccess: #2555: 1: Success after binutils/gcc/gdb: 3 commits discards cf24cecbf8 304: onsuccess: #2554: 1: Success after binutils/gcc/linux/g [...] discards 4ea69b3b68 303: onsuccess: #2553: 1: Success after binutils/gcc/gdb/qem [...] discards 105fca6fa1 302: onsuccess: #2552: 1: Success after binutils/gcc/gdb: 8 commits discards 057cb57606 301: onsuccess: #2551: 1: Success after binutils/gcc/linux/g [...] discards 17f19e621a 300: onsuccess: #2550: 1: Success after binutils/gcc/linux/g [...] discards 4026ba45fc 299: onsuccess: #2549: 1: Success after binutils/gcc/gdb/qem [...] discards e9693a0193 298: onsuccess: #2548: 1: Success after binutils/gdb: 6 commits discards 85c772a7ba 297: onsuccess: #2547: 1: Success after binutils/gcc/glibc/g [...] discards 2ed618cb48 296: onsuccess: #2546: 1: Success after binutils/gcc/gdb: 79 [...] discards f9371893fc 295: onsuccess: #2545: 1: Success after linux: 10 commits discards f8878659ba 294: onsuccess: #2544: 1: Success after glibc-2.36.9000-416- [...] discards 687ea7e20b 293: onsuccess: #2542: 1: Success after gcc: 5 commits discards 6eb41c4755 292: onsuccess: #2541: 1: Success after binutils: 13 commits discards 6fc1fe9e4c 291: onsuccess: #2539: 1: Success after binutils/gcc/glibc/g [...] discards e4fb9e024a 290: onsuccess: #2538: 1: Success after binutils/gcc/glibc/g [...] new 0bfe010254 290: onsuccess: #2538: 1: Success after binutils/gcc/glibc/g [...] new cacbda0775 291: onsuccess: #2539: 1: Success after binutils/gcc/glibc/g [...] new 533fce475f 292: onsuccess: #2541: 1: Success after binutils: 13 commits new bde0fc0cdf 293: onsuccess: #2542: 1: Success after gcc: 5 commits new fb0ca36284 294: onsuccess: #2544: 1: Success after glibc-2.36.9000-416- [...] new 04674562eb 295: onsuccess: #2545: 1: Success after linux: 10 commits new 4d99fb18b8 296: onsuccess: #2546: 1: Success after binutils/gcc/gdb: 79 [...] new 8a6accfdbb 297: onsuccess: #2547: 1: Success after binutils/gcc/glibc/g [...] new 125d151889 298: onsuccess: #2548: 1: Success after binutils/gdb: 6 commits new facfaf5df8 299: onsuccess: #2549: 1: Success after binutils/gcc/gdb/qem [...] new 3249e156bc 300: onsuccess: #2550: 1: Success after binutils/gcc/linux/g [...] new 4a2ab8ce57 301: onsuccess: #2551: 1: Success after binutils/gcc/linux/g [...] new 15c3fcf8cb 302: onsuccess: #2552: 1: Success after binutils/gcc/gdb: 8 commits new bf0a406735 303: onsuccess: #2553: 1: Success after binutils/gcc/gdb/qem [...] new a497e6eeab 304: onsuccess: #2554: 1: Success after binutils/gcc/linux/g [...] new a429691b7f 305: onsuccess: #2555: 1: Success after binutils/gcc/gdb: 3 commits new fc87e53659 306: onsuccess: #2556: 1: Success after binutils/gcc/gdb: 5 commits new 170f82179d 307: onsuccess: #2557: 1: Success after binutils/gcc/gdb/qem [...] new d0a2c7f706 308: onsuccess: #2558: 1: Success after binutils/gcc/linux/g [...] new 2291fa8554 309: onsuccess: #2559: 1: Success after binutils/gcc/linux/g [...] new 07127089cf 310: onsuccess: #2560: 1: Success after v7.2.0-493-g052e6534 [...] new da71d97122 311: onsuccess: #2561: 1: Success after binutils/gcc/linux/g [...] new 2ff49294cc 312: onsuccess: #2562: 1: Success after binutils/gdb: 2 commits new a750cf51ae 313: onsuccess: #2563: 1: Success after linux/qemu: 44 commits new 9485d97196 314: onsuccess: #2564: 1: Success after binutils/gcc/gdb: 5 commits new 73cd42ea94 315: onsuccess: #2565: 1: Success after binutils/gcc/gdb/qem [...] new 44b143b11a 316: onsuccess: #2566: 1: Success after binutils/gcc/gdb/qem [...] new c980ed00e2 317: onsuccess: #2567: 1: Success after binutils/gcc/linux/g [...] new 4b502722bf 318: onsuccess: #2568: 1: Success after binutils/gdb: 142 commits new 29e30a419d 319: onsuccess: #2569: 1: Success after binutils/gcc/linux/g [...] new b6287e386d 320: onsuccess: #2570: 1: Success after binutils/gcc/linux/g [...] new 2ee8d98633 321: onsuccess: #2571: 1: Success after binutils/gcc/gdb: 19 [...] new bcde344076 322: onsuccess: #2572: 1: Success after binutils/gcc/gdb: 6 commits new 01ffe69fab 323: onsuccess: #2573: 1: Success after binutils/gcc/gdb: 18 [...] new 4920075db7 324: onsuccess: #2574: 1: Success after binutils/gcc/glibc/g [...] new 1112ed54f1 325: onsuccess: #2575: 1: Success after binutils/gcc/linux/g [...] new a33a8e395f 326: onsuccess: #2576: 1: Success after binutils/gdb: 6 commits new ebe78d54c2 327: onsuccess: #2577: 1: Success after binutils/gcc/linux/g [...] new 2e101dad29 328: onsuccess: #2578: 1: Success after binutils/gcc/glibc/g [...] new fbf6c6d249 329: onsuccess: #2579: 1: Success after binutils/gcc/linux/g [...] new f87f971cea 330: onsuccess: #2580: 1: Success after basepoints/gcc-13-51 [...] new 1ff192f746 331: onsuccess: #2581: 1: Success after binutils/gcc/linux/g [...] new aeae356534 332: onsuccess: #2582: 1: Success after binutils/gcc/linux/g [...] new fba47f1cc4 333: onsuccess: #2583: 1: Success after binutils/gcc/linux/g [...] new dd0f1e5399 334: onsuccess: #2584: 1: Success after gcc/linux: 15 commits new 220e195c1a 335: onsuccess: #2585: 1: Success after binutils/gcc/linux/g [...] new db6f8c7df4 336: onsuccess: #2586: 1: Success after binutils/gcc/gdb: 22 [...] new 04a46de034 337: onsuccess: #2587: 1: Success after binutils/gdb: 4 commits new dabdab4d46 338: onsuccess: #2588: 1: Success after binutils/gcc/linux/g [...] new 96d35fd18b 339: onsuccess: #2589: 1: Success after binutils/gcc/glibc/g [...] new c35bf15f7a 340: onsuccess: #2590: 1: Success after binutils/gcc/gdb/qem [...] new e0cc8bff1c 341: onsuccess: #2591: 1: Success after binutils/gcc/linux/g [...] new 6c74d52c55 342: onsuccess: #2592: 1: Success after binutils/gcc/linux/g [...] new bc5cd3755f 343: onsuccess: #2593: 1: Success after binutils/gcc/glibc/g [...] new ee58347199 344: onsuccess: #2594: 1: Success after binutils/gcc/linux/g [...] new 333218f72d 345: onsuccess: #2595: 1: Success after binutils/gcc/linux/g [...] new 51c17f5d8f 346: onsuccess: #2596: 1: Success after binutils/gcc/linux/g [...] new b378eded33 347: onsuccess: #2597: 1: Success after binutils/gcc/linux/g [...] new 1392963447 348: onsuccess: #2598: 1: Success after binutils/gcc/linux/g [...] new bc0244ade8 349: onsuccess: #2599: 1: Success after binutils/gcc/linux/g [...] new c71f75d2f7 350: onsuccess: #2600: 1: Success after binutils/gcc/linux/g [...] new 67f2e4a8d5 351: onsuccess: #2601: 1: Success after binutils/gcc/gdb: 17 [...] new a07395e783 352: onsuccess: #2602: 1: Success after binutils/gcc/linux/g [...] new d0c50ece43 353: onsuccess: #2603: 1: Success after binutils/gcc/linux/g [...] new b67d5908bf 354: onsuccess: #2604: 1: Success after binutils/gcc/glibc/g [...] new b89dd1185a 355: onsuccess: #2605: 1: Success after binutils/gcc/linux/g [...] new 7264bdc037 356: onsuccess: #2606: 1: Success after binutils/gcc/linux/g [...] new a7fef0718e 357: onsuccess: #2607: 1: Success after binutils/gcc/linux/g [...] new bd2ffa68d3 358: onsuccess: #2608: 1: Success after binutils/gcc/glibc/g [...] new 83616bdc34 359: onsuccess: #2609: 1: Success after binutils/gcc/linux/g [...] new 03efe62e92 360: onsuccess: #2610: 1: Success after binutils/gcc/gdb/qem [...] new cd9f7eb5c3 361: onsuccess: #2611: 1: Success after binutils/gcc/linux/g [...] new f2088c18cf 362: onsuccess: #2612: 1: Success after binutils/gcc/gdb: 3 commits new 027fc176ae 363: onsuccess: #2613: 1: Success after binutils/gcc/gdb/qem [...] new 83ccfc56c8 364: onsuccess: #2614: 1: Success after binutils/gcc/linux/g [...] new b26d9af017 365: onsuccess: #2615: 1: Success after binutils/gcc/linux/g [...] new aa470448be 366: onsuccess: #2616: 1: Success after glibc-2.37.9000-17-g [...] new a473bc7cab 367: onsuccess: #2617: 1: Success after gcc/linux/qemu: 107 commits new aeddfb361b 368: onsuccess: #2618: 1: Success after binutils/gcc/linux/g [...] new f04e47921f 369: onsuccess: #2619: 1: Success after binutils/gcc/gdb/qem [...] new d4c03a7e8e 370: onsuccess: #2620: 1: Success after binutils/gcc/glibc/g [...] new ebfd52165c 371: onsuccess: #2621: 1: Success after binutils/gcc/linux/g [...] new ba6b121a84 372: onsuccess: #2622: 1: Success after binutils/gcc/glibc/g [...] new a09654c26f 373: onsuccess: #2623: 1: Success after binutils/gcc/linux/g [...] new cac9396ae7 374: onsuccess: #2624: 1: Success after binutils/gcc/gdb: 6 commits new 08a39584b1 375: onsuccess: #2625: 1: Success after binutils/gcc/gdb/qem [...] new b53cced8d3 376: onsuccess: #2626: 1: Success after binutils/gcc/glibc/g [...] new 96c218b75d 377: onsuccess: #2627: 1: Success after basepoints/gcc-13-57 [...] new e14dfb30c2 378: onsuccess: #2629: 1: Success after binutils/gcc/glibc/g [...] new fc0cc2673a 379: onsuccess: #2630: 1: Success after binutils/gcc/linux/g [...] new 6a9e95a590 380: onsuccess: #2631: 1: Success after binutils/gcc/linux/g [...] new 01c9a33c82 381: onsuccess: #2632: 1: Success after binutils/gcc/gdb/qem [...] new ec4d6d767f 382: onsuccess: #2633: 1: Success after binutils/gcc/linux/g [...] new df091d9fb3 383: onsuccess: #2634: 1: Success after binutils/gcc/linux/g [...] new 728ccf4ab9 384: onsuccess: #2635: 1: Success after binutils/gcc/gdb: 10 [...] new aace75ac77 385: onsuccess: #2636: 1: Success after binutils/gcc/gdb: 10 [...] new f94a1dc72b 386: onsuccess: #2637: 1: Success after binutils/gcc/linux/g [...] new ba0becc269 387: onsuccess: #2638: 1: Success after binutils/gcc/gdb: 11 [...] new 55c08af12f 388: onsuccess: #2639: 1: Success after gcc/glibc: 44 commits new fc0a1e375b 389: onsuccess: #2640: 1: Success after binutils/gcc/linux/g [...] new 4c20bbcc75 390: onsuccess: #2641: 1: Success after binutils/gcc/gdb: 6 commits new dcba9c120f 391: onsuccess: #2642: 1: Success after binutils/gcc/gdb: 28 [...] 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 (8ada807f87) \ 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 1792 -> 1800 bytes 02-prepare_abe/console.log.xz | Bin 2764 -> 2764 bytes 03-build_abe-binutils/console.log.xz | Bin 31208 -> 31184 bytes 04-build_abe-stage1/console.log.xz | Bin 72960 -> 72888 bytes 06-build_abe-linux/console.log.xz | Bin 8360 -> 8356 bytes 07-build_abe-glibc/console.log.xz | Bin 244424 -> 244556 bytes 08-build_abe-stage2/console.log.xz | Bin 204296 -> 204244 bytes 09-build_abe-gdb/console.log.xz | Bin 38712 -> 38460 bytes 10-build_abe-qemu/console.log.xz | Bin 31516 -> 31348 bytes 11-build_abe-dejagnu/console.log.xz | Bin 3932 -> 3884 bytes 12-build_abe-check_gcc/console.log.xz | Bin 2796 -> 2752 bytes 13-check_regression/console.log.xz | Bin 5900 -> 6316 bytes 13-check_regression/extra-bisect-params | 1 - 13-check_regression/fails.sum | 23 - 13-check_regression/mail-body.txt | 42 +- 13-check_regression/results.compare | 29 +- 13-check_regression/results.compare2 | 72 +- 13-check_regression/results.regressions | 43 - 14-update_baseline/console.log | 64 +- 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 | 44 +- mail/mail-subject.txt | 2 +- manifest.sh | 32 +- results | 43 - sumfiles/g++.log.xz | Bin 3394120 -> 3376764 bytes sumfiles/g++.sum | 16 +- sumfiles/gcc.log.xz | Bin 3018372 -> 3022220 bytes sumfiles/gcc.sum | 4484 ++++++++++++++++--------------- sumfiles/gfortran.log.xz | Bin 1035412 -> 1039484 bytes sumfiles/gfortran.sum | 4 +- sumfiles/libatomic.log.xz | Bin 2288 -> 2296 bytes sumfiles/libatomic.sum | 2 +- sumfiles/libgomp.log.xz | Bin 217596 -> 217532 bytes sumfiles/libgomp.sum | 2 +- sumfiles/libitm.log.xz | Bin 2656 -> 2656 bytes sumfiles/libitm.sum | 2 +- sumfiles/libstdc++.log.xz | Bin 436124 -> 434832 bytes sumfiles/libstdc++.sum | 50 +- 42 files changed, 2433 insertions(+), 2532 deletions(-) delete mode 100644 13-check_regression/extra-bisect-params delete mode 100644 13-check_regression/fails.sum delete mode 100644 13-check_regression/results.regressions -- To stop receiving notification emails like this one, please contact the administrator of this repository.

1 year, 9 months

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_gnu_cross_build/master-arm updated (4fdfd2aaf7 -> 5efc66c3d2)

by git＠git.linaro.org

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_build/master-arm in repository toolchain/ci/base-artifacts. discards 4fdfd2aaf7 420: onsuccess: #2156: 7: Success after binutils/gcc/gdb: 27 [...] discards 00d8c89b28 419: onsuccess: #2155: 7: Success after binutils/gcc/gdb: 4 commits discards 0a65d486c6 418: onsuccess: #2154: 7: Success after binutils/gcc/linux/g [...] discards 2a94f7ccca 417: onsuccess: #2153: 7: Success after linux/glibc: 27 commits discards 652431ecd4 416: onsuccess: #2152: 7: Success after gcc: 50 commits discards 4f69a59a12 415: onsuccess: #2151: 7: Success after binutils/gcc/gdb: 93 [...] discards aead7182e3 414: onsuccess: #2150: 7: Success after binutils/gcc/linux/g [...] discards e2559a161b 413: onsuccess: #2149: 7: Success after binutils/gcc/linux/g [...] discards 8ad3534525 412: onsuccess: #2148: 7: Success after binutils/gcc/gdb: 6 commits discards fc9c13da9c 411: onsuccess: #2147: 7: Success after binutils/gcc/gdb: 9 commits discards 51586934f8 410: onsuccess: #2146: 7: Success after binutils/gcc/linux/g [...] discards daed7bcd88 409: onsuccess: #2145: 7: Success after binutils/gcc/linux/g [...] discards 193dc50fdd 408: onsuccess: #2144: 7: Success after binutils/gcc/gdb/qem [...] discards bacaf96fa9 407: onsuccess: #2143: 7: Success after binutils/gcc/linux/g [...] discards 033e5c639e 406: onsuccess: #2142: 7: Success after binutils/gcc/gdb: 14 [...] discards b7577e05ad 405: onsuccess: #2141: 7: Success after binutils/gcc/linux/g [...] discards f74cd3f28c 404: onsuccess: #2139: 7: Success after basepoints/gcc-13-57 [...] discards 5ae19dacf6 403: onsuccess: #2138: 7: Success after binutils/gcc/gdb: 4 commits discards 0b641f7e6f 402: onsuccess: #2137: 7: Success after binutils/gcc/gdb: 22 [...] discards 8025cc6fd4 401: onsuccess: #2136: 7: Success after binutils/gcc/glibc/g [...] discards c928d6f605 400: onsuccess: #2135: 7: Success after binutils/gcc/linux/g [...] discards 1002d4f419 399: onsuccess: #2134: 7: Success after binutils/gcc/linux/g [...] discards 3cfbf191c2 398: onsuccess: #2133: 7: Success after binutils/gcc/glibc/g [...] discards 4188b7d83a 397: onsuccess: #2132: 7: Success after gcc: 2 commits discards 63c28019ac 396: onsuccess: #2131: 7: Success after binutils/gcc/linux/g [...] discards 433b46f812 395: onsuccess: #2130: 7: Success after binutils/gcc/gdb/qem [...] discards 5d27773c9b 394: onsuccess: #2129: 7: Success after binutils/gcc/linux/g [...] discards b23878ed8c 393: onsuccess: #2128: 7: Success after gcc/qemu: 42 commits discards bfa6445de1 392: onsuccess: #2127: 7: Success after glibc-2.37.9000-17-g [...] discards 7c58abea54 391: onsuccess: #2126: 7: Success after binutils/gcc/linux/g [...] discards 70a746d2dd 390: onsuccess: #2125: 7: Success after binutils/gcc/linux/g [...] discards c569b14548 389: onsuccess: #2124: 7: Success after binutils/gcc/gdb: 5 commits discards 2c56964278 388: onsuccess: #2123: 7: Success after binutils/gcc/gdb: 3 commits discards 15656f3c8b 387: onsuccess: #2122: 7: Success after gcc/linux/qemu: 117 commits discards cb1d058aa6 386: onsuccess: #2121: 7: Success after binutils/gcc/glibc/g [...] discards 25fd149e6e 385: onsuccess: #2120: 7: Success after binutils/gcc/gdb/qem [...] discards f9e0e1c874 384: onsuccess: #2119: 7: Success after binutils/gcc/linux/g [...] discards e011bd7cd7 383: onsuccess: #2118: 7: Success after binutils/gcc/glibc/g [...] discards 01ec12571b 382: onsuccess: #2117: 7: Success after binutils/gcc/linux/g [...] discards 08d0b663c4 381: onsuccess: #2116: 7: Success after binutils/gcc/linux/g [...] discards 1d9e33962a 380: onsuccess: #2115: 7: Success after binutils/gcc/linux/g [...] discards 2984041097 379: onsuccess: #2114: 7: Success after binutils/gcc/linux/g [...] discards babdc4b140 378: onsuccess: #2113: 7: Success after binutils/gcc/linux/g [...] discards 563ed097d6 377: onsuccess: #2112: 7: Success after binutils/gcc/gdb: 16 [...] discards 822de416f3 376: onsuccess: #2111: 7: Success after binutils/gcc/linux/g [...] discards 3da061ca38 375: onsuccess: #2110: 7: Success after binutils/gcc/linux/g [...] discards aa3010d1e7 374: onsuccess: #2109: 7: Success after binutils/gcc/linux/g [...] discards c16cf2e5f5 373: onsuccess: #2107: 7: Success after binutils/gcc/linux/g [...] discards 136ff1706e 372: onsuccess: #2106: 7: Success after binutils/gcc/linux/g [...] discards 7bb60e26e4 371: onsuccess: #2105: 7: Success after binutils/gcc/gdb/qem [...] discards fd08d899c3 370: onsuccess: #2104: 7: Success after binutils/gcc/linux/g [...] discards 579e5774bb 369: onsuccess: #2103: 7: Success after binutils/gcc/linux/g [...] discards 69447667a7 368: onsuccess: #2102: 7: Success after binutils/gcc/linux/g [...] discards b9b84e73f2 367: onsuccess: #2101: 7: Success after binutils/gcc/linux/g [...] discards 4f74031edd 366: onsuccess: #2100: 7: Success after binutils/gcc/glibc/g [...] discards f1402d74ed 365: onsuccess: #2099: 7: Success after gcc/linux: 21 commits discards bc2f16053d 364: onsuccess: #2098: 7: Success after binutils/gdb: 4 commits discards 537d7e7f48 363: onsuccess: #2097: 7: Success after binutils/gcc/gdb: 25 [...] discards 6210778705 362: onsuccess: #2096: 7: Success after binutils/gcc/linux/g [...] discards 28271c033a 361: onsuccess: #2095: 7: Success after gcc/linux: 15 commits discards abcfc99329 360: onsuccess: #2094: 7: Success after binutils/gcc/linux/g [...] discards ee7fd7b210 359: onsuccess: #2093: 7: Success after binutils/gcc/linux/g [...] discards 945c444e8f 358: onsuccess: #2092: 7: Success after binutils/gcc/gdb: 10 [...] discards 1edc7d6c59 357: onsuccess: #2091: 7: Success after binutils/gcc/linux/g [...] discards 71ffa9e52b 356: onsuccess: #2090: 7: Success after binutils/gcc/glibc/g [...] discards 08034a1db2 355: onsuccess: #2089: 7: Success after binutils/gcc/linux/g [...] discards 8e65c90c36 354: onsuccess: #2088: 7: Success after binutils/gcc/gdb: 7 commits discards 5c22f53b2f 353: onsuccess: #2087: 7: Success after binutils/gcc/linux/g [...] discards cf6d153491 352: onsuccess: #2086: 7: Success after binutils/gcc/gdb: 9 commits discards 826657a6cc 351: onsuccess: #2085: 7: Success after binutils/gcc/gdb: 19 [...] discards e1ab3dda89 350: onsuccess: #2084: 7: Success after binutils/gcc/gdb: 4 commits discards 95d5379242 349: onsuccess: #2083: 7: Success after binutils/gcc/linux/g [...] discards 7f02ad1829 348: onsuccess: #2082: 7: Success after binutils/gcc/glibc/g [...] discards d7aa33fd03 347: onsuccess: #2081: 7: Success after binutils/gcc/linux/g [...] discards d96d4cf0a8 346: onsuccess: #2080: 7: Success after binutils/gdb: 142 commits discards c76406ccf2 345: onsuccess: #2079: 7: Success after binutils/gcc/linux/g [...] discards 796351f050 344: onsuccess: #2078: 7: Success after binutils/gcc/gdb: 6 commits discards ac07ff490c 343: onsuccess: #2077: 7: Success after binutils/gcc/gdb/qem [...] discards 3a1639e8ad 342: onsuccess: #2076: 7: Success after binutils/gcc/gdb: 5 commits discards f0c4f6dfeb 341: onsuccess: #2075: 7: Success after linux/qemu: 44 commits discards 5c3ac2f441 340: onsuccess: #2074: 7: Success after binutils/gcc/gdb: 5 commits discards 1ac0773066 339: onsuccess: #2073: 7: Success after gcc/linux/qemu: 38 commits discards 4e429061d6 338: onsuccess: #2072: 7: Success after v7.2.0-493-g052e6534 [...] discards 407401fd4e 337: onsuccess: #2071: 7: Success after basepoints/gcc-13-50 [...] discards 6100e459b1 336: onsuccess: #2070: 7: Success after binutils/gcc/linux/g [...] discards a7523d416f 335: onsuccess: #2069: 7: Success after binutils/gcc/linux/g [...] discards 34c04570ab 334: onsuccess: #2068: 7: Success after binutils/gcc/gdb/qem [...] discards 8ec81a029a 333: onsuccess: #2067: 7: Success after basepoints/gcc-13-50 [...] discards 0bb4826eb6 332: onsuccess: #2066: 7: Success after binutils/gcc/linux/g [...] discards 7be0ff2266 331: onsuccess: #2065: 7: Success after binutils/gcc/linux/g [...] discards 852c564633 330: onsuccess: #2064: 7: Success after binutils/gcc/gdb: 8 commits discards fceb4c3127 329: onsuccess: #2063: 7: Success after binutils/gcc/gdb: 11 [...] discards 681bbf9fb9 328: onsuccess: #2062: 7: Success after binutils/gcc/linux/g [...] discards ba72707d1d 327: onsuccess: #2061: 7: Success after binutils/gcc/linux/g [...] discards 4844520954 326: onsuccess: #2060: 7: Success after binutils/gcc/gdb: 28 [...] discards 474007d2fb 325: onsuccess: #2059: 7: Success after binutils/gcc/gdb: 9 commits discards 67ae449f4d 324: onsuccess: #2058: 7: Success after binutils/gcc/linux/g [...] discards e9c6601051 323: onsuccess: #2057: 5: Success after gdb-13-branchpoint-2 [...] discards 4f95493691 322: force: #2056: 5: Failure after gdb-13-branchpoint-245-g [...] discards 1c258d918a 321: force: #2055: 7: Success after gdb: 2 commits discards 5f1f669305 320: onsuccess: #2050: 7: Success after gcc: 4 commits new e43d36712a 320: onsuccess: #2050: 7: Success after gcc: 4 commits new 440312a492 321: force: #2055: 7: Success after gdb: 2 commits new be58de7061 322: force: #2056: 5: Failure after gdb-13-branchpoint-245-g [...] new 17831852c4 323: onsuccess: #2057: 5: Success after gdb-13-branchpoint-2 [...] new c283704929 324: onsuccess: #2058: 7: Success after binutils/gcc/linux/g [...] new 1b00809de0 325: onsuccess: #2059: 7: Success after binutils/gcc/gdb: 9 commits new 755deb837e 326: onsuccess: #2060: 7: Success after binutils/gcc/gdb: 28 [...] new 35a0f0d5c4 327: onsuccess: #2061: 7: Success after binutils/gcc/linux/g [...] new a9766a764a 328: onsuccess: #2062: 7: Success after binutils/gcc/linux/g [...] new a9f9209992 329: onsuccess: #2063: 7: Success after binutils/gcc/gdb: 11 [...] new 29335139d1 330: onsuccess: #2064: 7: Success after binutils/gcc/gdb: 8 commits new b4a09c6986 331: onsuccess: #2065: 7: Success after binutils/gcc/linux/g [...] new 6554c5e0d3 332: onsuccess: #2066: 7: Success after binutils/gcc/linux/g [...] new bd4b6f5eea 333: onsuccess: #2067: 7: Success after basepoints/gcc-13-50 [...] new 71e79802a1 334: onsuccess: #2068: 7: Success after binutils/gcc/gdb/qem [...] new ed97e1ac77 335: onsuccess: #2069: 7: Success after binutils/gcc/linux/g [...] new 4687b3bb29 336: onsuccess: #2070: 7: Success after binutils/gcc/linux/g [...] new 42365d4230 337: onsuccess: #2071: 7: Success after basepoints/gcc-13-50 [...] new bfb1c4b3fb 338: onsuccess: #2072: 7: Success after v7.2.0-493-g052e6534 [...] new a92a883bd3 339: onsuccess: #2073: 7: Success after gcc/linux/qemu: 38 commits new 71998cd746 340: onsuccess: #2074: 7: Success after binutils/gcc/gdb: 5 commits new 3e40762648 341: onsuccess: #2075: 7: Success after linux/qemu: 44 commits new 7d10e999fa 342: onsuccess: #2076: 7: Success after binutils/gcc/gdb: 5 commits new ab96e5f196 343: onsuccess: #2077: 7: Success after binutils/gcc/gdb/qem [...] new 5951ee4b6e 344: onsuccess: #2078: 7: Success after binutils/gcc/gdb: 6 commits new 5d66db5af3 345: onsuccess: #2079: 7: Success after binutils/gcc/linux/g [...] new 1d5d037d4f 346: onsuccess: #2080: 7: Success after binutils/gdb: 142 commits new f2b237c121 347: onsuccess: #2081: 7: Success after binutils/gcc/linux/g [...] new 6470f392dc 348: onsuccess: #2082: 7: Success after binutils/gcc/glibc/g [...] new f122651ac0 349: onsuccess: #2083: 7: Success after binutils/gcc/linux/g [...] new 92209fd76d 350: onsuccess: #2084: 7: Success after binutils/gcc/gdb: 4 commits new b574887905 351: onsuccess: #2085: 7: Success after binutils/gcc/gdb: 19 [...] new 5516ee6017 352: onsuccess: #2086: 7: Success after binutils/gcc/gdb: 9 commits new c88cbb1f0e 353: onsuccess: #2087: 7: Success after binutils/gcc/linux/g [...] new 3f912974dc 354: onsuccess: #2088: 7: Success after binutils/gcc/gdb: 7 commits new d387a552dd 355: onsuccess: #2089: 7: Success after binutils/gcc/linux/g [...] new f907f0a459 356: onsuccess: #2090: 7: Success after binutils/gcc/glibc/g [...] new 7ea8e68c6e 357: onsuccess: #2091: 7: Success after binutils/gcc/linux/g [...] new 75bd2e2a4b 358: onsuccess: #2092: 7: Success after binutils/gcc/gdb: 10 [...] new ad62f965bd 359: onsuccess: #2093: 7: Success after binutils/gcc/linux/g [...] new b95acdf82a 360: onsuccess: #2094: 7: Success after binutils/gcc/linux/g [...] new 8949b3754a 361: onsuccess: #2095: 7: Success after gcc/linux: 15 commits new 5ef8eeb199 362: onsuccess: #2096: 7: Success after binutils/gcc/linux/g [...] new cafaab05e7 363: onsuccess: #2097: 7: Success after binutils/gcc/gdb: 25 [...] new 94933140d3 364: onsuccess: #2098: 7: Success after binutils/gdb: 4 commits new 80a77c6cfa 365: onsuccess: #2099: 7: Success after gcc/linux: 21 commits new 7231729247 366: onsuccess: #2100: 7: Success after binutils/gcc/glibc/g [...] new 76b19fef0a 367: onsuccess: #2101: 7: Success after binutils/gcc/linux/g [...] new 96097e3d8f 368: onsuccess: #2102: 7: Success after binutils/gcc/linux/g [...] new 0382a67ec5 369: onsuccess: #2103: 7: Success after binutils/gcc/linux/g [...] new 7d0a2f8020 370: onsuccess: #2104: 7: Success after binutils/gcc/linux/g [...] new aeb3040144 371: onsuccess: #2105: 7: Success after binutils/gcc/gdb/qem [...] new af07068b12 372: onsuccess: #2106: 7: Success after binutils/gcc/linux/g [...] new c871cb28ee 373: onsuccess: #2107: 7: Success after binutils/gcc/linux/g [...] new 3991727662 374: onsuccess: #2109: 7: Success after binutils/gcc/linux/g [...] new 52e2796c26 375: onsuccess: #2110: 7: Success after binutils/gcc/linux/g [...] new 221d9cb0ab 376: onsuccess: #2111: 7: Success after binutils/gcc/linux/g [...] new 0bdcd319d7 377: onsuccess: #2112: 7: Success after binutils/gcc/gdb: 16 [...] new 0623a70698 378: onsuccess: #2113: 7: Success after binutils/gcc/linux/g [...] new c1c73cccdd 379: onsuccess: #2114: 7: Success after binutils/gcc/linux/g [...] new 9e6785dd72 380: onsuccess: #2115: 7: Success after binutils/gcc/linux/g [...] new b46b340801 381: onsuccess: #2116: 7: Success after binutils/gcc/linux/g [...] new 991fedb09c 382: onsuccess: #2117: 7: Success after binutils/gcc/linux/g [...] new 8398ca9ff6 383: onsuccess: #2118: 7: Success after binutils/gcc/glibc/g [...] new 2efadb6a40 384: onsuccess: #2119: 7: Success after binutils/gcc/linux/g [...] new e3b0dc1cfb 385: onsuccess: #2120: 7: Success after binutils/gcc/gdb/qem [...] new 5348bb6746 386: onsuccess: #2121: 7: Success after binutils/gcc/glibc/g [...] new d6f04081a2 387: onsuccess: #2122: 7: Success after gcc/linux/qemu: 117 commits new 980083fc2c 388: onsuccess: #2123: 7: Success after binutils/gcc/gdb: 3 commits new 0dbb56783f 389: onsuccess: #2124: 7: Success after binutils/gcc/gdb: 5 commits new a7acb21aa6 390: onsuccess: #2125: 7: Success after binutils/gcc/linux/g [...] new 66acfb6329 391: onsuccess: #2126: 7: Success after binutils/gcc/linux/g [...] new 80f460b333 392: onsuccess: #2127: 7: Success after glibc-2.37.9000-17-g [...] new 08d6516ff4 393: onsuccess: #2128: 7: Success after gcc/qemu: 42 commits new f9f96fedf1 394: onsuccess: #2129: 7: Success after binutils/gcc/linux/g [...] new fcbd718dcc 395: onsuccess: #2130: 7: Success after binutils/gcc/gdb/qem [...] new e9a545ff87 396: onsuccess: #2131: 7: Success after binutils/gcc/linux/g [...] new bff42752ac 397: onsuccess: #2132: 7: Success after gcc: 2 commits new 018a05ef04 398: onsuccess: #2133: 7: Success after binutils/gcc/glibc/g [...] new 733ade6fad 399: onsuccess: #2134: 7: Success after binutils/gcc/linux/g [...] new e8de0380a8 400: onsuccess: #2135: 7: Success after binutils/gcc/linux/g [...] new 8cb1644c87 401: onsuccess: #2136: 7: Success after binutils/gcc/glibc/g [...] new 79943121ac 402: onsuccess: #2137: 7: Success after binutils/gcc/gdb: 22 [...] new 48f7f03d60 403: onsuccess: #2138: 7: Success after binutils/gcc/gdb: 4 commits new 49c13c840a 404: onsuccess: #2139: 7: Success after basepoints/gcc-13-57 [...] new 0d9157185a 405: onsuccess: #2141: 7: Success after binutils/gcc/linux/g [...] new b14bdb620f 406: onsuccess: #2142: 7: Success after binutils/gcc/gdb: 14 [...] new f86f36995f 407: onsuccess: #2143: 7: Success after binutils/gcc/linux/g [...] new 4e8e1f5a2c 408: onsuccess: #2144: 7: Success after binutils/gcc/gdb/qem [...] new e5a7b400e1 409: onsuccess: #2145: 7: Success after binutils/gcc/linux/g [...] new 8041d7c9da 410: onsuccess: #2146: 7: Success after binutils/gcc/linux/g [...] new 3e8c96ed90 411: onsuccess: #2147: 7: Success after binutils/gcc/gdb: 9 commits new e3ccba3d69 412: onsuccess: #2148: 7: Success after binutils/gcc/gdb: 6 commits new 7c48562184 413: onsuccess: #2149: 7: Success after binutils/gcc/linux/g [...] new b24e45660c 414: onsuccess: #2150: 7: Success after binutils/gcc/linux/g [...] new 61cf59385d 415: onsuccess: #2151: 7: Success after binutils/gcc/gdb: 93 [...] new 2d150832a9 416: onsuccess: #2152: 7: Success after gcc: 50 commits new 9c19bf27dc 417: onsuccess: #2153: 7: Success after linux/glibc: 27 commits new ad93506f44 418: onsuccess: #2154: 7: Success after binutils/gcc/linux/g [...] new 9ee82a71f8 419: onsuccess: #2155: 7: Success after binutils/gcc/gdb: 4 commits new 297870b38b 420: onsuccess: #2156: 7: Success after binutils/gcc/gdb: 27 [...] new 5efc66c3d2 421: onsuccess: #2157: 7: 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 (4fdfd2aaf7) \ N -- N -- N refs/heads/linaro-local/ci/tcwg_gnu_cross_build/master-a [...] 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 1772 -> 1736 bytes 02-prepare_abe/console.log.xz | Bin 2764 -> 2764 bytes 04-build_abe-binutils/console.log.xz | Bin 31188 -> 30768 bytes 05-build_abe-stage1/console.log.xz | Bin 91888 -> 91496 bytes 07-build_abe-linux/console.log.xz | Bin 8368 -> 8540 bytes 08-build_abe-glibc/console.log.xz | Bin 236324 -> 236920 bytes 09-build_abe-stage2/console.log.xz | Bin 228640 -> 228536 bytes 10-build_abe-gdb/console.log.xz | Bin 38400 -> 38056 bytes 11-build_abe-qemu/console.log.xz | Bin 31900 -> 31956 bytes 12-check_regression/console.log.xz | Bin 3768 -> 4784 bytes 13-update_baseline/console.log | 66 +++++++++++++++++------------------ dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- git/gdb_rev | 2 +- git/glibc_rev | 2 +- git/linux_rev | 2 +- git/qemu_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 2 +- mail/mail-subject.txt | 2 +- manifest.sh | 48 ++++++++++++------------- 22 files changed, 67 insertions(+), 67 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

1 year, 9 months

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_kernel/gnu-master-aarch64-stable-allyesconfig updated (f5e1d58447 -> d0b404b684)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. tcwg-buildslave pushed a change to branch linaro-local/ci/tcwg_kernel/gnu-master-aarch64-stable-allyesconfig in repository toolchain/ci/base-artifacts. from f5e1d58447 46: onsuccess: #518: 33: Success after binutils/gcc/qemu: 32 [...] new d0b404b684 47: onsuccess: #520: 33: Success after binutils/gcc/linux/qe [...] The 1 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 2040 -> 1768 bytes 02-prepare_abe/console.log.xz | Bin 2808 -> 2772 bytes 03-build_abe-binutils/console.log.xz | Bin 31836 -> 31136 bytes 04-build_abe-stage1/console.log.xz | Bin 74144 -> 73516 bytes 05-build_abe-qemu/console.log.xz | Bin 32276 -> 33008 bytes 06-build_linux/console.log.xz | Bin 5052 -> 5028 bytes 08-check_regression/console.log.xz | Bin 3900 -> 4392 bytes dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- git/linux_rev | 2 +- git/qemu_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 2 +- mail/mail-subject.txt | 2 +- manifest.sh | 32 ++++++++++++++++---------------- 16 files changed, 24 insertions(+), 24 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

1 year, 9 months

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_bmk-code_size-spec2k6/llvm-arm-master-Os_LTO updated (e0657e5b6f -> b6466516c3)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. tcwg-buildslave pushed a change to branch linaro-local/ci/tcwg_bmk-code_size-spec2k6/llvm-arm-master-Os_LTO in repository toolchain/ci/base-artifacts. from e0657e5b6f 57: onsuccess: #21: 1: [TCWG CI] No change after binutils/gc [...] new b6466516c3 58: onsuccess: #22: 1: [TCWG CI] No change after binutils/gc [...] The 1 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 1828 -> 1844 bytes 02-prepare_abe/console.log.xz | Bin 2784 -> 2772 bytes 03-build_abe-binutils/console.log.xz | Bin 32340 -> 31632 bytes 04-build_abe-stage1/console.log.xz | Bin 93416 -> 92984 bytes 06-build_abe-linux/console.log.xz | Bin 8688 -> 8696 bytes 07-build_abe-glibc/console.log.xz | Bin 238376 -> 238132 bytes 08-build_abe-stage2/console.log.xz | Bin 218944 -> 218848 bytes 09-build_llvm-true-false-cflags-/console.log.xz | Bin 61528 -> 64036 bytes 10-benchmark/benchmark-build.log | 104 +- 10-benchmark/benchmark.log | 102 +- 10-benchmark/console.log.xz | Bin 3900 -> 3892 bytes 11-check_regression/console.log.xz | Bin 7448 -> 7304 bytes .../csv-results-vs-first-0/results.csv | 393630 ++++++++--------- .../csv-results-vs-first-0/size.csv | 400668 +++++++++--------- 11-check_regression/csv-results-vs-first-0/sve.csv | 22 +- .../csv-results-vs-first-1/perf.csv | 117 +- .../csv-results-vs-first-1/results.csv | 371070 ++++++++-------- .../csv-results-vs-first-1/size.csv | 371144 ++++++++-------- 11-check_regression/csv-results-vs-first-1/sve.csv | 26 +- 11-check_regression/csv-results-vs-prev-0/perf.csv | 111 +- .../csv-results-vs-prev-0/results.csv | 356966 ++++++++-------- 11-check_regression/csv-results-vs-prev-0/size.csv | 357034 ++++++++-------- 11-check_regression/csv-results-vs-prev-0/sve.csv | 24 +- 11-check_regression/csv-results-vs-prev-1/perf.csv | 117 +- .../csv-results-vs-prev-1/results.csv | 371070 ++++++++-------- 11-check_regression/csv-results-vs-prev-1/size.csv | 371144 ++++++++-------- 11-check_regression/csv-results-vs-prev-1/sve.csv | 26 +- 11-check_regression/results-vs-first-brief.csv | 40 +- 11-check_regression/results-vs-first-full.csv | 119 +- 11-check_regression/results-vs-first-internal.csv | 50 +- 11-check_regression/results-vs-first.csv | 50 +- 11-check_regression/results-vs-first.log | 846 +- 11-check_regression/results-vs-prev-brief.csv | 40 +- 11-check_regression/results-vs-prev-full.csv | 125 +- 11-check_regression/results-vs-prev-internal.csv | 50 +- 11-check_regression/results-vs-prev.csv | 50 +- 11-check_regression/results-vs-prev.log | 858 +- dashboard/dashboard-generate.sh | 2 +- .../400.perlbench/results-metadata.json | 16 +- .../squad-vs-first/401.bzip2/results-metadata.json | 16 +- .../squad-vs-first/401.bzip2/results-metrics.json | 2 +- .../squad-vs-first/403.gcc/results-metadata.json | 16 +- .../squad-vs-first/403.gcc/results-metrics.json | 2 +- .../squad-vs-first/429.mcf/results-metadata.json | 16 +- .../squad-vs-first/429.mcf/results-metrics.json | 2 +- .../squad-vs-first/433.milc/results-metadata.json | 16 +- .../squad-vs-first/433.milc/results-metrics.json | 2 +- .../squad-vs-first/444.namd/results-metadata.json | 16 +- .../squad-vs-first/444.namd/results-metrics.json | 2 +- .../squad-vs-first/445.gobmk/results-metadata.json | 16 +- .../squad-vs-first/445.gobmk/results-metrics.json | 2 +- .../447.dealII/results-metadata.json | 16 +- .../squad-vs-first/447.dealII/results-metrics.json | 2 +- .../450.soplex/results-metadata.json | 16 +- .../squad-vs-first/450.soplex/results-metrics.json | 2 +- .../453.povray/results-metadata.json | 16 +- .../squad-vs-first/456.hmmer/results-metadata.json | 16 +- .../squad-vs-first/456.hmmer/results-metrics.json | 2 +- .../squad-vs-first/458.sjeng/results-metadata.json | 16 +- .../squad-vs-first/458.sjeng/results-metrics.json | 2 +- .../462.libquantum/results-metadata.json | 16 +- .../462.libquantum/results-metrics.json | 2 +- .../464.h264ref/results-metadata.json | 16 +- .../464.h264ref/results-metrics.json | 2 +- .../squad-vs-first/470.lbm/results-metadata.json | 16 +- .../squad-vs-first/470.lbm/results-metrics.json | 2 +- .../471.omnetpp/results-metadata.json | 16 +- .../471.omnetpp/results-metrics.json | 2 +- .../squad-vs-first/473.astar/results-metadata.json | 16 +- .../squad-vs-first/473.astar/results-metrics.json | 2 +- .../482.sphinx3/results-metadata.json | 16 +- .../482.sphinx3/results-metrics.json | 2 +- .../483.xalancbmk/results-metadata.json | 16 +- .../483.xalancbmk/results-metrics.json | 2 +- .../squad-vs-first/Mean/results-metadata.json | 16 +- dashboard/squad-vs-first/dashboard-push-squad.sh | 82 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- git/glibc_rev | 2 +- git/llvm_rev | 2 +- mail/jira-body.txt | 56 +- mail/mail-body.txt | 56 +- mail/mail-subject.txt | 2 +- manifest.sh | 38 +- results_id | 2 +- save-temps/400.perlbench.tar.xz | Bin 2549756 -> 1281720 bytes save-temps/401.bzip2.tar.xz | Bin 234492 -> 94476 bytes save-temps/403.gcc.tar.xz | Bin 6843768 -> 3567072 bytes save-temps/410.bwaves.tar.xz | Bin 47844 -> 15100 bytes save-temps/416.gamess.tar.xz | Bin 13817220 -> 4210492 bytes save-temps/429.mcf.tar.xz | Bin 69628 -> 36580 bytes save-temps/433.milc.tar.xz | Bin 333244 -> 167760 bytes save-temps/434.zeusmp.tar.xz | Bin 428176 -> 126512 bytes save-temps/435.gromacs.tar.xz | Bin 2111148 -> 979240 bytes save-temps/436.cactusADM.tar.xz | Bin 1524620 -> 725464 bytes save-temps/437.leslie3d.tar.xz | Bin 151400 -> 46336 bytes save-temps/444.namd.tar.xz | Bin 486200 -> 168352 bytes save-temps/445.gobmk.tar.xz | Bin 2490084 -> 1833032 bytes save-temps/447.dealII.tar.xz | Bin 10714172 -> 6165516 bytes save-temps/450.soplex.tar.xz | Bin 1215988 -> 709924 bytes save-temps/453.povray.tar.xz | Bin 2277212 -> 1335448 bytes save-temps/454.calculix.tar.xz | Bin 3174532 -> 1232436 bytes save-temps/456.hmmer.tar.xz | Bin 808860 -> 379444 bytes save-temps/458.sjeng.tar.xz | Bin 301852 -> 148100 bytes save-temps/459.GemsFDTD.tar.xz | Bin 521928 -> 145032 bytes save-temps/462.libquantum.tar.xz | Bin 120504 -> 61684 bytes save-temps/464.h264ref.tar.xz | Bin 1827476 -> 563352 bytes save-temps/465.tonto.tar.xz | Bin 6061996 -> 2068872 bytes save-temps/470.lbm.tar.xz | Bin 43972 -> 26328 bytes save-temps/471.omnetpp.tar.xz | Bin 1408972 -> 1066824 bytes save-temps/473.astar.tar.xz | Bin 141708 -> 88336 bytes save-temps/481.wrf.tar.xz | Bin 6952448 -> 1583616 bytes save-temps/482.sphinx3.tar.xz | Bin 519772 -> 254240 bytes save-temps/483.xalancbmk.tar.xz | Bin 15541408 -> 11851876 bytes 114 files changed, 1526289 insertions(+), 1469914 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

1 year, 9 months

[gcc] branch master updated (296cf77b78b -> 00b8a212ea2)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. unknown user pushed a change to branch master in repository gcc. from 296cf77b78b Cleanup libgm2/libm2iso/RTco.cc new 00b8a212ea2 i386: Relax extract location operand mode requirements [PR108516] The 1 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: gcc/config/i386/i386.md | 17 +++++++++++++++-- gcc/config/i386/predicates.md | 8 ++++++++ gcc/testsuite/gcc.target/i386/pr108516-1.c | 19 +++++++++++++++++++ gcc/testsuite/gcc.target/i386/pr108516-2.c | 19 +++++++++++++++++++ 4 files changed, 61 insertions(+), 2 deletions(-) create mode 100644 gcc/testsuite/gcc.target/i386/pr108516-1.c create mode 100644 gcc/testsuite/gcc.target/i386/pr108516-2.c -- To stop receiving notification emails like this one, please contact the administrator of this repository.

1 year, 9 months

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_gnu_cross_build/master-aarch64 updated (cf117a7498 -> cbfaef651c)

by git＠git.linaro.org

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_build/master-aarch64 in repository toolchain/ci/base-artifacts. discards cf117a7498 406: onsuccess: #2109: 7: Success after binutils/gcc/gdb: 26 [...] discards a68fde380b 405: onsuccess: #2108: 7: Success after binutils/gcc/gdb: 3 commits discards cd8b8a4310 404: onsuccess: #2107: 7: Success after binutils/gcc/linux/g [...] discards 748192e4bb 403: onsuccess: #2106: 7: Success after glibc: 12 commits discards 8e15e32b61 402: onsuccess: #2105: 7: Success after binutils/gcc/gdb: 58 [...] discards 367fb662cf 401: onsuccess: #2104: 7: Success after binutils/gcc/gdb: 85 [...] discards 4d67b12cae 400: onsuccess: #2103: 7: Success after binutils/gcc/linux/g [...] discards 55ef132300 399: onsuccess: #2102: 7: Success after binutils/gcc/gdb: 9 commits discards e73286c67c 398: onsuccess: #2101: 7: Success after binutils/gcc/gdb: 6 commits discards 1654297433 397: onsuccess: #2100: 7: Success after binutils/gcc/gdb: 9 commits discards 118cdeae8f 396: onsuccess: #2099: 7: Success after binutils/gcc/linux/g [...] discards 29b8679985 395: onsuccess: #2098: 7: Success after binutils/gcc/linux/g [...] discards 77d3bb0fe5 394: onsuccess: #2097: 7: Success after binutils/gcc/gdb/qem [...] discards 8edb32d2d6 393: onsuccess: #2096: 7: Success after gcc/linux: 45 commits discards 20569739ee 392: onsuccess: #2095: 7: Success after binutils/gcc/linux/g [...] discards 3209001256 391: onsuccess: #2094: 7: Success after binutils/gcc/linux/g [...] discards 06c26afad6 390: onsuccess: #2092: 7: Success after basepoints/gcc-13-57 [...] discards 1c48472754 389: onsuccess: #2091: 7: Success after binutils/gcc/gdb: 12 [...] discards 0179181145 388: onsuccess: #2090: 7: Success after binutils/gcc/glibc/g [...] discards 45035409ca 387: onsuccess: #2089: 7: Success after binutils/gcc/gdb/qem [...] discards d5667a3e96 386: onsuccess: #2087: 7: Success after binutils/gcc/linux/g [...] discards 1bc7965389 385: onsuccess: #2086: 7: Success after binutils/gcc/linux/g [...] discards 1c2ac0e547 384: onsuccess: #2085: 7: Success after binutils/gcc/glibc/g [...] discards c1f3936dec 383: onsuccess: #2084: 7: Success after binutils/gcc/gdb: 4 commits discards 2f03c840ec 382: onsuccess: #2083: 7: Success after binutils/gcc/linux/g [...] discards 0852d976c1 381: onsuccess: #2082: 7: Success after binutils/gcc/gdb/qem [...] discards 9cd96c76ac 380: onsuccess: #2081: 7: Success after basepoints/gcc-13-57 [...] discards 4cb498da92 379: onsuccess: #2080: 7: Success after binutils/gcc/linux/g [...] discards 2d40afc2c8 378: onsuccess: #2079: 7: Success after gcc/qemu: 42 commits discards c28cda068e 377: onsuccess: #2078: 7: Success after glibc-2.37.9000-17-g [...] discards 3312b55ad8 376: onsuccess: #2077: 7: Success after v6.2-rc6-273-g837c07 [...] discards 506e2048fd 375: onsuccess: #2076: 7: Success after binutils/gcc/linux/g [...] discards 742e06027a 374: onsuccess: #2075: 7: Success after binutils/gcc/gdb/qem [...] discards 6e0fefeb8a 373: onsuccess: #2074: 7: Success after binutils/gdb: 4 commits discards ff115bf802 372: onsuccess: #2073: 7: Success after binutils/gcc/gdb: 3 commits discards f5a391e427 371: onsuccess: #2072: 7: Success after binutils/gcc/linux/g [...] discards 83cd6bfd1d 370: onsuccess: #2071: 7: Success after binutils/gcc/gdb/qem [...] discards 39eff91ef6 369: onsuccess: #2070: 7: Success after binutils/gcc/glibc/g [...] discards fcc8c3a7bc 368: onsuccess: #2069: 7: Success after binutils/gcc/linux/g [...] discards a36ccb3080 367: onsuccess: #2068: 7: Success after binutils/gcc/linux/g [...] discards fb691fe6ed 366: onsuccess: #2067: 7: Success after binutils/gcc/linux/g [...] discards e2b58dd31b 365: onsuccess: #2066: 7: Success after binutils/gcc/gdb: 71 [...] discards cf68b39d02 364: onsuccess: #2065: 7: Success after binutils/gcc/linux/g [...] discards 6c88db35f9 363: onsuccess: #2064: 7: Success after binutils/gcc/linux/g [...] discards 58cdda9b54 362: onsuccess: #2063: 7: Success after binutils/gcc/linux/g [...] discards 80654b8e78 361: onsuccess: #2062: 7: Success after binutils/gcc/linux/g [...] discards cb60f94ffe 360: onsuccess: #2061: 7: Success after binutils/gcc/linux/g [...] discards 691c15d696 359: onsuccess: #2060: 7: Success after binutils/gcc/linux/g [...] discards aa5a204dce 358: onsuccess: #2059: 7: Success after binutils/gcc/linux/g [...] discards 775c5df940 357: onsuccess: #2058: 7: Success after binutils/gcc/linux/g [...] discards 78448367a1 356: onsuccess: #2057: 7: Success after binutils/gcc/linux/g [...] discards d2c710c1b8 355: onsuccess: #2056: 7: Success after binutils/gcc/linux/g [...] discards b85470db8b 354: onsuccess: #2055: 7: Success after binutils/gcc/linux/g [...] discards 48551c1b3c 353: onsuccess: #2054: 7: Success after binutils/gcc/glibc/g [...] discards cc463b439c 352: onsuccess: #2053: 7: Success after binutils/gcc/linux/g [...] discards af9f5c7803 351: onsuccess: #2052: 7: Success after binutils/gcc/linux/g [...] discards 140ccf31c7 350: onsuccess: #2051: 7: Success after binutils/gcc/gdb: 35 [...] discards 8afcd873b4 349: onsuccess: #2050: 7: Success after binutils/gcc/linux/g [...] discards f1bb37d5dd 348: onsuccess: #2049: 7: Success after binutils/gcc/gdb: 5 commits discards fe4b943b93 347: onsuccess: #2048: 7: Success after binutils/gcc/gdb: 27 [...] discards cce87857cf 346: onsuccess: #2047: 7: Success after binutils/gcc/linux/g [...] discards f5e3c4be86 345: onsuccess: #2046: 7: Success after basepoints/gcc-13-51 [...] discards 7fcbb38bc1 344: onsuccess: #2045: 7: Success after binutils/gcc/linux/g [...] discards 76ea890b73 343: onsuccess: #2044: 7: Success after binutils/gcc/linux/g [...] discards a1a3e5b7fd 342: onsuccess: #2043: 7: Success after binutils/gcc/gdb: 9 commits discards 97a8561c21 341: onsuccess: #2042: 7: Success after basepoints/gcc-13-51 [...] discards a48ccddca3 340: onsuccess: #2041: 7: Success after binutils/gcc/linux/g [...] discards dd3c8bb235 339: onsuccess: #2040: 7: Success after binutils/gcc/glibc/g [...] discards d7c9208080 338: onsuccess: #2039: 7: Success after gcc/linux/glibc: 37 commits discards 1b2de3efbb 337: onsuccess: #2038: 7: Success after binutils/gcc/gdb: 7 commits discards 4dff57516e 336: onsuccess: #2037: 7: Success after binutils/gcc/linux/g [...] discards 03910a266b 335: onsuccess: #2036: 7: Success after binutils/gcc/gdb: 11 [...] discards aadaa62e80 334: onsuccess: #2035: 7: Success after binutils/gcc/gdb: 16 [...] discards c496853af1 333: onsuccess: #2034: 7: Success after binutils/gcc/gdb: 3 commits discards 051356b3ee 332: onsuccess: #2033: 7: Success after binutils/gcc/linux/g [...] discards f17133b235 331: onsuccess: #2032: 7: Success after binutils/gcc/glibc/g [...] discards d5603f4ea3 330: onsuccess: #2031: 7: Success after binutils/gcc/linux/g [...] discards 6b237e5c49 329: onsuccess: #2030: 7: Success after binutils/gdb: 146 commits discards c2a244614b 328: onsuccess: #2029: 7: Success after binutils/gcc/linux/g [...] discards 8e377185c0 327: onsuccess: #2028: 7: Success after binutils/gcc/gdb/qem [...] discards 38e1e3358a 326: onsuccess: #2027: 7: Success after binutils/gcc/gdb/qem [...] discards 7a685dc8be 325: onsuccess: #2026: 7: Success after binutils/gcc/linux/g [...] discards 51ab93fb62 324: onsuccess: #2025: 7: Success after linux/qemu: 35 commits discards 52a0c56a5e 323: onsuccess: #2024: 7: Success after binutils/gcc/gdb/qem [...] discards 4c597d400d 322: onsuccess: #2023: 7: Success after gcc/linux: 34 commits discards 3a89ce3994 321: onsuccess: #2022: 7: Success after gcc/qemu: 45 commits discards 566461f5f6 320: onsuccess: #2021: 7: Success after binutils/gcc/linux/g [...] discards 85cb74c79e 319: onsuccess: #2020: 7: Success after binutils/gcc/glibc/g [...] discards 93ed45a152 318: onsuccess: #2019: 7: Success after binutils/gcc/gdb/qem [...] discards d39ca8107e 317: onsuccess: #2018: 7: Success after basepoints/gcc-13-50 [...] discards d77276f2f2 316: onsuccess: #2017: 7: Success after binutils/gcc/linux/g [...] discards 2a05cf9ce6 315: onsuccess: #2016: 7: Success after binutils/gcc/linux/g [...] discards 05315de705 314: onsuccess: #2015: 7: Success after binutils/gcc/gdb: 6 commits discards 0599f63f78 313: onsuccess: #2014: 7: Success after binutils/gcc/linux/g [...] discards b5a064da7f 312: onsuccess: #2013: 7: Success after binutils/gcc/glibc/g [...] discards 0024b0e2c6 311: onsuccess: #2012: 7: Success after binutils/gcc/linux/g [...] discards 69da2bf712 310: onsuccess: #2011: 7: Success after binutils/gcc/gdb: 21 [...] discards 8f84944de7 309: onsuccess: #2010: 7: Success after binutils/gcc/glibc/g [...] discards 23580c05bc 308: onsuccess: #2009: 7: Success after binutils/gcc/linux/g [...] discards b02883533a 307: onsuccess: #2008: 5: Success after gdb-13-branchpoint-2 [...] discards 7ab0021ce0 306: force: #2007: 5: Failure after gdb-13-branchpoint-245-g [...] new a4616e73ea 306: force: #2007: 5: Failure after gdb-13-branchpoint-245-g [...] new 0baacd9650 307: onsuccess: #2008: 5: Success after gdb-13-branchpoint-2 [...] new ead7074a99 308: onsuccess: #2009: 7: Success after binutils/gcc/linux/g [...] new 1e0ff90ecc 309: onsuccess: #2010: 7: Success after binutils/gcc/glibc/g [...] new 7ad12cf80a 310: onsuccess: #2011: 7: Success after binutils/gcc/gdb: 21 [...] new f0945beb72 311: onsuccess: #2012: 7: Success after binutils/gcc/linux/g [...] new c1379ba422 312: onsuccess: #2013: 7: Success after binutils/gcc/glibc/g [...] new 1df55ff620 313: onsuccess: #2014: 7: Success after binutils/gcc/linux/g [...] new d1c90d231e 314: onsuccess: #2015: 7: Success after binutils/gcc/gdb: 6 commits new 609bb6fdef 315: onsuccess: #2016: 7: Success after binutils/gcc/linux/g [...] new dd9f062f01 316: onsuccess: #2017: 7: Success after binutils/gcc/linux/g [...] new 9ada5fda03 317: onsuccess: #2018: 7: Success after basepoints/gcc-13-50 [...] new d3714b0df1 318: onsuccess: #2019: 7: Success after binutils/gcc/gdb/qem [...] new 33e8d8c527 319: onsuccess: #2020: 7: Success after binutils/gcc/glibc/g [...] new 5e2075e8db 320: onsuccess: #2021: 7: Success after binutils/gcc/linux/g [...] new 3dfc861dcd 321: onsuccess: #2022: 7: Success after gcc/qemu: 45 commits new cb2d6c1e3d 322: onsuccess: #2023: 7: Success after gcc/linux: 34 commits new 06f274e991 323: onsuccess: #2024: 7: Success after binutils/gcc/gdb/qem [...] new ddfa77e7d4 324: onsuccess: #2025: 7: Success after linux/qemu: 35 commits new b46254d65b 325: onsuccess: #2026: 7: Success after binutils/gcc/linux/g [...] new a9fc776948 326: onsuccess: #2027: 7: Success after binutils/gcc/gdb/qem [...] new d1d217da9d 327: onsuccess: #2028: 7: Success after binutils/gcc/gdb/qem [...] new d4398d2574 328: onsuccess: #2029: 7: Success after binutils/gcc/linux/g [...] new 465488be9f 329: onsuccess: #2030: 7: Success after binutils/gdb: 146 commits new 470d963e49 330: onsuccess: #2031: 7: Success after binutils/gcc/linux/g [...] new 56b687c380 331: onsuccess: #2032: 7: Success after binutils/gcc/glibc/g [...] new 4873af618d 332: onsuccess: #2033: 7: Success after binutils/gcc/linux/g [...] new 9d99a370bf 333: onsuccess: #2034: 7: Success after binutils/gcc/gdb: 3 commits new 30e84c982f 334: onsuccess: #2035: 7: Success after binutils/gcc/gdb: 16 [...] new e50b4b3119 335: onsuccess: #2036: 7: Success after binutils/gcc/gdb: 11 [...] new 964513c78b 336: onsuccess: #2037: 7: Success after binutils/gcc/linux/g [...] new e44cf5ad33 337: onsuccess: #2038: 7: Success after binutils/gcc/gdb: 7 commits new f27eeafa73 338: onsuccess: #2039: 7: Success after gcc/linux/glibc: 37 commits new e7e7c751fa 339: onsuccess: #2040: 7: Success after binutils/gcc/glibc/g [...] new c1e39e8441 340: onsuccess: #2041: 7: Success after binutils/gcc/linux/g [...] new 7da0be3dc0 341: onsuccess: #2042: 7: Success after basepoints/gcc-13-51 [...] new 0a204a9129 342: onsuccess: #2043: 7: Success after binutils/gcc/gdb: 9 commits new 71c38b5e3c 343: onsuccess: #2044: 7: Success after binutils/gcc/linux/g [...] new 93fe6e8fdf 344: onsuccess: #2045: 7: Success after binutils/gcc/linux/g [...] new 9020cd07e8 345: onsuccess: #2046: 7: Success after basepoints/gcc-13-51 [...] new 47b8913291 346: onsuccess: #2047: 7: Success after binutils/gcc/linux/g [...] new 6a7f151bc3 347: onsuccess: #2048: 7: Success after binutils/gcc/gdb: 27 [...] new 4365676791 348: onsuccess: #2049: 7: Success after binutils/gcc/gdb: 5 commits new b6f8588fc5 349: onsuccess: #2050: 7: Success after binutils/gcc/linux/g [...] new e8f3acab90 350: onsuccess: #2051: 7: Success after binutils/gcc/gdb: 35 [...] new eb93f1e12b 351: onsuccess: #2052: 7: Success after binutils/gcc/linux/g [...] new d8dce38ae3 352: onsuccess: #2053: 7: Success after binutils/gcc/linux/g [...] new e79bd5d00b 353: onsuccess: #2054: 7: Success after binutils/gcc/glibc/g [...] new 207e6b2cf8 354: onsuccess: #2055: 7: Success after binutils/gcc/linux/g [...] new fe120a30e2 355: onsuccess: #2056: 7: Success after binutils/gcc/linux/g [...] new 98a7a7dcbd 356: onsuccess: #2057: 7: Success after binutils/gcc/linux/g [...] new 15970bc7aa 357: onsuccess: #2058: 7: Success after binutils/gcc/linux/g [...] new 71744d1051 358: onsuccess: #2059: 7: Success after binutils/gcc/linux/g [...] new dd90e1e533 359: onsuccess: #2060: 7: Success after binutils/gcc/linux/g [...] new e9336a4c11 360: onsuccess: #2061: 7: Success after binutils/gcc/linux/g [...] new aace2b1609 361: onsuccess: #2062: 7: Success after binutils/gcc/linux/g [...] new 4b65f07b27 362: onsuccess: #2063: 7: Success after binutils/gcc/linux/g [...] new f1c4ed34d6 363: onsuccess: #2064: 7: Success after binutils/gcc/linux/g [...] new 7f7f72798a 364: onsuccess: #2065: 7: Success after binutils/gcc/linux/g [...] new bcc7eb34bb 365: onsuccess: #2066: 7: Success after binutils/gcc/gdb: 71 [...] new 6946156296 366: onsuccess: #2067: 7: Success after binutils/gcc/linux/g [...] new b1118210ce 367: onsuccess: #2068: 7: Success after binutils/gcc/linux/g [...] new 0bbba231d6 368: onsuccess: #2069: 7: Success after binutils/gcc/linux/g [...] new d79ef4bcde 369: onsuccess: #2070: 7: Success after binutils/gcc/glibc/g [...] new 60ba2160ce 370: onsuccess: #2071: 7: Success after binutils/gcc/gdb/qem [...] new 4e650a292f 371: onsuccess: #2072: 7: Success after binutils/gcc/linux/g [...] new cd5f60229a 372: onsuccess: #2073: 7: Success after binutils/gcc/gdb: 3 commits new 0b756bfd3f 373: onsuccess: #2074: 7: Success after binutils/gdb: 4 commits new 165539f00e 374: onsuccess: #2075: 7: Success after binutils/gcc/gdb/qem [...] new cb1433efcf 375: onsuccess: #2076: 7: Success after binutils/gcc/linux/g [...] new f7988dcd18 376: onsuccess: #2077: 7: Success after v6.2-rc6-273-g837c07 [...] new b663400b84 377: onsuccess: #2078: 7: Success after glibc-2.37.9000-17-g [...] new a0c55d444a 378: onsuccess: #2079: 7: Success after gcc/qemu: 42 commits new a4e87dcddd 379: onsuccess: #2080: 7: Success after binutils/gcc/linux/g [...] new a887c1654a 380: onsuccess: #2081: 7: Success after basepoints/gcc-13-57 [...] new 98ba6e028d 381: onsuccess: #2082: 7: Success after binutils/gcc/gdb/qem [...] new 9bfdc03b6f 382: onsuccess: #2083: 7: Success after binutils/gcc/linux/g [...] new f2c361b678 383: onsuccess: #2084: 7: Success after binutils/gcc/gdb: 4 commits new 6e0754af62 384: onsuccess: #2085: 7: Success after binutils/gcc/glibc/g [...] new 6f82477bb6 385: onsuccess: #2086: 7: Success after binutils/gcc/linux/g [...] new 5fa5434c9c 386: onsuccess: #2087: 7: Success after binutils/gcc/linux/g [...] new befccc1489 387: onsuccess: #2089: 7: Success after binutils/gcc/gdb/qem [...] new 78c57e1ac2 388: onsuccess: #2090: 7: Success after binutils/gcc/glibc/g [...] new 8241a255cf 389: onsuccess: #2091: 7: Success after binutils/gcc/gdb: 12 [...] new b2422805b3 390: onsuccess: #2092: 7: Success after basepoints/gcc-13-57 [...] new 365c1f40ed 391: onsuccess: #2094: 7: Success after binutils/gcc/linux/g [...] new dcdb6a0060 392: onsuccess: #2095: 7: Success after binutils/gcc/linux/g [...] new 33eb696a94 393: onsuccess: #2096: 7: Success after gcc/linux: 45 commits new 562c9daa16 394: onsuccess: #2097: 7: Success after binutils/gcc/gdb/qem [...] new 73528636c5 395: onsuccess: #2098: 7: Success after binutils/gcc/linux/g [...] new f76d8be5f3 396: onsuccess: #2099: 7: Success after binutils/gcc/linux/g [...] new ab92b2a771 397: onsuccess: #2100: 7: Success after binutils/gcc/gdb: 9 commits new 965e293cdb 398: onsuccess: #2101: 7: Success after binutils/gcc/gdb: 6 commits new 2f98bb5dc1 399: onsuccess: #2102: 7: Success after binutils/gcc/gdb: 9 commits new 75a6aa19ab 400: onsuccess: #2103: 7: Success after binutils/gcc/linux/g [...] new 9635d0ba95 401: onsuccess: #2104: 7: Success after binutils/gcc/gdb: 85 [...] new ef340abfee 402: onsuccess: #2105: 7: Success after binutils/gcc/gdb: 58 [...] new 87bc2573a9 403: onsuccess: #2106: 7: Success after glibc: 12 commits new 88ac7c4656 404: onsuccess: #2107: 7: Success after binutils/gcc/linux/g [...] new 1406da6c3d 405: onsuccess: #2108: 7: Success after binutils/gcc/gdb: 3 commits new 4a20399a15 406: onsuccess: #2109: 7: Success after binutils/gcc/gdb: 26 [...] new cbfaef651c 407: onsuccess: #2110: 7: 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 (cf117a7498) \ N -- N -- N refs/heads/linaro-local/ci/tcwg_gnu_cross_build/master-a [...] 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 1700 -> 1760 bytes 02-prepare_abe/console.log.xz | Bin 2768 -> 2772 bytes 04-build_abe-binutils/console.log.xz | Bin 31236 -> 31284 bytes 05-build_abe-stage1/console.log.xz | Bin 73428 -> 72856 bytes 07-build_abe-linux/console.log.xz | Bin 8372 -> 8352 bytes 08-build_abe-glibc/console.log.xz | Bin 245184 -> 244928 bytes 09-build_abe-stage2/console.log.xz | Bin 205176 -> 204648 bytes 10-build_abe-gdb/console.log.xz | Bin 38464 -> 38368 bytes 11-build_abe-qemu/console.log.xz | Bin 31968 -> 32612 bytes 12-check_regression/console.log.xz | Bin 3808 -> 4552 bytes 13-update_baseline/console.log | 66 +++++++++++++++++------------------ 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 +++++++++++------------ 21 files changed, 64 insertions(+), 64 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

1 year, 9 months

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_kernel/llvm-master-arm-mainline-allnoconfig updated (54d1e3ba7e -> 85bb8738c8)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. tcwg-buildslave pushed a change to branch linaro-local/ci/tcwg_kernel/llvm-master-arm-mainline-allnoconfig in repository toolchain/ci/base-artifacts. from 54d1e3ba7e 43: onsuccess: #457: all: Success after binutils/llvm/linux/ [...] new 85bb8738c8 44: onsuccess: #458: all: Success after binutils/llvm/linux/ [...] The 1 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 2020 -> 1760 bytes 02-prepare_abe/console.log.xz | Bin 2780 -> 2768 bytes 03-build_abe-binutils/console.log.xz | Bin 31412 -> 31052 bytes 04-build_kernel_llvm/console.log.xz | Bin 63304 -> 63964 bytes 05-build_abe-qemu/console.log.xz | Bin 30716 -> 32336 bytes 06-build_linux/console.log.xz | Bin 3116 -> 3056 bytes 07-boot_linux/console.log.xz | Bin 496 -> 496 bytes 08-check_regression/console.log.xz | Bin 4328 -> 4328 bytes dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/linux_rev | 2 +- git/llvm_rev | 2 +- git/qemu_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 2 +- mail/mail-subject.txt | 2 +- manifest.sh | 32 ++++++++++++++++---------------- 17 files changed, 24 insertions(+), 24 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

1 year, 9 months

[gcc] branch master updated (086a1df4374 -> 296cf77b78b)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. unknown user pushed a change to branch master in repository gcc. from 086a1df4374 Fortran: Add !GCC$ attributes NOINLINE,NORETURN,WEAK new 296cf77b78b Cleanup libgm2/libm2iso/RTco.cc The 1 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: libgm2/libm2iso/RTco.cc | 3 +-- 1 file changed, 1 insertion(+), 2 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

1 year, 9 months

[linux] branch master updated (ceaa837f96ad -> b408817d4884)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. unknown user pushed a change to branch master in repository linux. from ceaa837f96ad Linux 6.2-rc8 new eb4b55f2f26f platform/x86/intel/vsec: Add support for Meteor Lake new b408817d4884 Merge tag 'platform-drivers-x86-v6.2-5' of git://git.kerne [...] The 2 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: drivers/platform/x86/intel/vsec.c | 9 +++++++++ 1 file changed, 9 insertions(+) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

1 year, 9 months

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_gnu_cross_check_gcc/master-arm updated (aff339e825 -> 9a160ecf1a)

by git＠git.linaro.org

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 aff339e825 407: onsuccess: #2228: 1: Success after binutils/gcc/linux/g [...] discards ad37064fd2 406: onsuccess: #2227: 1: Success after binutils/linux/glibc [...] discards d3301d7980 405: onsuccess: #2226: 1: Success after gcc/glibc: 39 commits discards b417f833ba 404: onsuccess: #2225: 1: Success after binutils/gcc/gdb: 10 [...] discards 0ba59f2241 403: onsuccess: #2224: 1: Success after binutils/gcc/linux/g [...] discards d66d7ddfcb 402: onsuccess: #2223: 1: Success after binutils/gcc/gdb: 10 [...] discards 578a92e522 401: onsuccess: #2222: 1: Success after binutils/gcc/gdb: 10 [...] discards 973093ceaa 400: onsuccess: #2221: 1: Success after binutils/gcc/linux/g [...] discards f3f1c9b43b 399: onsuccess: #2220: 1: Success after binutils/gcc/linux/g [...] discards 71bed2a178 398: onsuccess: #2219: 1: Success after binutils/gcc/gdb/qem [...] discards f8baf9605d 397: onsuccess: #2218: 1: Success after binutils/gcc/linux/g [...] discards 11afcf3fdc 396: onsuccess: #2217: 1: Success after binutils/gcc/linux/g [...] discards b1535c5af2 395: onsuccess: #2216: 1: Success after binutils/gcc/linux/g [...] discards 3f545e4f66 394: onsuccess: #2215: 1: Success after binutils/gcc/gdb: 8 commits discards 65bfd50cbb 393: onsuccess: #2214: 1: Success after binutils/gcc/gdb: 12 [...] discards aea1dc2762 392: onsuccess: #2213: 1: Success after binutils/gcc/glibc/g [...] discards 461452133e 391: onsuccess: #2212: 1: Success after binutils/gcc/gdb/qem [...] discards 70ecd7951b 390: onsuccess: #2211: 1: Success after binutils/gcc/linux/g [...] discards a0875e2108 389: onsuccess: #2210: 1: Success after binutils/gcc/linux/g [...] discards 604078c5d3 388: onsuccess: #2209: 1: Success after binutils/gcc/glibc/g [...] discards d6bf70032a 387: onsuccess: #2208: 1: Success after gcc: 2 commits discards 3671874d07 386: onsuccess: #2207: 1: Success after binutils/gcc/linux/g [...] discards eeb4fc645c 385: onsuccess: #2206: 1: Success after binutils/gcc/glibc/g [...] discards 6ab890fdac 384: onsuccess: #2205: 1: Success after gcc: 2 commits discards ec2db6717f 383: onsuccess: #2204: 1: Success after binutils/gcc/linux/g [...] discards e39f92b38b 382: onsuccess: #2203: 1: Success after gcc/qemu: 42 commits discards 9143596843 381: onsuccess: #2202: 1: Success after glibc-2.37.9000-17-g [...] discards 65f020e52b 380: onsuccess: #2201: 1: Success after binutils/gcc/linux/g [...] discards ed65c295a3 379: onsuccess: #2200: 1: Success after binutils/gcc/linux/g [...] discards 3545ddd447 378: onsuccess: #2199: 1: Success after binutils/gdb: 4 commits discards d654fe0abd 377: onsuccess: #2198: 1: Success after binutils/gcc/gdb: 3 commits discards 3c39569c7e 376: onsuccess: #2197: 1: Success after binutils/gcc/linux/g [...] discards 60c5acc93a 375: onsuccess: #2195: 1: Success after binutils/gcc/gdb/qem [...] discards e1c353648b 374: onsuccess: #2194: 1: Success after binutils/gcc/linux/g [...] discards 11327ec5ce 373: onsuccess: #2193: 1: Success after binutils/gcc/glibc/g [...] discards b142b73545 372: onsuccess: #2192: 1: Success after binutils/gcc/linux/g [...] discards a8f582d91e 371: onsuccess: #2191: 1: Success after binutils/gcc/gdb: 10 [...] discards 1ceede6a5b 370: onsuccess: #2190: 1: Success after binutils/gcc/linux/g [...] discards 9af97e876e 369: onsuccess: #2189: 1: Success after binutils/gcc/linux/g [...] discards 0cd679a3e5 368: onsuccess: #2188: 1: Success after binutils/gcc/linux/g [...] discards 95ab4eab16 367: onsuccess: #2187: 1: Success after binutils/gcc/gdb: 14 [...] discards 0615b03e29 366: onsuccess: #2186: 1: Success after binutils/gcc/linux/g [...] discards 2c936cb8ce 365: onsuccess: #2185: 1: Success after binutils/gcc/linux/g [...] discards aa2cdde22c 364: onsuccess: #2184: 1: Success after binutils/gcc/linux/g [...] discards 1b15163fdd 363: onsuccess: #2183: 1: Success after binutils/gcc/linux/g [...] discards 86324a1792 362: onsuccess: #2182: 1: Success after binutils/gcc/linux/g [...] discards c6d44f69ac 361: onsuccess: #2181: 1: Success after binutils/gcc/linux/g [...] discards 4928fdb092 360: onsuccess: #2180: 1: Success after binutils/gcc/linux/g [...] discards 1168a29bdb 359: onsuccess: #2179: 1: Success after binutils/gcc/glibc/g [...] discards 0f75f8d9de 358: onsuccess: #2178: 1: Success after binutils/gcc/linux/g [...] discards 7ac6166c20 357: onsuccess: #2177: 1: Success after binutils/gcc/linux/g [...] discards 61dec95a18 356: onsuccess: #2176: 1: Success after binutils/gcc/linux/g [...] discards 313c1df9dd 355: onsuccess: #2175: 1: Success after binutils/gcc/linux/g [...] discards 3da6167ac3 354: onsuccess: #2174: 1: Success after binutils/gcc/linux/g [...] discards df473b493a 353: onsuccess: #2173: 1: Success after binutils/gcc/gdb: 27 [...] discards 07e228b957 352: onsuccess: #2172: 1: Success after binutils/gcc/linux/g [...] discards 1b00ad2374 351: onsuccess: #2171: 1: Success after gcc/linux: 15 commits discards a39e8f6c72 350: onsuccess: #2170: 1: Success after binutils/gcc/linux/g [...] discards 778cfd326c 349: onsuccess: #2169: 1: Success after binutils/gcc/linux/g [...] discards 1c77b03c50 348: onsuccess: #2168: 1: Success after binutils/gcc/gdb: 9 commits discards db5bd77494 347: onsuccess: #2167: 1: Success after basepoints/gcc-13-51 [...] discards 8ee9b28539 346: onsuccess: #2166: 1: Success after binutils/gcc/linux/g [...] discards a3bfdcb804 345: onsuccess: #2165: 1: Success after binutils/gcc/glibc/g [...] discards bf9e375342 344: onsuccess: #2164: 1: Success after gcc/linux/glibc: 37 commits discards fc755a63eb 343: onsuccess: #2163: 1: Success after binutils/gcc/gdb: 7 commits discards 5f5a243fca 342: onsuccess: #2162: 1: Success after binutils/gcc/linux/g [...] discards e99fe04b05 341: onsuccess: #2161: 1: Success after binutils/gcc/gdb: 11 [...] discards e72d828884 340: onsuccess: #2160: 1: Success after binutils/gcc/gdb: 15 [...] discards 1beb5183cc 339: onsuccess: #2159: 1: Success after binutils/gcc/gdb: 4 commits discards c406ad1018 338: onsuccess: #2158: 1: Success after binutils/gcc/linux/g [...] discards afa9b44d63 337: onsuccess: #2157: 1: Success after binutils/gcc/glibc/g [...] discards 9afa398da2 336: onsuccess: #2156: 1: Success after binutils/gcc/linux/g [...] discards ef505445b8 335: onsuccess: #2155: 1: Success after binutils/gdb: 146 commits discards 54dde8ed6a 334: onsuccess: #2154: 1: Success after binutils/gcc/linux/g [...] discards 3f90243009 333: onsuccess: #2153: 1: Success after binutils/gcc/gdb/qem [...] discards c4dfdec98f 332: onsuccess: #2152: 1: Success after binutils/gcc/gdb/qem [...] discards e95faca4e8 331: onsuccess: #2151: 1: Success after binutils/gcc/linux/g [...] discards 5cb46f3b05 330: onsuccess: #2150: 1: Success after linux/qemu: 36 commits discards a2519f12c8 329: onsuccess: #2149: 1: Success after binutils/gcc/gdb/qem [...] discards 285c14716e 328: onsuccess: #2148: 1: Success after gcc/linux/qemu: 78 commits discards cae80273af 327: onsuccess: #2147: 1: Success after basepoints/gcc-13-50 [...] discards cbb0152f82 326: onsuccess: #2146: 1: Success after binutils/gcc/linux/g [...] discards 5faf6b3a1a 325: onsuccess: #2145: 1: Success after binutils/gcc/glibc/g [...] discards 990a99708e 324: onsuccess: #2144: 1: Success after binutils/gcc/gdb/qem [...] discards 0d2c572f64 323: onsuccess: #2143: 1: Success after basepoints/gcc-13-50 [...] discards 8f3d875153 322: onsuccess: #2142: 1: Success after binutils/gcc/linux/g [...] discards 8eb17d9316 321: onsuccess: #2141: 1: Success after binutils/gcc/linux/g [...] discards 095fa54700 320: onsuccess: #2140: 1: Success after binutils/gcc/gdb: 6 commits discards e131d7418f 319: onsuccess: #2139: 1: Success after binutils/gcc/gdb: 11 [...] discards 69f1b591e8 318: onsuccess: #2138: 1: Success after binutils/gcc/linux/g [...] discards 43b6e101df 317: onsuccess: #2137: 1: Success after binutils/gcc/linux/g [...] discards d0798f7bf6 316: onsuccess: #2136: 1: Success after binutils/gcc/gdb: 26 [...] discards d08a5bfe79 315: onsuccess: #2135: 1: Success after binutils/gcc/gdb: 11 [...] discards 548ce13611 314: onsuccess: #2134: 1: Success after binutils/gcc/glibc/g [...] discards fa4eacf721 313: onsuccess: #2133: 1: Success after binutils/gcc/linux/g [...] discards 9237408ab6 312: onsuccess: #2132: 1: Success after glibc-2.36.9000-416- [...] discards f487730857 311: onsuccess: #2130: 1: Success after gcc: 4 commits discards 5df8561d7c 310: onsuccess: #2129: 1: Success after binutils: 4 commits discards cb8e0ad290 309: onsuccess: #2127: 1: Success after binutils/gcc/glibc/g [...] discards 283af43ad1 308: onsuccess: #2126: 1: Success after binutils/gcc/linux/g [...] discards b86ae5f31c 307: onsuccess: #2124: 1: Success after gcc: 2 commits new af236204a4 307: onsuccess: #2124: 1: Success after gcc: 2 commits new 48b1427755 308: onsuccess: #2126: 1: Success after binutils/gcc/linux/g [...] new a10e0f2976 309: onsuccess: #2127: 1: Success after binutils/gcc/glibc/g [...] new 9d15d3524f 310: onsuccess: #2129: 1: Success after binutils: 4 commits new 4a3a3bb340 311: onsuccess: #2130: 1: Success after gcc: 4 commits new 50e4f9923c 312: onsuccess: #2132: 1: Success after glibc-2.36.9000-416- [...] new 34eec244bf 313: onsuccess: #2133: 1: Success after binutils/gcc/linux/g [...] new cc01545b77 314: onsuccess: #2134: 1: Success after binutils/gcc/glibc/g [...] new 6b96531694 315: onsuccess: #2135: 1: Success after binutils/gcc/gdb: 11 [...] new cb70063a39 316: onsuccess: #2136: 1: Success after binutils/gcc/gdb: 26 [...] new be0332442d 317: onsuccess: #2137: 1: Success after binutils/gcc/linux/g [...] new b7a84fc61b 318: onsuccess: #2138: 1: Success after binutils/gcc/linux/g [...] new 1e304c58e5 319: onsuccess: #2139: 1: Success after binutils/gcc/gdb: 11 [...] new 60fcc4c09c 320: onsuccess: #2140: 1: Success after binutils/gcc/gdb: 6 commits new 87c7f5be2f 321: onsuccess: #2141: 1: Success after binutils/gcc/linux/g [...] new 8ab831060f 322: onsuccess: #2142: 1: Success after binutils/gcc/linux/g [...] new 2f605e0312 323: onsuccess: #2143: 1: Success after basepoints/gcc-13-50 [...] new 14cad5c4cb 324: onsuccess: #2144: 1: Success after binutils/gcc/gdb/qem [...] new b4ad41c25b 325: onsuccess: #2145: 1: Success after binutils/gcc/glibc/g [...] new ca14fd946c 326: onsuccess: #2146: 1: Success after binutils/gcc/linux/g [...] new b8bcbdae48 327: onsuccess: #2147: 1: Success after basepoints/gcc-13-50 [...] new 2b484ba430 328: onsuccess: #2148: 1: Success after gcc/linux/qemu: 78 commits new e8269cf158 329: onsuccess: #2149: 1: Success after binutils/gcc/gdb/qem [...] new 69e7e9ed50 330: onsuccess: #2150: 1: Success after linux/qemu: 36 commits new 85e74243f0 331: onsuccess: #2151: 1: Success after binutils/gcc/linux/g [...] new 1b378edfab 332: onsuccess: #2152: 1: Success after binutils/gcc/gdb/qem [...] new 0180d54aba 333: onsuccess: #2153: 1: Success after binutils/gcc/gdb/qem [...] new 600e3b4976 334: onsuccess: #2154: 1: Success after binutils/gcc/linux/g [...] new 608fa06d0c 335: onsuccess: #2155: 1: Success after binutils/gdb: 146 commits new 8e56325308 336: onsuccess: #2156: 1: Success after binutils/gcc/linux/g [...] new 11ac2a8f41 337: onsuccess: #2157: 1: Success after binutils/gcc/glibc/g [...] new ca3f11775a 338: onsuccess: #2158: 1: Success after binutils/gcc/linux/g [...] new 2f3a2d6175 339: onsuccess: #2159: 1: Success after binutils/gcc/gdb: 4 commits new cb66b23814 340: onsuccess: #2160: 1: Success after binutils/gcc/gdb: 15 [...] new dc0ab4bc4a 341: onsuccess: #2161: 1: Success after binutils/gcc/gdb: 11 [...] new 32f65c65e1 342: onsuccess: #2162: 1: Success after binutils/gcc/linux/g [...] new d9e992468a 343: onsuccess: #2163: 1: Success after binutils/gcc/gdb: 7 commits new 262e44aa41 344: onsuccess: #2164: 1: Success after gcc/linux/glibc: 37 commits new 2aef378fbd 345: onsuccess: #2165: 1: Success after binutils/gcc/glibc/g [...] new 26e4123d49 346: onsuccess: #2166: 1: Success after binutils/gcc/linux/g [...] new 63469ec0e1 347: onsuccess: #2167: 1: Success after basepoints/gcc-13-51 [...] new 7bd4fe5718 348: onsuccess: #2168: 1: Success after binutils/gcc/gdb: 9 commits new 00f7ecbb38 349: onsuccess: #2169: 1: Success after binutils/gcc/linux/g [...] new cb7c93ef0b 350: onsuccess: #2170: 1: Success after binutils/gcc/linux/g [...] new 064378c4b8 351: onsuccess: #2171: 1: Success after gcc/linux: 15 commits new 144da59b22 352: onsuccess: #2172: 1: Success after binutils/gcc/linux/g [...] new 50bca415e2 353: onsuccess: #2173: 1: Success after binutils/gcc/gdb: 27 [...] new 53f0d66ebc 354: onsuccess: #2174: 1: Success after binutils/gcc/linux/g [...] new 445bbaab2b 355: onsuccess: #2175: 1: Success after binutils/gcc/linux/g [...] new 7b5f89df44 356: onsuccess: #2176: 1: Success after binutils/gcc/linux/g [...] new a80eafd2ad 357: onsuccess: #2177: 1: Success after binutils/gcc/linux/g [...] new d15dc63a7d 358: onsuccess: #2178: 1: Success after binutils/gcc/linux/g [...] new f9e9241a10 359: onsuccess: #2179: 1: Success after binutils/gcc/glibc/g [...] new 48d7149ea6 360: onsuccess: #2180: 1: Success after binutils/gcc/linux/g [...] new 8dd923b78b 361: onsuccess: #2181: 1: Success after binutils/gcc/linux/g [...] new 59eefa6c49 362: onsuccess: #2182: 1: Success after binutils/gcc/linux/g [...] new c1ca1be5ce 363: onsuccess: #2183: 1: Success after binutils/gcc/linux/g [...] new 09ab7a85c4 364: onsuccess: #2184: 1: Success after binutils/gcc/linux/g [...] new 20bc1186fe 365: onsuccess: #2185: 1: Success after binutils/gcc/linux/g [...] new 116dffebc7 366: onsuccess: #2186: 1: Success after binutils/gcc/linux/g [...] new 3ca526829a 367: onsuccess: #2187: 1: Success after binutils/gcc/gdb: 14 [...] new 1f24341dfb 368: onsuccess: #2188: 1: Success after binutils/gcc/linux/g [...] new af4e78a50b 369: onsuccess: #2189: 1: Success after binutils/gcc/linux/g [...] new dc3997a021 370: onsuccess: #2190: 1: Success after binutils/gcc/linux/g [...] new 228ac3c777 371: onsuccess: #2191: 1: Success after binutils/gcc/gdb: 10 [...] new c35372c0cb 372: onsuccess: #2192: 1: Success after binutils/gcc/linux/g [...] new 635622b795 373: onsuccess: #2193: 1: Success after binutils/gcc/glibc/g [...] new e61d36d2e8 374: onsuccess: #2194: 1: Success after binutils/gcc/linux/g [...] new d593c22a67 375: onsuccess: #2195: 1: Success after binutils/gcc/gdb/qem [...] new b923fcc188 376: onsuccess: #2197: 1: Success after binutils/gcc/linux/g [...] new 458aa10650 377: onsuccess: #2198: 1: Success after binutils/gcc/gdb: 3 commits new eaabd0e4e7 378: onsuccess: #2199: 1: Success after binutils/gdb: 4 commits new 1c05901069 379: onsuccess: #2200: 1: Success after binutils/gcc/linux/g [...] new 7dd8ae3c5f 380: onsuccess: #2201: 1: Success after binutils/gcc/linux/g [...] new d0353521b9 381: onsuccess: #2202: 1: Success after glibc-2.37.9000-17-g [...] new bf4d17a432 382: onsuccess: #2203: 1: Success after gcc/qemu: 42 commits new 637befe854 383: onsuccess: #2204: 1: Success after binutils/gcc/linux/g [...] new 8ea7e2c3e4 384: onsuccess: #2205: 1: Success after gcc: 2 commits new 78c2f5595a 385: onsuccess: #2206: 1: Success after binutils/gcc/glibc/g [...] new 2a4d914f1b 386: onsuccess: #2207: 1: Success after binutils/gcc/linux/g [...] new 193ef8e8b3 387: onsuccess: #2208: 1: Success after gcc: 2 commits new 4b76ce3149 388: onsuccess: #2209: 1: Success after binutils/gcc/glibc/g [...] new 5003621f61 389: onsuccess: #2210: 1: Success after binutils/gcc/linux/g [...] new f811aa7fac 390: onsuccess: #2211: 1: Success after binutils/gcc/linux/g [...] new 8f9966a4b2 391: onsuccess: #2212: 1: Success after binutils/gcc/gdb/qem [...] new 4df5395413 392: onsuccess: #2213: 1: Success after binutils/gcc/glibc/g [...] new a05342a463 393: onsuccess: #2214: 1: Success after binutils/gcc/gdb: 12 [...] new 949b5f8e14 394: onsuccess: #2215: 1: Success after binutils/gcc/gdb: 8 commits new 11f9eb1953 395: onsuccess: #2216: 1: Success after binutils/gcc/linux/g [...] new cee1ad0451 396: onsuccess: #2217: 1: Success after binutils/gcc/linux/g [...] new 85949951a2 397: onsuccess: #2218: 1: Success after binutils/gcc/linux/g [...] new d136e06fbc 398: onsuccess: #2219: 1: Success after binutils/gcc/gdb/qem [...] new cc8affcc78 399: onsuccess: #2220: 1: Success after binutils/gcc/linux/g [...] new 07051fef7d 400: onsuccess: #2221: 1: Success after binutils/gcc/linux/g [...] new ce29ca9977 401: onsuccess: #2222: 1: Success after binutils/gcc/gdb: 10 [...] new 04187331ba 402: onsuccess: #2223: 1: Success after binutils/gcc/gdb: 10 [...] new 53feba3716 403: onsuccess: #2224: 1: Success after binutils/gcc/linux/g [...] new 709aea27d0 404: onsuccess: #2225: 1: Success after binutils/gcc/gdb: 10 [...] new e571b6bbc2 405: onsuccess: #2226: 1: Success after gcc/glibc: 39 commits new a73fe56f2d 406: onsuccess: #2227: 1: Success after binutils/linux/glibc [...] new f020a3bd77 407: onsuccess: #2228: 1: Success after binutils/gcc/linux/g [...] new 9a160ecf1a 408: onsuccess: #2229: 1: Success after binutils/gcc/gdb: 26 [...] 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 (aff339e825) \ 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 1756 -> 1756 bytes 02-prepare_abe/console.log.xz | Bin 2776 -> 2764 bytes 03-build_abe-binutils/console.log.xz | Bin 31028 -> 31016 bytes 04-build_abe-stage1/console.log.xz | Bin 91412 -> 91372 bytes 06-build_abe-linux/console.log.xz | Bin 8360 -> 8360 bytes 07-build_abe-glibc/console.log.xz | Bin 236372 -> 235948 bytes 08-build_abe-stage2/console.log.xz | Bin 228632 -> 227284 bytes 09-build_abe-gdb/console.log.xz | Bin 38340 -> 38148 bytes 10-build_abe-qemu/console.log.xz | Bin 30956 -> 31096 bytes 11-build_abe-dejagnu/console.log.xz | Bin 3884 -> 3884 bytes 12-build_abe-check_gcc/console.log.xz | Bin 2792 -> 2764 bytes 13-check_regression/console.log.xz | Bin 6080 -> 6228 bytes 13-check_regression/extra-bisect-params | 1 - 13-check_regression/fails.sum | 6 - 13-check_regression/mail-body.txt | 42 +- 13-check_regression/results.compare | 25 +- 13-check_regression/results.compare2 | 45 +- 13-check_regression/results.regressions | 26 - 14-update_baseline/console.log | 62 +- 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 | 44 +- mail/mail-subject.txt | 2 +- manifest.sh | 32 +- results | 26 - sumfiles/g++.log.xz | Bin 2662376 -> 2633360 bytes sumfiles/g++.sum | 22 +- sumfiles/gcc.log.xz | Bin 2199044 -> 2180684 bytes sumfiles/gcc.sum | 2108 ++++++++++++++++--------------- sumfiles/gfortran.log.xz | Bin 892396 -> 889360 bytes sumfiles/gfortran.sum | 4 +- sumfiles/libatomic.log.xz | Bin 2260 -> 2260 bytes sumfiles/libatomic.sum | 2 +- sumfiles/libgomp.log.xz | Bin 216984 -> 216820 bytes sumfiles/libgomp.sum | 2 +- sumfiles/libitm.log.xz | Bin 2676 -> 2664 bytes sumfiles/libitm.sum | 2 +- sumfiles/libstdc++.log.xz | Bin 443340 -> 435788 bytes sumfiles/libstdc++.sum | 26 +- 42 files changed, 1241 insertions(+), 1246 deletions(-) delete mode 100644 13-check_regression/extra-bisect-params delete mode 100644 13-check_regression/fails.sum delete mode 100644 13-check_regression/results.regressions -- To stop receiving notification emails like this one, please contact the administrator of this repository.

1 year, 9 months

Jump to page: