Tcwg-commits April 2023

tcwg-commits@lists.linaro.org

5 participants
5583 discussions

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_bmk-code_vect-spec2k6/llvm-arm-master-O3_LTO updated (3db101c88bee -> db48711df968)

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/llvm-arm-master-O3_LTO in repository toolchain/ci/base-artifacts. from 3db101c88bee 4: force: #9: 1: Failure after baseline build: no new commits new db48711df968 5: onsuccess: #11: 1: [TCWG CI] Success after llvm: 1252 commits The 1 revisions listed above as "new" are entirely new to this repository and will be described in separate emails. The revisions listed as "adds" were already present in the repository and have only been added to this reference. Summary of changes: 01-reset_artifacts/console.log.xz | Bin 2048 -> 1896 bytes 02-build_bmk_llvm/console.log.xz | Bin 227244 -> 235584 bytes 03-benchmark/benchmark-build.log | 104 +-- 03-benchmark/benchmark.log | 102 +-- 03-benchmark/console.log.xz | Bin 3868 -> 3880 bytes .../compare-results-vs-first-internal.csv | 44 +- .../compare-results-vs-prev-internal.csv | 44 +- 04-check_regression/console.log.xz | Bin 2440 -> 6192 bytes .../csv-results-vs-first-1/perf.csv | 82 +- .../csv-results-vs-first-1/results.csv | 297 +++---- .../csv-results-vs-first-1/size.csv | 233 +++-- 04-check_regression/csv-results-vs-prev-0/perf.csv | 84 +- .../csv-results-vs-prev-0/results.csv | 88 +- 04-check_regression/csv-results-vs-prev-1/perf.csv | 82 +- .../csv-results-vs-prev-1/results.csv | 297 +++---- 04-check_regression/csv-results-vs-prev-1/size.csv | 233 +++-- 04-check_regression/extra-bisect-params | 1 + 04-check_regression/mail-body.txt | 24 +- 04-check_regression/mail-subject.txt | 2 +- .../output-bmk-results/error_code-1 | 0 04-check_regression/results-vs-first-brief.csv | 40 +- 04-check_regression/results-vs-first-full.csv | 88 +- 04-check_regression/results-vs-first-internal.csv | 44 +- 04-check_regression/results-vs-first.csv | 44 +- 04-check_regression/results-vs-first.log | 942 ++++++++++----------- 04-check_regression/results-vs-prev-brief.csv | 40 +- 04-check_regression/results-vs-prev-compare.csv | 1 + 04-check_regression/results-vs-prev-full.csv | 96 ++- 04-check_regression/results-vs-prev-internal.csv | 44 +- 04-check_regression/results-vs-prev.csv | 44 +- 04-check_regression/results-vs-prev.log | 938 ++++++++++---------- 05-update_baseline/console.log | 2 +- dashboard/dashboard-generate.sh | 2 +- .../400.perlbench/results-metadata.json | 10 +- .../squad-vs-first/401.bzip2/results-metadata.json | 10 +- .../squad-vs-first/403.gcc/results-metadata.json | 10 +- .../squad-vs-first/403.gcc/results-metrics.json | 2 +- .../squad-vs-first/429.mcf/results-metadata.json | 10 +- .../squad-vs-first/429.mcf/results-metrics.json | 2 +- .../squad-vs-first/433.milc/results-metadata.json | 10 +- .../squad-vs-first/444.namd/results-metadata.json | 10 +- .../squad-vs-first/444.namd/results-metrics.json | 2 +- .../squad-vs-first/445.gobmk/results-metadata.json | 10 +- .../squad-vs-first/445.gobmk/results-metrics.json | 2 +- .../447.dealII/results-metadata.json | 10 +- .../squad-vs-first/447.dealII/results-metrics.json | 2 +- .../450.soplex/results-metadata.json | 10 +- .../squad-vs-first/450.soplex/results-metrics.json | 2 +- .../453.povray/results-metadata.json | 10 +- .../squad-vs-first/453.povray/results-metrics.json | 2 +- .../squad-vs-first/456.hmmer/results-metadata.json | 10 +- .../squad-vs-first/456.hmmer/results-metrics.json | 2 +- .../squad-vs-first/458.sjeng/results-metadata.json | 10 +- .../squad-vs-first/458.sjeng/results-metrics.json | 2 +- .../462.libquantum/results-metadata.json | 10 +- .../462.libquantum/results-metrics.json | 2 +- .../464.h264ref/results-metadata.json | 10 +- .../464.h264ref/results-metrics.json | 2 +- .../squad-vs-first/470.lbm/results-metadata.json | 10 +- .../471.omnetpp/results-metadata.json | 10 +- .../471.omnetpp/results-metrics.json | 2 +- .../squad-vs-first/473.astar/results-metadata.json | 10 +- .../squad-vs-first/473.astar/results-metrics.json | 2 +- .../482.sphinx3/results-metadata.json | 10 +- .../482.sphinx3/results-metrics.json | 2 +- .../483.xalancbmk/results-metadata.json | 10 +- .../483.xalancbmk/results-metrics.json | 2 +- .../squad-vs-first/Mean/results-metadata.json | 10 +- dashboard/squad-vs-first/dashboard-push-squad.sh | 226 ++--- git/llvm_rev | 2 +- mail/changes-list-long.txt | 8 + mail/changes-list-short.txt | 1 + manifest.sh => mail/last_good.sh | 0 mail/mail-body.txt | 15 - mail/mail-subject.txt | 1 - mail/short-diag.txt | 1 + manifest.sh | 17 +- results_id | 2 +- 78 files changed, 2276 insertions(+), 2269 deletions(-) create mode 100644 04-check_regression/extra-bisect-params copy dashboard/squad-vs-first/summary-annotation.txt => 04-check_regression/output [...] create mode 100644 04-check_regression/results-vs-prev-compare.csv create mode 100644 mail/changes-list-long.txt create mode 100644 mail/changes-list-short.txt copy manifest.sh => mail/last_good.sh (100%) delete mode 100644 mail/mail-body.txt delete mode 100644 mail/mail-subject.txt create mode 100644 mail/short-diag.txt -- To stop receiving notification emails like this one, please contact the administrator of this repository.

1 year, 7 months

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_bmk-code_speed-coremark/gnu_eabi-arm_eabi-master-O3_LTO updated (40576896a8ad -> 88ee6d866cf4)

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-coremark/gnu_eabi-arm_eabi-master-O3_LTO in repository toolchain/ci/base-artifacts. from 40576896a8ad 71: force: #27: 1: [TCWG CI] No change after baseline buil [...] new 88ee6d866cf4 72: onsuccess: #29: 1: [TCWG CI] Success after binutils/gc [...] The 1 revisions listed above as "new" are entirely new to this repository and will be described in separate emails. The revisions listed as "adds" were already present in the repository and have only been added to this reference. Summary of changes: 01-reset_artifacts/console.log.xz | Bin 1928 -> 1984 bytes 02-prepare_abe/console.log.xz | Bin 2500 -> 2552 bytes 03-build_abe-binutils/console.log.xz | Bin 27032 -> 27024 bytes 04-build_abe-stage1/console.log.xz | Bin 87620 -> 87124 bytes 05-clean_sysroot/console.log.xz | Bin 336 -> 336 bytes 06-build_abe-newlib/console.log.xz | Bin 12664 -> 12308 bytes 07-build_abe-stage2/console.log.xz | Bin 162408 -> 162112 bytes 08-benchmark/benchmark-build.log | 106 +++--- 08-benchmark/benchmark.log | 104 +++--- 08-benchmark/console.log.xz | Bin 4044 -> 4016 bytes 09-check_regression/bmk-specific-variability.csv | 6 - 09-check_regression/console.log.xz | Bin 6128 -> 7868 bytes .../csv-results-vs-first-1/results.csv | 6 +- .../csv-results-vs-first-1/size.csv | 6 +- .../csv-results-vs-prev-1/results.csv | 6 +- 09-check_regression/csv-results-vs-prev-1/size.csv | 6 +- 09-check_regression/results-vs-first.log | 86 ++--- 09-check_regression/results-vs-prev.log | 88 ++--- dashboard/dashboard-generate.sh | 2 +- .../squad-vs-first/Coremark/results-metadata.json | 12 +- .../squad-vs-first/Mean/results-metadata.json | 12 +- .../squad-vs-first/coremark/results-metadata.json | 12 +- dashboard/squad-vs-first/dashboard-push-squad.sh | 406 ++++++++++----------- git/binutils_rev | 2 +- git/gcc_rev | 2 +- git/newlib_rev | 2 +- mail/changes-list-long.txt | 20 + mail/changes-list-short.txt | 1 + manifest.sh => mail/last_good.sh | 0 mail/mail-body.txt | 13 - mail/mail-subject.txt | 1 - mail/short-diag.txt | 1 + manifest.sh | 31 +- results_id | 2 +- 34 files changed, 469 insertions(+), 464 deletions(-) create mode 100644 mail/changes-list-long.txt create mode 100644 mail/changes-list-short.txt copy manifest.sh => mail/last_good.sh (100%) delete mode 100644 mail/mail-body.txt delete mode 100644 mail/mail-subject.txt create mode 100644 mail/short-diag.txt -- To stop receiving notification emails like this one, please contact the administrator of this repository.

1 year, 7 months

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_gnu_cross_check_binutils/master-arm updated (a00a4f80d6a9 -> 3d9ff2c4231d)

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_binutils/master-arm in repository toolchain/ci/base-artifacts. from a00a4f80d6a9 8: onsuccess: #10: 1: [TCWG CI] Success after binutils/gcc [...] new 3d9ff2c4231d 9: onsuccess: #11: 1: [TCWG CI] Success 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 2092 -> 2072 bytes 02-prepare_abe/console.log.xz | Bin 2576 -> 2524 bytes 03-build_abe-binutils/console.log.xz | Bin 26972 -> 26900 bytes 04-build_abe-stage1/console.log.xz | Bin 89696 -> 89100 bytes 05-clean_sysroot/console.log.xz | Bin 332 -> 332 bytes 06-build_abe-linux/console.log.xz | Bin 8484 -> 8752 bytes 07-build_abe-glibc/console.log.xz | Bin 233248 -> 232736 bytes 08-build_abe-stage2/console.log.xz | Bin 225336 -> 225412 bytes 09-build_abe-gdb/console.log.xz | Bin 34496 -> 34676 bytes 10-build_abe-qemu/console.log.xz | Bin 31752 -> 32136 bytes 11-build_abe-dejagnu/console.log.xz | Bin 3800 -> 3828 bytes 12-build_abe-check_binutils/console.log.xz | Bin 2212 -> 2208 bytes 13-check_regression/console.log.xz | Bin 4708 -> 5440 bytes 13-check_regression/results.compare | 10 +++---- 13-check_regression/results.compare2 | 6 ++-- 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/changes-list-long.txt | 46 +++++++++++++++++++---------- mail/changes-list-short.txt | 2 +- mail/last_good.sh | 38 ++++++++++++------------ manifest.sh | 44 +++++++++++++-------------- sumfiles/binutils.log.xz | Bin 62208 -> 61040 bytes sumfiles/binutils.sum | 2 +- sumfiles/gas.log.xz | Bin 101060 -> 101024 bytes sumfiles/gas.sum | 4 +-- sumfiles/ld.log.xz | Bin 114140 -> 114176 bytes sumfiles/ld.sum | 4 +-- 31 files changed, 92 insertions(+), 76 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

