Tcwg-commits January 2023

tcwg-commits@lists.linaro.org

5 participants
4127 discussions

[binutils-gdb] branch gdb-13-branch updated (44916dc8501 -> 322fde46dcc)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. unknown user pushed a change to branch gdb-13-branch in repository binutils-gdb. from 44916dc8501 Automatic date update in version.in new 322fde46dcc [gdb] Fix segfault during inferior call to ifunc 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: gdb/infcall.c | 3 +++ gdb/testsuite/gdb.base/gnu-ifunc.exp | 9 +++++++-- 2 files changed, 10 insertions(+), 2 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

1 year, 10 months

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_bmk_llvm_apm/llvm-master-aarch64-spec2k6-Oz_LTO updated (8e3837e7ec -> 476c1a7948)

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_llvm_apm/llvm-master-aarch64-spec2k6-Oz_LTO in repository toolchain/ci/base-artifacts. from 8e3837e7ec 35: onsuccess: #339: 1: [TCWG CI] No change after binutils/g [...] new 476c1a7948 36: onsuccess: #340: 1: [TCWG CI] No change after binutils/g [...] 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 1912 -> 1856 bytes 02-prepare_abe/console.log.xz | Bin 2776 -> 2768 bytes 03-build_abe-binutils/console.log.xz | Bin 32136 -> 32788 bytes 04-build_abe-stage1/console.log.xz | Bin 74016 -> 73844 bytes 05-clean_sysroot/console.log.xz | Bin 332 -> 332 bytes 06-build_abe-linux/console.log.xz | Bin 8700 -> 8704 bytes 07-build_abe-glibc/console.log.xz | Bin 245160 -> 246840 bytes 08-build_abe-stage2/console.log.xz | Bin 178680 -> 183788 bytes 09-build_llvm-true-false-cflags-/console.log.xz | Bin 63892 -> 61536 bytes 10-benchmark/benchmark-build.log | 98 +- 10-benchmark/benchmark.log | 96 +- 10-benchmark/console.log.xz | Bin 3992 -> 4004 bytes 11-check_regression/console.log.xz | Bin 6788 -> 7764 bytes .../csv-results-vs-first-0/results.csv | 32112 +- .../csv-results-vs-first-0/size.csv | 389412 +++++++++--------- .../csv-results-vs-first-1/perf.csv | 130 +- .../csv-results-vs-first-1/results.csv | 43419 +- .../csv-results-vs-first-1/size.csv | 375358 +++++++++-------- 11-check_regression/csv-results-vs-prev-0/perf.csv | 150 +- .../csv-results-vs-prev-0/results.csv | 41596 +- 11-check_regression/csv-results-vs-prev-0/size.csv | 334736 +++++++-------- 11-check_regression/csv-results-vs-prev-1/perf.csv | 130 +- .../csv-results-vs-prev-1/results.csv | 43419 +- 11-check_regression/csv-results-vs-prev-1/size.csv | 375358 +++++++++-------- 11-check_regression/results-vs-first-brief.csv | 40 +- 11-check_regression/results-vs-first-full.csv | 140 +- 11-check_regression/results-vs-first-internal.csv | 46 +- 11-check_regression/results-vs-first.csv | 46 +- 11-check_regression/results-vs-first.log | 840 +- 11-check_regression/results-vs-prev-brief.csv | 40 +- 11-check_regression/results-vs-prev-full.csv | 148 +- 11-check_regression/results-vs-prev-internal.csv | 46 +- 11-check_regression/results-vs-prev.csv | 46 +- 11-check_regression/results-vs-prev.log | 928 +- 12-update_baseline/console.log | 16 +- dashboard/dashboard-generate.sh | 2 +- .../400.perlbench/results-metadata.json | 18 +- .../400.perlbench/results-metrics.json | 2 +- .../squad-vs-first/401.bzip2/results-metadata.json | 18 +- .../squad-vs-first/401.bzip2/results-metrics.json | 2 +- .../squad-vs-first/403.gcc/results-metadata.json | 18 +- .../squad-vs-first/403.gcc/results-metrics.json | 2 +- .../squad-vs-first/429.mcf/results-metadata.json | 18 +- .../squad-vs-first/433.milc/results-metadata.json | 18 +- .../squad-vs-first/444.namd/results-metadata.json | 18 +- .../squad-vs-first/445.gobmk/results-metadata.json | 18 +- .../447.dealII/results-metadata.json | 18 +- .../450.soplex/results-metadata.json | 18 +- .../squad-vs-first/450.soplex/results-metrics.json | 2 +- .../453.povray/results-metadata.json | 18 +- .../squad-vs-first/456.hmmer/results-metadata.json | 18 +- .../squad-vs-first/456.hmmer/results-metrics.json | 2 +- .../squad-vs-first/458.sjeng/results-metadata.json | 18 +- .../462.libquantum/results-metadata.json | 18 +- .../464.h264ref/results-metadata.json | 18 +- .../464.h264ref/results-metrics.json | 2 +- .../squad-vs-first/470.lbm/results-metadata.json | 18 +- .../471.omnetpp/results-metadata.json | 18 +- .../471.omnetpp/results-metrics.json | 2 +- .../squad-vs-first/473.astar/results-metadata.json | 18 +- .../482.sphinx3/results-metadata.json | 18 +- .../483.xalancbmk/results-metadata.json | 18 +- .../squad-vs-first/Mean/results-metadata.json | 18 +- dashboard/squad-vs-first/dashboard-push-squad.sh | 82 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- git/glibc_rev | 2 +- git/linux_rev | 2 +- git/llvm_rev | 2 +- mail/jira-body.txt | 50 +- mail/mail-body.txt | 50 +- mail/mail-subject.txt | 2 +- manifest.sh | 42 +- results_id | 2 +- save-temps/400.perlbench.tar.xz | Bin 1259332 -> 2929656 bytes save-temps/401.bzip2.tar.xz | Bin 92008 -> 301040 bytes save-temps/403.gcc.tar.xz | Bin 3536536 -> 7625560 bytes save-temps/410.bwaves.tar.xz | Bin 15240 -> 53080 bytes save-temps/416.gamess.tar.xz | Bin 4118768 -> 17149476 bytes save-temps/429.mcf.tar.xz | Bin 36544 -> 71796 bytes save-temps/433.milc.tar.xz | Bin 165368 -> 370604 bytes save-temps/434.zeusmp.tar.xz | Bin 126080 -> 530532 bytes save-temps/435.gromacs.tar.xz | Bin 956692 -> 2368288 bytes save-temps/436.cactusADM.tar.xz | Bin 709776 -> 1833968 bytes save-temps/437.leslie3d.tar.xz | Bin 47112 -> 176528 bytes save-temps/444.namd.tar.xz | Bin 165180 -> 674188 bytes save-temps/445.gobmk.tar.xz | Bin 1836896 -> 2723592 bytes save-temps/447.dealII.tar.xz | Bin 6437144 -> 11643184 bytes save-temps/450.soplex.tar.xz | Bin 731120 -> 1472664 bytes save-temps/453.povray.tar.xz | Bin 1385108 -> 2672576 bytes save-temps/454.calculix.tar.xz | Bin 1233932 -> 3557816 bytes save-temps/456.hmmer.tar.xz | Bin 371356 -> 988732 bytes save-temps/458.sjeng.tar.xz | Bin 144080 -> 322344 bytes save-temps/459.GemsFDTD.tar.xz | Bin 150768 -> 640068 bytes save-temps/462.libquantum.tar.xz | Bin 62008 -> 116332 bytes save-temps/464.h264ref.tar.xz | Bin 556680 -> 3324868 bytes save-temps/465.tonto.tar.xz | Bin 2229060 -> 8355464 bytes save-temps/470.lbm.tar.xz | Bin 26824 -> 52176 bytes save-temps/471.omnetpp.tar.xz | Bin 1098832 -> 1522300 bytes save-temps/473.astar.tar.xz | Bin 89276 -> 160528 bytes save-temps/481.wrf.tar.xz | Bin 1593700 -> 9113560 bytes save-temps/482.sphinx3.tar.xz | Bin 248684 -> 586712 bytes save-temps/483.xalancbmk.tar.xz | Bin 11895996 -> 17713580 bytes 103 files changed, 818179 insertions(+), 820785 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

1 year, 10 months

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_gcc_bootstrap/release-arm-bootstrap_O1 updated (95c2a7a52f -> f1a7266c78)

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_gcc_bootstrap/release-arm-bootstrap_O1 in repository toolchain/ci/base-artifacts. from 95c2a7a52f 43: onsuccess: #149: 2: Success after binutils/gcc: 7 commits new f1a7266c78 44: onsuccess: #150: 2: Success after binutils/gcc: 13 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 1720 -> 1752 bytes 02-prepare_abe/console.log.xz | Bin 2756 -> 2744 bytes 04-build_abe-binutils/console.log.xz | Bin 50824 -> 52200 bytes 05-build_abe-bootstrap_O1/console.log.xz | Bin 461200 -> 460684 bytes 06-check_regression/console.log.xz | Bin 2668 -> 2780 bytes dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 2 +- mail/mail-subject.txt | 2 +- manifest.sh | 20 ++++++++++---------- 12 files changed, 16 insertions(+), 16 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

