Tcwg-commits March 2023

tcwg-commits@lists.linaro.org

5 participants
3834 discussions

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_bmk-code_vect-spec2k6/gnu-aarch64-master-O3 updated (0b9ac4d6295 -> 67fd8998993)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. tcwg-buildslave pushed a change to branch linaro-local/ci/tcwg_bmk-code_vect-spec2k6/gnu-aarch64-master-O3 in repository toolchain/ci/base-artifacts. from 0b9ac4d6295 6: onsuccess: #7: 1: [TCWG CI] No change after binutils/gcc [...] new 67fd8998993 7: onsuccess: #9: 1: [TCWG CI] Success after binutils/glibc [...] 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 2040 -> 2040 bytes 02-prepare_abe/console.log.xz | Bin 2540 -> 2520 bytes 03-build_abe-binutils/console.log.xz | Bin 27312 -> 27596 bytes 04-build_abe-stage1/console.log.xz | Bin 71252 -> 71000 bytes 05-clean_sysroot/console.log.xz | Bin 332 -> 332 bytes 06-build_abe-linux/console.log.xz | Bin 8284 -> 8380 bytes 07-build_abe-glibc/console.log.xz | Bin 242436 -> 241912 bytes 08-build_abe-stage2/console.log.xz | Bin 176660 -> 175324 bytes 09-benchmark/benchmark-build.log | 96 +- 09-benchmark/benchmark.log | 94 +- 09-benchmark/console.log.xz | Bin 3976 -> 4072 bytes 10-check_regression/bmk-specific-variability.csv | 87 +- .../compare-results-vs-first-internal.csv | 230 +- .../compare-results-vs-prev-internal.csv | 242 +- 10-check_regression/console.log.xz | Bin 17280 -> 15812 bytes .../csv-results-vs-first-1/md5sum.csv | 1526 +- .../csv-results-vs-first-1/perf.csv | 2450 +- .../csv-results-vs-first-1/results.csv | 16306 +- .../csv-results-vs-first-1/size.csv | 13398 +- .../csv-results-vs-prev-0/md5sum.csv | 2217 +- 10-check_regression/csv-results-vs-prev-0/perf.csv | 2422 +- .../csv-results-vs-prev-0/results.csv | 9098 +- 10-check_regression/csv-results-vs-prev-0/size.csv | 423507 +++++++++--------- 10-check_regression/csv-results-vs-prev-0/sve.csv | 14975 +- 10-check_regression/csv-results-vs-prev-0/vect.csv | 3525 +- .../csv-results-vs-prev-1/md5sum.csv | 1526 +- 10-check_regression/csv-results-vs-prev-1/perf.csv | 2450 +- .../csv-results-vs-prev-1/results.csv | 16306 +- 10-check_regression/csv-results-vs-prev-1/size.csv | 13398 +- .../output-bmk-results/exe.improvement | 1 - .../output-bmk-results/exe.improvement.diff | 1 - .../output-bmk-results/exe.regression | 14 +- .../output-bmk-results/exe.regression.diff | 2 +- .../output-bmk-results/symbol.improvement | 7 +- .../output-bmk-results/symbol.improvement.diff | 2 +- .../output-bmk-results/symbol.regression | 16 +- .../output-bmk-results/symbol.regression.diff | 2 +- 10-check_regression/results-vs-first-brief.csv | 64 +- 10-check_regression/results-vs-first-full.csv | 2468 +- 10-check_regression/results-vs-first-internal.csv | 230 +- 10-check_regression/results-vs-first.csv | 230 +- 10-check_regression/results-vs-first.log | 1508 +- 10-check_regression/results-vs-prev-brief.csv | 68 +- 10-check_regression/results-vs-prev-compare.csv | 3 +- 10-check_regression/results-vs-prev-full.csv | 2798 +- 10-check_regression/results-vs-prev-internal.csv | 242 +- 10-check_regression/results-vs-prev.csv | 242 +- 10-check_regression/results-vs-prev.log | 1572 +- dashboard/dashboard-generate.sh | 2 +- .../400.perlbench/results-metadata.json | 12 +- .../squad-vs-first/401.bzip2/results-metadata.json | 12 +- .../squad-vs-first/401.bzip2/results-metrics.json | 2 +- .../squad-vs-first/403.gcc/results-metadata.json | 12 +- .../squad-vs-first/403.gcc/results-metrics.json | 2 +- .../410.bwaves/results-metadata.json | 12 +- .../squad-vs-first/410.bwaves/results-metrics.json | 2 +- .../416.gamess/results-metadata.json | 12 +- .../squad-vs-first/429.mcf/results-metadata.json | 12 +- .../squad-vs-first/429.mcf/results-metrics.json | 2 +- .../squad-vs-first/433.milc/results-metadata.json | 12 +- .../squad-vs-first/433.milc/results-metrics.json | 2 +- .../434.zeusmp/results-metadata.json | 12 +- .../squad-vs-first/434.zeusmp/results-metrics.json | 2 +- .../435.gromacs/results-metadata.json | 12 +- .../435.gromacs/results-metrics.json | 2 +- .../436.cactusADM/results-metadata.json | 12 +- .../437.leslie3d/results-metadata.json | 12 +- .../squad-vs-first/444.namd/results-metadata.json | 12 +- .../squad-vs-first/444.namd/results-metrics.json | 2 +- .../squad-vs-first/445.gobmk/results-metadata.json | 12 +- .../447.dealII/results-metadata.json | 12 +- .../squad-vs-first/447.dealII/results-metrics.json | 2 +- .../450.soplex/results-metadata.json | 12 +- .../squad-vs-first/450.soplex/results-metrics.json | 2 +- .../453.povray/results-metadata.json | 12 +- .../squad-vs-first/453.povray/results-metrics.json | 2 +- .../454.calculix/results-metadata.json | 12 +- .../squad-vs-first/456.hmmer/results-metadata.json | 12 +- .../squad-vs-first/458.sjeng/results-metadata.json | 12 +- .../459.GemsFDTD/results-metadata.json | 12 +- .../459.GemsFDTD/results-metrics.json | 2 +- .../462.libquantum/results-metadata.json | 12 +- .../462.libquantum/results-metrics.json | 2 +- .../464.h264ref/results-metadata.json | 12 +- .../464.h264ref/results-metrics.json | 2 +- .../squad-vs-first/465.tonto/results-metadata.json | 12 +- .../squad-vs-first/465.tonto/results-metrics.json | 2 +- .../squad-vs-first/470.lbm/results-metadata.json | 12 +- .../squad-vs-first/470.lbm/results-metrics.json | 2 +- .../471.omnetpp/results-metadata.json | 12 +- .../squad-vs-first/473.astar/results-metadata.json | 12 +- .../squad-vs-first/473.astar/results-metrics.json | 2 +- .../squad-vs-first/481.wrf/results-metadata.json | 12 +- .../squad-vs-first/481.wrf/results-metrics.json | 2 +- .../482.sphinx3/results-metadata.json | 12 +- .../482.sphinx3/results-metrics.json | 2 +- .../483.xalancbmk/results-metadata.json | 12 +- .../483.xalancbmk/results-metrics.json | 2 +- .../squad-vs-first/Mean/results-metadata.json | 12 +- dashboard/squad-vs-first/dashboard-push-squad.sh | 122 +- git/binutils_rev | 2 +- git/glibc_rev | 2 +- mail/changes-list-long.txt | 14 + mail/changes-list-short.txt | 1 + mail/mail-body.txt | 31 - mail/mail-subject.txt | 1 - mail/short-diag.txt | 1 + manifest.sh | 30 +- results_id | 2 +- 109 files changed, 267774 insertions(+), 266157 deletions(-) delete mode 100644 10-check_regression/output-bmk-results/exe.improvement delete mode 100644 10-check_regression/output-bmk-results/exe.improvement.diff create mode 100644 mail/changes-list-long.txt create mode 100644 mail/changes-list-short.txt 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, 8 months

