Tcwg-commits March 2023

tcwg-commits@lists.linaro.org

5 participants
3834 discussions

[binutils-gdb] branch master updated (7cd38c3c566 -> 3e8154778ba)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. unknown user pushed a change to branch master in repository binutils-gdb. from 7cd38c3c566 gdb/testsuite: allow "require" callbacks to provide a reason new 3e8154778ba Put pretty-printers to_string output in varobj result The 1 revisions listed above as "new" are entirely new to this repository and will be described in separate emails. The revisions listed as "adds" were already present in the repository and have only been added to this reference. Summary of changes: gdb/doc/gdb.texinfo | 5 +++-- gdb/testsuite/gdb.python/py-mi.exp | 19 +++++++++++-------- gdb/testsuite/lib/mi-support.exp | 8 ++++---- gdb/varobj.c | 29 ++++++++--------------------- 4 files changed, 26 insertions(+), 35 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

1 year, 9 months

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

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 af45b17d0a8 c++: Allow translations of check_postcondition_result messa [...] new 22c3a6c3c11 Don't emit -Wxor-used-as-pow on macro expansions [PR107002] The 1 revisions listed above as "new" are entirely new to this repository and will be described in separate emails. The revisions listed as "adds" were already present in the repository and have only been added to this reference. Summary of changes: gcc/c-family/c-common.h | 2 +- gcc/c-family/c-warn.cc | 23 ++++++++++++++++++---- gcc/c/c-typeck.cc | 2 +- gcc/cp/parser.cc | 1 + gcc/diagnostic-show-locus.cc | 13 +++++++++--- gcc/testsuite/c-c++-common/Wxor-used-as-pow-1.c | 4 ++++ .../c-c++-common/Wxor-used-as-pow-pr107002-0.c | 9 +++++++++ .../c-c++-common/Wxor-used-as-pow-pr107002-1.c | 5 +++++ .../c-c++-common/Wxor-used-as-pow-pr107002-2.c | 5 +++++ 9 files changed, 55 insertions(+), 9 deletions(-) create mode 100644 gcc/testsuite/c-c++-common/Wxor-used-as-pow-pr107002-0.c create mode 100644 gcc/testsuite/c-c++-common/Wxor-used-as-pow-pr107002-1.c create mode 100644 gcc/testsuite/c-c++-common/Wxor-used-as-pow-pr107002-2.c -- To stop receiving notification emails like this one, please contact the administrator of this repository.

1 year, 9 months

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_kernel/gnu-master-arm-next-allyesconfig updated (8120ff79d04 -> e4c31eb2a4a)

by git＠git.linaro.org