1 year, 10 months

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_gnu_native_check_binutils/master-arm updated (7e2d96c92f -> bc816971bf)

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_native_check_binutils/master-arm in repository toolchain/ci/base-artifacts. discards 7e2d96c92f 150: onsuccess: #577: 1: Success after binutils/gcc/linux/gd [...] discards d42fbee223 149: onsuccess: #576: 1: Success after binutils/gcc/linux/gd [...] discards c94cfcfd07 148: onsuccess: #575: 1: Success after binutils/gcc/linux/gd [...] discards 9f3db1d35a 147: onsuccess: #574: 1: Success after binutils/gcc/linux/gl [...] discards be62a855a9 146: onsuccess: #573: 1: Success after binutils/gcc/gdb: 11 commits discards 23417dd913 145: onsuccess: #572: 1: Success after binutils/gcc/gdb: 27 commits discards ff04d48667 144: onsuccess: #571: 1: Success after binutils/gcc/gdb: 28 commits discards 8f5016b554 143: onsuccess: #570: 1: Success after binutils/gcc/linux/gd [...] discards 465a35b24e 142: onsuccess: #569: 1: Success after binutils/gcc/gdb: 46 commits discards 91001093b3 141: onsuccess: #568: 1: Success after binutils/gcc/linux/gd [...] discards 1d69a1c235 140: onsuccess: #567: 1: Success after binutils/gcc/linux/gl [...] discards f4903d65b2 139: onsuccess: #566: 1: Success after binutils/gcc/linux/gl [...] discards b84f440724 138: onsuccess: #565: 1: Success after binutils/gcc/linux/gl [...] discards 89b77677f0 137: onsuccess: #564: 1: Success after binutils/gcc/linux/gl [...] discards f05cca9b2f 136: onsuccess: #563: 1: Success after binutils/gcc/glibc/gd [...] discards 7404eb9ae8 135: onsuccess: #562: 1: Success after binutils/gcc/linux/gd [...] discards 4207133f4d 134: onsuccess: #561: 1: Success after binutils/gcc/linux/gd [...] discards c6acea4e5f 133: onsuccess: #560: 1: Success after binutils/gcc/linux/gl [...] discards 2ef66fed89 132: onsuccess: #559: 1: Success after binutils/gcc/linux/gd [...] discards 7329eb23a2 131: onsuccess: #558: 1: Success after binutils/gcc/linux/gl [...] discards 56fde29991 130: onsuccess: #557: 1: Success after binutils/gcc/linux/gl [...] discards e43ea109ac 129: onsuccess: #556: 1: Success after binutils/gcc/linux/gd [...] discards 01900a0641 128: onsuccess: #555: 1: Success after binutils/gcc/linux/gd [...] discards 31d9973c51 127: onsuccess: #554: 1: Success after binutils/gcc/linux/gl [...] discards a8defd5851 126: onsuccess: #553: 1: Success after binutils/gcc/linux/gl [...] discards 80ca52244b 125: onsuccess: #552: 1: Success after binutils/gcc/linux/gl [...] discards 996fb38d74 124: onsuccess: #551: 1: Success after binutils/gcc/linux/gl [...] discards 2b6a4b64ca 123: onsuccess: #550: 1: Success after binutils/gcc/linux/gd [...] discards 37679decce 122: onsuccess: #549: 1: Success after binutils/gcc/linux/gd [...] discards ef6b6be60f 121: onsuccess: #548: 1: Success after binutils/gcc/linux/gd [...] discards d9038c0256 120: onsuccess: #547: 1: Success after binutils/gcc/linux/gl [...] discards 7184062ea4 119: onsuccess: #546: 1: Success after binutils/gcc/linux/gd [...] discards 11b203ea8e 118: onsuccess: #545: 1: Success after binutils/gcc/linux/gd [...] discards 79b7818ec9 117: onsuccess: #544: 1: Success after binutils/gcc/linux/gl [...] discards 4d2f2ada0b 116: onsuccess: #543: 1: Success after binutils/gcc/linux/gl [...] discards 257dc1bf2a 115: onsuccess: #542: 1: Success after binutils/gcc/linux/gl [...] discards 48c297d29e 114: onsuccess: #541: 1: Success after binutils/gcc/linux/gd [...] discards ef281b10a4 113: onsuccess: #539: 1: Success after binutils/gcc/linux/gd [...] discards aa487e7ef4 112: onsuccess: #538: 1: Success after binutils/gcc/linux/gd [...] discards 015ef3e74d 111: onsuccess: #537: 1: Success after binutils/gcc/gdb: 69 commits discards 3ba4b7e1a4 110: onsuccess: #536: 1: Success after binutils/gcc/glibc/gd [...] discards 55a94c8e39 109: onsuccess: #535: 1: Success after binutils/gcc/linux/gd [...] discards 9765f51fd5 108: onsuccess: #534: 1: Success after binutils/gcc/linux/gd [...] discards 8c9d2cbb09 107: onsuccess: #533: 1: Success after binutils/gcc/linux/gd [...] discards 902211bdb5 106: onsuccess: #532: 1: Success after binutils/gcc/linux/gl [...] discards 157a7de388 105: onsuccess: #531: 1: Success after binutils/gcc/linux/gd [...] discards 79bb132488 104: onsuccess: #530: 1: Success after gcc: 7 commits discards 3888aa789e 103: onsuccess: #529: 1: Success after binutils/gcc/linux/gl [...] discards 21d88d2ace 102: onsuccess: #527: 1: Success after binutils: 5 commits discards d02a974f46 101: onsuccess: #524: 1: Success after binutils: 2 commits discards 6afaf8ff6e 100: onsuccess: #521: 1: Success after binutils: 10 commits discards eb4a0e3428 99: onsuccess: #519: 1: Success after binutils/gcc/linux/gli [...] discards 8f96a3551e 98: onsuccess: #518: 1: Success after binutils/gcc/linux/gli [...] discards e0a0ac5ed1 97: onsuccess: #517: 1: Success after binutils/gcc/linux/gli [...] discards 72bd2775e4 96: onsuccess: #516: 1: Success after binutils/gcc/linux/gli [...] discards d8d6925f39 95: onsuccess: #515: 1: Success after binutils/gcc/linux/gdb [...] discards d54a344cda 94: onsuccess: #514: 1: Success after binutils/gcc/linux/gdb [...] discards 387e562bf6 93: onsuccess: #513: 1: Success after binutils/gcc/linux/gli [...] discards d90a4812a8 92: onsuccess: #512: 1: Success after binutils/gcc/linux/gli [...] discards 9e2163bff4 91: onsuccess: #511: 1: Success after linux: 27 commits discards 000ea56693 90: onsuccess: #510: 1: Success after glibc: 5 commits discards 9b2c1bd6d2 89: onsuccess: #508: 1: Success after binutils: 12 commits discards c07a2b9740 88: onsuccess: #506: 1: Success after linux: 34 commits discards 24aaa2f2e7 87: onsuccess: #505: 1: Success after glibc: 7 commits discards c4ef0ad55d 86: onsuccess: #503: 1: Success after binutils: 12 commits discards 55cd3e9a92 85: onsuccess: #501: 1: Success after binutils/gcc/linux/gli [...] discards 18379529f2 84: onsuccess: #500: 1: Success after binutils/gcc/linux/gli [...] discards fc787a9d9a 83: onsuccess: #499: 1: Success after binutils/gcc/linux/gdb [...] discards 1478c3fc0f 82: onsuccess: #498: 1: Success after binutils/gcc/linux/gli [...] discards 785aea605c 81: onsuccess: #497: 1: Success after binutils/gcc/linux/gli [...] discards 5d232ff22a 80: onsuccess: #496: 1: Success after binutils/gcc/linux/gli [...] discards ac03f4d9d1 79: onsuccess: #495: 1: Success after binutils/gcc/linux/gli [...] discards 042b7bf973 78: onsuccess: #494: 1: Success after binutils/gcc/linux/gli [...] discards 5f4469769d 77: onsuccess: #493: 1: Success after binutils/gcc/linux/gdb [...] discards a1d0d41e90 76: onsuccess: #492: 1: Success after binutils/gcc/linux/gdb [...] discards 283c9dc3d8 75: onsuccess: #491: 1: Success after binutils/gcc/linux/gdb [...] discards 5cc1676af9 74: onsuccess: #490: 1: Success after binutils/gcc/linux/gli [...] discards af1ef45c0e 73: onsuccess: #489: 1: Success after binutils/gcc/glibc/gdb [...] discards f72dd15324 72: onsuccess: #488: 1: Success after binutils/gcc/linux/gli [...] discards dd309f6277 71: onsuccess: #487: 1: Success after binutils/gcc/linux/gdb [...] discards 5aaa293034 70: onsuccess: #486: 1: Success after binutils/gcc/linux/gli [...] discards a6d68aea51 69: onsuccess: #485: 1: Success after binutils/gcc/linux/gdb [...] discards 3a3b054733 68: onsuccess: #484: 1: Success after binutils/gcc/linux/gli [...] discards 276feb22bf 67: onsuccess: #483: 1: Success after binutils/gcc/linux/gli [...] discards 4dfd1b7cae 66: onsuccess: #482: 1: Success after binutils/gcc/linux/gli [...] discards 55ab9a7379 65: onsuccess: #481: 1: Success after binutils/gcc/linux/gdb [...] discards 03055cd1a6 64: onsuccess: #480: 1: Success after binutils/gcc/linux/gli [...] discards db71640bbe 63: onsuccess: #479: 1: Success after binutils/gcc/linux/gli [...] discards 9b65c16230 62: onsuccess: #478: 1: Success after binutils/gcc/linux/gli [...] discards 06cd6bd0da 61: onsuccess: #477: 1: Success after binutils/gcc/linux/gli [...] discards 9d06588e07 60: onsuccess: #476: 1: Success after binutils/gcc/linux/gli [...] discards ef6746d002 59: onsuccess: #475: 1: Success after binutils/gcc/linux/gli [...] discards ccd72917d6 58: onsuccess: #474: 1: Success after binutils/gcc/linux/gli [...] discards 76d40a4894 57: onsuccess: #473: 1: Success after binutils/gcc/linux/gli [...] discards 32aa934778 56: onsuccess: #472: 1: Success after binutils/gcc/linux/gdb [...] discards a31e99a39e 55: onsuccess: #471: 1: Success after binutils/gcc/linux/gli [...] discards 2d54c8d7a5 54: onsuccess: #470: 1: Success after binutils/gcc/linux/gli [...] discards 03438754ed 53: onsuccess: #469: 1: Success after binutils/gcc/linux/gli [...] discards 946507a7fe 52: onsuccess: #467: 1: Success after binutils: 9 commits discards 4b980d1ff3 51: onsuccess: #464: 1: Success after binutils: 6 commits discards 2f8a5b98a6 50: onsuccess: #461: 1: Success after binutils: 12 commits new afa18542bd 50: onsuccess: #461: 1: Success after binutils: 12 commits new a97c8a3c10 51: onsuccess: #464: 1: Success after binutils: 6 commits new a476de794b 52: onsuccess: #467: 1: Success after binutils: 9 commits new 88ab033f24 53: onsuccess: #469: 1: Success after binutils/gcc/linux/gli [...] new 33dfc98f84 54: onsuccess: #470: 1: Success after binutils/gcc/linux/gli [...] new 619f9df9d7 55: onsuccess: #471: 1: Success after binutils/gcc/linux/gli [...] new 9046e058ce 56: onsuccess: #472: 1: Success after binutils/gcc/linux/gdb [...] new 1456d04a7c 57: onsuccess: #473: 1: Success after binutils/gcc/linux/gli [...] new 70e5213358 58: onsuccess: #474: 1: Success after binutils/gcc/linux/gli [...] new d71bbe382f 59: onsuccess: #475: 1: Success after binutils/gcc/linux/gli [...] new 6227653263 60: onsuccess: #476: 1: Success after binutils/gcc/linux/gli [...] new 8ae8739f6d 61: onsuccess: #477: 1: Success after binutils/gcc/linux/gli [...] new ff8250d91f 62: onsuccess: #478: 1: Success after binutils/gcc/linux/gli [...] new c2895aa094 63: onsuccess: #479: 1: Success after binutils/gcc/linux/gli [...] new f1a50a0b12 64: onsuccess: #480: 1: Success after binutils/gcc/linux/gli [...] new b78e41fa14 65: onsuccess: #481: 1: Success after binutils/gcc/linux/gdb [...] new 552313d8dc 66: onsuccess: #482: 1: Success after binutils/gcc/linux/gli [...] new a2ab5aab38 67: onsuccess: #483: 1: Success after binutils/gcc/linux/gli [...] new 3ae0d24de6 68: onsuccess: #484: 1: Success after binutils/gcc/linux/gli [...] new cdbcc06509 69: onsuccess: #485: 1: Success after binutils/gcc/linux/gdb [...] new 74a5df3382 70: onsuccess: #486: 1: Success after binutils/gcc/linux/gli [...] new 618fb26fb0 71: onsuccess: #487: 1: Success after binutils/gcc/linux/gdb [...] new a3a6d98257 72: onsuccess: #488: 1: Success after binutils/gcc/linux/gli [...] new a8836a624c 73: onsuccess: #489: 1: Success after binutils/gcc/glibc/gdb [...] new ba36805a27 74: onsuccess: #490: 1: Success after binutils/gcc/linux/gli [...] new 9149d72fa5 75: onsuccess: #491: 1: Success after binutils/gcc/linux/gdb [...] new 7ccd198715 76: onsuccess: #492: 1: Success after binutils/gcc/linux/gdb [...] new 304e3653ba 77: onsuccess: #493: 1: Success after binutils/gcc/linux/gdb [...] new 264e413f9f 78: onsuccess: #494: 1: Success after binutils/gcc/linux/gli [...] new 22156b8ed7 79: onsuccess: #495: 1: Success after binutils/gcc/linux/gli [...] new da85553bff 80: onsuccess: #496: 1: Success after binutils/gcc/linux/gli [...] new 7238e95434 81: onsuccess: #497: 1: Success after binutils/gcc/linux/gli [...] new 838811925d 82: onsuccess: #498: 1: Success after binutils/gcc/linux/gli [...] new c74645e41d 83: onsuccess: #499: 1: Success after binutils/gcc/linux/gdb [...] new 8a5f7d8ef3 84: onsuccess: #500: 1: Success after binutils/gcc/linux/gli [...] new 9f68af69a3 85: onsuccess: #501: 1: Success after binutils/gcc/linux/gli [...] new 2f024f0062 86: onsuccess: #503: 1: Success after binutils: 12 commits new 7bc02763d0 87: onsuccess: #505: 1: Success after glibc: 7 commits new e3d1df8921 88: onsuccess: #506: 1: Success after linux: 34 commits new 0e3ee5c260 89: onsuccess: #508: 1: Success after binutils: 12 commits new 92d76e6220 90: onsuccess: #510: 1: Success after glibc: 5 commits new 31dd9c9375 91: onsuccess: #511: 1: Success after linux: 27 commits new 5d6b502e67 92: onsuccess: #512: 1: Success after binutils/gcc/linux/gli [...] new 89bb44b443 93: onsuccess: #513: 1: Success after binutils/gcc/linux/gli [...] new 929b73f3d2 94: onsuccess: #514: 1: Success after binutils/gcc/linux/gdb [...] new 010c7a9268 95: onsuccess: #515: 1: Success after binutils/gcc/linux/gdb [...] new 0dcd440898 96: onsuccess: #516: 1: Success after binutils/gcc/linux/gli [...] new 2673b35d1e 97: onsuccess: #517: 1: Success after binutils/gcc/linux/gli [...] new dc90e0adcd 98: onsuccess: #518: 1: Success after binutils/gcc/linux/gli [...] new 7766f04292 99: onsuccess: #519: 1: Success after binutils/gcc/linux/gli [...] new 0d032ef7c5 100: onsuccess: #521: 1: Success after binutils: 10 commits new 0a5486bbbd 101: onsuccess: #524: 1: Success after binutils: 2 commits new fca2bc4066 102: onsuccess: #527: 1: Success after binutils: 5 commits new cb3ec0e347 103: onsuccess: #529: 1: Success after binutils/gcc/linux/gl [...] new d67cf0e4fd 104: onsuccess: #530: 1: Success after gcc: 7 commits new 76a142fee1 105: onsuccess: #531: 1: Success after binutils/gcc/linux/gd [...] new abef5c937d 106: onsuccess: #532: 1: Success after binutils/gcc/linux/gl [...] new 299a3f2f6f 107: onsuccess: #533: 1: Success after binutils/gcc/linux/gd [...] new 2968d67126 108: onsuccess: #534: 1: Success after binutils/gcc/linux/gd [...] new a7ae0fb04a 109: onsuccess: #535: 1: Success after binutils/gcc/linux/gd [...] new aa22619e05 110: onsuccess: #536: 1: Success after binutils/gcc/glibc/gd [...] new 9587975d63 111: onsuccess: #537: 1: Success after binutils/gcc/gdb: 69 commits new 819b36bd5e 112: onsuccess: #538: 1: Success after binutils/gcc/linux/gd [...] new c575b2233c 113: onsuccess: #539: 1: Success after binutils/gcc/linux/gd [...] new 0de0b1feed 114: onsuccess: #541: 1: Success after binutils/gcc/linux/gd [...] new 0c5e0df77f 115: onsuccess: #542: 1: Success after binutils/gcc/linux/gl [...] new dd2f60f82b 116: onsuccess: #543: 1: Success after binutils/gcc/linux/gl [...] new ab56093aae 117: onsuccess: #544: 1: Success after binutils/gcc/linux/gl [...] new be4821e31b 118: onsuccess: #545: 1: Success after binutils/gcc/linux/gd [...] new b60d21973d 119: onsuccess: #546: 1: Success after binutils/gcc/linux/gd [...] new bad92de5e4 120: onsuccess: #547: 1: Success after binutils/gcc/linux/gl [...] new 692e8dcb75 121: onsuccess: #548: 1: Success after binutils/gcc/linux/gd [...] new 659a4bdc88 122: onsuccess: #549: 1: Success after binutils/gcc/linux/gd [...] new e7d54e77c7 123: onsuccess: #550: 1: Success after binutils/gcc/linux/gd [...] new a35630bc74 124: onsuccess: #551: 1: Success after binutils/gcc/linux/gl [...] new c1a445f3cf 125: onsuccess: #552: 1: Success after binutils/gcc/linux/gl [...] new 097b8357e8 126: onsuccess: #553: 1: Success after binutils/gcc/linux/gl [...] new 8937ec58a8 127: onsuccess: #554: 1: Success after binutils/gcc/linux/gl [...] new a782e8a688 128: onsuccess: #555: 1: Success after binutils/gcc/linux/gd [...] new 750a760dfd 129: onsuccess: #556: 1: Success after binutils/gcc/linux/gd [...] new 1de2020f6c 130: onsuccess: #557: 1: Success after binutils/gcc/linux/gl [...] new 963ffe3324 131: onsuccess: #558: 1: Success after binutils/gcc/linux/gl [...] new 1606d19f8e 132: onsuccess: #559: 1: Success after binutils/gcc/linux/gd [...] new 31a0adb943 133: onsuccess: #560: 1: Success after binutils/gcc/linux/gl [...] new 404428e5f8 134: onsuccess: #561: 1: Success after binutils/gcc/linux/gd [...] new 81baf3fb24 135: onsuccess: #562: 1: Success after binutils/gcc/linux/gd [...] new 3a74f60b9a 136: onsuccess: #563: 1: Success after binutils/gcc/glibc/gd [...] new 03681b3e35 137: onsuccess: #564: 1: Success after binutils/gcc/linux/gl [...] new bae6299243 138: onsuccess: #565: 1: Success after binutils/gcc/linux/gl [...] new 60b0501c70 139: onsuccess: #566: 1: Success after binutils/gcc/linux/gl [...] new 29044edbd9 140: onsuccess: #567: 1: Success after binutils/gcc/linux/gl [...] new 2e31e3ded1 141: onsuccess: #568: 1: Success after binutils/gcc/linux/gd [...] new 20b509cfd7 142: onsuccess: #569: 1: Success after binutils/gcc/gdb: 46 commits new eb29263f7c 143: onsuccess: #570: 1: Success after binutils/gcc/linux/gd [...] new 5ed474cd86 144: onsuccess: #571: 1: Success after binutils/gcc/gdb: 28 commits new 5560616bd1 145: onsuccess: #572: 1: Success after binutils/gcc/gdb: 27 commits new 6e9d7b9219 146: onsuccess: #573: 1: Success after binutils/gcc/gdb: 11 commits new 084e94bdb8 147: onsuccess: #574: 1: Success after binutils/gcc/linux/gl [...] new ddbf7af160 148: onsuccess: #575: 1: Success after binutils/gcc/linux/gd [...] new cc436ed5d3 149: onsuccess: #576: 1: Success after binutils/gcc/linux/gd [...] new ef74a04229 150: onsuccess: #577: 1: Success after binutils/gcc/linux/gd [...] new bc816971bf 151: onsuccess: #579: 1: Success after binutils: 21 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 (7e2d96c92f) \ N -- N -- N refs/heads/linaro-local/ci/tcwg_gnu_native_check_binutil [...] 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 1776 -> 1680 bytes 02-prepare_abe/console.log.xz | Bin 2748 -> 2756 bytes 03-build_abe-binutils/console.log.xz | Bin 52608 -> 53352 bytes 04-build_abe-gcc/console.log.xz | Bin 238256 -> 238156 bytes 05-clean_sysroot/console.log.xz | Bin 316 -> 316 bytes 06-build_abe-linux/console.log.xz | Bin 8364 -> 8512 bytes 07-build_abe-glibc/console.log.xz | Bin 236492 -> 236916 bytes 08-build_abe-gdb/console.log.xz | Bin 52012 -> 51228 bytes 09-build_abe-dejagnu/console.log.xz | Bin 3840 -> 3824 bytes 10-build_abe-check_binutils/console.log.xz | Bin 2188 -> 2704 bytes 11-check_regression/console.log.xz | Bin 5660 -> 4708 bytes 11-check_regression/results.compare | 8 +- 11-check_regression/results.compare2 | 6 +- 12-update_baseline/console.log | 64 +++--- dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 2 +- mail/mail-subject.txt | 2 +- manifest.sh | 28 +-- sumfiles/binutils.log.xz | Bin 62656 -> 62756 bytes sumfiles/binutils.sum | 62 +++--- sumfiles/gas.log.xz | Bin 100352 -> 100508 bytes sumfiles/gas.sum | 272 +++++++++++------------ sumfiles/ld.log.xz | Bin 132176 -> 132292 bytes sumfiles/ld.sum | 344 ++++++++++++++--------------- 26 files changed, 395 insertions(+), 399 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

