Tcwg-commits March 2023

tcwg-commits@lists.linaro.org

5 participants
3834 discussions

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_bmk-code_speed-spec2k6/gnu-aarch64-master-O2_LTO updated (dc4986de72d -> 01248d4340b)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. tcwg-buildslave pushed a change to branch linaro-local/ci/tcwg_bmk-code_speed-spec2k6/gnu-aarch64-master-O2_LTO in repository toolchain/ci/base-artifacts. from dc4986de72d 84: onsuccess: #9: 1: [TCWG CI] No change after binutils/gc [...] new 01248d4340b 85: onsuccess: #10: 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 2112 -> 1812 bytes 02-prepare_abe/console.log.xz | Bin 2560 -> 2588 bytes 03-build_abe-binutils/console.log.xz | Bin 27708 -> 27860 bytes 04-build_abe-stage1/console.log.xz | Bin 72040 -> 71772 bytes 05-clean_sysroot/console.log.xz | Bin 332 -> 332 bytes 06-build_abe-linux/console.log.xz | Bin 8264 -> 8292 bytes 07-build_abe-glibc/console.log.xz | Bin 243696 -> 241760 bytes 08-build_abe-stage2/console.log.xz | Bin 176312 -> 178308 bytes 09-benchmark/benchmark-build.log | 136 +- 09-benchmark/benchmark.log | 134 +- 09-benchmark/console.log.xz | Bin 4136 -> 4204 bytes .../compare-results-vs-first-internal.csv | 76 +- .../compare-results-vs-prev-internal.csv | 80 +- 10-check_regression/console.log.xz | Bin 8936 -> 8764 bytes .../csv-results-vs-first-1/perf.csv | 172 +- .../csv-results-vs-first-1/results.csv | 10496 +- .../csv-results-vs-first-1/size.csv | 398784 +++++------ 10-check_regression/csv-results-vs-first-1/sve.csv | 13312 +- .../csv-results-vs-first-1/vect.csv | 74 +- 10-check_regression/csv-results-vs-prev-0/perf.csv | 166 +- .../csv-results-vs-prev-0/results.csv | 49344 +- 10-check_regression/csv-results-vs-prev-0/size.csv | 655120 +++++++++--------- 10-check_regression/csv-results-vs-prev-0/sve.csv | 15902 +- 10-check_regression/csv-results-vs-prev-0/vect.csv | 128 +- 10-check_regression/csv-results-vs-prev-1/perf.csv | 172 +- .../csv-results-vs-prev-1/results.csv | 10496 +- 10-check_regression/csv-results-vs-prev-1/size.csv | 398784 +++++------ 10-check_regression/csv-results-vs-prev-1/sve.csv | 13312 +- 10-check_regression/csv-results-vs-prev-1/vect.csv | 74 +- 10-check_regression/results-vs-first-brief.csv | 66 +- 10-check_regression/results-vs-first-full.csv | 182 +- 10-check_regression/results-vs-first-internal.csv | 78 +- 10-check_regression/results-vs-first.csv | 78 +- 10-check_regression/results-vs-first.log | 1336 +- 10-check_regression/results-vs-prev-brief.csv | 68 +- 10-check_regression/results-vs-prev-full.csv | 190 +- 10-check_regression/results-vs-prev-internal.csv | 80 +- 10-check_regression/results-vs-prev.csv | 80 +- 10-check_regression/results-vs-prev.log | 1498 +- dashboard/dashboard-generate.sh | 2 +- .../400.perlbench/results-metadata.json | 14 +- .../squad-vs-first/401.bzip2/results-metadata.json | 14 +- .../squad-vs-first/403.gcc/results-metadata.json | 14 +- .../410.bwaves/results-metadata.json | 14 +- .../416.gamess/results-metadata.json | 14 +- .../squad-vs-first/429.mcf/results-metadata.json | 14 +- .../squad-vs-first/433.milc/results-metadata.json | 14 +- .../squad-vs-first/433.milc/results-metrics.json | 2 +- .../434.zeusmp/results-metadata.json | 14 +- .../435.gromacs/results-metadata.json | 14 +- .../436.cactusADM/results-metadata.json | 14 +- .../437.leslie3d/results-metadata.json | 14 +- .../437.leslie3d/results-metrics.json | 2 +- .../squad-vs-first/444.namd/results-metadata.json | 14 +- .../squad-vs-first/445.gobmk/results-metadata.json | 14 +- .../squad-vs-first/445.gobmk/results-metrics.json | 2 +- .../447.dealII/results-metadata.json | 14 +- .../squad-vs-first/447.dealII/results-metrics.json | 2 +- .../450.soplex/results-metadata.json | 14 +- .../453.povray/results-metadata.json | 14 +- .../squad-vs-first/453.povray/results-metrics.json | 2 +- .../454.calculix/results-metadata.json | 14 +- .../squad-vs-first/456.hmmer/results-metadata.json | 14 +- .../squad-vs-first/458.sjeng/results-metadata.json | 14 +- .../459.GemsFDTD/results-metadata.json | 14 +- .../459.GemsFDTD/results-metrics.json | 2 +- .../462.libquantum/results-metadata.json | 14 +- .../464.h264ref/results-metadata.json | 14 +- .../squad-vs-first/465.tonto/results-metadata.json | 14 +- .../squad-vs-first/465.tonto/results-metrics.json | 2 +- .../squad-vs-first/470.lbm/results-metadata.json | 14 +- .../471.omnetpp/results-metadata.json | 14 +- .../471.omnetpp/results-metrics.json | 2 +- .../squad-vs-first/473.astar/results-metadata.json | 14 +- .../squad-vs-first/481.wrf/results-metadata.json | 14 +- .../482.sphinx3/results-metadata.json | 14 +- .../483.xalancbmk/results-metadata.json | 14 +- .../483.xalancbmk/results-metrics.json | 2 +- .../squad-vs-first/Mean/results-metadata.json | 14 +- dashboard/squad-vs-first/dashboard-push-squad.sh | 122 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- git/glibc_rev | 2 +- mail/jira-body.txt | 33 +- mail/mail-body.txt | 33 +- mail/mail-subject.txt | 2 +- manifest.sh | 32 +- results_id | 2 +- 88 files changed, 773773 insertions(+), 797315 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 3 months

[gcc] branch master updated (3e791f45ded -> 5a1717fbdfd)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. unknown user pushed a change to branch master in repository gcc. from 3e791f45ded Fortran: improve checking of FINAL subroutine arguments [PR104572] new 5a1717fbdfd c++: array bound partial ordering [PR108390] The 1 revisions listed above as "new" are entirely new to this repository and will be described in separate emails. The revisions listed as "adds" were already present in the repository and have only been added to this reference. Summary of changes: gcc/cp/pt.cc | 8 +++++--- gcc/testsuite/g++.dg/template/partial-order3.C | 6 ++++++ 2 files changed, 11 insertions(+), 3 deletions(-) create mode 100644 gcc/testsuite/g++.dg/template/partial-order3.C -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 3 months

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_bmk-code_vect-spec2k6/gnu-aarch64-master-O3 updated (f30de8afe6e -> d63d7eaa6f1)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. tcwg-buildslave pushed a change to branch linaro-local/ci/tcwg_bmk-code_vect-spec2k6/gnu-aarch64-master-O3 in repository toolchain/ci/base-artifacts. from f30de8afe6e 4: onsuccess: #5: 1: [TCWG CI] No change after binutils/gcc [...] new d63d7eaa6f1 5: onsuccess: #6: 1: [TCWG CI] No change after binutils/gcc [...] 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 1976 -> 1808 bytes 02-prepare_abe/console.log.xz | Bin 2528 -> 2600 bytes 03-build_abe-binutils/console.log.xz | Bin 26964 -> 27652 bytes 04-build_abe-stage1/console.log.xz | Bin 71532 -> 71936 bytes 05-clean_sysroot/console.log.xz | Bin 332 -> 332 bytes 06-build_abe-linux/console.log.xz | Bin 8308 -> 8304 bytes 07-build_abe-glibc/console.log.xz | Bin 242436 -> 242072 bytes 08-build_abe-stage2/console.log.xz | Bin 176460 -> 175908 bytes 09-benchmark/benchmark-build.log | 100 +- 09-benchmark/benchmark.log | 98 +- 09-benchmark/console.log.xz | Bin 4032 -> 3980 bytes .../compare-results-vs-first-internal.csv | 234 +- .../compare-results-vs-prev-internal.csv | 240 +- 10-check_regression/console.log.xz | Bin 14976 -> 14992 bytes .../csv-results-vs-first-1/md5sum.csv | 1537 +- .../csv-results-vs-first-1/perf.csv | 2382 +- .../csv-results-vs-first-1/results.csv | 4684 +- .../csv-results-vs-first-1/size.csv | 1922 +- .../csv-results-vs-prev-0/md5sum.csv | 2092 +- 10-check_regression/csv-results-vs-prev-0/perf.csv | 2570 +- .../csv-results-vs-prev-0/results.csv | 2910 +- 10-check_regression/csv-results-vs-prev-0/size.csv | 502638 +++++++++--------- 10-check_regression/csv-results-vs-prev-0/sve.csv | 15478 +- 10-check_regression/csv-results-vs-prev-0/vect.csv | 4092 +- .../csv-results-vs-prev-1/md5sum.csv | 1537 +- 10-check_regression/csv-results-vs-prev-1/perf.csv | 2382 +- .../csv-results-vs-prev-1/results.csv | 4684 +- 10-check_regression/csv-results-vs-prev-1/size.csv | 1922 +- .../output-bmk-results/exe.regression | 4 - .../output-bmk-results/exe.regression.diff | 1 - .../output-bmk-results/symbol.regression | 8 +- .../output-bmk-results/symbol.regression.diff | 2 +- 10-check_regression/results-vs-first-brief.csv | 68 +- 10-check_regression/results-vs-first-full.csv | 2414 +- 10-check_regression/results-vs-first-internal.csv | 234 +- 10-check_regression/results-vs-first.csv | 234 +- 10-check_regression/results-vs-first.log | 1276 +- 10-check_regression/results-vs-prev-brief.csv | 68 +- 10-check_regression/results-vs-prev-compare.csv | 11 +- 10-check_regression/results-vs-prev-full.csv | 2682 +- 10-check_regression/results-vs-prev-internal.csv | 240 +- 10-check_regression/results-vs-prev.csv | 240 +- 10-check_regression/results-vs-prev.log | 1308 +- 11-update_baseline/console.log | 8 +- dashboard/dashboard-generate.sh | 2 +- .../400.perlbench/results-metadata.json | 14 +- .../400.perlbench/results-metrics.json | 2 +- .../squad-vs-first/401.bzip2/results-metadata.json | 14 +- .../squad-vs-first/401.bzip2/results-metrics.json | 2 +- .../squad-vs-first/403.gcc/results-metadata.json | 14 +- .../squad-vs-first/403.gcc/results-metrics.json | 2 +- .../410.bwaves/results-metadata.json | 14 +- .../416.gamess/results-metadata.json | 14 +- .../squad-vs-first/429.mcf/results-metadata.json | 14 +- .../squad-vs-first/433.milc/results-metadata.json | 14 +- .../squad-vs-first/433.milc/results-metrics.json | 2 +- .../434.zeusmp/results-metadata.json | 14 +- .../435.gromacs/results-metadata.json | 14 +- .../436.cactusADM/results-metadata.json | 14 +- .../436.cactusADM/results-metrics.json | 2 +- .../437.leslie3d/results-metadata.json | 14 +- .../437.leslie3d/results-metrics.json | 2 +- .../squad-vs-first/444.namd/results-metadata.json | 14 +- .../squad-vs-first/444.namd/results-metrics.json | 2 +- .../squad-vs-first/445.gobmk/results-metadata.json | 14 +- .../447.dealII/results-metadata.json | 14 +- .../squad-vs-first/447.dealII/results-metrics.json | 2 +- .../450.soplex/results-metadata.json | 14 +- .../squad-vs-first/450.soplex/results-metrics.json | 2 +- .../453.povray/results-metadata.json | 14 +- .../squad-vs-first/453.povray/results-metrics.json | 2 +- .../454.calculix/results-metadata.json | 14 +- .../454.calculix/results-metrics.json | 2 +- .../squad-vs-first/456.hmmer/results-metadata.json | 14 +- .../squad-vs-first/456.hmmer/results-metrics.json | 2 +- .../squad-vs-first/458.sjeng/results-metadata.json | 14 +- .../squad-vs-first/458.sjeng/results-metrics.json | 2 +- .../459.GemsFDTD/results-metadata.json | 14 +- .../459.GemsFDTD/results-metrics.json | 2 +- .../462.libquantum/results-metadata.json | 14 +- .../462.libquantum/results-metrics.json | 2 +- .../464.h264ref/results-metadata.json | 14 +- .../464.h264ref/results-metrics.json | 2 +- .../squad-vs-first/465.tonto/results-metadata.json | 14 +- .../squad-vs-first/465.tonto/results-metrics.json | 2 +- .../squad-vs-first/470.lbm/results-metadata.json | 14 +- .../squad-vs-first/470.lbm/results-metrics.json | 2 +- .../471.omnetpp/results-metadata.json | 14 +- .../squad-vs-first/473.astar/results-metadata.json | 14 +- .../squad-vs-first/473.astar/results-metrics.json | 2 +- .../squad-vs-first/481.wrf/results-metadata.json | 14 +- .../squad-vs-first/481.wrf/results-metrics.json | 2 +- .../482.sphinx3/results-metadata.json | 14 +- .../482.sphinx3/results-metrics.json | 2 +- .../483.xalancbmk/results-metadata.json | 14 +- .../483.xalancbmk/results-metrics.json | 2 +- .../squad-vs-first/Mean/results-metadata.json | 14 +- dashboard/squad-vs-first/Mean/results-metrics.json | 2 +- dashboard/squad-vs-first/dashboard-push-squad.sh | 122 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- git/glibc_rev | 2 +- mail/jira-body.txt | 33 +- mail/mail-body.txt | 33 +- mail/mail-subject.txt | 2 +- manifest.sh | 32 +- results_id | 2 +- 107 files changed, 280481 insertions(+), 280517 deletions(-) delete mode 100644 10-check_regression/output-bmk-results/exe.regression -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 3 months