1 year, 9 months

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_bmk-code_size-spec2k6/gnu-aarch64-master-O2_LTO updated (b40f2d74f31 -> d8d7aa886ae)

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_size-spec2k6/gnu-aarch64-master-O2_LTO in repository toolchain/ci/base-artifacts. from b40f2d74f31 0: init: #1: 1: [TCWG CI] No change after baseline build: n [...] new d8d7aa886ae 1: onsuccess: #2: 1: [TCWG CI] Success after binutils/gcc/g [...] The 1 revisions listed above as "new" are entirely new to this repository and will be described in separate emails. The revisions listed as "adds" were already present in the repository and have only been added to this reference. Summary of changes: 01-reset_artifacts/console.log.xz | Bin 2516 -> 2104 bytes 01-reset_artifacts/patch-env.sh | 2 - 02-prepare_abe/console.log.xz | Bin 2600 -> 2548 bytes 03-build_abe-binutils/console.log.xz | Bin 27940 -> 27608 bytes 04-build_abe-stage1/console.log.xz | Bin 71512 -> 71416 bytes 05-clean_sysroot/console.log.xz | Bin 332 -> 332 bytes 06-build_abe-linux/console.log.xz | Bin 7572 -> 8280 bytes 07-build_abe-glibc/console.log.xz | Bin 243152 -> 241556 bytes 08-build_abe-stage2/console.log.xz | Bin 180096 -> 176108 bytes 09-benchmark/benchmark-build.log | 101 +- 09-benchmark/benchmark.log | 99 +- 09-benchmark/console.log.xz | Bin 3992 -> 4068 bytes 10-check_regression/bmk-specific-variability.csv | 39 + .../compare-results-vs-first-internal.csv | 76 +- .../compare-results-vs-prev-internal.csv | 76 +- 10-check_regression/console.log.xz | Bin 9516 -> 11732 bytes .../csv-results-vs-first-0/results.csv | 923082 ++++++++--------- .../csv-results-vs-first-0/size.csv | 925830 ++++++++--------- 10-check_regression/csv-results-vs-first-0/sve.csv | 19036 +- .../csv-results-vs-first-0/vect.csv | 306 +- .../csv-results-vs-first-1/perf.csv | 146 +- .../csv-results-vs-first-1/results.csv | 923489 ++++++++--------- .../csv-results-vs-first-1/size.csv | 926248 +++++++++--------- 10-check_regression/csv-results-vs-first-1/sve.csv | 19036 +- .../csv-results-vs-first-1/vect.csv | 306 +- .../csv-results-vs-prev-0/results.csv | 923082 ++++++++--------- 10-check_regression/csv-results-vs-prev-0/size.csv | 925830 ++++++++--------- 10-check_regression/csv-results-vs-prev-0/sve.csv | 19036 +- 10-check_regression/csv-results-vs-prev-0/vect.csv | 306 +- 10-check_regression/csv-results-vs-prev-1/perf.csv | 146 +- .../csv-results-vs-prev-1/results.csv | 923489 ++++++++--------- 10-check_regression/csv-results-vs-prev-1/size.csv | 926248 +++++++++--------- 10-check_regression/csv-results-vs-prev-1/sve.csv | 19036 +- 10-check_regression/csv-results-vs-prev-1/vect.csv | 306 +- .../output-bmk-results/exe.improvement | 1 + .../output-bmk-results/exe.improvement.diff | 1 + .../output-bmk-results/exe.regression | 1 + .../output-bmk-results/exe.regression.diff | 1 + 10-check_regression/results-vs-first-brief.csv | 111 +- 10-check_regression/results-vs-first-full.csv | 168 +- 10-check_regression/results-vs-first-internal.csv | 103 +- 10-check_regression/results-vs-first.csv | 103 +- 10-check_regression/results-vs-first.log | 1684 +- 10-check_regression/results-vs-prev-brief.csv | 111 +- 10-check_regression/results-vs-prev-compare.csv | 27 +- 10-check_regression/results-vs-prev-full.csv | 168 +- 10-check_regression/results-vs-prev-internal.csv | 103 +- 10-check_regression/results-vs-prev.csv | 103 +- 10-check_regression/results-vs-prev.log | 1834 +- 11-update_baseline/console.log | 2 +- 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 +- .../squad-vs-first/403.gcc/results-metrics.json | 2 +- .../410.bwaves/results-metadata.json | 14 +- .../squad-vs-first/410.bwaves/results-metrics.json | 2 +- .../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 +- .../435.gromacs/results-metrics.json | 2 +- .../436.cactusADM/results-metadata.json | 14 +- .../437.leslie3d/results-metadata.json | 14 +- .../437.leslie3d/results-metrics.json | 2 +- .../squad-vs-first/444.namd/results-metadata.json | 14 +- .../squad-vs-first/444.namd/results-metrics.json | 2 +- .../squad-vs-first/445.gobmk/results-metadata.json | 14 +- .../squad-vs-first/445.gobmk/results-metrics.json | 2 +- .../447.dealII/results-metadata.json | 14 +- .../squad-vs-first/447.dealII/results-metrics.json | 2 +- .../450.soplex/results-metadata.json | 14 +- .../squad-vs-first/450.soplex/results-metrics.json | 2 +- .../453.povray/results-metadata.json | 14 +- .../squad-vs-first/453.povray/results-metrics.json | 4 +- .../454.calculix/results-metadata.json | 14 +- .../454.calculix/results-metrics.json | 2 +- .../squad-vs-first/456.hmmer/results-metadata.json | 14 +- .../squad-vs-first/458.sjeng/results-metadata.json | 14 +- .../459.GemsFDTD/results-metadata.json | 14 +- .../459.GemsFDTD/results-metrics.json | 4 +- .../462.libquantum/results-metadata.json | 14 +- .../462.libquantum/results-metrics.json | 2 +- .../464.h264ref/results-metadata.json | 14 +- .../464.h264ref/results-metrics.json | 2 +- .../squad-vs-first/465.tonto/results-metadata.json | 14 +- .../squad-vs-first/470.lbm/results-metadata.json | 14 +- .../471.omnetpp/results-metadata.json | 14 +- .../squad-vs-first/473.astar/results-metadata.json | 14 +- .../squad-vs-first/473.astar/results-metrics.json | 2 +- .../squad-vs-first/481.wrf/results-metadata.json | 14 +- .../squad-vs-first/481.wrf/results-metrics.json | 2 +- .../482.sphinx3/results-metadata.json | 14 +- .../483.xalancbmk/results-metadata.json | 14 +- .../squad-vs-first/Mean/results-metadata.json | 14 +- dashboard/squad-vs-first/dashboard-push-squad.sh | 509 +- 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 | 13 - mail/mail-subject.txt | 1 - mail/short-diag.txt | 1 + manifest.sh | 32 +- results_id | 2 +- 109 files changed, 3741349 insertions(+), 3739570 deletions(-) delete mode 100644 01-reset_artifacts/patch-env.sh create mode 100644 10-check_regression/bmk-specific-variability.csv create mode 100644 10-check_regression/output-bmk-results/exe.improvement create mode 100644 10-check_regression/output-bmk-results/exe.improvement.diff 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, 9 months

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

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 315d12afdd6 219: force: #64: 1: [TCWG CI] Success after gdb: 32 commits discards 09c44f04e6e 218: onsuccess: #62: 1: [TCWG CI] Success after binutils/gc [...] discards 4df4e73781e 217: onsuccess: #53: 1: Success after binutils/gcc/linux/gd [...] discards b40f8c71944 216: onsuccess: #52: 1: Success after binutils/gcc/linux/gd [...] discards 8209e747cdb 215: onsuccess: #48: 1: Success after binutils/gcc/linux/gd [...] discards e2afb2c3ec3 214: onsuccess: #47: 1: Success after gdb: 21 commits discards fd0cb722538 213: force: #46: 1: Success after gdb-13-branchpoint-1550-g [...] discards 4ffd2b44258 212: force: #45: 1: Success after gdb: 22 commits discards 3f14ab86cd0 211: onsuccess: #44: 1: Success after linux: 26 commits discards 5d06170677e 210: onsuccess: #43: 1: Success after glibc-2.37.9000-181-g [...] discards 1caa10ced7c 209: force: #37: 1: Success after baseline build: no new commits discards fd6b02747f4 208: onsuccess: #30: 1: Success after binutils/gcc/linux/gd [...] discards f855b3b9bf7 207: onsuccess: #29: 1: Success after binutils/gcc/linux/gd [...] discards b7caca5a96d 206: onsuccess: #28: 1: Success after binutils/gcc/linux/gd [...] discards 46376cd4153 205: onsuccess: #27: 1: Success after binutils/gcc/linux/gd [...] discards baf31157b8c 204: force: #26: : Failure after baseline build: no new commits discards a3b368ce873 203: onsuccess: #19: 1: Success after binutils/gcc/linux/gl [...] discards 8cd9408cd98 202: onsuccess: #18: 1: Success after binutils/gcc/linux/gl [...] discards 9b474344e05 201: onsuccess: #17: 1: Success after binutils/gcc/linux/gd [...] discards aa8de6bd727 200: onsuccess: #16: 1: Success after binutils/gcc/linux/gl [...] discards 74240094c06 199: onsuccess: #15: 1: Success after binutils/gcc/linux/gd [...] discards 9f3e9ebcee0 198: onsuccess: #14: 1: Success after binutils/gcc/linux/gl [...] discards 8944ad8d166 197: onsuccess: #13: 1: Success after binutils/gcc/linux/gl [...] discards 857ce37abfc 196: onsuccess: #12: 1: Success after binutils/gcc/linux/gl [...] discards 62e997c9651 195: onsuccess: #11: 1: Success after binutils/gcc/linux/gd [...] discards 1feaec752e9 194: onsuccess: #10: 1: Success after binutils/gcc/linux/gd [...] discards f9c9a3f2cac 193: onsuccess: #9: 1: Success after binutils/gcc/linux/gdb [...] discards 4f6e3705842 192: onsuccess: #8: 1: Success after binutils/gcc/linux/gli [...] discards 889cb16da20 191: onsuccess: #7: 1: Success after binutils/gcc/linux/gli [...] discards eaac9083644 190: onsuccess: #6: 1: Success after binutils/gcc/linux/gli [...] discards 43b97da9923 189: onsuccess: #5: 1: Success after binutils/gcc/linux/gli [...] discards 4847a146890 188: onsuccess: #4: 1: Success after binutils/gcc/linux/gdb [...] discards c655ea4754f 187: onsuccess: #3: 1: Success after binutils/gcc/linux/gli [...] discards 16c4932f350 186: onsuccess: #2: 1: Success after binutils/gcc/linux/gdb [...] discards 6d6402f623e 185: onsuccess: #1: 1: Success after binutils/gcc/linux/gli [...] discards 4dbc66d1d06 184: onsuccess: #977: 1: Success after binutils/gcc/linux/g [...] discards 99691193428 183: onsuccess: #976: 1: Success after binutils/gcc/linux/g [...] discards 6bd410fff44 182: onsuccess: #975: 1: Success after binutils/gcc/linux/g [...] discards 1e32132cac0 181: onsuccess: #974: 1: Success after binutils/gcc/linux/g [...] discards a76838b0de1 180: onsuccess: #973: 1: Success after binutils/gcc/linux/g [...] discards 0298f0a7bee 179: onsuccess: #972: 1: Success after binutils/gcc/linux/g [...] discards 9f4e9791e04 178: onsuccess: #971: 1: Success after binutils/gcc/linux/g [...] discards d0a261dd2c0 177: onsuccess: #970: 1: Success after binutils/gcc/linux/g [...] discards cc909f77fc7 176: onsuccess: #969: 1: Success after binutils/gcc/linux/g [...] discards a3321a9eb14 175: onsuccess: #968: 1: Success after binutils/gcc/linux/g [...] discards 02c925ce31f 174: onsuccess: #967: 1: Success after binutils/gcc/linux/g [...] discards 8d265ade25c 173: onsuccess: #966: 1: Success after binutils/gcc/linux/g [...] discards 364274487b2 172: onsuccess: #965: 1: Success after binutils/gcc/glibc/g [...] discards afa02f3a23c 171: onsuccess: #964: 1: Success after binutils/gcc/linux/g [...] discards f1ac2ab1707 170: onsuccess: #963: 1: Success after binutils/gcc/linux/g [...] discards 7f5716d8286 169: onsuccess: #962: 1: Success after binutils/gcc/linux/g [...] discards 3861c88152e 168: onsuccess: #961: 1: Success after binutils/gcc/linux/g [...] discards 3eab06faff5 167: onsuccess: #960: 1: Success after binutils/gcc/linux/g [...] discards 413eb2a4733 166: onsuccess: #959: 1: Success after binutils/gcc/linux/g [...] discards 9c87835ef8c 165: onsuccess: #958: 1: Success after binutils/gcc/linux/g [...] discards 35bf9fecfd0 164: onsuccess: #957: 1: Success after binutils/gcc/glibc/g [...] discards 812ac746ee5 163: onsuccess: #956: 1: Success after binutils/gcc/linux/g [...] discards 77f6f9871ec 162: onsuccess: #955: 1: Success after binutils/gcc/linux/g [...] discards 8b30ae1de91 161: onsuccess: #954: 1: Success after binutils/gcc/linux/g [...] discards 538bcc9be05 160: onsuccess: #953: 1: Success after binutils/gcc/linux/g [...] discards f579fa939a1 159: onsuccess: #952: 1: Success after binutils/gcc/linux/g [...] discards 62021d83829 158: onsuccess: #951: 1: Success after gcc/linux: 19 commits discards cd6e0b64c72 157: onsuccess: #950: 1: Success after binutils/gcc/linux/g [...] discards a4116bea665 156: onsuccess: #949: 1: Success after binutils/gcc/linux/g [...] discards 56163872a58 155: onsuccess: #948: 1: Success after binutils/gcc/linux/g [...] discards 316f3f6a69c 154: onsuccess: #947: 1: Success after binutils/gcc/linux/g [...] discards 6860eac6807 153: onsuccess: #946: 1: Success after binutils/gcc/linux/g [...] discards 8d342a9e9ee 152: onsuccess: #945: 1: Success after binutils/gcc/linux/g [...] discards 56f62d50f4f 151: onsuccess: #944: 1: Success after binutils/gcc/linux/g [...] discards c59b599f015 150: onsuccess: #943: 1: Success after binutils/gcc/linux/g [...] discards 05744a4c338 149: onsuccess: #942: 1: Success after binutils/gcc/linux/g [...] discards 0a4e9a75717 148: onsuccess: #941: 1: Success after binutils/gcc/linux/g [...] discards 9ec09bdee87 147: onsuccess: #940: 1: Success after binutils/gcc/linux/g [...] discards a41d8a01cbb 146: onsuccess: #939: 1: Success after binutils/gcc/linux/g [...] discards 839b26551c9 145: onsuccess: #934: 1: Success after binutils/gcc/linux/g [...] discards 1ef3d2e25f0 144: onsuccess: #933: 1: Success after binutils/gcc/glibc/g [...] discards 21d4cc09a24 143: onsuccess: #931: 1: Success after binutils/gcc/linux/g [...] discards 98c495f1a2e 142: onsuccess: #929: 1: Success after binutils/gcc/linux/g [...] discards 541167abb43 141: onsuccess: #928: 1: Success after binutils/gcc/linux/g [...] discards 401148fae3b 140: onsuccess: #927: 1: Success after binutils/gcc/linux/g [...] discards a579fd4ddd7 139: onsuccess: #926: 1: Success after binutils/gcc/linux/g [...] discards 5d437af5857 138: onsuccess: #925: 1: Success after binutils/gcc/gdb: 11 [...] discards 74fea35e337 137: onsuccess: #924: 1: Success after binutils/gcc/gdb: 43 [...] discards 2ffe17ca434 136: onsuccess: #923: 1: Success after binutils/gcc/gdb: 10 [...] discards 2a4ffffaa8b 135: onsuccess: #922: 1: Success after binutils/gcc/linux/g [...] discards 36060b68e0a 134: onsuccess: #921: 1: Success after binutils/gcc/gdb: 26 [...] discards 4077730580b 133: onsuccess: #920: 1: Success after binutils/gcc/linux/g [...] discards 626a27d3e79 132: onsuccess: #919: 1: Success after binutils/gcc/linux/g [...] discards c5fb7d91091 131: onsuccess: #918: 1: Success after binutils/gcc/linux/g [...] discards 43cd36dfb64 130: onsuccess: #917: 1: Success after binutils/gcc/linux/g [...] discards 11a5ad99a9f 129: onsuccess: #916: 1: Success after binutils/gcc/linux/g [...] discards 5a031ed412d 128: onsuccess: #915: 1: Success after binutils/gcc/glibc/g [...] discards 95e17bd52de 127: onsuccess: #914: 1: Success after binutils/gcc/linux/g [...] discards 23d15655411 126: onsuccess: #913: 1: Success after binutils/gcc/linux/g [...] discards ce27619ec1d 125: onsuccess: #912: 1: Success after binutils/gcc/linux/g [...] discards a8f4e8ac802 124: onsuccess: #911: 1: Success after binutils/gcc/linux/g [...] discards aaf9b4cc22f 123: onsuccess: #910: 1: Success after binutils/gcc/linux/g [...] discards c37fff1602e 122: onsuccess: #909: 1: Success after linux: 2753 commits discards 81e32b82fda 121: onsuccess: #908: 1: Success after glibc: 2 commits discards e61080d775a 120: onsuccess: #906: 1: Success after binutils: 29 commits discards 192626d1687 119: onsuccess: #904: 1: Success after binutils/gcc/linux/g [...] new cb84854d4b5 119: onsuccess: #904: 1: Success after binutils/gcc/linux/g [...] new aeef4082401 120: onsuccess: #906: 1: Success after binutils: 29 commits new 70f7a3620b2 121: onsuccess: #908: 1: Success after glibc: 2 commits new 62e65401217 122: onsuccess: #909: 1: Success after linux: 2753 commits new 407f11f75bd 123: onsuccess: #910: 1: Success after binutils/gcc/linux/g [...] new 522016d2592 124: onsuccess: #911: 1: Success after binutils/gcc/linux/g [...] new f74aa9ca171 125: onsuccess: #912: 1: Success after binutils/gcc/linux/g [...] new 5d914e0f903 126: onsuccess: #913: 1: Success after binutils/gcc/linux/g [...] new 7f62d832845 127: onsuccess: #914: 1: Success after binutils/gcc/linux/g [...] new dcf12b7f75f 128: onsuccess: #915: 1: Success after binutils/gcc/glibc/g [...] new 7181b31847b 129: onsuccess: #916: 1: Success after binutils/gcc/linux/g [...] new dbf1b0cadd8 130: onsuccess: #917: 1: Success after binutils/gcc/linux/g [...] new 251e9ed9995 131: onsuccess: #918: 1: Success after binutils/gcc/linux/g [...] new 5ef1d856729 132: onsuccess: #919: 1: Success after binutils/gcc/linux/g [...] new 56670330aa2 133: onsuccess: #920: 1: Success after binutils/gcc/linux/g [...] new f85772815c8 134: onsuccess: #921: 1: Success after binutils/gcc/gdb: 26 [...] new a024921548e 135: onsuccess: #922: 1: Success after binutils/gcc/linux/g [...] new c1df253ca9c 136: onsuccess: #923: 1: Success after binutils/gcc/gdb: 10 [...] new 8456c620862 137: onsuccess: #924: 1: Success after binutils/gcc/gdb: 43 [...] new 069d7b3e27c 138: onsuccess: #925: 1: Success after binutils/gcc/gdb: 11 [...] new fa5b803a7e8 139: onsuccess: #926: 1: Success after binutils/gcc/linux/g [...] new a130631c4de 140: onsuccess: #927: 1: Success after binutils/gcc/linux/g [...] new 6e85f5f2fbb 141: onsuccess: #928: 1: Success after binutils/gcc/linux/g [...] new c6b4dce66bc 142: onsuccess: #929: 1: Success after binutils/gcc/linux/g [...] new fa3ecb94a33 143: onsuccess: #931: 1: Success after binutils/gcc/linux/g [...] new ed4ce363c58 144: onsuccess: #933: 1: Success after binutils/gcc/glibc/g [...] new 0548d04d5e8 145: onsuccess: #934: 1: Success after binutils/gcc/linux/g [...] new 71e4b66f588 146: onsuccess: #939: 1: Success after binutils/gcc/linux/g [...] new 514c659ba82 147: onsuccess: #940: 1: Success after binutils/gcc/linux/g [...] new 791614f5f44 148: onsuccess: #941: 1: Success after binutils/gcc/linux/g [...] new 499096342e8 149: onsuccess: #942: 1: Success after binutils/gcc/linux/g [...] new d373994863a 150: onsuccess: #943: 1: Success after binutils/gcc/linux/g [...] new 4e3b86d3072 151: onsuccess: #944: 1: Success after binutils/gcc/linux/g [...] new 4482ec07717 152: onsuccess: #945: 1: Success after binutils/gcc/linux/g [...] new dfd6159e28e 153: onsuccess: #946: 1: Success after binutils/gcc/linux/g [...] new a7fb8010d48 154: onsuccess: #947: 1: Success after binutils/gcc/linux/g [...] new 70f900f45d4 155: onsuccess: #948: 1: Success after binutils/gcc/linux/g [...] new 282a7e9754a 156: onsuccess: #949: 1: Success after binutils/gcc/linux/g [...] new bc867be843a 157: onsuccess: #950: 1: Success after binutils/gcc/linux/g [...] new 11afd56271a 158: onsuccess: #951: 1: Success after gcc/linux: 19 commits new 93c29dd21c0 159: onsuccess: #952: 1: Success after binutils/gcc/linux/g [...] new 7b1644aba97 160: onsuccess: #953: 1: Success after binutils/gcc/linux/g [...] new a0daa035931 161: onsuccess: #954: 1: Success after binutils/gcc/linux/g [...] new 0ae4690a938 162: onsuccess: #955: 1: Success after binutils/gcc/linux/g [...] new 428369abe8c 163: onsuccess: #956: 1: Success after binutils/gcc/linux/g [...] new ca37abc44fa 164: onsuccess: #957: 1: Success after binutils/gcc/glibc/g [...] new 96b4c0460c8 165: onsuccess: #958: 1: Success after binutils/gcc/linux/g [...] new aa4c7e2c28a 166: onsuccess: #959: 1: Success after binutils/gcc/linux/g [...] new 5976aa7b1d9 167: onsuccess: #960: 1: Success after binutils/gcc/linux/g [...] new e2cf48c66d4 168: onsuccess: #961: 1: Success after binutils/gcc/linux/g [...] new ed3d70cd145 169: onsuccess: #962: 1: Success after binutils/gcc/linux/g [...] new 8d571085253 170: onsuccess: #963: 1: Success after binutils/gcc/linux/g [...] new 337220fa982 171: onsuccess: #964: 1: Success after binutils/gcc/linux/g [...] new 9dd5e1a7048 172: onsuccess: #965: 1: Success after binutils/gcc/glibc/g [...] new d33f8795c93 173: onsuccess: #966: 1: Success after binutils/gcc/linux/g [...] new c2dd837b589 174: onsuccess: #967: 1: Success after binutils/gcc/linux/g [...] new 389ad1b099d 175: onsuccess: #968: 1: Success after binutils/gcc/linux/g [...] new 8a975022466 176: onsuccess: #969: 1: Success after binutils/gcc/linux/g [...] new 1efb01772bb 177: onsuccess: #970: 1: Success after binutils/gcc/linux/g [...] new 980815729a6 178: onsuccess: #971: 1: Success after binutils/gcc/linux/g [...] new d8f8489cb3a 179: onsuccess: #972: 1: Success after binutils/gcc/linux/g [...] new dc05ce056b9 180: onsuccess: #973: 1: Success after binutils/gcc/linux/g [...] new 04d00bd2ae8 181: onsuccess: #974: 1: Success after binutils/gcc/linux/g [...] new 17d612ce84d 182: onsuccess: #975: 1: Success after binutils/gcc/linux/g [...] new 1fc2b8f6dae 183: onsuccess: #976: 1: Success after binutils/gcc/linux/g [...] new e3bd187d4c2 184: onsuccess: #977: 1: Success after binutils/gcc/linux/g [...] new 849570e8b73 185: onsuccess: #1: 1: Success after binutils/gcc/linux/gli [...] new 5f784bd2353 186: onsuccess: #2: 1: Success after binutils/gcc/linux/gdb [...] new 9c92227b4a8 187: onsuccess: #3: 1: Success after binutils/gcc/linux/gli [...] new e2532431e8d 188: onsuccess: #4: 1: Success after binutils/gcc/linux/gdb [...] new 0f11a255f1d 189: onsuccess: #5: 1: Success after binutils/gcc/linux/gli [...] new 61e6bccf795 190: onsuccess: #6: 1: Success after binutils/gcc/linux/gli [...] new 3e0ad9fcba6 191: onsuccess: #7: 1: Success after binutils/gcc/linux/gli [...] new b0a6518a65f 192: onsuccess: #8: 1: Success after binutils/gcc/linux/gli [...] new 4c2ad6a63ea 193: onsuccess: #9: 1: Success after binutils/gcc/linux/gdb [...] new b4d14f6efdf 194: onsuccess: #10: 1: Success after binutils/gcc/linux/gd [...] new 9fb5ef8bf7d 195: onsuccess: #11: 1: Success after binutils/gcc/linux/gd [...] new 591399f1433 196: onsuccess: #12: 1: Success after binutils/gcc/linux/gl [...] new eafb6fd02a4 197: onsuccess: #13: 1: Success after binutils/gcc/linux/gl [...] new cb351186e7e 198: onsuccess: #14: 1: Success after binutils/gcc/linux/gl [...] new 7db63c3df75 199: onsuccess: #15: 1: Success after binutils/gcc/linux/gd [...] new 8b860345329 200: onsuccess: #16: 1: Success after binutils/gcc/linux/gl [...] new 28d9bc090e2 201: onsuccess: #17: 1: Success after binutils/gcc/linux/gd [...] new b14dbd0410a 202: onsuccess: #18: 1: Success after binutils/gcc/linux/gl [...] new 1a3724e0664 203: onsuccess: #19: 1: Success after binutils/gcc/linux/gl [...] new 27ef9a9e204 204: force: #26: : Failure after baseline build: no new commits new db3a2a933fa 205: onsuccess: #27: 1: Success after binutils/gcc/linux/gd [...] new b6ce1592da8 206: onsuccess: #28: 1: Success after binutils/gcc/linux/gd [...] new abfaa9b7c21 207: onsuccess: #29: 1: Success after binutils/gcc/linux/gd [...] new 208200ca9ba 208: onsuccess: #30: 1: Success after binutils/gcc/linux/gd [...] new 91af2700105 209: force: #37: 1: Success after baseline build: no new commits new 9f0f389d5b1 210: onsuccess: #43: 1: Success after glibc-2.37.9000-181-g [...] new 6e87fc04c97 211: onsuccess: #44: 1: Success after linux: 26 commits new d3eff7a75c2 212: force: #45: 1: Success after gdb: 22 commits new 42ef6dae7f6 213: force: #46: 1: Success after gdb-13-branchpoint-1550-g [...] new 25bed252ef4 214: onsuccess: #47: 1: Success after gdb: 21 commits new f621495d1d5 215: onsuccess: #48: 1: Success after binutils/gcc/linux/gd [...] new 4130945d9f6 216: onsuccess: #52: 1: Success after binutils/gcc/linux/gd [...] new ccb6c867c63 217: onsuccess: #53: 1: Success after binutils/gcc/linux/gd [...] new 08262ba346c 218: onsuccess: #62: 1: [TCWG CI] Success after binutils/gc [...] new 488577a333d 219: force: #64: 1: [TCWG CI] Success after gdb: 32 commits new 2d4504a95ac 220: force: #65: 1: [TCWG CI] Failure after gdb-13-branchpo [...] 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 (315d12afdd6) \ 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 2204 -> 2032 bytes 02-prepare_abe/console.log.xz | Bin 2492 -> 2500 bytes 03-build_abe-binutils/console.log.xz | Bin 35188 -> 35276 bytes 04-build_abe-gcc/console.log.xz | Bin 206552 -> 202768 bytes 06-build_abe-linux/console.log.xz | Bin 8876 -> 8820 bytes 07-build_abe-glibc/console.log.xz | Bin 242328 -> 241448 bytes 08-build_abe-gdb/console.log.xz | Bin 34532 -> 34716 bytes 09-build_abe-dejagnu/console.log.xz | Bin 3844 -> 3780 bytes 10-build_abe-check_gdb/console.log.xz | Bin 2752 -> 2692 bytes 11-check_regression/console.log.xz | Bin 3120 -> 3648 bytes 11-check_regression/extra-bisect-params | 1 + 11-check_regression/fails.sum | 6 + 11-check_regression/results.compare | 9 +- 11-check_regression/results.regressions | 14 + 11-check_regression/trigger-bisect | 3 + 11-check_regression/trigger-notify | 0 12-update_baseline/console.log | 40 +- 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 | 20 +- results | 14 + sumfiles/gdb.log.0.xz | Bin 1966132 -> 1932664 bytes sumfiles/gdb.log.1.xz | Bin 70144 -> 20768 bytes sumfiles/gdb.log.2.xz | Bin 0 -> 5552 bytes sumfiles/gdb.log.3.xz | Bin 0 -> 5484 bytes sumfiles/gdb.sum | 5304 ++++++++++++++++--- sumfiles/gdb.sum.0 | 5310 ++++++++++++++++--- sumfiles/gdb.sum.1 | 8445 +------------------------------ sumfiles/gdb.sum.2 | 182 + sumfiles/gdb.sum.3 | 182 + 34 files changed, 9929 insertions(+), 9623 deletions(-) create mode 100644 11-check_regression/extra-bisect-params create mode 100644 11-check_regression/fails.sum create mode 100644 11-check_regression/results.regressions create mode 100644 11-check_regression/trigger-bisect create mode 100644 11-check_regression/trigger-notify create mode 100755 jenkins/notify.sh create mode 100644 sumfiles/gdb.log.2.xz create mode 100644 sumfiles/gdb.log.3.xz create mode 100644 sumfiles/gdb.sum.2 create mode 100644 sumfiles/gdb.sum.3 -- To stop receiving notification emails like this one, please contact the administrator of this repository.