1 year, 10 months

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_gnu_cross_build/master-aarch64 updated (2c249afb12 -> 4c1be4c99c)

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 2c249afb12 305: force: #2006: 7: Success after gdb: 2 commits discards 7a1ed76f97 304: onsuccess: #2002: 7: Success after gcc: 4 commits discards 025b875193 303: onsuccess: #2001: 7: Success after binutils: 4 commits discards afd29a301f 302: onsuccess: #1999: 7: Success after binutils/gcc/glibc/g [...] discards bf8ab4d38d 301: onsuccess: #1998: 7: Success after binutils/gdb: 6 commits discards 03e0b91a36 300: onsuccess: #1997: 7: Success after binutils/gcc/linux/g [...] discards 5d2696796c 299: onsuccess: #1996: 7: Success after binutils/gcc/gdb: 10 [...] discards 03e529eda9 298: onsuccess: #1995: 7: Success after binutils/gcc/gdb: 7 commits discards 1060259996 297: onsuccess: #1994: 7: Success after binutils/gcc/gdb: 4 commits discards 5b4a31105d 296: onsuccess: #1993: 7: Success after binutils/gcc/linux/g [...] discards 1739c6d5ff 295: onsuccess: #1992: 7: Success after binutils/gdb: 18 commits discards f440e421c8 294: onsuccess: #1991: 7: Success after binutils/gdb: 6 commits discards d00b62143b 293: onsuccess: #1990: 7: Success after binutils/gcc/linux/g [...] discards 39c23ec210 292: onsuccess: #1989: 7: Success after binutils/gcc/gdb: 8 commits discards def3398ba3 291: onsuccess: #1988: 7: Success after binutils/gcc/gdb: 5 commits discards 9d95e134d8 290: onsuccess: #1987: 7: Success after gcc/linux: 26 commits discards 03d95bc575 289: onsuccess: #1986: 7: Success after binutils/gcc/linux/g [...] discards cc90549712 288: onsuccess: #1985: 7: Success after gcc: 17 commits discards f58755b1fe 287: onsuccess: #1984: 7: Success after binutils/gdb: 2 commits discards 972541fa25 286: onsuccess: #1983: 7: Success after binutils/gcc/gdb: 3 commits discards 183c051e44 285: onsuccess: #1982: 7: Success after binutils/gcc/gdb: 6 commits discards e2f2ab9ec2 284: onsuccess: #1981: 7: Success after gcc: 2 commits discards a4b2b4dc72 283: onsuccess: #1980: 7: Success after binutils/gcc/gdb: 6 commits discards 9435a90a8e 282: onsuccess: #1979: 7: Success after binutils/gcc/gdb: 18 [...] discards ac00246a4c 281: onsuccess: #1978: 7: Success after basepoints/gcc-13-48 [...] discards 305943ef5a 280: onsuccess: #1977: 7: Success after binutils/gdb: 18 commits discards f7395c29bc 279: onsuccess: #1976: 7: Success after binutils/gcc/gdb: 5 commits discards 7035b197d7 278: onsuccess: #1975: 7: Success after basepoints/gcc-13-48 [...] discards 6bb10a70f5 277: onsuccess: #1974: 7: Success after binutils/gdb: 4 commits discards 9e94f7ac3d 276: onsuccess: #1973: 7: Success after binutils/gcc/linux/g [...] discards 6612709a50 275: onsuccess: #1972: 7: Success after binutils/gcc/gdb: 23 [...] discards 0e50cffb9d 274: onsuccess: #1971: 7: Success after binutils/gcc/gdb: 21 [...] discards 35ac8272a4 273: onsuccess: #1970: 7: Success after binutils/gcc/gdb: 5 commits discards d7cc133527 272: onsuccess: #1969: 7: Success after binutils/gcc/linux/g [...] discards 75c6c6ee2b 271: onsuccess: #1968: 7: Success after binutils/gcc/linux/g [...] discards 7de79fafce 270: onsuccess: #1967: 7: Success after binutils/gcc/gdb: 71 [...] discards 7c96e30f7f 269: onsuccess: #1966: 7: Success after binutils/gcc/gdb: 43 [...] discards 17d6aab6c0 268: onsuccess: #1965: 7: Success after binutils/gcc/linux/g [...] discards 29819eec60 267: onsuccess: #1964: 7: Success after binutils/gcc/glibc/g [...] discards 63927c8095 266: onsuccess: #1963: 7: Success after binutils/gcc/gdb: 28 [...] discards d397d6825b 265: onsuccess: #1962: 7: Success after binutils/gcc/linux/g [...] discards 8e7670f590 264: onsuccess: #1961: 7: Success after binutils/gcc/glibc/g [...] discards b54577531c 263: onsuccess: #1960: 7: Success after binutils/gcc/linux/g [...] discards 6c46427c27 262: onsuccess: #1959: 7: Success after binutils/gcc/gdb/qem [...] discards 9386ad4f5b 261: onsuccess: #1958: 7: Success after binutils/gcc/gdb: 64 [...] discards d826563f49 260: onsuccess: #1957: 7: Success after binutils/gcc/gdb: 8 commits discards cf048a7176 259: onsuccess: #1956: 7: Success after gcc/linux/glibc/qemu [...] discards abdb312075 258: onsuccess: #1955: 7: Success after binutils/gcc/gdb: 7 commits discards 0e19185898 257: onsuccess: #1954: 7: Success after binutils/gcc/gdb: 7 commits discards 496d2c5c6b 256: onsuccess: #1953: 7: Success after binutils/gcc/linux/g [...] discards 48bf688e80 255: onsuccess: #1952: 7: Success after binutils/gcc/linux/g [...] discards 58fc8c1618 254: onsuccess: #1951: 7: Success after binutils/gcc/glibc/g [...] discards dc5fce6954 253: onsuccess: #1950: 7: Success after glibc: 2 commits discards bd9db73819 252: onsuccess: #1949: 7: Success after binutils/gcc/glibc/g [...] discards 1f88275f8c 251: onsuccess: #1948: 7: Success after v7.2.0-211-g562d4af3 [...] discards 016194d900 250: onsuccess: #1947: 7: Success after binutils/gcc/gdb: 5 commits discards 6112190c66 249: onsuccess: #1946: 7: Success after binutils/gcc/gdb: 5 commits discards 0b2d583084 248: onsuccess: #1945: 7: Success after binutils/gcc/gdb/qem [...] discards 2a09f7b682 247: onsuccess: #1944: 7: Success after gcc/linux: 109 commits discards 2cededd310 246: onsuccess: #1943: 7: Success after binutils/gdb: 6 commits discards f20c6b0300 245: onsuccess: #1942: 7: Success after binutils/gcc/gdb: 13 [...] discards 6d0ddafeba 244: onsuccess: #1941: 7: Success after binutils/gcc/linux/g [...] discards 96aff88f3d 243: onsuccess: #1940: 7: Success after binutils/gcc/linux/g [...] discards ae05e6f69a 242: onsuccess: #1939: 7: Success after binutils/gcc/gdb/qem [...] discards 9325439d56 241: onsuccess: #1938: 7: Success after binutils/gcc/linux/g [...] discards 37add7e626 240: onsuccess: #1937: 7: Success after binutils/gcc/linux/g [...] discards bf5c7988a8 239: onsuccess: #1936: 7: Success after binutils/gcc/linux/g [...] discards 09bbd6837e 238: onsuccess: #1935: 7: Success after binutils/gcc/gdb/qem [...] discards 6435de4261 237: onsuccess: #1934: 7: Success after basepoints/gcc-13-47 [...] discards ce83375626 236: onsuccess: #1933: 7: Success after binutils/gcc/linux/g [...] discards 932789154d 235: onsuccess: #1932: 7: Success after binutils/gcc/linux/g [...] discards fd0e69fb3b 234: onsuccess: #1931: 7: Success after binutils/gcc/gdb: 22 [...] discards 1b94b4285c 233: onsuccess: #1930: 7: Success after binutils/gcc/linux/g [...] discards 26a7d43c1e 232: onsuccess: #1929: 7: Success after binutils/gcc/linux/g [...] discards 6507f712ea 231: onsuccess: #1928: 3: Success after gcc: 8 commits discards b488369c4f 230: force: #1927: 3: Failure after basepoints/gcc-13-4618-g [...] discards 1b18361c98 229: force: #1926: 7: Success after gcc: 7 commits discards 753f268745 228: onsuccess: #1914: 7: Success after gdb-12-branchpoint-3 [...] discards e18dc31879 227: onsuccess: #1906: 7: Success after binutils: 9 commits discards c6b545c543 226: onsuccess: #1904: 7: Success after binutils/gcc/gdb: 38 [...] discards 1a46eea660 225: onsuccess: #1903: 7: Success after binutils/gcc/linux/g [...] discards 578819e340 224: onsuccess: #1902: 7: Success after binutils/gcc/linux/g [...] discards 89ef3a66a1 223: onsuccess: #1901: 7: Success after basepoints/gcc-13-45 [...] discards f5f559b375 222: onsuccess: #1900: 7: Success after binutils/gcc/linux/g [...] discards d78f06f3ce 221: onsuccess: #1899: 7: Success after binutils/gcc/gdb: 15 [...] discards e29b9494ec 220: onsuccess: #1898: 7: Success after binutils/linux/glibc [...] discards 15f61da5b9 219: onsuccess: #1897: 7: Success after binutils/gcc/gdb: 8 commits discards ac5ef50012 218: onsuccess: #1896: 7: Success after binutils/gcc/linux/g [...] discards c380b71a61 217: onsuccess: #1893: 7: Success after binutils/gcc/gdb: 10 [...] discards 90ebdb2e9f 216: onsuccess: #1892: 7: Success after binutils/gdb: 2 commits discards e9b511ed94 215: onsuccess: #1891: 7: Success after binutils/gcc/linux/g [...] discards 6d81f7937e 214: onsuccess: #1890: 7: Success after binutils/gcc/glibc/g [...] discards 52ba6b84d3 213: onsuccess: #1889: 7: Success after gcc: 5 commits discards a9e3852c32 212: onsuccess: #1888: 7: Success after binutils/gcc/glibc/g [...] discards 408be0718e 211: onsuccess: #1887: 7: Success after binutils/gcc/linux/g [...] discards 17eb6ce577 210: onsuccess: #1868: 7: Success after binutils: 7 commits discards d3a43c8efc 209: onsuccess: #1866: 7: Success after binutils/gcc/gdb/qem [...] discards 4ffd4429b4 208: onsuccess: #1865: 7: Success after linux: 12 commits discards 6d15012695 207: onsuccess: #1862: 7: Success after binutils: 4 commits discards 6f4d639c7b 206: onsuccess: #1860: 7: Success after gcc: 2 commits discards bac98c05ce 205: onsuccess: #1859: 7: Success after gcc: 3 commits new 46ca07c197 205: onsuccess: #1859: 7: Success after gcc: 3 commits new d52544cbd3 206: onsuccess: #1860: 7: Success after gcc: 2 commits new b76cd0bd13 207: onsuccess: #1862: 7: Success after binutils: 4 commits new 79b5344c3e 208: onsuccess: #1865: 7: Success after linux: 12 commits new 45ad8ef6ef 209: onsuccess: #1866: 7: Success after binutils/gcc/gdb/qem [...] new 16ce1134c4 210: onsuccess: #1868: 7: Success after binutils: 7 commits new e8156329e3 211: onsuccess: #1887: 7: Success after binutils/gcc/linux/g [...] new 92213d524a 212: onsuccess: #1888: 7: Success after binutils/gcc/glibc/g [...] new 9c929e9e5c 213: onsuccess: #1889: 7: Success after gcc: 5 commits new 56798982a0 214: onsuccess: #1890: 7: Success after binutils/gcc/glibc/g [...] new 78553024f3 215: onsuccess: #1891: 7: Success after binutils/gcc/linux/g [...] new 1b24f84f96 216: onsuccess: #1892: 7: Success after binutils/gdb: 2 commits new 246fd0c542 217: onsuccess: #1893: 7: Success after binutils/gcc/gdb: 10 [...] new 07fc612170 218: onsuccess: #1896: 7: Success after binutils/gcc/linux/g [...] new 20e1be10e2 219: onsuccess: #1897: 7: Success after binutils/gcc/gdb: 8 commits new 05647aaf1c 220: onsuccess: #1898: 7: Success after binutils/linux/glibc [...] new fdccbb462e 221: onsuccess: #1899: 7: Success after binutils/gcc/gdb: 15 [...] new 57e9e3b0b4 222: onsuccess: #1900: 7: Success after binutils/gcc/linux/g [...] new ec7f17e96c 223: onsuccess: #1901: 7: Success after basepoints/gcc-13-45 [...] new 50a379e0a8 224: onsuccess: #1902: 7: Success after binutils/gcc/linux/g [...] new a9f0e97f22 225: onsuccess: #1903: 7: Success after binutils/gcc/linux/g [...] new dc8133fb61 226: onsuccess: #1904: 7: Success after binutils/gcc/gdb: 38 [...] new 903a5ac748 227: onsuccess: #1906: 7: Success after binutils: 9 commits new baf66f15b6 228: onsuccess: #1914: 7: Success after gdb-12-branchpoint-3 [...] new 5495ecf8c0 229: force: #1926: 7: Success after gcc: 7 commits new 2cbc6b1804 230: force: #1927: 3: Failure after basepoints/gcc-13-4618-g [...] new 6c30f5b173 231: onsuccess: #1928: 3: Success after gcc: 8 commits new 5dbdbc681c 232: onsuccess: #1929: 7: Success after binutils/gcc/linux/g [...] new 2792cd8540 233: onsuccess: #1930: 7: Success after binutils/gcc/linux/g [...] new d3957c0827 234: onsuccess: #1931: 7: Success after binutils/gcc/gdb: 22 [...] new 249f62c553 235: onsuccess: #1932: 7: Success after binutils/gcc/linux/g [...] new f437823544 236: onsuccess: #1933: 7: Success after binutils/gcc/linux/g [...] new 2918fb58f6 237: onsuccess: #1934: 7: Success after basepoints/gcc-13-47 [...] new b9e42a0592 238: onsuccess: #1935: 7: Success after binutils/gcc/gdb/qem [...] new 26ccad8ef4 239: onsuccess: #1936: 7: Success after binutils/gcc/linux/g [...] new 86890d7cb6 240: onsuccess: #1937: 7: Success after binutils/gcc/linux/g [...] new f3cd146c6b 241: onsuccess: #1938: 7: Success after binutils/gcc/linux/g [...] new 7a58a1250d 242: onsuccess: #1939: 7: Success after binutils/gcc/gdb/qem [...] new 4c5cc02c5c 243: onsuccess: #1940: 7: Success after binutils/gcc/linux/g [...] new 8208d73cf0 244: onsuccess: #1941: 7: Success after binutils/gcc/linux/g [...] new 9e84d8cab9 245: onsuccess: #1942: 7: Success after binutils/gcc/gdb: 13 [...] new c4ae240a4a 246: onsuccess: #1943: 7: Success after binutils/gdb: 6 commits new 6e2676e4ff 247: onsuccess: #1944: 7: Success after gcc/linux: 109 commits new 2112e562f3 248: onsuccess: #1945: 7: Success after binutils/gcc/gdb/qem [...] new 28397c6f61 249: onsuccess: #1946: 7: Success after binutils/gcc/gdb: 5 commits new 301efc8b9d 250: onsuccess: #1947: 7: Success after binutils/gcc/gdb: 5 commits new 25e02ef6e7 251: onsuccess: #1948: 7: Success after v7.2.0-211-g562d4af3 [...] new 9e83da319c 252: onsuccess: #1949: 7: Success after binutils/gcc/glibc/g [...] new dced5517cb 253: onsuccess: #1950: 7: Success after glibc: 2 commits new f95f53bdf6 254: onsuccess: #1951: 7: Success after binutils/gcc/glibc/g [...] new b406447d7a 255: onsuccess: #1952: 7: Success after binutils/gcc/linux/g [...] new 58d5f9bb99 256: onsuccess: #1953: 7: Success after binutils/gcc/linux/g [...] new 65855d3647 257: onsuccess: #1954: 7: Success after binutils/gcc/gdb: 7 commits new 11099b9d84 258: onsuccess: #1955: 7: Success after binutils/gcc/gdb: 7 commits new 00f38687c0 259: onsuccess: #1956: 7: Success after gcc/linux/glibc/qemu [...] new 868c5c5c6c 260: onsuccess: #1957: 7: Success after binutils/gcc/gdb: 8 commits new 99de18cd59 261: onsuccess: #1958: 7: Success after binutils/gcc/gdb: 64 [...] new 65a06279b6 262: onsuccess: #1959: 7: Success after binutils/gcc/gdb/qem [...] new 6cddbaa829 263: onsuccess: #1960: 7: Success after binutils/gcc/linux/g [...] new 162e04eacb 264: onsuccess: #1961: 7: Success after binutils/gcc/glibc/g [...] new 7757525844 265: onsuccess: #1962: 7: Success after binutils/gcc/linux/g [...] new 03e14760ec 266: onsuccess: #1963: 7: Success after binutils/gcc/gdb: 28 [...] new da07fff7d4 267: onsuccess: #1964: 7: Success after binutils/gcc/glibc/g [...] new e99c979d12 268: onsuccess: #1965: 7: Success after binutils/gcc/linux/g [...] new d86573e9bd 269: onsuccess: #1966: 7: Success after binutils/gcc/gdb: 43 [...] new b650936c3e 270: onsuccess: #1967: 7: Success after binutils/gcc/gdb: 71 [...] new 40947ab95d 271: onsuccess: #1968: 7: Success after binutils/gcc/linux/g [...] new b8a17f47dd 272: onsuccess: #1969: 7: Success after binutils/gcc/linux/g [...] new 43a7e613a3 273: onsuccess: #1970: 7: Success after binutils/gcc/gdb: 5 commits new 994dd322fb 274: onsuccess: #1971: 7: Success after binutils/gcc/gdb: 21 [...] new 345ef9784f 275: onsuccess: #1972: 7: Success after binutils/gcc/gdb: 23 [...] new f28911ad8a 276: onsuccess: #1973: 7: Success after binutils/gcc/linux/g [...] new 2a0465bb7d 277: onsuccess: #1974: 7: Success after binutils/gdb: 4 commits new cc107d4c87 278: onsuccess: #1975: 7: Success after basepoints/gcc-13-48 [...] new 2af207c855 279: onsuccess: #1976: 7: Success after binutils/gcc/gdb: 5 commits new 1f16746fbb 280: onsuccess: #1977: 7: Success after binutils/gdb: 18 commits new 51c2c02f19 281: onsuccess: #1978: 7: Success after basepoints/gcc-13-48 [...] new 13afff1a10 282: onsuccess: #1979: 7: Success after binutils/gcc/gdb: 18 [...] new 7db7af6925 283: onsuccess: #1980: 7: Success after binutils/gcc/gdb: 6 commits new f3bbc5f9bd 284: onsuccess: #1981: 7: Success after gcc: 2 commits new 6f5384acef 285: onsuccess: #1982: 7: Success after binutils/gcc/gdb: 6 commits new 9470238c22 286: onsuccess: #1983: 7: Success after binutils/gcc/gdb: 3 commits new 5cb14f24ee 287: onsuccess: #1984: 7: Success after binutils/gdb: 2 commits new 69c8de141b 288: onsuccess: #1985: 7: Success after gcc: 17 commits new da0112d327 289: onsuccess: #1986: 7: Success after binutils/gcc/linux/g [...] new 1c84e6dff9 290: onsuccess: #1987: 7: Success after gcc/linux: 26 commits new 999c6c8d29 291: onsuccess: #1988: 7: Success after binutils/gcc/gdb: 5 commits new 66884c7ce3 292: onsuccess: #1989: 7: Success after binutils/gcc/gdb: 8 commits new 93dccd0661 293: onsuccess: #1990: 7: Success after binutils/gcc/linux/g [...] new cbf47fdb66 294: onsuccess: #1991: 7: Success after binutils/gdb: 6 commits new 66f05ccc98 295: onsuccess: #1992: 7: Success after binutils/gdb: 18 commits new b723852010 296: onsuccess: #1993: 7: Success after binutils/gcc/linux/g [...] new aa62c14fc6 297: onsuccess: #1994: 7: Success after binutils/gcc/gdb: 4 commits new f81974ee92 298: onsuccess: #1995: 7: Success after binutils/gcc/gdb: 7 commits new a9472f21da 299: onsuccess: #1996: 7: Success after binutils/gcc/gdb: 10 [...] new dded69c6b3 300: onsuccess: #1997: 7: Success after binutils/gcc/linux/g [...] new 2377794ad3 301: onsuccess: #1998: 7: Success after binutils/gdb: 6 commits new c49e986f65 302: onsuccess: #1999: 7: Success after binutils/gcc/glibc/g [...] new 25795ce68d 303: onsuccess: #2001: 7: Success after binutils: 4 commits new 38049d7a0b 304: onsuccess: #2002: 7: Success after gcc: 4 commits new 0da47ca43e 305: force: #2006: 7: Success after gdb: 2 commits new 4c1be4c99c 306: force: #2007: 5: Failure after gdb-13-branchpoint-245-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 (2c249afb12) \ 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 1744 -> 1676 bytes 02-prepare_abe/console.log.xz | Bin 2772 -> 2760 bytes 04-build_abe-binutils/console.log.xz | Bin 32092 -> 32168 bytes 05-build_abe-stage1/console.log.xz | Bin 74012 -> 73892 bytes 07-build_abe-linux/console.log.xz | Bin 8520 -> 8528 bytes 08-build_abe-glibc/console.log.xz | Bin 245432 -> 245148 bytes 09-build_abe-stage2/console.log.xz | Bin 205564 -> 204928 bytes 10-build_abe-gdb/console.log.xz | Bin 39572 -> 36604 bytes 11-build_abe-qemu/console.log.xz | Bin 31504 -> 0 bytes 12-check_regression/console.log.xz | Bin 2952 -> 3724 bytes 12-check_regression/jira-body.txt | 2 +- 12-check_regression/mail-body.txt | 10 +- 12-check_regression/mail-subject.txt | 2 +- 12-check_regression/results.regressions | 4 + 12-check_regression/trigger-bisect | 2 + 12-check_regression/trigger-notify | 0 13-update_baseline/console.log | 42 +- dashboard/dashboard-generate.sh | 2 +- .../squad-vs-first/score/results-functional.json | 1 - git/gdb_rev | 2 +- jenkins/jira-status.draft | 4 + jenkins/mail-body.draft | 1072 ++++++++++++++++++++ jenkins/mail-recipients.draft | 1 + jenkins/mail-subject.draft | 1 + jenkins/notify.sh | 3 + mail/jira-body.txt | 2 +- mail/mail-body.txt | 10 +- mail/mail-subject.txt | 2 +- manifest.sh | 23 +- results | 8 +- 30 files changed, 1141 insertions(+), 52 deletions(-) delete mode 100644 11-build_abe-qemu/console.log.xz create mode 100644 12-check_regression/results.regressions create mode 100644 12-check_regression/trigger-bisect create mode 100644 12-check_regression/trigger-notify delete mode 100644 dashboard/squad-vs-first/score/results-functional.json create mode 100644 jenkins/jira-status.draft create mode 100644 jenkins/mail-body.draft create mode 100644 jenkins/mail-recipients.draft create mode 100644 jenkins/mail-subject.draft create mode 100755 jenkins/notify.sh -- To stop receiving notification emails like this one, please contact the administrator of this repository.

1 year, 10 months

[toolchain/ci/interesting-commits] branch master updated (1642b672 -> d00f1469)

by tcwg-buildslave