[gcc] branch master updated (22c3a6c3c11 -> 2e71f05403c)

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 22c3a6c3c11 Don't emit -Wxor-used-as-pow on macro expansions [PR107002] new 2e71f05403c libbacktrace: minor fixes for zstd decompression 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: libbacktrace/elf.c | 40 ++++++++++++++++++++-------------------- 1 file changed, 20 insertions(+), 20 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_aosp-code_size-surfaceflinger/oriole-master updated (e85e74cdbe0 -> 07dccf3334c)

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_aosp-code_size-surfaceflinger/oriole-master in repository toolchain/ci/base-artifacts. from e85e74cdbe0 1: onsuccess: #47: 2: Success after aosp_superproject/llvm/ [...] new 07dccf3334c 2: onsuccess: #53: 2: [TCWG CI] Success after aosp_superpro [...] The 1 revisions listed above as "new" are entirely new to this repository and will be described in separate emails. The revisions listed as "adds" were already present in the repository and have only been added to this reference. Summary of changes: 01-reset_artifacts/console.log.xz | Bin 1976 -> 1988 bytes 02-build_aosp_toolchain/console.log.xz | Bin 197752 -> 198040 bytes 03-build_shadow_llvm/console.log.xz | Bin 130516 -> 131108 bytes 04-build_aosp/console.log.xz | Bin 69440 -> 69740 bytes 06-check_regression/aosp.improvements | 1 - 06-check_regression/binary.regressions | 7 +++ 06-check_regression/console.log.xz | Bin 7056 -> 6692 bytes 06-check_regression/jira-body.txt | 1 - 06-check_regression/mail-body.txt | 27 ---------- 06-check_regression/mail-subject.txt | 1 - 06-check_regression/results-vs-first.csv | 36 ++++++------- 06-check_regression/results-vs-prev.csv | 88 +++++++++++++++---------------- 06-check_regression/results.regressions | 1 + dashboard/dashboard-generate.sh | 2 +- git/aosp_superproject_rev | 2 +- git/toolchain_superproject_rev | 2 +- mail/changes-list-long.txt | 14 +++++ mail/changes-list-short.txt | 1 + mail/jira-body.txt | 1 - mail/mail-body.txt | 27 ---------- mail/mail-subject.txt | 1 - mail/short-diag.txt | 1 + manifest.sh | 25 +++++---- results | 1 + size.csv | 88 +++++++++++++++---------------- 25 files changed, 146 insertions(+), 181 deletions(-) delete mode 100644 06-check_regression/aosp.improvements create mode 100644 06-check_regression/binary.regressions delete mode 100644 06-check_regression/jira-body.txt delete mode 100644 06-check_regression/mail-body.txt delete mode 100644 06-check_regression/mail-subject.txt create mode 100644 06-check_regression/results.regressions create mode 100644 mail/changes-list-long.txt create mode 100644 mail/changes-list-short.txt delete mode 100644 mail/jira-body.txt 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, 8 months

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_gnu_native_check_gdb/master-aarch64 updated (2d4504a95ac -> f31d5445f2c)

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_gdb/master-aarch64 in repository toolchain/ci/base-artifacts. discards 2d4504a95ac 220: force: #65: 1: [TCWG CI] Failure after gdb-13-branchpo [...] discards 488577a333d 219: force: #64: 1: [TCWG CI] Success after gdb: 32 commits discards 08262ba346c 218: onsuccess: #62: 1: [TCWG CI] Success after binutils/gc [...] discards ccb6c867c63 217: onsuccess: #53: 1: Success after binutils/gcc/linux/gd [...] discards 4130945d9f6 216: onsuccess: #52: 1: Success after binutils/gcc/linux/gd [...] discards f621495d1d5 215: onsuccess: #48: 1: Success after binutils/gcc/linux/gd [...] discards 25bed252ef4 214: onsuccess: #47: 1: Success after gdb: 21 commits discards 42ef6dae7f6 213: force: #46: 1: Success after gdb-13-branchpoint-1550-g [...] discards d3eff7a75c2 212: force: #45: 1: Success after gdb: 22 commits discards 6e87fc04c97 211: onsuccess: #44: 1: Success after linux: 26 commits discards 9f0f389d5b1 210: onsuccess: #43: 1: Success after glibc-2.37.9000-181-g [...] discards 91af2700105 209: force: #37: 1: Success after baseline build: no new commits discards 208200ca9ba 208: onsuccess: #30: 1: Success after binutils/gcc/linux/gd [...] discards abfaa9b7c21 207: onsuccess: #29: 1: Success after binutils/gcc/linux/gd [...] discards b6ce1592da8 206: onsuccess: #28: 1: Success after binutils/gcc/linux/gd [...] discards db3a2a933fa 205: onsuccess: #27: 1: Success after binutils/gcc/linux/gd [...] discards 27ef9a9e204 204: force: #26: : Failure after baseline build: no new commits discards 1a3724e0664 203: onsuccess: #19: 1: Success after binutils/gcc/linux/gl [...] discards b14dbd0410a 202: onsuccess: #18: 1: Success after binutils/gcc/linux/gl [...] discards 28d9bc090e2 201: onsuccess: #17: 1: Success after binutils/gcc/linux/gd [...] discards 8b860345329 200: onsuccess: #16: 1: Success after binutils/gcc/linux/gl [...] discards 7db63c3df75 199: onsuccess: #15: 1: Success after binutils/gcc/linux/gd [...] discards cb351186e7e 198: onsuccess: #14: 1: Success after binutils/gcc/linux/gl [...] discards eafb6fd02a4 197: onsuccess: #13: 1: Success after binutils/gcc/linux/gl [...] discards 591399f1433 196: onsuccess: #12: 1: Success after binutils/gcc/linux/gl [...] discards 9fb5ef8bf7d 195: onsuccess: #11: 1: Success after binutils/gcc/linux/gd [...] discards b4d14f6efdf 194: onsuccess: #10: 1: Success after binutils/gcc/linux/gd [...] discards 4c2ad6a63ea 193: onsuccess: #9: 1: Success after binutils/gcc/linux/gdb [...] discards b0a6518a65f 192: onsuccess: #8: 1: Success after binutils/gcc/linux/gli [...] discards 3e0ad9fcba6 191: onsuccess: #7: 1: Success after binutils/gcc/linux/gli [...] discards 61e6bccf795 190: onsuccess: #6: 1: Success after binutils/gcc/linux/gli [...] discards 0f11a255f1d 189: onsuccess: #5: 1: Success after binutils/gcc/linux/gli [...] discards e2532431e8d 188: onsuccess: #4: 1: Success after binutils/gcc/linux/gdb [...] discards 9c92227b4a8 187: onsuccess: #3: 1: Success after binutils/gcc/linux/gli [...] discards 5f784bd2353 186: onsuccess: #2: 1: Success after binutils/gcc/linux/gdb [...] discards 849570e8b73 185: onsuccess: #1: 1: Success after binutils/gcc/linux/gli [...] discards e3bd187d4c2 184: onsuccess: #977: 1: Success after binutils/gcc/linux/g [...] discards 1fc2b8f6dae 183: onsuccess: #976: 1: Success after binutils/gcc/linux/g [...] discards 17d612ce84d 182: onsuccess: #975: 1: Success after binutils/gcc/linux/g [...] discards 04d00bd2ae8 181: onsuccess: #974: 1: Success after binutils/gcc/linux/g [...] discards dc05ce056b9 180: onsuccess: #973: 1: Success after binutils/gcc/linux/g [...] discards d8f8489cb3a 179: onsuccess: #972: 1: Success after binutils/gcc/linux/g [...] discards 980815729a6 178: onsuccess: #971: 1: Success after binutils/gcc/linux/g [...] discards 1efb01772bb 177: onsuccess: #970: 1: Success after binutils/gcc/linux/g [...] discards 8a975022466 176: onsuccess: #969: 1: Success after binutils/gcc/linux/g [...] discards 389ad1b099d 175: onsuccess: #968: 1: Success after binutils/gcc/linux/g [...] discards c2dd837b589 174: onsuccess: #967: 1: Success after binutils/gcc/linux/g [...] discards d33f8795c93 173: onsuccess: #966: 1: Success after binutils/gcc/linux/g [...] discards 9dd5e1a7048 172: onsuccess: #965: 1: Success after binutils/gcc/glibc/g [...] discards 337220fa982 171: onsuccess: #964: 1: Success after binutils/gcc/linux/g [...] discards 8d571085253 170: onsuccess: #963: 1: Success after binutils/gcc/linux/g [...] discards ed3d70cd145 169: onsuccess: #962: 1: Success after binutils/gcc/linux/g [...] discards e2cf48c66d4 168: onsuccess: #961: 1: Success after binutils/gcc/linux/g [...] discards 5976aa7b1d9 167: onsuccess: #960: 1: Success after binutils/gcc/linux/g [...] discards aa4c7e2c28a 166: onsuccess: #959: 1: Success after binutils/gcc/linux/g [...] discards 96b4c0460c8 165: onsuccess: #958: 1: Success after binutils/gcc/linux/g [...] discards ca37abc44fa 164: onsuccess: #957: 1: Success after binutils/gcc/glibc/g [...] discards 428369abe8c 163: onsuccess: #956: 1: Success after binutils/gcc/linux/g [...] discards 0ae4690a938 162: onsuccess: #955: 1: Success after binutils/gcc/linux/g [...] discards a0daa035931 161: onsuccess: #954: 1: Success after binutils/gcc/linux/g [...] discards 7b1644aba97 160: onsuccess: #953: 1: Success after binutils/gcc/linux/g [...] discards 93c29dd21c0 159: onsuccess: #952: 1: Success after binutils/gcc/linux/g [...] discards 11afd56271a 158: onsuccess: #951: 1: Success after gcc/linux: 19 commits discards bc867be843a 157: onsuccess: #950: 1: Success after binutils/gcc/linux/g [...] discards 282a7e9754a 156: onsuccess: #949: 1: Success after binutils/gcc/linux/g [...] discards 70f900f45d4 155: onsuccess: #948: 1: Success after binutils/gcc/linux/g [...] discards a7fb8010d48 154: onsuccess: #947: 1: Success after binutils/gcc/linux/g [...] discards dfd6159e28e 153: onsuccess: #946: 1: Success after binutils/gcc/linux/g [...] discards 4482ec07717 152: onsuccess: #945: 1: Success after binutils/gcc/linux/g [...] discards 4e3b86d3072 151: onsuccess: #944: 1: Success after binutils/gcc/linux/g [...] discards d373994863a 150: onsuccess: #943: 1: Success after binutils/gcc/linux/g [...] discards 499096342e8 149: onsuccess: #942: 1: Success after binutils/gcc/linux/g [...] discards 791614f5f44 148: onsuccess: #941: 1: Success after binutils/gcc/linux/g [...] discards 514c659ba82 147: onsuccess: #940: 1: Success after binutils/gcc/linux/g [...] discards 71e4b66f588 146: onsuccess: #939: 1: Success after binutils/gcc/linux/g [...] discards 0548d04d5e8 145: onsuccess: #934: 1: Success after binutils/gcc/linux/g [...] discards ed4ce363c58 144: onsuccess: #933: 1: Success after binutils/gcc/glibc/g [...] discards fa3ecb94a33 143: onsuccess: #931: 1: Success after binutils/gcc/linux/g [...] discards c6b4dce66bc 142: onsuccess: #929: 1: Success after binutils/gcc/linux/g [...] discards 6e85f5f2fbb 141: onsuccess: #928: 1: Success after binutils/gcc/linux/g [...] discards a130631c4de 140: onsuccess: #927: 1: Success after binutils/gcc/linux/g [...] discards fa5b803a7e8 139: onsuccess: #926: 1: Success after binutils/gcc/linux/g [...] discards 069d7b3e27c 138: onsuccess: #925: 1: Success after binutils/gcc/gdb: 11 [...] discards 8456c620862 137: onsuccess: #924: 1: Success after binutils/gcc/gdb: 43 [...] discards c1df253ca9c 136: onsuccess: #923: 1: Success after binutils/gcc/gdb: 10 [...] discards a024921548e 135: onsuccess: #922: 1: Success after binutils/gcc/linux/g [...] discards f85772815c8 134: onsuccess: #921: 1: Success after binutils/gcc/gdb: 26 [...] discards 56670330aa2 133: onsuccess: #920: 1: Success after binutils/gcc/linux/g [...] discards 5ef1d856729 132: onsuccess: #919: 1: Success after binutils/gcc/linux/g [...] discards 251e9ed9995 131: onsuccess: #918: 1: Success after binutils/gcc/linux/g [...] discards dbf1b0cadd8 130: onsuccess: #917: 1: Success after binutils/gcc/linux/g [...] discards 7181b31847b 129: onsuccess: #916: 1: Success after binutils/gcc/linux/g [...] discards dcf12b7f75f 128: onsuccess: #915: 1: Success after binutils/gcc/glibc/g [...] discards 7f62d832845 127: onsuccess: #914: 1: Success after binutils/gcc/linux/g [...] discards 5d914e0f903 126: onsuccess: #913: 1: Success after binutils/gcc/linux/g [...] discards f74aa9ca171 125: onsuccess: #912: 1: Success after binutils/gcc/linux/g [...] discards 522016d2592 124: onsuccess: #911: 1: Success after binutils/gcc/linux/g [...] discards 407f11f75bd 123: onsuccess: #910: 1: Success after binutils/gcc/linux/g [...] discards 62e65401217 122: onsuccess: #909: 1: Success after linux: 2753 commits discards 70f7a3620b2 121: onsuccess: #908: 1: Success after glibc: 2 commits discards aeef4082401 120: onsuccess: #906: 1: Success after binutils: 29 commits new 56ebbf4081e 120: onsuccess: #906: 1: Success after binutils: 29 commits new a95dca712b8 121: onsuccess: #908: 1: Success after glibc: 2 commits new d6b2fd17e54 122: onsuccess: #909: 1: Success after linux: 2753 commits new 003e788654f 123: onsuccess: #910: 1: Success after binutils/gcc/linux/g [...] new 28aa58308ee 124: onsuccess: #911: 1: Success after binutils/gcc/linux/g [...] new e8bd9e4e03d 125: onsuccess: #912: 1: Success after binutils/gcc/linux/g [...] new 29bd102fa3c 126: onsuccess: #913: 1: Success after binutils/gcc/linux/g [...] new ada6218b2c9 127: onsuccess: #914: 1: Success after binutils/gcc/linux/g [...] new f2471e34de9 128: onsuccess: #915: 1: Success after binutils/gcc/glibc/g [...] new 99be72c7cd2 129: onsuccess: #916: 1: Success after binutils/gcc/linux/g [...] new 5e6886f9950 130: onsuccess: #917: 1: Success after binutils/gcc/linux/g [...] new e8da27bacf5 131: onsuccess: #918: 1: Success after binutils/gcc/linux/g [...] new 4fdcb9291a5 132: onsuccess: #919: 1: Success after binutils/gcc/linux/g [...] new 50566f68fbb 133: onsuccess: #920: 1: Success after binutils/gcc/linux/g [...] new 713fa3d4c81 134: onsuccess: #921: 1: Success after binutils/gcc/gdb: 26 [...] new 2492689ea5c 135: onsuccess: #922: 1: Success after binutils/gcc/linux/g [...] new 8e756043466 136: onsuccess: #923: 1: Success after binutils/gcc/gdb: 10 [...] new 2b80bd077d8 137: onsuccess: #924: 1: Success after binutils/gcc/gdb: 43 [...] new d0c49ee87e2 138: onsuccess: #925: 1: Success after binutils/gcc/gdb: 11 [...] new 5ecd163bf2b 139: onsuccess: #926: 1: Success after binutils/gcc/linux/g [...] new 44d54229529 140: onsuccess: #927: 1: Success after binutils/gcc/linux/g [...] new a07785ac0c0 141: onsuccess: #928: 1: Success after binutils/gcc/linux/g [...] new bfd675a23cc 142: onsuccess: #929: 1: Success after binutils/gcc/linux/g [...] new 2e2897d5b2a 143: onsuccess: #931: 1: Success after binutils/gcc/linux/g [...] new 9ff10c4edf0 144: onsuccess: #933: 1: Success after binutils/gcc/glibc/g [...] new 0ff0f941589 145: onsuccess: #934: 1: Success after binutils/gcc/linux/g [...] new 7c9cf424e7e 146: onsuccess: #939: 1: Success after binutils/gcc/linux/g [...] new 02efbbdd985 147: onsuccess: #940: 1: Success after binutils/gcc/linux/g [...] new 96150f25e61 148: onsuccess: #941: 1: Success after binutils/gcc/linux/g [...] new f8a7a46f7f8 149: onsuccess: #942: 1: Success after binutils/gcc/linux/g [...] new 055ca3326c7 150: onsuccess: #943: 1: Success after binutils/gcc/linux/g [...] new bfa9f57ba7a 151: onsuccess: #944: 1: Success after binutils/gcc/linux/g [...] new 1b73d2f6fcc 152: onsuccess: #945: 1: Success after binutils/gcc/linux/g [...] new 8d848ba9bdc 153: onsuccess: #946: 1: Success after binutils/gcc/linux/g [...] new 7a524aa3241 154: onsuccess: #947: 1: Success after binutils/gcc/linux/g [...] new 0ff60d4c234 155: onsuccess: #948: 1: Success after binutils/gcc/linux/g [...] new 27557a9c615 156: onsuccess: #949: 1: Success after binutils/gcc/linux/g [...] new 5c594f6c4ed 157: onsuccess: #950: 1: Success after binutils/gcc/linux/g [...] new 32c728b43bc 158: onsuccess: #951: 1: Success after gcc/linux: 19 commits new 6398cae56be 159: onsuccess: #952: 1: Success after binutils/gcc/linux/g [...] new 7dd89d3eb6e 160: onsuccess: #953: 1: Success after binutils/gcc/linux/g [...] new 258afa83822 161: onsuccess: #954: 1: Success after binutils/gcc/linux/g [...] new 1e329fa7ccd 162: onsuccess: #955: 1: Success after binutils/gcc/linux/g [...] new 29023845b10 163: onsuccess: #956: 1: Success after binutils/gcc/linux/g [...] new b31c7d9d152 164: onsuccess: #957: 1: Success after binutils/gcc/glibc/g [...] new c7503bd7b07 165: onsuccess: #958: 1: Success after binutils/gcc/linux/g [...] new c92428a4bbf 166: onsuccess: #959: 1: Success after binutils/gcc/linux/g [...] new af2b6707a4d 167: onsuccess: #960: 1: Success after binutils/gcc/linux/g [...] new de60303642f 168: onsuccess: #961: 1: Success after binutils/gcc/linux/g [...] new 5cc499b0cb5 169: onsuccess: #962: 1: Success after binutils/gcc/linux/g [...] new 674ce4ef9a3 170: onsuccess: #963: 1: Success after binutils/gcc/linux/g [...] new 89179b05355 171: onsuccess: #964: 1: Success after binutils/gcc/linux/g [...] new 90a924f6fc1 172: onsuccess: #965: 1: Success after binutils/gcc/glibc/g [...] new da4c034d559 173: onsuccess: #966: 1: Success after binutils/gcc/linux/g [...] new 93069d90411 174: onsuccess: #967: 1: Success after binutils/gcc/linux/g [...] new 5b81b9660d1 175: onsuccess: #968: 1: Success after binutils/gcc/linux/g [...] new fabc52a31e8 176: onsuccess: #969: 1: Success after binutils/gcc/linux/g [...] new d7405ed577a 177: onsuccess: #970: 1: Success after binutils/gcc/linux/g [...] new f60c7c7a7b4 178: onsuccess: #971: 1: Success after binutils/gcc/linux/g [...] new 2a4ebeb7d75 179: onsuccess: #972: 1: Success after binutils/gcc/linux/g [...] new 17a1381c38d 180: onsuccess: #973: 1: Success after binutils/gcc/linux/g [...] new ed69d3627e0 181: onsuccess: #974: 1: Success after binutils/gcc/linux/g [...] new 5986ff8a2f8 182: onsuccess: #975: 1: Success after binutils/gcc/linux/g [...] new 541c6bdf2a2 183: onsuccess: #976: 1: Success after binutils/gcc/linux/g [...] new 8c14d932ff3 184: onsuccess: #977: 1: Success after binutils/gcc/linux/g [...] new a4afa2b1ec9 185: onsuccess: #1: 1: Success after binutils/gcc/linux/gli [...] new c4be55c0a50 186: onsuccess: #2: 1: Success after binutils/gcc/linux/gdb [...] new 1a169b5ca4c 187: onsuccess: #3: 1: Success after binutils/gcc/linux/gli [...] new 7f8f0a1c3fa 188: onsuccess: #4: 1: Success after binutils/gcc/linux/gdb [...] new 54e1e9c7a17 189: onsuccess: #5: 1: Success after binutils/gcc/linux/gli [...] new 7c3f2f604bc 190: onsuccess: #6: 1: Success after binutils/gcc/linux/gli [...] new 00a19c16162 191: onsuccess: #7: 1: Success after binutils/gcc/linux/gli [...] new 89698251ab8 192: onsuccess: #8: 1: Success after binutils/gcc/linux/gli [...] new 093c33d97e1 193: onsuccess: #9: 1: Success after binutils/gcc/linux/gdb [...] new da532bad07d 194: onsuccess: #10: 1: Success after binutils/gcc/linux/gd [...] new 0e0ffd8b29d 195: onsuccess: #11: 1: Success after binutils/gcc/linux/gd [...] new 7e733a8e6d6 196: onsuccess: #12: 1: Success after binutils/gcc/linux/gl [...] new 4f3e5f3eef7 197: onsuccess: #13: 1: Success after binutils/gcc/linux/gl [...] new 3ae1519b9d4 198: onsuccess: #14: 1: Success after binutils/gcc/linux/gl [...] new 27c70738761 199: onsuccess: #15: 1: Success after binutils/gcc/linux/gd [...] new c264b456526 200: onsuccess: #16: 1: Success after binutils/gcc/linux/gl [...] new 78f1601fd77 201: onsuccess: #17: 1: Success after binutils/gcc/linux/gd [...] new 12b2031d719 202: onsuccess: #18: 1: Success after binutils/gcc/linux/gl [...] new 1fbb2211dc2 203: onsuccess: #19: 1: Success after binutils/gcc/linux/gl [...] new d5a2527a016 204: force: #26: : Failure after baseline build: no new commits new 0fbc77ac0d5 205: onsuccess: #27: 1: Success after binutils/gcc/linux/gd [...] new d5f5ab75b9e 206: onsuccess: #28: 1: Success after binutils/gcc/linux/gd [...] new 88eda637be5 207: onsuccess: #29: 1: Success after binutils/gcc/linux/gd [...] new 991e201b890 208: onsuccess: #30: 1: Success after binutils/gcc/linux/gd [...] new bddd52c35df 209: force: #37: 1: Success after baseline build: no new commits new 2eac9e0f723 210: onsuccess: #43: 1: Success after glibc-2.37.9000-181-g [...] new 581c9f25a32 211: onsuccess: #44: 1: Success after linux: 26 commits new 58b0ea4d3ba 212: force: #45: 1: Success after gdb: 22 commits new ecd322c76bd 213: force: #46: 1: Success after gdb-13-branchpoint-1550-g [...] new f0000d73dd7 214: onsuccess: #47: 1: Success after gdb: 21 commits new 4d47ceba027 215: onsuccess: #48: 1: Success after binutils/gcc/linux/gd [...] new 6a9aea6a0d3 216: onsuccess: #52: 1: Success after binutils/gcc/linux/gd [...] new 971a2fa4873 217: onsuccess: #53: 1: Success after binutils/gcc/linux/gd [...] new 43aca899884 218: onsuccess: #62: 1: [TCWG CI] Success after binutils/gc [...] new b41e6ff1e80 219: force: #64: 1: [TCWG CI] Success after gdb: 32 commits new 4662a23de58 220: force: #65: 1: [TCWG CI] Failure after gdb-13-branchpo [...] new f31d5445f2c 221: onsuccess: #66: 1: [TCWG CI] Success after gdb: 17 commits This update added new revisions after undoing existing revisions. That is to say, some revisions that were in the old version of the branch are not in the new version. This situation occurs when a user --force pushes a change and generates a repository containing something like this: * -- * -- B -- O -- O -- O (2d4504a95ac) \ N -- N -- N refs/heads/linaro-local/ci/tcwg_gnu_native_check_gdb/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 2032 -> 2012 bytes 02-prepare_abe/console.log.xz | Bin 2500 -> 2516 bytes 03-build_abe-binutils/console.log.xz | Bin 35276 -> 35228 bytes 04-build_abe-gcc/console.log.xz | Bin 202768 -> 204064 bytes 06-build_abe-linux/console.log.xz | Bin 8820 -> 8896 bytes 07-build_abe-glibc/console.log.xz | Bin 241448 -> 240924 bytes 08-build_abe-gdb/console.log.xz | Bin 34716 -> 34964 bytes 09-build_abe-dejagnu/console.log.xz | Bin 3780 -> 3784 bytes 10-build_abe-check_gdb/console.log.xz | Bin 2692 -> 2824 bytes 11-check_regression/console.log.xz | Bin 3648 -> 4252 bytes 11-check_regression/extra-bisect-params | 1 - 11-check_regression/fails.sum | 6 -- 11-check_regression/results.compare | 9 +- 11-check_regression/results.compare2 | 163 +++++++++++++++++++++++++++++++- 11-check_regression/results.regressions | 14 --- 11-check_regression/trigger-bisect | 3 - 11-check_regression/trigger-notify | 0 12-update_baseline/console.log | 62 ++++++------ dashboard/dashboard-generate.sh | 2 +- git/gdb_rev | 2 +- jenkins/notify.sh | 3 - mail/changes-list-long.txt | 11 ++- mail/changes-list-short.txt | 2 +- mail/short-diag.txt | 2 +- manifest.sh | 22 ++--- results | 14 --- sumfiles/gdb.log.0.xz | Bin 1932664 -> 1948932 bytes sumfiles/gdb.log.1.xz | Bin 20768 -> 34336 bytes sumfiles/gdb.log.2.xz | Bin 5552 -> 5508 bytes sumfiles/gdb.log.3.xz | Bin 5484 -> 5424 bytes sumfiles/gdb.sum | 57 +++++------ sumfiles/gdb.sum.0 | 60 ++++++------ sumfiles/gdb.sum.1 | 101 +++++++++++++++++++- sumfiles/gdb.sum.2 | 4 +- sumfiles/gdb.sum.3 | 4 +- 35 files changed, 378 insertions(+), 164 deletions(-) delete mode 100644 11-check_regression/extra-bisect-params delete mode 100644 11-check_regression/fails.sum delete mode 100644 11-check_regression/results.regressions delete mode 100644 11-check_regression/trigger-bisect delete mode 100644 11-check_regression/trigger-notify delete mode 100755 jenkins/notify.sh -- 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_binutils/master-arm updated (19188942ac4 -> fc912da49f2)

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 19188942ac4 2: onsuccess: #3: 1: Success after binutils/gcc/linux/glibc [...] new fc912da49f2 3: onsuccess: #5: 1: [TCWG CI] Success after binutils/gcc/l [...] 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 2080 -> 2072 bytes 02-prepare_abe/console.log.xz | Bin 2536 -> 2496 bytes 03-build_abe-binutils/console.log.xz | Bin 27392 -> 26860 bytes 04-build_abe-stage1/console.log.xz | Bin 89180 -> 88992 bytes 05-clean_sysroot/console.log.xz | Bin 332 -> 332 bytes 06-build_abe-linux/console.log.xz | Bin 9104 -> 8760 bytes 07-build_abe-glibc/console.log.xz | Bin 233588 -> 232528 bytes 08-build_abe-stage2/console.log.xz | Bin 225560 -> 225264 bytes 09-build_abe-gdb/console.log.xz | Bin 34716 -> 34592 bytes 10-build_abe-qemu/console.log.xz | Bin 32020 -> 30968 bytes 11-build_abe-dejagnu/console.log.xz | Bin 3820 -> 3812 bytes 12-build_abe-check_binutils/console.log.xz | Bin 2524 -> 2324 bytes 13-check_regression/console.log.xz | Bin 4836 -> 5796 bytes 13-check_regression/mail-body.txt | 43 -------------------------- 13-check_regression/mail-subject.txt | 1 - 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 +- git/qemu_rev | 2 +- mail/changes-list-long.txt | 38 +++++++++++++++++++++++ mail/changes-list-short.txt | 1 + mail/mail-body.txt | 43 -------------------------- mail/mail-subject.txt | 1 - mail/short-diag.txt | 1 + manifest.sh | 48 ++++++++++++++--------------- sumfiles/binutils.log.xz | Bin 61180 -> 62000 bytes sumfiles/binutils.sum | 2 +- sumfiles/gas.log.xz | Bin 101048 -> 101044 bytes sumfiles/gas.sum | 4 +-- sumfiles/ld.log.xz | Bin 113984 -> 114016 bytes sumfiles/ld.sum | 4 +-- 36 files changed, 84 insertions(+), 132 deletions(-) delete mode 100644 13-check_regression/mail-body.txt delete mode 100644 13-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/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, 8 months

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_kernel/llvm-master-aarch64-lts-defconfig updated (a5b5ae4fce1 -> 3280add548c)

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-lts-defconfig in repository toolchain/ci/base-artifacts. from a5b5ae4fce1 50: onsuccess: #8: boot: Success after binutils/llvm/linux/ [...] new 3280add548c 51: onsuccess: #9: boot: [TCWG CI] Success after binutils/l [...] 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 2012 -> 1996 bytes 02-prepare_abe/console.log.xz | Bin 2572 -> 2496 bytes 03-build_abe-binutils/console.log.xz | Bin 27448 -> 27376 bytes 04-build_kernel_llvm/console.log.xz | Bin 66644 -> 67464 bytes 05-build_abe-qemu/console.log.xz | Bin 32900 -> 31672 bytes 06-build_linux/console.log.xz | Bin 3120 -> 3104 bytes 07-boot_linux/console.log.xz | Bin 6136 -> 6104 bytes 08-check_regression/console.log.xz | Bin 4228 -> 3808 bytes 08-check_regression/mail-body.txt | 31 ------------------------------- 08-check_regression/mail-subject.txt | 1 - 09-update_baseline/console.log | 9 --------- dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/llvm_rev | 2 +- git/qemu_rev | 2 +- mail/changes-list-long.txt | 20 ++++++++++++++++++++ mail/changes-list-short.txt | 1 + mail/mail-body.txt | 31 ------------------------------- mail/mail-subject.txt | 1 - mail/short-diag.txt | 1 + manifest.sh | 28 ++++++++++++++-------------- 21 files changed, 40 insertions(+), 91 deletions(-) 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/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, 8 months

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

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. tcwg-buildslave pushed a change to branch linaro-local/ci/tcwg_bmk-code_speed-spec2k6/gnu-aarch64-master-O2_LTO in repository toolchain/ci/base-artifacts. from d5c18511674 86: onsuccess: #11: 1: [TCWG CI] No change after binutils/g [...] new e2187bf2743 87: onsuccess: #12: 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 2324 -> 2064 bytes 02-prepare_abe/console.log.xz | Bin 2560 -> 2564 bytes 03-build_abe-binutils/console.log.xz | Bin 27396 -> 27924 bytes 04-build_abe-stage1/console.log.xz | Bin 71864 -> 71948 bytes 05-clean_sysroot/console.log.xz | Bin 332 -> 332 bytes 06-build_abe-linux/console.log.xz | Bin 8312 -> 7512 bytes 07-build_abe-glibc/console.log.xz | Bin 242328 -> 242480 bytes 08-build_abe-stage2/console.log.xz | Bin 176752 -> 177248 bytes 09-benchmark/benchmark-build.log | 190 +- 09-benchmark/benchmark.log | 188 +- 09-benchmark/console.log.xz | Bin 4092 -> 4192 bytes 10-check_regression/bmk-specific-variability.csv | 80 +- .../compare-results-vs-first-internal.csv | 78 +- .../compare-results-vs-prev-internal.csv | 80 +- 10-check_regression/console.log.xz | Bin 9804 -> 10180 bytes .../csv-results-vs-first-0/results.csv | 681366 ++++++++--------- .../csv-results-vs-first-0/size.csv | 683686 ++++++++--------- 10-check_regression/csv-results-vs-first-0/sve.csv | 42 +- .../csv-results-vs-first-1/perf.csv | 178 +- .../csv-results-vs-first-1/results.csv | 696086 +++++++++-------- .../csv-results-vs-first-1/size.csv | 698540 +++++++++--------- 10-check_regression/csv-results-vs-first-1/sve.csv | 18914 +- .../csv-results-vs-first-1/vect.csv | 320 +- 10-check_regression/csv-results-vs-prev-0/perf.csv | 179 +- .../csv-results-vs-prev-0/results.csv | 690927 +++++++++-------- 10-check_regression/csv-results-vs-prev-0/size.csv | 693265 ++++++++--------- 10-check_regression/csv-results-vs-prev-0/sve.csv | 19076 +- 10-check_regression/csv-results-vs-prev-0/vect.csv | 284 +- 10-check_regression/csv-results-vs-prev-1/perf.csv | 178 +- .../csv-results-vs-prev-1/results.csv | 696086 +++++++++-------- 10-check_regression/csv-results-vs-prev-1/size.csv | 698540 +++++++++--------- 10-check_regression/csv-results-vs-prev-1/sve.csv | 18914 +- 10-check_regression/csv-results-vs-prev-1/vect.csv | 320 +- .../output-bmk-results/exe.regression | 1 + .../output-bmk-results/exe.regression.diff | 1 + 10-check_regression/results-vs-first-brief.csv | 68 +- 10-check_regression/results-vs-first-full.csv | 192 +- 10-check_regression/results-vs-first-internal.csv | 80 +- 10-check_regression/results-vs-first.csv | 80 +- 10-check_regression/results-vs-first.log | 1714 +- 10-check_regression/results-vs-prev-brief.csv | 68 +- 10-check_regression/results-vs-prev-full.csv | 192 +- 10-check_regression/results-vs-prev-internal.csv | 80 +- 10-check_regression/results-vs-prev.csv | 80 +- 10-check_regression/results-vs-prev.log | 2002 +- dashboard/dashboard-generate.sh | 2 +- .../400.perlbench/results-metadata.json | 14 +- .../400.perlbench/results-metrics.json | 2 +- .../squad-vs-first/401.bzip2/results-metadata.json | 14 +- .../squad-vs-first/403.gcc/results-metadata.json | 14 +- .../410.bwaves/results-metadata.json | 14 +- .../416.gamess/results-metadata.json | 14 +- .../squad-vs-first/429.mcf/results-metadata.json | 14 +- .../squad-vs-first/433.milc/results-metadata.json | 14 +- .../squad-vs-first/433.milc/results-metrics.json | 4 +- .../434.zeusmp/results-metadata.json | 14 +- .../435.gromacs/results-metadata.json | 14 +- .../436.cactusADM/results-metadata.json | 14 +- .../437.leslie3d/results-metadata.json | 14 +- .../squad-vs-first/444.namd/results-metadata.json | 14 +- .../squad-vs-first/445.gobmk/results-metadata.json | 14 +- .../squad-vs-first/445.gobmk/results-metrics.json | 2 +- .../447.dealII/results-metadata.json | 14 +- .../450.soplex/results-metadata.json | 14 +- .../453.povray/results-metadata.json | 14 +- .../squad-vs-first/453.povray/results-metrics.json | 4 +- .../454.calculix/results-metadata.json | 14 +- .../squad-vs-first/456.hmmer/results-metadata.json | 14 +- .../squad-vs-first/456.hmmer/results-metrics.json | 2 +- .../squad-vs-first/458.sjeng/results-metadata.json | 14 +- .../459.GemsFDTD/results-metadata.json | 14 +- .../459.GemsFDTD/results-metrics.json | 4 +- .../462.libquantum/results-metadata.json | 14 +- .../462.libquantum/results-metrics.json | 2 +- .../464.h264ref/results-metadata.json | 14 +- .../squad-vs-first/465.tonto/results-metadata.json | 14 +- .../squad-vs-first/470.lbm/results-metadata.json | 14 +- .../471.omnetpp/results-metadata.json | 14 +- .../471.omnetpp/results-metrics.json | 2 +- .../squad-vs-first/473.astar/results-metadata.json | 14 +- .../squad-vs-first/473.astar/results-metrics.json | 2 +- .../squad-vs-first/481.wrf/results-metadata.json | 14 +- .../squad-vs-first/481.wrf/results-metrics.json | 4 +- .../482.sphinx3/results-metadata.json | 14 +- .../483.xalancbmk/results-metadata.json | 14 +- .../squad-vs-first/Mean/results-metadata.json | 14 +- dashboard/squad-vs-first/dashboard-push-squad.sh | 122 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- git/glibc_rev | 2 +- mail/changes-list-long.txt | 20 + mail/changes-list-short.txt | 1 + mail/mail-body.txt | 31 - mail/mail-subject.txt | 1 - mail/short-diag.txt | 1 + manifest.sh | 32 +- results_id | 2 +- 97 files changed, 2777119 insertions(+), 2825622 deletions(-) create mode 100644 10-check_regression/output-bmk-results/exe.regression create mode 100644 10-check_regression/output-bmk-results/exe.regression.diff create mode 100644 mail/changes-list-long.txt create mode 100644 mail/changes-list-short.txt 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, 8 months

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_gcc_bootstrap/master-arm-bootstrap_profiled_lto updated (8943003d70e -> 7cc2cd3ec09)

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-arm-bootstrap_profiled_lto in repository toolchain/ci/base-artifacts. discards 8943003d70e 195: onsuccess: #35: 2: Success after binutils/gcc: 5 commits discards ceb9e370e3b 194: onsuccess: #34: 2: Success after binutils/gcc: 45 commits discards a9a4b394ab7 193: onsuccess: #32: 2: Success after binutils/gcc: 42 commits discards 7fa180bf5f6 192: onsuccess: #31: 2: Success after binutils/gcc: 25 commits discards 511f0112e87 191: onsuccess: #30: 2: Success after binutils/gcc: 42 commits discards 9d13b90a4d0 190: onsuccess: #29: 2: Success after binutils/gcc: 27 commits discards 582c7bf4499 189: onsuccess: #28: 2: Success after binutils/gcc: 32 commits discards e4514ad51b9 188: onsuccess: #27: 2: Success after binutils/gcc: 63 commits discards e0bcfccaca8 187: onsuccess: #25: 2: Success after binutils/gcc: 34 commits discards 650b668dfca 186: onsuccess: #24: 2: Success after binutils/gcc: 41 commits discards 1c88552078f 185: onsuccess: #23: 2: Success after binutils/gcc: 61 commits discards efe74190b8b 184: onsuccess: #22: 2: Success after binutils/gcc: 34 commits discards 80ec32eac7b 183: onsuccess: #21: 2: Success after binutils/gcc: 11 commits discards 2e382df4350 182: onsuccess: #20: 2: Success after binutils/gcc: 27 commits discards 86e93b5b94b 181: onsuccess: #19: 2: Success after binutils/gcc: 51 commits discards a8a92d3d52d 180: onsuccess: #18: 2: Success after binutils/gcc: 26 commits discards 7041fa8b92a 179: onsuccess: #17: 2: Success after binutils/gcc: 56 commits discards 3089b042e0a 178: onsuccess: #16: 0: Success after binutils: 15 commits discards 4ee57dd3081 177: force: #15: 0: Failure after gdb-13-branchpoint-1318-g [...] discards 691eca549c8 176: force: #14: 2: Success after binutils: 18 commits discards 9a50d397f82 175: onsuccess: #12: 2: Success after binutils/gcc: 34 commits discards 1707944a67a 174: onsuccess: #11: 2: Success after binutils/gcc: 10 commits discards 8402a3d2293 173: onsuccess: #10: 2: Success after binutils/gcc: 29 commits discards bc6553abd87 172: onsuccess: #9: 2: Success after binutils/gcc: 48 commits discards 1c911a3af9f 171: onsuccess: #8: 2: Success after binutils/gcc: 36 commits discards 16bb90389ce 170: onsuccess: #7: 2: Success after binutils/gcc: 23 commits discards 91d236c15cb 169: onsuccess: #6: 2: Success after binutils/gcc: 66 commits discards 955d33323da 168: onsuccess: #5: 2: Success after binutils/gcc: 22 commits discards 771e605e6f6 167: onsuccess: #4: 2: Success after binutils/gcc: 8 commits discards fbd90925176 166: onsuccess: #3: 2: Success after binutils/gcc: 4 commits discards f38d8267500 165: onsuccess: #2: 2: Success after binutils/gcc: 38 commits discards a59409a1f5b 164: onsuccess: #1: 2: Success after binutils/gcc: 23 commits discards 3c504ea4773 163: onsuccess: #593: 2: Success after binutils/gcc: 48 commits discards f049f5b3e3b 162: onsuccess: #592: 2: Success after binutils/gcc: 139 commits discards 65f2b0e3ffe 161: onsuccess: #591: 2: Success after binutils/gcc: 271 commits discards 80219dfb92b 160: onsuccess: #585: 2: Success after binutils/gcc: 36 commits discards 570a8bb5637 159: onsuccess: #584: 2: Success after binutils/gcc: 87 commits discards b4e91e61a59 158: onsuccess: #583: 2: Success after binutils/gcc: 146 commits discards 00656e7cfd1 157: onsuccess: #582: 2: Success after binutils/gcc: 68 commits discards 769bea0fa4d 156: onsuccess: #581: 2: Success after binutils/gcc: 45 commits discards 10fc2590012 155: onsuccess: #579: 2: Success after binutils/gcc: 35 commits discards eac217d5caf 154: onsuccess: #578: 2: Success after binutils/gcc: 32 commits discards 04bffc1bd83 153: onsuccess: #577: 2: Success after binutils/gcc: 8 commits discards 2f78b7e2f3d 152: onsuccess: #576: 2: Success after binutils/gcc: 9 commits discards 762720c1ede 151: onsuccess: #575: 2: Success after binutils/gcc: 49 commits discards 78532e6cfe8 150: onsuccess: #574: 2: Success after binutils/gcc: 51 commits discards a3887b0901a 149: onsuccess: #573: 2: Success after binutils/gcc: 178 commits discards e9eae46d380 148: onsuccess: #571: 2: Success after gcc: 4 commits discards f1c9d3e2e70 147: onsuccess: #570: 2: Success after binutils/gcc: 24 commits discards 0f7fd906c7e 146: onsuccess: #569: 2: Success after binutils/gcc: 157 commits discards c0caa411a91 145: onsuccess: #568: 2: Success after binutils/gcc: 72 commits discards 3ae5b24e802 144: onsuccess: #567: 2: Success after binutils/gcc: 36 commits discards 9a4091a75b8 143: onsuccess: #566: 2: Success after binutils/gcc: 41 commits discards 59cb0a6ace1 142: onsuccess: #565: 2: Success after binutils/gcc: 4 commits discards 513d29e5647 141: onsuccess: #564: 2: Success after binutils/gcc: 23 commits discards 27cfea595fb 140: onsuccess: #563: 2: Success after binutils/gcc: 40 commits discards 710cccd7423 139: onsuccess: #562: 2: Success after binutils/gcc: 73 commits discards db6be31af4a 138: onsuccess: #560: 2: Success after binutils/gcc: 74 commits discards cb448def27b 137: onsuccess: #559: 2: Success after binutils/gcc: 128 commits discards 234c0bc02f3 136: onsuccess: #558: 2: Success after binutils/gcc: 41 commits discards c9d7af4d3da 135: onsuccess: #557: 2: Success after binutils/gcc: 52 commits discards e43fe6d3ab0 134: onsuccess: #556: 2: Success after binutils/gcc: 106 commits discards 438b2fd941d 133: onsuccess: #552: 2: Success after binutils/gcc: 6 commits discards bc219e4ba09 132: onsuccess: #551: 2: Success after binutils/gcc: 79 commits discards 54da221eb03 131: onsuccess: #547: 2: Success after binutils/gcc: 37 commits discards 93d7322279a 130: onsuccess: #546: 2: Success after binutils/gcc: 51 commits discards 97bcbf792ba 129: onsuccess: #545: 2: Success after binutils/gcc: 30 commits discards c295d743245 128: onsuccess: #544: 2: Success after binutils/gcc: 18 commits discards ea11605040c 127: onsuccess: #543: 2: Success after binutils/gcc: 18 commits discards 05db4598173 126: onsuccess: #542: 2: Success after binutils/gcc: 11 commits discards a76f394041c 125: onsuccess: #541: 2: Success after binutils/gcc: 20 commits discards 303a3b5e914 124: onsuccess: #540: 2: Success after binutils/gcc: 9 commits discards 2cb5b552eb4 123: onsuccess: #539: 2: Success after binutils/gcc: 29 commits discards 48cef57b91b 122: onsuccess: #538: 2: Success after binutils/gcc: 6 commits discards 4d97a6893d3 121: onsuccess: #537: 2: Success after binutils/gcc: 24 commits discards 86e7bb65a0c 120: onsuccess: #536: 2: Success after binutils/gcc: 9 commits discards 38e7bba1a08 119: onsuccess: #535: 2: Success after binutils/gcc: 74 commits discards 7bfb92216fb 118: onsuccess: #534: 2: Success after binutils/gcc: 58 commits discards f7ed9baf76e 117: onsuccess: #533: 2: Success after binutils/gcc: 81 commits discards f8cd62a49e4 116: onsuccess: #531: 2: Success after binutils/gcc: 55 commits discards 73222d3a48e 115: onsuccess: #530: 2: Success after binutils/gcc: 9 commits discards 8879847b7ed 114: onsuccess: #529: 2: Success after binutils/gcc: 4 commits discards b77399e6c76 113: onsuccess: #528: 2: Success after binutils/gcc: 187 commits discards 86b801d6332 112: onsuccess: #527: 1: Success after binutils: 10 commits discards 6482e4e46ac 111: force: #526: 1: Failure after binutils: 5 commits discards 6cb7bcb95f4 110: onsuccess: #520: 2: Success after binutils/gcc: 47 commits discards d712caf6c08 109: onsuccess: #519: 2: Success after binutils/gcc: 12 commits discards ef07f257616 108: onsuccess: #518: 2: Success after binutils/gcc: 3 commits discards e701bf27dde 107: onsuccess: #517: 2: Success after binutils/gcc: 64 commits discards 5a3b0628674 106: onsuccess: #516: 2: Success after binutils/gcc: 27 commits discards a3795ff2282 105: onsuccess: #515: 2: Success after binutils/gcc: 94 commits discards 77c2a4d22c8 104: onsuccess: #513: 2: Success after binutils/gcc: 6 commits discards cde08faeabe 103: onsuccess: #512: 2: Success after binutils/gcc: 126 commits discards 7310c434a10 102: onsuccess: #511: 2: Success after binutils/gcc: 25 commits discards f86d50bbb5c 101: onsuccess: #510: 2: Success after binutils/gcc: 117 commits discards 20dc7f3890b 100: onsuccess: #509: 1: Success after binutils/gcc: 7 commits discards 303a714426c 99: onsuccess: #508: 1: Success after binutils/gcc: 7 commits discards 0ec727a0f43 98: onsuccess: #507: 1: Success after binutils/gcc: 94 commits discards cbbd891a1b8 97: onsuccess: #506: 1: Success after gcc: 27 commits discards bd811ea1b56 96: force: #505: 1: Success after basepoints/gcc-13-4227-g0 [...] discards 42e7c8c13a6 95: force: #504: 1: Failure after gcc: 4 commits new 00fe7d3d06e 95: force: #504: 1: Failure after gcc: 4 commits new 03e03f253dc 96: force: #505: 1: Success after basepoints/gcc-13-4227-g0 [...] new 75a69e4e1cf 97: onsuccess: #506: 1: Success after gcc: 27 commits new 573c112525c 98: onsuccess: #507: 1: Success after binutils/gcc: 94 commits new 0131550eec9 99: onsuccess: #508: 1: Success after binutils/gcc: 7 commits new 42bac608c21 100: onsuccess: #509: 1: Success after binutils/gcc: 7 commits new ae34fb53b75 101: onsuccess: #510: 2: Success after binutils/gcc: 117 commits new 3a5a5212d81 102: onsuccess: #511: 2: Success after binutils/gcc: 25 commits new e6019abda2f 103: onsuccess: #512: 2: Success after binutils/gcc: 126 commits new 091dd53e4e6 104: onsuccess: #513: 2: Success after binutils/gcc: 6 commits new c0459d0caf2 105: onsuccess: #515: 2: Success after binutils/gcc: 94 commits new f05bf719a34 106: onsuccess: #516: 2: Success after binutils/gcc: 27 commits new 59f7f909f43 107: onsuccess: #517: 2: Success after binutils/gcc: 64 commits new dc6aa2489f7 108: onsuccess: #518: 2: Success after binutils/gcc: 3 commits new 8bf3c1132d1 109: onsuccess: #519: 2: Success after binutils/gcc: 12 commits new 84eacc63aae 110: onsuccess: #520: 2: Success after binutils/gcc: 47 commits new 0dc0911d2cd 111: force: #526: 1: Failure after binutils: 5 commits new 9c92f51d4db 112: onsuccess: #527: 1: Success after binutils: 10 commits new a3664132c56 113: onsuccess: #528: 2: Success after binutils/gcc: 187 commits new 2f2a8247757 114: onsuccess: #529: 2: Success after binutils/gcc: 4 commits new 5530f6d221b 115: onsuccess: #530: 2: Success after binutils/gcc: 9 commits new 49d90f2a7ac 116: onsuccess: #531: 2: Success after binutils/gcc: 55 commits new a19e6dcea97 117: onsuccess: #533: 2: Success after binutils/gcc: 81 commits new 8fe573d65b7 118: onsuccess: #534: 2: Success after binutils/gcc: 58 commits new 96944a03a72 119: onsuccess: #535: 2: Success after binutils/gcc: 74 commits new f3e51ef70e8 120: onsuccess: #536: 2: Success after binutils/gcc: 9 commits new 36e3371aedb 121: onsuccess: #537: 2: Success after binutils/gcc: 24 commits new d811bb536a5 122: onsuccess: #538: 2: Success after binutils/gcc: 6 commits new 24ba2d0ab85 123: onsuccess: #539: 2: Success after binutils/gcc: 29 commits new 401e8602c8d 124: onsuccess: #540: 2: Success after binutils/gcc: 9 commits new 3b6e12dec3f 125: onsuccess: #541: 2: Success after binutils/gcc: 20 commits new e145e2da0dc 126: onsuccess: #542: 2: Success after binutils/gcc: 11 commits new 69535ed7d50 127: onsuccess: #543: 2: Success after binutils/gcc: 18 commits new 15bffa126af 128: onsuccess: #544: 2: Success after binutils/gcc: 18 commits new dbc8ccaf684 129: onsuccess: #545: 2: Success after binutils/gcc: 30 commits new 86fbdc31aa8 130: onsuccess: #546: 2: Success after binutils/gcc: 51 commits new ee66cc20095 131: onsuccess: #547: 2: Success after binutils/gcc: 37 commits new 7e144ddc23e 132: onsuccess: #551: 2: Success after binutils/gcc: 79 commits new 36c658ced91 133: onsuccess: #552: 2: Success after binutils/gcc: 6 commits new 1c0db19cb12 134: onsuccess: #556: 2: Success after binutils/gcc: 106 commits new b89ce39d5fd 135: onsuccess: #557: 2: Success after binutils/gcc: 52 commits new c4933c629a2 136: onsuccess: #558: 2: Success after binutils/gcc: 41 commits new a571c30c8e7 137: onsuccess: #559: 2: Success after binutils/gcc: 128 commits new 68526689a6e 138: onsuccess: #560: 2: Success after binutils/gcc: 74 commits new 569435a016b 139: onsuccess: #562: 2: Success after binutils/gcc: 73 commits new f6bd6755efe 140: onsuccess: #563: 2: Success after binutils/gcc: 40 commits new ff4b84d61c7 141: onsuccess: #564: 2: Success after binutils/gcc: 23 commits new c4a2120fe22 142: onsuccess: #565: 2: Success after binutils/gcc: 4 commits new 06eeba03b33 143: onsuccess: #566: 2: Success after binutils/gcc: 41 commits new b07cf89ba32 144: onsuccess: #567: 2: Success after binutils/gcc: 36 commits new 7c4d8ba1846 145: onsuccess: #568: 2: Success after binutils/gcc: 72 commits new cfd89284c9d 146: onsuccess: #569: 2: Success after binutils/gcc: 157 commits new a8231a8572c 147: onsuccess: #570: 2: Success after binutils/gcc: 24 commits new d6c5e8aa35f 148: onsuccess: #571: 2: Success after gcc: 4 commits new 6492ea93204 149: onsuccess: #573: 2: Success after binutils/gcc: 178 commits new 7442ce394e1 150: onsuccess: #574: 2: Success after binutils/gcc: 51 commits new 9ee016eaa04 151: onsuccess: #575: 2: Success after binutils/gcc: 49 commits new 6dcfbded34d 152: onsuccess: #576: 2: Success after binutils/gcc: 9 commits new 205fc8ef49f 153: onsuccess: #577: 2: Success after binutils/gcc: 8 commits new e8186dd3897 154: onsuccess: #578: 2: Success after binutils/gcc: 32 commits new bc56f5d611b 155: onsuccess: #579: 2: Success after binutils/gcc: 35 commits new 140e1869bf4 156: onsuccess: #581: 2: Success after binutils/gcc: 45 commits new 5cd97e5425e 157: onsuccess: #582: 2: Success after binutils/gcc: 68 commits new c98324b7ea1 158: onsuccess: #583: 2: Success after binutils/gcc: 146 commits new e49be243266 159: onsuccess: #584: 2: Success after binutils/gcc: 87 commits new 7e483b4bdb6 160: onsuccess: #585: 2: Success after binutils/gcc: 36 commits new 657d997e221 161: onsuccess: #591: 2: Success after binutils/gcc: 271 commits new 53778c5f21e 162: onsuccess: #592: 2: Success after binutils/gcc: 139 commits new 76ba6596d4e 163: onsuccess: #593: 2: Success after binutils/gcc: 48 commits new a6674a06679 164: onsuccess: #1: 2: Success after binutils/gcc: 23 commits new 0f5e9dbdbb8 165: onsuccess: #2: 2: Success after binutils/gcc: 38 commits new e08a92bf07c 166: onsuccess: #3: 2: Success after binutils/gcc: 4 commits new 3c481ed9699 167: onsuccess: #4: 2: Success after binutils/gcc: 8 commits new 73c69e06b3c 168: onsuccess: #5: 2: Success after binutils/gcc: 22 commits new bfc71ddada6 169: onsuccess: #6: 2: Success after binutils/gcc: 66 commits new 68479777947 170: onsuccess: #7: 2: Success after binutils/gcc: 23 commits new 89eeb6989a4 171: onsuccess: #8: 2: Success after binutils/gcc: 36 commits new 923d46712d0 172: onsuccess: #9: 2: Success after binutils/gcc: 48 commits new d7b23d237e3 173: onsuccess: #10: 2: Success after binutils/gcc: 29 commits new f1642187bfe 174: onsuccess: #11: 2: Success after binutils/gcc: 10 commits new 44b9f3ef190 175: onsuccess: #12: 2: Success after binutils/gcc: 34 commits new 6d5f20ad15c 176: force: #14: 2: Success after binutils: 18 commits new 981611fda15 177: force: #15: 0: Failure after gdb-13-branchpoint-1318-g [...] new f60fdf1e61c 178: onsuccess: #16: 0: Success after binutils: 15 commits new 115d38bf642 179: onsuccess: #17: 2: Success after binutils/gcc: 56 commits new 458157d7530 180: onsuccess: #18: 2: Success after binutils/gcc: 26 commits new e19a69d3891 181: onsuccess: #19: 2: Success after binutils/gcc: 51 commits new 5a37638b0bf 182: onsuccess: #20: 2: Success after binutils/gcc: 27 commits new 686a4f8ce26 183: onsuccess: #21: 2: Success after binutils/gcc: 11 commits new dd920a9f1d5 184: onsuccess: #22: 2: Success after binutils/gcc: 34 commits new 58e501c4ff6 185: onsuccess: #23: 2: Success after binutils/gcc: 61 commits new 15047f06693 186: onsuccess: #24: 2: Success after binutils/gcc: 41 commits new e5e8a65a889 187: onsuccess: #25: 2: Success after binutils/gcc: 34 commits new d766bc3c828 188: onsuccess: #27: 2: Success after binutils/gcc: 63 commits new 214dbb78a99 189: onsuccess: #28: 2: Success after binutils/gcc: 32 commits new 52064302b5b 190: onsuccess: #29: 2: Success after binutils/gcc: 27 commits new 9123d298f82 191: onsuccess: #30: 2: Success after binutils/gcc: 42 commits new b97ef006dc0 192: onsuccess: #31: 2: Success after binutils/gcc: 25 commits new cf0a66c97a3 193: onsuccess: #32: 2: Success after binutils/gcc: 42 commits new 41b42f50d91 194: onsuccess: #34: 2: Success after binutils/gcc: 45 commits new 21b747cd0a6 195: onsuccess: #35: 2: Success after binutils/gcc: 5 commits new 7cc2cd3ec09 196: onsuccess: #38: 2: [TCWG CI] Success after binutils: 5 [...] 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 (8943003d70e) \ N -- N -- N refs/heads/linaro-local/ci/tcwg_gcc_bootstrap/master-arm [...] 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 1904 -> 1928 bytes 02-prepare_abe/console.log.xz | Bin 2512 -> 2520 bytes 04-build_abe-binutils/console.log.xz | Bin 49220 -> 49496 bytes 05-build_abe-bootstrap_profiled_lto/console.log.xz | Bin 607640 -> 609264 bytes 06-check_regression/console.log.xz | Bin 2688 -> 2528 bytes 06-check_regression/mail-body.txt | 19 ----------- 06-check_regression/mail-subject.txt | 1 - 07-update_baseline/console.log | 38 ++++++++++----------- dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- mail/changes-list-long.txt | 8 +++++ mail/changes-list-short.txt | 1 + mail/mail-body.txt | 19 ----------- mail/mail-subject.txt | 1 - mail/short-diag.txt | 1 + manifest.sh | 19 +++++------ 16 files changed, 40 insertions(+), 71 deletions(-) delete mode 100644 06-check_regression/mail-body.txt delete mode 100644 06-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/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, 8 months

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_gnu_native_check_gcc/master-arm updated (51a972b909e -> d1cc93aa0b1)

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 51a972b909e 232: onsuccess: #32: 1: Success after binutils/gcc/linux/gl [...] discards f99d31b4e81 231: onsuccess: #31: 1: Success after binutils/gcc/linux/gd [...] discards 1fd91ef65f6 230: onsuccess: #30: 1: Success after binutils/gcc/linux/gd [...] discards a2388eb7e2e 229: onsuccess: #29: 1: Success after binutils/gcc/linux/gd [...] discards a583cd7badc 228: onsuccess: #28: 1: Success after binutils/gcc/linux/gl [...] discards ac3a413b437 227: onsuccess: #27: 1: Success after binutils/gcc/linux/gd [...] discards 38e6b467401 226: onsuccess: #26: 1: Success after binutils/gcc/linux/gd [...] discards 66c15f9f90d 225: onsuccess: #25: 1: Success after binutils/gcc/linux/gd [...] discards ee94ac9fa73 224: onsuccess: #21: 1: Success after binutils/gcc/linux/gl [...] discards f7559731074 223: onsuccess: #20: 1: Success after binutils/gcc/linux/gl [...] discards 41add5933e9 222: onsuccess: #19: 1: Success after binutils/gcc/linux/gl [...] discards 1704156cf3b 221: onsuccess: #18: 1: Success after binutils/gcc/linux/gd [...] discards fd1a27dfbce 220: onsuccess: #17: 1: Success after binutils/gcc/linux/gl [...] discards 652fc17cae3 219: onsuccess: #16: 1: Success after binutils/gcc/linux/gl [...] discards 58eae4eaade 218: onsuccess: #15: 1: Success after binutils/gcc/linux/gl [...] discards 87e8d7e51dc 217: onsuccess: #14: 1: Success after binutils/gcc/linux/gl [...] discards 6c41fcca33f 216: onsuccess: #12: 1: Success after binutils/gcc/linux/gl [...] discards dfd4ac17a8f 215: onsuccess: #11: 1: Success after binutils/gcc/linux/gd [...] discards fafc7fb7ab8 214: onsuccess: #10: 1: Success after binutils/gcc/linux/gd [...] discards ea53126a411 213: onsuccess: #9: 1: Success after binutils/gcc/linux/gli [...] discards 10c023d0dc4 212: onsuccess: #8: 1: Success after binutils/gcc/linux/gli [...] discards 0c1788a129d 211: onsuccess: #7: 1: Success after binutils/gcc/linux/gdb [...] discards 1d760e24c13 210: onsuccess: #6: 1: Success after binutils/gcc/linux/gli [...] discards 0c72c8034ab 209: onsuccess: #5: 1: Success after binutils/gcc/linux/gli [...] discards ad3f6b39b1d 208: onsuccess: #4: 1: Success after binutils/gcc/linux/gli [...] discards 19318008900 207: onsuccess: #3: 1: Success after binutils/gcc/linux/gdb [...] discards fb9f4f8db0d 206: onsuccess: #2: 1: Success after binutils/gcc/linux/gli [...] discards 4d90a52af5b 205: onsuccess: #1: 1: Success after binutils/gcc/linux/gli [...] discards 59efc369950 204: onsuccess: #672: 1: Success after binutils/gcc/linux/g [...] discards a3958af5cb9 203: onsuccess: #671: 1: Success after binutils/gcc/linux/g [...] discards c358dff2f68 202: onsuccess: #670: 1: Success after binutils/gcc/linux/g [...] discards a104cd1fd66 201: onsuccess: #664: 1: Success after binutils/gcc/glibc/g [...] discards c1f00113ae8 200: onsuccess: #663: 1: Success after binutils/gcc/linux/g [...] discards d426a0135cf 199: onsuccess: #662: 1: Success after binutils/gcc/linux/g [...] discards 4c2cdf2f864 198: onsuccess: #661: 1: Success after binutils/gcc/linux/g [...] discards abc365060de 197: onsuccess: #660: 1: Success after binutils/gcc/linux/g [...] discards b750d29696f 196: onsuccess: #659: 1: Success after binutils/gcc/linux/g [...] discards 4034a70b6ef 195: onsuccess: #657: 1: Success after binutils/gcc/linux/g [...] discards aa528a7d455 194: onsuccess: #656: 1: Success after binutils/gcc/linux/g [...] discards 8399344feab 193: onsuccess: #655: 1: Success after binutils/gcc/linux/g [...] discards 506a3731a0a 192: onsuccess: #654: 1: Success after binutils/gcc/linux/g [...] discards 3486f56e541 191: onsuccess: #653: 1: Success after binutils/gcc/linux/g [...] discards 28e0068aa1f 190: onsuccess: #652: 1: Success after binutils/gcc/linux/g [...] discards ca8075cdb4e 189: onsuccess: #651: 1: Success after binutils/gcc/linux/g [...] discards 5a8fe8cd6b8 188: onsuccess: #650: 1: Success after binutils/gcc/linux/g [...] discards 28764d7b257 187: onsuccess: #649: 1: Success after binutils/gcc/linux/g [...] discards 8e64d047f52 186: onsuccess: #648: 1: Success after binutils/gcc/linux/g [...] discards 0d4665e70ce 185: onsuccess: #647: 1: Success after binutils/gcc/linux/g [...] discards fe311ed58a1 184: onsuccess: #646: 1: Success after binutils/gcc/linux/g [...] discards b77a5282568 183: onsuccess: #645: 1: Success after binutils/gcc/gdb: 20 [...] discards 015bfd31506 182: onsuccess: #644: 1: Success after binutils/gcc/gdb: 30 [...] discards 5d68cef8b15 181: onsuccess: #643: 1: Success after binutils/gcc/linux/g [...] discards 6ce8156d157 180: onsuccess: #642: 1: Success after binutils/gcc/linux/g [...] discards 0d1a749ad2b 179: onsuccess: #641: 1: Success after binutils/gcc/linux/g [...] discards ce65531a2a5 178: onsuccess: #640: 1: Success after binutils/gcc/linux/g [...] discards 996f697651b 177: onsuccess: #639: 1: Success after binutils/gcc/linux/g [...] discards bd9feb8397e 176: onsuccess: #638: 1: Success after binutils/gcc/linux/g [...] discards 624278eac29 175: onsuccess: #637: 1: Success after binutils/gcc/linux/g [...] discards f250b5492a1 174: onsuccess: #636: 1: Success after binutils/gcc/linux/g [...] discards 16809b6b5a5 173: onsuccess: #635: 1: Success after binutils/gcc/linux/g [...] discards 1140fcefee2 172: onsuccess: #634: 1: Success after binutils/gcc/linux/g [...] discards 3a2507abbba 171: onsuccess: #633: 1: Success after binutils/gcc/linux/g [...] discards 5560623183d 170: onsuccess: #632: 1: Success after binutils/gcc/linux/g [...] discards 91a7e759947 169: onsuccess: #631: 1: Success after binutils/gcc/linux/g [...] discards 86e883c9b4c 168: onsuccess: #630: 1: Success after binutils/gcc/linux/g [...] discards df867b1f874 167: onsuccess: #629: 1: Success after binutils/gcc/linux/g [...] discards 81288b36abf 166: onsuccess: #628: 1: Success after binutils/gcc/linux/g [...] discards c2b6c56c502 165: onsuccess: #627: 1: Success after binutils/gcc/linux/g [...] discards 644930f8b05 164: onsuccess: #626: 1: Success after binutils/gcc/linux/g [...] discards f89d6a1fb9c 163: onsuccess: #625: 1: Success after binutils/gcc/glibc/g [...] discards 1d629ddade2 162: onsuccess: #624: 1: Success after linux: 10 commits discards c7e463c6c41 161: onsuccess: #623: 1: Success after glibc: 9 commits discards 6a77f9bfd93 160: onsuccess: #621: 1: Success after gcc: 11 commits discards 418af3d6e92 159: onsuccess: #620: 1: Success after binutils: 12 commits discards 964e4dbf3a6 158: onsuccess: #618: 1: Success after binutils/gcc/linux/g [...] discards d87ed2c1368 157: onsuccess: #617: 1: Success after binutils/gcc/linux/g [...] discards 2753396fcb5 156: onsuccess: #616: 1: Success after binutils/gcc/linux/g [...] discards 0bf00103cb8 155: onsuccess: #615: 1: Success after binutils/gcc/linux/g [...] discards a76a2502ffd 154: onsuccess: #614: 1: Success after binutils/gcc/gdb: 14 [...] discards cfe4bc04532 153: onsuccess: #613: 1: Success after binutils/gcc/gdb: 40 [...] discards 8ecc69b5c27 152: onsuccess: #612: 1: Success after binutils/gcc/gdb: 11 [...] discards b96839d9dbf 151: onsuccess: #611: 1: Success after binutils/gcc/linux/g [...] discards 5f9333596d2 150: onsuccess: #610: 1: Success after binutils/gcc/linux/g [...] discards 2260528e6d8 149: onsuccess: #609: 1: Success after binutils/gcc/linux/g [...] discards 70c3372339f 148: onsuccess: #608: 1: Success after binutils/gcc/linux/g [...] discards 239315a4fb4 147: onsuccess: #607: 1: Success after binutils/gcc/linux/g [...] discards 2baf70be69b 146: onsuccess: #606: 1: Success after binutils/gcc/linux/g [...] discards c4464cf0eaa 145: onsuccess: #605: 1: Success after binutils/gcc/linux/g [...] discards 88ca1afd8c5 144: onsuccess: #604: 1: Success after binutils/gcc/gdb: 14 [...] discards edc1505ca6b 143: onsuccess: #603: 1: Success after binutils/gcc/linux/g [...] discards 62248de7ce4 142: onsuccess: #602: 1: Success after binutils/gcc/linux/g [...] discards 31f367a7be3 141: onsuccess: #601: 1: Success after linux: 794 commits discards 6001724bff2 140: onsuccess: #600: 1: Success after gcc: 23 commits discards 7f4f985a74d 139: onsuccess: #599: 1: Success after binutils: 10 commits discards 538a586d35d 138: onsuccess: #597: 1: Success after binutils/gcc/linux/g [...] discards 58285c6674f 137: onsuccess: #596: 1: Success after binutils/gcc/linux/g [...] discards 59fde2a6b81 136: onsuccess: #595: 1: Success after binutils/gcc/linux/g [...] discards dca42e17443 135: onsuccess: #594: 1: Success after binutils/gcc/linux/g [...] discards 2b9d36dd47b 134: onsuccess: #593: 1: Success after binutils/gcc/linux/g [...] discards 389ab66b08c 133: onsuccess: #592: 1: Success after binutils/gcc/linux/g [...] discards f9fb652881b 132: onsuccess: #591: 1: Success after binutils/gcc/linux/g [...] new 95cc19c8cce 132: onsuccess: #591: 1: Success after binutils/gcc/linux/g [...] new 7800566a28a 133: onsuccess: #592: 1: Success after binutils/gcc/linux/g [...] new bdac2f919c2 134: onsuccess: #593: 1: Success after binutils/gcc/linux/g [...] new 9873c79add7 135: onsuccess: #594: 1: Success after binutils/gcc/linux/g [...] new 85acb4c8562 136: onsuccess: #595: 1: Success after binutils/gcc/linux/g [...] new 9afc8619b27 137: onsuccess: #596: 1: Success after binutils/gcc/linux/g [...] new b548c66124d 138: onsuccess: #597: 1: Success after binutils/gcc/linux/g [...] new 76a16211b94 139: onsuccess: #599: 1: Success after binutils: 10 commits new 6441d3e55da 140: onsuccess: #600: 1: Success after gcc: 23 commits new ea6cd74f4dd 141: onsuccess: #601: 1: Success after linux: 794 commits new 4d1a01a4071 142: onsuccess: #602: 1: Success after binutils/gcc/linux/g [...] new 7c6599d840e 143: onsuccess: #603: 1: Success after binutils/gcc/linux/g [...] new de5b8a82ba6 144: onsuccess: #604: 1: Success after binutils/gcc/gdb: 14 [...] new d21ab754805 145: onsuccess: #605: 1: Success after binutils/gcc/linux/g [...] new 2f9620697ec 146: onsuccess: #606: 1: Success after binutils/gcc/linux/g [...] new 322d4fed547 147: onsuccess: #607: 1: Success after binutils/gcc/linux/g [...] new cb2bc6c39b2 148: onsuccess: #608: 1: Success after binutils/gcc/linux/g [...] new ad8409d436a 149: onsuccess: #609: 1: Success after binutils/gcc/linux/g [...] new 7b9a528a713 150: onsuccess: #610: 1: Success after binutils/gcc/linux/g [...] new 05646a5c7d6 151: onsuccess: #611: 1: Success after binutils/gcc/linux/g [...] new ffb1e254d1e 152: onsuccess: #612: 1: Success after binutils/gcc/gdb: 11 [...] new cc81ed86589 153: onsuccess: #613: 1: Success after binutils/gcc/gdb: 40 [...] new e052323ab50 154: onsuccess: #614: 1: Success after binutils/gcc/gdb: 14 [...] new d9dacf0100e 155: onsuccess: #615: 1: Success after binutils/gcc/linux/g [...] new 423d152dffb 156: onsuccess: #616: 1: Success after binutils/gcc/linux/g [...] new d29b43be1d7 157: onsuccess: #617: 1: Success after binutils/gcc/linux/g [...] new f820cefe1c3 158: onsuccess: #618: 1: Success after binutils/gcc/linux/g [...] new 94a99765540 159: onsuccess: #620: 1: Success after binutils: 12 commits new 8a7171ed535 160: onsuccess: #621: 1: Success after gcc: 11 commits new 46099ba55ff 161: onsuccess: #623: 1: Success after glibc: 9 commits new 6a17c4ff396 162: onsuccess: #624: 1: Success after linux: 10 commits new ebd2e2f4d4c 163: onsuccess: #625: 1: Success after binutils/gcc/glibc/g [...] new 0f06d5dd167 164: onsuccess: #626: 1: Success after binutils/gcc/linux/g [...] new 45a9048a3f0 165: onsuccess: #627: 1: Success after binutils/gcc/linux/g [...] new 94534de5a42 166: onsuccess: #628: 1: Success after binutils/gcc/linux/g [...] new 0cba5c84bae 167: onsuccess: #629: 1: Success after binutils/gcc/linux/g [...] new 0ca65c020b2 168: onsuccess: #630: 1: Success after binutils/gcc/linux/g [...] new 2ba9d6fa81c 169: onsuccess: #631: 1: Success after binutils/gcc/linux/g [...] new 2ae0f2ec205 170: onsuccess: #632: 1: Success after binutils/gcc/linux/g [...] new e93315cb775 171: onsuccess: #633: 1: Success after binutils/gcc/linux/g [...] new 298db8c1178 172: onsuccess: #634: 1: Success after binutils/gcc/linux/g [...] new 09423a865e0 173: onsuccess: #635: 1: Success after binutils/gcc/linux/g [...] new a28dddd5601 174: onsuccess: #636: 1: Success after binutils/gcc/linux/g [...] new 78c5339f345 175: onsuccess: #637: 1: Success after binutils/gcc/linux/g [...] new 7272430cc4f 176: onsuccess: #638: 1: Success after binutils/gcc/linux/g [...] new 4d66d1a8998 177: onsuccess: #639: 1: Success after binutils/gcc/linux/g [...] new 70778682171 178: onsuccess: #640: 1: Success after binutils/gcc/linux/g [...] new 4f4d28a1b4b 179: onsuccess: #641: 1: Success after binutils/gcc/linux/g [...] new 4bc27f92496 180: onsuccess: #642: 1: Success after binutils/gcc/linux/g [...] new e611daa85d6 181: onsuccess: #643: 1: Success after binutils/gcc/linux/g [...] new 4932369b070 182: onsuccess: #644: 1: Success after binutils/gcc/gdb: 30 [...] new fb9ae3d6521 183: onsuccess: #645: 1: Success after binutils/gcc/gdb: 20 [...] new 51e0862fe1e 184: onsuccess: #646: 1: Success after binutils/gcc/linux/g [...] new d0196ddc0a3 185: onsuccess: #647: 1: Success after binutils/gcc/linux/g [...] new 994735cef55 186: onsuccess: #648: 1: Success after binutils/gcc/linux/g [...] new 0575139bf9a 187: onsuccess: #649: 1: Success after binutils/gcc/linux/g [...] new 09cce729a9d 188: onsuccess: #650: 1: Success after binutils/gcc/linux/g [...] new 4e04ba7374f 189: onsuccess: #651: 1: Success after binutils/gcc/linux/g [...] new 2ce7e4b6a12 190: onsuccess: #652: 1: Success after binutils/gcc/linux/g [...] new 2320c935f0f 191: onsuccess: #653: 1: Success after binutils/gcc/linux/g [...] new 2ae60a302f4 192: onsuccess: #654: 1: Success after binutils/gcc/linux/g [...] new 0579e4cb3cb 193: onsuccess: #655: 1: Success after binutils/gcc/linux/g [...] new bcb214c7fc6 194: onsuccess: #656: 1: Success after binutils/gcc/linux/g [...] new 002499e8a73 195: onsuccess: #657: 1: Success after binutils/gcc/linux/g [...] new 95cc3d5467b 196: onsuccess: #659: 1: Success after binutils/gcc/linux/g [...] new d57954f36d8 197: onsuccess: #660: 1: Success after binutils/gcc/linux/g [...] new 9ed6b71f6a7 198: onsuccess: #661: 1: Success after binutils/gcc/linux/g [...] new 58510e71a93 199: onsuccess: #662: 1: Success after binutils/gcc/linux/g [...] new c53cd082335 200: onsuccess: #663: 1: Success after binutils/gcc/linux/g [...] new 5744de6eb0d 201: onsuccess: #664: 1: Success after binutils/gcc/glibc/g [...] new 1faf9fa6a7c 202: onsuccess: #670: 1: Success after binutils/gcc/linux/g [...] new 8eb6e26d2c6 203: onsuccess: #671: 1: Success after binutils/gcc/linux/g [...] new 64bc9c03f7e 204: onsuccess: #672: 1: Success after binutils/gcc/linux/g [...] new 72316afad0c 205: onsuccess: #1: 1: Success after binutils/gcc/linux/gli [...] new d3502d04631 206: onsuccess: #2: 1: Success after binutils/gcc/linux/gli [...] new 98896b558eb 207: onsuccess: #3: 1: Success after binutils/gcc/linux/gdb [...] new 810ffc5750b 208: onsuccess: #4: 1: Success after binutils/gcc/linux/gli [...] new f40bffcd5f0 209: onsuccess: #5: 1: Success after binutils/gcc/linux/gli [...] new 437259df509 210: onsuccess: #6: 1: Success after binutils/gcc/linux/gli [...] new 4b2748380bc 211: onsuccess: #7: 1: Success after binutils/gcc/linux/gdb [...] new 78b1b158406 212: onsuccess: #8: 1: Success after binutils/gcc/linux/gli [...] new 5947675283c 213: onsuccess: #9: 1: Success after binutils/gcc/linux/gli [...] new bca0dc38aec 214: onsuccess: #10: 1: Success after binutils/gcc/linux/gd [...] new 0863b5ffcf6 215: onsuccess: #11: 1: Success after binutils/gcc/linux/gd [...] new 9b1192b49ba 216: onsuccess: #12: 1: Success after binutils/gcc/linux/gl [...] new ac359510777 217: onsuccess: #14: 1: Success after binutils/gcc/linux/gl [...] new da6c97b79a5 218: onsuccess: #15: 1: Success after binutils/gcc/linux/gl [...] new 41be65ac343 219: onsuccess: #16: 1: Success after binutils/gcc/linux/gl [...] new e17e44ed193 220: onsuccess: #17: 1: Success after binutils/gcc/linux/gl [...] new 1974fcea928 221: onsuccess: #18: 1: Success after binutils/gcc/linux/gd [...] new 153a17eb179 222: onsuccess: #19: 1: Success after binutils/gcc/linux/gl [...] new 321b1cc07fe 223: onsuccess: #20: 1: Success after binutils/gcc/linux/gl [...] new db1cec72008 224: onsuccess: #21: 1: Success after binutils/gcc/linux/gl [...] new 14131ed17cc 225: onsuccess: #25: 1: Success after binutils/gcc/linux/gd [...] new 6a136c9d06b 226: onsuccess: #26: 1: Success after binutils/gcc/linux/gd [...] new b75e37b546b 227: onsuccess: #27: 1: Success after binutils/gcc/linux/gd [...] new 86ccc7dfc63 228: onsuccess: #28: 1: Success after binutils/gcc/linux/gl [...] new 29313e56bfc 229: onsuccess: #29: 1: Success after binutils/gcc/linux/gd [...] new b8f017a8a41 230: onsuccess: #30: 1: Success after binutils/gcc/linux/gd [...] new 45eff6ba742 231: onsuccess: #31: 1: Success after binutils/gcc/linux/gd [...] new 283ab35d399 232: onsuccess: #32: 1: Success after binutils/gcc/linux/gl [...] new d1cc93aa0b1 233: onsuccess: #34: 1: [TCWG CI] Success after binutils/gc [...] 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 (51a972b909e) \ 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 2032 -> 2024 bytes 02-prepare_abe/console.log.xz | Bin 2492 -> 2508 bytes 03-build_abe-binutils/console.log.xz | Bin 49508 -> 49268 bytes 04-build_abe-gcc/console.log.xz | Bin 235476 -> 236868 bytes 05-clean_sysroot/console.log.xz | Bin 316 -> 316 bytes 06-build_abe-linux/console.log.xz | Bin 9096 -> 8780 bytes 07-build_abe-glibc/console.log.xz | Bin 232456 -> 232448 bytes 08-build_abe-gdb/console.log.xz | Bin 47112 -> 46708 bytes 09-build_abe-dejagnu/console.log.xz | Bin 3764 -> 3820 bytes 10-build_abe-check_gcc/console.log.xz | Bin 11160 -> 9612 bytes 11-check_regression/console.log.xz | Bin 4608 -> 5836 bytes 11-check_regression/mail-body.txt | 35 - 11-check_regression/mail-subject.txt | 1 - 11-check_regression/results.compare | 26 +- 11-check_regression/results.compare2 | 77 +- 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 | 32 + mail/changes-list-short.txt | 1 + mail/mail-body.txt | 35 - mail/mail-subject.txt | 1 - mail/short-diag.txt | 1 + manifest.sh | 38 +- sumfiles/g++.log.sep.xz | Bin 86148 -> 71732 bytes sumfiles/g++.log.xz | Bin 2889652 -> 2878556 bytes sumfiles/g++.sum | 34 +- sumfiles/g++.sum.sep | 7187 ++++++++++++++++++++++----------- sumfiles/gcc.log.sep.xz | Bin 87928 -> 68272 bytes sumfiles/gcc.log.xz | Bin 2518088 -> 2459744 bytes sumfiles/gcc.sum | 20 +- sumfiles/gcc.sum.sep | 6635 +++++------------------------- sumfiles/gfortran.log.sep.xz | Bin 17384 -> 30176 bytes sumfiles/gfortran.log.xz | Bin 959236 -> 958048 bytes sumfiles/gfortran.sum | 5 +- sumfiles/gfortran.sum.sep | 2526 +++++++----- sumfiles/libatomic.log.xz | Bin 2284 -> 2284 bytes sumfiles/libatomic.sum | 2 +- sumfiles/libgomp.log.xz | Bin 233880 -> 233784 bytes sumfiles/libgomp.sum | 2 +- sumfiles/libitm.log.xz | Bin 2688 -> 2692 bytes sumfiles/libitm.sum | 2 +- sumfiles/libstdc++.log.sep.xz | Bin 6140 -> 17112 bytes sumfiles/libstdc++.log.xz | Bin 481288 -> 468272 bytes sumfiles/libstdc++.sum.sep | 292 +- 49 files changed, 7775 insertions(+), 9257 deletions(-) delete mode 100644 11-check_regression/mail-body.txt delete mode 100644 11-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/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, 8 months

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

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 f64c901f4c3 131: onsuccess: #37: 1: Success after binutils/gcc/linux/gl [...] discards cfd62d8c456 130: onsuccess: #36: 1: Success after binutils/gcc/linux/gd [...] discards 28878b87fd0 129: onsuccess: #35: 1: Success after binutils/gcc/linux/gd [...] discards 9d960cea1bb 128: onsuccess: #34: 1: Success after binutils/gcc/linux/gd [...] discards 8464d592922 127: onsuccess: #33: 1: Success after binutils/gcc/linux/gl [...] discards b1393e358df 126: onsuccess: #32: 1: Success after binutils/gcc/linux/gd [...] discards 363a035607d 125: onsuccess: #31: 1: Success after binutils/gcc/linux/gd [...] discards 8276ab3d7f9 124: onsuccess: #30: 1: Success after binutils/gcc/linux/gd [...] discards 2d1fd746d13 123: onsuccess: #29: 1: Success after binutils/gcc/linux/gd [...] discards 7cd17810b98 122: onsuccess: #28: 1: Success after binutils/gcc/linux/gd [...] discards ac0a62f3723 121: force: #26: : Failure after baseline build: no new commits discards bdeacf83496 120: onsuccess: #19: 1: Success after binutils/gcc/linux/gl [...] discards 07eaba07a61 119: onsuccess: #18: 1: Success after binutils/gcc/linux/gl [...] discards 44cb068010d 118: onsuccess: #17: 1: Success after binutils/gcc/linux/gd [...] discards 73583a00bd6 117: onsuccess: #16: 1: Success after binutils/gcc/linux/gd [...] discards ac88dc028a3 116: onsuccess: #15: 1: Success after binutils/gcc/linux/gl [...] discards 67907a82a4d 115: onsuccess: #14: 1: Success after binutils/gcc/linux/gl [...] discards a2eb30f504f 114: onsuccess: #13: 1: Success after binutils/gcc/linux/gl [...] discards 3e0f808ce68 113: onsuccess: #11: 1: Success after binutils/gcc/linux/gl [...] discards ac65c509fcb 112: onsuccess: #10: 1: Success after binutils/gcc/linux/gd [...] discards 469233c8d93 111: onsuccess: #9: 1: Success after binutils/gcc/linux/gdb [...] discards 335255acbb9 110: onsuccess: #8: 1: Success after binutils/gcc/linux/gli [...] discards 2e63262bb9e 109: onsuccess: #7: 1: Success after binutils/gcc/linux/gli [...] discards 4fbe4186c07 108: onsuccess: #6: 1: Success after binutils/gcc/linux/gdb [...] discards d35299b8155 107: onsuccess: #5: 1: Success after binutils/gcc/linux/gli [...] discards f7d70113383 106: onsuccess: #4: 1: Success after binutils/gcc/linux/gli [...] discards 955fe62214f 105: onsuccess: #3: 1: Success after binutils/gcc/linux/gli [...] discards 9bc65a9e2b3 104: onsuccess: #2: 1: Success after binutils/gcc/linux/gli [...] discards a5257db7559 103: onsuccess: #1: 1: Success after binutils/gcc/linux/gli [...] discards 4d8b53c6aa9 102: onsuccess: #123: 1: Success after binutils/gcc/linux/g [...] discards 6fc3a2c3cc5 101: onsuccess: #122: 1: Success after binutils/gcc/linux/g [...] discards c3a7e8e72c0 100: onsuccess: #121: 1: Success after binutils/gcc/glibc/g [...] discards 157647e71e3 99: onsuccess: #120: 1: Success after binutils/gcc/linux/gl [...] discards 457dccf59e1 98: onsuccess: #108: 1: Success after binutils/gcc/linux/gl [...] discards 1e5f6f920a7 97: onsuccess: #107: 1: Success after binutils/gcc/linux/gl [...] discards 57cf6c5c512 96: onsuccess: #106: 1: Success after binutils/gcc/linux/gl [...] discards 915b3da164c 95: onsuccess: #105: 1: Success after binutils/gcc/linux/gd [...] discards f9484783012 94: onsuccess: #104: 1: Success after binutils/gcc/linux/gl [...] discards 0e0c69ef1e0 93: onsuccess: #103: 1: Success after binutils/gcc/linux/gl [...] discards b8c1c43e9f9 92: onsuccess: #101: 1: Success after binutils/gcc/linux/gl [...] discards ae001d0f266 91: onsuccess: #100: 1: Success after binutils/gcc/linux/gl [...] discards c63caa13d4d 90: onsuccess: #99: 1: Success after binutils/gcc/linux/gdb [...] discards 34d6f3b1365 89: onsuccess: #98: 1: Success after binutils/gcc/linux/gli [...] discards 3bc324dfdaf 88: onsuccess: #97: 1: Success after binutils/gcc/linux/gli [...] discards df1d79cd74f 87: onsuccess: #96: 1: Success after binutils/gcc/linux/gli [...] discards 942acd838fc 86: onsuccess: #95: 1: Success after binutils/gcc/linux/gli [...] discards 98c2fd58bcb 85: onsuccess: #94: 1: Success after binutils/gcc/linux/gli [...] discards 29de1b0d680 84: onsuccess: #93: 1: Success after binutils/gcc/linux/gli [...] discards 85a0cb0bc5f 83: onsuccess: #92: 1: Success after binutils/gcc/linux/gdb [...] discards 2f19d5eef8d 82: onsuccess: #91: 1: Success after binutils/gcc/linux/gdb [...] discards 753a0a22aa9 81: onsuccess: #90: 1: Success after binutils/gcc/linux/gli [...] discards 3dd53f0ae5c 80: onsuccess: #89: 1: Success after binutils/gcc/gdb: 198 commits discards 316039bfb2c 79: onsuccess: #88: 1: Success after binutils/gcc/linux/gdb [...] discards 766006296cb 78: onsuccess: #87: 1: Success after binutils/gcc/linux/gli [...] discards 63f504de5b6 77: onsuccess: #86: 1: Success after binutils/gcc/linux/gli [...] discards 98315b1f4e7 76: onsuccess: #85: 1: Success after binutils/gcc/linux/gdb [...] discards e192ee60281 75: onsuccess: #84: 1: Success after binutils/gcc/linux/gdb [...] discards 2985bc11459 74: onsuccess: #83: 1: Success after binutils/gcc/linux/gdb [...] discards b39f21eb0f0 73: onsuccess: #82: 1: Success after binutils/gcc/linux/gdb [...] discards 5f4bd08221e 72: onsuccess: #81: 1: Success after binutils/gcc/linux/gli [...] discards 6f852a1e2de 71: onsuccess: #80: 1: Success after binutils/gcc/linux/gli [...] discards 84a553107fe 70: onsuccess: #79: 1: Success after binutils/gcc/linux/gli [...] discards a86c6dee708 69: onsuccess: #78: 1: Success after binutils/gcc/linux/gdb [...] discards c5d8712bbda 68: onsuccess: #77: 1: Success after binutils/gcc/linux/gli [...] discards 125d55919de 67: onsuccess: #76: 1: Success after binutils/gcc/linux/gli [...] discards 30355328e44 66: onsuccess: #75: 1: Success after binutils/gcc/gdb: 30 commits discards 72c283d4bf5 65: onsuccess: #74: 1: Success after binutils/gcc/linux/gdb [...] discards a75808e067b 64: onsuccess: #73: 1: Success after binutils/gcc/linux/gli [...] discards 475e053f47a 63: onsuccess: #72: 1: Success after binutils/gcc/linux/gli [...] discards 06339428b13 62: onsuccess: #71: 1: Success after binutils/gcc/linux/gli [...] discards effd588c80e 61: onsuccess: #70: 1: Success after binutils/gcc/glibc/gdb [...] discards 1950dc22a18 60: onsuccess: #69: 1: Success after binutils/gcc/gdb: 103 commits discards 3e7c7f08623 59: onsuccess: #67: 1: Success after binutils/gcc/linux/gli [...] discards 7c04df0347a 58: onsuccess: #65: 1: Success after binutils/gcc/linux/gdb [...] discards 87ed52aa4f2 57: onsuccess: #64: 1: Success after binutils/gcc/linux/gdb [...] discards 7991d914d45 56: onsuccess: #63: 1: Success after binutils/gcc/linux/gli [...] discards 9a3294bec35 55: onsuccess: #62: 1: Success after binutils/gcc/linux/gdb [...] discards e3bd3de71da 54: onsuccess: #61: 1: Success after binutils/gcc/gdb: 14 commits discards fe122f93653 53: onsuccess: #60: 1: Success after binutils/gcc/gdb: 42 commits discards dc47058663e 52: onsuccess: #59: 1: Success after binutils/gcc/linux/gdb [...] discards e2167028ea9 51: onsuccess: #58: 1: Success after binutils/gcc/gdb: 46 commits discards a586b6a7c1b 50: onsuccess: #57: 1: Success after binutils/gcc/linux/gdb [...] discards d03c3a3d64d 49: onsuccess: #56: 1: Success after binutils/gcc/linux/gdb [...] discards 4978299584b 48: onsuccess: #55: 1: Success after binutils/gcc/linux/gli [...] discards 08ec21b8cdf 47: onsuccess: #54: 1: Success after binutils/gcc/linux/gli [...] discards 46304be2a48 46: onsuccess: #53: 1: Success after binutils/gcc/linux/gli [...] discards bb122ffe110 45: onsuccess: #52: 1: Success after binutils/gcc/linux/gli [...] discards 43c6cc68b74 44: onsuccess: #51: 1: Success after binutils/gcc/gdb: 15 commits discards b1f864c0939 43: onsuccess: #50: 1: Success after binutils/gcc/linux/gdb [...] discards 2b7e9102ff2 42: onsuccess: #49: 1: Success after binutils/gcc/linux/gdb [...] discards 661decd8c74 41: onsuccess: #48: 1: Success after binutils/gcc/linux/gli [...] discards 3302a9b1ca9 40: onsuccess: #47: 1: Success after binutils/gcc/linux/gli [...] discards c096e5f04a5 39: onsuccess: #46: 1: Success after binutils/gcc/linux/gdb [...] discards 8e0c12a4f9d 38: onsuccess: #45: 1: Success after binutils/gcc/linux/gli [...] discards c377413b353 37: onsuccess: #44: 1: Success after binutils/gcc/linux/gdb [...] discards 5a1374b2455 36: onsuccess: #43: 1: Success after binutils/gcc/linux/gdb [...] discards 9b2d4ae25d2 35: onsuccess: #42: 1: Success after binutils/gcc/linux/gli [...] discards 055c7bdcf2c 34: onsuccess: #41: 1: Success after binutils/gcc/linux/gli [...] discards f9d9d7544d5 33: onsuccess: #40: 1: Success after binutils/gcc/glibc/gdb [...] discards 0b43e433e02 32: onsuccess: #39: 1: Success after binutils/gcc/linux/gli [...] discards 82818de69cf 31: onsuccess: #38: 1: Success after linux: 14 commits new 2a194d71f7e 31: onsuccess: #38: 1: Success after linux: 14 commits new 4557969e428 32: onsuccess: #39: 1: Success after binutils/gcc/linux/gli [...] new 000d7744215 33: onsuccess: #40: 1: Success after binutils/gcc/glibc/gdb [...] new 0be3f40934c 34: onsuccess: #41: 1: Success after binutils/gcc/linux/gli [...] new a56fbe99fe2 35: onsuccess: #42: 1: Success after binutils/gcc/linux/gli [...] new 4d2209743a6 36: onsuccess: #43: 1: Success after binutils/gcc/linux/gdb [...] new 6da430bfb14 37: onsuccess: #44: 1: Success after binutils/gcc/linux/gdb [...] new dc1d2198c45 38: onsuccess: #45: 1: Success after binutils/gcc/linux/gli [...] new 6c876c22726 39: onsuccess: #46: 1: Success after binutils/gcc/linux/gdb [...] new c1533967497 40: onsuccess: #47: 1: Success after binutils/gcc/linux/gli [...] new 4d3e8d7a465 41: onsuccess: #48: 1: Success after binutils/gcc/linux/gli [...] new 3cbe5651e6c 42: onsuccess: #49: 1: Success after binutils/gcc/linux/gdb [...] new 736ae1ac3b2 43: onsuccess: #50: 1: Success after binutils/gcc/linux/gdb [...] new 1daf02b0283 44: onsuccess: #51: 1: Success after binutils/gcc/gdb: 15 commits new ed2f02077ed 45: onsuccess: #52: 1: Success after binutils/gcc/linux/gli [...] new 66f5baf9cf4 46: onsuccess: #53: 1: Success after binutils/gcc/linux/gli [...] new 32eaa1a8f97 47: onsuccess: #54: 1: Success after binutils/gcc/linux/gli [...] new d481ee693a0 48: onsuccess: #55: 1: Success after binutils/gcc/linux/gli [...] new 2adcf1aae5b 49: onsuccess: #56: 1: Success after binutils/gcc/linux/gdb [...] new aebc850dcbb 50: onsuccess: #57: 1: Success after binutils/gcc/linux/gdb [...] new cba3bc99683 51: onsuccess: #58: 1: Success after binutils/gcc/gdb: 46 commits new 4d656707a1f 52: onsuccess: #59: 1: Success after binutils/gcc/linux/gdb [...] new ef200bc8674 53: onsuccess: #60: 1: Success after binutils/gcc/gdb: 42 commits new 2a6a2f867db 54: onsuccess: #61: 1: Success after binutils/gcc/gdb: 14 commits new b7cbacd1337 55: onsuccess: #62: 1: Success after binutils/gcc/linux/gdb [...] new 56cd0ef8c9e 56: onsuccess: #63: 1: Success after binutils/gcc/linux/gli [...] new 6c1f697b9e4 57: onsuccess: #64: 1: Success after binutils/gcc/linux/gdb [...] new 482699c01b2 58: onsuccess: #65: 1: Success after binutils/gcc/linux/gdb [...] new 5dc12dec343 59: onsuccess: #67: 1: Success after binutils/gcc/linux/gli [...] new cf847c607c2 60: onsuccess: #69: 1: Success after binutils/gcc/gdb: 103 commits new e5a42b6d222 61: onsuccess: #70: 1: Success after binutils/gcc/glibc/gdb [...] new 7e49461c8a9 62: onsuccess: #71: 1: Success after binutils/gcc/linux/gli [...] new b3bdc959c26 63: onsuccess: #72: 1: Success after binutils/gcc/linux/gli [...] new 1790ca4ab0d 64: onsuccess: #73: 1: Success after binutils/gcc/linux/gli [...] new b0d7ee78d5b 65: onsuccess: #74: 1: Success after binutils/gcc/linux/gdb [...] new c8feaf4f0e1 66: onsuccess: #75: 1: Success after binutils/gcc/gdb: 30 commits new 52c46fc2703 67: onsuccess: #76: 1: Success after binutils/gcc/linux/gli [...] new d0c8d0706ec 68: onsuccess: #77: 1: Success after binutils/gcc/linux/gli [...] new 0dfd91cb703 69: onsuccess: #78: 1: Success after binutils/gcc/linux/gdb [...] new 3feab57ff72 70: onsuccess: #79: 1: Success after binutils/gcc/linux/gli [...] new a5c7d9b27cb 71: onsuccess: #80: 1: Success after binutils/gcc/linux/gli [...] new 4a56f3d56f3 72: onsuccess: #81: 1: Success after binutils/gcc/linux/gli [...] new 11d47a7204f 73: onsuccess: #82: 1: Success after binutils/gcc/linux/gdb [...] new 7576fe06766 74: onsuccess: #83: 1: Success after binutils/gcc/linux/gdb [...] new 9cc2dcae95d 75: onsuccess: #84: 1: Success after binutils/gcc/linux/gdb [...] new 1051553765d 76: onsuccess: #85: 1: Success after binutils/gcc/linux/gdb [...] new 9a0dbed0743 77: onsuccess: #86: 1: Success after binutils/gcc/linux/gli [...] new 8b8dad2a0a7 78: onsuccess: #87: 1: Success after binutils/gcc/linux/gli [...] new edab1b6c8ff 79: onsuccess: #88: 1: Success after binutils/gcc/linux/gdb [...] new a289d7cda78 80: onsuccess: #89: 1: Success after binutils/gcc/gdb: 198 commits new cd5121eb18c 81: onsuccess: #90: 1: Success after binutils/gcc/linux/gli [...] new 07e5b69e041 82: onsuccess: #91: 1: Success after binutils/gcc/linux/gdb [...] new 32b74b9e1ba 83: onsuccess: #92: 1: Success after binutils/gcc/linux/gdb [...] new f0664068560 84: onsuccess: #93: 1: Success after binutils/gcc/linux/gli [...] new fdb0406a8c7 85: onsuccess: #94: 1: Success after binutils/gcc/linux/gli [...] new ae0386f12c0 86: onsuccess: #95: 1: Success after binutils/gcc/linux/gli [...] new 9ad2d6f1040 87: onsuccess: #96: 1: Success after binutils/gcc/linux/gli [...] new 0ea294c1a2b 88: onsuccess: #97: 1: Success after binutils/gcc/linux/gli [...] new 20f79b58769 89: onsuccess: #98: 1: Success after binutils/gcc/linux/gli [...] new 138fb685876 90: onsuccess: #99: 1: Success after binutils/gcc/linux/gdb [...] new 1bb55a2c005 91: onsuccess: #100: 1: Success after binutils/gcc/linux/gl [...] new ec030133642 92: onsuccess: #101: 1: Success after binutils/gcc/linux/gl [...] new 0f90e2c3fa5 93: onsuccess: #103: 1: Success after binutils/gcc/linux/gl [...] new 628fe377b6a 94: onsuccess: #104: 1: Success after binutils/gcc/linux/gl [...] new fe7d946b57c 95: onsuccess: #105: 1: Success after binutils/gcc/linux/gd [...] new bd9e8bde1e0 96: onsuccess: #106: 1: Success after binutils/gcc/linux/gl [...] new 4e0b2efee08 97: onsuccess: #107: 1: Success after binutils/gcc/linux/gl [...] new 138b43f2819 98: onsuccess: #108: 1: Success after binutils/gcc/linux/gl [...] new 83d3f93acdb 99: onsuccess: #120: 1: Success after binutils/gcc/linux/gl [...] new d3e0fc5685e 100: onsuccess: #121: 1: Success after binutils/gcc/glibc/g [...] new 3a806223ace 101: onsuccess: #122: 1: Success after binutils/gcc/linux/g [...] new 55e56a0da6a 102: onsuccess: #123: 1: Success after binutils/gcc/linux/g [...] new c9fc24029fe 103: onsuccess: #1: 1: Success after binutils/gcc/linux/gli [...] new 6b8a8afb73c 104: onsuccess: #2: 1: Success after binutils/gcc/linux/gli [...] new 435fe00b7d6 105: onsuccess: #3: 1: Success after binutils/gcc/linux/gli [...] new 8510a3e9e9c 106: onsuccess: #4: 1: Success after binutils/gcc/linux/gli [...] new abf68736a3e 107: onsuccess: #5: 1: Success after binutils/gcc/linux/gli [...] new d57260d82b6 108: onsuccess: #6: 1: Success after binutils/gcc/linux/gdb [...] new c4977297949 109: onsuccess: #7: 1: Success after binutils/gcc/linux/gli [...] new 1fc63313c12 110: onsuccess: #8: 1: Success after binutils/gcc/linux/gli [...] new ac272ba2ae3 111: onsuccess: #9: 1: Success after binutils/gcc/linux/gdb [...] new 8ac4498208b 112: onsuccess: #10: 1: Success after binutils/gcc/linux/gd [...] new a23868e02a6 113: onsuccess: #11: 1: Success after binutils/gcc/linux/gl [...] new 8de90255302 114: onsuccess: #13: 1: Success after binutils/gcc/linux/gl [...] new 5c0683dd03b 115: onsuccess: #14: 1: Success after binutils/gcc/linux/gl [...] new 9bcc97ef33e 116: onsuccess: #15: 1: Success after binutils/gcc/linux/gl [...] new 310b70174f9 117: onsuccess: #16: 1: Success after binutils/gcc/linux/gd [...] new 4401ef10513 118: onsuccess: #17: 1: Success after binutils/gcc/linux/gd [...] new 8abcb736db6 119: onsuccess: #18: 1: Success after binutils/gcc/linux/gl [...] new ec7935eb063 120: onsuccess: #19: 1: Success after binutils/gcc/linux/gl [...] new dd7691ca033 121: force: #26: : Failure after baseline build: no new commits new 8c4cb6b75c3 122: onsuccess: #28: 1: Success after binutils/gcc/linux/gd [...] new 464deac6488 123: onsuccess: #29: 1: Success after binutils/gcc/linux/gd [...] new 1438c79c199 124: onsuccess: #30: 1: Success after binutils/gcc/linux/gd [...] new ec3327554c5 125: onsuccess: #31: 1: Success after binutils/gcc/linux/gd [...] new baf3c4bebee 126: onsuccess: #32: 1: Success after binutils/gcc/linux/gd [...] new 1f01bafb196 127: onsuccess: #33: 1: Success after binutils/gcc/linux/gl [...] new 2a2b7d12ce5 128: onsuccess: #34: 1: Success after binutils/gcc/linux/gd [...] new b264ffc1ac6 129: onsuccess: #35: 1: Success after binutils/gcc/linux/gd [...] new e8b48c8bd7f 130: onsuccess: #36: 1: Success after binutils/gcc/linux/gd [...] new 47766b00e8c 131: onsuccess: #37: 1: Success after binutils/gcc/linux/gl [...] new 4b2f18a351c 132: onsuccess: #39: 1: [TCWG CI] Success after binutils/gc [...] 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 (f64c901f4c3) \ 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 2040 -> 2260 bytes 02-prepare_abe/console.log.xz | Bin 2576 -> 2552 bytes 03-build_abe-binutils/console.log.xz | Bin 49244 -> 50148 bytes 04-build_abe-gcc/console.log.xz | Bin 235312 -> 237464 bytes 05-clean_sysroot/console.log.xz | Bin 316 -> 316 bytes 06-build_abe-linux/console.log.xz | Bin 9064 -> 8784 bytes 07-build_abe-glibc/console.log.xz | Bin 232684 -> 232348 bytes 08-build_abe-gdb/console.log.xz | Bin 47160 -> 46788 bytes 09-build_abe-dejagnu/console.log.xz | Bin 3796 -> 3772 bytes 10-build_abe-check_gdb/console.log.xz | Bin 3072 -> 3108 bytes 11-check_regression/console.log.xz | Bin 4452 -> 5132 bytes 11-check_regression/mail-body.txt | 35 ----------------------------- 11-check_regression/mail-subject.txt | 1 - 11-check_regression/results.compare | 4 ++-- 11-check_regression/results.compare2 | 6 ++--- 12-update_baseline/console.log | 40 +++++++++++++++++----------------- 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 | 32 +++++++++++++++++++++++++++ mail/changes-list-short.txt | 1 + mail/mail-body.txt | 35 ----------------------------- mail/mail-subject.txt | 1 - mail/short-diag.txt | 1 + manifest.sh | 38 ++++++++++++++++---------------- sumfiles/gdb.log.xz | Bin 14456 -> 14452 bytes sumfiles/gdb.sum | 4 ++-- 30 files changed, 86 insertions(+), 124 deletions(-) delete mode 100644 11-check_regression/mail-body.txt delete mode 100644 11-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/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, 8 months

Jump to page:

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

Tcwg-commits March 2023