1 year, 9 months

[toolchain/ci/interesting-commits] branch master updated (d13f1e40 -> 89bc00c3)

by tcwg-buildslave

This is an automated email from the git hooks/post-receive script. "tcwg-buildslave pushed a change to branch master in repository toolchain/ci/interesting-commits. from d13f1e40 Add entry 303a881f8789733248f27af0c872d356a34be009 from https [...] new 89bc00c3 Add entry 7005080802d695d112530a7c24c9d3d44ee109a3 from https [...] The 1 revisions listed above as "new" are entirely new to this repository and will be described in separate emails. The revisions listed as "adds" were already present in the repository and have only been added to this reference. Summary of changes: gdb/gdb-13-branchpoint-1629-g7005080802d | 1 + .../master-aarch64/build_url | 1 + .../master-aarch64/last_good | 1 + .../master-aarch64/summary.txt | 63 ++++++++++++++++++ .../tcwg_gnu_native_check_gdb/status.txt | 74 ++++++++++++++++++++++ 5 files changed, 140 insertions(+) create mode 120000 gdb/gdb-13-branchpoint-1629-g7005080802d create mode 100644 gdb/sha1/7005080802d695d112530a7c24c9d3d44ee109a3/tcwg_gnu_nati [...] create mode 100644 gdb/sha1/7005080802d695d112530a7c24c9d3d44ee109a3/tcwg_gnu_nati [...] create mode 100644 gdb/sha1/7005080802d695d112530a7c24c9d3d44ee109a3/tcwg_gnu_nati [...] create mode 100644 gdb/sha1/7005080802d695d112530a7c24c9d3d44ee109a3/tcwg_gnu_nati [...] -- To stop receiving notification emails like this one, please contact the administrator of this repository.