This is an automated email from the git hooks/post-receive script. "tcwg-buildslave pushed a change to branch master in repository toolchain/ci/interesting-commits. from 1642b672 Add entry 3b6cac2b44b384cd2091eaeaebeb3478c253a25d from https [...] new d00f1469 Add entry de7d7cb58e6209ed11c31f635545ee2ee6ded307 from https [...] 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: gdb/gdb-13-branchpoint-245-gde7d7cb58e6 | 1 + .../tcwg_gnu_cross_build/master-aarch64/build_url | 2 +- .../tcwg_gnu_cross_build/master-aarch64/last_good | 1 + .../master-aarch64/summary.txt | 1 + .../tcwg_gnu_cross_build/status.txt | 47 ++++++++++++++++++++++ 5 files changed, 51 insertions(+), 1 deletion(-) create mode 120000 gdb/gdb-13-branchpoint-245-gde7d7cb58e6 copy {gcc/sha1/1214196da79aabbe5c14ed36e5a28012e141f04c => gdb/sha1/de7d7cb58e6209 [...] create mode 100644 gdb/sha1/de7d7cb58e6209ed11c31f635545ee2ee6ded307/tcwg_gnu_cros [...] create mode 100644 gdb/sha1/de7d7cb58e6209ed11c31f635545ee2ee6ded307/tcwg_gnu_cros [...] create mode 100644 gdb/sha1/de7d7cb58e6209ed11c31f635545ee2ee6ded307/tcwg_gnu_cros [...] -- To stop receiving notification emails like this one, please contact the administrator of this repository.

1 year, 10 months

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_gnu_native_check_binutils/master-aarch64 updated (e3a664aa57 -> 18a709f2d0)

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_native_check_binutils/master-aarch64 in repository toolchain/ci/base-artifacts. discards e3a664aa57 146: onsuccess: #680: 1: Success after binutils: 20 commits discards 7c7d1b1d61 145: onsuccess: #678: 1: Success after binutils/gcc/linux/gd [...] discards 6ba59bddfe 144: onsuccess: #677: 1: Success after binutils/gcc/linux/gd [...] discards 8619ba4bcc 143: onsuccess: #676: 1: Success after binutils/gcc/linux/gd [...] discards 486408aa02 142: onsuccess: #675: 1: Success after binutils/gcc/linux/gl [...] discards 65c849dee5 141: onsuccess: #674: 1: Success after binutils/gcc/gdb: 12 commits discards 3b29445a25 140: onsuccess: #673: 1: Success after binutils/gcc/gdb: 26 commits discards f639100b66 139: onsuccess: #672: 1: Success after binutils/gcc/gdb: 28 commits discards 0bd6397141 138: onsuccess: #671: 1: Success after binutils/gcc/linux/gd [...] discards 422b50de4b 137: onsuccess: #670: 1: Success after binutils/gcc/gdb: 46 commits discards ea40a0b166 136: onsuccess: #669: 1: Success after binutils/gcc/linux/gd [...] discards 8e371f6d04 135: onsuccess: #668: 1: Success after binutils/gcc/linux/gl [...] discards 8fba766d80 134: onsuccess: #667: 1: Success after binutils/gcc/linux/gl [...] discards d4be070983 133: onsuccess: #666: 1: Success after binutils/gcc/linux/gl [...] discards eb26c987b9 132: onsuccess: #665: 1: Success after binutils/gcc/linux/gl [...] discards c4e117b6aa 131: onsuccess: #664: 1: Success after binutils/gcc/glibc/gd [...] discards 15988d86c8 130: onsuccess: #663: 1: Success after binutils/gcc/linux/gd [...] discards cf196708fa 129: onsuccess: #662: 1: Success after binutils/gcc/linux/gd [...] discards a6219741a0 128: onsuccess: #661: 1: Success after binutils/gcc/linux/gl [...] discards 9f806cb3db 127: onsuccess: #660: 1: Success after binutils/gcc/linux/gd [...] discards c08e40ac0f 126: onsuccess: #659: 1: Success after binutils/gcc/linux/gl [...] discards d8296c1ef8 125: onsuccess: #658: 1: Success after linux: 3224 commits discards e6c5ea8b8e 124: onsuccess: #657: 1: Success after glibc: 2 commits discards 3e19a9132e 123: onsuccess: #655: 1: Success after binutils: 22 commits discards dc2387ba88 122: onsuccess: #653: 1: Success after binutils/gcc/linux/gd [...] discards e160ed7833 121: onsuccess: #652: 1: Success after binutils/gcc/linux/gd [...] discards 02b116bb56 120: onsuccess: #651: 1: Success after binutils/gcc/linux/gl [...] discards db3354c7c5 119: onsuccess: #650: 1: Success after binutils/gcc/linux/gl [...] discards 6e94eb0ee7 118: onsuccess: #649: 1: Success after binutils/gcc/linux/gl [...] discards fd8e30140d 117: onsuccess: #648: 1: Success after binutils/gcc/linux/gl [...] discards 0458a97b53 116: onsuccess: #647: 1: Success after linux: 3 commits discards 50025cee18 115: onsuccess: #645: 1: Success after binutils: 27 commits discards 9ec640ea06 114: onsuccess: #643: 1: Success after binutils/gcc/linux/gd [...] discards 7c0d3262b4 113: onsuccess: #642: 1: Success after binutils/gcc/linux/gd [...] discards 89791161ab 112: onsuccess: #641: 1: Success after binutils/gcc/linux/gl [...] discards b058a2cfbf 111: onsuccess: #640: 1: Success after binutils/gcc/linux/gd [...] discards c77e621dc1 110: onsuccess: #639: 1: Success after binutils/gcc/linux/gd [...] discards 64c1107172 109: onsuccess: #638: 1: Success after binutils/gcc/linux/gl [...] discards d96a84a3a6 108: onsuccess: #637: 1: Success after binutils/gcc/linux/gl [...] discards 252f0a42fe 107: onsuccess: #636: 1: Success after binutils/gcc/linux/gl [...] discards b4ad50f298 106: onsuccess: #635: 1: Success after binutils/gcc/linux/gd [...] discards 78cb0f1e56 105: onsuccess: #631: 1: Success after binutils/gcc/linux/gd [...] discards 7017510f4a 104: onsuccess: #630: 1: Success after binutils/gcc/linux/gd [...] discards f61ca132a8 103: onsuccess: #629: 1: Success after binutils/gcc/gdb: 68 commits discards 93736de6ff 102: onsuccess: #628: 1: Success after binutils/gcc/glibc/gd [...] discards 0fa9c25012 101: onsuccess: #627: 1: Success after binutils/gcc/linux/gd [...] discards a5ac8b3f72 100: onsuccess: #625: 1: Success after binutils/gcc/linux/gd [...] discards 46313bd71a 99: onsuccess: #624: 1: Success after binutils/gcc/linux/gli [...] discards 23b9a33908 98: onsuccess: #623: 1: Success after binutils/gcc/linux/gdb [...] discards 142a126e9a 97: onsuccess: #622: 1: Success after binutils/gcc/gdb: 8 commits discards f812f8c02f 96: onsuccess: #621: 1: Success after binutils/gcc/linux/gli [...] discards b2295d49a8 95: onsuccess: #619: 1: Success after binutils: 5 commits discards 32d45b8c1f 94: onsuccess: #616: 1: Success after binutils: 2 commits discards 2a7ae2d91f 93: onsuccess: #613: 1: Success after binutils: 19 commits discards aceaf17e17 92: onsuccess: #611: 1: Success after binutils/gcc/linux/gli [...] discards 89f7aafc04 91: onsuccess: #610: 1: Success after binutils/gcc/linux/gli [...] discards a34de59d07 90: onsuccess: #606: 1: Success after binutils/gcc/linux/gli [...] discards ec2ddca829 89: onsuccess: #605: 1: Success after binutils/gcc/linux/gdb [...] discards db735d4968 88: onsuccess: #604: 1: Success after binutils/gcc/linux/gdb [...] discards 32d12d1e46 87: onsuccess: #603: 1: Success after binutils/gcc/linux/gli [...] discards d99c062f59 86: onsuccess: #602: 1: Success after binutils/gcc/linux/gli [...] discards b14ab985f2 85: onsuccess: #601: 1: Success after binutils/gcc/linux/gli [...] discards 4f97a98e74 84: onsuccess: #600: 1: Success after binutils/gcc/linux/gli [...] discards e75ae5a934 83: onsuccess: #599: 1: Success after binutils/gcc/linux/gli [...] discards 725a08d5d5 82: onsuccess: #598: 1: Success after binutils/gcc/linux/gli [...] discards 8d6d9efaca 81: onsuccess: #597: 1: Success after binutils/gcc/linux/gdb [...] discards 96b0c7d5bc 80: onsuccess: #596: 1: Success after binutils/gcc/linux/gli [...] discards 651c8a0958 79: onsuccess: #595: 1: Success after binutils/gcc/linux/gli [...] discards 02c1721c89 78: onsuccess: #594: 1: Success after binutils/gcc/linux/gli [...] discards cb242a3735 77: onsuccess: #593: 1: Success after binutils/gcc/linux/gli [...] discards a9e0906c10 76: onsuccess: #592: 1: Success after linux: 63 commits discards ecafc0d231 75: onsuccess: #591: 1: Success after gcc: 25 commits discards a3c1dea9ab 74: onsuccess: #590: 1: Success after binutils: 16 commits discards 8da31dae6f 73: onsuccess: #588: 1: Success after binutils/gcc/linux/gdb [...] discards edf604bed0 72: onsuccess: #587: 1: Success after binutils/gcc/linux/gdb [...] discards aa3d7e1066 71: onsuccess: #586: 1: Success after binutils/gcc/linux/gdb [...] discards 483d11fcea 70: onsuccess: #585: 1: Success after binutils/gcc/linux/gli [...] discards b088e6ca6b 69: onsuccess: #584: 1: Success after binutils/gcc/glibc/gdb [...] discards 07cca11f4c 68: onsuccess: #583: 1: Success after binutils/gcc/linux/gli [...] discards fdf9d69bcb 67: onsuccess: #582: 1: Success after binutils/gcc/linux/gdb [...] discards 5a8d48e2be 66: onsuccess: #581: 1: Success after binutils/gcc/linux/gli [...] discards 092fd71bd4 65: onsuccess: #580: 1: Success after binutils/gcc/linux/gdb [...] discards 1843ff8f7c 64: onsuccess: #579: 1: Success after binutils/gcc/linux/gli [...] discards e29394183b 63: onsuccess: #577: 1: Success after binutils/gcc/linux/gli [...] discards 6361406038 62: onsuccess: #576: 1: Success after binutils/gcc/linux/gdb [...] discards b5c4e400e1 61: onsuccess: #575: 1: Success after binutils/gcc/linux/gli [...] discards 373ce88b9d 60: onsuccess: #574: 1: Success after binutils/gcc/linux/gli [...] discards b84d5f9daa 59: onsuccess: #573: 1: Success after binutils/gcc/linux/gli [...] discards 1cc806c9f8 58: onsuccess: #572: 1: Success after binutils/gcc/linux/gli [...] discards 3b12ea8e31 57: onsuccess: #571: 1: Success after binutils/gcc/linux/gli [...] discards 11811e428f 56: onsuccess: #570: 1: Success after binutils/gcc/linux/gli [...] discards 45196b2792 55: onsuccess: #569: 1: Success after binutils/gcc/linux/gli [...] discards 771aa4f550 54: onsuccess: #568: 1: Success after binutils/gcc/linux/gli [...] discards 5659ec54a4 53: onsuccess: #567: 1: Success after binutils/gcc/linux/gdb [...] discards 40c25a2952 52: onsuccess: #566: 1: Success after binutils/gcc/linux/gli [...] discards 6a721db68c 51: onsuccess: #565: 1: Success after binutils/gcc/linux/gli [...] discards 92d4fff944 50: onsuccess: #564: 1: Success after binutils/gcc/linux/gli [...] discards 6bb6193565 49: onsuccess: #562: 1: Success after binutils: 9 commits discards ee6533bf87 48: onsuccess: #559: 1: Success after binutils: 6 commits discards 49166b8758 47: onsuccess: #556: 1: Success after binutils: 12 commits discards ca993b6423 46: onsuccess: #554: 1: Success after binutils/gcc/linux/gdb [...] new 721b5a1f08 46: onsuccess: #554: 1: Success after binutils/gcc/linux/gdb [...] new 68a5911c7b 47: onsuccess: #556: 1: Success after binutils: 12 commits new 728798791b 48: onsuccess: #559: 1: Success after binutils: 6 commits new c26ce52bea 49: onsuccess: #562: 1: Success after binutils: 9 commits new 6959097cb6 50: onsuccess: #564: 1: Success after binutils/gcc/linux/gli [...] new 21e138ece8 51: onsuccess: #565: 1: Success after binutils/gcc/linux/gli [...] new ea59048046 52: onsuccess: #566: 1: Success after binutils/gcc/linux/gli [...] new 3223bc2b4a 53: onsuccess: #567: 1: Success after binutils/gcc/linux/gdb [...] new e30a685a23 54: onsuccess: #568: 1: Success after binutils/gcc/linux/gli [...] new d15320f39d 55: onsuccess: #569: 1: Success after binutils/gcc/linux/gli [...] new 1784645a4b 56: onsuccess: #570: 1: Success after binutils/gcc/linux/gli [...] new 4b06031da8 57: onsuccess: #571: 1: Success after binutils/gcc/linux/gli [...] new eccb025b41 58: onsuccess: #572: 1: Success after binutils/gcc/linux/gli [...] new d5246d636e 59: onsuccess: #573: 1: Success after binutils/gcc/linux/gli [...] new 92bb0f9403 60: onsuccess: #574: 1: Success after binutils/gcc/linux/gli [...] new cc630e367c 61: onsuccess: #575: 1: Success after binutils/gcc/linux/gli [...] new 8123faa841 62: onsuccess: #576: 1: Success after binutils/gcc/linux/gdb [...] new 17a48b2a20 63: onsuccess: #577: 1: Success after binutils/gcc/linux/gli [...] new a55455dcdf 64: onsuccess: #579: 1: Success after binutils/gcc/linux/gli [...] new a201ca3ed4 65: onsuccess: #580: 1: Success after binutils/gcc/linux/gdb [...] new 0a945cc33a 66: onsuccess: #581: 1: Success after binutils/gcc/linux/gli [...] new e65d2a16da 67: onsuccess: #582: 1: Success after binutils/gcc/linux/gdb [...] new 8ff9721896 68: onsuccess: #583: 1: Success after binutils/gcc/linux/gli [...] new 4b748715d9 69: onsuccess: #584: 1: Success after binutils/gcc/glibc/gdb [...] new 3fd9b09edc 70: onsuccess: #585: 1: Success after binutils/gcc/linux/gli [...] new f153beb287 71: onsuccess: #586: 1: Success after binutils/gcc/linux/gdb [...] new 8a48110330 72: onsuccess: #587: 1: Success after binutils/gcc/linux/gdb [...] new 53c96cd336 73: onsuccess: #588: 1: Success after binutils/gcc/linux/gdb [...] new 4204720b7c 74: onsuccess: #590: 1: Success after binutils: 16 commits new 939932ee26 75: onsuccess: #591: 1: Success after gcc: 25 commits new df1f45d273 76: onsuccess: #592: 1: Success after linux: 63 commits new b96ce86723 77: onsuccess: #593: 1: Success after binutils/gcc/linux/gli [...] new 579e65e55d 78: onsuccess: #594: 1: Success after binutils/gcc/linux/gli [...] new 818a7cbfaa 79: onsuccess: #595: 1: Success after binutils/gcc/linux/gli [...] new 03efc4cb14 80: onsuccess: #596: 1: Success after binutils/gcc/linux/gli [...] new b6070bbd65 81: onsuccess: #597: 1: Success after binutils/gcc/linux/gdb [...] new a05966f8ee 82: onsuccess: #598: 1: Success after binutils/gcc/linux/gli [...] new 02a38c7f3d 83: onsuccess: #599: 1: Success after binutils/gcc/linux/gli [...] new 63478f7239 84: onsuccess: #600: 1: Success after binutils/gcc/linux/gli [...] new 98cc22b7ef 85: onsuccess: #601: 1: Success after binutils/gcc/linux/gli [...] new 1367b4cd36 86: onsuccess: #602: 1: Success after binutils/gcc/linux/gli [...] new 125d8bc03a 87: onsuccess: #603: 1: Success after binutils/gcc/linux/gli [...] new ebbeeff726 88: onsuccess: #604: 1: Success after binutils/gcc/linux/gdb [...] new 732f77cac9 89: onsuccess: #605: 1: Success after binutils/gcc/linux/gdb [...] new 28582690a0 90: onsuccess: #606: 1: Success after binutils/gcc/linux/gli [...] new 9ccb34a38c 91: onsuccess: #610: 1: Success after binutils/gcc/linux/gli [...] new fffff68001 92: onsuccess: #611: 1: Success after binutils/gcc/linux/gli [...] new fd79567e88 93: onsuccess: #613: 1: Success after binutils: 19 commits new 0ef936ab5c 94: onsuccess: #616: 1: Success after binutils: 2 commits new 36472efe20 95: onsuccess: #619: 1: Success after binutils: 5 commits new d512ef80c1 96: onsuccess: #621: 1: Success after binutils/gcc/linux/gli [...] new 580c8b4c62 97: onsuccess: #622: 1: Success after binutils/gcc/gdb: 8 commits new f6e088ded4 98: onsuccess: #623: 1: Success after binutils/gcc/linux/gdb [...] new 9659383b2c 99: onsuccess: #624: 1: Success after binutils/gcc/linux/gli [...] new 65678afdba 100: onsuccess: #625: 1: Success after binutils/gcc/linux/gd [...] new 851ef620d2 101: onsuccess: #627: 1: Success after binutils/gcc/linux/gd [...] new 2c414bf964 102: onsuccess: #628: 1: Success after binutils/gcc/glibc/gd [...] new ef099971cb 103: onsuccess: #629: 1: Success after binutils/gcc/gdb: 68 commits new f13a125818 104: onsuccess: #630: 1: Success after binutils/gcc/linux/gd [...] new 51aeb8f6f4 105: onsuccess: #631: 1: Success after binutils/gcc/linux/gd [...] new 3114bf3deb 106: onsuccess: #635: 1: Success after binutils/gcc/linux/gd [...] new bfb1c85a7d 107: onsuccess: #636: 1: Success after binutils/gcc/linux/gl [...] new 65b6839e50 108: onsuccess: #637: 1: Success after binutils/gcc/linux/gl [...] new 05aab08eb5 109: onsuccess: #638: 1: Success after binutils/gcc/linux/gl [...] new 0e95f749e0 110: onsuccess: #639: 1: Success after binutils/gcc/linux/gd [...] new 26a87686c2 111: onsuccess: #640: 1: Success after binutils/gcc/linux/gd [...] new d02ad50a81 112: onsuccess: #641: 1: Success after binutils/gcc/linux/gl [...] new dc70348ad9 113: onsuccess: #642: 1: Success after binutils/gcc/linux/gd [...] new 036ba8d9de 114: onsuccess: #643: 1: Success after binutils/gcc/linux/gd [...] new 47f0a16643 115: onsuccess: #645: 1: Success after binutils: 27 commits new bfe3d125e3 116: onsuccess: #647: 1: Success after linux: 3 commits new 7feff0d903 117: onsuccess: #648: 1: Success after binutils/gcc/linux/gl [...] new a093d08966 118: onsuccess: #649: 1: Success after binutils/gcc/linux/gl [...] new 6615806ecf 119: onsuccess: #650: 1: Success after binutils/gcc/linux/gl [...] new bacec76722 120: onsuccess: #651: 1: Success after binutils/gcc/linux/gl [...] new 5b5df3e6ae 121: onsuccess: #652: 1: Success after binutils/gcc/linux/gd [...] new c53ebd08a9 122: onsuccess: #653: 1: Success after binutils/gcc/linux/gd [...] new a7e259723f 123: onsuccess: #655: 1: Success after binutils: 22 commits new c2edc36c5f 124: onsuccess: #657: 1: Success after glibc: 2 commits new 0834b8bc17 125: onsuccess: #658: 1: Success after linux: 3224 commits new 655a48c582 126: onsuccess: #659: 1: Success after binutils/gcc/linux/gl [...] new 2f379aea8b 127: onsuccess: #660: 1: Success after binutils/gcc/linux/gd [...] new 4ba7473c1f 128: onsuccess: #661: 1: Success after binutils/gcc/linux/gl [...] new 42c4486ef1 129: onsuccess: #662: 1: Success after binutils/gcc/linux/gd [...] new 09db655321 130: onsuccess: #663: 1: Success after binutils/gcc/linux/gd [...] new a3e29a8b6e 131: onsuccess: #664: 1: Success after binutils/gcc/glibc/gd [...] new 064fbe1d7f 132: onsuccess: #665: 1: Success after binutils/gcc/linux/gl [...] new 812cb5a7db 133: onsuccess: #666: 1: Success after binutils/gcc/linux/gl [...] new 10af84c926 134: onsuccess: #667: 1: Success after binutils/gcc/linux/gl [...] new f9acb75826 135: onsuccess: #668: 1: Success after binutils/gcc/linux/gl [...] new fb8d2bed67 136: onsuccess: #669: 1: Success after binutils/gcc/linux/gd [...] new 689e2a56ef 137: onsuccess: #670: 1: Success after binutils/gcc/gdb: 46 commits new d183ce1969 138: onsuccess: #671: 1: Success after binutils/gcc/linux/gd [...] new 6487db7e4b 139: onsuccess: #672: 1: Success after binutils/gcc/gdb: 28 commits new 606b95512d 140: onsuccess: #673: 1: Success after binutils/gcc/gdb: 26 commits new e7693cd140 141: onsuccess: #674: 1: Success after binutils/gcc/gdb: 12 commits new 24cbee938f 142: onsuccess: #675: 1: Success after binutils/gcc/linux/gl [...] new 42193bf965 143: onsuccess: #676: 1: Success after binutils/gcc/linux/gd [...] new f766b36254 144: onsuccess: #677: 1: Success after binutils/gcc/linux/gd [...] new aa0be89123 145: onsuccess: #678: 1: Success after binutils/gcc/linux/gd [...] new aad8710867 146: onsuccess: #680: 1: Success after binutils: 20 commits new 18a709f2d0 147: onsuccess: #681: 1: Success after gcc: 6 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 (e3a664aa57) \ N -- N -- N refs/heads/linaro-local/ci/tcwg_gnu_native_check_binutil [...] 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 1728 -> 1724 bytes 02-prepare_abe/console.log.xz | Bin 2744 -> 2756 bytes 03-build_abe-binutils/console.log.xz | Bin 40448 -> 39720 bytes 04-build_abe-gcc/console.log.xz | Bin 214840 -> 214444 bytes 05-clean_sysroot/console.log.xz | Bin 312 -> 312 bytes 06-build_abe-linux/console.log.xz | Bin 8532 -> 8524 bytes 07-build_abe-glibc/console.log.xz | Bin 245124 -> 245220 bytes 08-build_abe-gdb/console.log.xz | Bin 39832 -> 39536 bytes 09-build_abe-dejagnu/console.log.xz | Bin 3904 -> 3888 bytes 10-build_abe-check_binutils/console.log.xz | Bin 2300 -> 2220 bytes 11-check_regression/console.log.xz | Bin 4676 -> 4796 bytes 11-check_regression/results.compare | 8 +- 11-check_regression/results.compare2 | 6 +- 12-update_baseline/console.log | 40 ++-- dashboard/dashboard-generate.sh | 2 +- git/gcc_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 2 +- mail/mail-subject.txt | 2 +- manifest.sh | 12 +- sumfiles/binutils.log.xz | Bin 63228 -> 63144 bytes sumfiles/binutils.sum | 62 +++--- sumfiles/gas.log.xz | Bin 83904 -> 83968 bytes sumfiles/gas.sum | 272 +++++++++++------------ sumfiles/ld.log.xz | Bin 122412 -> 122400 bytes sumfiles/ld.sum | 342 ++++++++++++++--------------- 26 files changed, 376 insertions(+), 376 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