[binutils-gdb] branch master updated (1c3b2b83dc2 -> 52ec426b5eb)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. unknown user pushed a change to branch master in repository binutils-gdb. from 1c3b2b83dc2 gdb/testsuite: adjust test cases to previous "maintenance i [...] new 52ec426b5eb Remove unnecessary cast 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/dwarf2/read.c | 3 +-- 1 file changed, 1 insertion(+), 2 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 3 months

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_gcc_bootstrap/master-aarch64-bootstrap_profiled_lto updated (541625244f5 -> c8486b659eb)

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/master-aarch64-bootstrap_profiled_lto in repository toolchain/ci/base-artifacts. discards 541625244f5 211: onsuccess: #27: 2: Success after binutils/gcc: 41 commits discards 0bcf9f4d91b 210: onsuccess: #26: 2: Success after binutils/gcc: 27 commits discards 2f4781f99a1 209: onsuccess: #25: 2: Success after binutils/gcc: 12 commits discards 68dd59daefc 208: onsuccess: #24: 2: Success after binutils/gcc: 44 commits discards 0dcd686dd2c 207: onsuccess: #23: 2: Success after binutils/gcc: 75 commits discards a7ed2759bef 206: onsuccess: #21: 2: Success after binutils/gcc: 38 commits discards 64cac7d7009 205: onsuccess: #20: 2: Success after binutils/gcc: 59 commits discards c4a859d664b 204: onsuccess: #19: 2: Success after binutils/gcc: 39 commits discards f3133228a53 203: onsuccess: #18: 2: Success after binutils/gcc: 9 commits discards c6601d911ff 202: onsuccess: #17: 2: Success after binutils/gcc: 25 commits discards 86774e34583 201: onsuccess: #16: 2: Success after binutils/gcc: 55 commits discards cff792e1b72 200: onsuccess: #15: 2: Success after binutils/gcc: 26 commits discards 90f8ce35de9 199: onsuccess: #14: 2: Success after binutils/gcc: 31 commits discards 0fa6a723415 198: onsuccess: #13: 2: Success after binutils/gcc: 58 commits discards deb31ed3e65 197: onsuccess: #12: 2: Success after binutils/gcc: 29 commits discards a5ca1ce4a41 196: onsuccess: #11: 2: Success after binutils/gcc: 16 commits discards 83346dad0dc 195: onsuccess: #10: 2: Success after binutils/gcc: 28 commits discards d6b237f3ac2 194: onsuccess: #9: 2: Success after binutils/gcc: 48 commits discards 1415ef654be 193: onsuccess: #8: 2: Success after binutils/gcc: 37 commits discards 50964a1ed2d 192: onsuccess: #7: 2: Success after binutils/gcc: 22 commits discards 0b76f87fb96 191: onsuccess: #6: 2: Success after binutils/gcc: 65 commits discards c5885b1c401 190: onsuccess: #5: 2: Success after binutils/gcc: 23 commits discards c33fea659f4 189: onsuccess: #4: 2: Success after binutils/gcc: 8 commits discards d1bbba4c230 188: onsuccess: #3: 2: Success after binutils/gcc: 5 commits discards ba5c92b0671 187: onsuccess: #2: 2: Success after binutils/gcc: 22 commits discards e803c4df208 186: onsuccess: #1: 2: Success after binutils/gcc: 54 commits discards b02f5489923 185: onsuccess: #605: 2: Success after binutils/gcc: 38 commits discards f78df2f678e 184: onsuccess: #604: 2: Success after binutils/gcc: 138 commits discards ddca2667ff5 183: onsuccess: #603: 2: Success after binutils/gcc: 33 commits discards cc29ad8796d 182: onsuccess: #602: 2: Success after binutils/gcc: 32 commits discards a41f173376d 181: onsuccess: #601: 2: Success after binutils/gcc: 13 commits discards 3a79a835153 180: onsuccess: #600: 2: Success after binutils/gcc: 32 commits discards 02697a51e0c 179: onsuccess: #599: 2: Success after binutils/gcc: 27 commits discards eb5d266c19e 178: onsuccess: #598: 2: Success after binutils/gcc: 54 commits discards fb405414d5c 177: onsuccess: #597: 2: Success after binutils/gcc: 86 commits discards 778adebc1c4 176: onsuccess: #596: 2: Success after binutils/gcc: 84 commits discards 4cd9f896dc1 175: onsuccess: #595: 2: Success after binutils/gcc: 30 commits discards 3114378b258 174: onsuccess: #594: 2: Success after binutils/gcc: 147 commits discards 137f8b19b22 173: onsuccess: #593: 2: Success after binutils/gcc: 74 commits discards b3e31b4dd2a 172: onsuccess: #592: 2: Success after binutils/gcc: 57 commits discards bad41c3f123 171: onsuccess: #590: 2: Success after binutils/gcc: 21 commits discards dc39443e87e 170: onsuccess: #589: 2: Success after binutils/gcc: 28 commits discards 87b8ae61643 169: onsuccess: #588: 2: Success after binutils/gcc: 7 commits discards 7707ce61416 168: onsuccess: #587: 2: Success after binutils/gcc: 2 commits discards 5d2e52d5c00 167: onsuccess: #586: 2: Success after binutils/gcc: 16 commits discards 0aa316a31a7 166: onsuccess: #585: 2: Success after binutils/gcc: 59 commits discards 6283cdd4467 165: onsuccess: #584: 2: Success after binutils/gcc: 45 commits discards 1bcbd476e4b 164: onsuccess: #583: 2: Success after binutils/gcc: 110 commits discards 14c5be674ed 163: onsuccess: #582: 2: Success after binutils/gcc: 55 commits discards 7065264918d 162: onsuccess: #581: 2: Success after binutils/gcc: 6 commits discards 31953fa47d5 161: onsuccess: #580: 2: Success after binutils/gcc: 10 commits discards 04ebf9f72fe 160: onsuccess: #579: 2: Success after binutils/gcc: 17 commits discards c517a83a09b 159: onsuccess: #578: 2: Success after binutils/gcc: 130 commits discards 3cd4ae30e26 158: onsuccess: #577: 2: Success after binutils/gcc: 27 commits discards cfce5694cc4 157: onsuccess: #576: 2: Success after binutils/gcc: 80 commits discards d5662b957b6 156: onsuccess: #575: 2: Success after binutils/gcc: 27 commits discards d71b3412e6d 155: onsuccess: #574: 2: Success after binutils/gcc: 36 commits discards 7ff3867f3bc 154: onsuccess: #573: 2: Success after binutils/gcc: 6 commits discards 89bfcbd2714 153: onsuccess: #572: 2: Success after binutils/gcc: 28 commits discards b8030595a5a 152: onsuccess: #571: 2: Success after binutils/gcc: 43 commits discards bc65b102a3a 151: onsuccess: #570: 2: Success after binutils/gcc: 36 commits discards 976a660cf44 150: onsuccess: #569: 2: Success after binutils/gcc: 32 commits discards c61940f4743 149: onsuccess: #568: 2: Success after binutils/gcc: 69 commits discards aabcecb5833 148: onsuccess: #567: 2: Success after binutils/gcc: 128 commits discards e5c250c8aee 147: onsuccess: #566: 2: Success after binutils/gcc: 50 commits discards 54ee2723edd 146: onsuccess: #565: 2: Success after binutils/gcc: 115 commits discards 176883354bb 145: onsuccess: #564: 2: Success after binutils/gcc: 30 commits discards c3abe10ea7e 144: onsuccess: #563: 2: Success after binutils/gcc: 4 commits discards 186a55fbf02 143: onsuccess: #562: 2: Success after binutils/gcc: 6 commits discards 606fd9ffa53 142: onsuccess: #561: 2: Success after binutils/gcc: 176 commits discards 0a1f9a21f59 141: onsuccess: #559: 1: Success after gcc: 4 commits discards ce49033aeb7 140: force: #558: 1: Failure after basepoints/gcc-13-4953-g [...] discards 5012317767e 139: force: #557: 2: Success after gcc: 6 commits discards fa823c32ba2 138: onsuccess: #554: 2: Success after binutils: 10 commits discards 10aa1472693 137: onsuccess: #552: 2: Success after binutils/gcc: 18 commits discards 3094652b9ae 136: onsuccess: #551: 2: Success after binutils/gcc: 18 commits discards fff72b5d7ed 135: onsuccess: #550: 2: Success after binutils/gcc: 31 commits discards feb1a52aab2 134: onsuccess: #549: 2: Success after binutils/gcc: 9 commits discards 2b1ff0c1082 133: onsuccess: #548: 2: Success after binutils/gcc: 29 commits discards e1662f7f641 132: onsuccess: #547: 2: Success after binutils/gcc: 7 commits discards cdc5bfefa8e 131: onsuccess: #546: 2: Success after binutils/gcc: 24 commits discards 63d10918031 130: onsuccess: #545: 2: Success after binutils/gcc: 9 commits discards 37259d36e17 129: onsuccess: #544: 2: Success after binutils/gcc: 79 commits discards 79a68f3fc21 128: onsuccess: #543: 2: Success after binutils/gcc: 52 commits discards ea64cc81c14 127: onsuccess: #542: 2: Success after binutils/gcc: 66 commits discards 300ec77b1e5 126: onsuccess: #541: 2: Success after binutils/gcc: 17 commits discards d0a23baf291 125: onsuccess: #540: 2: Success after binutils/gcc: 53 commits discards 1ab48fc5dfe 124: onsuccess: #539: 2: Success after binutils/gcc: 9 commits discards 6711b2b52ec 123: onsuccess: #538: 2: Success after binutils/gcc: 14 commits discards be13a7307e5 122: onsuccess: #537: 2: Success after binutils/gcc: 36 commits discards 5b01153178a 121: onsuccess: #536: 1: Success after binutils/gcc: 76 commits discards bfd45d0dc4c 120: onsuccess: #535: 1: Success after binutils: 10 commits discards 9a4396eb79e 119: force: #534: 1: Failure after gdb-12-branchpoint-3046- [...] discards da5012c6ee8 118: force: #533: 2: Success after binutils: 4 commits discards 5d309364085 117: onsuccess: #531: 2: Success after gcc: 65 commits discards 422753eaeb1 116: onsuccess: #528: 2: Success after binutils/gcc: 48 commits discards 8b29633f1bf 115: onsuccess: #527: 2: Success after binutils/gcc: 11 commits discards 7ae3ba87151 114: onsuccess: #526: 2: Success after binutils/gcc: 3 commits discards 93e59e99ab8 113: onsuccess: #525: 2: Success after binutils/gcc: 35 commits discards 4aee934c5f0 112: onsuccess: #524: 2: Success after binutils/gcc: 32 commits discards 028f75d4fbd 111: onsuccess: #523: 2: Success after binutils/gcc: 26 commits new 4b80cde4071 111: onsuccess: #523: 2: Success after binutils/gcc: 26 commits new e056abeeff3 112: onsuccess: #524: 2: Success after binutils/gcc: 32 commits new a9b51f9ebe6 113: onsuccess: #525: 2: Success after binutils/gcc: 35 commits new 6ddfeb4c046 114: onsuccess: #526: 2: Success after binutils/gcc: 3 commits new 9b2a2120a62 115: onsuccess: #527: 2: Success after binutils/gcc: 11 commits new 89aabae787f 116: onsuccess: #528: 2: Success after binutils/gcc: 48 commits new 7f75db353f9 117: onsuccess: #531: 2: Success after gcc: 65 commits new f0e09be0437 118: force: #533: 2: Success after binutils: 4 commits new 54295f82a8c 119: force: #534: 1: Failure after gdb-12-branchpoint-3046- [...] new 130a19a71aa 120: onsuccess: #535: 1: Success after binutils: 10 commits new dcefe3e7c22 121: onsuccess: #536: 1: Success after binutils/gcc: 76 commits new 01f60b7e047 122: onsuccess: #537: 2: Success after binutils/gcc: 36 commits new e4a3f8f336d 123: onsuccess: #538: 2: Success after binutils/gcc: 14 commits new 4889dd2921d 124: onsuccess: #539: 2: Success after binutils/gcc: 9 commits new 535a1ce7bc8 125: onsuccess: #540: 2: Success after binutils/gcc: 53 commits new 513ad3748ff 126: onsuccess: #541: 2: Success after binutils/gcc: 17 commits new 5a76de66dd9 127: onsuccess: #542: 2: Success after binutils/gcc: 66 commits new aa066870c9b 128: onsuccess: #543: 2: Success after binutils/gcc: 52 commits new a15c589c18c 129: onsuccess: #544: 2: Success after binutils/gcc: 79 commits new 2ddc1403c24 130: onsuccess: #545: 2: Success after binutils/gcc: 9 commits new 76af2be307b 131: onsuccess: #546: 2: Success after binutils/gcc: 24 commits new d132beba715 132: onsuccess: #547: 2: Success after binutils/gcc: 7 commits new 22570f835df 133: onsuccess: #548: 2: Success after binutils/gcc: 29 commits new 453f6588bf1 134: onsuccess: #549: 2: Success after binutils/gcc: 9 commits new ea3aa102656 135: onsuccess: #550: 2: Success after binutils/gcc: 31 commits new f1c08feb313 136: onsuccess: #551: 2: Success after binutils/gcc: 18 commits new 50f368fb8b4 137: onsuccess: #552: 2: Success after binutils/gcc: 18 commits new 3b255d0b17f 138: onsuccess: #554: 2: Success after binutils: 10 commits new 13dca9f737e 139: force: #557: 2: Success after gcc: 6 commits new bfe5f601bf6 140: force: #558: 1: Failure after basepoints/gcc-13-4953-g [...] new dacc3b19c1d 141: onsuccess: #559: 1: Success after gcc: 4 commits new 342207cd3c9 142: onsuccess: #561: 2: Success after binutils/gcc: 176 commits new 5f4ef8525d3 143: onsuccess: #562: 2: Success after binutils/gcc: 6 commits new e0df6798dbd 144: onsuccess: #563: 2: Success after binutils/gcc: 4 commits new ba6c2e6eaa2 145: onsuccess: #564: 2: Success after binutils/gcc: 30 commits new d92a72d6861 146: onsuccess: #565: 2: Success after binutils/gcc: 115 commits new 87072ea718d 147: onsuccess: #566: 2: Success after binutils/gcc: 50 commits new cf5e12b9b22 148: onsuccess: #567: 2: Success after binutils/gcc: 128 commits new 967d61ebc67 149: onsuccess: #568: 2: Success after binutils/gcc: 69 commits new a1ed0e279d1 150: onsuccess: #569: 2: Success after binutils/gcc: 32 commits new 58eacaee8a0 151: onsuccess: #570: 2: Success after binutils/gcc: 36 commits new 4bcfb0c12b3 152: onsuccess: #571: 2: Success after binutils/gcc: 43 commits new ed76086d05b 153: onsuccess: #572: 2: Success after binutils/gcc: 28 commits new 7402d5984f3 154: onsuccess: #573: 2: Success after binutils/gcc: 6 commits new 8e764e2ef9f 155: onsuccess: #574: 2: Success after binutils/gcc: 36 commits new 6f83c7cf26d 156: onsuccess: #575: 2: Success after binutils/gcc: 27 commits new 45e6d1a89ee 157: onsuccess: #576: 2: Success after binutils/gcc: 80 commits new 740272b0839 158: onsuccess: #577: 2: Success after binutils/gcc: 27 commits new 127dd371606 159: onsuccess: #578: 2: Success after binutils/gcc: 130 commits new 47ed976dcbb 160: onsuccess: #579: 2: Success after binutils/gcc: 17 commits new f21b4fc5efa 161: onsuccess: #580: 2: Success after binutils/gcc: 10 commits new fcce7a7db95 162: onsuccess: #581: 2: Success after binutils/gcc: 6 commits new 2afe92e1343 163: onsuccess: #582: 2: Success after binutils/gcc: 55 commits new ed11bf1dda1 164: onsuccess: #583: 2: Success after binutils/gcc: 110 commits new fcf1fdf7e0f 165: onsuccess: #584: 2: Success after binutils/gcc: 45 commits new 2082328dce0 166: onsuccess: #585: 2: Success after binutils/gcc: 59 commits new e24defd2c39 167: onsuccess: #586: 2: Success after binutils/gcc: 16 commits new 046f9f5faa2 168: onsuccess: #587: 2: Success after binutils/gcc: 2 commits new 836ecdeeb1b 169: onsuccess: #588: 2: Success after binutils/gcc: 7 commits new 8c040421162 170: onsuccess: #589: 2: Success after binutils/gcc: 28 commits new 29d8f722a77 171: onsuccess: #590: 2: Success after binutils/gcc: 21 commits new 57865a3141a 172: onsuccess: #592: 2: Success after binutils/gcc: 57 commits new 3144c7ce602 173: onsuccess: #593: 2: Success after binutils/gcc: 74 commits new 207416da210 174: onsuccess: #594: 2: Success after binutils/gcc: 147 commits new ee15bb675f0 175: onsuccess: #595: 2: Success after binutils/gcc: 30 commits new e5cc5ac99a2 176: onsuccess: #596: 2: Success after binutils/gcc: 84 commits new e39dcd884e1 177: onsuccess: #597: 2: Success after binutils/gcc: 86 commits new bb61876c19a 178: onsuccess: #598: 2: Success after binutils/gcc: 54 commits new b2cfd1e8016 179: onsuccess: #599: 2: Success after binutils/gcc: 27 commits new 9b1c4f4d7dd 180: onsuccess: #600: 2: Success after binutils/gcc: 32 commits new 420ce34fd22 181: onsuccess: #601: 2: Success after binutils/gcc: 13 commits new 9cc10067fbb 182: onsuccess: #602: 2: Success after binutils/gcc: 32 commits new 9e65ba26375 183: onsuccess: #603: 2: Success after binutils/gcc: 33 commits new 95907458656 184: onsuccess: #604: 2: Success after binutils/gcc: 138 commits new f43c655b074 185: onsuccess: #605: 2: Success after binutils/gcc: 38 commits new 2d2fe7aed6f 186: onsuccess: #1: 2: Success after binutils/gcc: 54 commits new 51db723150d 187: onsuccess: #2: 2: Success after binutils/gcc: 22 commits new 157730607d4 188: onsuccess: #3: 2: Success after binutils/gcc: 5 commits new b8409f535cd 189: onsuccess: #4: 2: Success after binutils/gcc: 8 commits new f6d53064f6e 190: onsuccess: #5: 2: Success after binutils/gcc: 23 commits new b50b5e15c6f 191: onsuccess: #6: 2: Success after binutils/gcc: 65 commits new 543c4c03de3 192: onsuccess: #7: 2: Success after binutils/gcc: 22 commits new ce007b1ce8b 193: onsuccess: #8: 2: Success after binutils/gcc: 37 commits new fdd150159e3 194: onsuccess: #9: 2: Success after binutils/gcc: 48 commits new 53a9acca04a 195: onsuccess: #10: 2: Success after binutils/gcc: 28 commits new 5b2c4d5f4c9 196: onsuccess: #11: 2: Success after binutils/gcc: 16 commits new e5f841351c9 197: onsuccess: #12: 2: Success after binutils/gcc: 29 commits new 1dc8e31ee86 198: onsuccess: #13: 2: Success after binutils/gcc: 58 commits new 95ad7ee018c 199: onsuccess: #14: 2: Success after binutils/gcc: 31 commits new 66ecb21296c 200: onsuccess: #15: 2: Success after binutils/gcc: 26 commits new dff5f0901a7 201: onsuccess: #16: 2: Success after binutils/gcc: 55 commits new 32af0db6bce 202: onsuccess: #17: 2: Success after binutils/gcc: 25 commits new 29b77e77b27 203: onsuccess: #18: 2: Success after binutils/gcc: 9 commits new 19b8b42641c 204: onsuccess: #19: 2: Success after binutils/gcc: 39 commits new a3362048693 205: onsuccess: #20: 2: Success after binutils/gcc: 59 commits new 3769e3a4a8f 206: onsuccess: #21: 2: Success after binutils/gcc: 38 commits new bcc66e57471 207: onsuccess: #23: 2: Success after binutils/gcc: 75 commits new e3471eba6fc 208: onsuccess: #24: 2: Success after binutils/gcc: 44 commits new 618e34c249d 209: onsuccess: #25: 2: Success after binutils/gcc: 12 commits new c6150c41f99 210: onsuccess: #26: 2: Success after binutils/gcc: 27 commits new bdbec87611b 211: onsuccess: #27: 2: Success after binutils/gcc: 41 commits new c8486b659eb 212: onsuccess: #28: 2: Success after binutils/gcc: 34 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 (541625244f5) \ N -- N -- N refs/heads/linaro-local/ci/tcwg_gcc_bootstrap/master-aar [...] 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 1752 -> 1928 bytes 02-prepare_abe/console.log.xz | Bin 2484 -> 2500 bytes 04-build_abe-binutils/console.log.xz | Bin 35204 -> 35164 bytes 05-build_abe-bootstrap_profiled_lto/console.log.xz | Bin 304092 -> 305804 bytes 06-check_regression/console.log.xz | Bin 3096 -> 3084 bytes 07-update_baseline/console.log | 40 ++++++++++----------- 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 +++++------ 13 files changed, 36 insertions(+), 36 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 3 months