1 year, 9 months

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_kernel/gnu-master-arm-next-allyesconfig updated (0099e4098ab -> 8120ff79d04)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. tcwg-buildslave pushed a change to branch linaro-local/ci/tcwg_kernel/gnu-master-arm-next-allyesconfig in repository toolchain/ci/base-artifacts. from 0099e4098ab 56: onsuccess: #9: 21237: Success after binutils/gcc/linux/ [...] new 8120ff79d04 57: onsuccess: #13: 21260: [TCWG CI] Success after linux: 3 [...] 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 1764 -> 1980 bytes 02-prepare_abe/console.log.xz | Bin 2504 -> 2564 bytes 03-build_abe-binutils/console.log.xz | Bin 26960 -> 27216 bytes 04-build_abe-stage1/console.log.xz | Bin 88536 -> 88696 bytes 05-build_abe-qemu/console.log.xz | Bin 31724 -> 32228 bytes 06-build_linux/console.log.xz | Bin 8764 -> 7680 bytes 08-check_regression/console.log.xz | Bin 4344 -> 2864 bytes 08-check_regression/jira-body.txt | 1 - 08-check_regression/mail-body.txt | 23 ----------------------- 08-check_regression/mail-subject.txt | 1 - dashboard/dashboard-generate.sh | 2 +- git/linux_rev | 2 +- mail/changes-list-long.txt | 8 ++++++++ mail/changes-list-short.txt | 1 + mail/jira-body.txt | 1 - mail/mail-body.txt | 23 ----------------------- mail/mail-subject.txt | 1 - mail/short-diag.txt | 1 + manifest.sh | 25 +++++++++++-------------- results | 2 +- 20 files changed, 24 insertions(+), 67 deletions(-) delete mode 100644 08-check_regression/jira-body.txt delete mode 100644 08-check_regression/mail-body.txt delete mode 100644 08-check_regression/mail-subject.txt create mode 100644 mail/changes-list-long.txt create mode 100644 mail/changes-list-short.txt delete mode 100644 mail/jira-body.txt 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, 9 months

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_bmk-code_size-spec2k6/llvm-arm-master-O3_LTO updated (abb1238ad7d -> ee1b026919c)

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_size-spec2k6/llvm-arm-master-O3_LTO in repository toolchain/ci/base-artifacts. from abb1238ad7d 0: init: #1: 1: [TCWG CI] No change after baseline build: n [...] new ee1b026919c 1: onsuccess: #2: 1: [TCWG CI] Success after llvm: 244 commits The 1 revisions listed above as "new" are entirely new to this repository and will be described in separate emails. The revisions listed as "adds" were already present in the repository and have only been added to this reference. Summary of changes: 01-reset_artifacts/console.log.xz | Bin 2264 -> 1880 bytes 01-reset_artifacts/patch-env.sh | 2 - 02-build_bmk_llvm/console.log.xz | Bin 229804 -> 247100 bytes 03-benchmark/benchmark-build.log | 114 +- 03-benchmark/benchmark.log | 112 +- 03-benchmark/console.log.xz | Bin 3888 -> 3920 bytes .../compare-results-vs-first-internal.csv | 38 +- .../compare-results-vs-prev-internal.csv | 38 +- 04-check_regression/console.log.xz | Bin 6160 -> 6960 bytes .../csv-results-vs-first-1/perf.csv | 75 +- .../csv-results-vs-first-1/results.csv | 75 +- 04-check_regression/csv-results-vs-prev-1/perf.csv | 75 +- .../csv-results-vs-prev-1/results.csv | 75 +- 04-check_regression/results-vs-first-brief.csv | 34 +- 04-check_regression/results-vs-first-full.csv | 75 +- 04-check_regression/results-vs-first-internal.csv | 38 +- 04-check_regression/results-vs-first.csv | 38 +- 04-check_regression/results-vs-first.log | 1126 +++++++++---------- 04-check_regression/results-vs-prev-brief.csv | 34 +- 04-check_regression/results-vs-prev-full.csv | 75 +- 04-check_regression/results-vs-prev-internal.csv | 38 +- 04-check_regression/results-vs-prev.csv | 38 +- 04-check_regression/results-vs-prev.log | 1172 ++++++++++---------- 05-update_baseline/console.log | 2 +- dashboard/dashboard-generate.sh | 2 +- .../400.perlbench/results-metadata.json | 10 +- .../squad-vs-first/401.bzip2/results-metadata.json | 10 +- .../squad-vs-first/403.gcc/results-metadata.json | 10 +- .../squad-vs-first/429.mcf/results-metadata.json | 10 +- .../squad-vs-first/429.mcf/results-metrics.json | 2 +- .../squad-vs-first/433.milc/results-metadata.json | 10 +- .../squad-vs-first/444.namd/results-metadata.json | 10 +- .../squad-vs-first/445.gobmk/results-metadata.json | 10 +- .../447.dealII/results-metadata.json | 10 +- .../450.soplex/results-metadata.json | 10 +- .../453.povray/results-metadata.json | 10 +- .../squad-vs-first/456.hmmer/results-metadata.json | 10 +- .../squad-vs-first/458.sjeng/results-metadata.json | 10 +- .../462.libquantum/results-metadata.json | 10 +- .../462.libquantum/results-metrics.json | 2 +- .../464.h264ref/results-metadata.json | 10 +- .../464.h264ref/results-metrics.json | 2 +- .../squad-vs-first/470.lbm/results-metadata.json | 10 +- .../471.omnetpp/results-metadata.json | 10 +- .../471.omnetpp/results-metrics.json | 2 +- .../squad-vs-first/473.astar/results-metadata.json | 10 +- .../482.sphinx3/results-metadata.json | 10 +- .../482.sphinx3/results-metrics.json | 2 +- .../483.xalancbmk/results-metadata.json | 10 +- .../483.xalancbmk/results-metrics.json | 2 +- .../squad-vs-first/Mean/results-metadata.json | 10 +- dashboard/squad-vs-first/dashboard-push-squad.sh | 230 ++-- git/llvm_rev | 2 +- mail/changes-list-long.txt | 8 + mail/changes-list-short.txt | 1 + mail/mail-body.txt | 13 - mail/mail-subject.txt | 1 - mail/short-diag.txt | 1 + manifest.sh | 14 +- results_id | 2 +- 60 files changed, 1878 insertions(+), 1882 deletions(-) delete mode 100644 01-reset_artifacts/patch-env.sh 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, 9 months

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_gnu_native_check_gdb/master-arm updated (9b2397a6d6c -> d48e49aefae)

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-arm in repository toolchain/ci/base-artifacts. discards 9b2397a6d6c 231: force: #89: 1: [TCWG CI] Failure after gdb: 31 commits discards 16db361a45b 230: onsuccess: #78: 1: Success after gdb: 2 commits discards 0e57dad3c95 229: force: #77: 1: Failure after gdb-13-branchpoint-1594-g [...] discards 9761e53dd16 228: force: #74: 1: Success after gdb: 53 commits discards e69e6f65cb0 227: onsuccess: #72: 1: Success after binutils/gcc/linux/gl [...] discards f8236434d4b 226: force: #70: 1: Success after baseline build: no new commits discards 1154a01eff2 225: force: #68: 1: Failure after gdb-13-branchpoint-1540-g [...] discards 82fdd8f79f4 224: force: #65: 1: Success after gdb: 50 commits discards 02526e9073e 223: force: #63: 1: Failure after gdb-13-branchpoint-1489-g [...] discards ce3ece35f24 222: force: #60: 1: Success after gdb: 16 commits discards 60e4a7241e1 221: force: #53: 1: Success after gdb-13-branchpoint-1472-g [...] discards be618bd2fe5 220: force: #51: 1: Success after v6.2-rc6-1149-g5b49da02dd [...] discards cf023fa6a85 219: force: #50: 1: Failure after linux: 2520 commits discards 904c1e3d338 218: force: #48: 1: Success after gdb-13-branchpoint-1471-g [...] discards a61f753e4eb 217: force: #45: 1: Success after linux: 1 commits discards bd8f5853c26 216: force: #43: : Failure after baseline build: no new commits discards 388f8732d64 215: force: #41: 1: Failure after gdb-13-branchpoint-1470-g [...] discards 96f6086fca5 214: force: #39: 1: Failure after gdb-13-branchpoint-1470-g [...] discards 74cc5af8298 213: onsuccess: #28: 1: Success after binutils/gcc/linux/gd [...] discards e823cd587a3 212: force: #27: : Failure after baseline build: no new commits discards e4b2322863a 211: onsuccess: #20: 1: Success after binutils/gcc/linux/gl [...] discards c1806d2636c 210: onsuccess: #19: 1: Success after binutils/gcc/linux/gl [...] discards 7ae2b412f26 209: onsuccess: #18: 1: Success after binutils/gcc/linux/gl [...] discards a220aa59cae 208: onsuccess: #17: 1: Success after binutils/gcc/linux/gd [...] discards 0758fb66e61 207: onsuccess: #16: 1: Success after binutils/gcc/linux/gl [...] discards 73a0460632c 206: onsuccess: #15: 1: Success after binutils/gcc/linux/gd [...] discards 61d6f7a239f 205: onsuccess: #14: 1: Success after binutils/gcc/linux/gl [...] discards 99694e135bc 204: onsuccess: #12: 1: Success after binutils/gcc/linux/gl [...] discards 90e855cf4cc 203: onsuccess: #11: 1: Success after binutils/gcc/linux/gd [...] discards d1be582a639 202: onsuccess: #10: 1: Success after binutils/gcc/linux/gd [...] discards c2b3dcf71c5 201: onsuccess: #9: 1: Success after binutils/gcc/linux/gdb [...] discards 79e66421c9c 200: onsuccess: #8: 1: Success after binutils/gcc/linux/gli [...] discards fb73f935f3e 199: onsuccess: #7: 1: Success after binutils/gcc/linux/gli [...] discards 48ac593bd25 198: onsuccess: #6: 1: Success after binutils/gcc/linux/gli [...] discards b268b191408 197: onsuccess: #5: 1: Success after binutils/gcc/linux/gli [...] discards e6ef9e7e656 196: onsuccess: #4: 1: Success after binutils/gcc/linux/gdb [...] discards 1ac4622912d 195: onsuccess: #3: 1: Success after binutils/gcc/linux/gli [...] discards 9dce3e0bcae 194: onsuccess: #2: 1: Success after binutils/gcc/linux/gdb [...] discards 2e687837379 193: onsuccess: #1: 1: Success after binutils/gcc/linux/gli [...] discards 0011c4506aa 192: onsuccess: #695: 1: Success after binutils/gcc/linux/g [...] discards 062843d9248 191: onsuccess: #694: 1: Success after binutils/gcc/linux/g [...] discards 1474590f3e6 190: onsuccess: #693: 1: Success after binutils/gcc/linux/g [...] discards 5cfba8fde42 189: onsuccess: #683: 1: Success after binutils/gcc/linux/g [...] discards 27240afe69b 188: onsuccess: #682: 1: Success after binutils/gcc/linux/g [...] discards 59ee3771c62 187: onsuccess: #681: 1: Success after binutils/gcc/linux/g [...] discards 46a54cf6bae 186: onsuccess: #680: 1: Success after binutils/gcc/linux/g [...] discards 6f19cf404f8 185: onsuccess: #679: 1: Success after binutils/gcc/linux/g [...] discards ba0575bf7fd 184: onsuccess: #678: 1: Success after binutils/gcc/glibc/g [...] discards 76c19a49f8a 183: onsuccess: #677: 1: Success after binutils/gcc/linux/g [...] discards 6d82da5054c 182: onsuccess: #676: 1: Success after binutils/gcc/linux/g [...] discards 23e5b0bf41b 181: onsuccess: #675: 1: Success after binutils/gcc/linux/g [...] discards 4954ab7933f 180: onsuccess: #674: 1: Success after binutils/gcc/linux/g [...] discards 25f87b31cd5 179: onsuccess: #673: 1: Success after binutils/gcc/linux/g [...] discards 71df560a079 178: onsuccess: #672: 1: Success after binutils/gcc/linux/g [...] discards 8cceff3798d 177: onsuccess: #671: 1: Success after binutils/gcc/linux/g [...] discards c3585fd67d9 176: onsuccess: #670: 1: Success after binutils/gcc/linux/g [...] discards b179ae05a44 175: onsuccess: #669: 1: Success after binutils/gcc/linux/g [...] discards b8a24010f0c 174: onsuccess: #668: 1: Success after binutils/gcc/linux/g [...] discards c6020674758 173: onsuccess: #667: 1: Success after binutils/gcc/gdb: 18 [...] discards 310852dca42 172: onsuccess: #666: 1: Success after binutils/gcc/linux/g [...] discards 430bdc73101 171: onsuccess: #665: 1: Success after binutils/gcc/linux/g [...] discards fc4bfa199fd 170: onsuccess: #664: 1: Success after binutils/gcc/linux/g [...] discards 259250547cf 169: onsuccess: #663: 1: Success after binutils/gcc/linux/g [...] discards af42f0f736b 168: onsuccess: #662: 1: Success after binutils/gcc/linux/g [...] discards 81dafb7c2b8 167: onsuccess: #661: 1: Success after binutils/gcc/linux/g [...] discards 4c00846d12e 166: onsuccess: #660: 1: Success after binutils/gcc/linux/g [...] discards 4e03864e5a0 165: onsuccess: #659: 1: Success after binutils/gcc/linux/g [...] discards 394dc782270 164: onsuccess: #658: 1: Success after binutils/gcc/linux/g [...] discards 2f9816751a4 163: onsuccess: #657: 1: Success after binutils/gcc/linux/g [...] discards 1a313b9ac35 162: onsuccess: #656: 1: Success after binutils/gcc/linux/g [...] discards adad544cfcb 161: onsuccess: #655: 1: Success after binutils/gcc/linux/g [...] discards 3169b9e0086 160: onsuccess: #654: 1: Success after binutils/gcc/linux/g [...] discards 21708fa791f 159: onsuccess: #653: 1: Success after binutils/gcc/linux/g [...] discards 43d65d4fbc5 158: onsuccess: #652: 1: Success after binutils/gcc/linux/g [...] discards 04466964537 157: onsuccess: #651: 1: Success after binutils/gcc/linux/g [...] discards beab48b1fcc 156: onsuccess: #650: 1: Success after binutils/gcc/linux/g [...] discards 49b4b9f4273 155: onsuccess: #649: 1: Success after binutils/gcc/linux/g [...] discards ee0a843d5fd 154: onsuccess: #648: 1: Success after binutils/gcc/glibc/g [...] discards 58e53bd1103 153: onsuccess: #647: 1: Success after binutils/gcc/linux/g [...] discards 3693b4bcecf 152: onsuccess: #645: 1: Success after binutils/gcc/linux/g [...] discards 6a2e3f44e1b 151: onsuccess: #643: 1: Success after binutils/gcc/linux/g [...] discards b32561f5bb5 150: onsuccess: #642: 1: Success after binutils/gcc/linux/g [...] discards 05568d35dc6 149: onsuccess: #641: 1: Success after binutils/gcc/linux/g [...] discards 978adba5937 148: onsuccess: #640: 1: Success after binutils/gcc/gdb: 7 commits discards 302d74dafbc 147: onsuccess: #639: 1: Success after binutils/gcc/gdb: 19 [...] discards 4f58fc99118 146: onsuccess: #638: 1: Success after binutils/gcc/gdb: 35 [...] discards cc08142dd53 145: onsuccess: #637: 1: Success after binutils/gcc/linux/g [...] discards 06091e8e9f4 144: onsuccess: #636: 1: Success after binutils/gcc/gdb: 47 [...] discards b031020047b 143: onsuccess: #635: 1: Success after binutils/gcc/linux/g [...] discards 47881f1d8e1 142: onsuccess: #634: 1: Success after binutils/gcc/linux/g [...] discards 432507f5605 141: onsuccess: #633: 1: Success after binutils/gcc/linux/g [...] discards 0c6a791220f 140: onsuccess: #631: 1: Success after binutils/gcc/linux/g [...] discards c8134c9ff79 139: onsuccess: #629: 1: Success after binutils/gcc/linux/g [...] discards 356298aa850 138: onsuccess: #628: 1: Success after binutils/gcc/linux/g [...] discards 7d8e9835a5a 137: onsuccess: #627: 1: Success after binutils/gcc/gdb: 14 [...] discards 2bb6e503c32 136: onsuccess: #626: 1: Success after binutils/gcc/linux/g [...] discards d8fff820090 135: onsuccess: #625: 1: Success after binutils/gcc/linux/g [...] discards c355c247d96 134: onsuccess: #624: 1: Success after binutils/gcc/linux/g [...] discards 325a4efa125 133: onsuccess: #623: 1: Success after binutils/gcc/linux/g [...] discards a6e4899e55a 132: onsuccess: #622: 1: Success after binutils/gcc/linux/g [...] discards 21df92ea21d 131: onsuccess: #621: 1: Success after binutils/gcc/linux/g [...] new 6580d984d76 131: onsuccess: #621: 1: Success after binutils/gcc/linux/g [...] new 77275994b47 132: onsuccess: #622: 1: Success after binutils/gcc/linux/g [...] new 3e3abc507b4 133: onsuccess: #623: 1: Success after binutils/gcc/linux/g [...] new 42a50708170 134: onsuccess: #624: 1: Success after binutils/gcc/linux/g [...] new 5c272fa575c 135: onsuccess: #625: 1: Success after binutils/gcc/linux/g [...] new 901fe343402 136: onsuccess: #626: 1: Success after binutils/gcc/linux/g [...] new e3f93ce5393 137: onsuccess: #627: 1: Success after binutils/gcc/gdb: 14 [...] new 28e8748a351 138: onsuccess: #628: 1: Success after binutils/gcc/linux/g [...] new 774fe7b4af0 139: onsuccess: #629: 1: Success after binutils/gcc/linux/g [...] new 55a01a87704 140: onsuccess: #631: 1: Success after binutils/gcc/linux/g [...] new c70f13a8109 141: onsuccess: #633: 1: Success after binutils/gcc/linux/g [...] new 0ff48f9001c 142: onsuccess: #634: 1: Success after binutils/gcc/linux/g [...] new fff0194bbd1 143: onsuccess: #635: 1: Success after binutils/gcc/linux/g [...] new 2f4781a4441 144: onsuccess: #636: 1: Success after binutils/gcc/gdb: 47 [...] new bbc831e16bc 145: onsuccess: #637: 1: Success after binutils/gcc/linux/g [...] new 15b657b7c93 146: onsuccess: #638: 1: Success after binutils/gcc/gdb: 35 [...] new 938ae107bdf 147: onsuccess: #639: 1: Success after binutils/gcc/gdb: 19 [...] new 32f34a5171c 148: onsuccess: #640: 1: Success after binutils/gcc/gdb: 7 commits new 5ecbe6b0f83 149: onsuccess: #641: 1: Success after binutils/gcc/linux/g [...] new 32db60a7997 150: onsuccess: #642: 1: Success after binutils/gcc/linux/g [...] new 9388cfd43dc 151: onsuccess: #643: 1: Success after binutils/gcc/linux/g [...] new 77261ec2b69 152: onsuccess: #645: 1: Success after binutils/gcc/linux/g [...] new a7f661cef69 153: onsuccess: #647: 1: Success after binutils/gcc/linux/g [...] new 64b0783c127 154: onsuccess: #648: 1: Success after binutils/gcc/glibc/g [...] new 41265fabc1e 155: onsuccess: #649: 1: Success after binutils/gcc/linux/g [...] new 53b86b26578 156: onsuccess: #650: 1: Success after binutils/gcc/linux/g [...] new f38ab3941dd 157: onsuccess: #651: 1: Success after binutils/gcc/linux/g [...] new a5000431b66 158: onsuccess: #652: 1: Success after binutils/gcc/linux/g [...] new 15ae8ad124d 159: onsuccess: #653: 1: Success after binutils/gcc/linux/g [...] new 92700f792cb 160: onsuccess: #654: 1: Success after binutils/gcc/linux/g [...] new 046b1994e6d 161: onsuccess: #655: 1: Success after binutils/gcc/linux/g [...] new 8173cb6a242 162: onsuccess: #656: 1: Success after binutils/gcc/linux/g [...] new 225f437f2df 163: onsuccess: #657: 1: Success after binutils/gcc/linux/g [...] new 6c5d4f0a874 164: onsuccess: #658: 1: Success after binutils/gcc/linux/g [...] new dfa8d876bf9 165: onsuccess: #659: 1: Success after binutils/gcc/linux/g [...] new ecc93bb2e82 166: onsuccess: #660: 1: Success after binutils/gcc/linux/g [...] new 6f852f84b66 167: onsuccess: #661: 1: Success after binutils/gcc/linux/g [...] new 6557abf9563 168: onsuccess: #662: 1: Success after binutils/gcc/linux/g [...] new 174597bbd01 169: onsuccess: #663: 1: Success after binutils/gcc/linux/g [...] new 9b48d43b410 170: onsuccess: #664: 1: Success after binutils/gcc/linux/g [...] new d86fb056037 171: onsuccess: #665: 1: Success after binutils/gcc/linux/g [...] new 1e329ef04b5 172: onsuccess: #666: 1: Success after binutils/gcc/linux/g [...] new 6700e8a544c 173: onsuccess: #667: 1: Success after binutils/gcc/gdb: 18 [...] new 9e6cf6351a5 174: onsuccess: #668: 1: Success after binutils/gcc/linux/g [...] new 937848ce337 175: onsuccess: #669: 1: Success after binutils/gcc/linux/g [...] new 4140b1b770d 176: onsuccess: #670: 1: Success after binutils/gcc/linux/g [...] new 2da7b16a08f 177: onsuccess: #671: 1: Success after binutils/gcc/linux/g [...] new 17c8f10e4f9 178: onsuccess: #672: 1: Success after binutils/gcc/linux/g [...] new 13ab67fd95a 179: onsuccess: #673: 1: Success after binutils/gcc/linux/g [...] new 26313a60086 180: onsuccess: #674: 1: Success after binutils/gcc/linux/g [...] new 602dadc8aab 181: onsuccess: #675: 1: Success after binutils/gcc/linux/g [...] new 76eab9a6cf6 182: onsuccess: #676: 1: Success after binutils/gcc/linux/g [...] new 778db42c17c 183: onsuccess: #677: 1: Success after binutils/gcc/linux/g [...] new 1f363c28f32 184: onsuccess: #678: 1: Success after binutils/gcc/glibc/g [...] new ddc7fe0f6d0 185: onsuccess: #679: 1: Success after binutils/gcc/linux/g [...] new 4d5dd9a9185 186: onsuccess: #680: 1: Success after binutils/gcc/linux/g [...] new febc7a0966f 187: onsuccess: #681: 1: Success after binutils/gcc/linux/g [...] new 60caf904e00 188: onsuccess: #682: 1: Success after binutils/gcc/linux/g [...] new 5d6c732b7a1 189: onsuccess: #683: 1: Success after binutils/gcc/linux/g [...] new a4648ba60b7 190: onsuccess: #693: 1: Success after binutils/gcc/linux/g [...] new df9518e8d44 191: onsuccess: #694: 1: Success after binutils/gcc/linux/g [...] new bc7d7f1d055 192: onsuccess: #695: 1: Success after binutils/gcc/linux/g [...] new a19ff7cfa2c 193: onsuccess: #1: 1: Success after binutils/gcc/linux/gli [...] new 4909a26d0c9 194: onsuccess: #2: 1: Success after binutils/gcc/linux/gdb [...] new 539d43fa958 195: onsuccess: #3: 1: Success after binutils/gcc/linux/gli [...] new 4cad0455ff2 196: onsuccess: #4: 1: Success after binutils/gcc/linux/gdb [...] new d9d29fcd8a0 197: onsuccess: #5: 1: Success after binutils/gcc/linux/gli [...] new a9502971f71 198: onsuccess: #6: 1: Success after binutils/gcc/linux/gli [...] new cb332d45fd8 199: onsuccess: #7: 1: Success after binutils/gcc/linux/gli [...] new eb845b39b2e 200: onsuccess: #8: 1: Success after binutils/gcc/linux/gli [...] new 5dbbb89000f 201: onsuccess: #9: 1: Success after binutils/gcc/linux/gdb [...] new 358b224898c 202: onsuccess: #10: 1: Success after binutils/gcc/linux/gd [...] new 1beea157dac 203: onsuccess: #11: 1: Success after binutils/gcc/linux/gd [...] new 000cd533bdd 204: onsuccess: #12: 1: Success after binutils/gcc/linux/gl [...] new 36e7e685124 205: onsuccess: #14: 1: Success after binutils/gcc/linux/gl [...] new efe02801fe9 206: onsuccess: #15: 1: Success after binutils/gcc/linux/gd [...] new 930ba52c92e 207: onsuccess: #16: 1: Success after binutils/gcc/linux/gl [...] new c5f492054da 208: onsuccess: #17: 1: Success after binutils/gcc/linux/gd [...] new df01ccd4498 209: onsuccess: #18: 1: Success after binutils/gcc/linux/gl [...] new 2972c792b33 210: onsuccess: #19: 1: Success after binutils/gcc/linux/gl [...] new 64268be1bc0 211: onsuccess: #20: 1: Success after binutils/gcc/linux/gl [...] new 46fc9bddbc1 212: force: #27: : Failure after baseline build: no new commits new 30455faa0b5 213: onsuccess: #28: 1: Success after binutils/gcc/linux/gd [...] new f2b3da8de13 214: force: #39: 1: Failure after gdb-13-branchpoint-1470-g [...] new 5d56917a495 215: force: #41: 1: Failure after gdb-13-branchpoint-1470-g [...] new d37e4c7f474 216: force: #43: : Failure after baseline build: no new commits new 2ad782bd95a 217: force: #45: 1: Success after linux: 1 commits new 7e7f65b56c3 218: force: #48: 1: Success after gdb-13-branchpoint-1471-g [...] new ae32327da9f 219: force: #50: 1: Failure after linux: 2520 commits new e32453f94cb 220: force: #51: 1: Success after v6.2-rc6-1149-g5b49da02dd [...] new 57e7a34ec00 221: force: #53: 1: Success after gdb-13-branchpoint-1472-g [...] new afcd278ea90 222: force: #60: 1: Success after gdb: 16 commits new 4f8546fad6f 223: force: #63: 1: Failure after gdb-13-branchpoint-1489-g [...] new 814d8beeef0 224: force: #65: 1: Success after gdb: 50 commits new b47c522bc55 225: force: #68: 1: Failure after gdb-13-branchpoint-1540-g [...] new 738f5dafe31 226: force: #70: 1: Success after baseline build: no new commits new 7f498dd2426 227: onsuccess: #72: 1: Success after binutils/gcc/linux/gl [...] new 5a8c417a1ee 228: force: #74: 1: Success after gdb: 53 commits new 7f7c4367fb3 229: force: #77: 1: Failure after gdb-13-branchpoint-1594-g [...] new e25eb1d12e2 230: onsuccess: #78: 1: Success after gdb: 2 commits new ca18ce7724d 231: force: #89: 1: [TCWG CI] Failure after gdb: 31 commits new d48e49aefae 232: force: #90: 1: [TCWG CI] Failure after gdb-13-branchpo [...] 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 (9b2397a6d6c) \ 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 2008 -> 1968 bytes 02-prepare_abe/console.log.xz | Bin 2528 -> 2528 bytes 03-build_abe-binutils/console.log.xz | Bin 49220 -> 48976 bytes 04-build_abe-gcc/console.log.xz | Bin 234368 -> 234616 bytes 06-build_abe-linux/console.log.xz | Bin 8472 -> 8476 bytes 07-build_abe-glibc/console.log.xz | Bin 234128 -> 234328 bytes 08-build_abe-gdb/console.log.xz | Bin 48848 -> 47548 bytes 09-build_abe-dejagnu/console.log.xz | Bin 3820 -> 3772 bytes 10-build_abe-check_gdb/console.log.xz | Bin 4588 -> 4368 bytes 11-check_regression/console.log.xz | Bin 3636 -> 3920 bytes 11-check_regression/extra-bisect-params | 2 +- 11-check_regression/fails.sum | 11 +- 11-check_regression/results.compare | 17 + 11-check_regression/results.regressions | 17 + 11-check_regression/trigger-bisect | 4 +- 11-check_regression/trigger-notify | 0 12-update_baseline/console.log | 36 +- 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 +- manifest.sh | 12 +- results | 17 + sumfiles/gdb.log.0.xz | Bin 2887436 -> 2881008 bytes sumfiles/gdb.log.1.xz | Bin 187828 -> 143244 bytes sumfiles/gdb.log.10.xz | Bin 10312 -> 0 bytes sumfiles/gdb.log.2.xz | Bin 20256 -> 15568 bytes sumfiles/gdb.log.3.xz | Bin 14916 -> 0 bytes sumfiles/gdb.log.4.xz | Bin 14976 -> 0 bytes sumfiles/gdb.log.5.xz | Bin 14936 -> 0 bytes sumfiles/gdb.log.6.xz | Bin 10360 -> 0 bytes sumfiles/gdb.log.7.xz | Bin 10264 -> 0 bytes sumfiles/gdb.log.8.xz | Bin 10252 -> 0 bytes sumfiles/gdb.log.9.xz | Bin 10364 -> 0 bytes sumfiles/gdb.sum | 1948 ++++++- sumfiles/gdb.sum.0 | 1970 +++++++- sumfiles/gdb.sum.1 | 8408 +------------------------------ sumfiles/gdb.sum.10 | 2167 -------- sumfiles/gdb.sum.2 | 219 +- sumfiles/gdb.sum.3 | 2356 --------- sumfiles/gdb.sum.4 | 2344 --------- sumfiles/gdb.sum.5 | 2414 --------- sumfiles/gdb.sum.6 | 2187 -------- sumfiles/gdb.sum.7 | 2189 -------- sumfiles/gdb.sum.8 | 2166 -------- sumfiles/gdb.sum.9 | 2191 -------- 47 files changed, 3899 insertions(+), 26796 deletions(-) create mode 100644 11-check_regression/trigger-notify create mode 100755 jenkins/notify.sh delete mode 100644 sumfiles/gdb.log.10.xz delete mode 100644 sumfiles/gdb.log.3.xz delete mode 100644 sumfiles/gdb.log.4.xz delete mode 100644 sumfiles/gdb.log.5.xz delete mode 100644 sumfiles/gdb.log.6.xz delete mode 100644 sumfiles/gdb.log.7.xz delete mode 100644 sumfiles/gdb.log.8.xz delete mode 100644 sumfiles/gdb.log.9.xz delete mode 100644 sumfiles/gdb.sum.10 delete mode 100644 sumfiles/gdb.sum.3 delete mode 100644 sumfiles/gdb.sum.4 delete mode 100644 sumfiles/gdb.sum.5 delete mode 100644 sumfiles/gdb.sum.6 delete mode 100644 sumfiles/gdb.sum.7 delete mode 100644 sumfiles/gdb.sum.8 delete mode 100644 sumfiles/gdb.sum.9 -- To stop receiving notification emails like this one, please contact the administrator of this repository.