1 year, 10 months

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_gnu_cross_check_gcc/master-aarch64 updated (fcf720e9a1 -> 73d59edcd6)

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 fcf720e9a1 291: onsuccess: #2539: 1: Success after binutils/gcc/glibc/g [...] discards 50f8b24e74 290: onsuccess: #2538: 1: Success after binutils/gcc/glibc/g [...] discards 122fd026cc 289: onsuccess: #2537: 1: Success after binutils/gcc/linux/g [...] discards 3f2d0655a2 288: onsuccess: #2536: 1: Success after binutils/gcc/linux/g [...] discards aadfa70fc3 287: onsuccess: #2535: 1: Success after binutils/gcc/gdb: 15 [...] discards 39016b6684 286: onsuccess: #2534: 1: Success after binutils/gcc/gdb: 4 commits discards c074a96a5a 285: onsuccess: #2533: 1: Success after gcc/linux: 13 commits discards bba67fe243 284: onsuccess: #2532: 1: Success after binutils/gdb: 10 commits discards 6e71817370 283: onsuccess: #2531: 1: Success after binutils/gdb: 16 commits discards 50fea6e26c 282: onsuccess: #2530: 1: Success after binutils/gcc/gdb: 3 commits discards e539b527e8 281: onsuccess: #2529: 1: Success after binutils/gcc/linux/g [...] discards 1e461128a5 280: onsuccess: #2528: 1: Success after binutils/gcc/gdb: 7 commits discards 997656d501 279: onsuccess: #2527: 1: Success after basepoints/gcc-13-49 [...] discards f844cb7cba 278: onsuccess: #2526: 1: Success after binutils/gcc/linux/g [...] discards 18a00eac18 277: onsuccess: #2525: 1: Success after gcc/linux: 60 commits discards 2005f96504 276: onsuccess: #2524: 1: Success after binutils/gdb: 2 commits discards c2e7aa661e 275: onsuccess: #2523: 1: Success after basepoints/gcc-13-49 [...] discards ea0f36b1ad 274: onsuccess: #2522: 1: Success after binutils/gcc/gdb: 8 commits discards 2ce087790f 273: onsuccess: #2521: 1: Success after gcc: 2 commits discards b6eeeab8e0 272: onsuccess: #2520: 1: Success after basepoints/gcc-13-49 [...] discards 3149727d67 271: onsuccess: #2519: 1: Success after binutils/gcc/gdb: 23 [...] discards 0cab340467 270: onsuccess: #2518: 1: Success after binutils/gcc/gdb: 19 [...] discards d15bfa1e23 269: onsuccess: #2517: 1: Success after binutils/gcc/gdb: 3 commits discards 9d8e4d8783 268: onsuccess: #2516: 1: Success after binutils/gcc/gdb: 3 commits discards 39ea29da8a 267: onsuccess: #2515: 1: Success after binutils/gdb: 4 commits discards c8bd4754ce 266: onsuccess: #2514: 1: Success after binutils/gcc/linux/g [...] discards 0df4782418 265: onsuccess: #2513: 1: Success after binutils/gdb: 4 commits discards 4469f6439c 264: onsuccess: #2512: 1: Success after binutils/gcc/gdb: 21 [...] discards d1aaedd2eb 263: onsuccess: #2511: 1: Success after binutils/gdb: 16 commits discards 31d909a0d0 262: onsuccess: #2510: 1: Success after binutils/gcc/gdb: 10 [...] discards 2b408f0d30 261: onsuccess: #2509: 1: Success after binutils/gcc/gdb: 3 commits discards 6b39e2115e 260: onsuccess: #2508: 1: Success after binutils/gcc/linux/g [...] discards a8f63bd69f 259: onsuccess: #2507: 1: Success after binutils/gcc/gdb: 49 [...] discards 20237bf7b5 258: onsuccess: #2506: 1: Success after binutils/gcc/gdb: 49 [...] discards f165ad8b59 257: onsuccess: #2505: 1: Success after binutils/gcc/gdb: 47 [...] discards ae16dc2e87 256: onsuccess: #2504: 1: Success after binutils/gcc/linux/g [...] discards e046e53212 255: onsuccess: #2503: 1: Success after binutils/gcc/glibc/g [...] discards d1ba732df9 254: onsuccess: #2502: 1: Success after binutils/gcc/gdb: 37 [...] discards 2f0c986daf 253: onsuccess: #2501: 1: Success after binutils/gcc/linux/g [...] discards 9c66e65062 252: onsuccess: #2500: 1: Success after binutils/gcc/linux/g [...] discards 8f3ff19081 251: onsuccess: #2499: 1: Success after binutils/gcc/gdb/qem [...] discards e80100dbc6 250: onsuccess: #2498: 1: Success after binutils/gcc/gdb: 68 [...] discards aa09842b46 249: onsuccess: #2497: 1: Success after binutils/gcc/gdb: 16 [...] discards 57bcd44272 248: onsuccess: #2496: 1: Success after binutils/gcc/glibc/g [...] discards d10c157e90 247: onsuccess: #2495: 1: Success after binutils/gcc/linux/g [...] discards 3249b5363c 246: onsuccess: #2494: 1: Success after binutils/gcc/gdb: 6 commits discards aa5e75899d 245: onsuccess: #2493: 1: Success after binutils/gcc/gdb: 9 commits discards 0157fc1104 244: onsuccess: #2492: 1: Success after binutils/gcc/linux/g [...] discards cedb745025 243: onsuccess: #2491: 1: Success after binutils/gcc/linux/g [...] discards d1570a2e9c 242: onsuccess: #2490: 1: Success after binutils/gcc/gdb: 16 [...] discards 236984374f 241: onsuccess: #2489: 1: Success after binutils/gcc/glibc/g [...] discards 92dbd4e470 240: onsuccess: #2488: 1: Success after gcc/qemu: 3 commits discards 5c6ed1f8fb 239: onsuccess: #2487: 1: Success after binutils/gcc/gdb: 5 commits discards 058e457723 238: onsuccess: #2486: 1: Success after binutils/gcc/gdb: 5 commits discards 9cc7936440 237: onsuccess: #2485: 1: Success after binutils/gcc/gdb/qem [...] discards 7061851527 236: onsuccess: #2484: 1: Success after gcc: 2 commits discards 9365880877 235: onsuccess: #2483: 1: Success after linux: 108 commits discards 168eac6b41 234: onsuccess: #2482: 1: Success after binutils/gdb: 18 commits discards 5d30145f4e 233: onsuccess: #2481: 1: Success after binutils/gcc/gdb/qem [...] discards d9b275d630 232: onsuccess: #2480: 1: Success after binutils/gcc/linux/g [...] discards 92ee1b81ed 231: onsuccess: #2479: 1: Success after binutils/gcc/gdb/qem [...] discards 7cb17c9d2d 230: onsuccess: #2477: 1: Success after binutils/gcc/linux/g [...] discards 7e16282fe8 229: onsuccess: #2476: 1: Success after binutils/gcc/linux/g [...] discards f87b7ce69e 228: onsuccess: #2475: 1: Success after binutils/gcc/gdb/qem [...] discards c71371e630 227: onsuccess: #2474: 1: Success after gcc: 2 commits discards 60ceaeac7b 226: onsuccess: #2473: 1: Success after binutils/gcc/linux/g [...] discards cc6e391cba 225: onsuccess: #2472: 1: Success after gcc/linux: 532 commits discards 1468956be4 224: onsuccess: #2471: 1: Success after binutils/gcc/gdb: 34 [...] discards ef18608cde 223: onsuccess: #2470: 1: Success after binutils/gcc/linux/g [...] discards 711b506070 222: onsuccess: #2469: 1: Success after binutils/gcc/linux/g [...] discards 0c96af92d9 221: onsuccess: #2467: 1: Success after binutils: 3 commits discards d3ffeda9b9 220: onsuccess: #2465: 1: Success after linux: 572 commits discards 539f39be98 219: onsuccess: #2463: 1: Success after binutils: 3 commits discards e891fef04e 218: onsuccess: #2461: 1: Success after linux: 916 commits discards f326c67564 217: onsuccess: #2459: 1: Success after binutils: 3 commits discards 7efeab237e 216: onsuccess: #2457: 1: Success after linux: 1736 commits discards ecf3a980ab 215: onsuccess: #2455: 1: Success after binutils: 3 commits discards db6b5a4a79 214: onsuccess: #2453: 1: Success after binutils/gcc/glibc/g [...] discards 6d859b522b 213: onsuccess: #2452: 1: Success after binutils/gcc/gdb: 22 [...] discards c2289992b1 212: onsuccess: #2451: 1: Success after binutils/gcc/linux/g [...] discards d894f81788 211: onsuccess: #2450: 1: Success after gcc/linux: 7 commits discards 7a4f627824 210: onsuccess: #2449: 1: Success after binutils/gcc/gdb: 6 commits discards 0d641ae831 209: onsuccess: #2448: 1: Success after binutils/gcc/linux/g [...] discards c1427388a0 208: onsuccess: #2447: 1: Success after binutils/gcc/gdb: 14 [...] discards 130893c8e0 207: onsuccess: #2446: 1: Success after binutils/gcc/linux/g [...] discards bb5e215eb4 206: onsuccess: #2445: 1: Success after binutils/gcc/glibc/g [...] discards 0b51e1863c 205: onsuccess: #2444: 1: Success after binutils/gcc/linux/g [...] discards 3e329f6507 204: onsuccess: #2435: 1: Success after linux: 3 commits discards b853b2337c 203: onsuccess: #2433: 1: Success after binutils: 27 commits discards 83fc16e07f 202: onsuccess: #2431: 1: Success after linux: 944 commits discards ba3108f2e3 201: onsuccess: #2430: 1: Success after glibc: 26 commits discards fc2494ab9b 200: onsuccess: #2427: 1: Success after binutils: 274 commits discards 019960a344 199: onsuccess: #2363: 1: Success after binutils/gcc/linux/g [...] discards 43f663483e 198: onsuccess: #2360: 1: Success after binutils/gcc/linux/g [...] discards 5d7ef7e379 197: onsuccess: #2348: 1: Success after linux: 190 commits discards c805bbbfbc 196: onsuccess: #2342: 1: Success after binutils/gcc/gdb: 41 [...] discards 0467cb0982 195: onsuccess: #2341: 1: Success after binutils/gcc/linux/g [...] discards 7caee73481 194: onsuccess: #2340: 1: Success after binutils/gcc/linux/g [...] discards 3f58c3f517 193: onsuccess: #2339: 1: Success after binutils/gcc/glibc/g [...] discards 720ec55c0d 192: onsuccess: #2338: 1: Success after binutils/gcc/linux/g [...] discards 718e9049da 191: onsuccess: #2331: 1: Success after gcc/qemu: 90 commits new 39746e001c 191: onsuccess: #2331: 1: Success after gcc/qemu: 90 commits new 3eb3999a1e 192: onsuccess: #2338: 1: Success after binutils/gcc/linux/g [...] new 4e57fc74e6 193: onsuccess: #2339: 1: Success after binutils/gcc/glibc/g [...] new 4edd9b3505 194: onsuccess: #2340: 1: Success after binutils/gcc/linux/g [...] new 642049d331 195: onsuccess: #2341: 1: Success after binutils/gcc/linux/g [...] new 542c883e16 196: onsuccess: #2342: 1: Success after binutils/gcc/gdb: 41 [...] new b66b198a64 197: onsuccess: #2348: 1: Success after linux: 190 commits new 82f97c442c 198: onsuccess: #2360: 1: Success after binutils/gcc/linux/g [...] new 51326fe916 199: onsuccess: #2363: 1: Success after binutils/gcc/linux/g [...] new 0a5246bddf 200: onsuccess: #2427: 1: Success after binutils: 274 commits new 0213010688 201: onsuccess: #2430: 1: Success after glibc: 26 commits new 67c978fd76 202: onsuccess: #2431: 1: Success after linux: 944 commits new 7dc2294257 203: onsuccess: #2433: 1: Success after binutils: 27 commits new 25716abcc3 204: onsuccess: #2435: 1: Success after linux: 3 commits new 57981c11d9 205: onsuccess: #2444: 1: Success after binutils/gcc/linux/g [...] new bd57c428ae 206: onsuccess: #2445: 1: Success after binutils/gcc/glibc/g [...] new 4e52e63248 207: onsuccess: #2446: 1: Success after binutils/gcc/linux/g [...] new e4d551ab6e 208: onsuccess: #2447: 1: Success after binutils/gcc/gdb: 14 [...] new 39a558dd33 209: onsuccess: #2448: 1: Success after binutils/gcc/linux/g [...] new 76e5dd6fe4 210: onsuccess: #2449: 1: Success after binutils/gcc/gdb: 6 commits new c80b152ec1 211: onsuccess: #2450: 1: Success after gcc/linux: 7 commits new 37b153404e 212: onsuccess: #2451: 1: Success after binutils/gcc/linux/g [...] new 509a43e5eb 213: onsuccess: #2452: 1: Success after binutils/gcc/gdb: 22 [...] new 29532f4edc 214: onsuccess: #2453: 1: Success after binutils/gcc/glibc/g [...] new 6e840b1d98 215: onsuccess: #2455: 1: Success after binutils: 3 commits new c888bc302b 216: onsuccess: #2457: 1: Success after linux: 1736 commits new fb6c51ae60 217: onsuccess: #2459: 1: Success after binutils: 3 commits new 4eead1ca7d 218: onsuccess: #2461: 1: Success after linux: 916 commits new 4c63669704 219: onsuccess: #2463: 1: Success after binutils: 3 commits new 041a8069a8 220: onsuccess: #2465: 1: Success after linux: 572 commits new 02fef3eac6 221: onsuccess: #2467: 1: Success after binutils: 3 commits new feb0097b47 222: onsuccess: #2469: 1: Success after binutils/gcc/linux/g [...] new 45e65dc6d5 223: onsuccess: #2470: 1: Success after binutils/gcc/linux/g [...] new 4b1a176bc9 224: onsuccess: #2471: 1: Success after binutils/gcc/gdb: 34 [...] new 177cd99e72 225: onsuccess: #2472: 1: Success after gcc/linux: 532 commits new e78d05745d 226: onsuccess: #2473: 1: Success after binutils/gcc/linux/g [...] new d03b084633 227: onsuccess: #2474: 1: Success after gcc: 2 commits new 85e2f0eff3 228: onsuccess: #2475: 1: Success after binutils/gcc/gdb/qem [...] new 5c66369e66 229: onsuccess: #2476: 1: Success after binutils/gcc/linux/g [...] new 64be448da1 230: onsuccess: #2477: 1: Success after binutils/gcc/linux/g [...] new e7d7de3fc8 231: onsuccess: #2479: 1: Success after binutils/gcc/gdb/qem [...] new 7972415f67 232: onsuccess: #2480: 1: Success after binutils/gcc/linux/g [...] new c9553dc524 233: onsuccess: #2481: 1: Success after binutils/gcc/gdb/qem [...] new c1e59d2d75 234: onsuccess: #2482: 1: Success after binutils/gdb: 18 commits new 54d97c952e 235: onsuccess: #2483: 1: Success after linux: 108 commits new acc762c0c3 236: onsuccess: #2484: 1: Success after gcc: 2 commits new 67c23cbfcc 237: onsuccess: #2485: 1: Success after binutils/gcc/gdb/qem [...] new 1601ebf9da 238: onsuccess: #2486: 1: Success after binutils/gcc/gdb: 5 commits new a54261ef5e 239: onsuccess: #2487: 1: Success after binutils/gcc/gdb: 5 commits new 316b94016b 240: onsuccess: #2488: 1: Success after gcc/qemu: 3 commits new 4a5131dc12 241: onsuccess: #2489: 1: Success after binutils/gcc/glibc/g [...] new 0e4f8f02c1 242: onsuccess: #2490: 1: Success after binutils/gcc/gdb: 16 [...] new ff2f681e06 243: onsuccess: #2491: 1: Success after binutils/gcc/linux/g [...] new b4ca569580 244: onsuccess: #2492: 1: Success after binutils/gcc/linux/g [...] new c4b05b2374 245: onsuccess: #2493: 1: Success after binutils/gcc/gdb: 9 commits new c9610334f9 246: onsuccess: #2494: 1: Success after binutils/gcc/gdb: 6 commits new 3cd9a001d0 247: onsuccess: #2495: 1: Success after binutils/gcc/linux/g [...] new 4d0d722313 248: onsuccess: #2496: 1: Success after binutils/gcc/glibc/g [...] new e7f5b21624 249: onsuccess: #2497: 1: Success after binutils/gcc/gdb: 16 [...] new 79b773dabc 250: onsuccess: #2498: 1: Success after binutils/gcc/gdb: 68 [...] new 74ae4c49e2 251: onsuccess: #2499: 1: Success after binutils/gcc/gdb/qem [...] new c1ee0a92ce 252: onsuccess: #2500: 1: Success after binutils/gcc/linux/g [...] new 16a24eb9a6 253: onsuccess: #2501: 1: Success after binutils/gcc/linux/g [...] new ab6a51e051 254: onsuccess: #2502: 1: Success after binutils/gcc/gdb: 37 [...] new f299c19117 255: onsuccess: #2503: 1: Success after binutils/gcc/glibc/g [...] new bfaeb4ecc6 256: onsuccess: #2504: 1: Success after binutils/gcc/linux/g [...] new e21878af63 257: onsuccess: #2505: 1: Success after binutils/gcc/gdb: 47 [...] new d4df59df55 258: onsuccess: #2506: 1: Success after binutils/gcc/gdb: 49 [...] new 37694fad9c 259: onsuccess: #2507: 1: Success after binutils/gcc/gdb: 49 [...] new c52f73715c 260: onsuccess: #2508: 1: Success after binutils/gcc/linux/g [...] new e514c9a0ea 261: onsuccess: #2509: 1: Success after binutils/gcc/gdb: 3 commits new d9228fd456 262: onsuccess: #2510: 1: Success after binutils/gcc/gdb: 10 [...] new 17d6019d99 263: onsuccess: #2511: 1: Success after binutils/gdb: 16 commits new a3cd2587cb 264: onsuccess: #2512: 1: Success after binutils/gcc/gdb: 21 [...] new f75933d2e9 265: onsuccess: #2513: 1: Success after binutils/gdb: 4 commits new 8b466f58f5 266: onsuccess: #2514: 1: Success after binutils/gcc/linux/g [...] new 256e5e681f 267: onsuccess: #2515: 1: Success after binutils/gdb: 4 commits new c7f7b1acc2 268: onsuccess: #2516: 1: Success after binutils/gcc/gdb: 3 commits new cf2f9d85f2 269: onsuccess: #2517: 1: Success after binutils/gcc/gdb: 3 commits new 422dced050 270: onsuccess: #2518: 1: Success after binutils/gcc/gdb: 19 [...] new 784d6e2a9c 271: onsuccess: #2519: 1: Success after binutils/gcc/gdb: 23 [...] new fe662f82ee 272: onsuccess: #2520: 1: Success after basepoints/gcc-13-49 [...] new dd909e7488 273: onsuccess: #2521: 1: Success after gcc: 2 commits new d57378817e 274: onsuccess: #2522: 1: Success after binutils/gcc/gdb: 8 commits new 26ac3f7188 275: onsuccess: #2523: 1: Success after basepoints/gcc-13-49 [...] new 7622376188 276: onsuccess: #2524: 1: Success after binutils/gdb: 2 commits new d64f407a19 277: onsuccess: #2525: 1: Success after gcc/linux: 60 commits new 81138a6d26 278: onsuccess: #2526: 1: Success after binutils/gcc/linux/g [...] new 6739b673fa 279: onsuccess: #2527: 1: Success after basepoints/gcc-13-49 [...] new 6de113cd0b 280: onsuccess: #2528: 1: Success after binutils/gcc/gdb: 7 commits new 7d012b155a 281: onsuccess: #2529: 1: Success after binutils/gcc/linux/g [...] new e58d159300 282: onsuccess: #2530: 1: Success after binutils/gcc/gdb: 3 commits new 4d5d78b4b7 283: onsuccess: #2531: 1: Success after binutils/gdb: 16 commits new 873bcf9360 284: onsuccess: #2532: 1: Success after binutils/gdb: 10 commits new 371a6613e8 285: onsuccess: #2533: 1: Success after gcc/linux: 13 commits new 9c2e227193 286: onsuccess: #2534: 1: Success after binutils/gcc/gdb: 4 commits new ecb799fa64 287: onsuccess: #2535: 1: Success after binutils/gcc/gdb: 15 [...] new 076ea2d195 288: onsuccess: #2536: 1: Success after binutils/gcc/linux/g [...] new 1c3d7a8381 289: onsuccess: #2537: 1: Success after binutils/gcc/linux/g [...] new 520c86db6e 290: onsuccess: #2538: 1: Success after binutils/gcc/glibc/g [...] new 1101ce9904 291: onsuccess: #2539: 1: Success after binutils/gcc/glibc/g [...] new 73d59edcd6 292: onsuccess: #2541: 1: Success after binutils: 13 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 (fcf720e9a1) \ 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 -> 1948 bytes 02-prepare_abe/console.log.xz | Bin 2764 -> 2768 bytes 03-build_abe-binutils/console.log.xz | Bin 32200 -> 32096 bytes 04-build_abe-stage1/console.log.xz | Bin 73888 -> 73828 bytes 06-build_abe-linux/console.log.xz | Bin 8376 -> 8512 bytes 07-build_abe-glibc/console.log.xz | Bin 245352 -> 245212 bytes 08-build_abe-stage2/console.log.xz | Bin 205516 -> 205224 bytes 09-build_abe-gdb/console.log.xz | Bin 39580 -> 39684 bytes 10-build_abe-qemu/console.log.xz | Bin 31448 -> 31596 bytes 11-build_abe-dejagnu/console.log.xz | Bin 3884 -> 3892 bytes 12-build_abe-check_gcc/console.log.xz | Bin 3184 -> 3184 bytes 13-check_regression/console.log.xz | Bin 6612 -> 5472 bytes 13-check_regression/extra-bisect-params | 2 +- 13-check_regression/fails.sum | 8 +- 13-check_regression/mail-body.txt | 98 +- 13-check_regression/results.compare | 20 +- 13-check_regression/results.compare2 | 49 +- 13-check_regression/results.regressions | 20 +- 14-update_baseline/console.log | 66 +- dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 100 +- mail/mail-subject.txt | 2 +- manifest.sh | 31 +- results | 20 +- sumfiles/g++.log.xz | Bin 3437944 -> 3436068 bytes sumfiles/g++.sum | 8 +- sumfiles/gcc.log.xz | Bin 3020864 -> 3009160 bytes sumfiles/gcc.sum | 4964 +++++++++++++++---------------- sumfiles/gfortran.log.xz | Bin 1036156 -> 1036752 bytes sumfiles/gfortran.sum | 2 +- sumfiles/libatomic.log.xz | Bin 2292 -> 2288 bytes sumfiles/libatomic.sum | 2 +- sumfiles/libgomp.log.xz | Bin 214632 -> 214684 bytes sumfiles/libgomp.sum | 2 +- sumfiles/libitm.log.xz | Bin 2692 -> 2696 bytes sumfiles/libitm.sum | 2 +- sumfiles/libstdc++.log.xz | Bin 433644 -> 425784 bytes sumfiles/libstdc++.sum | 2 +- 40 files changed, 2631 insertions(+), 2773 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