1 year, 7 months

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_kernel/llvm-master-aarch64-next-allyesconfig updated (72f5f1f467a7 -> c852ec02a695)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. tcwg-buildslave pushed a change to branch linaro-local/ci/tcwg_kernel/llvm-master-aarch64-next-allyesconfig in repository toolchain/ci/base-artifacts. from 72f5f1f467a7 75: onsuccess: #13: 21757: Success after binutils/llvm/lin [...] new c852ec02a695 76: onsuccess: #15: 21786: [TCWG CI] Success after binutil [...] 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 2000 -> 2036 bytes 02-prepare_abe/console.log.xz | Bin 2548 -> 2580 bytes 03-build_abe-binutils/console.log.xz | Bin 27456 -> 27044 bytes 04-build_kernel_llvm/console.log.xz | Bin 67676 -> 65284 bytes 05-build_abe-qemu/console.log.xz | Bin 32248 -> 31948 bytes 06-build_linux/console.log.xz | Bin 3548 -> 3396 bytes 08-check_regression/console.log.xz | Bin 4372 -> 4444 bytes 08-check_regression/jira-body.txt | 1 - 08-check_regression/mail-body.txt | 23 ----------------------- 08-check_regression/mail-subject.txt | 1 - dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/linux_rev | 2 +- git/llvm_rev | 2 +- git/qemu_rev | 2 +- mail/changes-list-long.txt | 26 ++++++++++++++++++++++++++ mail/changes-list-short.txt | 1 + mail/jira-body.txt | 1 - manifest.sh => mail/last_good.sh | 0 mail/mail-body.txt | 23 ----------------------- mail/mail-subject.txt | 1 - mail/short-diag.txt | 1 + manifest.sh | 32 ++++++++++++++++---------------- results | 2 +- 24 files changed, 50 insertions(+), 72 deletions(-) delete mode 100644 08-check_regression/jira-body.txt delete mode 100644 08-check_regression/mail-body.txt delete mode 100644 08-check_regression/mail-subject.txt create mode 100644 mail/changes-list-long.txt create mode 100644 mail/changes-list-short.txt delete mode 100644 mail/jira-body.txt copy manifest.sh => mail/last_good.sh (100%) delete mode 100644 mail/mail-body.txt delete mode 100644 mail/mail-subject.txt create mode 100644 mail/short-diag.txt -- To stop receiving notification emails like this one, please contact the administrator of this repository.