1 year, 9 months

[toolchain/ci/interesting-commits] branch master updated (3545e8b7 -> d13f1e40)

by tcwg-buildslave

This is an automated email from the git hooks/post-receive script. "tcwg-buildslave pushed a change to branch master in repository toolchain/ci/interesting-commits. from 3545e8b7 Add entry 4bfcb286dd1f85f74616f169b4ca9db7677fab5b from https [...] new d13f1e40 Add entry 303a881f8789733248f27af0c872d356a34be009 from https [...] The 1 revisions listed above as "new" are entirely new to this repository and will be described in separate emails. The revisions listed as "adds" were already present in the repository and have only been added to this reference. Summary of changes: gdb/gdb-13-branchpoint-1628-g303a881f878 | 1 + .../tcwg_gnu_native_check_gdb/master-arm/build_url | 2 +- .../tcwg_gnu_native_check_gdb/master-arm/last_good | 1 + .../master-arm/summary.txt | 105 ++++++++++++++++++ .../tcwg_gnu_native_check_gdb/status.txt | 121 +++++++++++++++++++++ 5 files changed, 229 insertions(+), 1 deletion(-) create mode 120000 gdb/gdb-13-branchpoint-1628-g303a881f878 copy {binutils/sha1/14317f7f05d0290586f456d02176dd77a81aee69 => gdb/sha1/303a881f8 [...] create mode 100644 gdb/sha1/303a881f8789733248f27af0c872d356a34be009/tcwg_gnu_nati [...] create mode 100644 gdb/sha1/303a881f8789733248f27af0c872d356a34be009/tcwg_gnu_nati [...] create mode 100644 gdb/sha1/303a881f8789733248f27af0c872d356a34be009/tcwg_gnu_nati [...] -- To stop receiving notification emails like this one, please contact the administrator of this repository.

1 year, 9 months

Jump to page:

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

Tcwg-commits March 2023