1 year, 10 months

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_gnu_native_check_binutils/master-aarch64 updated (f2cd1f52a1 -> e3a664aa57)

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_native_check_binutils/master-aarch64 in repository toolchain/ci/base-artifacts. discards f2cd1f52a1 145: onsuccess: #678: 1: Success after binutils/gcc/linux/gd [...] discards cb15b048ed 144: onsuccess: #677: 1: Success after binutils/gcc/linux/gd [...] discards bc7a615966 143: onsuccess: #676: 1: Success after binutils/gcc/linux/gd [...] discards 3694218832 142: onsuccess: #675: 1: Success after binutils/gcc/linux/gl [...] discards 62d614f3a3 141: onsuccess: #674: 1: Success after binutils/gcc/gdb: 12 commits discards adfe3749da 140: onsuccess: #673: 1: Success after binutils/gcc/gdb: 26 commits discards 68ada2c2e5 139: onsuccess: #672: 1: Success after binutils/gcc/gdb: 28 commits discards 6bae02b5e3 138: onsuccess: #671: 1: Success after binutils/gcc/linux/gd [...] discards fd177ce42c 137: onsuccess: #670: 1: Success after binutils/gcc/gdb: 46 commits discards 2718cda0c8 136: onsuccess: #669: 1: Success after binutils/gcc/linux/gd [...] discards 5635483c3d 135: onsuccess: #668: 1: Success after binutils/gcc/linux/gl [...] discards 4c5efbf4f7 134: onsuccess: #667: 1: Success after binutils/gcc/linux/gl [...] discards aaa313a164 133: onsuccess: #666: 1: Success after binutils/gcc/linux/gl [...] discards 63b0500b84 132: onsuccess: #665: 1: Success after binutils/gcc/linux/gl [...] discards c98a2a63c6 131: onsuccess: #664: 1: Success after binutils/gcc/glibc/gd [...] discards cd1168d4e4 130: onsuccess: #663: 1: Success after binutils/gcc/linux/gd [...] discards af11031253 129: onsuccess: #662: 1: Success after binutils/gcc/linux/gd [...] discards 735398df09 128: onsuccess: #661: 1: Success after binutils/gcc/linux/gl [...] discards 17a9bb6aa9 127: onsuccess: #660: 1: Success after binutils/gcc/linux/gd [...] discards a2d4f18751 126: onsuccess: #659: 1: Success after binutils/gcc/linux/gl [...] discards 5fe039e08c 125: onsuccess: #658: 1: Success after linux: 3224 commits discards fb0af920a7 124: onsuccess: #657: 1: Success after glibc: 2 commits discards 8918313cf7 123: onsuccess: #655: 1: Success after binutils: 22 commits discards fe56b04382 122: onsuccess: #653: 1: Success after binutils/gcc/linux/gd [...] discards d3bba2b4be 121: onsuccess: #652: 1: Success after binutils/gcc/linux/gd [...] discards 8b761f08cd 120: onsuccess: #651: 1: Success after binutils/gcc/linux/gl [...] discards 22d0c9e642 119: onsuccess: #650: 1: Success after binutils/gcc/linux/gl [...] discards 2de0fe41f3 118: onsuccess: #649: 1: Success after binutils/gcc/linux/gl [...] discards 03d2032d07 117: onsuccess: #648: 1: Success after binutils/gcc/linux/gl [...] discards df21068f4f 116: onsuccess: #647: 1: Success after linux: 3 commits discards fc2329c483 115: onsuccess: #645: 1: Success after binutils: 27 commits discards a7681de2ab 114: onsuccess: #643: 1: Success after binutils/gcc/linux/gd [...] discards ae37f9d3e2 113: onsuccess: #642: 1: Success after binutils/gcc/linux/gd [...] discards 778667ae60 112: onsuccess: #641: 1: Success after binutils/gcc/linux/gl [...] discards fd5773cfca 111: onsuccess: #640: 1: Success after binutils/gcc/linux/gd [...] discards 938d6f91d7 110: onsuccess: #639: 1: Success after binutils/gcc/linux/gd [...] discards 1072b0fffe 109: onsuccess: #638: 1: Success after binutils/gcc/linux/gl [...] discards 0a77cf6b8b 108: onsuccess: #637: 1: Success after binutils/gcc/linux/gl [...] discards 0d7f673869 107: onsuccess: #636: 1: Success after binutils/gcc/linux/gl [...] discards 9b16a2fbec 106: onsuccess: #635: 1: Success after binutils/gcc/linux/gd [...] discards 1310d3a8cd 105: onsuccess: #631: 1: Success after binutils/gcc/linux/gd [...] discards 3b9811006b 104: onsuccess: #630: 1: Success after binutils/gcc/linux/gd [...] discards 4f16087134 103: onsuccess: #629: 1: Success after binutils/gcc/gdb: 68 commits discards aed9a15de3 102: onsuccess: #628: 1: Success after binutils/gcc/glibc/gd [...] discards 89219f13de 101: onsuccess: #627: 1: Success after binutils/gcc/linux/gd [...] discards 2f2738f3a4 100: onsuccess: #625: 1: Success after binutils/gcc/linux/gd [...] discards 84734e4b4f 99: onsuccess: #624: 1: Success after binutils/gcc/linux/gli [...] discards f954100c6c 98: onsuccess: #623: 1: Success after binutils/gcc/linux/gdb [...] discards 04281d6743 97: onsuccess: #622: 1: Success after binutils/gcc/gdb: 8 commits discards 100f242b1f 96: onsuccess: #621: 1: Success after binutils/gcc/linux/gli [...] discards 8f2b0139dd 95: onsuccess: #619: 1: Success after binutils: 5 commits discards 019a27e5ea 94: onsuccess: #616: 1: Success after binutils: 2 commits discards 16be040e23 93: onsuccess: #613: 1: Success after binutils: 19 commits discards 5028f82d5d 92: onsuccess: #611: 1: Success after binutils/gcc/linux/gli [...] discards 058151573a 91: onsuccess: #610: 1: Success after binutils/gcc/linux/gli [...] discards 7999b115e6 90: onsuccess: #606: 1: Success after binutils/gcc/linux/gli [...] discards 117edc9b3e 89: onsuccess: #605: 1: Success after binutils/gcc/linux/gdb [...] discards 2a1bf84807 88: onsuccess: #604: 1: Success after binutils/gcc/linux/gdb [...] discards 06ca2afb87 87: onsuccess: #603: 1: Success after binutils/gcc/linux/gli [...] discards 4a66352a88 86: onsuccess: #602: 1: Success after binutils/gcc/linux/gli [...] discards f29fcaa496 85: onsuccess: #601: 1: Success after binutils/gcc/linux/gli [...] discards 949e09d80c 84: onsuccess: #600: 1: Success after binutils/gcc/linux/gli [...] discards b6d835b4ca 83: onsuccess: #599: 1: Success after binutils/gcc/linux/gli [...] discards e77be7132a 82: onsuccess: #598: 1: Success after binutils/gcc/linux/gli [...] discards d788dc3bc7 81: onsuccess: #597: 1: Success after binutils/gcc/linux/gdb [...] discards 688810ddd6 80: onsuccess: #596: 1: Success after binutils/gcc/linux/gli [...] discards 49ff0391cc 79: onsuccess: #595: 1: Success after binutils/gcc/linux/gli [...] discards 6a53f40395 78: onsuccess: #594: 1: Success after binutils/gcc/linux/gli [...] discards d6525f2a47 77: onsuccess: #593: 1: Success after binutils/gcc/linux/gli [...] discards 7c624af18f 76: onsuccess: #592: 1: Success after linux: 63 commits discards ed7cd78efd 75: onsuccess: #591: 1: Success after gcc: 25 commits discards 33d80d5f97 74: onsuccess: #590: 1: Success after binutils: 16 commits discards 73e0560fa0 73: onsuccess: #588: 1: Success after binutils/gcc/linux/gdb [...] discards 63653523e7 72: onsuccess: #587: 1: Success after binutils/gcc/linux/gdb [...] discards 4b5759649f 71: onsuccess: #586: 1: Success after binutils/gcc/linux/gdb [...] discards b36236364f 70: onsuccess: #585: 1: Success after binutils/gcc/linux/gli [...] discards 9702b0f076 69: onsuccess: #584: 1: Success after binutils/gcc/glibc/gdb [...] discards 4b69d0bbd5 68: onsuccess: #583: 1: Success after binutils/gcc/linux/gli [...] discards 7b5b21a8a4 67: onsuccess: #582: 1: Success after binutils/gcc/linux/gdb [...] discards a1aee36c16 66: onsuccess: #581: 1: Success after binutils/gcc/linux/gli [...] discards a8f4486160 65: onsuccess: #580: 1: Success after binutils/gcc/linux/gdb [...] discards cbf8be61b9 64: onsuccess: #579: 1: Success after binutils/gcc/linux/gli [...] discards 73daa98bd1 63: onsuccess: #577: 1: Success after binutils/gcc/linux/gli [...] discards 3bc849ef3a 62: onsuccess: #576: 1: Success after binutils/gcc/linux/gdb [...] discards 9d12450d60 61: onsuccess: #575: 1: Success after binutils/gcc/linux/gli [...] discards 2b289b6911 60: onsuccess: #574: 1: Success after binutils/gcc/linux/gli [...] discards b37d71e5d3 59: onsuccess: #573: 1: Success after binutils/gcc/linux/gli [...] discards b69556e1d8 58: onsuccess: #572: 1: Success after binutils/gcc/linux/gli [...] discards b9edd77649 57: onsuccess: #571: 1: Success after binutils/gcc/linux/gli [...] discards 2915cd3149 56: onsuccess: #570: 1: Success after binutils/gcc/linux/gli [...] discards 3df29b6321 55: onsuccess: #569: 1: Success after binutils/gcc/linux/gli [...] discards 932fdda0d4 54: onsuccess: #568: 1: Success after binutils/gcc/linux/gli [...] discards c1e1eda560 53: onsuccess: #567: 1: Success after binutils/gcc/linux/gdb [...] discards c3500482ef 52: onsuccess: #566: 1: Success after binutils/gcc/linux/gli [...] discards 830e6d7e45 51: onsuccess: #565: 1: Success after binutils/gcc/linux/gli [...] discards 80870c8786 50: onsuccess: #564: 1: Success after binutils/gcc/linux/gli [...] discards f244cc8acc 49: onsuccess: #562: 1: Success after binutils: 9 commits discards d386314428 48: onsuccess: #559: 1: Success after binutils: 6 commits discards ea6310561b 47: onsuccess: #556: 1: Success after binutils: 12 commits discards 0329a36667 46: onsuccess: #554: 1: Success after binutils/gcc/linux/gdb [...] discards e61ebf1dd6 45: onsuccess: #553: 1: Success after binutils/gcc/linux/gdb [...] new 1983de84c8 45: onsuccess: #553: 1: Success after binutils/gcc/linux/gdb [...] new ca993b6423 46: onsuccess: #554: 1: Success after binutils/gcc/linux/gdb [...] new 49166b8758 47: onsuccess: #556: 1: Success after binutils: 12 commits new ee6533bf87 48: onsuccess: #559: 1: Success after binutils: 6 commits new 6bb6193565 49: onsuccess: #562: 1: Success after binutils: 9 commits new 92d4fff944 50: onsuccess: #564: 1: Success after binutils/gcc/linux/gli [...] new 6a721db68c 51: onsuccess: #565: 1: Success after binutils/gcc/linux/gli [...] new 40c25a2952 52: onsuccess: #566: 1: Success after binutils/gcc/linux/gli [...] new 5659ec54a4 53: onsuccess: #567: 1: Success after binutils/gcc/linux/gdb [...] new 771aa4f550 54: onsuccess: #568: 1: Success after binutils/gcc/linux/gli [...] new 45196b2792 55: onsuccess: #569: 1: Success after binutils/gcc/linux/gli [...] new 11811e428f 56: onsuccess: #570: 1: Success after binutils/gcc/linux/gli [...] new 3b12ea8e31 57: onsuccess: #571: 1: Success after binutils/gcc/linux/gli [...] new 1cc806c9f8 58: onsuccess: #572: 1: Success after binutils/gcc/linux/gli [...] new b84d5f9daa 59: onsuccess: #573: 1: Success after binutils/gcc/linux/gli [...] new 373ce88b9d 60: onsuccess: #574: 1: Success after binutils/gcc/linux/gli [...] new b5c4e400e1 61: onsuccess: #575: 1: Success after binutils/gcc/linux/gli [...] new 6361406038 62: onsuccess: #576: 1: Success after binutils/gcc/linux/gdb [...] new e29394183b 63: onsuccess: #577: 1: Success after binutils/gcc/linux/gli [...] new 1843ff8f7c 64: onsuccess: #579: 1: Success after binutils/gcc/linux/gli [...] new 092fd71bd4 65: onsuccess: #580: 1: Success after binutils/gcc/linux/gdb [...] new 5a8d48e2be 66: onsuccess: #581: 1: Success after binutils/gcc/linux/gli [...] new fdf9d69bcb 67: onsuccess: #582: 1: Success after binutils/gcc/linux/gdb [...] new 07cca11f4c 68: onsuccess: #583: 1: Success after binutils/gcc/linux/gli [...] new b088e6ca6b 69: onsuccess: #584: 1: Success after binutils/gcc/glibc/gdb [...] new 483d11fcea 70: onsuccess: #585: 1: Success after binutils/gcc/linux/gli [...] new aa3d7e1066 71: onsuccess: #586: 1: Success after binutils/gcc/linux/gdb [...] new edf604bed0 72: onsuccess: #587: 1: Success after binutils/gcc/linux/gdb [...] new 8da31dae6f 73: onsuccess: #588: 1: Success after binutils/gcc/linux/gdb [...] new a3c1dea9ab 74: onsuccess: #590: 1: Success after binutils: 16 commits new ecafc0d231 75: onsuccess: #591: 1: Success after gcc: 25 commits new a9e0906c10 76: onsuccess: #592: 1: Success after linux: 63 commits new cb242a3735 77: onsuccess: #593: 1: Success after binutils/gcc/linux/gli [...] new 02c1721c89 78: onsuccess: #594: 1: Success after binutils/gcc/linux/gli [...] new 651c8a0958 79: onsuccess: #595: 1: Success after binutils/gcc/linux/gli [...] new 96b0c7d5bc 80: onsuccess: #596: 1: Success after binutils/gcc/linux/gli [...] new 8d6d9efaca 81: onsuccess: #597: 1: Success after binutils/gcc/linux/gdb [...] new 725a08d5d5 82: onsuccess: #598: 1: Success after binutils/gcc/linux/gli [...] new e75ae5a934 83: onsuccess: #599: 1: Success after binutils/gcc/linux/gli [...] new 4f97a98e74 84: onsuccess: #600: 1: Success after binutils/gcc/linux/gli [...] new b14ab985f2 85: onsuccess: #601: 1: Success after binutils/gcc/linux/gli [...] new d99c062f59 86: onsuccess: #602: 1: Success after binutils/gcc/linux/gli [...] new 32d12d1e46 87: onsuccess: #603: 1: Success after binutils/gcc/linux/gli [...] new db735d4968 88: onsuccess: #604: 1: Success after binutils/gcc/linux/gdb [...] new ec2ddca829 89: onsuccess: #605: 1: Success after binutils/gcc/linux/gdb [...] new a34de59d07 90: onsuccess: #606: 1: Success after binutils/gcc/linux/gli [...] new 89f7aafc04 91: onsuccess: #610: 1: Success after binutils/gcc/linux/gli [...] new aceaf17e17 92: onsuccess: #611: 1: Success after binutils/gcc/linux/gli [...] new 2a7ae2d91f 93: onsuccess: #613: 1: Success after binutils: 19 commits new 32d45b8c1f 94: onsuccess: #616: 1: Success after binutils: 2 commits new b2295d49a8 95: onsuccess: #619: 1: Success after binutils: 5 commits new f812f8c02f 96: onsuccess: #621: 1: Success after binutils/gcc/linux/gli [...] new 142a126e9a 97: onsuccess: #622: 1: Success after binutils/gcc/gdb: 8 commits new 23b9a33908 98: onsuccess: #623: 1: Success after binutils/gcc/linux/gdb [...] new 46313bd71a 99: onsuccess: #624: 1: Success after binutils/gcc/linux/gli [...] new a5ac8b3f72 100: onsuccess: #625: 1: Success after binutils/gcc/linux/gd [...] new 0fa9c25012 101: onsuccess: #627: 1: Success after binutils/gcc/linux/gd [...] new 93736de6ff 102: onsuccess: #628: 1: Success after binutils/gcc/glibc/gd [...] new f61ca132a8 103: onsuccess: #629: 1: Success after binutils/gcc/gdb: 68 commits new 7017510f4a 104: onsuccess: #630: 1: Success after binutils/gcc/linux/gd [...] new 78cb0f1e56 105: onsuccess: #631: 1: Success after binutils/gcc/linux/gd [...] new b4ad50f298 106: onsuccess: #635: 1: Success after binutils/gcc/linux/gd [...] new 252f0a42fe 107: onsuccess: #636: 1: Success after binutils/gcc/linux/gl [...] new d96a84a3a6 108: onsuccess: #637: 1: Success after binutils/gcc/linux/gl [...] new 64c1107172 109: onsuccess: #638: 1: Success after binutils/gcc/linux/gl [...] new c77e621dc1 110: onsuccess: #639: 1: Success after binutils/gcc/linux/gd [...] new b058a2cfbf 111: onsuccess: #640: 1: Success after binutils/gcc/linux/gd [...] new 89791161ab 112: onsuccess: #641: 1: Success after binutils/gcc/linux/gl [...] new 7c0d3262b4 113: onsuccess: #642: 1: Success after binutils/gcc/linux/gd [...] new 9ec640ea06 114: onsuccess: #643: 1: Success after binutils/gcc/linux/gd [...] new 50025cee18 115: onsuccess: #645: 1: Success after binutils: 27 commits new 0458a97b53 116: onsuccess: #647: 1: Success after linux: 3 commits new fd8e30140d 117: onsuccess: #648: 1: Success after binutils/gcc/linux/gl [...] new 6e94eb0ee7 118: onsuccess: #649: 1: Success after binutils/gcc/linux/gl [...] new db3354c7c5 119: onsuccess: #650: 1: Success after binutils/gcc/linux/gl [...] new 02b116bb56 120: onsuccess: #651: 1: Success after binutils/gcc/linux/gl [...] new e160ed7833 121: onsuccess: #652: 1: Success after binutils/gcc/linux/gd [...] new dc2387ba88 122: onsuccess: #653: 1: Success after binutils/gcc/linux/gd [...] new 3e19a9132e 123: onsuccess: #655: 1: Success after binutils: 22 commits new e6c5ea8b8e 124: onsuccess: #657: 1: Success after glibc: 2 commits new d8296c1ef8 125: onsuccess: #658: 1: Success after linux: 3224 commits new c08e40ac0f 126: onsuccess: #659: 1: Success after binutils/gcc/linux/gl [...] new 9f806cb3db 127: onsuccess: #660: 1: Success after binutils/gcc/linux/gd [...] new a6219741a0 128: onsuccess: #661: 1: Success after binutils/gcc/linux/gl [...] new cf196708fa 129: onsuccess: #662: 1: Success after binutils/gcc/linux/gd [...] new 15988d86c8 130: onsuccess: #663: 1: Success after binutils/gcc/linux/gd [...] new c4e117b6aa 131: onsuccess: #664: 1: Success after binutils/gcc/glibc/gd [...] new eb26c987b9 132: onsuccess: #665: 1: Success after binutils/gcc/linux/gl [...] new d4be070983 133: onsuccess: #666: 1: Success after binutils/gcc/linux/gl [...] new 8fba766d80 134: onsuccess: #667: 1: Success after binutils/gcc/linux/gl [...] new 8e371f6d04 135: onsuccess: #668: 1: Success after binutils/gcc/linux/gl [...] new ea40a0b166 136: onsuccess: #669: 1: Success after binutils/gcc/linux/gd [...] new 422b50de4b 137: onsuccess: #670: 1: Success after binutils/gcc/gdb: 46 commits new 0bd6397141 138: onsuccess: #671: 1: Success after binutils/gcc/linux/gd [...] new f639100b66 139: onsuccess: #672: 1: Success after binutils/gcc/gdb: 28 commits new 3b29445a25 140: onsuccess: #673: 1: Success after binutils/gcc/gdb: 26 commits new 65c849dee5 141: onsuccess: #674: 1: Success after binutils/gcc/gdb: 12 commits new 486408aa02 142: onsuccess: #675: 1: Success after binutils/gcc/linux/gl [...] new 8619ba4bcc 143: onsuccess: #676: 1: Success after binutils/gcc/linux/gd [...] new 6ba59bddfe 144: onsuccess: #677: 1: Success after binutils/gcc/linux/gd [...] new 7c7d1b1d61 145: onsuccess: #678: 1: Success after binutils/gcc/linux/gd [...] new e3a664aa57 146: onsuccess: #680: 1: Success after binutils: 20 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 (f2cd1f52a1) \ N -- N -- N refs/heads/linaro-local/ci/tcwg_gnu_native_check_binutil [...] 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 1732 -> 1728 bytes 02-prepare_abe/console.log.xz | Bin 2760 -> 2744 bytes 03-build_abe-binutils/console.log.xz | Bin 40332 -> 40448 bytes 04-build_abe-gcc/console.log.xz | Bin 214120 -> 214840 bytes 05-clean_sysroot/console.log.xz | Bin 312 -> 312 bytes 06-build_abe-linux/console.log.xz | Bin 8284 -> 8532 bytes 07-build_abe-glibc/console.log.xz | Bin 244572 -> 245124 bytes 08-build_abe-gdb/console.log.xz | Bin 39632 -> 39832 bytes 09-build_abe-dejagnu/console.log.xz | Bin 3832 -> 3904 bytes 10-build_abe-check_binutils/console.log.xz | Bin 2176 -> 2300 bytes 11-check_regression/console.log.xz | Bin 5664 -> 4676 bytes 11-check_regression/results.compare | 8 +- 11-check_regression/results.compare2 | 6 +- 12-update_baseline/console.log | 38 ++-- dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 2 +- mail/mail-subject.txt | 2 +- manifest.sh | 28 +-- sumfiles/binutils.log.xz | Bin 63052 -> 63228 bytes sumfiles/binutils.sum | 62 +++--- sumfiles/gas.log.xz | Bin 83892 -> 83904 bytes sumfiles/gas.sum | 272 +++++++++++------------ sumfiles/ld.log.xz | Bin 122236 -> 122412 bytes sumfiles/ld.sum | 344 ++++++++++++++--------------- 26 files changed, 382 insertions(+), 386 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