[binutils-gdb] branch master updated (bf3f6c02d73 -> 1c3b2b83dc2)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. unknown user pushed a change to branch master in repository binutils-gdb. from bf3f6c02d73 [gdb/testsuite] Fix gdb.cp/cp-relocate.exp for remote host new 1c3b2b83dc2 gdb/testsuite: adjust test cases to previous "maintenance i [...] 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/testsuite/gdb.base/maint.exp | 8 ++++---- gdb/testsuite/gdb.dwarf2/dw2-out-of-range-end-of-seq.exp | 4 ++-- gdb/testsuite/gdb.dwarf2/dw2-ranges-base.exp | 6 +++--- 3 files changed, 9 insertions(+), 9 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 3 months

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_gnu_native_check_gcc/master-arm updated (281d28dfead -> 609e86e4415)

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_gcc/master-arm in repository toolchain/ci/base-artifacts. discards 281d28dfead 227: onsuccess: #27: 1: Success after binutils/gcc/linux/gd [...] discards 02fd1382745 226: onsuccess: #26: 1: Success after binutils/gcc/linux/gd [...] discards fa0c36480c0 225: onsuccess: #25: 1: Success after binutils/gcc/linux/gd [...] discards 4ea3d22989f 224: onsuccess: #21: 1: Success after binutils/gcc/linux/gl [...] discards b921ef0bdef 223: onsuccess: #20: 1: Success after binutils/gcc/linux/gl [...] discards 7c60e5b21f8 222: onsuccess: #19: 1: Success after binutils/gcc/linux/gl [...] discards a0fab6fa77a 221: onsuccess: #18: 1: Success after binutils/gcc/linux/gd [...] discards 33b0cf1bfca 220: onsuccess: #17: 1: Success after binutils/gcc/linux/gl [...] discards 6a4494f16eb 219: onsuccess: #16: 1: Success after binutils/gcc/linux/gl [...] discards f89f3a7869a 218: onsuccess: #15: 1: Success after binutils/gcc/linux/gl [...] discards a6d6e432762 217: onsuccess: #14: 1: Success after binutils/gcc/linux/gl [...] discards 226931e58cf 216: onsuccess: #12: 1: Success after binutils/gcc/linux/gl [...] discards affcc0d8c02 215: onsuccess: #11: 1: Success after binutils/gcc/linux/gd [...] discards 862bf3d55b4 214: onsuccess: #10: 1: Success after binutils/gcc/linux/gd [...] discards 5f3949107fc 213: onsuccess: #9: 1: Success after binutils/gcc/linux/gli [...] discards 82224aa9c8c 212: onsuccess: #8: 1: Success after binutils/gcc/linux/gli [...] discards 4a643caa416 211: onsuccess: #7: 1: Success after binutils/gcc/linux/gdb [...] discards 7c265a61256 210: onsuccess: #6: 1: Success after binutils/gcc/linux/gli [...] discards 3c7ce95831e 209: onsuccess: #5: 1: Success after binutils/gcc/linux/gli [...] discards 11f83068384 208: onsuccess: #4: 1: Success after binutils/gcc/linux/gli [...] discards a3903094b20 207: onsuccess: #3: 1: Success after binutils/gcc/linux/gdb [...] discards e168cc5e31d 206: onsuccess: #2: 1: Success after binutils/gcc/linux/gli [...] discards 6668e05a208 205: onsuccess: #1: 1: Success after binutils/gcc/linux/gli [...] discards 73722c18f63 204: onsuccess: #672: 1: Success after binutils/gcc/linux/g [...] discards 2a3c931f753 203: onsuccess: #671: 1: Success after binutils/gcc/linux/g [...] discards 208b85c1ff8 202: onsuccess: #670: 1: Success after binutils/gcc/linux/g [...] discards 8dd515691bc 201: onsuccess: #664: 1: Success after binutils/gcc/glibc/g [...] discards 1704db54c07 200: onsuccess: #663: 1: Success after binutils/gcc/linux/g [...] discards 21ba5a3399c 199: onsuccess: #662: 1: Success after binutils/gcc/linux/g [...] discards 7ab84b6be81 198: onsuccess: #661: 1: Success after binutils/gcc/linux/g [...] discards 447e4b0c6fe 197: onsuccess: #660: 1: Success after binutils/gcc/linux/g [...] discards a5b339e248d 196: onsuccess: #659: 1: Success after binutils/gcc/linux/g [...] discards 6b002a5f2f7 195: onsuccess: #657: 1: Success after binutils/gcc/linux/g [...] discards 9379b574b33 194: onsuccess: #656: 1: Success after binutils/gcc/linux/g [...] discards b482ef50b5a 193: onsuccess: #655: 1: Success after binutils/gcc/linux/g [...] discards d3c3684820b 192: onsuccess: #654: 1: Success after binutils/gcc/linux/g [...] discards 0bde67e4d47 191: onsuccess: #653: 1: Success after binutils/gcc/linux/g [...] discards 05dde24efdd 190: onsuccess: #652: 1: Success after binutils/gcc/linux/g [...] discards ebeb64f31e0 189: onsuccess: #651: 1: Success after binutils/gcc/linux/g [...] discards 91fd72cc52e 188: onsuccess: #650: 1: Success after binutils/gcc/linux/g [...] discards ce4cb1d6828 187: onsuccess: #649: 1: Success after binutils/gcc/linux/g [...] discards 22fcaa34916 186: onsuccess: #648: 1: Success after binutils/gcc/linux/g [...] discards 3f5337e953c 185: onsuccess: #647: 1: Success after binutils/gcc/linux/g [...] discards 66b7bf01629 184: onsuccess: #646: 1: Success after binutils/gcc/linux/g [...] discards 8fc6dc5b9fd 183: onsuccess: #645: 1: Success after binutils/gcc/gdb: 20 [...] discards 4732786c400 182: onsuccess: #644: 1: Success after binutils/gcc/gdb: 30 [...] discards e53f19a8983 181: onsuccess: #643: 1: Success after binutils/gcc/linux/g [...] discards 6294557d98d 180: onsuccess: #642: 1: Success after binutils/gcc/linux/g [...] discards f1494577cca 179: onsuccess: #641: 1: Success after binutils/gcc/linux/g [...] discards 0346ee56d52 178: onsuccess: #640: 1: Success after binutils/gcc/linux/g [...] discards e38ad16475a 177: onsuccess: #639: 1: Success after binutils/gcc/linux/g [...] discards 42d35303cfe 176: onsuccess: #638: 1: Success after binutils/gcc/linux/g [...] discards 6cdc3bbbf2f 175: onsuccess: #637: 1: Success after binutils/gcc/linux/g [...] discards cb777bf8df8 174: onsuccess: #636: 1: Success after binutils/gcc/linux/g [...] discards b041489db42 173: onsuccess: #635: 1: Success after binutils/gcc/linux/g [...] discards c2cf4551ed3 172: onsuccess: #634: 1: Success after binutils/gcc/linux/g [...] discards df27d2bc6f8 171: onsuccess: #633: 1: Success after binutils/gcc/linux/g [...] discards 6cfe6d7f64c 170: onsuccess: #632: 1: Success after binutils/gcc/linux/g [...] discards 594da3f18e7 169: onsuccess: #631: 1: Success after binutils/gcc/linux/g [...] discards 344f5bff566 168: onsuccess: #630: 1: Success after binutils/gcc/linux/g [...] discards ee5ad6b4f67 167: onsuccess: #629: 1: Success after binutils/gcc/linux/g [...] discards 68094f837f3 166: onsuccess: #628: 1: Success after binutils/gcc/linux/g [...] discards 35ae7b3c6f8 165: onsuccess: #627: 1: Success after binutils/gcc/linux/g [...] discards 19f91029165 164: onsuccess: #626: 1: Success after binutils/gcc/linux/g [...] discards 115ccda244a 163: onsuccess: #625: 1: Success after binutils/gcc/glibc/g [...] discards 88dcf6bff94 162: onsuccess: #624: 1: Success after linux: 10 commits discards d8d6261b1dd 161: onsuccess: #623: 1: Success after glibc: 9 commits discards e2329eb68fe 160: onsuccess: #621: 1: Success after gcc: 11 commits discards dfee1d341e4 159: onsuccess: #620: 1: Success after binutils: 12 commits discards 698b9cb8413 158: onsuccess: #618: 1: Success after binutils/gcc/linux/g [...] discards 191512e205e 157: onsuccess: #617: 1: Success after binutils/gcc/linux/g [...] discards 66dcb6224f3 156: onsuccess: #616: 1: Success after binutils/gcc/linux/g [...] discards 51eb0e81d24 155: onsuccess: #615: 1: Success after binutils/gcc/linux/g [...] discards 8caa5a4009a 154: onsuccess: #614: 1: Success after binutils/gcc/gdb: 14 [...] discards f37103dc474 153: onsuccess: #613: 1: Success after binutils/gcc/gdb: 40 [...] discards dc3f284013d 152: onsuccess: #612: 1: Success after binutils/gcc/gdb: 11 [...] discards 19bf265f75b 151: onsuccess: #611: 1: Success after binutils/gcc/linux/g [...] discards 5b40fab9898 150: onsuccess: #610: 1: Success after binutils/gcc/linux/g [...] discards f83b23e32d1 149: onsuccess: #609: 1: Success after binutils/gcc/linux/g [...] discards 3451700a883 148: onsuccess: #608: 1: Success after binutils/gcc/linux/g [...] discards 8b0d90f9c91 147: onsuccess: #607: 1: Success after binutils/gcc/linux/g [...] discards b8065bdf0a6 146: onsuccess: #606: 1: Success after binutils/gcc/linux/g [...] discards 76102eb9e36 145: onsuccess: #605: 1: Success after binutils/gcc/linux/g [...] discards 2bdbb55a333 144: onsuccess: #604: 1: Success after binutils/gcc/gdb: 14 [...] discards 8f9706f39c7 143: onsuccess: #603: 1: Success after binutils/gcc/linux/g [...] discards 0a0d4d6b36f 142: onsuccess: #602: 1: Success after binutils/gcc/linux/g [...] discards 18899583b69 141: onsuccess: #601: 1: Success after linux: 794 commits discards 8c91d2784b9 140: onsuccess: #600: 1: Success after gcc: 23 commits discards 11aa4c3808a 139: onsuccess: #599: 1: Success after binutils: 10 commits discards a0488bd0394 138: onsuccess: #597: 1: Success after binutils/gcc/linux/g [...] discards 0ad05732b38 137: onsuccess: #596: 1: Success after binutils/gcc/linux/g [...] discards 118f61f8a01 136: onsuccess: #595: 1: Success after binutils/gcc/linux/g [...] discards e5bc7131a42 135: onsuccess: #594: 1: Success after binutils/gcc/linux/g [...] discards 1e7eada4def 134: onsuccess: #593: 1: Success after binutils/gcc/linux/g [...] discards 9e1ffb3e1cb 133: onsuccess: #592: 1: Success after binutils/gcc/linux/g [...] discards 3d4692e0dc7 132: onsuccess: #591: 1: Success after binutils/gcc/linux/g [...] discards 208bb6ec2a2 131: onsuccess: #590: 1: Success after binutils/gcc/linux/g [...] discards d89143d8603 130: onsuccess: #589: 1: Success after binutils/gcc/linux/g [...] discards 7b5923cd3f3 129: onsuccess: #588: 1: Success after linux: 4 commits discards f4b8ead6617 128: onsuccess: #586: 1: Success after binutils: 22 commits discards f620e2bd3f2 127: onsuccess: #584: 1: Success after linux: 21 commits new 90885c2de89 127: onsuccess: #584: 1: Success after linux: 21 commits new 54e16e8a9ee 128: onsuccess: #586: 1: Success after binutils: 22 commits new 116118980ba 129: onsuccess: #588: 1: Success after linux: 4 commits new 5d27225e2e0 130: onsuccess: #589: 1: Success after binutils/gcc/linux/g [...] new d8d4d1944ce 131: onsuccess: #590: 1: Success after binutils/gcc/linux/g [...] new d338cae2ade 132: onsuccess: #591: 1: Success after binutils/gcc/linux/g [...] new ee2db3895ad 133: onsuccess: #592: 1: Success after binutils/gcc/linux/g [...] new 5f4b6f3ca70 134: onsuccess: #593: 1: Success after binutils/gcc/linux/g [...] new a40b79b0388 135: onsuccess: #594: 1: Success after binutils/gcc/linux/g [...] new 2ce87284f4e 136: onsuccess: #595: 1: Success after binutils/gcc/linux/g [...] new 4d8d1a0c785 137: onsuccess: #596: 1: Success after binutils/gcc/linux/g [...] new ed03b354ac2 138: onsuccess: #597: 1: Success after binutils/gcc/linux/g [...] new 5e03bca1c17 139: onsuccess: #599: 1: Success after binutils: 10 commits new a5b5483e110 140: onsuccess: #600: 1: Success after gcc: 23 commits new 9a12db58243 141: onsuccess: #601: 1: Success after linux: 794 commits new b3abb86dcfb 142: onsuccess: #602: 1: Success after binutils/gcc/linux/g [...] new 8caa2c689a8 143: onsuccess: #603: 1: Success after binutils/gcc/linux/g [...] new 5a5fa2023a7 144: onsuccess: #604: 1: Success after binutils/gcc/gdb: 14 [...] new 54df84ce860 145: onsuccess: #605: 1: Success after binutils/gcc/linux/g [...] new 56cf845a932 146: onsuccess: #606: 1: Success after binutils/gcc/linux/g [...] new 146bbb83014 147: onsuccess: #607: 1: Success after binutils/gcc/linux/g [...] new 76f45ae8b0b 148: onsuccess: #608: 1: Success after binutils/gcc/linux/g [...] new a9ac3e631f8 149: onsuccess: #609: 1: Success after binutils/gcc/linux/g [...] new 6c3bae3164e 150: onsuccess: #610: 1: Success after binutils/gcc/linux/g [...] new 7f5ca61fa16 151: onsuccess: #611: 1: Success after binutils/gcc/linux/g [...] new c965397e54f 152: onsuccess: #612: 1: Success after binutils/gcc/gdb: 11 [...] new c985d51ee8b 153: onsuccess: #613: 1: Success after binutils/gcc/gdb: 40 [...] new aebc19515d8 154: onsuccess: #614: 1: Success after binutils/gcc/gdb: 14 [...] new ea7812cfec7 155: onsuccess: #615: 1: Success after binutils/gcc/linux/g [...] new 25394ad1f23 156: onsuccess: #616: 1: Success after binutils/gcc/linux/g [...] new 273352ecccf 157: onsuccess: #617: 1: Success after binutils/gcc/linux/g [...] new e58323db238 158: onsuccess: #618: 1: Success after binutils/gcc/linux/g [...] new bea9c3f85d8 159: onsuccess: #620: 1: Success after binutils: 12 commits new 9a63000edd8 160: onsuccess: #621: 1: Success after gcc: 11 commits new 4d0170a317c 161: onsuccess: #623: 1: Success after glibc: 9 commits new 3ddeafa0263 162: onsuccess: #624: 1: Success after linux: 10 commits new 7697e2f025a 163: onsuccess: #625: 1: Success after binutils/gcc/glibc/g [...] new 59c419d0577 164: onsuccess: #626: 1: Success after binutils/gcc/linux/g [...] new 7078c59d2b2 165: onsuccess: #627: 1: Success after binutils/gcc/linux/g [...] new c239b332ea0 166: onsuccess: #628: 1: Success after binutils/gcc/linux/g [...] new 183ac8b1fe9 167: onsuccess: #629: 1: Success after binutils/gcc/linux/g [...] new 3953af1c439 168: onsuccess: #630: 1: Success after binutils/gcc/linux/g [...] new 269cc897e9c 169: onsuccess: #631: 1: Success after binutils/gcc/linux/g [...] new 798a006ab7e 170: onsuccess: #632: 1: Success after binutils/gcc/linux/g [...] new b1d3a168c64 171: onsuccess: #633: 1: Success after binutils/gcc/linux/g [...] new 8007764c5d7 172: onsuccess: #634: 1: Success after binutils/gcc/linux/g [...] new 52e05a22996 173: onsuccess: #635: 1: Success after binutils/gcc/linux/g [...] new 1d972328350 174: onsuccess: #636: 1: Success after binutils/gcc/linux/g [...] new 5b7faa16483 175: onsuccess: #637: 1: Success after binutils/gcc/linux/g [...] new a2546e7b2ef 176: onsuccess: #638: 1: Success after binutils/gcc/linux/g [...] new 6f1bdb16e4f 177: onsuccess: #639: 1: Success after binutils/gcc/linux/g [...] new 8a37e6b9269 178: onsuccess: #640: 1: Success after binutils/gcc/linux/g [...] new 9112621b46c 179: onsuccess: #641: 1: Success after binutils/gcc/linux/g [...] new a5210a8a3fe 180: onsuccess: #642: 1: Success after binutils/gcc/linux/g [...] new bd890ba69ac 181: onsuccess: #643: 1: Success after binutils/gcc/linux/g [...] new 8324b5b8577 182: onsuccess: #644: 1: Success after binutils/gcc/gdb: 30 [...] new f5281fb95e3 183: onsuccess: #645: 1: Success after binutils/gcc/gdb: 20 [...] new 22e3330f06d 184: onsuccess: #646: 1: Success after binutils/gcc/linux/g [...] new a343af4007e 185: onsuccess: #647: 1: Success after binutils/gcc/linux/g [...] new e562c58c96f 186: onsuccess: #648: 1: Success after binutils/gcc/linux/g [...] new 00bd5ab59e2 187: onsuccess: #649: 1: Success after binutils/gcc/linux/g [...] new f7e907af5ce 188: onsuccess: #650: 1: Success after binutils/gcc/linux/g [...] new 4f6c6247203 189: onsuccess: #651: 1: Success after binutils/gcc/linux/g [...] new 6ab2a981a14 190: onsuccess: #652: 1: Success after binutils/gcc/linux/g [...] new f688530775f 191: onsuccess: #653: 1: Success after binutils/gcc/linux/g [...] new dba59e01a9a 192: onsuccess: #654: 1: Success after binutils/gcc/linux/g [...] new e1431874691 193: onsuccess: #655: 1: Success after binutils/gcc/linux/g [...] new f459c97f759 194: onsuccess: #656: 1: Success after binutils/gcc/linux/g [...] new 9ee40c344a3 195: onsuccess: #657: 1: Success after binutils/gcc/linux/g [...] new 2e6b96a8c65 196: onsuccess: #659: 1: Success after binutils/gcc/linux/g [...] new 9c82d457f70 197: onsuccess: #660: 1: Success after binutils/gcc/linux/g [...] new 37692d29aaa 198: onsuccess: #661: 1: Success after binutils/gcc/linux/g [...] new 7f309b9a70a 199: onsuccess: #662: 1: Success after binutils/gcc/linux/g [...] new 8ac784be2cb 200: onsuccess: #663: 1: Success after binutils/gcc/linux/g [...] new 2350927f993 201: onsuccess: #664: 1: Success after binutils/gcc/glibc/g [...] new 802005d0013 202: onsuccess: #670: 1: Success after binutils/gcc/linux/g [...] new f6d3ff426dc 203: onsuccess: #671: 1: Success after binutils/gcc/linux/g [...] new 0803601c623 204: onsuccess: #672: 1: Success after binutils/gcc/linux/g [...] new b926b71bc1d 205: onsuccess: #1: 1: Success after binutils/gcc/linux/gli [...] new 8a99a8297cd 206: onsuccess: #2: 1: Success after binutils/gcc/linux/gli [...] new 8dfa428d5d3 207: onsuccess: #3: 1: Success after binutils/gcc/linux/gdb [...] new 44df691f6df 208: onsuccess: #4: 1: Success after binutils/gcc/linux/gli [...] new 0f17d57cc72 209: onsuccess: #5: 1: Success after binutils/gcc/linux/gli [...] new a75a4d2182c 210: onsuccess: #6: 1: Success after binutils/gcc/linux/gli [...] new 437765485a0 211: onsuccess: #7: 1: Success after binutils/gcc/linux/gdb [...] new 6e7db891263 212: onsuccess: #8: 1: Success after binutils/gcc/linux/gli [...] new e76413aeed6 213: onsuccess: #9: 1: Success after binutils/gcc/linux/gli [...] new a9fdf817641 214: onsuccess: #10: 1: Success after binutils/gcc/linux/gd [...] new 4e0d7c2c19f 215: onsuccess: #11: 1: Success after binutils/gcc/linux/gd [...] new cb852f68d74 216: onsuccess: #12: 1: Success after binutils/gcc/linux/gl [...] new 5adcff13a91 217: onsuccess: #14: 1: Success after binutils/gcc/linux/gl [...] new 4cdd9e52362 218: onsuccess: #15: 1: Success after binutils/gcc/linux/gl [...] new 43a01c2cf74 219: onsuccess: #16: 1: Success after binutils/gcc/linux/gl [...] new 3b78c2e4d6a 220: onsuccess: #17: 1: Success after binutils/gcc/linux/gl [...] new a812ece8bd9 221: onsuccess: #18: 1: Success after binutils/gcc/linux/gd [...] new 2736333baee 222: onsuccess: #19: 1: Success after binutils/gcc/linux/gl [...] new 9621aaeb497 223: onsuccess: #20: 1: Success after binutils/gcc/linux/gl [...] new 9567119fb60 224: onsuccess: #21: 1: Success after binutils/gcc/linux/gl [...] new 3a04281a868 225: onsuccess: #25: 1: Success after binutils/gcc/linux/gd [...] new dbf636b0283 226: onsuccess: #26: 1: Success after binutils/gcc/linux/gd [...] new df0e1d40ab2 227: onsuccess: #27: 1: Success after binutils/gcc/linux/gd [...] new 609e86e4415 228: onsuccess: #28: 1: Success after binutils/gcc/linux/gl [...] 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 (281d28dfead) \ N -- N -- N refs/heads/linaro-local/ci/tcwg_gnu_native_check_gcc/mas [...] 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 1748 -> 2040 bytes 02-prepare_abe/console.log.xz | Bin 2504 -> 2516 bytes 03-build_abe-binutils/console.log.xz | Bin 49216 -> 48968 bytes 04-build_abe-gcc/console.log.xz | Bin 236148 -> 237688 bytes 05-clean_sysroot/console.log.xz | Bin 316 -> 316 bytes 06-build_abe-linux/console.log.xz | Bin 8396 -> 8388 bytes 07-build_abe-glibc/console.log.xz | Bin 232532 -> 233788 bytes 08-build_abe-gdb/console.log.xz | Bin 46688 -> 47436 bytes 09-build_abe-dejagnu/console.log.xz | Bin 3784 -> 3820 bytes 10-build_abe-check_gcc/console.log.xz | Bin 10936 -> 9304 bytes 11-check_regression/console.log.xz | Bin 5604 -> 5576 bytes 11-check_regression/results.compare | 26 +- 11-check_regression/results.compare2 | 121 +- 12-update_baseline/console.log | 68 +- dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- git/gdb_rev | 2 +- git/glibc_rev | 2 +- git/linux_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 2 +- mail/mail-subject.txt | 2 +- manifest.sh | 38 +- sumfiles/g++.log.sep.xz | Bin 101148 -> 63168 bytes sumfiles/g++.log.xz | Bin 2879124 -> 2904900 bytes sumfiles/g++.sum | 24 +- sumfiles/g++.sum.sep | 8125 ++++++++++++++++++++------------- sumfiles/gcc.log.sep.xz | Bin 70056 -> 20364 bytes sumfiles/gcc.log.xz | Bin 2509840 -> 2472676 bytes sumfiles/gcc.sum | 7 +- sumfiles/gcc.sum.sep | 5113 ++++----------------- sumfiles/gfortran.log.sep.xz | Bin 46512 -> 38528 bytes sumfiles/gfortran.log.xz | Bin 954884 -> 950104 bytes sumfiles/gfortran.sum | 6 +- sumfiles/gfortran.sum.sep | 3190 +++++++++---- sumfiles/libatomic.log.xz | Bin 2280 -> 2280 bytes sumfiles/libatomic.sum | 2 +- sumfiles/libgomp.log.xz | Bin 233812 -> 233884 bytes sumfiles/libgomp.sum | 2 +- sumfiles/libitm.log.xz | Bin 2688 -> 2692 bytes sumfiles/libitm.sum | 2 +- sumfiles/libstdc++.log.sep.xz | Bin 6416 -> 9052 bytes sumfiles/libstdc++.log.xz | Bin 480148 -> 469848 bytes sumfiles/libstdc++.sum | 4 +- sumfiles/libstdc++.sum.sep | 388 +- 46 files changed, 8395 insertions(+), 8739 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 3 months

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_gnu_native_fast_check_gdb/master-arm updated (4a374ba3c59 -> ca00b6ef22f)

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_fast_check_gdb/master-arm in repository toolchain/ci/base-artifacts. discards 4a374ba3c59 126: onsuccess: #32: 1: Success after binutils/gcc/linux/gd [...] discards 945188c87ae 125: onsuccess: #31: 1: Success after binutils/gcc/linux/gd [...] discards 4f8959d77e0 124: onsuccess: #30: 1: Success after binutils/gcc/linux/gd [...] discards 783ca66f54f 123: onsuccess: #29: 1: Success after binutils/gcc/linux/gd [...] discards ccd3da37df5 122: onsuccess: #28: 1: Success after binutils/gcc/linux/gd [...] discards 64954ec0b8d 121: force: #26: : Failure after baseline build: no new commits discards f7199dd487b 120: onsuccess: #19: 1: Success after binutils/gcc/linux/gl [...] discards 0115578abca 119: onsuccess: #18: 1: Success after binutils/gcc/linux/gl [...] discards 9c74ea06f8c 118: onsuccess: #17: 1: Success after binutils/gcc/linux/gd [...] discards 7a1a0ca1702 117: onsuccess: #16: 1: Success after binutils/gcc/linux/gd [...] discards 049594f70f7 116: onsuccess: #15: 1: Success after binutils/gcc/linux/gl [...] discards 64128a95bc5 115: onsuccess: #14: 1: Success after binutils/gcc/linux/gl [...] discards 7e9588c6197 114: onsuccess: #13: 1: Success after binutils/gcc/linux/gl [...] discards e5ea0f11563 113: onsuccess: #11: 1: Success after binutils/gcc/linux/gl [...] discards 5a130adec6a 112: onsuccess: #10: 1: Success after binutils/gcc/linux/gd [...] discards f05afdd0e98 111: onsuccess: #9: 1: Success after binutils/gcc/linux/gdb [...] discards 015f2554d5d 110: onsuccess: #8: 1: Success after binutils/gcc/linux/gli [...] discards c2681bff147 109: onsuccess: #7: 1: Success after binutils/gcc/linux/gli [...] discards 0abb993e7d5 108: onsuccess: #6: 1: Success after binutils/gcc/linux/gdb [...] discards 431d8bbe77f 107: onsuccess: #5: 1: Success after binutils/gcc/linux/gli [...] discards 90bc1e2b682 106: onsuccess: #4: 1: Success after binutils/gcc/linux/gli [...] discards f4185230599 105: onsuccess: #3: 1: Success after binutils/gcc/linux/gli [...] discards 8826822e8e1 104: onsuccess: #2: 1: Success after binutils/gcc/linux/gli [...] discards 9613a3be5ce 103: onsuccess: #1: 1: Success after binutils/gcc/linux/gli [...] discards 33006f21542 102: onsuccess: #123: 1: Success after binutils/gcc/linux/g [...] discards 8b4ffc73464 101: onsuccess: #122: 1: Success after binutils/gcc/linux/g [...] discards 400bdb7c8ba 100: onsuccess: #121: 1: Success after binutils/gcc/glibc/g [...] discards f545fc72c59 99: onsuccess: #120: 1: Success after binutils/gcc/linux/gl [...] discards a4c2b93ac30 98: onsuccess: #108: 1: Success after binutils/gcc/linux/gl [...] discards dc42a7daca9 97: onsuccess: #107: 1: Success after binutils/gcc/linux/gl [...] discards 5e0d7aac85c 96: onsuccess: #106: 1: Success after binutils/gcc/linux/gl [...] discards 306d1286de3 95: onsuccess: #105: 1: Success after binutils/gcc/linux/gd [...] discards 218076dbd97 94: onsuccess: #104: 1: Success after binutils/gcc/linux/gl [...] discards b375cc723d6 93: onsuccess: #103: 1: Success after binutils/gcc/linux/gl [...] discards 3b038ad3567 92: onsuccess: #101: 1: Success after binutils/gcc/linux/gl [...] discards cfb20c6745e 91: onsuccess: #100: 1: Success after binutils/gcc/linux/gl [...] discards 098433c78d5 90: onsuccess: #99: 1: Success after binutils/gcc/linux/gdb [...] discards 499e679d042 89: onsuccess: #98: 1: Success after binutils/gcc/linux/gli [...] discards 6405a579831 88: onsuccess: #97: 1: Success after binutils/gcc/linux/gli [...] discards afe0e01e0e3 87: onsuccess: #96: 1: Success after binutils/gcc/linux/gli [...] discards befe4a06a45 86: onsuccess: #95: 1: Success after binutils/gcc/linux/gli [...] discards 5c095f5e99e 85: onsuccess: #94: 1: Success after binutils/gcc/linux/gli [...] discards 0cd2e5a9d15 84: onsuccess: #93: 1: Success after binutils/gcc/linux/gli [...] discards 69096adc431 83: onsuccess: #92: 1: Success after binutils/gcc/linux/gdb [...] discards c6a9185ef27 82: onsuccess: #91: 1: Success after binutils/gcc/linux/gdb [...] discards 6bdd989ff53 81: onsuccess: #90: 1: Success after binutils/gcc/linux/gli [...] discards b2ae59eb7b4 80: onsuccess: #89: 1: Success after binutils/gcc/gdb: 198 commits discards 84bced38dba 79: onsuccess: #88: 1: Success after binutils/gcc/linux/gdb [...] discards fe0ba61e3b3 78: onsuccess: #87: 1: Success after binutils/gcc/linux/gli [...] discards 7de90d3ee18 77: onsuccess: #86: 1: Success after binutils/gcc/linux/gli [...] discards 8e38416075b 76: onsuccess: #85: 1: Success after binutils/gcc/linux/gdb [...] discards 95219e8f0e3 75: onsuccess: #84: 1: Success after binutils/gcc/linux/gdb [...] discards 8a5d54b61f7 74: onsuccess: #83: 1: Success after binutils/gcc/linux/gdb [...] discards 5e7676bc950 73: onsuccess: #82: 1: Success after binutils/gcc/linux/gdb [...] discards 8a6bc21de03 72: onsuccess: #81: 1: Success after binutils/gcc/linux/gli [...] discards 0ba7ff1477f 71: onsuccess: #80: 1: Success after binutils/gcc/linux/gli [...] discards f1ff92b60ed 70: onsuccess: #79: 1: Success after binutils/gcc/linux/gli [...] discards b70c2610d5b 69: onsuccess: #78: 1: Success after binutils/gcc/linux/gdb [...] discards 51b245e1ad0 68: onsuccess: #77: 1: Success after binutils/gcc/linux/gli [...] discards cfcce76c26c 67: onsuccess: #76: 1: Success after binutils/gcc/linux/gli [...] discards 8f8936bff8e 66: onsuccess: #75: 1: Success after binutils/gcc/gdb: 30 commits discards 772399ee81c 65: onsuccess: #74: 1: Success after binutils/gcc/linux/gdb [...] discards 526daaa5304 64: onsuccess: #73: 1: Success after binutils/gcc/linux/gli [...] discards 325630e5bc2 63: onsuccess: #72: 1: Success after binutils/gcc/linux/gli [...] discards fdcd8a88382 62: onsuccess: #71: 1: Success after binutils/gcc/linux/gli [...] discards 6d722f1fcb1 61: onsuccess: #70: 1: Success after binutils/gcc/glibc/gdb [...] discards aea0fb3081c 60: onsuccess: #69: 1: Success after binutils/gcc/gdb: 103 commits discards 3c2b0f1461c 59: onsuccess: #67: 1: Success after binutils/gcc/linux/gli [...] discards 9ca0d04b3cb 58: onsuccess: #65: 1: Success after binutils/gcc/linux/gdb [...] discards 5b65b52afaf 57: onsuccess: #64: 1: Success after binutils/gcc/linux/gdb [...] discards 52f152528d3 56: onsuccess: #63: 1: Success after binutils/gcc/linux/gli [...] discards a13248c22fd 55: onsuccess: #62: 1: Success after binutils/gcc/linux/gdb [...] discards fa42c2ffd48 54: onsuccess: #61: 1: Success after binutils/gcc/gdb: 14 commits discards b6caa2fb3ac 53: onsuccess: #60: 1: Success after binutils/gcc/gdb: 42 commits discards fe99a0c8088 52: onsuccess: #59: 1: Success after binutils/gcc/linux/gdb [...] discards c17ed7c38b3 51: onsuccess: #58: 1: Success after binutils/gcc/gdb: 46 commits discards e7bc4e03c7b 50: onsuccess: #57: 1: Success after binutils/gcc/linux/gdb [...] discards 702c090e7b2 49: onsuccess: #56: 1: Success after binutils/gcc/linux/gdb [...] discards 193b596ce39 48: onsuccess: #55: 1: Success after binutils/gcc/linux/gli [...] discards 2aa883eceba 47: onsuccess: #54: 1: Success after binutils/gcc/linux/gli [...] discards b78409c09dd 46: onsuccess: #53: 1: Success after binutils/gcc/linux/gli [...] discards 513483c35f3 45: onsuccess: #52: 1: Success after binutils/gcc/linux/gli [...] discards 83ea3976bd7 44: onsuccess: #51: 1: Success after binutils/gcc/gdb: 15 commits discards bda4812f4ed 43: onsuccess: #50: 1: Success after binutils/gcc/linux/gdb [...] discards e6ed15f3183 42: onsuccess: #49: 1: Success after binutils/gcc/linux/gdb [...] discards d40c359869f 41: onsuccess: #48: 1: Success after binutils/gcc/linux/gli [...] discards 376b8376091 40: onsuccess: #47: 1: Success after binutils/gcc/linux/gli [...] discards e8f89c7e4a9 39: onsuccess: #46: 1: Success after binutils/gcc/linux/gdb [...] discards 8e151fc684c 38: onsuccess: #45: 1: Success after binutils/gcc/linux/gli [...] discards 8909ccb23a1 37: onsuccess: #44: 1: Success after binutils/gcc/linux/gdb [...] discards f1b0efeef2d 36: onsuccess: #43: 1: Success after binutils/gcc/linux/gdb [...] discards a5fd0776c24 35: onsuccess: #42: 1: Success after binutils/gcc/linux/gli [...] discards 0d94bb59577 34: onsuccess: #41: 1: Success after binutils/gcc/linux/gli [...] discards 7d411e0d92b 33: onsuccess: #40: 1: Success after binutils/gcc/glibc/gdb [...] discards 9b1b1ccfdc7 32: onsuccess: #39: 1: Success after binutils/gcc/linux/gli [...] discards 85c7fbf8b01 31: onsuccess: #38: 1: Success after linux: 14 commits discards 2e70113ce38 30: onsuccess: #36: 1: Success after binutils: 18 commits discards c5f7a147c55 29: onsuccess: #34: 1: Success after binutils/gcc/linux/gdb [...] discards f0b5ba5f155 28: onsuccess: #33: 1: Success after binutils/gcc/linux/gli [...] discards ff1fdc961bb 27: onsuccess: #32: 1: Success after binutils/gcc/linux/gli [...] discards dfbfd2bc09b 26: onsuccess: #31: 1: Success after binutils/gcc/linux/gdb [...] new cdbe02c864f 26: onsuccess: #31: 1: Success after binutils/gcc/linux/gdb [...] new c210536ec47 27: onsuccess: #32: 1: Success after binutils/gcc/linux/gli [...] new c184843ab87 28: onsuccess: #33: 1: Success after binutils/gcc/linux/gli [...] new a31ab09e0d6 29: onsuccess: #34: 1: Success after binutils/gcc/linux/gdb [...] new 5a83f9231b5 30: onsuccess: #36: 1: Success after binutils: 18 commits new a448c8dc51d 31: onsuccess: #38: 1: Success after linux: 14 commits new 293489ebb5f 32: onsuccess: #39: 1: Success after binutils/gcc/linux/gli [...] new 3a2bd564e14 33: onsuccess: #40: 1: Success after binutils/gcc/glibc/gdb [...] new 529981d3698 34: onsuccess: #41: 1: Success after binutils/gcc/linux/gli [...] new 7a8f8f27bdc 35: onsuccess: #42: 1: Success after binutils/gcc/linux/gli [...] new bc79b138010 36: onsuccess: #43: 1: Success after binutils/gcc/linux/gdb [...] new 9bf61c3552d 37: onsuccess: #44: 1: Success after binutils/gcc/linux/gdb [...] new 96330b3f189 38: onsuccess: #45: 1: Success after binutils/gcc/linux/gli [...] new 281d5aa2829 39: onsuccess: #46: 1: Success after binutils/gcc/linux/gdb [...] new a36fc0e7553 40: onsuccess: #47: 1: Success after binutils/gcc/linux/gli [...] new 987c44a82f0 41: onsuccess: #48: 1: Success after binutils/gcc/linux/gli [...] new 5e5230d4833 42: onsuccess: #49: 1: Success after binutils/gcc/linux/gdb [...] new dfb38c31f65 43: onsuccess: #50: 1: Success after binutils/gcc/linux/gdb [...] new 5d97ff68a98 44: onsuccess: #51: 1: Success after binutils/gcc/gdb: 15 commits new 62f5e4c105f 45: onsuccess: #52: 1: Success after binutils/gcc/linux/gli [...] new d83eba0b4bb 46: onsuccess: #53: 1: Success after binutils/gcc/linux/gli [...] new de55557b214 47: onsuccess: #54: 1: Success after binutils/gcc/linux/gli [...] new 43c76c4f3f4 48: onsuccess: #55: 1: Success after binutils/gcc/linux/gli [...] new f45c01a0a47 49: onsuccess: #56: 1: Success after binutils/gcc/linux/gdb [...] new d1a732b97cd 50: onsuccess: #57: 1: Success after binutils/gcc/linux/gdb [...] new 95ee6ed6228 51: onsuccess: #58: 1: Success after binutils/gcc/gdb: 46 commits new 1a6e0f9a41c 52: onsuccess: #59: 1: Success after binutils/gcc/linux/gdb [...] new 03278fbacc0 53: onsuccess: #60: 1: Success after binutils/gcc/gdb: 42 commits new 72c16ac9a6f 54: onsuccess: #61: 1: Success after binutils/gcc/gdb: 14 commits new a2b26326f34 55: onsuccess: #62: 1: Success after binutils/gcc/linux/gdb [...] new eff73f64b36 56: onsuccess: #63: 1: Success after binutils/gcc/linux/gli [...] new da878a73483 57: onsuccess: #64: 1: Success after binutils/gcc/linux/gdb [...] new f89a9f4f4b4 58: onsuccess: #65: 1: Success after binutils/gcc/linux/gdb [...] new 6f1401f8f30 59: onsuccess: #67: 1: Success after binutils/gcc/linux/gli [...] new d9d30391bd3 60: onsuccess: #69: 1: Success after binutils/gcc/gdb: 103 commits new 223d641ae70 61: onsuccess: #70: 1: Success after binutils/gcc/glibc/gdb [...] new b366e701a2c 62: onsuccess: #71: 1: Success after binutils/gcc/linux/gli [...] new 9f54d23fcbf 63: onsuccess: #72: 1: Success after binutils/gcc/linux/gli [...] new 498c3dd6132 64: onsuccess: #73: 1: Success after binutils/gcc/linux/gli [...] new 4832c9ad324 65: onsuccess: #74: 1: Success after binutils/gcc/linux/gdb [...] new 3b2443b57f0 66: onsuccess: #75: 1: Success after binutils/gcc/gdb: 30 commits new b9e12b786b3 67: onsuccess: #76: 1: Success after binutils/gcc/linux/gli [...] new 6b81bd48477 68: onsuccess: #77: 1: Success after binutils/gcc/linux/gli [...] new 19a73dd0fa3 69: onsuccess: #78: 1: Success after binutils/gcc/linux/gdb [...] new 4a0ed7cae5e 70: onsuccess: #79: 1: Success after binutils/gcc/linux/gli [...] new c187d811812 71: onsuccess: #80: 1: Success after binutils/gcc/linux/gli [...] new 5ef0e0f9035 72: onsuccess: #81: 1: Success after binutils/gcc/linux/gli [...] new d221f97ed2a 73: onsuccess: #82: 1: Success after binutils/gcc/linux/gdb [...] new bf91c7267a6 74: onsuccess: #83: 1: Success after binutils/gcc/linux/gdb [...] new ac7092bab31 75: onsuccess: #84: 1: Success after binutils/gcc/linux/gdb [...] new 604091260a1 76: onsuccess: #85: 1: Success after binutils/gcc/linux/gdb [...] new d6695a11ae3 77: onsuccess: #86: 1: Success after binutils/gcc/linux/gli [...] new eccd1bb9eb9 78: onsuccess: #87: 1: Success after binutils/gcc/linux/gli [...] new dd75ad0f738 79: onsuccess: #88: 1: Success after binutils/gcc/linux/gdb [...] new f9b150aa66b 80: onsuccess: #89: 1: Success after binutils/gcc/gdb: 198 commits new f50d42494f6 81: onsuccess: #90: 1: Success after binutils/gcc/linux/gli [...] new bda3fb54cbd 82: onsuccess: #91: 1: Success after binutils/gcc/linux/gdb [...] new c273cce8c2c 83: onsuccess: #92: 1: Success after binutils/gcc/linux/gdb [...] new 0afc14c2d68 84: onsuccess: #93: 1: Success after binutils/gcc/linux/gli [...] new b1961f30678 85: onsuccess: #94: 1: Success after binutils/gcc/linux/gli [...] new d21652521e7 86: onsuccess: #95: 1: Success after binutils/gcc/linux/gli [...] new 59129e3d537 87: onsuccess: #96: 1: Success after binutils/gcc/linux/gli [...] new ded065539f7 88: onsuccess: #97: 1: Success after binutils/gcc/linux/gli [...] new 99a90110c16 89: onsuccess: #98: 1: Success after binutils/gcc/linux/gli [...] new 3a81762ee80 90: onsuccess: #99: 1: Success after binutils/gcc/linux/gdb [...] new d61469e804c 91: onsuccess: #100: 1: Success after binutils/gcc/linux/gl [...] new d68c968182e 92: onsuccess: #101: 1: Success after binutils/gcc/linux/gl [...] new e499eda7fc4 93: onsuccess: #103: 1: Success after binutils/gcc/linux/gl [...] new 76b904bb0bf 94: onsuccess: #104: 1: Success after binutils/gcc/linux/gl [...] new 1e87fa39656 95: onsuccess: #105: 1: Success after binutils/gcc/linux/gd [...] new e84153f3da3 96: onsuccess: #106: 1: Success after binutils/gcc/linux/gl [...] new 0562cfdae37 97: onsuccess: #107: 1: Success after binutils/gcc/linux/gl [...] new 7ac64261d87 98: onsuccess: #108: 1: Success after binutils/gcc/linux/gl [...] new f8ddfe5f125 99: onsuccess: #120: 1: Success after binutils/gcc/linux/gl [...] new 71bf6b08a81 100: onsuccess: #121: 1: Success after binutils/gcc/glibc/g [...] new a5cdbd659db 101: onsuccess: #122: 1: Success after binutils/gcc/linux/g [...] new e343a67a8a4 102: onsuccess: #123: 1: Success after binutils/gcc/linux/g [...] new 64105ca7db9 103: onsuccess: #1: 1: Success after binutils/gcc/linux/gli [...] new 79329742227 104: onsuccess: #2: 1: Success after binutils/gcc/linux/gli [...] new b41f36ed7dd 105: onsuccess: #3: 1: Success after binutils/gcc/linux/gli [...] new 2a2a65be538 106: onsuccess: #4: 1: Success after binutils/gcc/linux/gli [...] new 1ff93b2f29f 107: onsuccess: #5: 1: Success after binutils/gcc/linux/gli [...] new 053e78ecd74 108: onsuccess: #6: 1: Success after binutils/gcc/linux/gdb [...] new aa1f39a1e2a 109: onsuccess: #7: 1: Success after binutils/gcc/linux/gli [...] new 99999ffdd9a 110: onsuccess: #8: 1: Success after binutils/gcc/linux/gli [...] new 23ac64a7392 111: onsuccess: #9: 1: Success after binutils/gcc/linux/gdb [...] new 7f930572e12 112: onsuccess: #10: 1: Success after binutils/gcc/linux/gd [...] new 84f44244578 113: onsuccess: #11: 1: Success after binutils/gcc/linux/gl [...] new 51df27ccb4c 114: onsuccess: #13: 1: Success after binutils/gcc/linux/gl [...] new 906c0e06466 115: onsuccess: #14: 1: Success after binutils/gcc/linux/gl [...] new 01d1723e00a 116: onsuccess: #15: 1: Success after binutils/gcc/linux/gl [...] new 08301457f71 117: onsuccess: #16: 1: Success after binutils/gcc/linux/gd [...] new 12c0271cba3 118: onsuccess: #17: 1: Success after binutils/gcc/linux/gd [...] new 14a473cddb8 119: onsuccess: #18: 1: Success after binutils/gcc/linux/gl [...] new ed52eadcb3f 120: onsuccess: #19: 1: Success after binutils/gcc/linux/gl [...] new e677cf76c81 121: force: #26: : Failure after baseline build: no new commits new 45415cc7be7 122: onsuccess: #28: 1: Success after binutils/gcc/linux/gd [...] new 237f52df399 123: onsuccess: #29: 1: Success after binutils/gcc/linux/gd [...] new fbc17d39d7e 124: onsuccess: #30: 1: Success after binutils/gcc/linux/gd [...] new d4838f45869 125: onsuccess: #31: 1: Success after binutils/gcc/linux/gd [...] new 29b878ea63b 126: onsuccess: #32: 1: Success after binutils/gcc/linux/gd [...] new ca00b6ef22f 127: onsuccess: #33: 1: Success after binutils/gcc/linux/gl [...] 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 (4a374ba3c59) \ N -- N -- N refs/heads/linaro-local/ci/tcwg_gnu_native_fast_check_gd [...] 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 1760 -> 2064 bytes 02-prepare_abe/console.log.xz | Bin 2512 -> 2564 bytes 03-build_abe-binutils/console.log.xz | Bin 49020 -> 49316 bytes 04-build_abe-gcc/console.log.xz | Bin 236288 -> 238844 bytes 05-clean_sysroot/console.log.xz | Bin 316 -> 316 bytes 06-build_abe-linux/console.log.xz | Bin 8404 -> 8408 bytes 07-build_abe-glibc/console.log.xz | Bin 232820 -> 232792 bytes 08-build_abe-gdb/console.log.xz | Bin 47588 -> 46776 bytes 09-build_abe-dejagnu/console.log.xz | Bin 3768 -> 3772 bytes 10-build_abe-check_gdb/console.log.xz | Bin 2916 -> 2712 bytes 11-check_regression/console.log.xz | Bin 4772 -> 5072 bytes 11-check_regression/results.compare | 4 +- 11-check_regression/results.compare2 | 6 +-- 12-update_baseline/console.log | 68 +++++++++++++++++----------------- dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- git/gdb_rev | 2 +- git/glibc_rev | 2 +- git/linux_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 2 +- mail/mail-subject.txt | 2 +- manifest.sh | 38 +++++++++---------- sumfiles/gdb.log.xz | Bin 14476 -> 14468 bytes sumfiles/gdb.sum | 4 +- 26 files changed, 69 insertions(+), 69 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 3 months