1 year, 7 months

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_gcc_bootstrap/master-aarch64-bootstrap_profiled_lto updated (81d3571e2469 -> 2cccd34dfe6d)

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 81d3571e2469 224: onsuccess: #43: 2: [TCWG CI] Success after binutils/g [...] discards a747db0aec4e 223: onsuccess: #42: 2: [TCWG CI] Success after binutils/g [...] discards 578856b94b17 222: onsuccess: #41: 2: [TCWG CI] Success after binutils/g [...] discards fca86c9b18c5 221: onsuccess: #40: 2: [TCWG CI] Success after binutils/g [...] discards 9861c228198f 220: onsuccess: #39: 1: [TCWG CI] Success after gcc: 2 commits discards ffd08900f1a2 219: force: #38: 1: [TCWG CI] Failure after basepoints/gcc [...] discards 2acc920e6949 218: force: #37: 2: [TCWG CI] Success after gcc: 40 commits discards 8224328754be 217: onsuccess: #35: 2: [TCWG CI] Success after binutils: [...] discards 00fb2c5b3f22 216: onsuccess: #32: 2: Success after binutils/gcc: 5 commits discards a0304dae2e4d 215: onsuccess: #31: 2: Success after binutils/gcc: 7 commits discards c980e25535d1 214: onsuccess: #30: 2: Success after binutils/gcc: 34 commits discards f0edd29b3a4b 213: onsuccess: #29: 2: Success after binutils/gcc: 36 commits discards ce852dc8c7b0 212: onsuccess: #28: 2: Success after binutils/gcc: 34 commits discards a55ffa19f81a 211: onsuccess: #27: 2: Success after binutils/gcc: 41 commits discards cd3b76450320 210: onsuccess: #26: 2: Success after binutils/gcc: 27 commits discards d9c6360812e6 209: onsuccess: #25: 2: Success after binutils/gcc: 12 commits discards 7ff559a8becd 208: onsuccess: #24: 2: Success after binutils/gcc: 44 commits discards 287fee757699 207: onsuccess: #23: 2: Success after binutils/gcc: 75 commits discards e866b7d5b990 206: onsuccess: #21: 2: Success after binutils/gcc: 38 commits discards 1b7b5935ec8f 205: onsuccess: #20: 2: Success after binutils/gcc: 59 commits discards dd633cd766cd 204: onsuccess: #19: 2: Success after binutils/gcc: 39 commits discards 42c980f71ccf 203: onsuccess: #18: 2: Success after binutils/gcc: 9 commits discards 96a8f003df60 202: onsuccess: #17: 2: Success after binutils/gcc: 25 commits discards a828158d4c1a 201: onsuccess: #16: 2: Success after binutils/gcc: 55 commits discards e92e86f2d5fd 200: onsuccess: #15: 2: Success after binutils/gcc: 26 commits discards 250a9ca5e335 199: onsuccess: #14: 2: Success after binutils/gcc: 31 commits discards 59a4ae761b85 198: onsuccess: #13: 2: Success after binutils/gcc: 58 commits discards 9025ad66c3c9 197: onsuccess: #12: 2: Success after binutils/gcc: 29 commits discards 832cb31c964c 196: onsuccess: #11: 2: Success after binutils/gcc: 16 commits discards 09d45fbda251 195: onsuccess: #10: 2: Success after binutils/gcc: 28 commits discards 3bd5334ac419 194: onsuccess: #9: 2: Success after binutils/gcc: 48 commits discards 13881f84c137 193: onsuccess: #8: 2: Success after binutils/gcc: 37 commits discards db20225ff28d 192: onsuccess: #7: 2: Success after binutils/gcc: 22 commits discards 0532e95ba999 191: onsuccess: #6: 2: Success after binutils/gcc: 65 commits discards 5e0641d1de88 190: onsuccess: #5: 2: Success after binutils/gcc: 23 commits discards c82553be1568 189: onsuccess: #4: 2: Success after binutils/gcc: 8 commits discards a0675ec988ae 188: onsuccess: #3: 2: Success after binutils/gcc: 5 commits discards 461317dfb00f 187: onsuccess: #2: 2: Success after binutils/gcc: 22 commits discards 5045f7c216e7 186: onsuccess: #1: 2: Success after binutils/gcc: 54 commits discards 9b77e28e4f79 185: onsuccess: #605: 2: Success after binutils/gcc: 38 commits discards fc2ba93c8958 184: onsuccess: #604: 2: Success after binutils/gcc: 138 commits discards f5f28a98b830 183: onsuccess: #603: 2: Success after binutils/gcc: 33 commits discards 6ad2729254fe 182: onsuccess: #602: 2: Success after binutils/gcc: 32 commits discards 4b110574ad34 181: onsuccess: #601: 2: Success after binutils/gcc: 13 commits discards fbf7e6401a58 180: onsuccess: #600: 2: Success after binutils/gcc: 32 commits discards cc0e51fd4bbf 179: onsuccess: #599: 2: Success after binutils/gcc: 27 commits discards 5effd091d5ab 178: onsuccess: #598: 2: Success after binutils/gcc: 54 commits discards 0386c56fb2a2 177: onsuccess: #597: 2: Success after binutils/gcc: 86 commits discards b0ca890d4dc6 176: onsuccess: #596: 2: Success after binutils/gcc: 84 commits discards e9fe5c8397bb 175: onsuccess: #595: 2: Success after binutils/gcc: 30 commits discards 6ca0842883e0 174: onsuccess: #594: 2: Success after binutils/gcc: 147 commits discards d49410107252 173: onsuccess: #593: 2: Success after binutils/gcc: 74 commits discards f8f9f5ce5fe7 172: onsuccess: #592: 2: Success after binutils/gcc: 57 commits discards 41ceec12fd34 171: onsuccess: #590: 2: Success after binutils/gcc: 21 commits discards 136a2f060938 170: onsuccess: #589: 2: Success after binutils/gcc: 28 commits discards abb189907ace 169: onsuccess: #588: 2: Success after binutils/gcc: 7 commits discards d7d2f46e8e0f 168: onsuccess: #587: 2: Success after binutils/gcc: 2 commits discards f8008fdb39bc 167: onsuccess: #586: 2: Success after binutils/gcc: 16 commits discards 87d1df4ab0d0 166: onsuccess: #585: 2: Success after binutils/gcc: 59 commits discards a04a1cc08b17 165: onsuccess: #584: 2: Success after binutils/gcc: 45 commits discards 7b3e0c7e90e2 164: onsuccess: #583: 2: Success after binutils/gcc: 110 commits discards e319635a1fc3 163: onsuccess: #582: 2: Success after binutils/gcc: 55 commits discards b41eb66bbfd3 162: onsuccess: #581: 2: Success after binutils/gcc: 6 commits discards 2f29e8581991 161: onsuccess: #580: 2: Success after binutils/gcc: 10 commits discards 23837ab4d8de 160: onsuccess: #579: 2: Success after binutils/gcc: 17 commits discards 162c8960a877 159: onsuccess: #578: 2: Success after binutils/gcc: 130 commits discards 4790e57f192e 158: onsuccess: #577: 2: Success after binutils/gcc: 27 commits discards e69dafc69280 157: onsuccess: #576: 2: Success after binutils/gcc: 80 commits discards 46e205d549c9 156: onsuccess: #575: 2: Success after binutils/gcc: 27 commits discards 0b3bf9c2267e 155: onsuccess: #574: 2: Success after binutils/gcc: 36 commits discards f0c76d21e16f 154: onsuccess: #573: 2: Success after binutils/gcc: 6 commits discards 3e33ca45befc 153: onsuccess: #572: 2: Success after binutils/gcc: 28 commits discards f81857267b3f 152: onsuccess: #571: 2: Success after binutils/gcc: 43 commits discards e0a3fe79e6dc 151: onsuccess: #570: 2: Success after binutils/gcc: 36 commits discards 1552c63e6960 150: onsuccess: #569: 2: Success after binutils/gcc: 32 commits discards 77e0447cf6cf 149: onsuccess: #568: 2: Success after binutils/gcc: 69 commits discards a238fb3818e6 148: onsuccess: #567: 2: Success after binutils/gcc: 128 commits discards 567283ef1a0f 147: onsuccess: #566: 2: Success after binutils/gcc: 50 commits discards fdfbf7dc5863 146: onsuccess: #565: 2: Success after binutils/gcc: 115 commits discards 715f25de2a90 145: onsuccess: #564: 2: Success after binutils/gcc: 30 commits discards 60a1ade96923 144: onsuccess: #563: 2: Success after binutils/gcc: 4 commits discards 9b9b305c2fe0 143: onsuccess: #562: 2: Success after binutils/gcc: 6 commits discards 82388367caa7 142: onsuccess: #561: 2: Success after binutils/gcc: 176 commits discards a062f1fe0f05 141: onsuccess: #559: 1: Success after gcc: 4 commits discards 8303180d4d98 140: force: #558: 1: Failure after basepoints/gcc-13-4953- [...] discards f845e8b9df44 139: force: #557: 2: Success after gcc: 6 commits discards abbcb0b3eab2 138: onsuccess: #554: 2: Success after binutils: 10 commits discards ff14d12dc4dc 137: onsuccess: #552: 2: Success after binutils/gcc: 18 commits discards 56ee1d315f1e 136: onsuccess: #551: 2: Success after binutils/gcc: 18 commits discards 7f36ad1392fc 135: onsuccess: #550: 2: Success after binutils/gcc: 31 commits discards 7659b795fe4d 134: onsuccess: #549: 2: Success after binutils/gcc: 9 commits discards 7bcc1d5fbc09 133: onsuccess: #548: 2: Success after binutils/gcc: 29 commits discards 31106048b21c 132: onsuccess: #547: 2: Success after binutils/gcc: 7 commits discards b354c8dcfcd9 131: onsuccess: #546: 2: Success after binutils/gcc: 24 commits discards e7b755140692 130: onsuccess: #545: 2: Success after binutils/gcc: 9 commits discards 6eb00aa687be 129: onsuccess: #544: 2: Success after binutils/gcc: 79 commits discards 77f5013c4950 128: onsuccess: #543: 2: Success after binutils/gcc: 52 commits discards cd4df4c0a307 127: onsuccess: #542: 2: Success after binutils/gcc: 66 commits discards 5177dde4f7e5 126: onsuccess: #541: 2: Success after binutils/gcc: 17 commits discards 82f6ca5aedf5 125: onsuccess: #540: 2: Success after binutils/gcc: 53 commits discards 6c3642491f18 124: onsuccess: #539: 2: Success after binutils/gcc: 9 commits new 83a038d92e92 124: onsuccess: #539: 2: Success after binutils/gcc: 9 commits new 27c644202f22 125: onsuccess: #540: 2: Success after binutils/gcc: 53 commits new 22678e58d2f6 126: onsuccess: #541: 2: Success after binutils/gcc: 17 commits new 765e63a1f1b8 127: onsuccess: #542: 2: Success after binutils/gcc: 66 commits new d900632ce2e0 128: onsuccess: #543: 2: Success after binutils/gcc: 52 commits new 6385020819c1 129: onsuccess: #544: 2: Success after binutils/gcc: 79 commits new fda759e95f97 130: onsuccess: #545: 2: Success after binutils/gcc: 9 commits new 04d485c1f0ad 131: onsuccess: #546: 2: Success after binutils/gcc: 24 commits new 899f62c050e8 132: onsuccess: #547: 2: Success after binutils/gcc: 7 commits new cc4b48e970bc 133: onsuccess: #548: 2: Success after binutils/gcc: 29 commits new 34ae473a7f56 134: onsuccess: #549: 2: Success after binutils/gcc: 9 commits new 6bcc3ac81ce1 135: onsuccess: #550: 2: Success after binutils/gcc: 31 commits new 48e28f10f20e 136: onsuccess: #551: 2: Success after binutils/gcc: 18 commits new 5a766e413d27 137: onsuccess: #552: 2: Success after binutils/gcc: 18 commits new b46bf2e84563 138: onsuccess: #554: 2: Success after binutils: 10 commits new 8c0569114a4d 139: force: #557: 2: Success after gcc: 6 commits new 2bb3569704c6 140: force: #558: 1: Failure after basepoints/gcc-13-4953- [...] new 4946bcdc4116 141: onsuccess: #559: 1: Success after gcc: 4 commits new bc10902008eb 142: onsuccess: #561: 2: Success after binutils/gcc: 176 commits new 214c5bde08c5 143: onsuccess: #562: 2: Success after binutils/gcc: 6 commits new 833ed95f760a 144: onsuccess: #563: 2: Success after binutils/gcc: 4 commits new 953e86c81374 145: onsuccess: #564: 2: Success after binutils/gcc: 30 commits new e08611e61760 146: onsuccess: #565: 2: Success after binutils/gcc: 115 commits new b114647799c3 147: onsuccess: #566: 2: Success after binutils/gcc: 50 commits new 830c30eb7126 148: onsuccess: #567: 2: Success after binutils/gcc: 128 commits new c6d024e607ed 149: onsuccess: #568: 2: Success after binutils/gcc: 69 commits new 0d775437f86b 150: onsuccess: #569: 2: Success after binutils/gcc: 32 commits new 81f1d4ca229c 151: onsuccess: #570: 2: Success after binutils/gcc: 36 commits new a29319a4dd67 152: onsuccess: #571: 2: Success after binutils/gcc: 43 commits new e1231a054bc1 153: onsuccess: #572: 2: Success after binutils/gcc: 28 commits new b3d9b6ed69a5 154: onsuccess: #573: 2: Success after binutils/gcc: 6 commits new 0c933d15cd69 155: onsuccess: #574: 2: Success after binutils/gcc: 36 commits new 6f383ff5253c 156: onsuccess: #575: 2: Success after binutils/gcc: 27 commits new e4356c7c672d 157: onsuccess: #576: 2: Success after binutils/gcc: 80 commits new 7919ea0dbc8a 158: onsuccess: #577: 2: Success after binutils/gcc: 27 commits new c806e3edf316 159: onsuccess: #578: 2: Success after binutils/gcc: 130 commits new 33a6188ff7b1 160: onsuccess: #579: 2: Success after binutils/gcc: 17 commits new 1f6353f08a92 161: onsuccess: #580: 2: Success after binutils/gcc: 10 commits new 44933b237b58 162: onsuccess: #581: 2: Success after binutils/gcc: 6 commits new 5f4033fd796a 163: onsuccess: #582: 2: Success after binutils/gcc: 55 commits new 1593c4747e0f 164: onsuccess: #583: 2: Success after binutils/gcc: 110 commits new 6c5e087a57c2 165: onsuccess: #584: 2: Success after binutils/gcc: 45 commits new 2a28cb208776 166: onsuccess: #585: 2: Success after binutils/gcc: 59 commits new facb314d0b61 167: onsuccess: #586: 2: Success after binutils/gcc: 16 commits new ff7e64caef49 168: onsuccess: #587: 2: Success after binutils/gcc: 2 commits new abd4dd8de15f 169: onsuccess: #588: 2: Success after binutils/gcc: 7 commits new de51128c19e6 170: onsuccess: #589: 2: Success after binutils/gcc: 28 commits new dd3f2beed0fb 171: onsuccess: #590: 2: Success after binutils/gcc: 21 commits new 4bf70c046ba0 172: onsuccess: #592: 2: Success after binutils/gcc: 57 commits new 4b72413b4968 173: onsuccess: #593: 2: Success after binutils/gcc: 74 commits new a36163c69f78 174: onsuccess: #594: 2: Success after binutils/gcc: 147 commits new eaed3f2df486 175: onsuccess: #595: 2: Success after binutils/gcc: 30 commits new 677ebb1d2e54 176: onsuccess: #596: 2: Success after binutils/gcc: 84 commits new 75182616ca7f 177: onsuccess: #597: 2: Success after binutils/gcc: 86 commits new c508965707d9 178: onsuccess: #598: 2: Success after binutils/gcc: 54 commits new b799387b8ab5 179: onsuccess: #599: 2: Success after binutils/gcc: 27 commits new 552e7da281e3 180: onsuccess: #600: 2: Success after binutils/gcc: 32 commits new 46651855d8f3 181: onsuccess: #601: 2: Success after binutils/gcc: 13 commits new 3f0c4cf5ef9b 182: onsuccess: #602: 2: Success after binutils/gcc: 32 commits new 39e7051907e4 183: onsuccess: #603: 2: Success after binutils/gcc: 33 commits new 31b8ef0ae4f2 184: onsuccess: #604: 2: Success after binutils/gcc: 138 commits new 0fd0dbe722a6 185: onsuccess: #605: 2: Success after binutils/gcc: 38 commits new f23278fc4d43 186: onsuccess: #1: 2: Success after binutils/gcc: 54 commits new 2eb73d12b4f6 187: onsuccess: #2: 2: Success after binutils/gcc: 22 commits new 1369fb541e6f 188: onsuccess: #3: 2: Success after binutils/gcc: 5 commits new 4cd46486250b 189: onsuccess: #4: 2: Success after binutils/gcc: 8 commits new 9a99ef14992b 190: onsuccess: #5: 2: Success after binutils/gcc: 23 commits new d384e87869b9 191: onsuccess: #6: 2: Success after binutils/gcc: 65 commits new 9ae2771e6940 192: onsuccess: #7: 2: Success after binutils/gcc: 22 commits new 8a6ea89cf12d 193: onsuccess: #8: 2: Success after binutils/gcc: 37 commits new 1423c1e06ad7 194: onsuccess: #9: 2: Success after binutils/gcc: 48 commits new e7ccf0c4727a 195: onsuccess: #10: 2: Success after binutils/gcc: 28 commits new 77e7cc910517 196: onsuccess: #11: 2: Success after binutils/gcc: 16 commits new 2058ff5e8f5a 197: onsuccess: #12: 2: Success after binutils/gcc: 29 commits new 15fe565ca332 198: onsuccess: #13: 2: Success after binutils/gcc: 58 commits new 00301db84744 199: onsuccess: #14: 2: Success after binutils/gcc: 31 commits new f4684288b0a5 200: onsuccess: #15: 2: Success after binutils/gcc: 26 commits new 4e7143639442 201: onsuccess: #16: 2: Success after binutils/gcc: 55 commits new 6a4fdc775273 202: onsuccess: #17: 2: Success after binutils/gcc: 25 commits new 696ebca50058 203: onsuccess: #18: 2: Success after binutils/gcc: 9 commits new 40c99cc6d1ec 204: onsuccess: #19: 2: Success after binutils/gcc: 39 commits new 205d1f481026 205: onsuccess: #20: 2: Success after binutils/gcc: 59 commits new 04c4ea998d7e 206: onsuccess: #21: 2: Success after binutils/gcc: 38 commits new ac64a17df009 207: onsuccess: #23: 2: Success after binutils/gcc: 75 commits new 28b1b673ebd3 208: onsuccess: #24: 2: Success after binutils/gcc: 44 commits new 3d9133ebcd91 209: onsuccess: #25: 2: Success after binutils/gcc: 12 commits new 239bfa4b85f2 210: onsuccess: #26: 2: Success after binutils/gcc: 27 commits new 77b932d426c0 211: onsuccess: #27: 2: Success after binutils/gcc: 41 commits new fad318a2fa49 212: onsuccess: #28: 2: Success after binutils/gcc: 34 commits new 615a8606415b 213: onsuccess: #29: 2: Success after binutils/gcc: 36 commits new f42d1fe2ee3d 214: onsuccess: #30: 2: Success after binutils/gcc: 34 commits new fd488e51654e 215: onsuccess: #31: 2: Success after binutils/gcc: 7 commits new 9526ef9c103a 216: onsuccess: #32: 2: Success after binutils/gcc: 5 commits new d713e192cd91 217: onsuccess: #35: 2: [TCWG CI] Success after binutils: [...] new 593f5b1bd530 218: force: #37: 2: [TCWG CI] Success after gcc: 40 commits new f47bbcd20fd0 219: force: #38: 1: [TCWG CI] Failure after basepoints/gcc [...] new 36a783fab2a7 220: onsuccess: #39: 1: [TCWG CI] Success after gcc: 2 commits new c30361f9f913 221: onsuccess: #40: 2: [TCWG CI] Success after binutils/g [...] new a94c4e94e9bc 222: onsuccess: #41: 2: [TCWG CI] Success after binutils/g [...] new de40ee2377ed 223: onsuccess: #42: 2: [TCWG CI] Success after binutils/g [...] new 978814814be6 224: onsuccess: #43: 2: [TCWG CI] Success after binutils/g [...] new 2cccd34dfe6d 225: onsuccess: #44: 2: [TCWG CI] Success after binutils/g [...] This update added new revisions after undoing existing revisions. That is to say, some revisions that were in the old version of the branch are not in the new version. This situation occurs when a user --force pushes a change and generates a repository containing something like this: * -- * -- B -- O -- O -- O (81d3571e2469) \ 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 1912 -> 1920 bytes 02-prepare_abe/console.log.xz | Bin 2532 -> 2500 bytes 04-build_abe-binutils/console.log.xz | Bin 34948 -> 35104 bytes 05-build_abe-bootstrap_profiled_lto/console.log.xz | Bin 305808 -> 306424 bytes 06-check_regression/console.log.xz | Bin 2552 -> 3052 bytes 07-update_baseline/console.log | 68 ++++++++++----------- dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- mail/changes-list-long.txt | 16 +++-- mail/changes-list-short.txt | 2 +- mail/last_good.sh | 18 +++--- manifest.sh | 20 +++--- 13 files changed, 69 insertions(+), 61 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