1 year, 10 months

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_gnu_cross_build/master-aarch64 updated (cd93961418 -> 2c249afb12)

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 cd93961418 304: onsuccess: #2002: 7: Success after gcc: 4 commits discards fce045d590 303: onsuccess: #2001: 7: Success after binutils: 4 commits discards b055f573d9 302: onsuccess: #1999: 7: Success after binutils/gcc/glibc/g [...] discards 72d6e63500 301: onsuccess: #1998: 7: Success after binutils/gdb: 6 commits discards 36c83b6dbd 300: onsuccess: #1997: 7: Success after binutils/gcc/linux/g [...] discards f55da033a6 299: onsuccess: #1996: 7: Success after binutils/gcc/gdb: 10 [...] discards ccdb0bc3dd 298: onsuccess: #1995: 7: Success after binutils/gcc/gdb: 7 commits discards 9fa3df4a9e 297: onsuccess: #1994: 7: Success after binutils/gcc/gdb: 4 commits discards eb677ec4ba 296: onsuccess: #1993: 7: Success after binutils/gcc/linux/g [...] discards bc770cddd1 295: onsuccess: #1992: 7: Success after binutils/gdb: 18 commits discards fd0330060e 294: onsuccess: #1991: 7: Success after binutils/gdb: 6 commits discards 68dc548403 293: onsuccess: #1990: 7: Success after binutils/gcc/linux/g [...] discards 0a26f4dbd6 292: onsuccess: #1989: 7: Success after binutils/gcc/gdb: 8 commits discards 8a8e188487 291: onsuccess: #1988: 7: Success after binutils/gcc/gdb: 5 commits discards 97762c105e 290: onsuccess: #1987: 7: Success after gcc/linux: 26 commits discards 7b33661d36 289: onsuccess: #1986: 7: Success after binutils/gcc/linux/g [...] discards 174416e32a 288: onsuccess: #1985: 7: Success after gcc: 17 commits discards 37231ab08a 287: onsuccess: #1984: 7: Success after binutils/gdb: 2 commits discards 0b08a18fae 286: onsuccess: #1983: 7: Success after binutils/gcc/gdb: 3 commits discards 5d71072ba9 285: onsuccess: #1982: 7: Success after binutils/gcc/gdb: 6 commits discards ca79948360 284: onsuccess: #1981: 7: Success after gcc: 2 commits discards c829417874 283: onsuccess: #1980: 7: Success after binutils/gcc/gdb: 6 commits discards 3dc8c59aae 282: onsuccess: #1979: 7: Success after binutils/gcc/gdb: 18 [...] discards d0c4eb33a8 281: onsuccess: #1978: 7: Success after basepoints/gcc-13-48 [...] discards 43a27564c4 280: onsuccess: #1977: 7: Success after binutils/gdb: 18 commits discards 7c88674380 279: onsuccess: #1976: 7: Success after binutils/gcc/gdb: 5 commits discards 59af999cbd 278: onsuccess: #1975: 7: Success after basepoints/gcc-13-48 [...] discards 3380793f68 277: onsuccess: #1974: 7: Success after binutils/gdb: 4 commits discards 4b2de90176 276: onsuccess: #1973: 7: Success after binutils/gcc/linux/g [...] discards 75b137131f 275: onsuccess: #1972: 7: Success after binutils/gcc/gdb: 23 [...] discards e12ec31c11 274: onsuccess: #1971: 7: Success after binutils/gcc/gdb: 21 [...] discards cdd7fb9f04 273: onsuccess: #1970: 7: Success after binutils/gcc/gdb: 5 commits discards 626e5f8944 272: onsuccess: #1969: 7: Success after binutils/gcc/linux/g [...] discards 17e37e79ca 271: onsuccess: #1968: 7: Success after binutils/gcc/linux/g [...] discards 6d320f1ad6 270: onsuccess: #1967: 7: Success after binutils/gcc/gdb: 71 [...] discards cbf89dbdab 269: onsuccess: #1966: 7: Success after binutils/gcc/gdb: 43 [...] discards da82f0b724 268: onsuccess: #1965: 7: Success after binutils/gcc/linux/g [...] discards a147186785 267: onsuccess: #1964: 7: Success after binutils/gcc/glibc/g [...] discards 0a7834fe27 266: onsuccess: #1963: 7: Success after binutils/gcc/gdb: 28 [...] discards 4970d88c86 265: onsuccess: #1962: 7: Success after binutils/gcc/linux/g [...] discards 60f4c7d7bf 264: onsuccess: #1961: 7: Success after binutils/gcc/glibc/g [...] discards 75094beaaa 263: onsuccess: #1960: 7: Success after binutils/gcc/linux/g [...] discards ebde2c55f5 262: onsuccess: #1959: 7: Success after binutils/gcc/gdb/qem [...] discards 3f8b03f36e 261: onsuccess: #1958: 7: Success after binutils/gcc/gdb: 64 [...] discards b1b2290715 260: onsuccess: #1957: 7: Success after binutils/gcc/gdb: 8 commits discards 1dd8d9f86a 259: onsuccess: #1956: 7: Success after gcc/linux/glibc/qemu [...] discards 1f89ca7acd 258: onsuccess: #1955: 7: Success after binutils/gcc/gdb: 7 commits discards b470573a41 257: onsuccess: #1954: 7: Success after binutils/gcc/gdb: 7 commits discards 9099a7e436 256: onsuccess: #1953: 7: Success after binutils/gcc/linux/g [...] discards 1fd77a6655 255: onsuccess: #1952: 7: Success after binutils/gcc/linux/g [...] discards 5ff3a87523 254: onsuccess: #1951: 7: Success after binutils/gcc/glibc/g [...] discards 341b9d9710 253: onsuccess: #1950: 7: Success after glibc: 2 commits discards 7ae29f933a 252: onsuccess: #1949: 7: Success after binutils/gcc/glibc/g [...] discards d4a08009db 251: onsuccess: #1948: 7: Success after v7.2.0-211-g562d4af3 [...] discards 78596970df 250: onsuccess: #1947: 7: Success after binutils/gcc/gdb: 5 commits discards 5d1278d0d6 249: onsuccess: #1946: 7: Success after binutils/gcc/gdb: 5 commits discards 8956e0ea18 248: onsuccess: #1945: 7: Success after binutils/gcc/gdb/qem [...] discards 1151ac2297 247: onsuccess: #1944: 7: Success after gcc/linux: 109 commits discards 70417aaf5e 246: onsuccess: #1943: 7: Success after binutils/gdb: 6 commits discards 0f4ba0f130 245: onsuccess: #1942: 7: Success after binutils/gcc/gdb: 13 [...] discards cce0f5fdbe 244: onsuccess: #1941: 7: Success after binutils/gcc/linux/g [...] discards 0759c19923 243: onsuccess: #1940: 7: Success after binutils/gcc/linux/g [...] discards 1e291a115c 242: onsuccess: #1939: 7: Success after binutils/gcc/gdb/qem [...] discards 5d01953977 241: onsuccess: #1938: 7: Success after binutils/gcc/linux/g [...] discards 51d6e8c602 240: onsuccess: #1937: 7: Success after binutils/gcc/linux/g [...] discards d321106f7e 239: onsuccess: #1936: 7: Success after binutils/gcc/linux/g [...] discards 65eb2ed8e5 238: onsuccess: #1935: 7: Success after binutils/gcc/gdb/qem [...] discards d1789c12e3 237: onsuccess: #1934: 7: Success after basepoints/gcc-13-47 [...] discards 2c874c19fe 236: onsuccess: #1933: 7: Success after binutils/gcc/linux/g [...] discards 19cb20bd32 235: onsuccess: #1932: 7: Success after binutils/gcc/linux/g [...] discards feb7f39ba1 234: onsuccess: #1931: 7: Success after binutils/gcc/gdb: 22 [...] discards 980308ab31 233: onsuccess: #1930: 7: Success after binutils/gcc/linux/g [...] discards 4393641ac9 232: onsuccess: #1929: 7: Success after binutils/gcc/linux/g [...] discards 3bace9f346 231: onsuccess: #1928: 3: Success after gcc: 8 commits discards 9d5ad25753 230: force: #1927: 3: Failure after basepoints/gcc-13-4618-g [...] discards 22424c63f7 229: force: #1926: 7: Success after gcc: 7 commits discards 96cf1c1e1d 228: onsuccess: #1914: 7: Success after gdb-12-branchpoint-3 [...] discards dba8d19ca7 227: onsuccess: #1906: 7: Success after binutils: 9 commits discards 9ddf9fecfb 226: onsuccess: #1904: 7: Success after binutils/gcc/gdb: 38 [...] discards 859d8088ea 225: onsuccess: #1903: 7: Success after binutils/gcc/linux/g [...] discards 5eadfeb691 224: onsuccess: #1902: 7: Success after binutils/gcc/linux/g [...] discards 0843ef3f36 223: onsuccess: #1901: 7: Success after basepoints/gcc-13-45 [...] discards e9353a7b5b 222: onsuccess: #1900: 7: Success after binutils/gcc/linux/g [...] discards e11317fd54 221: onsuccess: #1899: 7: Success after binutils/gcc/gdb: 15 [...] discards 2c49dcf62d 220: onsuccess: #1898: 7: Success after binutils/linux/glibc [...] discards 16556bf50f 219: onsuccess: #1897: 7: Success after binutils/gcc/gdb: 8 commits discards 274f0d2a24 218: onsuccess: #1896: 7: Success after binutils/gcc/linux/g [...] discards bd5e7e0860 217: onsuccess: #1893: 7: Success after binutils/gcc/gdb: 10 [...] discards fc24e24936 216: onsuccess: #1892: 7: Success after binutils/gdb: 2 commits discards c70a789178 215: onsuccess: #1891: 7: Success after binutils/gcc/linux/g [...] discards 1c548b4a06 214: onsuccess: #1890: 7: Success after binutils/gcc/glibc/g [...] discards 03d39470b6 213: onsuccess: #1889: 7: Success after gcc: 5 commits discards 1a273575e0 212: onsuccess: #1888: 7: Success after binutils/gcc/glibc/g [...] discards 052855bb3f 211: onsuccess: #1887: 7: Success after binutils/gcc/linux/g [...] discards d96a08507a 210: onsuccess: #1868: 7: Success after binutils: 7 commits discards 8ed81d0860 209: onsuccess: #1866: 7: Success after binutils/gcc/gdb/qem [...] discards aaec613ec2 208: onsuccess: #1865: 7: Success after linux: 12 commits discards 967ca66bdc 207: onsuccess: #1862: 7: Success after binutils: 4 commits discards f3dac09a1e 206: onsuccess: #1860: 7: Success after gcc: 2 commits discards 8b70724b3b 205: onsuccess: #1859: 7: Success after gcc: 3 commits discards 01249f86fb 204: onsuccess: #1858: 7: Success after binutils/gcc/linux/g [...] new 671be0eb32 204: onsuccess: #1858: 7: Success after binutils/gcc/linux/g [...] new bac98c05ce 205: onsuccess: #1859: 7: Success after gcc: 3 commits new 6f4d639c7b 206: onsuccess: #1860: 7: Success after gcc: 2 commits new 6d15012695 207: onsuccess: #1862: 7: Success after binutils: 4 commits new 4ffd4429b4 208: onsuccess: #1865: 7: Success after linux: 12 commits new d3a43c8efc 209: onsuccess: #1866: 7: Success after binutils/gcc/gdb/qem [...] new 17eb6ce577 210: onsuccess: #1868: 7: Success after binutils: 7 commits new 408be0718e 211: onsuccess: #1887: 7: Success after binutils/gcc/linux/g [...] new a9e3852c32 212: onsuccess: #1888: 7: Success after binutils/gcc/glibc/g [...] new 52ba6b84d3 213: onsuccess: #1889: 7: Success after gcc: 5 commits new 6d81f7937e 214: onsuccess: #1890: 7: Success after binutils/gcc/glibc/g [...] new e9b511ed94 215: onsuccess: #1891: 7: Success after binutils/gcc/linux/g [...] new 90ebdb2e9f 216: onsuccess: #1892: 7: Success after binutils/gdb: 2 commits new c380b71a61 217: onsuccess: #1893: 7: Success after binutils/gcc/gdb: 10 [...] new ac5ef50012 218: onsuccess: #1896: 7: Success after binutils/gcc/linux/g [...] new 15f61da5b9 219: onsuccess: #1897: 7: Success after binutils/gcc/gdb: 8 commits new e29b9494ec 220: onsuccess: #1898: 7: Success after binutils/linux/glibc [...] new d78f06f3ce 221: onsuccess: #1899: 7: Success after binutils/gcc/gdb: 15 [...] new f5f559b375 222: onsuccess: #1900: 7: Success after binutils/gcc/linux/g [...] new 89ef3a66a1 223: onsuccess: #1901: 7: Success after basepoints/gcc-13-45 [...] new 578819e340 224: onsuccess: #1902: 7: Success after binutils/gcc/linux/g [...] new 1a46eea660 225: onsuccess: #1903: 7: Success after binutils/gcc/linux/g [...] new c6b545c543 226: onsuccess: #1904: 7: Success after binutils/gcc/gdb: 38 [...] new e18dc31879 227: onsuccess: #1906: 7: Success after binutils: 9 commits new 753f268745 228: onsuccess: #1914: 7: Success after gdb-12-branchpoint-3 [...] new 1b18361c98 229: force: #1926: 7: Success after gcc: 7 commits new b488369c4f 230: force: #1927: 3: Failure after basepoints/gcc-13-4618-g [...] new 6507f712ea 231: onsuccess: #1928: 3: Success after gcc: 8 commits new 26a7d43c1e 232: onsuccess: #1929: 7: Success after binutils/gcc/linux/g [...] new 1b94b4285c 233: onsuccess: #1930: 7: Success after binutils/gcc/linux/g [...] new fd0e69fb3b 234: onsuccess: #1931: 7: Success after binutils/gcc/gdb: 22 [...] new 932789154d 235: onsuccess: #1932: 7: Success after binutils/gcc/linux/g [...] new ce83375626 236: onsuccess: #1933: 7: Success after binutils/gcc/linux/g [...] new 6435de4261 237: onsuccess: #1934: 7: Success after basepoints/gcc-13-47 [...] new 09bbd6837e 238: onsuccess: #1935: 7: Success after binutils/gcc/gdb/qem [...] new bf5c7988a8 239: onsuccess: #1936: 7: Success after binutils/gcc/linux/g [...] new 37add7e626 240: onsuccess: #1937: 7: Success after binutils/gcc/linux/g [...] new 9325439d56 241: onsuccess: #1938: 7: Success after binutils/gcc/linux/g [...] new ae05e6f69a 242: onsuccess: #1939: 7: Success after binutils/gcc/gdb/qem [...] new 96aff88f3d 243: onsuccess: #1940: 7: Success after binutils/gcc/linux/g [...] new 6d0ddafeba 244: onsuccess: #1941: 7: Success after binutils/gcc/linux/g [...] new f20c6b0300 245: onsuccess: #1942: 7: Success after binutils/gcc/gdb: 13 [...] new 2cededd310 246: onsuccess: #1943: 7: Success after binutils/gdb: 6 commits new 2a09f7b682 247: onsuccess: #1944: 7: Success after gcc/linux: 109 commits new 0b2d583084 248: onsuccess: #1945: 7: Success after binutils/gcc/gdb/qem [...] new 6112190c66 249: onsuccess: #1946: 7: Success after binutils/gcc/gdb: 5 commits new 016194d900 250: onsuccess: #1947: 7: Success after binutils/gcc/gdb: 5 commits new 1f88275f8c 251: onsuccess: #1948: 7: Success after v7.2.0-211-g562d4af3 [...] new bd9db73819 252: onsuccess: #1949: 7: Success after binutils/gcc/glibc/g [...] new dc5fce6954 253: onsuccess: #1950: 7: Success after glibc: 2 commits new 58fc8c1618 254: onsuccess: #1951: 7: Success after binutils/gcc/glibc/g [...] new 48bf688e80 255: onsuccess: #1952: 7: Success after binutils/gcc/linux/g [...] new 496d2c5c6b 256: onsuccess: #1953: 7: Success after binutils/gcc/linux/g [...] new 0e19185898 257: onsuccess: #1954: 7: Success after binutils/gcc/gdb: 7 commits new abdb312075 258: onsuccess: #1955: 7: Success after binutils/gcc/gdb: 7 commits new cf048a7176 259: onsuccess: #1956: 7: Success after gcc/linux/glibc/qemu [...] new d826563f49 260: onsuccess: #1957: 7: Success after binutils/gcc/gdb: 8 commits new 9386ad4f5b 261: onsuccess: #1958: 7: Success after binutils/gcc/gdb: 64 [...] new 6c46427c27 262: onsuccess: #1959: 7: Success after binutils/gcc/gdb/qem [...] new b54577531c 263: onsuccess: #1960: 7: Success after binutils/gcc/linux/g [...] new 8e7670f590 264: onsuccess: #1961: 7: Success after binutils/gcc/glibc/g [...] new d397d6825b 265: onsuccess: #1962: 7: Success after binutils/gcc/linux/g [...] new 63927c8095 266: onsuccess: #1963: 7: Success after binutils/gcc/gdb: 28 [...] new 29819eec60 267: onsuccess: #1964: 7: Success after binutils/gcc/glibc/g [...] new 17d6aab6c0 268: onsuccess: #1965: 7: Success after binutils/gcc/linux/g [...] new 7c96e30f7f 269: onsuccess: #1966: 7: Success after binutils/gcc/gdb: 43 [...] new 7de79fafce 270: onsuccess: #1967: 7: Success after binutils/gcc/gdb: 71 [...] new 75c6c6ee2b 271: onsuccess: #1968: 7: Success after binutils/gcc/linux/g [...] new d7cc133527 272: onsuccess: #1969: 7: Success after binutils/gcc/linux/g [...] new 35ac8272a4 273: onsuccess: #1970: 7: Success after binutils/gcc/gdb: 5 commits new 0e50cffb9d 274: onsuccess: #1971: 7: Success after binutils/gcc/gdb: 21 [...] new 6612709a50 275: onsuccess: #1972: 7: Success after binutils/gcc/gdb: 23 [...] new 9e94f7ac3d 276: onsuccess: #1973: 7: Success after binutils/gcc/linux/g [...] new 6bb10a70f5 277: onsuccess: #1974: 7: Success after binutils/gdb: 4 commits new 7035b197d7 278: onsuccess: #1975: 7: Success after basepoints/gcc-13-48 [...] new f7395c29bc 279: onsuccess: #1976: 7: Success after binutils/gcc/gdb: 5 commits new 305943ef5a 280: onsuccess: #1977: 7: Success after binutils/gdb: 18 commits new ac00246a4c 281: onsuccess: #1978: 7: Success after basepoints/gcc-13-48 [...] new 9435a90a8e 282: onsuccess: #1979: 7: Success after binutils/gcc/gdb: 18 [...] new a4b2b4dc72 283: onsuccess: #1980: 7: Success after binutils/gcc/gdb: 6 commits new e2f2ab9ec2 284: onsuccess: #1981: 7: Success after gcc: 2 commits new 183c051e44 285: onsuccess: #1982: 7: Success after binutils/gcc/gdb: 6 commits new 972541fa25 286: onsuccess: #1983: 7: Success after binutils/gcc/gdb: 3 commits new f58755b1fe 287: onsuccess: #1984: 7: Success after binutils/gdb: 2 commits new cc90549712 288: onsuccess: #1985: 7: Success after gcc: 17 commits new 03d95bc575 289: onsuccess: #1986: 7: Success after binutils/gcc/linux/g [...] new 9d95e134d8 290: onsuccess: #1987: 7: Success after gcc/linux: 26 commits new def3398ba3 291: onsuccess: #1988: 7: Success after binutils/gcc/gdb: 5 commits new 39c23ec210 292: onsuccess: #1989: 7: Success after binutils/gcc/gdb: 8 commits new d00b62143b 293: onsuccess: #1990: 7: Success after binutils/gcc/linux/g [...] new f440e421c8 294: onsuccess: #1991: 7: Success after binutils/gdb: 6 commits new 1739c6d5ff 295: onsuccess: #1992: 7: Success after binutils/gdb: 18 commits new 5b4a31105d 296: onsuccess: #1993: 7: Success after binutils/gcc/linux/g [...] new 1060259996 297: onsuccess: #1994: 7: Success after binutils/gcc/gdb: 4 commits new 03e529eda9 298: onsuccess: #1995: 7: Success after binutils/gcc/gdb: 7 commits new 5d2696796c 299: onsuccess: #1996: 7: Success after binutils/gcc/gdb: 10 [...] new 03e0b91a36 300: onsuccess: #1997: 7: Success after binutils/gcc/linux/g [...] new bf8ab4d38d 301: onsuccess: #1998: 7: Success after binutils/gdb: 6 commits new afd29a301f 302: onsuccess: #1999: 7: Success after binutils/gcc/glibc/g [...] new 025b875193 303: onsuccess: #2001: 7: Success after binutils: 4 commits new 7a1ed76f97 304: onsuccess: #2002: 7: Success after gcc: 4 commits new 2c249afb12 305: force: #2006: 7: Success after gdb: 2 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 (cd93961418) \ 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 1680 -> 1744 bytes 02-prepare_abe/console.log.xz | Bin 2756 -> 2772 bytes 04-build_abe-binutils/console.log.xz | Bin 32136 -> 32092 bytes 05-build_abe-stage1/console.log.xz | Bin 73972 -> 74012 bytes 07-build_abe-linux/console.log.xz | Bin 8524 -> 8520 bytes 08-build_abe-glibc/console.log.xz | Bin 244940 -> 245432 bytes 09-build_abe-stage2/console.log.xz | Bin 205244 -> 205564 bytes 10-build_abe-gdb/console.log.xz | Bin 39984 -> 39572 bytes 11-build_abe-qemu/console.log.xz | Bin 31984 -> 31504 bytes 12-check_regression/console.log.xz | Bin 3004 -> 2952 bytes 13-update_baseline/console.log | 44 +++++++++++++++++------------------ dashboard/dashboard-generate.sh | 2 +- git/gdb_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 2 +- mail/mail-subject.txt | 2 +- manifest.sh | 26 ++++++++++----------- 17 files changed, 40 insertions(+), 40 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

1 year, 10 months

Jump to page:

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

Tcwg-commits January 2023