Tcwg-commits February 2023

tcwg-commits@lists.linaro.org

5 participants
3393 discussions

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_bmk-code_speed-spec2k6/gnu-aarch64-master-O3_LTO updated (fa4478255f -> d69b0973da)

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_speed-spec2k6/gnu-aarch64-master-O3_LTO in repository toolchain/ci/base-artifacts. from fa4478255f 73: onsuccess: #27: 1: [TCWG CI] No change after glibc: 35 commits new d69b0973da 74: onsuccess: #28: 1: [TCWG CI] No change after linux: 676 commits 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 1832 -> 1832 bytes 02-prepare_abe/console.log.xz | Bin 2772 -> 2772 bytes 03-build_abe-binutils/console.log.xz | Bin 31776 -> 31820 bytes 04-build_abe-stage1/console.log.xz | Bin 73872 -> 73780 bytes 06-build_abe-linux/console.log.xz | Bin 8760 -> 8696 bytes 07-build_abe-glibc/console.log.xz | Bin 247160 -> 246960 bytes 08-build_abe-stage2/console.log.xz | Bin 183692 -> 183032 bytes 09-benchmark/benchmark-build.log | 114 +- 09-benchmark/benchmark.log | 112 +- 09-benchmark/console.log.xz | Bin 3920 -> 3908 bytes 10-check_regression/console.log.xz | Bin 6324 -> 6400 bytes .../csv-results-vs-first-1/perf.csv | 167 +- .../csv-results-vs-first-1/results.csv | 12185 +- .../csv-results-vs-first-1/size.csv | 453096 +++++++++-------- 10-check_regression/csv-results-vs-first-1/sve.csv | 38 +- .../csv-results-vs-first-1/vect.csv | 38 +- 10-check_regression/csv-results-vs-prev-0/perf.csv | 160 +- .../csv-results-vs-prev-0/results.csv | 18902 +- 10-check_regression/csv-results-vs-prev-0/size.csv | 456975 +++++++++--------- 10-check_regression/csv-results-vs-prev-0/sve.csv | 34 +- 10-check_regression/csv-results-vs-prev-0/vect.csv | 34 +- 10-check_regression/csv-results-vs-prev-1/perf.csv | 167 +- .../csv-results-vs-prev-1/results.csv | 12185 +- 10-check_regression/csv-results-vs-prev-1/size.csv | 453096 +++++++++-------- 10-check_regression/csv-results-vs-prev-1/sve.csv | 38 +- 10-check_regression/csv-results-vs-prev-1/vect.csv | 38 +- 10-check_regression/results-vs-first-brief.csv | 68 +- 10-check_regression/results-vs-first-full.csv | 175 +- 10-check_regression/results-vs-first-internal.csv | 82 +- 10-check_regression/results-vs-first.csv | 82 +- 10-check_regression/results-vs-first.log | 1298 +- 10-check_regression/results-vs-prev-brief.csv | 68 +- 10-check_regression/results-vs-prev-full.csv | 187 +- 10-check_regression/results-vs-prev-internal.csv | 82 +- 10-check_regression/results-vs-prev.csv | 82 +- 10-check_regression/results-vs-prev.log | 1556 +- dashboard/dashboard-generate.sh | 2 +- .../400.perlbench/results-metadata.json | 10 +- .../squad-vs-first/401.bzip2/results-metadata.json | 10 +- .../squad-vs-first/403.gcc/results-metadata.json | 10 +- .../410.bwaves/results-metadata.json | 10 +- .../416.gamess/results-metadata.json | 10 +- .../squad-vs-first/429.mcf/results-metadata.json | 10 +- .../squad-vs-first/433.milc/results-metadata.json | 10 +- .../434.zeusmp/results-metadata.json | 10 +- .../squad-vs-first/434.zeusmp/results-metrics.json | 2 +- .../435.gromacs/results-metadata.json | 10 +- .../436.cactusADM/results-metadata.json | 10 +- .../437.leslie3d/results-metadata.json | 10 +- .../437.leslie3d/results-metrics.json | 2 +- .../squad-vs-first/444.namd/results-metadata.json | 10 +- .../squad-vs-first/444.namd/results-metrics.json | 2 +- .../squad-vs-first/445.gobmk/results-metadata.json | 10 +- .../447.dealII/results-metadata.json | 10 +- .../squad-vs-first/447.dealII/results-metrics.json | 2 +- .../450.soplex/results-metadata.json | 10 +- .../453.povray/results-metadata.json | 10 +- .../454.calculix/results-metadata.json | 10 +- .../squad-vs-first/456.hmmer/results-metadata.json | 10 +- .../squad-vs-first/456.hmmer/results-metrics.json | 2 +- .../squad-vs-first/458.sjeng/results-metadata.json | 10 +- .../459.GemsFDTD/results-metadata.json | 10 +- .../459.GemsFDTD/results-metrics.json | 2 +- .../462.libquantum/results-metadata.json | 10 +- .../464.h264ref/results-metadata.json | 10 +- .../464.h264ref/results-metrics.json | 2 +- .../squad-vs-first/465.tonto/results-metadata.json | 10 +- .../squad-vs-first/465.tonto/results-metrics.json | 2 +- .../squad-vs-first/470.lbm/results-metadata.json | 10 +- .../471.omnetpp/results-metadata.json | 10 +- .../471.omnetpp/results-metrics.json | 2 +- .../squad-vs-first/473.astar/results-metadata.json | 10 +- .../squad-vs-first/481.wrf/results-metadata.json | 10 +- .../482.sphinx3/results-metadata.json | 10 +- .../483.xalancbmk/results-metadata.json | 10 +- .../483.xalancbmk/results-metrics.json | 2 +- .../squad-vs-first/Mean/results-metadata.json | 10 +- dashboard/squad-vs-first/dashboard-push-squad.sh | 122 +- git/linux_rev | 2 +- mail/jira-body.txt | 14 +- mail/mail-body.txt | 14 +- mail/mail-subject.txt | 2 +- manifest.sh | 20 +- results_id | 2 +- 84 files changed, 707385 insertions(+), 704172 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

1 year, 9 months

