Tcwg-commits March 2023

tcwg-commits@lists.linaro.org

5 participants
3834 discussions

[toolchain/jenkins-scripts] branch master updated (e4f787d0 -> e17412d6)

by Maxim Kuvyrkov

This is an automated email from the git hooks/post-receive script. "Maxim Kuvyrkov pushed a change to branch master in repository toolchain/jenkins-scripts. from e4f787d0 tcwg_aosp-build.sh: Detect and bisect failures in shadow build new 6b29a4c7 tcwg_aosp-build.sh: Improve processing of shadow data new 7ce224c5 wrappers/shadow-cc.sh: Handle "-iquote" option new e17412d6 wrappers/shadow-ar.sh: Don't error on no input files 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: tcwg_aosp-build.sh | 31 +++++++++++++++++-------------- wrappers/shadow-ar.sh | 4 ---- wrappers/shadow-cc.sh | 4 ++-- 3 files changed, 19 insertions(+), 20 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

1 year, 8 months

[gcc] branch master updated (5e812e8c1e8 -> 81295d445ec)

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 5e812e8c1e8 configure: regenerate new 81295d445ec frange: Implement nan_state class [PR109008] 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/value-range.cc | 18 +++++++++++++--- gcc/value-range.h | 62 ++++++++++++++++++++++++++++++++++++++++++++++++++++++ 2 files changed, 77 insertions(+), 3 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

1 year, 8 months