[gcc] branch master updated (f2e70da638b -> 3e791f45ded)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. unknown user pushed a change to branch master in repository gcc. from f2e70da638b libstdc++: Remove std::formatter<const charT[N], charT> spe [...] new 3e791f45ded Fortran: improve checking of FINAL subroutine arguments [PR104572] The 1 revisions listed above as "new" are entirely new to this repository and will be described in separate emails. The revisions listed as "adds" were already present in the repository and have only been added to this reference. Summary of changes: gcc/fortran/resolve.cc | 7 +++++++ gcc/testsuite/gfortran.dg/pr104572.f90 | 14 ++++++++++++++ 2 files changed, 21 insertions(+) create mode 100644 gcc/testsuite/gfortran.dg/pr104572.f90 -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 3 months

[gcc] branch releases/gcc-12 updated (c826442f665 -> 7eb94c5adfd)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. unknown user pushed a change to branch releases/gcc-12 in repository gcc. from c826442f665 ipa-cp: Fix various issues in update_specialized_profile (P [...] new b6bef857c1e Fortran: procedures with BIND(C) attribute require explicit [...] new f1342c21b2a Fortran: simplification of NEAREST for large argument [PR109186] new 7eb94c5adfd Fortran: reject MODULE PROCEDURE outside generic module int [...] The 3 revisions listed above as "new" are entirely new to this repository and will be described in separate emails. The revisions listed as "adds" were already present in the repository and have only been added to this reference. Summary of changes: gcc/fortran/decl.cc | 7 ++++--- gcc/fortran/resolve.cc | 10 ++++++++++ gcc/fortran/simplify.cc | 2 +- gcc/testsuite/gfortran.dg/nearest_6.f90 | 26 ++++++++++++++++++++++++++ gcc/testsuite/gfortran.dg/pr85877.f90 | 25 +++++++++++++++++++++++++ gcc/testsuite/gfortran.dg/pr99036.f90 | 9 +++++++++ 6 files changed, 75 insertions(+), 4 deletions(-) create mode 100644 gcc/testsuite/gfortran.dg/nearest_6.f90 create mode 100644 gcc/testsuite/gfortran.dg/pr85877.f90 create mode 100644 gcc/testsuite/gfortran.dg/pr99036.f90 -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 3 months

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

Tcwg-commits March 2023