[linux] branch master updated (db27c22251e7 -> 95078069c1e7)

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 db27c22251e7 Merge tag 'kbuild-fixes-v6.2-4' of git://git.kernel.org/pu [...] new 101ca8d05913 rtc: efi: Enable SET/GET WAKEUP services as optional new 51b3802e7960 dt-bindings: rtc: qcom-pm8xxx: allow 'wakeup-source' property new 08279468a294 rtc: sunplus: fix format string for printing resource new 95078069c1e7 Merge tag 'rtc-6.2-fixes' of git://git.kernel.org/pub/scm/ [...] The 4 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: .../devicetree/bindings/rtc/qcom-pm8xxx-rtc.yaml | 2 + drivers/rtc/rtc-efi.c | 48 ++++++++++++---------- drivers/rtc/rtc-sunplus.c | 4 +- include/linux/efi.h | 3 +- 4 files changed, 33 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_kernel/llvm-master-arm-stable-allmodconfig updated (8f08030ca7 -> f14c459725)

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-stable-allmodconfig in repository toolchain/ci/base-artifacts. from 8f08030ca7 60: onsuccess: #543: 23021: Success after llvm: 192 commits new f14c459725 61: onsuccess: #545: 23021: Success after binutils/llvm/qemu [...] 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 1772 -> 1796 bytes 02-prepare_abe/console.log.xz | Bin 2784 -> 2784 bytes 03-build_abe-binutils/console.log.xz | Bin 31468 -> 31860 bytes 04-build_kernel_llvm/console.log.xz | Bin 65136 -> 63460 bytes 05-build_abe-qemu/console.log.xz | Bin 31936 -> 31352 bytes 06-build_linux/console.log.xz | Bin 4092 -> 4260 bytes 08-check_regression/console.log.xz | Bin 3060 -> 4128 bytes 08-check_regression/mail-body.txt | 13 +------------ 09-update_baseline/console.log | 8 ++++---- dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/llvm_rev | 2 +- git/qemu_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 15 ++------------- mail/mail-subject.txt | 2 +- manifest.sh | 28 +++++++++++++++------------- 17 files changed, 28 insertions(+), 48 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-aarch64-stable-allmodconfig updated (521f73743f -> 0aa0eba590)

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-aarch64-stable-allmodconfig in repository toolchain/ci/base-artifacts. from 521f73743f 53: onsuccess: #555: all: Success after v7.2.0-912-g026817fb [...] new 0aa0eba590 54: force: #556: all: Success after llvm: 340 commits 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 1892 -> 1764 bytes 02-prepare_abe/console.log.xz | Bin 2760 -> 2764 bytes 03-build_abe-binutils/console.log.xz | Bin 31312 -> 31364 bytes 04-build_kernel_llvm/console.log.xz | Bin 64920 -> 64388 bytes 05-build_abe-qemu/console.log.xz | Bin 31900 -> 31884 bytes 06-build_linux/console.log.xz | Bin 3384 -> 3336 bytes 08-check_regression/console.log.xz | Bin 2640 -> 2844 bytes 09-update_baseline/console.log | 2 +- dashboard/dashboard-generate.sh | 2 +- git/llvm_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 2 +- mail/mail-subject.txt | 2 +- manifest.sh | 16 ++++++++-------- 14 files changed, 14 insertions(+), 14 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_gnu_cross_check_gcc/master-aarch64 updated (d8c84dc13a -> 7b8bee092f)

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 d8c84dc13a 362: onsuccess: #2612: 1: Success after binutils/gcc/gdb: 3 commits discards 8e07f5ebf2 361: onsuccess: #2611: 1: Success after binutils/gcc/linux/g [...] discards 8542fbc50d 360: onsuccess: #2610: 1: Success after binutils/gcc/gdb/qem [...] discards 17e76218f7 359: onsuccess: #2609: 1: Success after binutils/gcc/linux/g [...] discards 7f6e122b59 358: onsuccess: #2608: 1: Success after binutils/gcc/glibc/g [...] discards 74565d2159 357: onsuccess: #2607: 1: Success after binutils/gcc/linux/g [...] discards 3b23f9970e 356: onsuccess: #2606: 1: Success after binutils/gcc/linux/g [...] discards f5af229e47 355: onsuccess: #2605: 1: Success after binutils/gcc/linux/g [...] discards 953a8752e6 354: onsuccess: #2604: 1: Success after binutils/gcc/glibc/g [...] discards 9f0d01a048 353: onsuccess: #2603: 1: Success after binutils/gcc/linux/g [...] discards 36ff6210e6 352: onsuccess: #2602: 1: Success after binutils/gcc/linux/g [...] discards 421d04f2e0 351: onsuccess: #2601: 1: Success after binutils/gcc/gdb: 17 [...] discards 1face48555 350: onsuccess: #2600: 1: Success after binutils/gcc/linux/g [...] discards 5ec20c747c 349: onsuccess: #2599: 1: Success after binutils/gcc/linux/g [...] discards 14ea407a47 348: onsuccess: #2598: 1: Success after binutils/gcc/linux/g [...] discards 95df05f01c 347: onsuccess: #2597: 1: Success after binutils/gcc/linux/g [...] discards ddf1283a7a 346: onsuccess: #2596: 1: Success after binutils/gcc/linux/g [...] discards 1aa1e8b768 345: onsuccess: #2595: 1: Success after binutils/gcc/linux/g [...] discards 2f0e5792fa 344: onsuccess: #2594: 1: Success after binutils/gcc/linux/g [...] discards 487dc580f5 343: onsuccess: #2593: 1: Success after binutils/gcc/glibc/g [...] discards fc16299986 342: onsuccess: #2592: 1: Success after binutils/gcc/linux/g [...] discards f7465a4abb 341: onsuccess: #2591: 1: Success after binutils/gcc/linux/g [...] discards 10bace5932 340: onsuccess: #2590: 1: Success after binutils/gcc/gdb/qem [...] discards 45b0907198 339: onsuccess: #2589: 1: Success after binutils/gcc/glibc/g [...] discards a404eac385 338: onsuccess: #2588: 1: Success after binutils/gcc/linux/g [...] discards eb23db6a6d 337: onsuccess: #2587: 1: Success after binutils/gdb: 4 commits discards 961fafd4cf 336: onsuccess: #2586: 1: Success after binutils/gcc/gdb: 22 [...] discards 87ba5016ba 335: onsuccess: #2585: 1: Success after binutils/gcc/linux/g [...] discards 3a04b227a6 334: onsuccess: #2584: 1: Success after gcc/linux: 15 commits discards 342c32aff9 333: onsuccess: #2583: 1: Success after binutils/gcc/linux/g [...] discards b48ccc5880 332: onsuccess: #2582: 1: Success after binutils/gcc/linux/g [...] discards ab0604caec 331: onsuccess: #2581: 1: Success after binutils/gcc/linux/g [...] discards a3ab261af8 330: onsuccess: #2580: 1: Success after basepoints/gcc-13-51 [...] discards 51d9dc7168 329: onsuccess: #2579: 1: Success after binutils/gcc/linux/g [...] discards 1b1a45bcb6 328: onsuccess: #2578: 1: Success after binutils/gcc/glibc/g [...] discards 969feafeb1 327: onsuccess: #2577: 1: Success after binutils/gcc/linux/g [...] discards b5eb653398 326: onsuccess: #2576: 1: Success after binutils/gdb: 6 commits discards 809df0c5f7 325: onsuccess: #2575: 1: Success after binutils/gcc/linux/g [...] discards 04b2d5da76 324: onsuccess: #2574: 1: Success after binutils/gcc/glibc/g [...] discards a7dc6577f4 323: onsuccess: #2573: 1: Success after binutils/gcc/gdb: 18 [...] discards 627430534a 322: onsuccess: #2572: 1: Success after binutils/gcc/gdb: 6 commits discards 3c8cc41bc4 321: onsuccess: #2571: 1: Success after binutils/gcc/gdb: 19 [...] discards bbf1b13c7f 320: onsuccess: #2570: 1: Success after binutils/gcc/linux/g [...] discards 68d9d835a4 319: onsuccess: #2569: 1: Success after binutils/gcc/linux/g [...] discards 7687bc569a 318: onsuccess: #2568: 1: Success after binutils/gdb: 142 commits discards 9363d68c81 317: onsuccess: #2567: 1: Success after binutils/gcc/linux/g [...] discards 51d03d5ead 316: onsuccess: #2566: 1: Success after binutils/gcc/gdb/qem [...] discards 6e8c804457 315: onsuccess: #2565: 1: Success after binutils/gcc/gdb/qem [...] discards 53cadf092a 314: onsuccess: #2564: 1: Success after binutils/gcc/gdb: 5 commits discards f0b08df90d 313: onsuccess: #2563: 1: Success after linux/qemu: 44 commits discards ad21c29d08 312: onsuccess: #2562: 1: Success after binutils/gdb: 2 commits discards ca3306a43b 311: onsuccess: #2561: 1: Success after binutils/gcc/linux/g [...] discards 3cf51c4439 310: onsuccess: #2560: 1: Success after v7.2.0-493-g052e6534 [...] discards 8e946bb334 309: onsuccess: #2559: 1: Success after binutils/gcc/linux/g [...] discards 4e02dacd31 308: onsuccess: #2558: 1: Success after binutils/gcc/linux/g [...] discards df2c019c55 307: onsuccess: #2557: 1: Success after binutils/gcc/gdb/qem [...] discards 8c829b000d 306: onsuccess: #2556: 1: Success after binutils/gcc/gdb: 5 commits discards af707abb9f 305: onsuccess: #2555: 1: Success after binutils/gcc/gdb: 3 commits discards f86cfffd37 304: onsuccess: #2554: 1: Success after binutils/gcc/linux/g [...] discards a7e1b2c250 303: onsuccess: #2553: 1: Success after binutils/gcc/gdb/qem [...] discards f934b63687 302: onsuccess: #2552: 1: Success after binutils/gcc/gdb: 8 commits discards b1246fe3a1 301: onsuccess: #2551: 1: Success after binutils/gcc/linux/g [...] discards 0645f54bcb 300: onsuccess: #2550: 1: Success after binutils/gcc/linux/g [...] discards 7131c037d9 299: onsuccess: #2549: 1: Success after binutils/gcc/gdb/qem [...] discards 4ee9d2cce1 298: onsuccess: #2548: 1: Success after binutils/gdb: 6 commits discards 5aa99f64b3 297: onsuccess: #2547: 1: Success after binutils/gcc/glibc/g [...] discards ff97c96e90 296: onsuccess: #2546: 1: Success after binutils/gcc/gdb: 79 [...] discards 9dca4c9210 295: onsuccess: #2545: 1: Success after linux: 10 commits discards 38c85a879b 294: onsuccess: #2544: 1: Success after glibc-2.36.9000-416- [...] discards 1c5cbd3ad0 293: onsuccess: #2542: 1: Success after gcc: 5 commits discards f1b8bbcd94 292: onsuccess: #2541: 1: Success after binutils: 13 commits discards 5442e7cb44 291: onsuccess: #2539: 1: Success after binutils/gcc/glibc/g [...] discards 961cd10529 290: onsuccess: #2538: 1: Success after binutils/gcc/glibc/g [...] discards 83be1e8160 289: onsuccess: #2537: 1: Success after binutils/gcc/linux/g [...] discards ef9e53d0c8 288: onsuccess: #2536: 1: Success after binutils/gcc/linux/g [...] discards 649885d07a 287: onsuccess: #2535: 1: Success after binutils/gcc/gdb: 15 [...] discards ac2fc52990 286: onsuccess: #2534: 1: Success after binutils/gcc/gdb: 4 commits discards b98136a0c5 285: onsuccess: #2533: 1: Success after gcc/linux: 13 commits discards dee16addd6 284: onsuccess: #2532: 1: Success after binutils/gdb: 10 commits discards 1efa0f74e1 283: onsuccess: #2531: 1: Success after binutils/gdb: 16 commits discards 78b1453683 282: onsuccess: #2530: 1: Success after binutils/gcc/gdb: 3 commits discards 4cf8f7faca 281: onsuccess: #2529: 1: Success after binutils/gcc/linux/g [...] discards c7dad99cf1 280: onsuccess: #2528: 1: Success after binutils/gcc/gdb: 7 commits discards d7101daf3d 279: onsuccess: #2527: 1: Success after basepoints/gcc-13-49 [...] discards c4b5216d19 278: onsuccess: #2526: 1: Success after binutils/gcc/linux/g [...] discards f9932181f2 277: onsuccess: #2525: 1: Success after gcc/linux: 60 commits discards 7d4fe615b6 276: onsuccess: #2524: 1: Success after binutils/gdb: 2 commits discards 1a33864775 275: onsuccess: #2523: 1: Success after basepoints/gcc-13-49 [...] discards 2b534f7b2c 274: onsuccess: #2522: 1: Success after binutils/gcc/gdb: 8 commits discards 1061560c5a 273: onsuccess: #2521: 1: Success after gcc: 2 commits discards 4cb74f7813 272: onsuccess: #2520: 1: Success after basepoints/gcc-13-49 [...] discards d3d391c042 271: onsuccess: #2519: 1: Success after binutils/gcc/gdb: 23 [...] discards 1613402a72 270: onsuccess: #2518: 1: Success after binutils/gcc/gdb: 19 [...] discards 9bfee03ddc 269: onsuccess: #2517: 1: Success after binutils/gcc/gdb: 3 commits discards 4b34231fb4 268: onsuccess: #2516: 1: Success after binutils/gcc/gdb: 3 commits discards 15ed3034c3 267: onsuccess: #2515: 1: Success after binutils/gdb: 4 commits discards 24ae570b0b 266: onsuccess: #2514: 1: Success after binutils/gcc/linux/g [...] discards 3c54bdbd28 265: onsuccess: #2513: 1: Success after binutils/gdb: 4 commits discards 1013d6636d 264: onsuccess: #2512: 1: Success after binutils/gcc/gdb: 21 [...] discards 8b2bb73183 263: onsuccess: #2511: 1: Success after binutils/gdb: 16 commits discards e2373e7ff2 262: onsuccess: #2510: 1: Success after binutils/gcc/gdb: 10 [...] new 169b6eb11a 262: onsuccess: #2510: 1: Success after binutils/gcc/gdb: 10 [...] new a4e42493a2 263: onsuccess: #2511: 1: Success after binutils/gdb: 16 commits new 5207583f9c 264: onsuccess: #2512: 1: Success after binutils/gcc/gdb: 21 [...] new 7e1bb0644a 265: onsuccess: #2513: 1: Success after binutils/gdb: 4 commits new 4b066fdf68 266: onsuccess: #2514: 1: Success after binutils/gcc/linux/g [...] new b9c0845ff0 267: onsuccess: #2515: 1: Success after binutils/gdb: 4 commits new c3efc78fe1 268: onsuccess: #2516: 1: Success after binutils/gcc/gdb: 3 commits new 784e9eccb6 269: onsuccess: #2517: 1: Success after binutils/gcc/gdb: 3 commits new fa2b6aeec9 270: onsuccess: #2518: 1: Success after binutils/gcc/gdb: 19 [...] new cdf95e8dec 271: onsuccess: #2519: 1: Success after binutils/gcc/gdb: 23 [...] new ba3b41c181 272: onsuccess: #2520: 1: Success after basepoints/gcc-13-49 [...] new 9cb624db2e 273: onsuccess: #2521: 1: Success after gcc: 2 commits new 66ec4e10ec 274: onsuccess: #2522: 1: Success after binutils/gcc/gdb: 8 commits new 872b994247 275: onsuccess: #2523: 1: Success after basepoints/gcc-13-49 [...] new 023b9a635f 276: onsuccess: #2524: 1: Success after binutils/gdb: 2 commits new ced3f90276 277: onsuccess: #2525: 1: Success after gcc/linux: 60 commits new 03f9025908 278: onsuccess: #2526: 1: Success after binutils/gcc/linux/g [...] new 97e146111b 279: onsuccess: #2527: 1: Success after basepoints/gcc-13-49 [...] new c7ae9ca655 280: onsuccess: #2528: 1: Success after binutils/gcc/gdb: 7 commits new ce863dd0a3 281: onsuccess: #2529: 1: Success after binutils/gcc/linux/g [...] new ca1c6a1adf 282: onsuccess: #2530: 1: Success after binutils/gcc/gdb: 3 commits new 36ef7a0c0a 283: onsuccess: #2531: 1: Success after binutils/gdb: 16 commits new 18652c1511 284: onsuccess: #2532: 1: Success after binutils/gdb: 10 commits new 0514032a5c 285: onsuccess: #2533: 1: Success after gcc/linux: 13 commits new 467788a522 286: onsuccess: #2534: 1: Success after binutils/gcc/gdb: 4 commits new 85cb9141d6 287: onsuccess: #2535: 1: Success after binutils/gcc/gdb: 15 [...] new 9ea80651b7 288: onsuccess: #2536: 1: Success after binutils/gcc/linux/g [...] new fcd54dd025 289: onsuccess: #2537: 1: Success after binutils/gcc/linux/g [...] new ca981ba8af 290: onsuccess: #2538: 1: Success after binutils/gcc/glibc/g [...] new 333788ea06 291: onsuccess: #2539: 1: Success after binutils/gcc/glibc/g [...] new 5f1b5a2167 292: onsuccess: #2541: 1: Success after binutils: 13 commits new 7c276fe7bb 293: onsuccess: #2542: 1: Success after gcc: 5 commits new 5b228b8853 294: onsuccess: #2544: 1: Success after glibc-2.36.9000-416- [...] new 2ff008b72f 295: onsuccess: #2545: 1: Success after linux: 10 commits new 59ab3618be 296: onsuccess: #2546: 1: Success after binutils/gcc/gdb: 79 [...] new 9d14acbe85 297: onsuccess: #2547: 1: Success after binutils/gcc/glibc/g [...] new d13bf9fa25 298: onsuccess: #2548: 1: Success after binutils/gdb: 6 commits new ade54481b4 299: onsuccess: #2549: 1: Success after binutils/gcc/gdb/qem [...] new c23d770a39 300: onsuccess: #2550: 1: Success after binutils/gcc/linux/g [...] new 0d3b0169ce 301: onsuccess: #2551: 1: Success after binutils/gcc/linux/g [...] new 834d9daea5 302: onsuccess: #2552: 1: Success after binutils/gcc/gdb: 8 commits new 84ba5d8fab 303: onsuccess: #2553: 1: Success after binutils/gcc/gdb/qem [...] new 3480978fb7 304: onsuccess: #2554: 1: Success after binutils/gcc/linux/g [...] new acd75fa031 305: onsuccess: #2555: 1: Success after binutils/gcc/gdb: 3 commits new 03c7c333f6 306: onsuccess: #2556: 1: Success after binutils/gcc/gdb: 5 commits new 9a0e84bfbc 307: onsuccess: #2557: 1: Success after binutils/gcc/gdb/qem [...] new ec54e0c861 308: onsuccess: #2558: 1: Success after binutils/gcc/linux/g [...] new 927354c695 309: onsuccess: #2559: 1: Success after binutils/gcc/linux/g [...] new dd5c22d59e 310: onsuccess: #2560: 1: Success after v7.2.0-493-g052e6534 [...] new b4911689e2 311: onsuccess: #2561: 1: Success after binutils/gcc/linux/g [...] new 5ad9e23ad5 312: onsuccess: #2562: 1: Success after binutils/gdb: 2 commits new 939c76b7d4 313: onsuccess: #2563: 1: Success after linux/qemu: 44 commits new d3e2b08eec 314: onsuccess: #2564: 1: Success after binutils/gcc/gdb: 5 commits new fe8cc35064 315: onsuccess: #2565: 1: Success after binutils/gcc/gdb/qem [...] new f57c7e21d4 316: onsuccess: #2566: 1: Success after binutils/gcc/gdb/qem [...] new 8fb0325a76 317: onsuccess: #2567: 1: Success after binutils/gcc/linux/g [...] new b8d403ef8f 318: onsuccess: #2568: 1: Success after binutils/gdb: 142 commits new d1f2890588 319: onsuccess: #2569: 1: Success after binutils/gcc/linux/g [...] new d79540450c 320: onsuccess: #2570: 1: Success after binutils/gcc/linux/g [...] new f00278af1d 321: onsuccess: #2571: 1: Success after binutils/gcc/gdb: 19 [...] new 77c84aa8af 322: onsuccess: #2572: 1: Success after binutils/gcc/gdb: 6 commits new ac8e865288 323: onsuccess: #2573: 1: Success after binutils/gcc/gdb: 18 [...] new cb9d591567 324: onsuccess: #2574: 1: Success after binutils/gcc/glibc/g [...] new 3202c0b2b2 325: onsuccess: #2575: 1: Success after binutils/gcc/linux/g [...] new 6e977cdd1c 326: onsuccess: #2576: 1: Success after binutils/gdb: 6 commits new b283654e9f 327: onsuccess: #2577: 1: Success after binutils/gcc/linux/g [...] new f910f7ae83 328: onsuccess: #2578: 1: Success after binutils/gcc/glibc/g [...] new ab7fc0dc7e 329: onsuccess: #2579: 1: Success after binutils/gcc/linux/g [...] new 08448a815b 330: onsuccess: #2580: 1: Success after basepoints/gcc-13-51 [...] new 7d6f13d611 331: onsuccess: #2581: 1: Success after binutils/gcc/linux/g [...] new faa9599d34 332: onsuccess: #2582: 1: Success after binutils/gcc/linux/g [...] new 25ea36a06d 333: onsuccess: #2583: 1: Success after binutils/gcc/linux/g [...] new dfa395ea16 334: onsuccess: #2584: 1: Success after gcc/linux: 15 commits new 46d9a2a17a 335: onsuccess: #2585: 1: Success after binutils/gcc/linux/g [...] new d2fc588496 336: onsuccess: #2586: 1: Success after binutils/gcc/gdb: 22 [...] new 9b32322456 337: onsuccess: #2587: 1: Success after binutils/gdb: 4 commits new 04af7a2a7f 338: onsuccess: #2588: 1: Success after binutils/gcc/linux/g [...] new 357aba965c 339: onsuccess: #2589: 1: Success after binutils/gcc/glibc/g [...] new 95c81ab813 340: onsuccess: #2590: 1: Success after binutils/gcc/gdb/qem [...] new d45df33ac5 341: onsuccess: #2591: 1: Success after binutils/gcc/linux/g [...] new 4ef32c5a93 342: onsuccess: #2592: 1: Success after binutils/gcc/linux/g [...] new 1be05ba821 343: onsuccess: #2593: 1: Success after binutils/gcc/glibc/g [...] new 1dde03cd59 344: onsuccess: #2594: 1: Success after binutils/gcc/linux/g [...] new 916f95a94c 345: onsuccess: #2595: 1: Success after binutils/gcc/linux/g [...] new d4bfdc3b47 346: onsuccess: #2596: 1: Success after binutils/gcc/linux/g [...] new 587eb3f889 347: onsuccess: #2597: 1: Success after binutils/gcc/linux/g [...] new c1c612368b 348: onsuccess: #2598: 1: Success after binutils/gcc/linux/g [...] new f495d9eb0a 349: onsuccess: #2599: 1: Success after binutils/gcc/linux/g [...] new b7a9709216 350: onsuccess: #2600: 1: Success after binutils/gcc/linux/g [...] new d2fcdb66b7 351: onsuccess: #2601: 1: Success after binutils/gcc/gdb: 17 [...] new 86776634fb 352: onsuccess: #2602: 1: Success after binutils/gcc/linux/g [...] new 8b526d0477 353: onsuccess: #2603: 1: Success after binutils/gcc/linux/g [...] new 026bb6f798 354: onsuccess: #2604: 1: Success after binutils/gcc/glibc/g [...] new 4a2b902e27 355: onsuccess: #2605: 1: Success after binutils/gcc/linux/g [...] new af2436620e 356: onsuccess: #2606: 1: Success after binutils/gcc/linux/g [...] new 5a603c6cd6 357: onsuccess: #2607: 1: Success after binutils/gcc/linux/g [...] new ef7bbea610 358: onsuccess: #2608: 1: Success after binutils/gcc/glibc/g [...] new f9f137bc4f 359: onsuccess: #2609: 1: Success after binutils/gcc/linux/g [...] new a950380b2c 360: onsuccess: #2610: 1: Success after binutils/gcc/gdb/qem [...] new c99f413348 361: onsuccess: #2611: 1: Success after binutils/gcc/linux/g [...] new 710e6f30fe 362: onsuccess: #2612: 1: Success after binutils/gcc/gdb: 3 commits new 7b8bee092f 363: onsuccess: #2613: 1: Success after binutils/gcc/gdb/qem [...] 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 (d8c84dc13a) \ 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 1772 -> 1752 bytes 02-prepare_abe/console.log.xz | Bin 2756 -> 2764 bytes 03-build_abe-binutils/console.log.xz | Bin 31032 -> 31532 bytes 04-build_abe-stage1/console.log.xz | Bin 73028 -> 73368 bytes 06-build_abe-linux/console.log.xz | Bin 8864 -> 8888 bytes 07-build_abe-glibc/console.log.xz | Bin 244692 -> 244340 bytes 08-build_abe-stage2/console.log.xz | Bin 204076 -> 204576 bytes 09-build_abe-gdb/console.log.xz | Bin 38464 -> 38844 bytes 10-build_abe-qemu/console.log.xz | Bin 31960 -> 32020 bytes 11-build_abe-dejagnu/console.log.xz | Bin 3884 -> 3892 bytes 12-build_abe-check_gcc/console.log.xz | Bin 2656 -> 2996 bytes 13-check_regression/console.log.xz | Bin 5784 -> 6076 bytes 13-check_regression/extra-bisect-params | 1 - 13-check_regression/fails.sum | 10 - 13-check_regression/mail-body.txt | 57 +- 13-check_regression/results.compare | 48 +- 13-check_regression/results.compare2 | 53 +- 13-check_regression/results.regressions | 44 - 14-update_baseline/console.log | 48 +- dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- git/gdb_rev | 2 +- git/qemu_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 59 +- mail/mail-subject.txt | 2 +- manifest.sh | 38 +- results | 44 - sumfiles/g++.log.xz | Bin 3399592 -> 3385396 bytes sumfiles/g++.sum | 16 +- sumfiles/gcc.log.xz | Bin 3023404 -> 3012096 bytes sumfiles/gcc.sum | 4920 +++++++++++++++---------------- sumfiles/gfortran.log.xz | Bin 1040948 -> 1041316 bytes sumfiles/gfortran.sum | 2 +- sumfiles/libatomic.log.xz | Bin 2288 -> 2288 bytes sumfiles/libatomic.sum | 2 +- sumfiles/libgomp.log.xz | Bin 215216 -> 215112 bytes sumfiles/libgomp.sum | 2 +- sumfiles/libitm.log.xz | Bin 2652 -> 2656 bytes sumfiles/libitm.sum | 2 +- sumfiles/libstdc++.log.xz | Bin 438148 -> 423800 bytes sumfiles/libstdc++.sum | 55 +- 43 files changed, 2595 insertions(+), 2820 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 (319f7802ca -> 29a7128bcc)

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 319f7802ca 389: onsuccess: #2124: 7: Success after binutils/gcc/gdb: 5 commits discards 9c667ebc04 388: onsuccess: #2123: 7: Success after binutils/gcc/gdb: 3 commits discards a5a7dba714 387: onsuccess: #2122: 7: Success after gcc/linux/qemu: 117 commits discards 545f03d3b0 386: onsuccess: #2121: 7: Success after binutils/gcc/glibc/g [...] discards 737b90daa6 385: onsuccess: #2120: 7: Success after binutils/gcc/gdb/qem [...] discards cd55d24917 384: onsuccess: #2119: 7: Success after binutils/gcc/linux/g [...] discards fd7c761cdd 383: onsuccess: #2118: 7: Success after binutils/gcc/glibc/g [...] discards aa0d61c389 382: onsuccess: #2117: 7: Success after binutils/gcc/linux/g [...] discards 2202cfe3d0 381: onsuccess: #2116: 7: Success after binutils/gcc/linux/g [...] discards 7d7cae2860 380: onsuccess: #2115: 7: Success after binutils/gcc/linux/g [...] discards a4a6792be6 379: onsuccess: #2114: 7: Success after binutils/gcc/linux/g [...] discards f879e02bc6 378: onsuccess: #2113: 7: Success after binutils/gcc/linux/g [...] discards 930cd1f599 377: onsuccess: #2112: 7: Success after binutils/gcc/gdb: 16 [...] discards 0430f1d02a 376: onsuccess: #2111: 7: Success after binutils/gcc/linux/g [...] discards 905c0f44f8 375: onsuccess: #2110: 7: Success after binutils/gcc/linux/g [...] discards 9c98ecd36e 374: onsuccess: #2109: 7: Success after binutils/gcc/linux/g [...] discards 9669b6cb8a 373: onsuccess: #2107: 7: Success after binutils/gcc/linux/g [...] discards 7a91722804 372: onsuccess: #2106: 7: Success after binutils/gcc/linux/g [...] discards 2010a2a42a 371: onsuccess: #2105: 7: Success after binutils/gcc/gdb/qem [...] discards 6a995abb20 370: onsuccess: #2104: 7: Success after binutils/gcc/linux/g [...] discards 74807f0414 369: onsuccess: #2103: 7: Success after binutils/gcc/linux/g [...] discards 7c43243897 368: onsuccess: #2102: 7: Success after binutils/gcc/linux/g [...] discards da06509971 367: onsuccess: #2101: 7: Success after binutils/gcc/linux/g [...] discards d0e5f1ad2e 366: onsuccess: #2100: 7: Success after binutils/gcc/glibc/g [...] discards ee61c3020e 365: onsuccess: #2099: 7: Success after gcc/linux: 21 commits discards a6fd235001 364: onsuccess: #2098: 7: Success after binutils/gdb: 4 commits discards 02249e72e5 363: onsuccess: #2097: 7: Success after binutils/gcc/gdb: 25 [...] discards f4fc4bf677 362: onsuccess: #2096: 7: Success after binutils/gcc/linux/g [...] discards 1aa6edb499 361: onsuccess: #2095: 7: Success after gcc/linux: 15 commits discards de1dd2b913 360: onsuccess: #2094: 7: Success after binutils/gcc/linux/g [...] discards 64d0cb8be3 359: onsuccess: #2093: 7: Success after binutils/gcc/linux/g [...] discards 1399f3a7a6 358: onsuccess: #2092: 7: Success after binutils/gcc/gdb: 10 [...] discards deca30934c 357: onsuccess: #2091: 7: Success after binutils/gcc/linux/g [...] discards 9998d6224f 356: onsuccess: #2090: 7: Success after binutils/gcc/glibc/g [...] discards c2c0e79498 355: onsuccess: #2089: 7: Success after binutils/gcc/linux/g [...] discards 3e05249664 354: onsuccess: #2088: 7: Success after binutils/gcc/gdb: 7 commits discards eaf602e78b 353: onsuccess: #2087: 7: Success after binutils/gcc/linux/g [...] discards 4af13de3a3 352: onsuccess: #2086: 7: Success after binutils/gcc/gdb: 9 commits discards 25a87a8299 351: onsuccess: #2085: 7: Success after binutils/gcc/gdb: 19 [...] discards d754db404b 350: onsuccess: #2084: 7: Success after binutils/gcc/gdb: 4 commits discards e82ea27d33 349: onsuccess: #2083: 7: Success after binutils/gcc/linux/g [...] discards de9b0ab69b 348: onsuccess: #2082: 7: Success after binutils/gcc/glibc/g [...] discards 6b551f2362 347: onsuccess: #2081: 7: Success after binutils/gcc/linux/g [...] discards 56cdce485f 346: onsuccess: #2080: 7: Success after binutils/gdb: 142 commits discards 6e25617d7a 345: onsuccess: #2079: 7: Success after binutils/gcc/linux/g [...] discards fddb365836 344: onsuccess: #2078: 7: Success after binutils/gcc/gdb: 6 commits discards 45e90d3983 343: onsuccess: #2077: 7: Success after binutils/gcc/gdb/qem [...] discards 093d046ab0 342: onsuccess: #2076: 7: Success after binutils/gcc/gdb: 5 commits discards 1620ce393a 341: onsuccess: #2075: 7: Success after linux/qemu: 44 commits discards ef1c354708 340: onsuccess: #2074: 7: Success after binutils/gcc/gdb: 5 commits discards 2698170484 339: onsuccess: #2073: 7: Success after gcc/linux/qemu: 38 commits discards c2396e641c 338: onsuccess: #2072: 7: Success after v7.2.0-493-g052e6534 [...] discards df7b71c2e1 337: onsuccess: #2071: 7: Success after basepoints/gcc-13-50 [...] discards c9c84bed13 336: onsuccess: #2070: 7: Success after binutils/gcc/linux/g [...] discards 2797d1c58d 335: onsuccess: #2069: 7: Success after binutils/gcc/linux/g [...] discards f3f17bc1b3 334: onsuccess: #2068: 7: Success after binutils/gcc/gdb/qem [...] discards 2bc850388a 333: onsuccess: #2067: 7: Success after basepoints/gcc-13-50 [...] discards e2b7a54f6c 332: onsuccess: #2066: 7: Success after binutils/gcc/linux/g [...] discards 5fc70d12e8 331: onsuccess: #2065: 7: Success after binutils/gcc/linux/g [...] discards 24b10c3c64 330: onsuccess: #2064: 7: Success after binutils/gcc/gdb: 8 commits discards c4ffb17057 329: onsuccess: #2063: 7: Success after binutils/gcc/gdb: 11 [...] discards 3694526124 328: onsuccess: #2062: 7: Success after binutils/gcc/linux/g [...] discards f629eec82b 327: onsuccess: #2061: 7: Success after binutils/gcc/linux/g [...] discards 8d466e15f4 326: onsuccess: #2060: 7: Success after binutils/gcc/gdb: 28 [...] discards 710d3e75cc 325: onsuccess: #2059: 7: Success after binutils/gcc/gdb: 9 commits discards b0434d5c4c 324: onsuccess: #2058: 7: Success after binutils/gcc/linux/g [...] discards ddf8d4eccd 323: onsuccess: #2057: 5: Success after gdb-13-branchpoint-2 [...] discards 774b35d326 322: force: #2056: 5: Failure after gdb-13-branchpoint-245-g [...] discards bc93f301e0 321: force: #2055: 7: Success after gdb: 2 commits discards 9fe1a8b989 320: onsuccess: #2050: 7: Success after gcc: 4 commits discards 7a540ffe81 319: onsuccess: #2049: 7: Success after binutils: 4 commits discards a95fd4870d 318: onsuccess: #2047: 7: Success after binutils/gcc/glibc/g [...] discards 8f58cfaec1 317: onsuccess: #2046: 7: Success after binutils/gdb: 6 commits discards d7202811cd 316: onsuccess: #2045: 7: Success after binutils/gcc/linux/g [...] discards 4c5543020c 315: onsuccess: #2044: 7: Success after binutils/gcc/linux/g [...] discards a2418e3a5e 314: onsuccess: #2043: 7: Success after binutils/gcc/gdb: 15 [...] discards bf1cfb8484 313: onsuccess: #2042: 7: Success after binutils/gcc/gdb: 4 commits discards d254c1588c 312: onsuccess: #2041: 7: Success after gcc/linux: 13 commits discards b44f591998 311: onsuccess: #2040: 7: Success after binutils/gdb: 20 commits discards e6505812c0 310: onsuccess: #2039: 7: Success after binutils/gdb: 6 commits discards 45759d8f19 309: onsuccess: #2038: 7: Success after binutils/gcc/gdb: 3 commits discards 125714db07 308: onsuccess: #2037: 7: Success after binutils/gcc/linux/g [...] discards 6e749726bf 307: onsuccess: #2036: 7: Success after binutils/gcc/gdb: 7 commits discards f2e0ed27c6 306: onsuccess: #2035: 7: Success after basepoints/gcc-13-49 [...] discards fbb0ca9365 305: onsuccess: #2034: 7: Success after binutils/gcc/linux/g [...] discards a49a9fcc06 304: onsuccess: #2033: 7: Success after gcc/linux: 60 commits discards d809b028dc 303: onsuccess: #2032: 7: Success after binutils/gdb: 2 commits discards 71fdef83e7 302: onsuccess: #2031: 7: Success after binutils/gcc/gdb: 3 commits discards 8e583f4018 301: onsuccess: #2030: 7: Success after binutils/gcc/gdb: 4 commits discards 1c1928feeb 300: onsuccess: #2029: 7: Success after binutils/gcc/gdb: 4 commits discards 43bbad3170 299: onsuccess: #2028: 7: Success after binutils/gcc/gdb: 6 commits discards 54dc3f4b9a 298: onsuccess: #2027: 7: Success after binutils/gcc/gdb: 18 [...] discards ac6559b02d 297: onsuccess: #2026: 7: Success after binutils/gcc/gdb: 19 [...] discards a56da3ad03 296: onsuccess: #2025: 7: Success after binutils/gcc/gdb: 5 commits discards b6eca1130d 295: onsuccess: #2024: 7: Success after basepoints/gcc-13-48 [...] discards f625a6b5c2 294: onsuccess: #2023: 7: Success after binutils/gdb: 4 commits discards 1b24137a7d 293: onsuccess: #2022: 7: Success after gcc: 2 commits discards c684c8f42e 292: onsuccess: #2021: 7: Success after binutils/linux/gdb: [...] discards 6d59c03abf 291: onsuccess: #2020: 7: Success after binutils/gcc/gdb: 3 commits discards 44c09d5aca 290: onsuccess: #2019: 7: Success after binutils/gdb: 20 commits discards 6adab771df 289: onsuccess: #2018: 7: Success after binutils/gcc/gdb: 17 [...] new 88e12ce5ec 289: onsuccess: #2018: 7: Success after binutils/gcc/gdb: 17 [...] new 344c7b843b 290: onsuccess: #2019: 7: Success after binutils/gdb: 20 commits new 656142e052 291: onsuccess: #2020: 7: Success after binutils/gcc/gdb: 3 commits new cf27aa30e2 292: onsuccess: #2021: 7: Success after binutils/linux/gdb: [...] new c66478a42f 293: onsuccess: #2022: 7: Success after gcc: 2 commits new 6c160992d8 294: onsuccess: #2023: 7: Success after binutils/gdb: 4 commits new a8d4dfa764 295: onsuccess: #2024: 7: Success after basepoints/gcc-13-48 [...] new 5b77dfc314 296: onsuccess: #2025: 7: Success after binutils/gcc/gdb: 5 commits new c007eba6c9 297: onsuccess: #2026: 7: Success after binutils/gcc/gdb: 19 [...] new ed8d99377b 298: onsuccess: #2027: 7: Success after binutils/gcc/gdb: 18 [...] new 5ab6eda632 299: onsuccess: #2028: 7: Success after binutils/gcc/gdb: 6 commits new ca261d275e 300: onsuccess: #2029: 7: Success after binutils/gcc/gdb: 4 commits new 0355098844 301: onsuccess: #2030: 7: Success after binutils/gcc/gdb: 4 commits new 53c3b65455 302: onsuccess: #2031: 7: Success after binutils/gcc/gdb: 3 commits new 4c4e9e08c0 303: onsuccess: #2032: 7: Success after binutils/gdb: 2 commits new 57f89338ce 304: onsuccess: #2033: 7: Success after gcc/linux: 60 commits new 9df98d09b7 305: onsuccess: #2034: 7: Success after binutils/gcc/linux/g [...] new c90112d1fb 306: onsuccess: #2035: 7: Success after basepoints/gcc-13-49 [...] new 4f99ace1b4 307: onsuccess: #2036: 7: Success after binutils/gcc/gdb: 7 commits new 7363901c57 308: onsuccess: #2037: 7: Success after binutils/gcc/linux/g [...] new 042974e5a1 309: onsuccess: #2038: 7: Success after binutils/gcc/gdb: 3 commits new 79a4c404a2 310: onsuccess: #2039: 7: Success after binutils/gdb: 6 commits new 009e325e91 311: onsuccess: #2040: 7: Success after binutils/gdb: 20 commits new a29ffb5435 312: onsuccess: #2041: 7: Success after gcc/linux: 13 commits new fb1f004b67 313: onsuccess: #2042: 7: Success after binutils/gcc/gdb: 4 commits new 84bfd5556b 314: onsuccess: #2043: 7: Success after binutils/gcc/gdb: 15 [...] new 478e988a37 315: onsuccess: #2044: 7: Success after binutils/gcc/linux/g [...] new f82a930984 316: onsuccess: #2045: 7: Success after binutils/gcc/linux/g [...] new ec994070a5 317: onsuccess: #2046: 7: Success after binutils/gdb: 6 commits new 260fc7856c 318: onsuccess: #2047: 7: Success after binutils/gcc/glibc/g [...] new 2a539428e0 319: onsuccess: #2049: 7: Success after binutils: 4 commits new 4212c41492 320: onsuccess: #2050: 7: Success after gcc: 4 commits new b7578b2380 321: force: #2055: 7: Success after gdb: 2 commits new 56eb0eb3a7 322: force: #2056: 5: Failure after gdb-13-branchpoint-245-g [...] new 5fd5c08c47 323: onsuccess: #2057: 5: Success after gdb-13-branchpoint-2 [...] new c2a9c4b1d8 324: onsuccess: #2058: 7: Success after binutils/gcc/linux/g [...] new 7cb8e7932a 325: onsuccess: #2059: 7: Success after binutils/gcc/gdb: 9 commits new 43e2c85bdd 326: onsuccess: #2060: 7: Success after binutils/gcc/gdb: 28 [...] new 6a71fb5df2 327: onsuccess: #2061: 7: Success after binutils/gcc/linux/g [...] new 38ddc532d1 328: onsuccess: #2062: 7: Success after binutils/gcc/linux/g [...] new 75f5e57cde 329: onsuccess: #2063: 7: Success after binutils/gcc/gdb: 11 [...] new bb28bace1c 330: onsuccess: #2064: 7: Success after binutils/gcc/gdb: 8 commits new 1c79acc1b2 331: onsuccess: #2065: 7: Success after binutils/gcc/linux/g [...] new 6504d7f1ab 332: onsuccess: #2066: 7: Success after binutils/gcc/linux/g [...] new 4d6a918144 333: onsuccess: #2067: 7: Success after basepoints/gcc-13-50 [...] new dcc063801a 334: onsuccess: #2068: 7: Success after binutils/gcc/gdb/qem [...] new f988b754fe 335: onsuccess: #2069: 7: Success after binutils/gcc/linux/g [...] new a0cb4d9925 336: onsuccess: #2070: 7: Success after binutils/gcc/linux/g [...] new 48b4286e46 337: onsuccess: #2071: 7: Success after basepoints/gcc-13-50 [...] new 8f74732ce9 338: onsuccess: #2072: 7: Success after v7.2.0-493-g052e6534 [...] new 91856e264a 339: onsuccess: #2073: 7: Success after gcc/linux/qemu: 38 commits new 4cd444bed5 340: onsuccess: #2074: 7: Success after binutils/gcc/gdb: 5 commits new 2410f03791 341: onsuccess: #2075: 7: Success after linux/qemu: 44 commits new 3d028ec879 342: onsuccess: #2076: 7: Success after binutils/gcc/gdb: 5 commits new a36e290737 343: onsuccess: #2077: 7: Success after binutils/gcc/gdb/qem [...] new 5b68869d16 344: onsuccess: #2078: 7: Success after binutils/gcc/gdb: 6 commits new a40d6ec698 345: onsuccess: #2079: 7: Success after binutils/gcc/linux/g [...] new b16f070152 346: onsuccess: #2080: 7: Success after binutils/gdb: 142 commits new 3f8313ff1e 347: onsuccess: #2081: 7: Success after binutils/gcc/linux/g [...] new b15a1b578a 348: onsuccess: #2082: 7: Success after binutils/gcc/glibc/g [...] new 7903ae702a 349: onsuccess: #2083: 7: Success after binutils/gcc/linux/g [...] new f48fe881c9 350: onsuccess: #2084: 7: Success after binutils/gcc/gdb: 4 commits new 01c31b7c35 351: onsuccess: #2085: 7: Success after binutils/gcc/gdb: 19 [...] new fecbdd0d51 352: onsuccess: #2086: 7: Success after binutils/gcc/gdb: 9 commits new 255314a7c4 353: onsuccess: #2087: 7: Success after binutils/gcc/linux/g [...] new d5246e7d8c 354: onsuccess: #2088: 7: Success after binutils/gcc/gdb: 7 commits new 1dab876719 355: onsuccess: #2089: 7: Success after binutils/gcc/linux/g [...] new c1b85f24d3 356: onsuccess: #2090: 7: Success after binutils/gcc/glibc/g [...] new c8d57dff03 357: onsuccess: #2091: 7: Success after binutils/gcc/linux/g [...] new 1120eece4f 358: onsuccess: #2092: 7: Success after binutils/gcc/gdb: 10 [...] new f53b7c1aaf 359: onsuccess: #2093: 7: Success after binutils/gcc/linux/g [...] new 20dc106622 360: onsuccess: #2094: 7: Success after binutils/gcc/linux/g [...] new 36a52b24cd 361: onsuccess: #2095: 7: Success after gcc/linux: 15 commits new 0d5c519ac7 362: onsuccess: #2096: 7: Success after binutils/gcc/linux/g [...] new 281c7c2b9d 363: onsuccess: #2097: 7: Success after binutils/gcc/gdb: 25 [...] new e12c0668ac 364: onsuccess: #2098: 7: Success after binutils/gdb: 4 commits new 748e942848 365: onsuccess: #2099: 7: Success after gcc/linux: 21 commits new e2e238af89 366: onsuccess: #2100: 7: Success after binutils/gcc/glibc/g [...] new ff4eae4111 367: onsuccess: #2101: 7: Success after binutils/gcc/linux/g [...] new 445eb39b83 368: onsuccess: #2102: 7: Success after binutils/gcc/linux/g [...] new 3213f5e56d 369: onsuccess: #2103: 7: Success after binutils/gcc/linux/g [...] new 10c9fd0f26 370: onsuccess: #2104: 7: Success after binutils/gcc/linux/g [...] new 4b0589beee 371: onsuccess: #2105: 7: Success after binutils/gcc/gdb/qem [...] new e26eb26929 372: onsuccess: #2106: 7: Success after binutils/gcc/linux/g [...] new cda8dc7776 373: onsuccess: #2107: 7: Success after binutils/gcc/linux/g [...] new f0e7ce33f3 374: onsuccess: #2109: 7: Success after binutils/gcc/linux/g [...] new 243aa307bc 375: onsuccess: #2110: 7: Success after binutils/gcc/linux/g [...] new b69cbf71f0 376: onsuccess: #2111: 7: Success after binutils/gcc/linux/g [...] new f6cf715754 377: onsuccess: #2112: 7: Success after binutils/gcc/gdb: 16 [...] new fb88635a17 378: onsuccess: #2113: 7: Success after binutils/gcc/linux/g [...] new d73f71dae7 379: onsuccess: #2114: 7: Success after binutils/gcc/linux/g [...] new c2f8016c89 380: onsuccess: #2115: 7: Success after binutils/gcc/linux/g [...] new 55722548ae 381: onsuccess: #2116: 7: Success after binutils/gcc/linux/g [...] new d362fb8a6b 382: onsuccess: #2117: 7: Success after binutils/gcc/linux/g [...] new 6c0c70b8cf 383: onsuccess: #2118: 7: Success after binutils/gcc/glibc/g [...] new ccc5b48feb 384: onsuccess: #2119: 7: Success after binutils/gcc/linux/g [...] new 88b956f783 385: onsuccess: #2120: 7: Success after binutils/gcc/gdb/qem [...] new 75a810b7b9 386: onsuccess: #2121: 7: Success after binutils/gcc/glibc/g [...] new 354728bb21 387: onsuccess: #2122: 7: Success after gcc/linux/qemu: 117 commits new 6fa496c542 388: onsuccess: #2123: 7: Success after binutils/gcc/gdb: 3 commits new e3ce0a7103 389: onsuccess: #2124: 7: Success after binutils/gcc/gdb: 5 commits new 29a7128bcc 390: onsuccess: #2125: 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 (319f7802ca) \ 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 1768 -> 1732 bytes 02-prepare_abe/console.log.xz | Bin 2772 -> 2764 bytes 04-build_abe-binutils/console.log.xz | Bin 31472 -> 31160 bytes 05-build_abe-stage1/console.log.xz | Bin 91704 -> 91788 bytes 07-build_abe-linux/console.log.xz | Bin 8880 -> 8576 bytes 08-build_abe-glibc/console.log.xz | Bin 235748 -> 235724 bytes 09-build_abe-stage2/console.log.xz | Bin 229780 -> 228632 bytes 10-build_abe-gdb/console.log.xz | Bin 38788 -> 38368 bytes 11-build_abe-qemu/console.log.xz | Bin 31720 -> 31888 bytes 12-check_regression/console.log.xz | Bin 3456 -> 4268 bytes 13-update_baseline/console.log | 40 +++++++++++++++---------------- dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- git/gdb_rev | 2 +- git/linux_rev | 2 +- 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, 51 insertions(+), 51 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_gnu_cross_check_gcc/master-arm updated (fdddd83b18 -> 6c842f4f59)

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 fdddd83b18 377: onsuccess: #2198: 1: Success after binutils/gcc/gdb: 3 commits discards 341c752346 376: onsuccess: #2197: 1: Success after binutils/gcc/linux/g [...] discards 6465eeb40f 375: onsuccess: #2195: 1: Success after binutils/gcc/gdb/qem [...] discards bf11229c83 374: onsuccess: #2194: 1: Success after binutils/gcc/linux/g [...] discards a3268e3022 373: onsuccess: #2193: 1: Success after binutils/gcc/glibc/g [...] discards 45af7d9c93 372: onsuccess: #2192: 1: Success after binutils/gcc/linux/g [...] discards f0d5abd93d 371: onsuccess: #2191: 1: Success after binutils/gcc/gdb: 10 [...] discards aee68c2909 370: onsuccess: #2190: 1: Success after binutils/gcc/linux/g [...] discards 38192afb8c 369: onsuccess: #2189: 1: Success after binutils/gcc/linux/g [...] discards 9bddddfed4 368: onsuccess: #2188: 1: Success after binutils/gcc/linux/g [...] discards 1fb49a3338 367: onsuccess: #2187: 1: Success after binutils/gcc/gdb: 14 [...] discards d7757529b3 366: onsuccess: #2186: 1: Success after binutils/gcc/linux/g [...] discards 1fe5c14875 365: onsuccess: #2185: 1: Success after binutils/gcc/linux/g [...] discards bc34a3d587 364: onsuccess: #2184: 1: Success after binutils/gcc/linux/g [...] discards ceb710b284 363: onsuccess: #2183: 1: Success after binutils/gcc/linux/g [...] discards d3e32e9e9d 362: onsuccess: #2182: 1: Success after binutils/gcc/linux/g [...] discards 07b142f727 361: onsuccess: #2181: 1: Success after binutils/gcc/linux/g [...] discards 610198ffd6 360: onsuccess: #2180: 1: Success after binutils/gcc/linux/g [...] discards 864a30f996 359: onsuccess: #2179: 1: Success after binutils/gcc/glibc/g [...] discards 0e2eb65e15 358: onsuccess: #2178: 1: Success after binutils/gcc/linux/g [...] discards 16873edb3d 357: onsuccess: #2177: 1: Success after binutils/gcc/linux/g [...] discards eaea25eb08 356: onsuccess: #2176: 1: Success after binutils/gcc/linux/g [...] discards 0a52c1fe29 355: onsuccess: #2175: 1: Success after binutils/gcc/linux/g [...] discards 08824f263a 354: onsuccess: #2174: 1: Success after binutils/gcc/linux/g [...] discards 28ad8dc67a 353: onsuccess: #2173: 1: Success after binutils/gcc/gdb: 27 [...] discards 70ed1dc412 352: onsuccess: #2172: 1: Success after binutils/gcc/linux/g [...] discards 17accf1c67 351: onsuccess: #2171: 1: Success after gcc/linux: 15 commits discards 663d36c02f 350: onsuccess: #2170: 1: Success after binutils/gcc/linux/g [...] discards 668a7f572f 349: onsuccess: #2169: 1: Success after binutils/gcc/linux/g [...] discards bd675a7617 348: onsuccess: #2168: 1: Success after binutils/gcc/gdb: 9 commits discards c38061eb83 347: onsuccess: #2167: 1: Success after basepoints/gcc-13-51 [...] discards 2081dd6f3f 346: onsuccess: #2166: 1: Success after binutils/gcc/linux/g [...] discards 1bb151a3b8 345: onsuccess: #2165: 1: Success after binutils/gcc/glibc/g [...] discards dc0a2af762 344: onsuccess: #2164: 1: Success after gcc/linux/glibc: 37 commits discards 3ff1f9612a 343: onsuccess: #2163: 1: Success after binutils/gcc/gdb: 7 commits discards 8b6a027c87 342: onsuccess: #2162: 1: Success after binutils/gcc/linux/g [...] discards 23513fe457 341: onsuccess: #2161: 1: Success after binutils/gcc/gdb: 11 [...] discards 43a94fd0be 340: onsuccess: #2160: 1: Success after binutils/gcc/gdb: 15 [...] discards dbf0b00930 339: onsuccess: #2159: 1: Success after binutils/gcc/gdb: 4 commits discards f4d16ac7f1 338: onsuccess: #2158: 1: Success after binutils/gcc/linux/g [...] discards cc9244b668 337: onsuccess: #2157: 1: Success after binutils/gcc/glibc/g [...] discards b22c0934c8 336: onsuccess: #2156: 1: Success after binutils/gcc/linux/g [...] discards f5e03569e3 335: onsuccess: #2155: 1: Success after binutils/gdb: 146 commits discards c9adac6c8e 334: onsuccess: #2154: 1: Success after binutils/gcc/linux/g [...] discards 14f0c62547 333: onsuccess: #2153: 1: Success after binutils/gcc/gdb/qem [...] discards fbaca7098b 332: onsuccess: #2152: 1: Success after binutils/gcc/gdb/qem [...] discards 45e0bb8537 331: onsuccess: #2151: 1: Success after binutils/gcc/linux/g [...] discards bab047de63 330: onsuccess: #2150: 1: Success after linux/qemu: 36 commits discards 391ff87ca8 329: onsuccess: #2149: 1: Success after binutils/gcc/gdb/qem [...] discards 62e65779ce 328: onsuccess: #2148: 1: Success after gcc/linux/qemu: 78 commits discards 1f2c6712d6 327: onsuccess: #2147: 1: Success after basepoints/gcc-13-50 [...] discards d9ca5b1549 326: onsuccess: #2146: 1: Success after binutils/gcc/linux/g [...] discards ea23b99598 325: onsuccess: #2145: 1: Success after binutils/gcc/glibc/g [...] discards ee931eaa34 324: onsuccess: #2144: 1: Success after binutils/gcc/gdb/qem [...] discards 163716f1c7 323: onsuccess: #2143: 1: Success after basepoints/gcc-13-50 [...] discards 537131e932 322: onsuccess: #2142: 1: Success after binutils/gcc/linux/g [...] discards e41a828cda 321: onsuccess: #2141: 1: Success after binutils/gcc/linux/g [...] discards 919ef023bf 320: onsuccess: #2140: 1: Success after binutils/gcc/gdb: 6 commits discards 9c0bf617ce 319: onsuccess: #2139: 1: Success after binutils/gcc/gdb: 11 [...] discards a16ece18bb 318: onsuccess: #2138: 1: Success after binutils/gcc/linux/g [...] discards fddd578b81 317: onsuccess: #2137: 1: Success after binutils/gcc/linux/g [...] discards fed893d09e 316: onsuccess: #2136: 1: Success after binutils/gcc/gdb: 26 [...] discards 5738ca7a65 315: onsuccess: #2135: 1: Success after binutils/gcc/gdb: 11 [...] discards ce69c45304 314: onsuccess: #2134: 1: Success after binutils/gcc/glibc/g [...] discards 2f21bb2960 313: onsuccess: #2133: 1: Success after binutils/gcc/linux/g [...] discards 91af0dc10b 312: onsuccess: #2132: 1: Success after glibc-2.36.9000-416- [...] discards d1d919b683 311: onsuccess: #2130: 1: Success after gcc: 4 commits discards e95969cc65 310: onsuccess: #2129: 1: Success after binutils: 4 commits discards 77a0b02ea6 309: onsuccess: #2127: 1: Success after binutils/gcc/glibc/g [...] discards e1f38025b0 308: onsuccess: #2126: 1: Success after binutils/gcc/linux/g [...] discards 9baa537f07 307: onsuccess: #2124: 1: Success after gcc: 2 commits discards 072f292963 306: onsuccess: #2123: 1: Success after binutils/gcc/gdb: 15 [...] discards 94cd22429f 305: onsuccess: #2122: 1: Success after binutils/gcc/gdb: 4 commits discards 0bbd8ae00a 304: onsuccess: #2121: 1: Success after gcc/linux: 13 commits discards 9daf822009 303: onsuccess: #2120: 1: Success after binutils/gdb: 20 commits discards 63ff90cecf 302: onsuccess: #2119: 1: Success after binutils/gdb: 7 commits discards 2a10daf59b 301: onsuccess: #2118: 1: Success after linux: 16 commits discards 57c6dfcc10 300: onsuccess: #2117: 1: Success after basepoints/gcc-13-49 [...] discards feefe0c5d2 299: onsuccess: #2116: 1: Success after gdb-13-branchpoint-2 [...] discards 64fb764095 298: onsuccess: #2114: 1: Success after binutils/gcc/gdb: 6 commits discards f1293e1326 297: onsuccess: #2113: 1: Success after binutils/gcc/gdb: 7 commits discards c5a9916b3a 296: onsuccess: #2112: 1: Success after gcc/linux: 26 commits discards 3dbdfbfc84 295: onsuccess: #2111: 1: Success after binutils/gcc/linux/g [...] discards 3ee3542d02 294: onsuccess: #2110: 1: Success after gcc: 17 commits discards ef23e7a638 293: onsuccess: #2109: 1: Success after binutils/gdb: 2 commits discards cab0192ab7 292: onsuccess: #2108: 1: Success after binutils/gcc/gdb: 3 commits discards 7b526a597a 291: onsuccess: #2107: 1: Success after binutils/gcc/gdb: 6 commits discards 1b51018008 290: onsuccess: #2106: 1: Success after gcc: 2 commits discards 3df57840dd 289: onsuccess: #2105: 1: Success after binutils/gcc/gdb: 6 commits discards 86aff461d5 288: onsuccess: #2104: 1: Success after binutils/gcc/gdb: 10 [...] discards 6008c34a39 287: onsuccess: #2103: 1: Success after gcc: 9 commits discards 3ad66e9dc4 286: onsuccess: #2102: 1: Success after binutils/gdb: 18 commits discards df87fd8aed 285: onsuccess: #2101: 1: Success after binutils/gcc/gdb: 5 commits discards 16b2db05f9 284: onsuccess: #2100: 1: Success after basepoints/gcc-13-48 [...] discards 7489f8c940 283: onsuccess: #2099: 1: Success after binutils/gdb: 4 commits discards fb0045793d 282: onsuccess: #2098: 1: Success after binutils/gcc/linux/g [...] discards cd3b913149 281: onsuccess: #2097: 1: Success after binutils/gcc/gdb: 23 [...] discards fe0edc8d57 280: onsuccess: #2096: 1: Success after binutils/gcc/gdb: 21 [...] discards 3e2f993b13 279: onsuccess: #2095: 1: Success after binutils/gcc/gdb: 5 commits discards 577c7a1d3a 278: onsuccess: #2094: 1: Success after binutils/gcc/linux/g [...] discards ad882a7288 277: onsuccess: #2093: 1: Success after binutils/gcc/linux/g [...] new a9805542f1 277: onsuccess: #2093: 1: Success after binutils/gcc/linux/g [...] new a1732d6cf7 278: onsuccess: #2094: 1: Success after binutils/gcc/linux/g [...] new d414d3521d 279: onsuccess: #2095: 1: Success after binutils/gcc/gdb: 5 commits new 7372a98817 280: onsuccess: #2096: 1: Success after binutils/gcc/gdb: 21 [...] new 5d94fc31d7 281: onsuccess: #2097: 1: Success after binutils/gcc/gdb: 23 [...] new bc33abf3b9 282: onsuccess: #2098: 1: Success after binutils/gcc/linux/g [...] new 21a2fa0bb4 283: onsuccess: #2099: 1: Success after binutils/gdb: 4 commits new 7dce54457a 284: onsuccess: #2100: 1: Success after basepoints/gcc-13-48 [...] new fd44527db6 285: onsuccess: #2101: 1: Success after binutils/gcc/gdb: 5 commits new 51839bd901 286: onsuccess: #2102: 1: Success after binutils/gdb: 18 commits new 1039835a18 287: onsuccess: #2103: 1: Success after gcc: 9 commits new 41937fa279 288: onsuccess: #2104: 1: Success after binutils/gcc/gdb: 10 [...] new abdf740172 289: onsuccess: #2105: 1: Success after binutils/gcc/gdb: 6 commits new ea5621bc36 290: onsuccess: #2106: 1: Success after gcc: 2 commits new bd58d99680 291: onsuccess: #2107: 1: Success after binutils/gcc/gdb: 6 commits new f4a5d72353 292: onsuccess: #2108: 1: Success after binutils/gcc/gdb: 3 commits new d0f427ced4 293: onsuccess: #2109: 1: Success after binutils/gdb: 2 commits new a5b8023dfb 294: onsuccess: #2110: 1: Success after gcc: 17 commits new b408a9c122 295: onsuccess: #2111: 1: Success after binutils/gcc/linux/g [...] new 276edc757b 296: onsuccess: #2112: 1: Success after gcc/linux: 26 commits new fbb98a25ee 297: onsuccess: #2113: 1: Success after binutils/gcc/gdb: 7 commits new 00b9191c96 298: onsuccess: #2114: 1: Success after binutils/gcc/gdb: 6 commits new b23e237f1e 299: onsuccess: #2116: 1: Success after gdb-13-branchpoint-2 [...] new 231d7418db 300: onsuccess: #2117: 1: Success after basepoints/gcc-13-49 [...] new 6888b1113f 301: onsuccess: #2118: 1: Success after linux: 16 commits new 5cc758082c 302: onsuccess: #2119: 1: Success after binutils/gdb: 7 commits new 25f3f36f6f 303: onsuccess: #2120: 1: Success after binutils/gdb: 20 commits new 0d8c07ed1b 304: onsuccess: #2121: 1: Success after gcc/linux: 13 commits new 557c1eeae1 305: onsuccess: #2122: 1: Success after binutils/gcc/gdb: 4 commits new 1485be483c 306: onsuccess: #2123: 1: Success after binutils/gcc/gdb: 15 [...] new be1edbe023 307: onsuccess: #2124: 1: Success after gcc: 2 commits new 7993633fa8 308: onsuccess: #2126: 1: Success after binutils/gcc/linux/g [...] new 48b4416400 309: onsuccess: #2127: 1: Success after binutils/gcc/glibc/g [...] new a90373dbf6 310: onsuccess: #2129: 1: Success after binutils: 4 commits new 72c55177b3 311: onsuccess: #2130: 1: Success after gcc: 4 commits new 0d36126bc0 312: onsuccess: #2132: 1: Success after glibc-2.36.9000-416- [...] new 8a2361598b 313: onsuccess: #2133: 1: Success after binutils/gcc/linux/g [...] new 52de6e8e86 314: onsuccess: #2134: 1: Success after binutils/gcc/glibc/g [...] new 3ad68994b5 315: onsuccess: #2135: 1: Success after binutils/gcc/gdb: 11 [...] new fbe1e83bb2 316: onsuccess: #2136: 1: Success after binutils/gcc/gdb: 26 [...] new b8cb619577 317: onsuccess: #2137: 1: Success after binutils/gcc/linux/g [...] new f8344d9ccd 318: onsuccess: #2138: 1: Success after binutils/gcc/linux/g [...] new cea98f80f7 319: onsuccess: #2139: 1: Success after binutils/gcc/gdb: 11 [...] new 924f2ebd55 320: onsuccess: #2140: 1: Success after binutils/gcc/gdb: 6 commits new 675582e8e3 321: onsuccess: #2141: 1: Success after binutils/gcc/linux/g [...] new b6c0fb8a5d 322: onsuccess: #2142: 1: Success after binutils/gcc/linux/g [...] new a364ff87c7 323: onsuccess: #2143: 1: Success after basepoints/gcc-13-50 [...] new 0b3b2a7f59 324: onsuccess: #2144: 1: Success after binutils/gcc/gdb/qem [...] new 0ca8e9afbb 325: onsuccess: #2145: 1: Success after binutils/gcc/glibc/g [...] new 6910372d60 326: onsuccess: #2146: 1: Success after binutils/gcc/linux/g [...] new 36b48a3d58 327: onsuccess: #2147: 1: Success after basepoints/gcc-13-50 [...] new 9a9fddfce9 328: onsuccess: #2148: 1: Success after gcc/linux/qemu: 78 commits new 6764ccb533 329: onsuccess: #2149: 1: Success after binutils/gcc/gdb/qem [...] new eece2b41d8 330: onsuccess: #2150: 1: Success after linux/qemu: 36 commits new 7b10a1b24c 331: onsuccess: #2151: 1: Success after binutils/gcc/linux/g [...] new 36e5de135a 332: onsuccess: #2152: 1: Success after binutils/gcc/gdb/qem [...] new fcdba547e7 333: onsuccess: #2153: 1: Success after binutils/gcc/gdb/qem [...] new 63b8f2397f 334: onsuccess: #2154: 1: Success after binutils/gcc/linux/g [...] new 144fd92bd4 335: onsuccess: #2155: 1: Success after binutils/gdb: 146 commits new d7785f3eb5 336: onsuccess: #2156: 1: Success after binutils/gcc/linux/g [...] new c7cea911f8 337: onsuccess: #2157: 1: Success after binutils/gcc/glibc/g [...] new f22b5e969c 338: onsuccess: #2158: 1: Success after binutils/gcc/linux/g [...] new 5b2a0b2b32 339: onsuccess: #2159: 1: Success after binutils/gcc/gdb: 4 commits new 1064f3a585 340: onsuccess: #2160: 1: Success after binutils/gcc/gdb: 15 [...] new 338097f4f8 341: onsuccess: #2161: 1: Success after binutils/gcc/gdb: 11 [...] new c4e4201987 342: onsuccess: #2162: 1: Success after binutils/gcc/linux/g [...] new 2c321e6472 343: onsuccess: #2163: 1: Success after binutils/gcc/gdb: 7 commits new 2ba2b9a755 344: onsuccess: #2164: 1: Success after gcc/linux/glibc: 37 commits new 107101cb6e 345: onsuccess: #2165: 1: Success after binutils/gcc/glibc/g [...] new 0c1929bc36 346: onsuccess: #2166: 1: Success after binutils/gcc/linux/g [...] new 600310fad0 347: onsuccess: #2167: 1: Success after basepoints/gcc-13-51 [...] new 6be4595c31 348: onsuccess: #2168: 1: Success after binutils/gcc/gdb: 9 commits new 7977b4dd28 349: onsuccess: #2169: 1: Success after binutils/gcc/linux/g [...] new 1ea4608daa 350: onsuccess: #2170: 1: Success after binutils/gcc/linux/g [...] new d5453f4e97 351: onsuccess: #2171: 1: Success after gcc/linux: 15 commits new 40aa965579 352: onsuccess: #2172: 1: Success after binutils/gcc/linux/g [...] new 815b9ad4a7 353: onsuccess: #2173: 1: Success after binutils/gcc/gdb: 27 [...] new 2dc0bc7f00 354: onsuccess: #2174: 1: Success after binutils/gcc/linux/g [...] new ffcfed9697 355: onsuccess: #2175: 1: Success after binutils/gcc/linux/g [...] new 8221317a8c 356: onsuccess: #2176: 1: Success after binutils/gcc/linux/g [...] new 5f1a95bb95 357: onsuccess: #2177: 1: Success after binutils/gcc/linux/g [...] new 759b53648d 358: onsuccess: #2178: 1: Success after binutils/gcc/linux/g [...] new ef4d0c7489 359: onsuccess: #2179: 1: Success after binutils/gcc/glibc/g [...] new feba6cd4b7 360: onsuccess: #2180: 1: Success after binutils/gcc/linux/g [...] new 72664b79ec 361: onsuccess: #2181: 1: Success after binutils/gcc/linux/g [...] new 88d3b912e2 362: onsuccess: #2182: 1: Success after binutils/gcc/linux/g [...] new 85ce46e7d6 363: onsuccess: #2183: 1: Success after binutils/gcc/linux/g [...] new 079cb0d983 364: onsuccess: #2184: 1: Success after binutils/gcc/linux/g [...] new a2d056110f 365: onsuccess: #2185: 1: Success after binutils/gcc/linux/g [...] new b7b62ed6a4 366: onsuccess: #2186: 1: Success after binutils/gcc/linux/g [...] new c89eec8b3f 367: onsuccess: #2187: 1: Success after binutils/gcc/gdb: 14 [...] new 03785b8f06 368: onsuccess: #2188: 1: Success after binutils/gcc/linux/g [...] new 7b3b77a1be 369: onsuccess: #2189: 1: Success after binutils/gcc/linux/g [...] new b1d037d59a 370: onsuccess: #2190: 1: Success after binutils/gcc/linux/g [...] new 422216bd52 371: onsuccess: #2191: 1: Success after binutils/gcc/gdb: 10 [...] new 7dc2c11131 372: onsuccess: #2192: 1: Success after binutils/gcc/linux/g [...] new 1aed2f1f9e 373: onsuccess: #2193: 1: Success after binutils/gcc/glibc/g [...] new e98e997d12 374: onsuccess: #2194: 1: Success after binutils/gcc/linux/g [...] new e03a6442ee 375: onsuccess: #2195: 1: Success after binutils/gcc/gdb/qem [...] new 3a4bf55be9 376: onsuccess: #2197: 1: Success after binutils/gcc/linux/g [...] new 435c31d82e 377: onsuccess: #2198: 1: Success after binutils/gcc/gdb: 3 commits new 6c842f4f59 378: onsuccess: #2199: 1: Success after binutils/gdb: 4 commits This update added new revisions after undoing existing revisions. That is to say, some revisions that were in the old version of the branch are not in the new version. This situation occurs when a user --force pushes a change and generates a repository containing something like this: * -- * -- B -- O -- O -- O (fdddd83b18) \ N -- N -- N refs/heads/linaro-local/ci/tcwg_gnu_cross_check_gcc/mast [...] You should already have received notification emails for all of the O revisions, and so the following emails describe only the N revisions from the common base, B. Any revisions marked "omits" are not gone; other references still refer to them. Any revisions marked "discards" are gone forever. The 102 revisions listed above as "new" are entirely new to this repository and will be described in separate emails. The revisions listed as "adds" were already present in the repository and have only been added to this reference. Summary of changes: 01-reset_artifacts/console.log.xz | Bin 1816 -> 1792 bytes 02-prepare_abe/console.log.xz | Bin 2808 -> 2796 bytes 03-build_abe-binutils/console.log.xz | Bin 31228 -> 31720 bytes 04-build_abe-stage1/console.log.xz | Bin 91988 -> 91380 bytes 06-build_abe-linux/console.log.xz | Bin 8908 -> 8900 bytes 07-build_abe-glibc/console.log.xz | Bin 236880 -> 237984 bytes 08-build_abe-stage2/console.log.xz | Bin 229236 -> 230488 bytes 09-build_abe-gdb/console.log.xz | Bin 38608 -> 39204 bytes 10-build_abe-qemu/console.log.xz | Bin 32128 -> 32044 bytes 11-build_abe-dejagnu/console.log.xz | Bin 3888 -> 3888 bytes 12-build_abe-check_gcc/console.log.xz | Bin 2672 -> 2696 bytes 13-check_regression/console.log.xz | Bin 5804 -> 5544 bytes 13-check_regression/extra-bisect-params | 1 - 13-check_regression/fails.sum | 7 - 13-check_regression/mail-body.txt | 42 +- 13-check_regression/results.compare | 10 +- 13-check_regression/results.compare2 | 36 +- 13-check_regression/results.regressions | 27 - 14-update_baseline/console.log | 66 +- dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gdb_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 44 +- mail/mail-subject.txt | 2 +- manifest.sh | 28 +- results | 27 - sumfiles/g++.log.xz | Bin 2672236 -> 2677324 bytes sumfiles/g++.sum | 24 +- sumfiles/gcc.log.xz | Bin 2202476 -> 2211628 bytes sumfiles/gcc.sum | 2398 +++++++++++++++---------------- sumfiles/gfortran.log.xz | Bin 898476 -> 895252 bytes sumfiles/gfortran.sum | 56 +- sumfiles/libatomic.log.xz | Bin 2260 -> 2260 bytes sumfiles/libatomic.sum | 2 +- sumfiles/libgomp.log.xz | Bin 214544 -> 214436 bytes sumfiles/libgomp.sum | 2 +- sumfiles/libitm.log.xz | Bin 2668 -> 2676 bytes sumfiles/libitm.sum | 2 +- sumfiles/libstdc++.log.xz | Bin 438060 -> 445088 bytes sumfiles/libstdc++.sum | 36 +- 41 files changed, 1386 insertions(+), 1432 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_kernel/gnu-master-arm-next-allmodconfig updated (1bb71a9f65 -> 23ff20c75f)

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-arm-next-allmodconfig in repository toolchain/ci/base-artifacts. from 1bb71a9f65 41: onsuccess: #589: 23322: Success after binutils/gcc/linux [...] new 23ff20c75f 42: onsuccess: #590: 23350: Success after binutils/gcc/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 1768 -> 1764 bytes 02-prepare_abe/console.log.xz | Bin 2768 -> 2768 bytes 03-build_abe-binutils/console.log.xz | Bin 30712 -> 31272 bytes 04-build_abe-stage1/console.log.xz | Bin 90796 -> 91272 bytes 05-build_abe-qemu/console.log.xz | Bin 31012 -> 31956 bytes 06-build_linux/console.log.xz | Bin 11708 -> 11020 bytes 08-check_regression/console.log.xz | Bin 3868 -> 4500 bytes 08-check_regression/mail-body.txt | 4 ++-- 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 | 6 +++--- mail/mail-subject.txt | 2 +- manifest.sh | 32 ++++++++++++++++---------------- results | 2 +- 18 files changed, 29 insertions(+), 29 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-aarch64-stable-allmodconfig updated (8a1569ed98 -> 521f73743f)

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-aarch64-stable-allmodconfig in repository toolchain/ci/base-artifacts. from 8a1569ed98 52: onsuccess: #553: all: Success after binutils: 113 commits new 521f73743f 53: onsuccess: #555: all: Success after v7.2.0-912-g026817fb [...] 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 -> 1892 bytes 02-prepare_abe/console.log.xz | Bin 2800 -> 2760 bytes 03-build_abe-binutils/console.log.xz | Bin 31904 -> 31312 bytes 04-build_kernel_llvm/console.log.xz | Bin 66692 -> 64920 bytes 05-build_abe-qemu/console.log.xz | Bin 32316 -> 31900 bytes 06-build_linux/console.log.xz | Bin 4552 -> 3384 bytes 07-boot_linux/console.log.xz | Bin 504 -> 504 bytes 08-check_regression/console.log.xz | Bin 2860 -> 2640 bytes 09-update_baseline/console.log | 8 ++++---- dashboard/dashboard-generate.sh | 2 +- git/qemu_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 2 +- mail/mail-subject.txt | 2 +- manifest.sh | 20 ++++++++++---------- 15 files changed, 19 insertions(+), 19 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-lts-allnoconfig updated (0a4cacf45f -> c61287081c)

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-lts-allnoconfig in repository toolchain/ci/base-artifacts. from 0a4cacf45f 39: onsuccess: #481: boot: Success after binutils/gcc: 186 commits new c61287081c 40: onsuccess: #482: boot: Success after binutils/gcc/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 1800 -> 1784 bytes 02-prepare_abe/console.log.xz | Bin 2768 -> 2788 bytes 03-build_abe-binutils/console.log.xz | Bin 30988 -> 32016 bytes 04-build_abe-stage1/console.log.xz | Bin 73216 -> 74096 bytes 05-build_abe-qemu/console.log.xz | Bin 31364 -> 32756 bytes 06-build_linux/console.log.xz | Bin 3316 -> 3352 bytes 07-boot_linux/console.log.xz | Bin 504 -> 504 bytes 08-check_regression/console.log.xz | Bin 3412 -> 4356 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 ++++++++++++++++---------------- 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

Jump to page:

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

Tcwg-commits February 2023