1 year, 7 months

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_gnu_native_check_gcc/master-arm updated (281d6c0a9c85 -> 5b4a66efcee0)

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 281d6c0a9c85 238: onsuccess: #39: 1: [TCWG CI] Success after binutils/g [...] discards a60fdfe8ab86 237: onsuccess: #38: 1: [TCWG CI] Success after binutils/g [...] discards c4278b350d5e 236: onsuccess: #37: 1: [TCWG CI] Success after binutils/g [...] discards 76073f841bf7 235: onsuccess: #36: 1: [TCWG CI] Success after binutils/g [...] discards ee0b29ff6880 234: onsuccess: #35: 1: [TCWG CI] Success after binutils/g [...] discards e61ece673f6c 233: onsuccess: #34: 1: [TCWG CI] Success after binutils/g [...] discards b66448123ff2 232: onsuccess: #32: 1: Success after binutils/gcc/linux/g [...] discards b9abf7056a0f 231: onsuccess: #31: 1: Success after binutils/gcc/linux/g [...] discards 2b358235a806 230: onsuccess: #30: 1: Success after binutils/gcc/linux/g [...] discards 6a839b920739 229: onsuccess: #29: 1: Success after binutils/gcc/linux/g [...] discards e9f4e013484d 228: onsuccess: #28: 1: Success after binutils/gcc/linux/g [...] discards 6597fd4511a4 227: onsuccess: #27: 1: Success after binutils/gcc/linux/g [...] discards 01b2415b5d97 226: onsuccess: #26: 1: Success after binutils/gcc/linux/g [...] discards 240acc2b1c97 225: onsuccess: #25: 1: Success after binutils/gcc/linux/g [...] discards 4eaf10480a71 224: onsuccess: #21: 1: Success after binutils/gcc/linux/g [...] discards bd5a6109bfc6 223: onsuccess: #20: 1: Success after binutils/gcc/linux/g [...] discards 5c2060eb5ee1 222: onsuccess: #19: 1: Success after binutils/gcc/linux/g [...] discards a4b2825c0488 221: onsuccess: #18: 1: Success after binutils/gcc/linux/g [...] discards aa851302e064 220: onsuccess: #17: 1: Success after binutils/gcc/linux/g [...] discards e6851219b679 219: onsuccess: #16: 1: Success after binutils/gcc/linux/g [...] discards 178e50e36c34 218: onsuccess: #15: 1: Success after binutils/gcc/linux/g [...] discards cbf1c9266384 217: onsuccess: #14: 1: Success after binutils/gcc/linux/g [...] discards d739db6c525a 216: onsuccess: #12: 1: Success after binutils/gcc/linux/g [...] discards 633df806de9b 215: onsuccess: #11: 1: Success after binutils/gcc/linux/g [...] discards 725af4b86d1c 214: onsuccess: #10: 1: Success after binutils/gcc/linux/g [...] discards 0c73568e9277 213: onsuccess: #9: 1: Success after binutils/gcc/linux/gl [...] discards 9d3e4a843bb8 212: onsuccess: #8: 1: Success after binutils/gcc/linux/gl [...] discards 89079dc58f12 211: onsuccess: #7: 1: Success after binutils/gcc/linux/gd [...] discards 8ee9f8aaadfb 210: onsuccess: #6: 1: Success after binutils/gcc/linux/gl [...] discards bda81fe22efd 209: onsuccess: #5: 1: Success after binutils/gcc/linux/gl [...] discards c5637b939a51 208: onsuccess: #4: 1: Success after binutils/gcc/linux/gl [...] discards 84aa384858bc 207: onsuccess: #3: 1: Success after binutils/gcc/linux/gd [...] discards dff5c15a1105 206: onsuccess: #2: 1: Success after binutils/gcc/linux/gl [...] discards 54b3bd309b93 205: onsuccess: #1: 1: Success after binutils/gcc/linux/gl [...] discards b91f751eb513 204: onsuccess: #672: 1: Success after binutils/gcc/linux/ [...] discards 567df369b947 203: onsuccess: #671: 1: Success after binutils/gcc/linux/ [...] discards 8946bfd6ccdc 202: onsuccess: #670: 1: Success after binutils/gcc/linux/ [...] discards a570b2cb174d 201: onsuccess: #664: 1: Success after binutils/gcc/glibc/ [...] discards 0ca533e0a253 200: onsuccess: #663: 1: Success after binutils/gcc/linux/ [...] discards 8bda6a56d43f 199: onsuccess: #662: 1: Success after binutils/gcc/linux/ [...] discards 9223b173843e 198: onsuccess: #661: 1: Success after binutils/gcc/linux/ [...] discards a01ebb7525fe 197: onsuccess: #660: 1: Success after binutils/gcc/linux/ [...] discards e7c7162c8de7 196: onsuccess: #659: 1: Success after binutils/gcc/linux/ [...] discards c0054ada3518 195: onsuccess: #657: 1: Success after binutils/gcc/linux/ [...] discards 09611b82180d 194: onsuccess: #656: 1: Success after binutils/gcc/linux/ [...] discards 4401205c1a66 193: onsuccess: #655: 1: Success after binutils/gcc/linux/ [...] discards 6792ff58174f 192: onsuccess: #654: 1: Success after binutils/gcc/linux/ [...] discards c4c0fe779795 191: onsuccess: #653: 1: Success after binutils/gcc/linux/ [...] discards d300643a8f44 190: onsuccess: #652: 1: Success after binutils/gcc/linux/ [...] discards dd80fc8d4b93 189: onsuccess: #651: 1: Success after binutils/gcc/linux/ [...] discards ca40917bdac8 188: onsuccess: #650: 1: Success after binutils/gcc/linux/ [...] discards 33ea5c845268 187: onsuccess: #649: 1: Success after binutils/gcc/linux/ [...] discards 8e88a5418ebd 186: onsuccess: #648: 1: Success after binutils/gcc/linux/ [...] discards b2709aaf3137 185: onsuccess: #647: 1: Success after binutils/gcc/linux/ [...] discards fa1d766ca4f5 184: onsuccess: #646: 1: Success after binutils/gcc/linux/ [...] discards 8631bd224ce2 183: onsuccess: #645: 1: Success after binutils/gcc/gdb: 2 [...] discards 9b02643723e6 182: onsuccess: #644: 1: Success after binutils/gcc/gdb: 3 [...] discards 2ddcb699587b 181: onsuccess: #643: 1: Success after binutils/gcc/linux/ [...] discards 867889f49372 180: onsuccess: #642: 1: Success after binutils/gcc/linux/ [...] discards fe9d7c4da085 179: onsuccess: #641: 1: Success after binutils/gcc/linux/ [...] discards 4e283910b1c6 178: onsuccess: #640: 1: Success after binutils/gcc/linux/ [...] discards e0f6ddee2896 177: onsuccess: #639: 1: Success after binutils/gcc/linux/ [...] discards e0744a06b66c 176: onsuccess: #638: 1: Success after binutils/gcc/linux/ [...] discards 5c6e99791eef 175: onsuccess: #637: 1: Success after binutils/gcc/linux/ [...] discards f4aa9b2e12de 174: onsuccess: #636: 1: Success after binutils/gcc/linux/ [...] discards 07339a924c1a 173: onsuccess: #635: 1: Success after binutils/gcc/linux/ [...] discards b0e64ffe7977 172: onsuccess: #634: 1: Success after binutils/gcc/linux/ [...] discards af15f884eb20 171: onsuccess: #633: 1: Success after binutils/gcc/linux/ [...] discards aae5f05419aa 170: onsuccess: #632: 1: Success after binutils/gcc/linux/ [...] discards 105cec394dab 169: onsuccess: #631: 1: Success after binutils/gcc/linux/ [...] discards 3e58b1e46c20 168: onsuccess: #630: 1: Success after binutils/gcc/linux/ [...] discards 73ccab0486de 167: onsuccess: #629: 1: Success after binutils/gcc/linux/ [...] discards b470cef25505 166: onsuccess: #628: 1: Success after binutils/gcc/linux/ [...] discards f1c865ce1690 165: onsuccess: #627: 1: Success after binutils/gcc/linux/ [...] discards 534092f48a3c 164: onsuccess: #626: 1: Success after binutils/gcc/linux/ [...] discards 56eac4205dca 163: onsuccess: #625: 1: Success after binutils/gcc/glibc/ [...] discards 71c49f1ae21f 162: onsuccess: #624: 1: Success after linux: 10 commits discards 92edcd31a831 161: onsuccess: #623: 1: Success after glibc: 9 commits discards 06b7d82180e1 160: onsuccess: #621: 1: Success after gcc: 11 commits discards c5d10ae6cf5c 159: onsuccess: #620: 1: Success after binutils: 12 commits discards 36fe5154b0d1 158: onsuccess: #618: 1: Success after binutils/gcc/linux/ [...] discards 41de6a6dc0d6 157: onsuccess: #617: 1: Success after binutils/gcc/linux/ [...] discards f3df8debfd93 156: onsuccess: #616: 1: Success after binutils/gcc/linux/ [...] discards 4e6a9cac486d 155: onsuccess: #615: 1: Success after binutils/gcc/linux/ [...] discards 743ff2cdfceb 154: onsuccess: #614: 1: Success after binutils/gcc/gdb: 1 [...] discards 39a674153021 153: onsuccess: #613: 1: Success after binutils/gcc/gdb: 4 [...] discards f5fb9fceeef2 152: onsuccess: #612: 1: Success after binutils/gcc/gdb: 1 [...] discards 24c6edc799fd 151: onsuccess: #611: 1: Success after binutils/gcc/linux/ [...] discards e36f1d2476bf 150: onsuccess: #610: 1: Success after binutils/gcc/linux/ [...] discards b0852e6caecb 149: onsuccess: #609: 1: Success after binutils/gcc/linux/ [...] discards 8d7d6da2d764 148: onsuccess: #608: 1: Success after binutils/gcc/linux/ [...] discards a5016540e81f 147: onsuccess: #607: 1: Success after binutils/gcc/linux/ [...] discards a4116ad4803e 146: onsuccess: #606: 1: Success after binutils/gcc/linux/ [...] discards eec9eed36daa 145: onsuccess: #605: 1: Success after binutils/gcc/linux/ [...] discards afda512ca918 144: onsuccess: #604: 1: Success after binutils/gcc/gdb: 1 [...] discards 086347b78658 143: onsuccess: #603: 1: Success after binutils/gcc/linux/ [...] discards 229c73b78294 142: onsuccess: #602: 1: Success after binutils/gcc/linux/ [...] discards b6b278e893c0 141: onsuccess: #601: 1: Success after linux: 794 commits discards 90f8d6264b24 140: onsuccess: #600: 1: Success after gcc: 23 commits discards 51928e8837a0 139: onsuccess: #599: 1: Success after binutils: 10 commits discards 5abcc17ff3a8 138: onsuccess: #597: 1: Success after binutils/gcc/linux/ [...] new 8b04342b704e 138: onsuccess: #597: 1: Success after binutils/gcc/linux/ [...] new 4a946a123f72 139: onsuccess: #599: 1: Success after binutils: 10 commits new 719a8603d96a 140: onsuccess: #600: 1: Success after gcc: 23 commits new 68758b4f8d41 141: onsuccess: #601: 1: Success after linux: 794 commits new 0ff4df883e26 142: onsuccess: #602: 1: Success after binutils/gcc/linux/ [...] new 8940503b092b 143: onsuccess: #603: 1: Success after binutils/gcc/linux/ [...] new cfc77fefbd37 144: onsuccess: #604: 1: Success after binutils/gcc/gdb: 1 [...] new 7d51140f69f4 145: onsuccess: #605: 1: Success after binutils/gcc/linux/ [...] new 0356e7163675 146: onsuccess: #606: 1: Success after binutils/gcc/linux/ [...] new 68412e38bf25 147: onsuccess: #607: 1: Success after binutils/gcc/linux/ [...] new 6f1d176f6a3f 148: onsuccess: #608: 1: Success after binutils/gcc/linux/ [...] new 6730aa6911a9 149: onsuccess: #609: 1: Success after binutils/gcc/linux/ [...] new 611b60aa52c0 150: onsuccess: #610: 1: Success after binutils/gcc/linux/ [...] new 16721e25cd7c 151: onsuccess: #611: 1: Success after binutils/gcc/linux/ [...] new 91da68dd657b 152: onsuccess: #612: 1: Success after binutils/gcc/gdb: 1 [...] new 8f3b4e263453 153: onsuccess: #613: 1: Success after binutils/gcc/gdb: 4 [...] new ee2066320e0f 154: onsuccess: #614: 1: Success after binutils/gcc/gdb: 1 [...] new 2d583180108e 155: onsuccess: #615: 1: Success after binutils/gcc/linux/ [...] new 63221123f50c 156: onsuccess: #616: 1: Success after binutils/gcc/linux/ [...] new 2e44bfa41fef 157: onsuccess: #617: 1: Success after binutils/gcc/linux/ [...] new be3a6b96de9a 158: onsuccess: #618: 1: Success after binutils/gcc/linux/ [...] new 0d9cd388780c 159: onsuccess: #620: 1: Success after binutils: 12 commits new fc5b1ecf4653 160: onsuccess: #621: 1: Success after gcc: 11 commits new bcb82fa95617 161: onsuccess: #623: 1: Success after glibc: 9 commits new c7b77f6a0359 162: onsuccess: #624: 1: Success after linux: 10 commits new 4207d2c84b3d 163: onsuccess: #625: 1: Success after binutils/gcc/glibc/ [...] new e14878867543 164: onsuccess: #626: 1: Success after binutils/gcc/linux/ [...] new b1c311640860 165: onsuccess: #627: 1: Success after binutils/gcc/linux/ [...] new 8a776f496880 166: onsuccess: #628: 1: Success after binutils/gcc/linux/ [...] new e04ad265045c 167: onsuccess: #629: 1: Success after binutils/gcc/linux/ [...] new e35ba065af79 168: onsuccess: #630: 1: Success after binutils/gcc/linux/ [...] new 49641f1ff2f1 169: onsuccess: #631: 1: Success after binutils/gcc/linux/ [...] new 4b5ec7cf5109 170: onsuccess: #632: 1: Success after binutils/gcc/linux/ [...] new bdde4fad3de7 171: onsuccess: #633: 1: Success after binutils/gcc/linux/ [...] new f8a0e4e2ac60 172: onsuccess: #634: 1: Success after binutils/gcc/linux/ [...] new e9b67ee839a7 173: onsuccess: #635: 1: Success after binutils/gcc/linux/ [...] new f8fd2f8d3163 174: onsuccess: #636: 1: Success after binutils/gcc/linux/ [...] new 6cd25332aa48 175: onsuccess: #637: 1: Success after binutils/gcc/linux/ [...] new 5956ae31d6a5 176: onsuccess: #638: 1: Success after binutils/gcc/linux/ [...] new 2a343c8a0ab1 177: onsuccess: #639: 1: Success after binutils/gcc/linux/ [...] new 8285f2126d18 178: onsuccess: #640: 1: Success after binutils/gcc/linux/ [...] new 7572e4a0765e 179: onsuccess: #641: 1: Success after binutils/gcc/linux/ [...] new f00434110329 180: onsuccess: #642: 1: Success after binutils/gcc/linux/ [...] new bf4d1f948ee0 181: onsuccess: #643: 1: Success after binutils/gcc/linux/ [...] new 21b9383db257 182: onsuccess: #644: 1: Success after binutils/gcc/gdb: 3 [...] new 8297890c99d6 183: onsuccess: #645: 1: Success after binutils/gcc/gdb: 2 [...] new f766580b37f5 184: onsuccess: #646: 1: Success after binutils/gcc/linux/ [...] new 46b4004d581c 185: onsuccess: #647: 1: Success after binutils/gcc/linux/ [...] new daf4227b9eef 186: onsuccess: #648: 1: Success after binutils/gcc/linux/ [...] new 29b888266b81 187: onsuccess: #649: 1: Success after binutils/gcc/linux/ [...] new bd0b49fe2949 188: onsuccess: #650: 1: Success after binutils/gcc/linux/ [...] new 40718368413c 189: onsuccess: #651: 1: Success after binutils/gcc/linux/ [...] new fcfcea3b8cbc 190: onsuccess: #652: 1: Success after binutils/gcc/linux/ [...] new b05531a42682 191: onsuccess: #653: 1: Success after binutils/gcc/linux/ [...] new 90ec0b55ff05 192: onsuccess: #654: 1: Success after binutils/gcc/linux/ [...] new 1ca5af1209ba 193: onsuccess: #655: 1: Success after binutils/gcc/linux/ [...] new e801787ce7a3 194: onsuccess: #656: 1: Success after binutils/gcc/linux/ [...] new 581289d028a0 195: onsuccess: #657: 1: Success after binutils/gcc/linux/ [...] new 38fabe42dbf7 196: onsuccess: #659: 1: Success after binutils/gcc/linux/ [...] new c573edc12c54 197: onsuccess: #660: 1: Success after binutils/gcc/linux/ [...] new c1bf61bcd298 198: onsuccess: #661: 1: Success after binutils/gcc/linux/ [...] new 5868ca35e52f 199: onsuccess: #662: 1: Success after binutils/gcc/linux/ [...] new f62bb7c9bf2e 200: onsuccess: #663: 1: Success after binutils/gcc/linux/ [...] new 4ca6c7ed9c8d 201: onsuccess: #664: 1: Success after binutils/gcc/glibc/ [...] new 3bbb8afe142c 202: onsuccess: #670: 1: Success after binutils/gcc/linux/ [...] new 08f5d115e6d5 203: onsuccess: #671: 1: Success after binutils/gcc/linux/ [...] new 09cf2b5733a9 204: onsuccess: #672: 1: Success after binutils/gcc/linux/ [...] new 17fe587fe461 205: onsuccess: #1: 1: Success after binutils/gcc/linux/gl [...] new dab36602bbe4 206: onsuccess: #2: 1: Success after binutils/gcc/linux/gl [...] new 9ab46434488e 207: onsuccess: #3: 1: Success after binutils/gcc/linux/gd [...] new 9f82d25a70f7 208: onsuccess: #4: 1: Success after binutils/gcc/linux/gl [...] new 25a598caa100 209: onsuccess: #5: 1: Success after binutils/gcc/linux/gl [...] new a3975145c545 210: onsuccess: #6: 1: Success after binutils/gcc/linux/gl [...] new e0c4eff0d3dd 211: onsuccess: #7: 1: Success after binutils/gcc/linux/gd [...] new 8a5d670d160d 212: onsuccess: #8: 1: Success after binutils/gcc/linux/gl [...] new 7c1fe90b6093 213: onsuccess: #9: 1: Success after binutils/gcc/linux/gl [...] new 130e4dd8706f 214: onsuccess: #10: 1: Success after binutils/gcc/linux/g [...] new b3b6f010ddc7 215: onsuccess: #11: 1: Success after binutils/gcc/linux/g [...] new f51afc4ddc18 216: onsuccess: #12: 1: Success after binutils/gcc/linux/g [...] new bfccee4ea6da 217: onsuccess: #14: 1: Success after binutils/gcc/linux/g [...] new be7b88284d9e 218: onsuccess: #15: 1: Success after binutils/gcc/linux/g [...] new ebc012a86ebf 219: onsuccess: #16: 1: Success after binutils/gcc/linux/g [...] new 84ba766e0e35 220: onsuccess: #17: 1: Success after binutils/gcc/linux/g [...] new 05ce68ace0e8 221: onsuccess: #18: 1: Success after binutils/gcc/linux/g [...] new 49e0752f5d72 222: onsuccess: #19: 1: Success after binutils/gcc/linux/g [...] new 585caa1eaf40 223: onsuccess: #20: 1: Success after binutils/gcc/linux/g [...] new aeb674169737 224: onsuccess: #21: 1: Success after binutils/gcc/linux/g [...] new 75913f06a3e8 225: onsuccess: #25: 1: Success after binutils/gcc/linux/g [...] new 576a9d3c9772 226: onsuccess: #26: 1: Success after binutils/gcc/linux/g [...] new 2d9b951987bb 227: onsuccess: #27: 1: Success after binutils/gcc/linux/g [...] new 7f94124a78ba 228: onsuccess: #28: 1: Success after binutils/gcc/linux/g [...] new 0479050ca31f 229: onsuccess: #29: 1: Success after binutils/gcc/linux/g [...] new 9bd5a4c32a23 230: onsuccess: #30: 1: Success after binutils/gcc/linux/g [...] new 6838a7bf5956 231: onsuccess: #31: 1: Success after binutils/gcc/linux/g [...] new 99d5595682e6 232: onsuccess: #32: 1: Success after binutils/gcc/linux/g [...] new 7c1a088166ea 233: onsuccess: #34: 1: [TCWG CI] Success after binutils/g [...] new 56ca3e733b52 234: onsuccess: #35: 1: [TCWG CI] Success after binutils/g [...] new 6bb68e2cc6a9 235: onsuccess: #36: 1: [TCWG CI] Success after binutils/g [...] new 079eb44ca9c0 236: onsuccess: #37: 1: [TCWG CI] Success after binutils/g [...] new a37cca09ccc3 237: onsuccess: #38: 1: [TCWG CI] Success after binutils/g [...] new 124a73dc5090 238: onsuccess: #39: 1: [TCWG CI] Success after binutils/g [...] new 5b4a66efcee0 239: onsuccess: #40: 1: [TCWG CI] Success after binutils/g [...] This update added new revisions after undoing existing revisions. That is to say, some revisions that were in the old version of the branch are not in the new version. This situation occurs when a user --force pushes a change and generates a repository containing something like this: * -- * -- B -- O -- O -- O (281d6c0a9c85) \ 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 2036 -> 2052 bytes 02-prepare_abe/console.log.xz | Bin 2504 -> 2512 bytes 03-build_abe-binutils/console.log.xz | Bin 49236 -> 49100 bytes 04-build_abe-gcc/console.log.xz | Bin 236748 -> 237568 bytes 05-clean_sysroot/console.log.xz | Bin 316 -> 316 bytes 06-build_abe-linux/console.log.xz | Bin 8636 -> 8760 bytes 07-build_abe-glibc/console.log.xz | Bin 232396 -> 233416 bytes 08-build_abe-gdb/console.log.xz | Bin 46364 -> 46540 bytes 09-build_abe-dejagnu/console.log.xz | Bin 3820 -> 3772 bytes 10-build_abe-check_gcc/console.log.xz | Bin 9992 -> 10664 bytes 11-check_regression/console.log.xz | Bin 4944 -> 5744 bytes 11-check_regression/fails.sum | 2 +- 11-check_regression/results.compare | 32 +- 11-check_regression/results.compare2 | 24 +- 11-check_regression/results.regressions | 32 +- 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/changes-list-long.txt | 43 +- mail/changes-list-short.txt | 2 +- mail/last_good.sh | 32 +- manifest.sh | 38 +- results | 32 +- sumfiles/g++.log.sep.xz | Bin 79940 -> 71100 bytes sumfiles/g++.log.xz | Bin 2914596 -> 2915836 bytes sumfiles/g++.sum | 2 +- sumfiles/g++.sum.sep | 11386 +++++++++++------------------- sumfiles/gcc.log.sep.xz | Bin 81324 -> 75968 bytes sumfiles/gcc.log.xz | Bin 2472976 -> 2471712 bytes sumfiles/gcc.sum | 5 +- sumfiles/gcc.sum.sep | 2991 ++++++-- sumfiles/gfortran.log.sep.xz | Bin 32308 -> 37696 bytes sumfiles/gfortran.log.xz | Bin 952916 -> 971148 bytes sumfiles/gfortran.sum | 2 +- sumfiles/gfortran.sum.sep | 2480 +------ sumfiles/libatomic.log.xz | Bin 2280 -> 2284 bytes sumfiles/libatomic.sum | 2 +- sumfiles/libgomp.log.xz | Bin 230684 -> 230592 bytes sumfiles/libgomp.sum | 8 +- sumfiles/libitm.log.xz | Bin 2688 -> 2688 bytes sumfiles/libitm.sum | 2 +- sumfiles/libstdc++.log.sep.xz | Bin 11080 -> 14904 bytes sumfiles/libstdc++.log.xz | Bin 470772 -> 480724 bytes sumfiles/libstdc++.sum.sep | 577 +- 48 files changed, 7228 insertions(+), 10544 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