[binutils-gdb] branch master updated (904d9b02a18 -> bf3f6c02d73)

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 904d9b02a18 gdb: make "maintenance info line-table" show relocated addr [...] new 722c4596034 [gdb/testsuite] Fix gdb.cp/*.exp for remote host new 14662762048 [gdb/testsuite] Fix gdb.cp/annota{2,3}.exp for native-exten [...] new bf3f6c02d73 [gdb/testsuite] Fix gdb.cp/cp-relocate.exp for remote host 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: gdb/testsuite/gdb.cp/annota2.exp | 15 +++++++++++++-- gdb/testsuite/gdb.cp/annota3.exp | 25 +++++++++++++++++-------- gdb/testsuite/gdb.cp/breakpoint-locs.exp | 2 ++ gdb/testsuite/gdb.cp/cp-relocate.exp | 4 +++- gdb/testsuite/gdb.cp/filename.exp | 2 ++ gdb/testsuite/gdb.cp/gdb2384.exp | 2 ++ gdb/testsuite/gdb.cp/hang.exp | 2 ++ gdb/testsuite/gdb.cp/m-static.exp | 8 +++++++- gdb/testsuite/gdb.cp/mb-inline.exp | 1 + gdb/testsuite/gdb.cp/minsym-fallback.exp | 3 +++ gdb/testsuite/gdb.cp/ovsrch.exp | 2 ++ gdb/testsuite/gdb.cp/pr10728.exp | 2 ++ gdb/testsuite/gdb.cp/rtti.exp | 2 ++ gdb/testsuite/gdb.cp/stub-array-size.exp | 2 ++ gdb/testsuite/gdb.cp/subtypes.exp | 2 ++ gdb/testsuite/lib/gdb.exp | 12 ++++++++++++ 16 files changed, 74 insertions(+), 12 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

1 year, 8 months

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_bmk-code_speed-spec2k6/gnu-arm-master-O3_LTO updated (52a21ed03c6 -> 43224f28f3c)

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-arm-master-O3_LTO in repository toolchain/ci/base-artifacts. from 52a21ed03c6 88: onsuccess: #25: 1: [TCWG CI] 437.leslie3d speeds up by [...] new 43224f28f3c 89: force: #29: 1: [TCWG CI] No change after baseline build [...] 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 1972 -> 1936 bytes 02-prepare_abe/console.log.xz | Bin 2496 -> 2504 bytes 03-build_abe-binutils/console.log.xz | Bin 27356 -> 27380 bytes 04-build_abe-stage1/console.log.xz | Bin 90504 -> 89244 bytes 05-clean_sysroot/console.log.xz | Bin 336 -> 336 bytes 06-build_abe-linux/console.log.xz | Bin 7560 -> 8344 bytes 07-build_abe-glibc/console.log.xz | Bin 235280 -> 234500 bytes 08-build_abe-stage2/console.log.xz | Bin 214372 -> 210944 bytes 09-benchmark/benchmark-build.log | 191 +- 09-benchmark/benchmark.log | 189 +- 09-benchmark/console.log.xz | Bin 4160 -> 4108 bytes .../compare-results-vs-first-internal.csv | 76 +- .../compare-results-vs-prev-internal.csv | 80 +- 10-check_regression/console.log.xz | Bin 9144 -> 7512 bytes .../csv-results-vs-first-0/results.csv | 696328 ++++++++--------- .../csv-results-vs-first-0/size.csv | 698904 ++++++++--------- 10-check_regression/csv-results-vs-first-0/sve.csv | 38 +- .../csv-results-vs-first-1/perf.csv | 177 +- .../csv-results-vs-first-1/results.csv | 698523 ++++++++--------- .../csv-results-vs-first-1/size.csv | 711991 +++++++++--------- 10-check_regression/csv-results-vs-first-1/sve.csv | 20820 +- .../csv-results-vs-first-1/vect.csv | 788 +- 10-check_regression/csv-results-vs-prev-0/perf.csv | 185 +- .../csv-results-vs-prev-0/results.csv | 679365 ++++++++--------- 10-check_regression/csv-results-vs-prev-0/size.csv | 692827 ++++++++--------- 10-check_regression/csv-results-vs-prev-0/sve.csv | 20550 +- 10-check_regression/csv-results-vs-prev-0/vect.csv | 734 +- 10-check_regression/csv-results-vs-prev-1/perf.csv | 177 +- .../csv-results-vs-prev-1/results.csv | 698523 ++++++++--------- 10-check_regression/csv-results-vs-prev-1/size.csv | 711991 +++++++++--------- 10-check_regression/csv-results-vs-prev-1/sve.csv | 20820 +- 10-check_regression/csv-results-vs-prev-1/vect.csv | 788 +- 10-check_regression/exe.improvement | 1 - 10-check_regression/extra-bisect-params | 2 +- 10-check_regression/jira-body.txt | 3 - 10-check_regression/mail-body.txt | 3 - 10-check_regression/mail-subject.txt | 2 +- .../output-bmk-results/exe.improvement.diff | 1 - 10-check_regression/results-vs-first-brief.csv | 66 +- 10-check_regression/results-vs-first-full.csv | 179 +- 10-check_regression/results-vs-first-internal.csv | 78 +- 10-check_regression/results-vs-first.csv | 78 +- 10-check_regression/results-vs-first.log | 1542 +- 10-check_regression/results-vs-prev-brief.csv | 68 +- 10-check_regression/results-vs-prev-compare.csv | 2 +- 10-check_regression/results-vs-prev-full.csv | 195 +- 10-check_regression/results-vs-prev-internal.csv | 80 +- 10-check_regression/results-vs-prev.csv | 80 +- 10-check_regression/results-vs-prev.log | 1748 +- 11-update_baseline/console.log | 10 +- dashboard/dashboard-generate.sh | 2 +- .../400.perlbench/results-metadata.json | 8 +- .../squad-vs-first/401.bzip2/results-metadata.json | 8 +- .../squad-vs-first/403.gcc/results-metadata.json | 8 +- .../squad-vs-first/403.gcc/results-metrics.json | 2 +- .../410.bwaves/results-metadata.json | 8 +- .../416.gamess/results-metadata.json | 8 +- .../squad-vs-first/429.mcf/results-metadata.json | 8 +- .../squad-vs-first/433.milc/results-metadata.json | 8 +- .../434.zeusmp/results-metadata.json | 8 +- .../435.gromacs/results-metadata.json | 8 +- .../436.cactusADM/results-metadata.json | 8 +- .../437.leslie3d/results-metadata.json | 8 +- .../437.leslie3d/results-metrics.json | 2 +- .../squad-vs-first/444.namd/results-metadata.json | 8 +- .../squad-vs-first/445.gobmk/results-metadata.json | 8 +- .../447.dealII/results-metadata.json | 8 +- .../squad-vs-first/447.dealII/results-metrics.json | 2 +- .../450.soplex/results-metadata.json | 8 +- .../453.povray/results-metadata.json | 8 +- .../squad-vs-first/453.povray/results-metrics.json | 2 +- .../454.calculix/results-metadata.json | 8 +- .../squad-vs-first/456.hmmer/results-metadata.json | 8 +- .../squad-vs-first/458.sjeng/results-metadata.json | 8 +- .../459.GemsFDTD/results-metadata.json | 8 +- .../462.libquantum/results-metadata.json | 8 +- .../464.h264ref/results-metadata.json | 8 +- .../464.h264ref/results-metrics.json | 2 +- .../squad-vs-first/465.tonto/results-metadata.json | 8 +- .../squad-vs-first/470.lbm/results-metadata.json | 8 +- .../471.omnetpp/results-metadata.json | 8 +- .../squad-vs-first/473.astar/results-metadata.json | 8 +- .../squad-vs-first/481.wrf/results-metadata.json | 8 +- .../482.sphinx3/results-metadata.json | 8 +- .../483.xalancbmk/results-metadata.json | 8 +- .../483.xalancbmk/results-metrics.json | 2 +- .../squad-vs-first/Mean/results-metadata.json | 8 +- dashboard/squad-vs-first/dashboard-push-squad.sh | 128 +- dashboard/squad-vs-first/summary-annotation.txt | 1 - mail/jira-body.txt | 23 +- mail/mail-body.txt | 23 +- mail/mail-subject.txt | 2 +- manifest.sh | 26 +- results_id | 2 +- 94 files changed, 2859725 insertions(+), 2798937 deletions(-) delete mode 100644 10-check_regression/exe.improvement -- To stop receiving notification emails like this one, please contact the administrator of this repository.

1 year, 8 months

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_kernel/gnu-master-aarch64-mainline-allyesconfig updated (5843965d37a -> a29e6fa7e8b)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. tcwg-buildslave pushed a change to branch linaro-local/ci/tcwg_kernel/gnu-master-aarch64-mainline-allyesconfig in repository toolchain/ci/base-artifacts. from 5843965d37a 54: onsuccess: #10: 21862: Success after binutils/gcc/linux [...] new a29e6fa7e8b 55: onsuccess: #11: 21862: Success after binutils/gcc/linux [...] The 1 revisions listed above as "new" are entirely new to this repository and will be described in separate emails. The revisions listed as "adds" were already present in the repository and have only been added to this reference. Summary of changes: 01-reset_artifacts/console.log.xz | Bin 1776 -> 1772 bytes 02-prepare_abe/console.log.xz | Bin 2456 -> 2564 bytes 03-build_abe-binutils/console.log.xz | Bin 27020 -> 27736 bytes 04-build_abe-stage1/console.log.xz | Bin 70960 -> 71640 bytes 05-build_abe-qemu/console.log.xz | Bin 30708 -> 31312 bytes 06-build_linux/console.log.xz | Bin 8672 -> 8632 bytes 08-check_regression/console.log.xz | Bin 4328 -> 4516 bytes 08-check_regression/mail-body.txt | 11 ----------- dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- git/linux_rev | 2 +- git/qemu_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 13 +------------ mail/mail-subject.txt | 2 +- manifest.sh | 32 ++++++++++++++++---------------- 17 files changed, 24 insertions(+), 46 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

1 year, 8 months

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_kernel/gnu-master-arm-mainline-defconfig updated (977e588b300 -> ba06f494635)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. tcwg-buildslave pushed a change to branch linaro-local/ci/tcwg_kernel/gnu-master-arm-mainline-defconfig in repository toolchain/ci/base-artifacts. from 977e588b300 56: onsuccess: #6: boot: Success after binutils/gcc/linux/q [...] new ba06f494635 57: onsuccess: #7: boot: Success after binutils/gcc/linux/q [...] 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 1756 -> 1756 bytes 02-prepare_abe/console.log.xz | Bin 2456 -> 2548 bytes 03-build_abe-binutils/console.log.xz | Bin 26912 -> 27464 bytes 04-build_abe-stage1/console.log.xz | Bin 88528 -> 89140 bytes 05-build_abe-qemu/console.log.xz | Bin 31104 -> 30772 bytes 06-build_linux/console.log.xz | Bin 4824 -> 4568 bytes 07-boot_linux/console.log.xz | Bin 5660 -> 5676 bytes 08-check_regression/console.log.xz | Bin 4256 -> 4296 bytes 08-check_regression/mail-body.txt | 2 +- dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- git/linux_rev | 2 +- git/qemu_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 4 ++-- mail/mail-subject.txt | 2 +- manifest.sh | 32 ++++++++++++++++---------------- results | 2 +- 19 files changed, 27 insertions(+), 27 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

1 year, 8 months

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_bmk-code_speed-cpu2017rate/gnu-arm-master-O3_LTO updated (b60d6144993 -> 1b710da8c23)

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-cpu2017rate/gnu-arm-master-O3_LTO in repository toolchain/ci/base-artifacts. from b60d6144993 11: onsuccess: #13: 1: [TCWG CI] No change after binutils/g [...] new 1b710da8c23 12: onsuccess: #14: 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 1804 -> 1828 bytes 02-prepare_abe/console.log.xz | Bin 2536 -> 2540 bytes 03-build_abe-binutils/console.log.xz | Bin 26912 -> 27320 bytes 04-build_abe-stage1/console.log.xz | Bin 89248 -> 90196 bytes 05-clean_sysroot/console.log.xz | Bin 336 -> 336 bytes 06-build_abe-linux/console.log.xz | Bin 8324 -> 8284 bytes 07-build_abe-glibc/console.log.xz | Bin 233356 -> 233616 bytes 08-build_abe-stage2/console.log.xz | Bin 209884 -> 211080 bytes 09-benchmark/benchmark-build.log | 155 +- 09-benchmark/benchmark.log | 153 +- 09-benchmark/console.log.xz | Bin 4160 -> 4240 bytes .../compare-results-vs-first-internal.csv | 66 +- .../compare-results-vs-prev-internal.csv | 66 +- 10-check_regression/console.log.xz | Bin 8560 -> 8568 bytes .../csv-results-vs-first-1/perf.csv | 163 +- .../csv-results-vs-first-1/results.csv | 41397 +- .../csv-results-vs-first-1/size.csv | 532133 +++++++++--------- 10-check_regression/csv-results-vs-first-1/sve.csv | 23462 +- .../csv-results-vs-first-1/vect.csv | 466 +- 10-check_regression/csv-results-vs-prev-0/perf.csv | 155 +- .../csv-results-vs-prev-0/results.csv | 25412 +- 10-check_regression/csv-results-vs-prev-0/size.csv | 370119 ++++++------ 10-check_regression/csv-results-vs-prev-0/sve.csv | 23260 +- 10-check_regression/csv-results-vs-prev-0/vect.csv | 344 +- 10-check_regression/csv-results-vs-prev-1/perf.csv | 163 +- .../csv-results-vs-prev-1/results.csv | 41397 +- 10-check_regression/csv-results-vs-prev-1/size.csv | 532133 +++++++++--------- 10-check_regression/csv-results-vs-prev-1/sve.csv | 23462 +- 10-check_regression/csv-results-vs-prev-1/vect.csv | 466 +- 10-check_regression/results-vs-first-brief.csv | 56 +- 10-check_regression/results-vs-first-full.csv | 175 +- 10-check_regression/results-vs-first-internal.csv | 66 +- 10-check_regression/results-vs-first.csv | 66 +- 10-check_regression/results-vs-first.log | 984 +- 10-check_regression/results-vs-prev-brief.csv | 56 +- 10-check_regression/results-vs-prev-full.csv | 179 +- 10-check_regression/results-vs-prev-internal.csv | 66 +- 10-check_regression/results-vs-prev.csv | 66 +- 10-check_regression/results-vs-prev.log | 1294 +- dashboard/dashboard-generate.sh | 2 +- .../500.perlbench_r/results-metadata.json | 14 +- .../500.perlbench_r/results-metrics.json | 2 +- .../squad-vs-first/502.gcc_r/results-metadata.json | 14 +- .../503.bwaves_r/results-metadata.json | 14 +- .../squad-vs-first/505.mcf_r/results-metadata.json | 14 +- .../507.cactuBSSN_r/results-metadata.json | 14 +- .../508.namd_r/results-metadata.json | 14 +- .../510.parest_r/results-metadata.json | 14 +- .../511.povray_r/results-metadata.json | 14 +- .../squad-vs-first/519.lbm_r/results-metadata.json | 14 +- .../520.omnetpp_r/results-metadata.json | 14 +- .../520.omnetpp_r/results-metrics.json | 2 +- .../squad-vs-first/521.wrf_r/results-metadata.json | 14 +- .../523.xalancbmk_r/results-metadata.json | 14 +- .../525.x264_r/results-metadata.json | 14 +- .../526.blender_r/results-metadata.json | 14 +- .../527.cam4_r/results-metadata.json | 14 +- .../squad-vs-first/527.cam4_r/results-metrics.json | 2 +- .../531.deepsjeng_r/results-metadata.json | 14 +- .../531.deepsjeng_r/results-metrics.json | 2 +- .../538.imagick_r/results-metadata.json | 14 +- .../538.imagick_r/results-metrics.json | 2 +- .../541.leela_r/results-metadata.json | 14 +- .../squad-vs-first/544.nab_r/results-metadata.json | 14 +- .../squad-vs-first/544.nab_r/results-metrics.json | 2 +- .../548.exchange2_r/results-metadata.json | 14 +- .../549.fotonik3d_r/results-metadata.json | 14 +- .../554.roms_r/results-metadata.json | 14 +- .../squad-vs-first/557.xz_r/results-metadata.json | 14 +- .../squad-vs-first/Mean/results-metadata.json | 14 +- dashboard/squad-vs-first/dashboard-push-squad.sh | 98 +- 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 +- 79 files changed, 819053 insertions(+), 799483 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

1 year, 8 months

[gcc] branch master updated (573dbd5175d -> 5e812e8c1e8)

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 573dbd5175d PR modula2/107630 Remove M2LINK and remove some cross linking new 5e812e8c1e8 configure: regenerate 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/configure | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

1 year, 8 months

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_gnu_native_check_binutils/master-aarch64 updated (50d527d5199 -> 6c42d888502)

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 50d527d5199 217: onsuccess: #31: 1: Success after binutils/gcc/linux/gd [...] discards dba39fdb826 216: onsuccess: #30: 1: Success after binutils/gcc/linux/gd [...] discards 58de53d9774 215: onsuccess: #27: 1: Success after binutils/gcc/linux/gd [...] discards d96378e29c7 214: onsuccess: #26: 1: Success after binutils: 12 commits discards 480f646c8fa 213: force: #25: 1: Failure after gdb-13-branchpoint-1445-g [...] discards f112e53e833 212: force: #24: 1: Success after binutils: 2 commits discards 7ff51e6703e 211: onsuccess: #23: 1: Success after gcc/linux/gdb: 43 commits discards c36f4db8b89 210: onsuccess: #20: 1: Success after binutils/gcc/linux/gl [...] discards c132efc54b8 209: onsuccess: #19: 1: Success after binutils/gcc/linux/gl [...] discards e0c5be9f747 208: onsuccess: #18: 1: Success after binutils/gcc/linux/gl [...] discards c755be5d2f2 207: onsuccess: #17: 1: Success after binutils/gcc/linux/gd [...] discards a82fdd6eaf9 206: onsuccess: #16: 1: Success after binutils/gcc/linux/gl [...] discards 28021986832 205: onsuccess: #15: 1: Success after binutils/gcc/linux/gd [...] discards 6fd351aa5e1 204: onsuccess: #14: 1: Success after binutils/gcc/linux/gl [...] discards 6c0300a028a 203: onsuccess: #13: 1: Success after binutils/gcc/linux/gl [...] discards 3da70713184 202: onsuccess: #12: 1: Success after binutils/gcc/linux/gl [...] discards e29bafaa814 201: onsuccess: #11: 1: Success after binutils/gcc/linux/gd [...] discards eb455fd50b6 200: onsuccess: #10: 1: Success after binutils/gcc/linux/gd [...] discards b08a9ac19c7 199: onsuccess: #9: 1: Success after binutils/gcc/linux/gdb [...] discards f21068e2d51 198: onsuccess: #8: 1: Success after binutils/gcc/linux/gli [...] discards 7e50db61040 197: onsuccess: #7: 1: Success after binutils/gcc/linux/gli [...] discards 8eeb695dcff 196: onsuccess: #6: 1: Success after binutils/gcc/linux/gli [...] discards 6fb733f849b 195: onsuccess: #5: 1: Success after binutils/gcc/linux/gli [...] discards a11f3d05509 194: onsuccess: #4: 1: Success after binutils/gcc/linux/gdb [...] discards 21fed43a5a5 193: onsuccess: #3: 1: Success after binutils/gcc/linux/gli [...] discards 55aaaa849b2 192: onsuccess: #2: 1: Success after binutils/gcc/linux/gdb [...] discards 17db1c7d1e0 191: onsuccess: #1: 1: Success after binutils/gcc/linux/gli [...] discards b836f1c9cf4 190: onsuccess: #726: 1: Success after binutils/gcc/linux/g [...] discards 4bf63f121ff 189: onsuccess: #725: 1: Success after binutils/gcc/linux/g [...] discards e92571a37e3 188: onsuccess: #724: 1: Success after binutils/gcc/linux/g [...] discards c45a2347da7 187: onsuccess: #723: 1: Success after binutils/gcc/linux/g [...] discards e537d4db67c 186: onsuccess: #722: 1: Success after binutils/gcc/linux/g [...] discards 25aed00ec19 185: onsuccess: #721: 1: Success after binutils/gcc/linux/g [...] discards 3e3af519b5f 184: onsuccess: #720: 1: Success after binutils/gcc/linux/g [...] discards 46b49397f02 183: onsuccess: #719: 1: Success after binutils/gcc/gdb: 20 [...] discards 52d664fa071 182: onsuccess: #718: 1: Success after binutils/gcc/linux/g [...] discards 25f8d034fc4 181: onsuccess: #717: 1: Success after binutils/gcc/linux/g [...] discards 810884c6ef6 180: onsuccess: #716: 1: Success after binutils/gcc/linux/g [...] discards 443e71bdb72 179: onsuccess: #715: 1: Success after binutils/gcc/linux/g [...] discards f7a79dcd125 178: onsuccess: #714: 1: Success after binutils/gcc/linux/g [...] discards e2fe21a22c4 177: onsuccess: #712: 1: Success after binutils/gcc/linux/g [...] discards 8ad42dc07d6 176: onsuccess: #711: 1: Success after binutils/gcc/linux/g [...] discards b1b3a38321c 175: onsuccess: #710: 1: Success after binutils/gcc/linux/g [...] discards 7601c2f2176 174: onsuccess: #709: 1: Success after binutils/gcc/linux/g [...] discards f54f84e7a58 173: onsuccess: #708: 1: Success after binutils/gcc/linux/g [...] discards b2f42529ac4 172: onsuccess: #707: 1: Success after binutils/gcc/linux/g [...] discards 3c5e6176312 171: onsuccess: #706: 1: Success after binutils/gcc/linux/g [...] discards 14ff0da6744 170: onsuccess: #705: 1: Success after binutils/gcc/glibc/g [...] discards 1e938b519d2 169: onsuccess: #704: 1: Success after binutils/gcc/linux/g [...] discards 1743e2cc443 168: onsuccess: #703: 1: Success after binutils/gcc/linux/g [...] discards 4f083506b6d 167: onsuccess: #702: 1: Success after binutils/gcc/linux/g [...] discards 268ee384c06 166: onsuccess: #701: 1: Success after binutils/gcc/linux/g [...] discards 87a810fe608 165: onsuccess: #700: 1: Success after binutils/gcc/linux/g [...] discards 72fc56fa006 164: onsuccess: #699: 1: Success after binutils/gcc/linux/g [...] discards a4c268c9f42 163: onsuccess: #698: 1: Success after binutils/gcc/linux/g [...] discards 93cbc78b6b1 162: onsuccess: #697: 1: Success after binutils/gcc/linux/g [...] discards 31316713d13 161: onsuccess: #696: 1: Success after binutils/gcc/linux/g [...] discards 1c8f360c26b 160: onsuccess: #695: 1: Success after binutils/gcc/linux/g [...] discards 2700d713e89 159: onsuccess: #694: 1: Success after binutils/gcc/linux/g [...] discards 393985b1eed 158: onsuccess: #693: 1: Success after binutils/gcc/linux/g [...] discards c7401599a15 157: onsuccess: #692: 1: Success after binutils/gcc/linux/g [...] discards f43e9481e09 156: onsuccess: #691: 1: Success after binutils/gcc/linux/g [...] discards d50d4b5362a 155: onsuccess: #690: 1: Success after binutils/gcc/linux/g [...] discards 1839e7aef78 154: onsuccess: #689: 1: Success after binutils/gcc/linux/g [...] discards 53aef1da200 153: onsuccess: #688: 1: Success after binutils/gcc/linux/g [...] discards 3ba01d58221 152: onsuccess: #687: 1: Success after binutils/gcc/linux/g [...] discards 86c0bb03a9e 151: onsuccess: #686: 1: Success after binutils/gcc/linux/g [...] discards 63956c691a3 150: onsuccess: #685: 1: Success after binutils/gcc/glibc/g [...] discards 1585631af91 149: onsuccess: #684: 1: Success after linux: 10 commits discards a226781b670 148: onsuccess: #683: 1: Success after glibc: 9 commits discards 3a173db8930 147: onsuccess: #681: 1: Success after gcc: 6 commits discards 29add306075 146: onsuccess: #680: 1: Success after binutils: 20 commits discards 940cfd06329 145: onsuccess: #678: 1: Success after binutils/gcc/linux/g [...] discards 0f6d4bbdf9c 144: onsuccess: #677: 1: Success after binutils/gcc/linux/g [...] discards 66946f7634e 143: onsuccess: #676: 1: Success after binutils/gcc/linux/g [...] discards 4b6337d39a4 142: onsuccess: #675: 1: Success after binutils/gcc/linux/g [...] discards 26cea8c3c8b 141: onsuccess: #674: 1: Success after binutils/gcc/gdb: 12 [...] discards 0486b8a2d74 140: onsuccess: #673: 1: Success after binutils/gcc/gdb: 26 [...] discards 0c7480450a7 139: onsuccess: #672: 1: Success after binutils/gcc/gdb: 28 [...] discards 827a55100c9 138: onsuccess: #671: 1: Success after binutils/gcc/linux/g [...] discards a88627d0897 137: onsuccess: #670: 1: Success after binutils/gcc/gdb: 46 [...] discards 4c69af23a49 136: onsuccess: #669: 1: Success after binutils/gcc/linux/g [...] discards 819c92be357 135: onsuccess: #668: 1: Success after binutils/gcc/linux/g [...] discards 69437c375d1 134: onsuccess: #667: 1: Success after binutils/gcc/linux/g [...] discards ea35e0a1a4f 133: onsuccess: #666: 1: Success after binutils/gcc/linux/g [...] discards 377fe0eabbc 132: onsuccess: #665: 1: Success after binutils/gcc/linux/g [...] discards 3151c019f1a 131: onsuccess: #664: 1: Success after binutils/gcc/glibc/g [...] discards 2387e7ece9d 130: onsuccess: #663: 1: Success after binutils/gcc/linux/g [...] discards f87f48cc26d 129: onsuccess: #662: 1: Success after binutils/gcc/linux/g [...] discards 6db6c793ecb 128: onsuccess: #661: 1: Success after binutils/gcc/linux/g [...] discards d5e6879e7ab 127: onsuccess: #660: 1: Success after binutils/gcc/linux/g [...] discards e3a2bcacd6f 126: onsuccess: #659: 1: Success after binutils/gcc/linux/g [...] discards af866fc37f5 125: onsuccess: #658: 1: Success after linux: 3224 commits discards 52281e8c090 124: onsuccess: #657: 1: Success after glibc: 2 commits discards e65b2ce7ef4 123: onsuccess: #655: 1: Success after binutils: 22 commits discards 7d012b71f8a 122: onsuccess: #653: 1: Success after binutils/gcc/linux/g [...] discards aee708bb663 121: onsuccess: #652: 1: Success after binutils/gcc/linux/g [...] discards 01835fb520f 120: onsuccess: #651: 1: Success after binutils/gcc/linux/g [...] discards 9915516ff11 119: onsuccess: #650: 1: Success after binutils/gcc/linux/g [...] discards b0f972d4e6d 118: onsuccess: #649: 1: Success after binutils/gcc/linux/g [...] discards ef96c8cf97d 117: onsuccess: #648: 1: Success after binutils/gcc/linux/g [...] new 3e7660e29c3 117: onsuccess: #648: 1: Success after binutils/gcc/linux/g [...] new 8f4fe08e694 118: onsuccess: #649: 1: Success after binutils/gcc/linux/g [...] new 4c123a726d6 119: onsuccess: #650: 1: Success after binutils/gcc/linux/g [...] new 346195e0b79 120: onsuccess: #651: 1: Success after binutils/gcc/linux/g [...] new 203186d94d6 121: onsuccess: #652: 1: Success after binutils/gcc/linux/g [...] new 56ebc96a925 122: onsuccess: #653: 1: Success after binutils/gcc/linux/g [...] new c61356f161f 123: onsuccess: #655: 1: Success after binutils: 22 commits new a3a9cc8c7c6 124: onsuccess: #657: 1: Success after glibc: 2 commits new c2855d4c8ed 125: onsuccess: #658: 1: Success after linux: 3224 commits new e67f4318839 126: onsuccess: #659: 1: Success after binutils/gcc/linux/g [...] new e88e7bd2523 127: onsuccess: #660: 1: Success after binutils/gcc/linux/g [...] new 64f22b80227 128: onsuccess: #661: 1: Success after binutils/gcc/linux/g [...] new 6252db7efee 129: onsuccess: #662: 1: Success after binutils/gcc/linux/g [...] new 38c94fece50 130: onsuccess: #663: 1: Success after binutils/gcc/linux/g [...] new 8f565646fb0 131: onsuccess: #664: 1: Success after binutils/gcc/glibc/g [...] new 78bf2ebf887 132: onsuccess: #665: 1: Success after binutils/gcc/linux/g [...] new 1623678f8b5 133: onsuccess: #666: 1: Success after binutils/gcc/linux/g [...] new d8b258543db 134: onsuccess: #667: 1: Success after binutils/gcc/linux/g [...] new afc89332a7d 135: onsuccess: #668: 1: Success after binutils/gcc/linux/g [...] new 22385ec453d 136: onsuccess: #669: 1: Success after binutils/gcc/linux/g [...] new c5637ea760b 137: onsuccess: #670: 1: Success after binutils/gcc/gdb: 46 [...] new ba703a6191c 138: onsuccess: #671: 1: Success after binutils/gcc/linux/g [...] new 2e1f917b76a 139: onsuccess: #672: 1: Success after binutils/gcc/gdb: 28 [...] new 479e697a3d1 140: onsuccess: #673: 1: Success after binutils/gcc/gdb: 26 [...] new 9972de91ecc 141: onsuccess: #674: 1: Success after binutils/gcc/gdb: 12 [...] new 52759a745e9 142: onsuccess: #675: 1: Success after binutils/gcc/linux/g [...] new 4725e9ad33e 143: onsuccess: #676: 1: Success after binutils/gcc/linux/g [...] new b0c7e37b26c 144: onsuccess: #677: 1: Success after binutils/gcc/linux/g [...] new bd19d26d271 145: onsuccess: #678: 1: Success after binutils/gcc/linux/g [...] new 26ed271500c 146: onsuccess: #680: 1: Success after binutils: 20 commits new 59ecc2b9da5 147: onsuccess: #681: 1: Success after gcc: 6 commits new f0796fd7eeb 148: onsuccess: #683: 1: Success after glibc: 9 commits new b362726024f 149: onsuccess: #684: 1: Success after linux: 10 commits new 59988c67f91 150: onsuccess: #685: 1: Success after binutils/gcc/glibc/g [...] new ac7275ace9a 151: onsuccess: #686: 1: Success after binutils/gcc/linux/g [...] new 2c913f18501 152: onsuccess: #687: 1: Success after binutils/gcc/linux/g [...] new eeddbccee01 153: onsuccess: #688: 1: Success after binutils/gcc/linux/g [...] new 873fa6feec4 154: onsuccess: #689: 1: Success after binutils/gcc/linux/g [...] new 47e0ea2a856 155: onsuccess: #690: 1: Success after binutils/gcc/linux/g [...] new ce597050f64 156: onsuccess: #691: 1: Success after binutils/gcc/linux/g [...] new 9acc4375693 157: onsuccess: #692: 1: Success after binutils/gcc/linux/g [...] new dcb3f104da1 158: onsuccess: #693: 1: Success after binutils/gcc/linux/g [...] new 7c2e0993986 159: onsuccess: #694: 1: Success after binutils/gcc/linux/g [...] new b00d17d6fbf 160: onsuccess: #695: 1: Success after binutils/gcc/linux/g [...] new 57ce9578344 161: onsuccess: #696: 1: Success after binutils/gcc/linux/g [...] new cd22e17241a 162: onsuccess: #697: 1: Success after binutils/gcc/linux/g [...] new cb0cf3c2a16 163: onsuccess: #698: 1: Success after binutils/gcc/linux/g [...] new cadad796dd1 164: onsuccess: #699: 1: Success after binutils/gcc/linux/g [...] new d12545e8faa 165: onsuccess: #700: 1: Success after binutils/gcc/linux/g [...] new bb75e05f08c 166: onsuccess: #701: 1: Success after binutils/gcc/linux/g [...] new fe260035609 167: onsuccess: #702: 1: Success after binutils/gcc/linux/g [...] new 55b71e8a830 168: onsuccess: #703: 1: Success after binutils/gcc/linux/g [...] new 6052608dced 169: onsuccess: #704: 1: Success after binutils/gcc/linux/g [...] new c8bdb969020 170: onsuccess: #705: 1: Success after binutils/gcc/glibc/g [...] new 9c4d7d145a4 171: onsuccess: #706: 1: Success after binutils/gcc/linux/g [...] new e30c177741f 172: onsuccess: #707: 1: Success after binutils/gcc/linux/g [...] new 2e689d3f72c 173: onsuccess: #708: 1: Success after binutils/gcc/linux/g [...] new e7bedfb4c56 174: onsuccess: #709: 1: Success after binutils/gcc/linux/g [...] new e44d75718a5 175: onsuccess: #710: 1: Success after binutils/gcc/linux/g [...] new c47cd983595 176: onsuccess: #711: 1: Success after binutils/gcc/linux/g [...] new aff3bd9230c 177: onsuccess: #712: 1: Success after binutils/gcc/linux/g [...] new 5635356dee8 178: onsuccess: #714: 1: Success after binutils/gcc/linux/g [...] new 6237796f60a 179: onsuccess: #715: 1: Success after binutils/gcc/linux/g [...] new 54168336773 180: onsuccess: #716: 1: Success after binutils/gcc/linux/g [...] new 6ec4c2fa980 181: onsuccess: #717: 1: Success after binutils/gcc/linux/g [...] new e06cc71b5bd 182: onsuccess: #718: 1: Success after binutils/gcc/linux/g [...] new b1d1408c004 183: onsuccess: #719: 1: Success after binutils/gcc/gdb: 20 [...] new edebfb21bce 184: onsuccess: #720: 1: Success after binutils/gcc/linux/g [...] new 815d79f6575 185: onsuccess: #721: 1: Success after binutils/gcc/linux/g [...] new 54110599d75 186: onsuccess: #722: 1: Success after binutils/gcc/linux/g [...] new 53ac65108a6 187: onsuccess: #723: 1: Success after binutils/gcc/linux/g [...] new 55adbdf32ce 188: onsuccess: #724: 1: Success after binutils/gcc/linux/g [...] new a202c5fd696 189: onsuccess: #725: 1: Success after binutils/gcc/linux/g [...] new 70b2da3cf0b 190: onsuccess: #726: 1: Success after binutils/gcc/linux/g [...] new 2e88ae65906 191: onsuccess: #1: 1: Success after binutils/gcc/linux/gli [...] new caf6d0f8249 192: onsuccess: #2: 1: Success after binutils/gcc/linux/gdb [...] new a73b2e3d85a 193: onsuccess: #3: 1: Success after binutils/gcc/linux/gli [...] new 88150580b10 194: onsuccess: #4: 1: Success after binutils/gcc/linux/gdb [...] new 9d5c2d2a159 195: onsuccess: #5: 1: Success after binutils/gcc/linux/gli [...] new 34745968269 196: onsuccess: #6: 1: Success after binutils/gcc/linux/gli [...] new 373e07c43ae 197: onsuccess: #7: 1: Success after binutils/gcc/linux/gli [...] new 794789d21e9 198: onsuccess: #8: 1: Success after binutils/gcc/linux/gli [...] new 121a91851d0 199: onsuccess: #9: 1: Success after binutils/gcc/linux/gdb [...] new 0317379b294 200: onsuccess: #10: 1: Success after binutils/gcc/linux/gd [...] new 3651b2c7281 201: onsuccess: #11: 1: Success after binutils/gcc/linux/gd [...] new dc837a5bbaa 202: onsuccess: #12: 1: Success after binutils/gcc/linux/gl [...] new 7906b1dc03d 203: onsuccess: #13: 1: Success after binutils/gcc/linux/gl [...] new 936c7b28a2d 204: onsuccess: #14: 1: Success after binutils/gcc/linux/gl [...] new 1352a6270ff 205: onsuccess: #15: 1: Success after binutils/gcc/linux/gd [...] new 291f20c78c8 206: onsuccess: #16: 1: Success after binutils/gcc/linux/gl [...] new c524bd299fd 207: onsuccess: #17: 1: Success after binutils/gcc/linux/gd [...] new 20f8ea4d69e 208: onsuccess: #18: 1: Success after binutils/gcc/linux/gl [...] new 75f555064e3 209: onsuccess: #19: 1: Success after binutils/gcc/linux/gl [...] new 7a3b5a70ce8 210: onsuccess: #20: 1: Success after binutils/gcc/linux/gl [...] new c856b740850 211: onsuccess: #23: 1: Success after gcc/linux/gdb: 43 commits new ef413868a24 212: force: #24: 1: Success after binutils: 2 commits new 934c4e1dca7 213: force: #25: 1: Failure after gdb-13-branchpoint-1445-g [...] new 55e1c6fef11 214: onsuccess: #26: 1: Success after binutils: 12 commits new 27ea28bde4b 215: onsuccess: #27: 1: Success after binutils/gcc/linux/gd [...] new 258ae2c2458 216: onsuccess: #30: 1: Success after binutils/gcc/linux/gd [...] new 56a6ba4d7d7 217: onsuccess: #31: 1: Success after binutils/gcc/linux/gd [...] new 6c42d888502 218: onsuccess: #32: 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 (50d527d5199) \ 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 1792 -> 1932 bytes 02-prepare_abe/console.log.xz | Bin 2508 -> 2548 bytes 03-build_abe-binutils/console.log.xz | Bin 34864 -> 35556 bytes 04-build_abe-gcc/console.log.xz | Bin 202864 -> 203944 bytes 06-build_abe-linux/console.log.xz | Bin 8392 -> 8340 bytes 07-build_abe-glibc/console.log.xz | Bin 241760 -> 241596 bytes 08-build_abe-gdb/console.log.xz | Bin 34492 -> 35296 bytes 09-build_abe-dejagnu/console.log.xz | Bin 3780 -> 3780 bytes 10-build_abe-check_binutils/console.log.xz | Bin 2096 -> 2680 bytes 11-check_regression/console.log.xz | Bin 4732 -> 4968 bytes 11-check_regression/results.compare | 4 +- 11-check_regression/results.compare2 | 4 +- 12-update_baseline/console.log | 58 ++++++++++++++--------------- 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/binutils.log.xz | Bin 62964 -> 63020 bytes sumfiles/binutils.sum | 2 +- sumfiles/gas.log.xz | Bin 83984 -> 83988 bytes sumfiles/gas.sum | 4 +- sumfiles/ld.log.xz | Bin 122500 -> 122492 bytes sumfiles/ld.sum | 4 +- 29 files changed, 66 insertions(+), 66 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

1 year, 8 months

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_gnu_cross_check_gcc/master-arm updated (e60c20a7534 -> 67bfee24a40)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. tcwg-buildslave pushed a change to branch linaro-local/ci/tcwg_gnu_cross_check_gcc/master-arm in repository toolchain/ci/base-artifacts. discards e60c20a7534 470: onsuccess: #31: 1: Success after binutils/gcc/linux/gd [...] discards 28acde0c3e0 469: onsuccess: #30: 1: Success after binutils/gcc/linux/gd [...] discards 53669eb95a8 468: onsuccess: #29: 1: Success after binutils/gcc/linux/gd [...] discards a65cabf876a 467: onsuccess: #28: 1: Success after binutils/gcc/linux/gd [...] discards 12e91764063 466: onsuccess: #27: 1: Success after binutils/gcc/linux/gd [...] discards c6a602abc08 465: onsuccess: #26: 1: Success after binutils/gcc/linux/gd [...] discards 2fc5acf9737 464: onsuccess: #25: 1: Success after binutils/gcc/linux/gl [...] discards 768fe99e386 463: onsuccess: #24: 1: Success after binutils/gcc/linux/gl [...] discards 5f5b473fe25 462: onsuccess: #23: 1: Success after binutils/gcc/linux/gl [...] discards 6ca54c5b960 461: onsuccess: #22: 1: Success after binutils/gcc/linux/gd [...] discards 72d248603b4 460: onsuccess: #21: 1: Success after binutils/gcc/linux/gl [...] discards 087d6e9ccc8 459: onsuccess: #20: 1: Success after binutils/gcc/linux/gd [...] discards 35ebfd9b118 458: onsuccess: #19: 1: Success after binutils/gcc/linux/gl [...] discards e8c61c384e2 457: onsuccess: #18: 1: Success after binutils/gcc/linux/gl [...] discards e91e24a320e 456: onsuccess: #17: 1: Success after binutils/gcc/linux/gl [...] discards b12c86393d2 455: onsuccess: #16: 1: Success after binutils/gcc/linux/gd [...] discards 9351b11cf40 454: onsuccess: #15: 1: Success after binutils/gcc/linux/gd [...] discards 18538c7811c 453: onsuccess: #14: 1: Success after binutils/gcc/linux/gd [...] discards 1ebadf32f8e 452: onsuccess: #13: 1: Success after binutils/gcc/linux/gl [...] discards 931a3b8aebc 451: onsuccess: #12: 1: Success after binutils/gcc/linux/gl [...] discards b410236459b 450: onsuccess: #11: 1: Success after binutils/gcc/linux/gl [...] discards aa18f89cef0 449: onsuccess: #10: 1: Success after binutils/gcc/linux/gl [...] discards aede9d48e9e 448: onsuccess: #9: 1: Success after binutils/gcc/linux/gdb [...] discards 31bee5e8beb 447: onsuccess: #8: 1: Success after binutils/gcc/linux/gli [...] discards d84c5ab7c02 446: onsuccess: #7: 1: Success after binutils/gcc/gdb: 5 commits discards 24c6877fb5a 445: onsuccess: #6: 1: Success after binutils/gcc/linux/gdb [...] discards fb1fc1af63e 444: onsuccess: #5: 1: Success after binutils/gcc/linux/gli [...] discards ae3163fc390 443: onsuccess: #4: 1: Success after binutils/gcc/gdb/qemu: [...] discards ee71e2dfbeb 442: onsuccess: #3: 1: Success after binutils/gcc/glibc/gdb [...] discards dd3041be893 441: onsuccess: #2266: 1: Success after binutils/gcc/linux/ [...] discards 6a24384b4f9 440: onsuccess: #2265: 1: Success after binutils/gcc/linux/ [...] discards 14c014e0cb1 439: onsuccess: #2264: 1: Success after binutils/gcc/gdb: 1 [...] discards 02e89c4e2ef 438: onsuccess: #2263: 1: Success after binutils/gcc/linux/ [...] discards 08c08d5b3ca 437: onsuccess: #2261: 1: Success after binutils/gcc/glibc/ [...] discards 2e030245184 436: onsuccess: #2260: 1: Success after gcc: 7 commits discards fbf9d4f408d 435: onsuccess: #2259: 1: Success after binutils/gcc/linux/ [...] discards 6d18c065235 434: onsuccess: #2258: 1: Success after binutils/gcc/linux/ [...] discards 232e84445be 433: onsuccess: #2257: 1: Success after binutils/gcc/gdb/qe [...] discards 73735914f79 432: onsuccess: #2256: 1: Success after binutils/gdb: 10 commits discards b7d3f1439e1 431: onsuccess: #2255: 1: Success after binutils/gcc/linux/ [...] discards 7b3444d8cee 430: onsuccess: #2254: 1: Success after binutils/gcc/linux/ [...] discards 0ab357a3671 429: onsuccess: #2253: 1: Success after binutils/gcc/glibc/ [...] discards b127f59674f 428: onsuccess: #2252: 1: Success after binutils/gdb: 2 commits discards ca308419371 427: onsuccess: #2251: 1: Success after binutils/gcc/linux/ [...] discards fefedea6562 426: onsuccess: #2250: 1: Success after binutils/linux/gdb: [...] discards d60bc8b1083 425: onsuccess: #2249: 1: Success after binutils/gcc/linux/ [...] discards 474748c499a 424: onsuccess: #2248: 1: Success after gcc: 6 commits discards aef8f7fec48 423: onsuccess: #2247: 1: Success after gcc/linux: 8 commits discards 017ffa97f44 422: onsuccess: #2246: 1: Success after binutils/gcc/linux/ [...] discards d1804d96599 421: onsuccess: #2245: 1: Success after binutils/gcc/glibc/ [...] discards 88810759cfe 420: onsuccess: #2244: 1: Success after gcc/glibc: 5 commits discards 6e5ce788597 419: onsuccess: #2243: 1: Success after binutils/gcc/linux/ [...] discards f0a1a7f2dce 418: onsuccess: #2239: 1: Success after binutils/gcc/gdb: 5 [...] discards 7e14784ff42 417: onsuccess: #2238: 1: Success after binutils/gcc/linux/ [...] discards bfe8ecc8c61 416: onsuccess: #2237: 1: Success after binutils/gcc/glibc/ [...] discards 634ed743cf4 415: onsuccess: #2236: 1: Success after binutils/gcc/gdb: 1 [...] discards 8ee6c0b1f23 414: onsuccess: #2235: 1: Success after binutils/gcc/gdb: 1 [...] discards 05701e1c78c 413: onsuccess: #2234: 1: Success after binutils/gcc/linux/ [...] discards c2501f2500c 412: onsuccess: #2233: 1: Success after binutils/gcc/glibc/ [...] discards 53dd5159a44 411: onsuccess: #2232: 1: Success after gcc: 3 commits discards 493eaaf913f 410: onsuccess: #2231: 1: Success after binutils/gcc/linux/ [...] discards 3ecaa7be941 409: onsuccess: #2230: 1: Success after binutils/gcc/glibc/ [...] discards 1a6f507cf9e 408: onsuccess: #2229: 1: Success after binutils/gcc/gdb: 2 [...] discards 6734edbb1e1 407: onsuccess: #2228: 1: Success after binutils/gcc/linux/ [...] discards 824947b0704 406: onsuccess: #2227: 1: Success after binutils/linux/glib [...] discards 1dc7bde450f 405: onsuccess: #2226: 1: Success after gcc/glibc: 39 commits discards 7893235dece 404: onsuccess: #2225: 1: Success after binutils/gcc/gdb: 1 [...] discards aebbced5a95 403: onsuccess: #2224: 1: Success after binutils/gcc/linux/ [...] discards 2f37d5ac5db 402: onsuccess: #2223: 1: Success after binutils/gcc/gdb: 1 [...] discards 5f5034897f3 401: onsuccess: #2222: 1: Success after binutils/gcc/gdb: 1 [...] discards 99d8a0f3038 400: onsuccess: #2221: 1: Success after binutils/gcc/linux/ [...] discards 4f3cce3ad92 399: onsuccess: #2220: 1: Success after binutils/gcc/linux/ [...] discards d74baf3961b 398: onsuccess: #2219: 1: Success after binutils/gcc/gdb/qe [...] discards 0d2d431fde3 397: onsuccess: #2218: 1: Success after binutils/gcc/linux/ [...] discards e6b4abf4c62 396: onsuccess: #2217: 1: Success after binutils/gcc/linux/ [...] discards 0d000b4d49a 395: onsuccess: #2216: 1: Success after binutils/gcc/linux/ [...] discards f3e4c76b6d7 394: onsuccess: #2215: 1: Success after binutils/gcc/gdb: 8 [...] discards 4170060debb 393: onsuccess: #2214: 1: Success after binutils/gcc/gdb: 1 [...] discards 4c04d3d2cd3 392: onsuccess: #2213: 1: Success after binutils/gcc/glibc/ [...] discards 957c333deae 391: onsuccess: #2212: 1: Success after binutils/gcc/gdb/qe [...] discards 4ecb2c31510 390: onsuccess: #2211: 1: Success after binutils/gcc/linux/ [...] discards c90b9255d0d 389: onsuccess: #2210: 1: Success after binutils/gcc/linux/ [...] discards ff307abfb2e 388: onsuccess: #2209: 1: Success after binutils/gcc/glibc/ [...] discards bd9d1e2364b 387: onsuccess: #2208: 1: Success after gcc: 2 commits discards cd506d7e3e6 386: onsuccess: #2207: 1: Success after binutils/gcc/linux/ [...] discards f8e7971bb15 385: onsuccess: #2206: 1: Success after binutils/gcc/glibc/ [...] discards f807fe8d163 384: onsuccess: #2205: 1: Success after gcc: 2 commits discards c22c296df89 383: onsuccess: #2204: 1: Success after binutils/gcc/linux/ [...] discards c0b099ea099 382: onsuccess: #2203: 1: Success after gcc/qemu: 42 commits discards 7e308a1e1f8 381: onsuccess: #2202: 1: Success after glibc-2.37.9000-17- [...] discards bff94cd179c 380: onsuccess: #2201: 1: Success after binutils/gcc/linux/ [...] discards 078db411a15 379: onsuccess: #2200: 1: Success after binutils/gcc/linux/ [...] discards 4214cf099df 378: onsuccess: #2199: 1: Success after binutils/gdb: 4 commits discards 6a63816f020 377: onsuccess: #2198: 1: Success after binutils/gcc/gdb: 3 [...] discards 6944ee089d3 376: onsuccess: #2197: 1: Success after binutils/gcc/linux/ [...] discards d0afa2b8dc1 375: onsuccess: #2195: 1: Success after binutils/gcc/gdb/qe [...] discards 9b1c45fd46d 374: onsuccess: #2194: 1: Success after binutils/gcc/linux/ [...] discards a9017812be9 373: onsuccess: #2193: 1: Success after binutils/gcc/glibc/ [...] discards 21f497d7a4e 372: onsuccess: #2192: 1: Success after binutils/gcc/linux/ [...] discards 511cd96adcf 371: onsuccess: #2191: 1: Success after binutils/gcc/gdb: 1 [...] discards 7f2af18a0ea 370: onsuccess: #2190: 1: Success after binutils/gcc/linux/ [...] new 31176e65d48 370: onsuccess: #2190: 1: Success after binutils/gcc/linux/ [...] new e2f0f38286f 371: onsuccess: #2191: 1: Success after binutils/gcc/gdb: 1 [...] new a550897f12a 372: onsuccess: #2192: 1: Success after binutils/gcc/linux/ [...] new deb7c0b8f2e 373: onsuccess: #2193: 1: Success after binutils/gcc/glibc/ [...] new 3c95b88f83c 374: onsuccess: #2194: 1: Success after binutils/gcc/linux/ [...] new 4e28d52c31e 375: onsuccess: #2195: 1: Success after binutils/gcc/gdb/qe [...] new a84ad6af4df 376: onsuccess: #2197: 1: Success after binutils/gcc/linux/ [...] new e268aa09e3a 377: onsuccess: #2198: 1: Success after binutils/gcc/gdb: 3 [...] new c8e426eb6b1 378: onsuccess: #2199: 1: Success after binutils/gdb: 4 commits new 47186aca8cf 379: onsuccess: #2200: 1: Success after binutils/gcc/linux/ [...] new 2392a2a0b72 380: onsuccess: #2201: 1: Success after binutils/gcc/linux/ [...] new ec79c060f88 381: onsuccess: #2202: 1: Success after glibc-2.37.9000-17- [...] new 39b2b9cccd3 382: onsuccess: #2203: 1: Success after gcc/qemu: 42 commits new 0dfa2753957 383: onsuccess: #2204: 1: Success after binutils/gcc/linux/ [...] new 1722ce46bbd 384: onsuccess: #2205: 1: Success after gcc: 2 commits new 04d900cbdb2 385: onsuccess: #2206: 1: Success after binutils/gcc/glibc/ [...] new 426c7ef459a 386: onsuccess: #2207: 1: Success after binutils/gcc/linux/ [...] new 2091364c9e7 387: onsuccess: #2208: 1: Success after gcc: 2 commits new 3754a508b18 388: onsuccess: #2209: 1: Success after binutils/gcc/glibc/ [...] new d01093318f0 389: onsuccess: #2210: 1: Success after binutils/gcc/linux/ [...] new 7861c53c0ec 390: onsuccess: #2211: 1: Success after binutils/gcc/linux/ [...] new d084682f48e 391: onsuccess: #2212: 1: Success after binutils/gcc/gdb/qe [...] new f14a56b1146 392: onsuccess: #2213: 1: Success after binutils/gcc/glibc/ [...] new 9eb63b3e781 393: onsuccess: #2214: 1: Success after binutils/gcc/gdb: 1 [...] new 65c49271557 394: onsuccess: #2215: 1: Success after binutils/gcc/gdb: 8 [...] new 0322a9e5503 395: onsuccess: #2216: 1: Success after binutils/gcc/linux/ [...] new 98c91262356 396: onsuccess: #2217: 1: Success after binutils/gcc/linux/ [...] new d17612d8d6c 397: onsuccess: #2218: 1: Success after binutils/gcc/linux/ [...] new 79ec635f8c5 398: onsuccess: #2219: 1: Success after binutils/gcc/gdb/qe [...] new b6da4a5e0c3 399: onsuccess: #2220: 1: Success after binutils/gcc/linux/ [...] new 9f2447d2d4b 400: onsuccess: #2221: 1: Success after binutils/gcc/linux/ [...] new 925eec61eb1 401: onsuccess: #2222: 1: Success after binutils/gcc/gdb: 1 [...] new bf64db35ba4 402: onsuccess: #2223: 1: Success after binutils/gcc/gdb: 1 [...] new c1f369cffd5 403: onsuccess: #2224: 1: Success after binutils/gcc/linux/ [...] new ffa8086a061 404: onsuccess: #2225: 1: Success after binutils/gcc/gdb: 1 [...] new e39736600a5 405: onsuccess: #2226: 1: Success after gcc/glibc: 39 commits new 47a442265a4 406: onsuccess: #2227: 1: Success after binutils/linux/glib [...] new 9cd6ffb5e58 407: onsuccess: #2228: 1: Success after binutils/gcc/linux/ [...] new 6433d000e16 408: onsuccess: #2229: 1: Success after binutils/gcc/gdb: 2 [...] new 7dab002a472 409: onsuccess: #2230: 1: Success after binutils/gcc/glibc/ [...] new c43ae544d33 410: onsuccess: #2231: 1: Success after binutils/gcc/linux/ [...] new d403b6fa070 411: onsuccess: #2232: 1: Success after gcc: 3 commits new 0bd9ffe1904 412: onsuccess: #2233: 1: Success after binutils/gcc/glibc/ [...] new 2e8ca8c1100 413: onsuccess: #2234: 1: Success after binutils/gcc/linux/ [...] new 64c8b7fdbd8 414: onsuccess: #2235: 1: Success after binutils/gcc/gdb: 1 [...] new 9b6717cdd6a 415: onsuccess: #2236: 1: Success after binutils/gcc/gdb: 1 [...] new dbe42ce4564 416: onsuccess: #2237: 1: Success after binutils/gcc/glibc/ [...] new 6bb08cb5efb 417: onsuccess: #2238: 1: Success after binutils/gcc/linux/ [...] new c707068901f 418: onsuccess: #2239: 1: Success after binutils/gcc/gdb: 5 [...] new ce48bd18578 419: onsuccess: #2243: 1: Success after binutils/gcc/linux/ [...] new 13ee283dc95 420: onsuccess: #2244: 1: Success after gcc/glibc: 5 commits new b18d7015440 421: onsuccess: #2245: 1: Success after binutils/gcc/glibc/ [...] new ddc6896d499 422: onsuccess: #2246: 1: Success after binutils/gcc/linux/ [...] new 89065d51cc3 423: onsuccess: #2247: 1: Success after gcc/linux: 8 commits new 962953b42da 424: onsuccess: #2248: 1: Success after gcc: 6 commits new 652378996c8 425: onsuccess: #2249: 1: Success after binutils/gcc/linux/ [...] new 3fd9a148cd1 426: onsuccess: #2250: 1: Success after binutils/linux/gdb: [...] new 3595e3bf960 427: onsuccess: #2251: 1: Success after binutils/gcc/linux/ [...] new 4342808175d 428: onsuccess: #2252: 1: Success after binutils/gdb: 2 commits new 6c15ed91f61 429: onsuccess: #2253: 1: Success after binutils/gcc/glibc/ [...] new 400cfa0d20c 430: onsuccess: #2254: 1: Success after binutils/gcc/linux/ [...] new adccb3e0ce7 431: onsuccess: #2255: 1: Success after binutils/gcc/linux/ [...] new d04e5b0df68 432: onsuccess: #2256: 1: Success after binutils/gdb: 10 commits new f5577128261 433: onsuccess: #2257: 1: Success after binutils/gcc/gdb/qe [...] new be2a083902a 434: onsuccess: #2258: 1: Success after binutils/gcc/linux/ [...] new 83969525c06 435: onsuccess: #2259: 1: Success after binutils/gcc/linux/ [...] new 511a92793e3 436: onsuccess: #2260: 1: Success after gcc: 7 commits new 1596a74ad98 437: onsuccess: #2261: 1: Success after binutils/gcc/glibc/ [...] new a40b6f24569 438: onsuccess: #2263: 1: Success after binutils/gcc/linux/ [...] new 1881cf498e7 439: onsuccess: #2264: 1: Success after binutils/gcc/gdb: 1 [...] new b3e34e5bd8e 440: onsuccess: #2265: 1: Success after binutils/gcc/linux/ [...] new 560d2a4bfa5 441: onsuccess: #2266: 1: Success after binutils/gcc/linux/ [...] new 32c4ae6c6fc 442: onsuccess: #3: 1: Success after binutils/gcc/glibc/gdb [...] new 782025cff01 443: onsuccess: #4: 1: Success after binutils/gcc/gdb/qemu: [...] new 515a1f3e754 444: onsuccess: #5: 1: Success after binutils/gcc/linux/gli [...] new b29686993bc 445: onsuccess: #6: 1: Success after binutils/gcc/linux/gdb [...] new 0d91febddd1 446: onsuccess: #7: 1: Success after binutils/gcc/gdb: 5 commits new 6bc5af3c4f8 447: onsuccess: #8: 1: Success after binutils/gcc/linux/gli [...] new 7f644918844 448: onsuccess: #9: 1: Success after binutils/gcc/linux/gdb [...] new 39d480d4f3e 449: onsuccess: #10: 1: Success after binutils/gcc/linux/gl [...] new fc1da3a2b1f 450: onsuccess: #11: 1: Success after binutils/gcc/linux/gl [...] new cec724ee994 451: onsuccess: #12: 1: Success after binutils/gcc/linux/gl [...] new 268fb211d96 452: onsuccess: #13: 1: Success after binutils/gcc/linux/gl [...] new 8be7608e972 453: onsuccess: #14: 1: Success after binutils/gcc/linux/gd [...] new 8b93160b7a9 454: onsuccess: #15: 1: Success after binutils/gcc/linux/gd [...] new ca98ef92ded 455: onsuccess: #16: 1: Success after binutils/gcc/linux/gd [...] new b964b8efbe0 456: onsuccess: #17: 1: Success after binutils/gcc/linux/gl [...] new dd5964858c7 457: onsuccess: #18: 1: Success after binutils/gcc/linux/gl [...] new 4ccc975d848 458: onsuccess: #19: 1: Success after binutils/gcc/linux/gl [...] new 9cd71b22b46 459: onsuccess: #20: 1: Success after binutils/gcc/linux/gd [...] new 3e82953556e 460: onsuccess: #21: 1: Success after binutils/gcc/linux/gl [...] new 7e7fea2c830 461: onsuccess: #22: 1: Success after binutils/gcc/linux/gd [...] new 950b98966fe 462: onsuccess: #23: 1: Success after binutils/gcc/linux/gl [...] new a10d9a3e643 463: onsuccess: #24: 1: Success after binutils/gcc/linux/gl [...] new 5516c86fd2c 464: onsuccess: #25: 1: Success after binutils/gcc/linux/gl [...] new 22240bc2643 465: onsuccess: #26: 1: Success after binutils/gcc/linux/gd [...] new 3710801bc1c 466: onsuccess: #27: 1: Success after binutils/gcc/linux/gd [...] new 0c455c8fe7c 467: onsuccess: #28: 1: Success after binutils/gcc/linux/gd [...] new 307d0d11a76 468: onsuccess: #29: 1: Success after binutils/gcc/linux/gd [...] new e7e672f1511 469: onsuccess: #30: 1: Success after binutils/gcc/linux/gd [...] new 2ba09143afc 470: onsuccess: #31: 1: Success after binutils/gcc/linux/gd [...] new 67bfee24a40 471: onsuccess: #32: 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 (e60c20a7534) \ 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 1796 -> 1772 bytes 02-prepare_abe/console.log.xz | Bin 2536 -> 2568 bytes 03-build_abe-binutils/console.log.xz | Bin 27016 -> 27632 bytes 04-build_abe-stage1/console.log.xz | Bin 88628 -> 90092 bytes 06-build_abe-linux/console.log.xz | Bin 8408 -> 8364 bytes 07-build_abe-glibc/console.log.xz | Bin 233220 -> 233004 bytes 08-build_abe-stage2/console.log.xz | Bin 224332 -> 226768 bytes 09-build_abe-gdb/console.log.xz | Bin 34488 -> 35216 bytes 10-build_abe-qemu/console.log.xz | Bin 31688 -> 30676 bytes 11-build_abe-dejagnu/console.log.xz | Bin 3820 -> 3816 bytes 12-build_abe-check_gcc/console.log.xz | Bin 6172 -> 7164 bytes 13-check_regression/console.log.xz | Bin 5940 -> 6444 bytes 13-check_regression/results.compare | 16 +- 13-check_regression/results.compare2 | 134 +- 14-update_baseline/console.log | 70 +- dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- git/gdb_rev | 2 +- git/glibc_rev | 2 +- git/linux_rev | 2 +- git/qemu_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 2 +- mail/mail-subject.txt | 2 +- manifest.sh | 48 +- sumfiles/g++.log.sep.xz | Bin 126040 -> 99760 bytes sumfiles/g++.log.xz | Bin 2678108 -> 2662688 bytes sumfiles/g++.sum | 10 +- sumfiles/g++.sum.sep | 4519 +++++++++- sumfiles/gcc.log.sep.xz | Bin 177632 -> 99564 bytes sumfiles/gcc.log.xz | Bin 2208184 -> 2234784 bytes sumfiles/gcc.sum | 25 +- sumfiles/gcc.sum.sep | 14685 +++++++++++++++----------------- sumfiles/gfortran.log.sep.xz | Bin 57272 -> 72852 bytes sumfiles/gfortran.log.xz | Bin 897384 -> 903484 bytes sumfiles/gfortran.sum | 7 +- sumfiles/gfortran.sum.sep | 4252 +-------- sumfiles/libatomic.log.xz | Bin 2284 -> 2288 bytes sumfiles/libatomic.sum | 2 +- sumfiles/libgomp.log.xz | Bin 217132 -> 217260 bytes sumfiles/libgomp.sum | 2 +- sumfiles/libitm.log.xz | Bin 2692 -> 2692 bytes sumfiles/libitm.sum | 2 +- sumfiles/libstdc++.log.sep.xz | Bin 17048 -> 18144 bytes sumfiles/libstdc++.log.xz | Bin 444772 -> 443128 bytes sumfiles/libstdc++.sum | 6 +- sumfiles/libstdc++.sum.sep | 611 +- 48 files changed, 11892 insertions(+), 12517 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

1 year, 8 months

Jump to page:

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

Tcwg-commits March 2023