1 year, 7 months

[glibc] branch master updated (5d1ccdda7b -> 743113d42e)

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 glibc. from 5d1ccdda7b x86_64: Fix asm constraints in feraiseexcept (bug 30305) new 743113d42e x86: Set FSGSBASE to active if enabled by kernel 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: .../64/tst-map-32bit-mod.c => x86/dl-hwcap2.h} | 22 ++++++++-------------- sysdeps/x86/cpu-features.c | 3 +++ elf/tst-audit18mod.c => sysdeps/x86/dl-hwcap2.h | 10 ++++------ sysdeps/x86/tst-cpu-features-cpuinfo.c | 7 +++++++ 4 files changed, 22 insertions(+), 20 deletions(-) copy sysdeps/unix/sysv/linux/{x86_64/64/tst-map-32bit-mod.c => x86/dl-hwcap2.h} (68%) copy elf/tst-audit18mod.c => sysdeps/x86/dl-hwcap2.h (80%) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

1 year, 7 months

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_gnu_native_fast_check_gdb/master-arm updated (090d160c29f1 -> f9f8334e9bee)

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 090d160c29f1 137: onsuccess: #44: 1: [TCWG CI] Success after binutils/g [...] discards 50045b96b953 136: onsuccess: #43: 1: [TCWG CI] Success after binutils/g [...] discards 20532bff82ac 135: onsuccess: #42: 1: [TCWG CI] Success after binutils/g [...] discards da1f19a705c9 134: onsuccess: #41: 1: [TCWG CI] Success after binutils/g [...] discards 4e01f3501ccf 133: onsuccess: #40: 1: [TCWG CI] Success after binutils/g [...] discards e02963839ba6 132: onsuccess: #39: 1: [TCWG CI] Success after binutils/g [...] discards 3dfe7c09e159 131: onsuccess: #37: 1: Success after binutils/gcc/linux/g [...] discards 2bbc347bde38 130: onsuccess: #36: 1: Success after binutils/gcc/linux/g [...] discards 51f9be6d9ccf 129: onsuccess: #35: 1: Success after binutils/gcc/linux/g [...] discards bfde7589bb2f 128: onsuccess: #34: 1: Success after binutils/gcc/linux/g [...] discards 9a2dbe92a38f 127: onsuccess: #33: 1: Success after binutils/gcc/linux/g [...] discards 6d51debbb828 126: onsuccess: #32: 1: Success after binutils/gcc/linux/g [...] discards 5cf37d676d16 125: onsuccess: #31: 1: Success after binutils/gcc/linux/g [...] discards 057724b1e35e 124: onsuccess: #30: 1: Success after binutils/gcc/linux/g [...] discards 631c0cf04723 123: onsuccess: #29: 1: Success after binutils/gcc/linux/g [...] discards e9d593c65fdd 122: onsuccess: #28: 1: Success after binutils/gcc/linux/g [...] discards edcb893f5de7 121: force: #26: : Failure after baseline build: no new commits discards 62c4a627f354 120: onsuccess: #19: 1: Success after binutils/gcc/linux/g [...] discards 9bc991d0a65d 119: onsuccess: #18: 1: Success after binutils/gcc/linux/g [...] discards 18579ddf274f 118: onsuccess: #17: 1: Success after binutils/gcc/linux/g [...] discards cc39fde7028c 117: onsuccess: #16: 1: Success after binutils/gcc/linux/g [...] discards 621dc9b12a5f 116: onsuccess: #15: 1: Success after binutils/gcc/linux/g [...] discards f82fe94c0f2d 115: onsuccess: #14: 1: Success after binutils/gcc/linux/g [...] discards 97153be525c9 114: onsuccess: #13: 1: Success after binutils/gcc/linux/g [...] discards b16cdda49d1c 113: onsuccess: #11: 1: Success after binutils/gcc/linux/g [...] discards 9ce1942e4b69 112: onsuccess: #10: 1: Success after binutils/gcc/linux/g [...] discards 6fbfc7c7fa1b 111: onsuccess: #9: 1: Success after binutils/gcc/linux/gd [...] discards fb4a197ea1ab 110: onsuccess: #8: 1: Success after binutils/gcc/linux/gl [...] discards 13e0c268ebf2 109: onsuccess: #7: 1: Success after binutils/gcc/linux/gl [...] discards cd7af6475ae0 108: onsuccess: #6: 1: Success after binutils/gcc/linux/gd [...] discards 373b41504adb 107: onsuccess: #5: 1: Success after binutils/gcc/linux/gl [...] discards 9104da9d2837 106: onsuccess: #4: 1: Success after binutils/gcc/linux/gl [...] discards 071b4d46acea 105: onsuccess: #3: 1: Success after binutils/gcc/linux/gl [...] discards 33b8e1d234b8 104: onsuccess: #2: 1: Success after binutils/gcc/linux/gl [...] discards a160d566b3cb 103: onsuccess: #1: 1: Success after binutils/gcc/linux/gl [...] discards b395f059bfbd 102: onsuccess: #123: 1: Success after binutils/gcc/linux/ [...] discards 3cdfd0995bda 101: onsuccess: #122: 1: Success after binutils/gcc/linux/ [...] discards 2f3d5f6bc8e5 100: onsuccess: #121: 1: Success after binutils/gcc/glibc/ [...] discards 15a04fe24f07 99: onsuccess: #120: 1: Success after binutils/gcc/linux/g [...] discards 58eeb703b460 98: onsuccess: #108: 1: Success after binutils/gcc/linux/g [...] discards 73de783ab917 97: onsuccess: #107: 1: Success after binutils/gcc/linux/g [...] discards 3cd0643aa9f2 96: onsuccess: #106: 1: Success after binutils/gcc/linux/g [...] discards a230646d4f3f 95: onsuccess: #105: 1: Success after binutils/gcc/linux/g [...] discards ea3b5c516829 94: onsuccess: #104: 1: Success after binutils/gcc/linux/g [...] discards 16aefb88a254 93: onsuccess: #103: 1: Success after binutils/gcc/linux/g [...] discards 80bde34e7f09 92: onsuccess: #101: 1: Success after binutils/gcc/linux/g [...] discards 4b0611191504 91: onsuccess: #100: 1: Success after binutils/gcc/linux/g [...] discards 72001c02689e 90: onsuccess: #99: 1: Success after binutils/gcc/linux/gd [...] discards ebc78ff55f07 89: onsuccess: #98: 1: Success after binutils/gcc/linux/gl [...] discards eeac12c58643 88: onsuccess: #97: 1: Success after binutils/gcc/linux/gl [...] discards 346813260c7d 87: onsuccess: #96: 1: Success after binutils/gcc/linux/gl [...] discards 3a6ec04db157 86: onsuccess: #95: 1: Success after binutils/gcc/linux/gl [...] discards 7c25567c3eec 85: onsuccess: #94: 1: Success after binutils/gcc/linux/gl [...] discards 7dfbc8e2f2ba 84: onsuccess: #93: 1: Success after binutils/gcc/linux/gl [...] discards 40ee9f2facd8 83: onsuccess: #92: 1: Success after binutils/gcc/linux/gd [...] discards eddaa635a37a 82: onsuccess: #91: 1: Success after binutils/gcc/linux/gd [...] discards 6a2784fa2bd9 81: onsuccess: #90: 1: Success after binutils/gcc/linux/gl [...] discards adfcb10c9177 80: onsuccess: #89: 1: Success after binutils/gcc/gdb: 198 [...] discards 42daccd496cc 79: onsuccess: #88: 1: Success after binutils/gcc/linux/gd [...] discards 6c78c2c440d2 78: onsuccess: #87: 1: Success after binutils/gcc/linux/gl [...] discards 82419aac2d03 77: onsuccess: #86: 1: Success after binutils/gcc/linux/gl [...] discards 07e23abf5c6c 76: onsuccess: #85: 1: Success after binutils/gcc/linux/gd [...] discards 06e5b083c7bb 75: onsuccess: #84: 1: Success after binutils/gcc/linux/gd [...] discards 6482dc6a43ea 74: onsuccess: #83: 1: Success after binutils/gcc/linux/gd [...] discards 07677c0cb618 73: onsuccess: #82: 1: Success after binutils/gcc/linux/gd [...] discards dc51f158258d 72: onsuccess: #81: 1: Success after binutils/gcc/linux/gl [...] discards ecb28d08a6c4 71: onsuccess: #80: 1: Success after binutils/gcc/linux/gl [...] discards 4c30f0137a81 70: onsuccess: #79: 1: Success after binutils/gcc/linux/gl [...] discards 9bb9f5c26d52 69: onsuccess: #78: 1: Success after binutils/gcc/linux/gd [...] discards 8b9aefe61e9f 68: onsuccess: #77: 1: Success after binutils/gcc/linux/gl [...] discards 2ea4c8c9151d 67: onsuccess: #76: 1: Success after binutils/gcc/linux/gl [...] discards 696dc0cfd616 66: onsuccess: #75: 1: Success after binutils/gcc/gdb: 30 commits discards 66318d8fd972 65: onsuccess: #74: 1: Success after binutils/gcc/linux/gd [...] discards 1aa3cd96b1c5 64: onsuccess: #73: 1: Success after binutils/gcc/linux/gl [...] discards 9f5628be5996 63: onsuccess: #72: 1: Success after binutils/gcc/linux/gl [...] discards 4aee9cbc08f6 62: onsuccess: #71: 1: Success after binutils/gcc/linux/gl [...] discards 7874eff2bd28 61: onsuccess: #70: 1: Success after binutils/gcc/glibc/gd [...] discards 917c731203cf 60: onsuccess: #69: 1: Success after binutils/gcc/gdb: 103 [...] discards 42f8a9689dfb 59: onsuccess: #67: 1: Success after binutils/gcc/linux/gl [...] discards bd47f71c84db 58: onsuccess: #65: 1: Success after binutils/gcc/linux/gd [...] discards 812d6687691b 57: onsuccess: #64: 1: Success after binutils/gcc/linux/gd [...] discards cf92c0b97cd4 56: onsuccess: #63: 1: Success after binutils/gcc/linux/gl [...] discards 1f3ade66d7c9 55: onsuccess: #62: 1: Success after binutils/gcc/linux/gd [...] discards fb84ced8f401 54: onsuccess: #61: 1: Success after binutils/gcc/gdb: 14 commits discards d305690bfa30 53: onsuccess: #60: 1: Success after binutils/gcc/gdb: 42 commits discards 59e47b921042 52: onsuccess: #59: 1: Success after binutils/gcc/linux/gd [...] discards 3adbe3cb4fae 51: onsuccess: #58: 1: Success after binutils/gcc/gdb: 46 commits discards fdf93d178751 50: onsuccess: #57: 1: Success after binutils/gcc/linux/gd [...] discards e64556752313 49: onsuccess: #56: 1: Success after binutils/gcc/linux/gd [...] discards 359aad3c43ca 48: onsuccess: #55: 1: Success after binutils/gcc/linux/gl [...] discards ac8e50d5ba11 47: onsuccess: #54: 1: Success after binutils/gcc/linux/gl [...] discards b7d236506cbd 46: onsuccess: #53: 1: Success after binutils/gcc/linux/gl [...] discards 84bdd935f70c 45: onsuccess: #52: 1: Success after binutils/gcc/linux/gl [...] discards 9d7228c4f430 44: onsuccess: #51: 1: Success after binutils/gcc/gdb: 15 commits discards 4cc16bf36db1 43: onsuccess: #50: 1: Success after binutils/gcc/linux/gd [...] discards e98c21c1744d 42: onsuccess: #49: 1: Success after binutils/gcc/linux/gd [...] discards 64eb3bf15963 41: onsuccess: #48: 1: Success after binutils/gcc/linux/gl [...] discards 56f491a8e4fd 40: onsuccess: #47: 1: Success after binutils/gcc/linux/gl [...] discards b29f14e87431 39: onsuccess: #46: 1: Success after binutils/gcc/linux/gd [...] discards a00d4f4524df 38: onsuccess: #45: 1: Success after binutils/gcc/linux/gl [...] discards 8f901a61295c 37: onsuccess: #44: 1: Success after binutils/gcc/linux/gd [...] new 8bf3466af978 37: onsuccess: #44: 1: Success after binutils/gcc/linux/gd [...] new fb9c40a4d459 38: onsuccess: #45: 1: Success after binutils/gcc/linux/gl [...] new 43c20fa45cd8 39: onsuccess: #46: 1: Success after binutils/gcc/linux/gd [...] new 3666d86746ba 40: onsuccess: #47: 1: Success after binutils/gcc/linux/gl [...] new 042c3268fdb4 41: onsuccess: #48: 1: Success after binutils/gcc/linux/gl [...] new a024a10513ee 42: onsuccess: #49: 1: Success after binutils/gcc/linux/gd [...] new 41f68badc447 43: onsuccess: #50: 1: Success after binutils/gcc/linux/gd [...] new 33ef971256fd 44: onsuccess: #51: 1: Success after binutils/gcc/gdb: 15 commits new 783bd1ac7bf3 45: onsuccess: #52: 1: Success after binutils/gcc/linux/gl [...] new c12ff05ae0f5 46: onsuccess: #53: 1: Success after binutils/gcc/linux/gl [...] new 61c69f532a42 47: onsuccess: #54: 1: Success after binutils/gcc/linux/gl [...] new c51422b4aa90 48: onsuccess: #55: 1: Success after binutils/gcc/linux/gl [...] new 912069084958 49: onsuccess: #56: 1: Success after binutils/gcc/linux/gd [...] new 7d5651c3706a 50: onsuccess: #57: 1: Success after binutils/gcc/linux/gd [...] new ee3e650bf56b 51: onsuccess: #58: 1: Success after binutils/gcc/gdb: 46 commits new b0b0dd8e23e8 52: onsuccess: #59: 1: Success after binutils/gcc/linux/gd [...] new 446d17d5eb77 53: onsuccess: #60: 1: Success after binutils/gcc/gdb: 42 commits new 41d9f84831b5 54: onsuccess: #61: 1: Success after binutils/gcc/gdb: 14 commits new f5d061f66b18 55: onsuccess: #62: 1: Success after binutils/gcc/linux/gd [...] new 785cb3ee5258 56: onsuccess: #63: 1: Success after binutils/gcc/linux/gl [...] new 0b76ce3e2b35 57: onsuccess: #64: 1: Success after binutils/gcc/linux/gd [...] new d1952ff88172 58: onsuccess: #65: 1: Success after binutils/gcc/linux/gd [...] new e977ba8f3513 59: onsuccess: #67: 1: Success after binutils/gcc/linux/gl [...] new e794bdb6a176 60: onsuccess: #69: 1: Success after binutils/gcc/gdb: 103 [...] new f72bdeee05f7 61: onsuccess: #70: 1: Success after binutils/gcc/glibc/gd [...] new 4aea8cc3106e 62: onsuccess: #71: 1: Success after binutils/gcc/linux/gl [...] new d53206bcc2f2 63: onsuccess: #72: 1: Success after binutils/gcc/linux/gl [...] new 4a2a6c65ba8f 64: onsuccess: #73: 1: Success after binutils/gcc/linux/gl [...] new 3c9e1608c3e6 65: onsuccess: #74: 1: Success after binutils/gcc/linux/gd [...] new 53a7b7954cff 66: onsuccess: #75: 1: Success after binutils/gcc/gdb: 30 commits new 2d7bf98bbcb7 67: onsuccess: #76: 1: Success after binutils/gcc/linux/gl [...] new aa7bd43f1b17 68: onsuccess: #77: 1: Success after binutils/gcc/linux/gl [...] new 01eb13ecbeec 69: onsuccess: #78: 1: Success after binutils/gcc/linux/gd [...] new 043a0496207c 70: onsuccess: #79: 1: Success after binutils/gcc/linux/gl [...] new 3460b715b8e7 71: onsuccess: #80: 1: Success after binutils/gcc/linux/gl [...] new 047676ae0817 72: onsuccess: #81: 1: Success after binutils/gcc/linux/gl [...] new 765aca06e3cc 73: onsuccess: #82: 1: Success after binutils/gcc/linux/gd [...] new a13decf55288 74: onsuccess: #83: 1: Success after binutils/gcc/linux/gd [...] new ce5e3c861c2e 75: onsuccess: #84: 1: Success after binutils/gcc/linux/gd [...] new 70cb8ac897d1 76: onsuccess: #85: 1: Success after binutils/gcc/linux/gd [...] new 22bfde27a9ec 77: onsuccess: #86: 1: Success after binutils/gcc/linux/gl [...] new aca703e1b6d4 78: onsuccess: #87: 1: Success after binutils/gcc/linux/gl [...] new 9489f38c424b 79: onsuccess: #88: 1: Success after binutils/gcc/linux/gd [...] new 9b969fad3525 80: onsuccess: #89: 1: Success after binutils/gcc/gdb: 198 [...] new ae877c697a47 81: onsuccess: #90: 1: Success after binutils/gcc/linux/gl [...] new e664aaef3ab0 82: onsuccess: #91: 1: Success after binutils/gcc/linux/gd [...] new 1921944aa704 83: onsuccess: #92: 1: Success after binutils/gcc/linux/gd [...] new 00fc7e0083a7 84: onsuccess: #93: 1: Success after binutils/gcc/linux/gl [...] new 73caff62771e 85: onsuccess: #94: 1: Success after binutils/gcc/linux/gl [...] new db532b55f822 86: onsuccess: #95: 1: Success after binutils/gcc/linux/gl [...] new 900e078ea0fd 87: onsuccess: #96: 1: Success after binutils/gcc/linux/gl [...] new 5347079e8975 88: onsuccess: #97: 1: Success after binutils/gcc/linux/gl [...] new 292e5f0b0edd 89: onsuccess: #98: 1: Success after binutils/gcc/linux/gl [...] new b153f5362810 90: onsuccess: #99: 1: Success after binutils/gcc/linux/gd [...] new 8c4c22b04d20 91: onsuccess: #100: 1: Success after binutils/gcc/linux/g [...] new eaf1b2281060 92: onsuccess: #101: 1: Success after binutils/gcc/linux/g [...] new f46ee4b8823b 93: onsuccess: #103: 1: Success after binutils/gcc/linux/g [...] new 271350d53076 94: onsuccess: #104: 1: Success after binutils/gcc/linux/g [...] new d44df8d070ba 95: onsuccess: #105: 1: Success after binutils/gcc/linux/g [...] new ca47f532249b 96: onsuccess: #106: 1: Success after binutils/gcc/linux/g [...] new 1140a0552661 97: onsuccess: #107: 1: Success after binutils/gcc/linux/g [...] new 6a8639ef0114 98: onsuccess: #108: 1: Success after binutils/gcc/linux/g [...] new b7c6d80b33d1 99: onsuccess: #120: 1: Success after binutils/gcc/linux/g [...] new 82ef1b75797e 100: onsuccess: #121: 1: Success after binutils/gcc/glibc/ [...] new d1979672df95 101: onsuccess: #122: 1: Success after binutils/gcc/linux/ [...] new cf3f7cdd850c 102: onsuccess: #123: 1: Success after binutils/gcc/linux/ [...] new 3ca6f48f2e9a 103: onsuccess: #1: 1: Success after binutils/gcc/linux/gl [...] new ddf59345a8af 104: onsuccess: #2: 1: Success after binutils/gcc/linux/gl [...] new 573453f2bc41 105: onsuccess: #3: 1: Success after binutils/gcc/linux/gl [...] new ef2fcf008d44 106: onsuccess: #4: 1: Success after binutils/gcc/linux/gl [...] new 4322f6fe3aed 107: onsuccess: #5: 1: Success after binutils/gcc/linux/gl [...] new 8e15be964670 108: onsuccess: #6: 1: Success after binutils/gcc/linux/gd [...] new 5592e2338917 109: onsuccess: #7: 1: Success after binutils/gcc/linux/gl [...] new 8bd3716e7304 110: onsuccess: #8: 1: Success after binutils/gcc/linux/gl [...] new 40333a07fe42 111: onsuccess: #9: 1: Success after binutils/gcc/linux/gd [...] new de654fcce8f9 112: onsuccess: #10: 1: Success after binutils/gcc/linux/g [...] new a38648668796 113: onsuccess: #11: 1: Success after binutils/gcc/linux/g [...] new e87898019f62 114: onsuccess: #13: 1: Success after binutils/gcc/linux/g [...] new 4ed39b880ca7 115: onsuccess: #14: 1: Success after binutils/gcc/linux/g [...] new 820ee632749b 116: onsuccess: #15: 1: Success after binutils/gcc/linux/g [...] new b8c200e9ac6b 117: onsuccess: #16: 1: Success after binutils/gcc/linux/g [...] new fe1ed8dd8df0 118: onsuccess: #17: 1: Success after binutils/gcc/linux/g [...] new d5c4dd7c8ae5 119: onsuccess: #18: 1: Success after binutils/gcc/linux/g [...] new d2729fa74654 120: onsuccess: #19: 1: Success after binutils/gcc/linux/g [...] new 5518d7dfef6c 121: force: #26: : Failure after baseline build: no new commits new c42ff80abd8d 122: onsuccess: #28: 1: Success after binutils/gcc/linux/g [...] new 3676796d448e 123: onsuccess: #29: 1: Success after binutils/gcc/linux/g [...] new 3ac9702e4d40 124: onsuccess: #30: 1: Success after binutils/gcc/linux/g [...] new 6df11d6745f9 125: onsuccess: #31: 1: Success after binutils/gcc/linux/g [...] new cc514fecdce4 126: onsuccess: #32: 1: Success after binutils/gcc/linux/g [...] new 79992d1f7a88 127: onsuccess: #33: 1: Success after binutils/gcc/linux/g [...] new cf6eded33239 128: onsuccess: #34: 1: Success after binutils/gcc/linux/g [...] new 7c8c0e313bcf 129: onsuccess: #35: 1: Success after binutils/gcc/linux/g [...] new e1deb34fd70f 130: onsuccess: #36: 1: Success after binutils/gcc/linux/g [...] new c3607484e4d8 131: onsuccess: #37: 1: Success after binutils/gcc/linux/g [...] new a2b3577efbfe 132: onsuccess: #39: 1: [TCWG CI] Success after binutils/g [...] new 20bcb68b252f 133: onsuccess: #40: 1: [TCWG CI] Success after binutils/g [...] new f0af3b7c4c0e 134: onsuccess: #41: 1: [TCWG CI] Success after binutils/g [...] new 46a5f0da8b52 135: onsuccess: #42: 1: [TCWG CI] Success after binutils/g [...] new 30c07fa204d7 136: onsuccess: #43: 1: [TCWG CI] Success after binutils/g [...] new d58bdff50b41 137: onsuccess: #44: 1: [TCWG CI] Success after binutils/g [...] new f9f8334e9bee 138: onsuccess: #45: 1: [TCWG CI] Success after binutils/g [...] This update added new revisions after undoing existing revisions. That is to say, some revisions that were in the old version of the branch are not in the new version. This situation occurs when a user --force pushes a change and generates a repository containing something like this: * -- * -- B -- O -- O -- O (090d160c29f1) \ 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 2072 -> 2088 bytes 02-prepare_abe/console.log.xz | Bin 2508 -> 2548 bytes 03-build_abe-binutils/console.log.xz | Bin 49356 -> 49572 bytes 04-build_abe-gcc/console.log.xz | Bin 236412 -> 236344 bytes 06-build_abe-linux/console.log.xz | Bin 8480 -> 8740 bytes 07-build_abe-glibc/console.log.xz | Bin 232780 -> 233120 bytes 08-build_abe-gdb/console.log.xz | Bin 47332 -> 46644 bytes 09-build_abe-dejagnu/console.log.xz | Bin 3760 -> 3764 bytes 10-build_abe-check_gdb/console.log.xz | Bin 2784 -> 2760 bytes 11-check_regression/console.log.xz | Bin 4404 -> 5156 bytes 11-check_regression/results.compare2 | 4 +- 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/changes-list-long.txt | 46 +++++++++++++++-------- mail/changes-list-short.txt | 2 +- mail/last_good.sh | 32 ++++++++-------- manifest.sh | 38 +++++++++---------- sumfiles/gdb.log.xz | Bin 14444 -> 14436 bytes sumfiles/gdb.sum | 4 +- 24 files changed, 111 insertions(+), 95 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

1 year, 7 months

[newlib] branch main updated (544aa97f8 -> cc8404039)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. unknown user pushed a change to branch main in repository newlib. from 544aa97f8 Bump newlib version in the manual to 4.3.0 new cc8404039 Respect `db_home` setting even for SYSTEM/Microsoft accounts 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: winsup/cygwin/uinfo.cc | 6 +++++- 1 file changed, 5 insertions(+), 1 deletion(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

1 year, 7 months

[newlib] branch master updated (544aa97f8 -> cc8404039)

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 newlib. from 544aa97f8 Bump newlib version in the manual to 4.3.0 new cc8404039 Respect `db_home` setting even for SYSTEM/Microsoft accounts 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: winsup/cygwin/uinfo.cc | 6 +++++- 1 file changed, 5 insertions(+), 1 deletion(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

1 year, 7 months

Jump to page:

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

Tcwg-commits April 2023