Tcwg-commits April 2023

tcwg-commits@lists.linaro.org

5 participants
5583 discussions

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_bmk-code_size-spec2k6/llvm-aarch64-master-Oz updated (7b026d33ff71 -> 29751ac5a850)

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-aarch64-master-Oz in repository toolchain/ci/base-artifacts. from 7b026d33ff71 54: force: #14: 1: [TCWG CI] Failure after llvmorg-17-init [...] new 29751ac5a850 55: onsuccess: #15: 1: [TCWG CI] Success after llvm: 216 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 1848 -> 1992 bytes 02-build_bmk_llvm/console.log.xz | Bin 99860 -> 100252 bytes 03-benchmark/benchmark-build.log | 84 +- 03-benchmark/benchmark.log | 82 +- 03-benchmark/console.log.xz | Bin 3780 -> 3756 bytes .../compare-results-vs-first-internal.csv | 130 +- .../compare-results-vs-prev-internal.csv | 147 +- 04-check_regression/console.log.xz | Bin 10864 -> 10736 bytes .../csv-results-vs-first-1/md5sum.csv | 1749 +- .../csv-results-vs-first-1/perf.csv | 2064 +- .../csv-results-vs-first-1/results.csv | 2574 +- .../csv-results-vs-first-1/size.csv | 45492 ++++++++-------- 04-check_regression/csv-results-vs-first-1/sve.csv | 18 +- .../csv-results-vs-prev-0/md5sum.csv | 1753 +- 04-check_regression/csv-results-vs-prev-0/perf.csv | 2056 +- .../csv-results-vs-prev-0/results.csv | 10394 ++-- 04-check_regression/csv-results-vs-prev-0/size.csv | 52714 ++++++++++--------- 04-check_regression/csv-results-vs-prev-0/sve.csv | 18 +- .../csv-results-vs-prev-1/md5sum.csv | 1749 +- 04-check_regression/csv-results-vs-prev-1/perf.csv | 2064 +- .../csv-results-vs-prev-1/results.csv | 2574 +- 04-check_regression/csv-results-vs-prev-1/size.csv | 45492 ++++++++-------- 04-check_regression/csv-results-vs-prev-1/sve.csv | 18 +- 04-check_regression/exe.regression | 1 - 04-check_regression/extra-bisect-params | 2 +- 04-check_regression/mail-body.txt | 3 - 04-check_regression/mail-subject.txt | 2 +- .../output-bmk-results/exe.regression.diff | 1 - 04-check_regression/results-vs-first-brief.csv | 40 +- 04-check_regression/results-vs-first-full.csv | 1966 +- 04-check_regression/results-vs-first-internal.csv | 130 +- 04-check_regression/results-vs-first.csv | 130 +- 04-check_regression/results-vs-first.log | 1116 +- 04-check_regression/results-vs-prev-brief.csv | 40 +- 04-check_regression/results-vs-prev-compare.csv | 14 +- 04-check_regression/results-vs-prev-full.csv | 2108 +- 04-check_regression/results-vs-prev-internal.csv | 134 +- 04-check_regression/results-vs-prev.csv | 134 +- 04-check_regression/results-vs-prev.log | 1338 +- 04-check_regression/results.regressions | 17 - 04-check_regression/trigger-bisect | 3 - 04-check_regression/trigger-notify | 0 05-update_baseline/console.log | 2 +- dashboard/dashboard-generate.sh | 2 +- .../400.perlbench/results-metadata.json | 8 +- .../squad-vs-first/401.bzip2/results-metadata.json | 8 +- .../squad-vs-first/403.gcc/results-metadata.json | 8 +- .../410.bwaves/results-metadata.json | 8 +- .../416.gamess/results-metadata.json | 8 +- .../squad-vs-first/429.mcf/results-metadata.json | 8 +- .../squad-vs-first/433.milc/results-metadata.json | 8 +- .../434.zeusmp/results-metadata.json | 8 +- .../435.gromacs/results-metadata.json | 8 +- .../436.cactusADM/results-metadata.json | 8 +- .../437.leslie3d/results-metadata.json | 8 +- .../squad-vs-first/444.namd/results-metadata.json | 8 +- .../squad-vs-first/445.gobmk/results-metadata.json | 8 +- .../447.dealII/results-metadata.json | 8 +- .../450.soplex/results-metadata.json | 8 +- .../453.povray/results-metadata.json | 8 +- .../454.calculix/results-metadata.json | 8 +- .../squad-vs-first/456.hmmer/results-metadata.json | 8 +- .../squad-vs-first/458.sjeng/results-metadata.json | 8 +- .../459.GemsFDTD/results-metadata.json | 8 +- .../462.libquantum/results-metadata.json | 8 +- .../464.h264ref/results-metadata.json | 8 +- .../squad-vs-first/465.tonto/results-metadata.json | 8 +- .../squad-vs-first/470.lbm/results-metadata.json | 8 +- .../471.omnetpp/results-metadata.json | 8 +- .../squad-vs-first/473.astar/results-metadata.json | 8 +- .../squad-vs-first/481.wrf/results-metadata.json | 8 +- .../482.sphinx3/results-metadata.json | 8 +- .../483.xalancbmk/results-metadata.json | 8 +- .../squad-vs-first/Mean/results-metadata.json | 8 +- dashboard/squad-vs-first/dashboard-push-squad.sh | 122 +- git/llvm_rev | 2 +- jenkins/notify.sh | 3 - mail/changes-list-long.txt | 11 +- mail/changes-list-short.txt | 2 +- mail/last_good.sh | 12 +- mail/short-diag.txt | 2 +- manifest.sh | 14 +- results | 17 - results_id | 2 +- 84 files changed, 89418 insertions(+), 89364 deletions(-) delete mode 100644 04-check_regression/exe.regression delete mode 100644 04-check_regression/output-bmk-results/exe.regression.diff delete mode 100644 04-check_regression/results.regressions delete mode 100644 04-check_regression/trigger-bisect delete mode 100644 04-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, 7 months

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_aosp-build-aosp/oriole-master updated (74d5aa793e10 -> 4b0a2a8f7e55)

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-build-aosp/oriole-master in repository toolchain/ci/base-artifacts. from 74d5aa793e10 8: onsuccess: #39: 5: [TCWG CI] Success after aosp_superpr [...] new 4b0a2a8f7e55 9: onsuccess: #40: 5: [TCWG CI] Success after aosp_superpr [...] 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 2168 -> 1940 bytes 02-build_aosp_toolchain/console.log.xz | Bin 197864 -> 196624 bytes 03-build_shadow_llvm/console.log.xz | Bin 131200 -> 130972 bytes 04-build_aosp/console.log.xz | Bin 1289816 -> 1269392 bytes 05-process_shadow_data/console.log.xz | Bin 272 -> 272 bytes 06-check_regression/binary.regressions | 6 - 06-check_regression/console.log.xz | Bin 46836 -> 44724 bytes 06-check_regression/results-vs-first.csv | 2 +- 06-check_regression/results-vs-prev.csv | 1750 ++++++++++++++-------------- 06-check_regression/results.regressions | 1 - dashboard/dashboard-generate.sh | 2 +- git/aosp_superproject_rev | 2 +- git/llvm_rev | 2 +- git/toolchain_superproject_rev | 2 +- mail/changes-list-long.txt | 30 +- mail/changes-list-short.txt | 2 +- mail/last_good.sh | 24 +- manifest.sh | 24 +- results | 1 - size.csv | 1842 +++++++++++++++--------------- 20 files changed, 1839 insertions(+), 1851 deletions(-) delete mode 100644 06-check_regression/binary.regressions delete mode 100644 06-check_regression/results.regressions -- To stop receiving notification emails like this one, please contact the administrator of this repository.

1 year, 7 months

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_kernel/gnu-master-arm-lts-allmodconfig updated (3bd539fefff4 -> eb641b29e71c)

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-lts-allmodconfig in repository toolchain/ci/base-artifacts. from 3bd539fefff4 55: onsuccess: #8: 33: Success after binutils/gcc/linux/qe [...] new eb641b29e71c 56: onsuccess: #9: 33: [TCWG CI] Success after binutils/gc [...] The 1 revisions listed above as "new" are entirely new to this repository and will be described in separate emails. The revisions listed as "adds" were already present in the repository and have only been added to this reference. Summary of changes: 01-reset_artifacts/console.log.xz | Bin 2004 -> 2008 bytes 02-prepare_abe/console.log.xz | Bin 2512 -> 2580 bytes 03-build_abe-binutils/console.log.xz | Bin 27380 -> 27792 bytes 04-build_abe-stage1/console.log.xz | Bin 89040 -> 90472 bytes 05-build_abe-qemu/console.log.xz | Bin 31964 -> 32220 bytes 06-build_linux/console.log.xz | Bin 4692 -> 4900 bytes 08-check_regression/console.log.xz | Bin 4336 -> 4268 bytes 08-check_regression/mail-body.txt | 23 ----------------------- 08-check_regression/mail-subject.txt | 1 - dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- git/linux_rev | 2 +- git/qemu_rev | 2 +- mail/changes-list-long.txt | 26 ++++++++++++++++++++++++++ mail/changes-list-short.txt | 1 + manifest.sh => mail/last_good.sh | 0 mail/mail-body.txt | 23 ----------------------- mail/mail-subject.txt | 1 - mail/short-diag.txt | 1 + manifest.sh | 32 ++++++++++++++++---------------- 21 files changed, 49 insertions(+), 69 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 copy manifest.sh => mail/last_good.sh (100%) delete mode 100644 mail/mail-body.txt delete mode 100644 mail/mail-subject.txt create mode 100644 mail/short-diag.txt -- To stop receiving notification emails like this one, please contact the administrator of this repository.

1 year, 7 months

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_gnu_native_build/master-arm updated (1791c286df01 -> 73f3fcd3ccec)

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_build/master-arm in repository toolchain/ci/base-artifacts. discards 1791c286df01 232: onsuccess: #41: 6: [TCWG CI] Success after binutils/g [...] discards e6b77de12bf4 231: onsuccess: #39: 6: [TCWG CI] Success after binutils/g [...] discards a02fa1623c29 230: onsuccess: #38: 6: [TCWG CI] Success after binutils/g [...] discards 39b100870bab 229: onsuccess: #37: 6: [TCWG CI] Success after binutils/g [...] discards 58a7d8f2fa1a 228: onsuccess: #35: 6: Success after binutils/gcc/linux/g [...] discards d4f6655335f1 227: onsuccess: #34: 6: Success after binutils/gcc/linux/g [...] discards def7e241b6bb 226: onsuccess: #32: 6: Success after binutils/gcc/linux/g [...] discards ce7270a0e938 225: onsuccess: #31: 6: Success after binutils/gcc/linux/g [...] discards 74b9bb838b1a 224: onsuccess: #30: 6: Success after binutils/gcc/linux/g [...] discards e42461425fbd 223: onsuccess: #29: 6: Success after binutils/gcc/linux/g [...] discards a3438f84b148 222: onsuccess: #28: 6: Success after binutils/gcc/linux/g [...] discards 5eb6c5ef46d5 221: onsuccess: #26: 6: Success after binutils/gcc/linux/g [...] discards 4a745dd49915 220: onsuccess: #25: 6: Success after binutils/gcc/linux/g [...] discards 31d185539b10 219: onsuccess: #24: 6: Success after binutils/gcc/linux/g [...] discards 3a653fe759e4 218: onsuccess: #23: 6: Success after binutils/gcc/linux/g [...] discards d5985f46b379 217: onsuccess: #22: 6: Success after binutils/gcc/linux/g [...] discards 8cc05736ec20 216: onsuccess: #21: 6: Success after binutils/gcc/linux/g [...] discards 58ceaedf973c 215: onsuccess: #20: 6: Success after binutils/gcc/linux/g [...] discards ff214b7fa385 214: onsuccess: #19: 6: Success after binutils/gcc/linux/g [...] discards 9dc2bb47af4b 213: onsuccess: #18: 6: Success after binutils/gcc/linux/g [...] discards 0d5db7210bf7 212: onsuccess: #17: 6: Success after binutils/gcc/linux/g [...] discards f93526d22aa5 211: onsuccess: #12: 6: Success after binutils/gcc/linux/g [...] discards 79213e58f7e3 210: onsuccess: #11: 6: Success after binutils/gcc/linux/g [...] discards fd6829d87b9f 209: onsuccess: #10: 6: Success after binutils/gcc/linux/g [...] discards 8b92c8b2ede8 208: onsuccess: #9: 6: Success after binutils/gcc/linux/gl [...] discards 8b217c1d8606 207: onsuccess: #8: 6: Success after binutils/gcc/linux/gl [...] discards 6b0cfb4d9ac8 206: onsuccess: #7: 6: Success after binutils/gcc/linux/gd [...] discards 220b8804e5df 205: onsuccess: #6: 6: Success after binutils/gcc/linux/gl [...] discards 2bd08ad4eefd 204: onsuccess: #5: 6: Success after binutils/gcc/linux/gl [...] discards 4e5dfe29ccc6 203: onsuccess: #4: 6: Success after binutils/gcc/linux/gl [...] discards 7ad0ea55b394 202: onsuccess: #3: 6: Success after binutils/gcc/linux/gd [...] discards ca6268af1eba 201: onsuccess: #2: 6: Success after binutils/gcc/linux/gl [...] discards 687def8f1578 200: onsuccess: #1: 6: Success after binutils/gcc/linux/gl [...] discards 47e12fc8dca0 199: onsuccess: #630: 6: Success after binutils/gcc/linux/ [...] discards c8f29066b095 198: onsuccess: #629: 6: Success after binutils/gcc/linux/ [...] discards 1eff548ff38c 197: onsuccess: #628: 6: Success after binutils/gcc/linux/ [...] discards f5532c61c024 196: onsuccess: #621: 6: Success after binutils/gcc/linux/ [...] discards ad4360968a01 195: onsuccess: #620: 6: Success after binutils/gcc/linux/ [...] discards 58cb04db5419 194: onsuccess: #619: 6: Success after binutils/gcc/linux/ [...] discards 0f94855972bf 193: onsuccess: #618: 6: Success after binutils/gcc/linux/ [...] discards 7a5436721ad6 192: onsuccess: #617: 6: Success after binutils/gcc/linux/ [...] discards 9f7528931167 191: onsuccess: #615: 6: Success after binutils/gcc/linux/ [...] discards 1eb76e6e48a7 190: onsuccess: #614: 6: Success after binutils/gcc/linux/ [...] discards c9d22c70b847 189: onsuccess: #613: 6: Success after binutils/gcc/linux/ [...] discards 9c046be48478 188: onsuccess: #612: 6: Success after binutils/gcc/linux/ [...] discards 5a2e1e039f91 187: onsuccess: #611: 6: Success after binutils/gcc/linux/ [...] discards e013e227afd4 186: onsuccess: #610: 6: Success after binutils/gcc/linux/ [...] discards 6d60941e6389 185: onsuccess: #609: 6: Success after binutils/gcc/linux/ [...] discards ee1abdb1c310 184: onsuccess: #608: 6: Success after binutils/gcc/linux/ [...] discards cf70f12a6f15 183: onsuccess: #607: 6: Success after binutils/gcc/linux/ [...] discards cd5bdcff615d 182: onsuccess: #606: 6: Success after binutils/gcc/linux/ [...] discards e0c4f92152e8 181: onsuccess: #605: 6: Success after binutils/gcc/linux/ [...] discards f1d6ace1c35e 180: onsuccess: #604: 6: Success after binutils/gcc/linux/ [...] discards 273adaf5e04d 179: onsuccess: #603: 6: Success after binutils/gcc/linux/ [...] discards 40f3f9368928 178: onsuccess: #602: 6: Success after binutils/gcc/linux/ [...] discards 7c1de59e48ca 177: onsuccess: #601: 6: Success after binutils/gcc/linux/ [...] discards f026fd9b893c 176: onsuccess: #600: 6: Success after binutils/gcc/linux/ [...] discards 9f722155a800 175: onsuccess: #599: 6: Success after binutils/gcc/linux/ [...] discards 959de4a3f3f1 174: onsuccess: #598: 6: Success after binutils/gcc/linux/ [...] discards a34415d544fe 173: onsuccess: #597: 6: Success after binutils/gcc/linux/ [...] discards 06737cf51ad5 172: onsuccess: #596: 6: Success after binutils/gcc/linux/ [...] discards ff4d2cae7ce5 171: onsuccess: #595: 6: Success after binutils/gcc/linux/ [...] discards e10841033c61 170: onsuccess: #594: 6: Success after binutils/gcc/linux/ [...] discards 4567c3daaba2 169: onsuccess: #593: 6: Success after binutils/gcc/linux/ [...] discards 030275158691 168: onsuccess: #591: 6: Success after binutils/gcc/linux/ [...] discards b4664c3b44d0 167: onsuccess: #590: 6: Success after binutils/gcc/linux/ [...] discards a7613446756a 166: onsuccess: #589: 6: Success after binutils/gcc/linux/ [...] discards d03fe89965e5 165: onsuccess: #588: 6: Success after binutils/gcc/linux/ [...] discards b761105305da 164: onsuccess: #587: 6: Success after binutils/gcc/glibc/ [...] discards 58450add5918 163: onsuccess: #586: 6: Success after binutils/gcc/linux/ [...] discards 9501bdcec044 162: onsuccess: #579: 6: Success after gcc: 11 commits discards 6e0b86303ab7 161: onsuccess: #578: 6: Success after binutils: 15 commits discards 386f2771b266 160: onsuccess: #576: 6: Success after binutils/gcc/linux/ [...] discards 70d2f5a7f56c 159: onsuccess: #575: 6: Success after binutils/gcc/linux/ [...] discards 4691d792baca 158: onsuccess: #574: 6: Success after binutils/gcc/linux/ [...] discards 2c91ae4e7640 157: onsuccess: #573: 6: Success after binutils/gcc/gdb: 9 [...] discards ee4da45f42bd 156: onsuccess: #572: 6: Success after binutils/gcc/gdb: 1 [...] discards 865266753c27 155: onsuccess: #571: 6: Success after binutils/gcc/gdb: 3 [...] discards bc6c35054a04 154: onsuccess: #570: 6: Success after binutils/gcc/linux/ [...] discards 30e59e5445c5 153: onsuccess: #569: 6: Success after binutils/gcc/gdb: 4 [...] discards 543e7a084df6 152: onsuccess: #568: 6: Success after binutils/gcc/linux/ [...] discards 9005a9fdd08a 151: onsuccess: #567: 6: Success after binutils/gcc/linux/ [...] discards 201bf868ee9f 150: onsuccess: #566: 6: Success after binutils/gcc/linux/ [...] discards 1ef9da898165 149: onsuccess: #565: 6: Success after binutils/gcc/linux/ [...] discards f411964a3238 148: onsuccess: #564: 6: Success after binutils/gcc/linux/ [...] discards d8716ec16696 147: onsuccess: #563: 6: Success after binutils/gcc/linux/ [...] discards 23f52729da4b 146: onsuccess: #562: 6: Success after binutils/gcc/gdb: 1 [...] discards 1d141c56c0be 145: onsuccess: #561: 6: Success after binutils/gcc/linux/ [...] discards e55951888c33 144: onsuccess: #560: 6: Success after binutils/gcc/linux/ [...] discards 6d557e39fcdc 143: onsuccess: #559: 6: Success after binutils/gcc/linux/ [...] discards 94b6fa0f24d9 142: onsuccess: #558: 6: Success after binutils/gcc/linux/ [...] discards e66491f817c5 141: onsuccess: #557: 6: Success after binutils/gcc/linux/ [...] discards 57b1a5e818de 140: onsuccess: #556: 6: Success after binutils/gcc/linux/ [...] discards 513bb803213d 139: onsuccess: #555: 6: Success after binutils/gcc/linux/ [...] discards 8c4f1190295a 138: onsuccess: #554: 6: Success after binutils/gcc/linux/ [...] discards 69c00e78839e 137: onsuccess: #553: 6: Success after binutils/gcc/linux/ [...] discards b1e7c717d751 136: onsuccess: #551: 6: Success after binutils/gcc/linux/ [...] discards bb2b8a9af745 135: onsuccess: #550: 6: Success after binutils/gcc/linux/ [...] discards fdff57eaa3e3 134: onsuccess: #544: 6: Success after binutils: 18 commits discards 488544ca855c 133: onsuccess: #542: 6: Success after binutils/gcc/linux/ [...] discards 5b9c34b9721c 132: onsuccess: #541: 6: Success after binutils/gcc/linux/ [...] new 0316ecdd73dc 132: onsuccess: #541: 6: Success after binutils/gcc/linux/ [...] new 9103e9d29408 133: onsuccess: #542: 6: Success after binutils/gcc/linux/ [...] new 11360c81d599 134: onsuccess: #544: 6: Success after binutils: 18 commits new 22fbf34cefff 135: onsuccess: #550: 6: Success after binutils/gcc/linux/ [...] new 0dc8ec4d65af 136: onsuccess: #551: 6: Success after binutils/gcc/linux/ [...] new 03586c0beb3a 137: onsuccess: #553: 6: Success after binutils/gcc/linux/ [...] new 6e7093f3bbea 138: onsuccess: #554: 6: Success after binutils/gcc/linux/ [...] new b2cba8b4f182 139: onsuccess: #555: 6: Success after binutils/gcc/linux/ [...] new 43c0b348ed2d 140: onsuccess: #556: 6: Success after binutils/gcc/linux/ [...] new 53628ea63690 141: onsuccess: #557: 6: Success after binutils/gcc/linux/ [...] new a58d45155c81 142: onsuccess: #558: 6: Success after binutils/gcc/linux/ [...] new 9e18eb635095 143: onsuccess: #559: 6: Success after binutils/gcc/linux/ [...] new 38ad47a259d7 144: onsuccess: #560: 6: Success after binutils/gcc/linux/ [...] new c977a4709f10 145: onsuccess: #561: 6: Success after binutils/gcc/linux/ [...] new 805f2c411f72 146: onsuccess: #562: 6: Success after binutils/gcc/gdb: 1 [...] new 60c1484dbf54 147: onsuccess: #563: 6: Success after binutils/gcc/linux/ [...] new 178af9cc176f 148: onsuccess: #564: 6: Success after binutils/gcc/linux/ [...] new 0edb68929190 149: onsuccess: #565: 6: Success after binutils/gcc/linux/ [...] new d1dcf429d07d 150: onsuccess: #566: 6: Success after binutils/gcc/linux/ [...] new 10984cd08fa3 151: onsuccess: #567: 6: Success after binutils/gcc/linux/ [...] new 9c8f619c6e7a 152: onsuccess: #568: 6: Success after binutils/gcc/linux/ [...] new a4237a9c90db 153: onsuccess: #569: 6: Success after binutils/gcc/gdb: 4 [...] new ff7301b5d491 154: onsuccess: #570: 6: Success after binutils/gcc/linux/ [...] new 01532af7ab32 155: onsuccess: #571: 6: Success after binutils/gcc/gdb: 3 [...] new 64e48aad5dd3 156: onsuccess: #572: 6: Success after binutils/gcc/gdb: 1 [...] new 03276c5cadfe 157: onsuccess: #573: 6: Success after binutils/gcc/gdb: 9 [...] new 51938983f66c 158: onsuccess: #574: 6: Success after binutils/gcc/linux/ [...] new a4667a9a39dd 159: onsuccess: #575: 6: Success after binutils/gcc/linux/ [...] new d0e83238e03c 160: onsuccess: #576: 6: Success after binutils/gcc/linux/ [...] new 52ed998ec7a8 161: onsuccess: #578: 6: Success after binutils: 15 commits new c7bc0b56fe30 162: onsuccess: #579: 6: Success after gcc: 11 commits new fec9c2f34a30 163: onsuccess: #586: 6: Success after binutils/gcc/linux/ [...] new a86b1adf4519 164: onsuccess: #587: 6: Success after binutils/gcc/glibc/ [...] new 68e662f0367c 165: onsuccess: #588: 6: Success after binutils/gcc/linux/ [...] new ccbd41730f90 166: onsuccess: #589: 6: Success after binutils/gcc/linux/ [...] new 7051c6a1dd95 167: onsuccess: #590: 6: Success after binutils/gcc/linux/ [...] new a1c2d92076da 168: onsuccess: #591: 6: Success after binutils/gcc/linux/ [...] new 8462d8b901fd 169: onsuccess: #593: 6: Success after binutils/gcc/linux/ [...] new 4954ef44fbc3 170: onsuccess: #594: 6: Success after binutils/gcc/linux/ [...] new 4e304f7c6fac 171: onsuccess: #595: 6: Success after binutils/gcc/linux/ [...] new 358248b34152 172: onsuccess: #596: 6: Success after binutils/gcc/linux/ [...] new 50b413144108 173: onsuccess: #597: 6: Success after binutils/gcc/linux/ [...] new 0fef40b7996c 174: onsuccess: #598: 6: Success after binutils/gcc/linux/ [...] new 734ce94f82aa 175: onsuccess: #599: 6: Success after binutils/gcc/linux/ [...] new f1475c0acb0b 176: onsuccess: #600: 6: Success after binutils/gcc/linux/ [...] new eb89c49c0596 177: onsuccess: #601: 6: Success after binutils/gcc/linux/ [...] new d081ebbc3a1b 178: onsuccess: #602: 6: Success after binutils/gcc/linux/ [...] new 158d823e9281 179: onsuccess: #603: 6: Success after binutils/gcc/linux/ [...] new 95db594ab6a7 180: onsuccess: #604: 6: Success after binutils/gcc/linux/ [...] new 19a486c67b0e 181: onsuccess: #605: 6: Success after binutils/gcc/linux/ [...] new f860373a020c 182: onsuccess: #606: 6: Success after binutils/gcc/linux/ [...] new 1a03fe618ad4 183: onsuccess: #607: 6: Success after binutils/gcc/linux/ [...] new 05c06026ae2c 184: onsuccess: #608: 6: Success after binutils/gcc/linux/ [...] new 6679cb644b4f 185: onsuccess: #609: 6: Success after binutils/gcc/linux/ [...] new 28122090e97b 186: onsuccess: #610: 6: Success after binutils/gcc/linux/ [...] new 1663722f22d0 187: onsuccess: #611: 6: Success after binutils/gcc/linux/ [...] new 68230c1cf9c9 188: onsuccess: #612: 6: Success after binutils/gcc/linux/ [...] new fa5d51b72ebc 189: onsuccess: #613: 6: Success after binutils/gcc/linux/ [...] new f8b879f03994 190: onsuccess: #614: 6: Success after binutils/gcc/linux/ [...] new a9879bdea583 191: onsuccess: #615: 6: Success after binutils/gcc/linux/ [...] new 513b3bea4108 192: onsuccess: #617: 6: Success after binutils/gcc/linux/ [...] new b53e89fbe29a 193: onsuccess: #618: 6: Success after binutils/gcc/linux/ [...] new 2b420425cc36 194: onsuccess: #619: 6: Success after binutils/gcc/linux/ [...] new d7d0e5da14b3 195: onsuccess: #620: 6: Success after binutils/gcc/linux/ [...] new 51a19e8cf11e 196: onsuccess: #621: 6: Success after binutils/gcc/linux/ [...] new fbcda585431b 197: onsuccess: #628: 6: Success after binutils/gcc/linux/ [...] new 6f2e7622b019 198: onsuccess: #629: 6: Success after binutils/gcc/linux/ [...] new b29f538549e4 199: onsuccess: #630: 6: Success after binutils/gcc/linux/ [...] new bf1c28dbaf98 200: onsuccess: #1: 6: Success after binutils/gcc/linux/gl [...] new 6d3607f5dbce 201: onsuccess: #2: 6: Success after binutils/gcc/linux/gl [...] new a7de3dbcebdc 202: onsuccess: #3: 6: Success after binutils/gcc/linux/gd [...] new 7da399605723 203: onsuccess: #4: 6: Success after binutils/gcc/linux/gl [...] new 5fb5b4c6a550 204: onsuccess: #5: 6: Success after binutils/gcc/linux/gl [...] new 73f37319c161 205: onsuccess: #6: 6: Success after binutils/gcc/linux/gl [...] new 4132c9650f38 206: onsuccess: #7: 6: Success after binutils/gcc/linux/gd [...] new e0af4c05af86 207: onsuccess: #8: 6: Success after binutils/gcc/linux/gl [...] new ea161ba12ebe 208: onsuccess: #9: 6: Success after binutils/gcc/linux/gl [...] new d98d2c9e1108 209: onsuccess: #10: 6: Success after binutils/gcc/linux/g [...] new af852befa9a3 210: onsuccess: #11: 6: Success after binutils/gcc/linux/g [...] new 937b525d1ee9 211: onsuccess: #12: 6: Success after binutils/gcc/linux/g [...] new 8cdb22f660fb 212: onsuccess: #17: 6: Success after binutils/gcc/linux/g [...] new d74289ecb21c 213: onsuccess: #18: 6: Success after binutils/gcc/linux/g [...] new 9617fb5e9ebe 214: onsuccess: #19: 6: Success after binutils/gcc/linux/g [...] new 4412c9f63b46 215: onsuccess: #20: 6: Success after binutils/gcc/linux/g [...] new edf2cd9cdd71 216: onsuccess: #21: 6: Success after binutils/gcc/linux/g [...] new 8e193dc3f2c0 217: onsuccess: #22: 6: Success after binutils/gcc/linux/g [...] new 399cff7cf74c 218: onsuccess: #23: 6: Success after binutils/gcc/linux/g [...] new 1c44ddc4a683 219: onsuccess: #24: 6: Success after binutils/gcc/linux/g [...] new b773058497f3 220: onsuccess: #25: 6: Success after binutils/gcc/linux/g [...] new 49efa9349610 221: onsuccess: #26: 6: Success after binutils/gcc/linux/g [...] new cf02b50f2ddb 222: onsuccess: #28: 6: Success after binutils/gcc/linux/g [...] new aae854637b34 223: onsuccess: #29: 6: Success after binutils/gcc/linux/g [...] new e35781494a5a 224: onsuccess: #30: 6: Success after binutils/gcc/linux/g [...] new 56aed8b1d63d 225: onsuccess: #31: 6: Success after binutils/gcc/linux/g [...] new 127ba48c6bbc 226: onsuccess: #32: 6: Success after binutils/gcc/linux/g [...] new 046128431141 227: onsuccess: #34: 6: Success after binutils/gcc/linux/g [...] new 9eabfcc7bdba 228: onsuccess: #35: 6: Success after binutils/gcc/linux/g [...] new 558c90fee1ea 229: onsuccess: #37: 6: [TCWG CI] Success after binutils/g [...] new 3ae2424274bc 230: onsuccess: #38: 6: [TCWG CI] Success after binutils/g [...] new 10bede93a875 231: onsuccess: #39: 6: [TCWG CI] Success after binutils/g [...] new 11eead66de16 232: onsuccess: #41: 6: [TCWG CI] Success after binutils/g [...] new 73f3fcd3ccec 233: onsuccess: #42: 6: [TCWG CI] Success after binutils/g [...] This update added new revisions after undoing existing revisions. That is to say, some revisions that were in the old version of the branch are not in the new version. This situation occurs when a user --force pushes a change and generates a repository containing something like this: * -- * -- B -- O -- O -- O (1791c286df01) \ N -- N -- N refs/heads/linaro-local/ci/tcwg_gnu_native_build/master- [...] 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 2208 -> 2076 bytes 02-prepare_abe/console.log.xz | Bin 2508 -> 2508 bytes 04-build_abe-binutils/console.log.xz | Bin 49064 -> 48852 bytes 05-build_abe-gcc/console.log.xz | Bin 237080 -> 237364 bytes 06-clean_sysroot/console.log.xz | Bin 316 -> 316 bytes 07-build_abe-linux/console.log.xz | Bin 8876 -> 8620 bytes 08-build_abe-glibc/console.log.xz | Bin 232596 -> 232568 bytes 09-build_abe-gdb/console.log.xz | Bin 48012 -> 47164 bytes 10-check_regression/console.log.xz | Bin 4284 -> 3608 bytes 11-update_baseline/console.log | 42 +++++++++++++++++------------------ dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- git/gdb_rev | 2 +- git/linux_rev | 2 +- mail/changes-list-long.txt | 38 ++++++++++--------------------- mail/changes-list-short.txt | 2 +- mail/last_good.sh | 36 +++++++++++++++--------------- manifest.sh | 32 +++++++++++++------------- 19 files changed, 73 insertions(+), 87 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

1 year, 7 months

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_gnu_native_check_gdb/master-aarch64 updated (d9212ed9fc21 -> c98fd389ca21)

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 d9212ed9fc21 232: onsuccess: #87: 1: [TCWG CI] Success after gdb: 130 commits discards 0b60e070f4a4 231: onsuccess: #86: 1: [TCWG CI] Success after binutils/g [...] discards f0d9b711e32f 230: onsuccess: #84: 1: [TCWG CI] Success after glibc-2.37 [...] discards 04c783784416 229: force: #83: 1: [TCWG CI] Success after glibc-2.37.900 [...] discards e6c8052ddad9 228: force: #82: 1: [TCWG CI] Success after glibc: 4 commits discards 320c4aa054fe 227: force: #81: 1: [TCWG CI] Failure after baseline build [...] discards c93990530ae9 226: onsuccess: #78: 1: [TCWG CI] Success after gcc: 28 commits discards dc083791498c 225: onsuccess: #72: 1: [TCWG CI] Success after gdb: 13 commits discards bfe08beb14fa 224: force: #71: 1: [TCWG CI] Failure after gdb-13-branchp [...] discards a63fce81ea4c 223: force: #70: 1: [TCWG CI] Success after gdb: 18 commits discards 5f12c4895cd9 222: onsuccess: #68: 1: [TCWG CI] Success after binutils/g [...] discards ea01172890ad 221: onsuccess: #66: 1: [TCWG CI] Success after gdb: 17 commits discards f41840293e16 220: force: #65: 1: [TCWG CI] Failure after gdb-13-branchp [...] discards 66ff5ab45de1 219: force: #64: 1: [TCWG CI] Success after gdb: 32 commits discards 8ab674f6b076 218: onsuccess: #62: 1: [TCWG CI] Success after binutils/g [...] discards 40e2c38189ac 217: onsuccess: #53: 1: Success after binutils/gcc/linux/g [...] discards ae19fcd6d660 216: onsuccess: #52: 1: Success after binutils/gcc/linux/g [...] discards ce6b3493a45d 215: onsuccess: #48: 1: Success after binutils/gcc/linux/g [...] discards fbd11fb8002c 214: onsuccess: #47: 1: Success after gdb: 21 commits discards 85f4d82b4fb0 213: force: #46: 1: Success after gdb-13-branchpoint-1550- [...] discards 4513a94125bb 212: force: #45: 1: Success after gdb: 22 commits discards 7b22e2a0d367 211: onsuccess: #44: 1: Success after linux: 26 commits discards 31f5a8a517ac 210: onsuccess: #43: 1: Success after glibc-2.37.9000-181- [...] discards a0f92fc50410 209: force: #37: 1: Success after baseline build: no new commits discards 773fe9aad9d6 208: onsuccess: #30: 1: Success after binutils/gcc/linux/g [...] discards c1e18c298694 207: onsuccess: #29: 1: Success after binutils/gcc/linux/g [...] discards 8081fc1f0930 206: onsuccess: #28: 1: Success after binutils/gcc/linux/g [...] discards e13d3d0e9f6f 205: onsuccess: #27: 1: Success after binutils/gcc/linux/g [...] discards f792af40988a 204: force: #26: : Failure after baseline build: no new commits discards d99fa5d8c373 203: onsuccess: #19: 1: Success after binutils/gcc/linux/g [...] discards 9af6fdfdb92e 202: onsuccess: #18: 1: Success after binutils/gcc/linux/g [...] discards 5708095bfaec 201: onsuccess: #17: 1: Success after binutils/gcc/linux/g [...] discards 69303543a431 200: onsuccess: #16: 1: Success after binutils/gcc/linux/g [...] discards 4f2a6da79079 199: onsuccess: #15: 1: Success after binutils/gcc/linux/g [...] discards 4d6405c86c2f 198: onsuccess: #14: 1: Success after binutils/gcc/linux/g [...] discards de440ae8d26c 197: onsuccess: #13: 1: Success after binutils/gcc/linux/g [...] discards 28d612a39c1b 196: onsuccess: #12: 1: Success after binutils/gcc/linux/g [...] discards 193393611c86 195: onsuccess: #11: 1: Success after binutils/gcc/linux/g [...] discards cda4dcbdc040 194: onsuccess: #10: 1: Success after binutils/gcc/linux/g [...] discards a4f174aca4ec 193: onsuccess: #9: 1: Success after binutils/gcc/linux/gd [...] discards 9f4c64ee2e2e 192: onsuccess: #8: 1: Success after binutils/gcc/linux/gl [...] discards f43b73428ddd 191: onsuccess: #7: 1: Success after binutils/gcc/linux/gl [...] discards a44149a1c282 190: onsuccess: #6: 1: Success after binutils/gcc/linux/gl [...] discards c9a34aec135d 189: onsuccess: #5: 1: Success after binutils/gcc/linux/gl [...] discards c68be30522ca 188: onsuccess: #4: 1: Success after binutils/gcc/linux/gd [...] discards ac90b674cdb2 187: onsuccess: #3: 1: Success after binutils/gcc/linux/gl [...] discards 703bc6e362eb 186: onsuccess: #2: 1: Success after binutils/gcc/linux/gd [...] discards 0520f0328188 185: onsuccess: #1: 1: Success after binutils/gcc/linux/gl [...] discards 41b677eee84f 184: onsuccess: #977: 1: Success after binutils/gcc/linux/ [...] discards 2f709041007f 183: onsuccess: #976: 1: Success after binutils/gcc/linux/ [...] discards 8dd6dea3875d 182: onsuccess: #975: 1: Success after binutils/gcc/linux/ [...] discards fc50fc91d038 181: onsuccess: #974: 1: Success after binutils/gcc/linux/ [...] discards 90f5d431b1fb 180: onsuccess: #973: 1: Success after binutils/gcc/linux/ [...] discards 6bd175b6ddbd 179: onsuccess: #972: 1: Success after binutils/gcc/linux/ [...] discards e2b36fcb9d4f 178: onsuccess: #971: 1: Success after binutils/gcc/linux/ [...] discards a209cba5f05b 177: onsuccess: #970: 1: Success after binutils/gcc/linux/ [...] discards b34468f09296 176: onsuccess: #969: 1: Success after binutils/gcc/linux/ [...] discards 435f17540273 175: onsuccess: #968: 1: Success after binutils/gcc/linux/ [...] discards d89d36301047 174: onsuccess: #967: 1: Success after binutils/gcc/linux/ [...] discards 086ac5c59dbd 173: onsuccess: #966: 1: Success after binutils/gcc/linux/ [...] discards cea89db907ed 172: onsuccess: #965: 1: Success after binutils/gcc/glibc/ [...] discards b71fcca0e189 171: onsuccess: #964: 1: Success after binutils/gcc/linux/ [...] discards da2d78552547 170: onsuccess: #963: 1: Success after binutils/gcc/linux/ [...] discards f62f4caef3c7 169: onsuccess: #962: 1: Success after binutils/gcc/linux/ [...] discards 596b12dc9c91 168: onsuccess: #961: 1: Success after binutils/gcc/linux/ [...] discards d25ce7d6e137 167: onsuccess: #960: 1: Success after binutils/gcc/linux/ [...] discards c4c69a54e1c6 166: onsuccess: #959: 1: Success after binutils/gcc/linux/ [...] discards b43487132125 165: onsuccess: #958: 1: Success after binutils/gcc/linux/ [...] discards f5edf9531a87 164: onsuccess: #957: 1: Success after binutils/gcc/glibc/ [...] discards ef3892812ba8 163: onsuccess: #956: 1: Success after binutils/gcc/linux/ [...] discards cdd1751bd1f0 162: onsuccess: #955: 1: Success after binutils/gcc/linux/ [...] discards dbba8575ecf0 161: onsuccess: #954: 1: Success after binutils/gcc/linux/ [...] discards 0bdff104fb21 160: onsuccess: #953: 1: Success after binutils/gcc/linux/ [...] discards 5f3ac8171285 159: onsuccess: #952: 1: Success after binutils/gcc/linux/ [...] discards e0da84520595 158: onsuccess: #951: 1: Success after gcc/linux: 19 commits discards 489b15f18008 157: onsuccess: #950: 1: Success after binutils/gcc/linux/ [...] discards 9c4138a7fa3c 156: onsuccess: #949: 1: Success after binutils/gcc/linux/ [...] discards fdf7c70e32e8 155: onsuccess: #948: 1: Success after binutils/gcc/linux/ [...] discards 5a740d9a254d 154: onsuccess: #947: 1: Success after binutils/gcc/linux/ [...] discards 3f72947981c2 153: onsuccess: #946: 1: Success after binutils/gcc/linux/ [...] discards 457b0a02d72c 152: onsuccess: #945: 1: Success after binutils/gcc/linux/ [...] discards adf423b8dd79 151: onsuccess: #944: 1: Success after binutils/gcc/linux/ [...] discards 005777fd5c80 150: onsuccess: #943: 1: Success after binutils/gcc/linux/ [...] discards 037cae668efd 149: onsuccess: #942: 1: Success after binutils/gcc/linux/ [...] discards 43aaa62df888 148: onsuccess: #941: 1: Success after binutils/gcc/linux/ [...] discards de8f56d52879 147: onsuccess: #940: 1: Success after binutils/gcc/linux/ [...] discards dfbf28941ffd 146: onsuccess: #939: 1: Success after binutils/gcc/linux/ [...] discards 2041dd6ab04a 145: onsuccess: #934: 1: Success after binutils/gcc/linux/ [...] discards b927b436857e 144: onsuccess: #933: 1: Success after binutils/gcc/glibc/ [...] discards a5b08151ad54 143: onsuccess: #931: 1: Success after binutils/gcc/linux/ [...] discards 892021241691 142: onsuccess: #929: 1: Success after binutils/gcc/linux/ [...] discards d7b81634c350 141: onsuccess: #928: 1: Success after binutils/gcc/linux/ [...] discards c7531c38c562 140: onsuccess: #927: 1: Success after binutils/gcc/linux/ [...] discards 3e806b9a3b84 139: onsuccess: #926: 1: Success after binutils/gcc/linux/ [...] discards 7f3cec780792 138: onsuccess: #925: 1: Success after binutils/gcc/gdb: 1 [...] discards d65f9651c3bd 137: onsuccess: #924: 1: Success after binutils/gcc/gdb: 4 [...] discards 6f66f2fa4bfd 136: onsuccess: #923: 1: Success after binutils/gcc/gdb: 1 [...] discards eacfa25827f9 135: onsuccess: #922: 1: Success after binutils/gcc/linux/ [...] discards 3cac8bf2b514 134: onsuccess: #921: 1: Success after binutils/gcc/gdb: 2 [...] discards e7a00859c06d 133: onsuccess: #920: 1: Success after binutils/gcc/linux/ [...] discards 18a4d043164e 132: onsuccess: #919: 1: Success after binutils/gcc/linux/ [...] new d1fa5526e86c 132: onsuccess: #919: 1: Success after binutils/gcc/linux/ [...] new 798317f324b0 133: onsuccess: #920: 1: Success after binutils/gcc/linux/ [...] new de572fc2c340 134: onsuccess: #921: 1: Success after binutils/gcc/gdb: 2 [...] new aad408c663e2 135: onsuccess: #922: 1: Success after binutils/gcc/linux/ [...] new ba7d9d6de2a0 136: onsuccess: #923: 1: Success after binutils/gcc/gdb: 1 [...] new 89e5f9d9bf77 137: onsuccess: #924: 1: Success after binutils/gcc/gdb: 4 [...] new 5e7df03c52e9 138: onsuccess: #925: 1: Success after binutils/gcc/gdb: 1 [...] new 5f528a542544 139: onsuccess: #926: 1: Success after binutils/gcc/linux/ [...] new 53bd33e59ce6 140: onsuccess: #927: 1: Success after binutils/gcc/linux/ [...] new 498fa37b63e6 141: onsuccess: #928: 1: Success after binutils/gcc/linux/ [...] new 37a07f5a9191 142: onsuccess: #929: 1: Success after binutils/gcc/linux/ [...] new cc42d2d1178e 143: onsuccess: #931: 1: Success after binutils/gcc/linux/ [...] new c05278e5277b 144: onsuccess: #933: 1: Success after binutils/gcc/glibc/ [...] new 50f395ce7609 145: onsuccess: #934: 1: Success after binutils/gcc/linux/ [...] new bdae85645a91 146: onsuccess: #939: 1: Success after binutils/gcc/linux/ [...] new bd5ef690eada 147: onsuccess: #940: 1: Success after binutils/gcc/linux/ [...] new f386d11e603a 148: onsuccess: #941: 1: Success after binutils/gcc/linux/ [...] new 94fc3653f23a 149: onsuccess: #942: 1: Success after binutils/gcc/linux/ [...] new 66b7f9c2b6ae 150: onsuccess: #943: 1: Success after binutils/gcc/linux/ [...] new 1ba658452db7 151: onsuccess: #944: 1: Success after binutils/gcc/linux/ [...] new 2966ce36ed0c 152: onsuccess: #945: 1: Success after binutils/gcc/linux/ [...] new 8618576727d1 153: onsuccess: #946: 1: Success after binutils/gcc/linux/ [...] new 58e2362e0279 154: onsuccess: #947: 1: Success after binutils/gcc/linux/ [...] new 009dda8fcdfc 155: onsuccess: #948: 1: Success after binutils/gcc/linux/ [...] new 085d4c9025a8 156: onsuccess: #949: 1: Success after binutils/gcc/linux/ [...] new 5a6fbfdd3586 157: onsuccess: #950: 1: Success after binutils/gcc/linux/ [...] new 23c2d3dc66c7 158: onsuccess: #951: 1: Success after gcc/linux: 19 commits new 611df0ff04a1 159: onsuccess: #952: 1: Success after binutils/gcc/linux/ [...] new f00bdd805d2f 160: onsuccess: #953: 1: Success after binutils/gcc/linux/ [...] new fb46cdaf1dba 161: onsuccess: #954: 1: Success after binutils/gcc/linux/ [...] new e282d475e1b2 162: onsuccess: #955: 1: Success after binutils/gcc/linux/ [...] new a6ac83880c83 163: onsuccess: #956: 1: Success after binutils/gcc/linux/ [...] new 9b93db934bd8 164: onsuccess: #957: 1: Success after binutils/gcc/glibc/ [...] new 9a390d42ca4d 165: onsuccess: #958: 1: Success after binutils/gcc/linux/ [...] new 02ccde8adfee 166: onsuccess: #959: 1: Success after binutils/gcc/linux/ [...] new 4bb6414cc60f 167: onsuccess: #960: 1: Success after binutils/gcc/linux/ [...] new 315e711eba5e 168: onsuccess: #961: 1: Success after binutils/gcc/linux/ [...] new 215b51a366bd 169: onsuccess: #962: 1: Success after binutils/gcc/linux/ [...] new cf460cede84a 170: onsuccess: #963: 1: Success after binutils/gcc/linux/ [...] new bea43ce7826d 171: onsuccess: #964: 1: Success after binutils/gcc/linux/ [...] new 7892c0e2631b 172: onsuccess: #965: 1: Success after binutils/gcc/glibc/ [...] new a4776e96bde0 173: onsuccess: #966: 1: Success after binutils/gcc/linux/ [...] new 242bba3610b4 174: onsuccess: #967: 1: Success after binutils/gcc/linux/ [...] new 7b33437b74d1 175: onsuccess: #968: 1: Success after binutils/gcc/linux/ [...] new d30ac5abf31f 176: onsuccess: #969: 1: Success after binutils/gcc/linux/ [...] new 7f710885bfa5 177: onsuccess: #970: 1: Success after binutils/gcc/linux/ [...] new bf602d459adb 178: onsuccess: #971: 1: Success after binutils/gcc/linux/ [...] new de14562f815f 179: onsuccess: #972: 1: Success after binutils/gcc/linux/ [...] new 2a12f3183a9a 180: onsuccess: #973: 1: Success after binutils/gcc/linux/ [...] new 94996cf1b04a 181: onsuccess: #974: 1: Success after binutils/gcc/linux/ [...] new d7e1505b429f 182: onsuccess: #975: 1: Success after binutils/gcc/linux/ [...] new bf8eafc6e434 183: onsuccess: #976: 1: Success after binutils/gcc/linux/ [...] new e215f2ea7b56 184: onsuccess: #977: 1: Success after binutils/gcc/linux/ [...] new 4a289ea78f11 185: onsuccess: #1: 1: Success after binutils/gcc/linux/gl [...] new 0ef06341fc62 186: onsuccess: #2: 1: Success after binutils/gcc/linux/gd [...] new 78e6506d97a6 187: onsuccess: #3: 1: Success after binutils/gcc/linux/gl [...] new 8e04ca8e2d99 188: onsuccess: #4: 1: Success after binutils/gcc/linux/gd [...] new b0d757ee5860 189: onsuccess: #5: 1: Success after binutils/gcc/linux/gl [...] new 4ba3aef6c825 190: onsuccess: #6: 1: Success after binutils/gcc/linux/gl [...] new c05d8dadf78e 191: onsuccess: #7: 1: Success after binutils/gcc/linux/gl [...] new 4f38eaa59d39 192: onsuccess: #8: 1: Success after binutils/gcc/linux/gl [...] new 158be3a408ec 193: onsuccess: #9: 1: Success after binutils/gcc/linux/gd [...] new d3e9228153ac 194: onsuccess: #10: 1: Success after binutils/gcc/linux/g [...] new 2f4b96423cb0 195: onsuccess: #11: 1: Success after binutils/gcc/linux/g [...] new 546fb9916370 196: onsuccess: #12: 1: Success after binutils/gcc/linux/g [...] new 874393c35dc4 197: onsuccess: #13: 1: Success after binutils/gcc/linux/g [...] new ed059b149318 198: onsuccess: #14: 1: Success after binutils/gcc/linux/g [...] new ff48de8c8a34 199: onsuccess: #15: 1: Success after binutils/gcc/linux/g [...] new 21fc97d5277f 200: onsuccess: #16: 1: Success after binutils/gcc/linux/g [...] new b537e207f7fd 201: onsuccess: #17: 1: Success after binutils/gcc/linux/g [...] new b114dbaf8100 202: onsuccess: #18: 1: Success after binutils/gcc/linux/g [...] new 50c5b03d560a 203: onsuccess: #19: 1: Success after binutils/gcc/linux/g [...] new 8482aec7d7f5 204: force: #26: : Failure after baseline build: no new commits new d72861888bca 205: onsuccess: #27: 1: Success after binutils/gcc/linux/g [...] new 8034275b50e2 206: onsuccess: #28: 1: Success after binutils/gcc/linux/g [...] new b317b76772c6 207: onsuccess: #29: 1: Success after binutils/gcc/linux/g [...] new cc9ef43e04ed 208: onsuccess: #30: 1: Success after binutils/gcc/linux/g [...] new b99b84631337 209: force: #37: 1: Success after baseline build: no new commits new dd5947b73194 210: onsuccess: #43: 1: Success after glibc-2.37.9000-181- [...] new 5c3473ea3673 211: onsuccess: #44: 1: Success after linux: 26 commits new 68f425523c03 212: force: #45: 1: Success after gdb: 22 commits new fbb67cd10afe 213: force: #46: 1: Success after gdb-13-branchpoint-1550- [...] new aee3ba2b43d5 214: onsuccess: #47: 1: Success after gdb: 21 commits new bd2fcda259f5 215: onsuccess: #48: 1: Success after binutils/gcc/linux/g [...] new f8987b58c3f1 216: onsuccess: #52: 1: Success after binutils/gcc/linux/g [...] new bde89ce44324 217: onsuccess: #53: 1: Success after binutils/gcc/linux/g [...] new db8de1871063 218: onsuccess: #62: 1: [TCWG CI] Success after binutils/g [...] new 2ddfb22d1080 219: force: #64: 1: [TCWG CI] Success after gdb: 32 commits new 7b23403474db 220: force: #65: 1: [TCWG CI] Failure after gdb-13-branchp [...] new 9bb641c4a73c 221: onsuccess: #66: 1: [TCWG CI] Success after gdb: 17 commits new 124a55e93c1c 222: onsuccess: #68: 1: [TCWG CI] Success after binutils/g [...] new d3199563b474 223: force: #70: 1: [TCWG CI] Success after gdb: 18 commits new d15c883257f2 224: force: #71: 1: [TCWG CI] Failure after gdb-13-branchp [...] new 79470657747b 225: onsuccess: #72: 1: [TCWG CI] Success after gdb: 13 commits new 689830700837 226: onsuccess: #78: 1: [TCWG CI] Success after gcc: 28 commits new e8166cd509a4 227: force: #81: 1: [TCWG CI] Failure after baseline build [...] new 41a668f4a3f6 228: force: #82: 1: [TCWG CI] Success after glibc: 4 commits new 164f26197da2 229: force: #83: 1: [TCWG CI] Success after glibc-2.37.900 [...] new bb3911fde8b6 230: onsuccess: #84: 1: [TCWG CI] Success after glibc-2.37 [...] new d8e5d8e9d60f 231: onsuccess: #86: 1: [TCWG CI] Success after binutils/g [...] new a68372d7f85b 232: onsuccess: #87: 1: [TCWG CI] Success after gdb: 130 commits new c98fd389ca21 233: onsuccess: #91: 1: [TCWG CI] Success after binutils: [...] 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 (d9212ed9fc21) \ 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 1984 -> 2000 bytes 02-prepare_abe/console.log.xz | Bin 2520 -> 2508 bytes 03-build_abe-binutils/console.log.xz | Bin 34988 -> 35204 bytes 04-build_abe-gcc/console.log.xz | Bin 203244 -> 204820 bytes 06-build_abe-linux/console.log.xz | Bin 8976 -> 9004 bytes 07-build_abe-glibc/console.log.xz | Bin 241148 -> 241200 bytes 08-build_abe-gdb/console.log.xz | Bin 34644 -> 34688 bytes 09-build_abe-dejagnu/console.log.xz | Bin 3780 -> 3800 bytes 10-build_abe-check_gdb/console.log.xz | Bin 2620 -> 2604 bytes 11-check_regression/console.log.xz | Bin 4472 -> 3796 bytes 11-check_regression/results.compare | 14 ---- 11-check_regression/results.compare2 | 122 +++++++++++++--------------------- 12-update_baseline/console.log | 40 +++++------ dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- mail/changes-list-long.txt | 10 +-- mail/changes-list-short.txt | 2 +- mail/last_good.sh | 25 +++---- manifest.sh | 20 +++--- sumfiles/gdb.log.0.xz | Bin 2004004 -> 2026176 bytes sumfiles/gdb.log.1.xz | Bin 29420 -> 30048 bytes sumfiles/gdb.log.2.xz | Bin 15496 -> 14636 bytes sumfiles/gdb.log.3.xz | Bin 15664 -> 0 bytes sumfiles/gdb.sum | 30 ++++----- sumfiles/gdb.sum.0 | 32 ++++----- sumfiles/gdb.sum.1 | 12 ++-- sumfiles/gdb.sum.2 | 20 +++--- sumfiles/gdb.sum.3 | 110 ------------------------------ 28 files changed, 140 insertions(+), 301 deletions(-) delete mode 100644 sumfiles/gdb.log.3.xz delete mode 100644 sumfiles/gdb.sum.3 -- To stop receiving notification emails like this one, please contact the administrator of this repository.

1 year, 7 months

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_bmk-code_speed-cpu2017rate/gnu-aarch64-master-O2 updated (d100390a4917 -> a91d5b3f6321)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. tcwg-buildslave pushed a change to branch linaro-local/ci/tcwg_bmk-code_speed-cpu2017rate/gnu-aarch64-master-O2 in repository toolchain/ci/base-artifacts. from d100390a4917 14: onsuccess: #17: 1: [TCWG CI] No change after binutils/ [...] new a91d5b3f6321 15: onsuccess: #18: 1: [TCWG CI] Success after binutils/gc [...] The 1 revisions listed above as "new" are entirely new to this repository and will be described in separate emails. The revisions listed as "adds" were already present in the repository and have only been added to this reference. Summary of changes: 01-reset_artifacts/console.log.xz | Bin 2088 -> 2040 bytes 02-prepare_abe/console.log.xz | Bin 2560 -> 2520 bytes 03-build_abe-binutils/console.log.xz | Bin 27300 -> 27140 bytes 04-build_abe-stage1/console.log.xz | Bin 72240 -> 71568 bytes 05-clean_sysroot/console.log.xz | Bin 332 -> 332 bytes 06-build_abe-linux/console.log.xz | Bin 7524 -> 8308 bytes 07-build_abe-glibc/console.log.xz | Bin 242988 -> 241508 bytes 08-build_abe-stage2/console.log.xz | Bin 177600 -> 176552 bytes 09-benchmark/benchmark-build.log | 142 +- 09-benchmark/benchmark.log | 140 +- 09-benchmark/console.log.xz | Bin 4124 -> 4096 bytes 10-check_regression/bmk-specific-variability.csv | 70 +- .../compare-results-vs-first-internal.csv | 193 +- .../compare-results-vs-prev-internal.csv | 193 +- 10-check_regression/console.log.xz | Bin 16292 -> 17068 bytes .../csv-results-vs-first-0/md5sum.csv | 2508 +- .../csv-results-vs-first-0/results.csv | 773088 ++++++++--------- .../csv-results-vs-first-0/size.csv | 777890 +++++++++--------- 10-check_regression/csv-results-vs-first-0/sve.csv | 24318 +- .../csv-results-vs-first-0/vect.csv | 738 +- .../csv-results-vs-first-1/md5sum.csv | 2500 +- .../csv-results-vs-first-1/perf.csv | 2785 +- .../csv-results-vs-first-1/results.csv | 704057 ++++++++-------- .../csv-results-vs-first-1/size.csv | 708666 ++++++++-------- 10-check_regression/csv-results-vs-first-1/sve.csv | 24520 +- .../csv-results-vs-first-1/vect.csv | 744 +- .../csv-results-vs-prev-0/md5sum.csv | 2452 +- 10-check_regression/csv-results-vs-prev-0/perf.csv | 2789 +- .../csv-results-vs-prev-0/results.csv | 726408 ++++++++-------- 10-check_regression/csv-results-vs-prev-0/size.csv | 730984 ++++++++-------- 10-check_regression/csv-results-vs-prev-0/sve.csv | 24058 +- 10-check_regression/csv-results-vs-prev-0/vect.csv | 674 +- .../csv-results-vs-prev-1/md5sum.csv | 2500 +- 10-check_regression/csv-results-vs-prev-1/perf.csv | 2785 +- .../csv-results-vs-prev-1/results.csv | 704057 ++++++++-------- 10-check_regression/csv-results-vs-prev-1/size.csv | 708666 ++++++++-------- 10-check_regression/csv-results-vs-prev-1/sve.csv | 24520 +- 10-check_regression/csv-results-vs-prev-1/vect.csv | 744 +- .../output-bmk-results/exe.improvement | 1 + .../output-bmk-results/exe.improvement.diff | 1 + .../output-bmk-results/symbol.improvement | 9 +- .../output-bmk-results/symbol.improvement.diff | 2 +- .../output-bmk-results/symbol.regression | 6 +- .../output-bmk-results/symbol.regression.diff | 2 +- 10-check_regression/results-vs-first-brief.csv | 56 +- 10-check_regression/results-vs-first-full.csv | 2801 +- 10-check_regression/results-vs-first-internal.csv | 193 +- 10-check_regression/results-vs-first.csv | 193 +- 10-check_regression/results-vs-first.log | 1430 +- 10-check_regression/results-vs-prev-brief.csv | 56 +- 10-check_regression/results-vs-prev-compare.csv | 5 +- 10-check_regression/results-vs-prev-full.csv | 2875 +- 10-check_regression/results-vs-prev-internal.csv | 193 +- 10-check_regression/results-vs-prev.csv | 193 +- 10-check_regression/results-vs-prev.log | 1590 +- dashboard/dashboard-generate.sh | 2 +- .../500.perlbench_r/results-metadata.json | 16 +- .../squad-vs-first/502.gcc_r/results-metadata.json | 16 +- .../503.bwaves_r/results-metadata.json | 16 +- .../503.bwaves_r/results-metrics.json | 4 +- .../squad-vs-first/505.mcf_r/results-metadata.json | 16 +- .../squad-vs-first/505.mcf_r/results-metrics.json | 2 +- .../507.cactuBSSN_r/results-metadata.json | 16 +- .../507.cactuBSSN_r/results-metrics.json | 2 +- .../508.namd_r/results-metadata.json | 16 +- .../squad-vs-first/508.namd_r/results-metrics.json | 2 +- .../510.parest_r/results-metadata.json | 16 +- .../510.parest_r/results-metrics.json | 2 +- .../511.povray_r/results-metadata.json | 16 +- .../511.povray_r/results-metrics.json | 4 +- .../squad-vs-first/519.lbm_r/results-metadata.json | 16 +- .../520.omnetpp_r/results-metadata.json | 16 +- .../520.omnetpp_r/results-metrics.json | 2 +- .../squad-vs-first/521.wrf_r/results-metadata.json | 16 +- .../squad-vs-first/521.wrf_r/results-metrics.json | 2 +- .../523.xalancbmk_r/results-metadata.json | 16 +- .../523.xalancbmk_r/results-metrics.json | 2 +- .../525.x264_r/results-metadata.json | 16 +- .../526.blender_r/results-metadata.json | 16 +- .../527.cam4_r/results-metadata.json | 16 +- .../squad-vs-first/527.cam4_r/results-metrics.json | 2 +- .../531.deepsjeng_r/results-metadata.json | 16 +- .../531.deepsjeng_r/results-metrics.json | 2 +- .../538.imagick_r/results-metadata.json | 16 +- .../541.leela_r/results-metadata.json | 16 +- .../541.leela_r/results-metrics.json | 4 +- .../squad-vs-first/544.nab_r/results-metadata.json | 16 +- .../squad-vs-first/544.nab_r/results-metrics.json | 2 +- .../548.exchange2_r/results-metadata.json | 16 +- .../548.exchange2_r/results-metrics.json | 2 +- .../549.fotonik3d_r/results-metadata.json | 16 +- .../549.fotonik3d_r/results-metrics.json | 2 +- .../554.roms_r/results-metadata.json | 16 +- .../squad-vs-first/554.roms_r/results-metrics.json | 2 +- .../squad-vs-first/557.xz_r/results-metadata.json | 16 +- .../squad-vs-first/Mean/results-metadata.json | 16 +- dashboard/squad-vs-first/dashboard-push-squad.sh | 98 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- git/glibc_rev | 2 +- git/linux_rev | 2 +- mail/changes-list-long.txt | 26 + mail/changes-list-short.txt | 1 + manifest.sh => mail/last_good.sh | 0 mail/mail-body.txt | 27 - mail/mail-subject.txt | 1 - mail/short-diag.txt | 1 + manifest.sh | 36 +- results_id | 2 +- 109 files changed, 2953786 insertions(+), 3009633 deletions(-) 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 mail/changes-list-long.txt create mode 100644 mail/changes-list-short.txt copy manifest.sh => mail/last_good.sh (100%) delete mode 100644 mail/mail-body.txt delete mode 100644 mail/mail-subject.txt create mode 100644 mail/short-diag.txt -- To stop receiving notification emails like this one, please contact the administrator of this repository.

1 year, 7 months

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_bmk-code_size-spec2k6/llvm-aarch64-master-Oz updated (160c54b44399 -> 7b026d33ff71)

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-aarch64-master-Oz in repository toolchain/ci/base-artifacts. from 160c54b44399 53: force: #13: 1: [TCWG CI] Success after llvm: 469 commits new 7b026d33ff71 54: force: #14: 1: [TCWG CI] Failure after llvmorg-17-init [...] 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 1880 -> 1848 bytes 02-build_bmk_llvm/console.log.xz | Bin 99624 -> 99860 bytes 03-benchmark/benchmark-build.log | 92 +- 03-benchmark/benchmark.log | 90 +- 03-benchmark/console.log.xz | Bin 3828 -> 3780 bytes .../compare-results-vs-first-internal.csv | 126 +- .../compare-results-vs-prev-internal.csv | 147 +- 04-check_regression/console.log.xz | Bin 10596 -> 10864 bytes .../csv-results-vs-first-1/md5sum.csv | 1753 +- .../csv-results-vs-first-1/perf.csv | 2056 +- .../csv-results-vs-first-1/results.csv | 10394 +-- .../csv-results-vs-first-1/size.csv | 52714 +++++------ 04-check_regression/csv-results-vs-first-1/sve.csv | 18 +- .../csv-results-vs-prev-0/md5sum.csv | 1743 +- 04-check_regression/csv-results-vs-prev-0/perf.csv | 1975 +- .../csv-results-vs-prev-0/results.csv | 4467 +- 04-check_regression/csv-results-vs-prev-0/size.csv | 92000 ++++++++++--------- 04-check_regression/csv-results-vs-prev-0/sve.csv | 14 +- .../csv-results-vs-prev-1/md5sum.csv | 1753 +- 04-check_regression/csv-results-vs-prev-1/perf.csv | 2056 +- .../csv-results-vs-prev-1/results.csv | 10394 +-- 04-check_regression/csv-results-vs-prev-1/size.csv | 52714 +++++------ 04-check_regression/csv-results-vs-prev-1/sve.csv | 18 +- 04-check_regression/exe.regression | 1 + 04-check_regression/extra-bisect-params | 2 +- 04-check_regression/mail-body.txt | 3 + 04-check_regression/mail-subject.txt | 2 +- .../output-bmk-results/exe.regression.diff | 1 + 04-check_regression/results-vs-first-brief.csv | 38 +- 04-check_regression/results-vs-first-full.csv | 1955 +- 04-check_regression/results-vs-first-internal.csv | 126 +- 04-check_regression/results-vs-first.csv | 126 +- 04-check_regression/results-vs-first.log | 1030 +- 04-check_regression/results-vs-prev-brief.csv | 42 +- 04-check_regression/results-vs-prev-compare.csv | 7 +- 04-check_regression/results-vs-prev-full.csv | 2111 +- 04-check_regression/results-vs-prev-internal.csv | 136 +- 04-check_regression/results-vs-prev.csv | 136 +- 04-check_regression/results-vs-prev.log | 1106 +- 04-check_regression/results.regressions | 17 + 04-check_regression/trigger-bisect | 3 + .../error_code-1 => trigger-notify} | 0 dashboard/dashboard-generate.sh | 2 +- .../400.perlbench/results-metadata.json | 8 +- .../squad-vs-first/401.bzip2/results-metadata.json | 8 +- .../squad-vs-first/403.gcc/results-metadata.json | 8 +- .../410.bwaves/results-metadata.json | 8 +- .../416.gamess/results-metadata.json | 8 +- .../squad-vs-first/429.mcf/results-metadata.json | 8 +- .../squad-vs-first/433.milc/results-metadata.json | 8 +- .../434.zeusmp/results-metadata.json | 8 +- .../435.gromacs/results-metadata.json | 8 +- .../436.cactusADM/results-metadata.json | 8 +- .../437.leslie3d/results-metadata.json | 8 +- .../squad-vs-first/444.namd/results-metadata.json | 8 +- .../squad-vs-first/445.gobmk/results-metadata.json | 8 +- .../447.dealII/results-metadata.json | 8 +- .../450.soplex/results-metadata.json | 8 +- .../453.povray/results-metadata.json | 8 +- .../454.calculix/results-metadata.json | 8 +- .../squad-vs-first/456.hmmer/results-metadata.json | 8 +- .../squad-vs-first/458.sjeng/results-metadata.json | 8 +- .../459.GemsFDTD/results-metadata.json | 8 +- .../462.libquantum/results-metadata.json | 8 +- .../464.h264ref/results-metadata.json | 8 +- .../squad-vs-first/465.tonto/results-metadata.json | 8 +- .../squad-vs-first/470.lbm/results-metadata.json | 8 +- .../471.omnetpp/results-metadata.json | 8 +- .../471.omnetpp/results-metrics.json | 2 +- .../squad-vs-first/473.astar/results-metadata.json | 8 +- .../squad-vs-first/481.wrf/results-metadata.json | 8 +- .../482.sphinx3/results-metadata.json | 8 +- .../483.xalancbmk/results-metadata.json | 8 +- .../483.xalancbmk/results-metrics.json | 2 +- .../squad-vs-first/Mean/results-metadata.json | 8 +- dashboard/squad-vs-first/dashboard-push-squad.sh | 122 +- git/llvm_rev | 2 +- jenkins/notify.sh | 3 + mail/changes-list-long.txt | 11 +- mail/changes-list-short.txt | 2 +- mail/last_good.sh | 16 +- mail/short-diag.txt | 2 +- manifest.sh | 12 +- results | 17 + results_id | 2 +- 85 files changed, 120974 insertions(+), 120827 deletions(-) create mode 100644 04-check_regression/exe.regression create mode 100644 04-check_regression/output-bmk-results/exe.regression.diff create mode 100644 04-check_regression/results.regressions create mode 100644 04-check_regression/trigger-bisect copy 04-check_regression/{output-bmk-results/error_code-1 => trigger-notify} (100%) create mode 100755 jenkins/notify.sh -- To stop receiving notification emails like this one, please contact the administrator of this repository.

1 year, 7 months

[toolchain/ci/interesting-commits] branch master updated (d230b09c -> 9ae339cb)

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 d230b09c Add entry 69044e11ac52e93622c3d368ae2fd9ef8c3ec015 from https [...] new 9ae339cb Add entry e8bc77ec085cf23a743bf203d526000df8f45946 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: .../build_url | 2 +- .../last_good | 0 .../summary.txt | 16 +++---- .../tcwg_bmk-code_size-spec2k6/status.txt | 51 ++++++++++++++++++++++ 4 files changed, 60 insertions(+), 9 deletions(-) copy llvm/sha1/e8bc77ec085cf23a743bf203d526000df8f45946/tcwg_bmk-code_size-spec2k6 [...] copy llvm/sha1/e8bc77ec085cf23a743bf203d526000df8f45946/tcwg_bmk-code_size-spec2k6 [...] copy llvm/sha1/e8bc77ec085cf23a743bf203d526000df8f45946/tcwg_bmk-code_size-spec2k6 [...] -- To stop receiving notification emails like this one, please contact the administrator of this repository.

1 year, 7 months

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_gnu_cross_build/master-aarch64 updated (24f351b4fa4a -> 6801752f6958)

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_build/master-aarch64 in repository toolchain/ci/base-artifacts. discards 24f351b4fa4a 485: onsuccess: #43: 7: [TCWG CI] Success after binutils/g [...] discards b3e52797a60c 484: onsuccess: #42: 7: [TCWG CI] Success after binutils/g [...] discards daf9b0ae7225 483: onsuccess: #41: 7: [TCWG CI] Success after binutils/g [...] discards e30b2b9bc1ae 482: onsuccess: #40: 7: [TCWG CI] Success after binutils/g [...] discards 32867a3f9fe8 481: onsuccess: #39: 7: [TCWG CI] Success after binutils/g [...] discards d53a9706334f 480: onsuccess: #37: 7: Success after binutils/gcc/linux/g [...] discards 706f6e75e1ab 479: onsuccess: #36: 7: Success after binutils/gcc/linux/g [...] discards 23e371c55085 478: onsuccess: #34: 7: Success after binutils/gcc/linux/g [...] discards 921e6566e2fc 477: onsuccess: #33: 7: Success after binutils/gcc/linux/g [...] discards 041bc89a5999 476: onsuccess: #32: 7: Success after binutils/gcc/linux/g [...] discards 584826b2ad7d 475: onsuccess: #31: 7: Success after binutils/gcc/linux/g [...] discards 157f79752454 474: onsuccess: #30: 7: Success after binutils/gcc/linux/g [...] discards 784c7b405929 473: onsuccess: #29: 7: Success after binutils/gcc/linux/g [...] discards 62f22d909166 472: onsuccess: #27: 7: Success after binutils/gcc/linux/g [...] discards 62c0e1bcc7e1 471: onsuccess: #26: 7: Success after binutils/gcc/linux/g [...] discards 2a365210e674 470: onsuccess: #25: 7: Success after binutils/gcc/linux/g [...] discards 14075d11ff0a 469: onsuccess: #24: 7: Success after binutils/gcc/linux/g [...] discards aeb3ce9321f5 468: onsuccess: #23: 7: Success after binutils/gcc/linux/g [...] discards aa78345da135 467: onsuccess: #22: 7: Success after binutils/gcc/linux/g [...] discards 26e61f06009f 466: onsuccess: #21: 7: Success after binutils/gcc/linux/g [...] discards d5e8c5bfd146 465: onsuccess: #20: 7: Success after binutils/gcc/linux/g [...] discards 923b6814a3ee 464: onsuccess: #19: 7: Success after binutils/gcc/linux/g [...] discards ba1197e0e78a 463: onsuccess: #18: 7: Success after binutils/gcc/linux/g [...] discards 3239c7a09387 462: onsuccess: #17: 7: Success after binutils/gcc/linux/g [...] discards 710585c8e50c 461: onsuccess: #16: 7: Success after binutils/gcc/linux/g [...] discards 3d985caf6212 460: onsuccess: #15: 7: Success after binutils/gcc/linux/g [...] discards 828fddd0e70a 459: onsuccess: #14: 7: Success after binutils/gcc/linux/g [...] discards ddadf18cc24e 458: onsuccess: #13: 7: Success after binutils/gcc/linux/g [...] discards 6e89d4556e1b 457: onsuccess: #12: 7: Success after binutils/gcc/linux/g [...] discards 95c48ebf18b2 456: onsuccess: #11: 7: Success after binutils/gcc/linux/g [...] discards 6f963b615e8e 455: onsuccess: #10: 7: Success after binutils/gcc/linux/g [...] discards 30b9e25c293a 454: onsuccess: #9: 7: Success after binutils/gcc/linux/gl [...] discards 3e20ffd20b79 453: onsuccess: #8: 7: Success after binutils/gcc/gdb: 6 commits discards 19c9cdbc243c 452: onsuccess: #7: 7: Success after baseline build: no ne [...] discards 7e197632bfbc 451: onsuccess: #6: 7: Success after binutils/gcc/linux/gd [...] discards 24039765c8f2 450: onsuccess: #5: 7: Success after binutils/gcc/linux/gl [...] discards 70ac6967426e 449: onsuccess: #4: 7: Success after binutils/gcc/gdb/qemu [...] discards 38306cbba069 448: onsuccess: #3: 7: Success after binutils/gcc/glibc/gd [...] discards 18ca94af33ed 447: onsuccess: #2149: 7: Success after binutils/gcc/glibc [...] discards 224bd5dc9ddb 446: onsuccess: #2: 7: Success after binutils/gcc/linux/gd [...] discards 72facc01ed68 445: onsuccess: #2148: 7: Success after binutils/gcc/linux [...] discards f579cdc20a35 444: onsuccess: #1: 7: Success after binutils/gcc/gdb: 11 commits discards 84416d7ce56d 443: onsuccess: #2147: 7: Success after binutils/gcc/gdb: [...] discards a98ea23cca58 442: onsuccess: #2146: 7: Success after binutils/gcc/linux [...] discards 41cabb6455a5 441: onsuccess: #2145: 7: Success after binutils/gcc/linux [...] discards 3b486e773048 440: onsuccess: #2144: 7: Success after binutils/gcc/glibc [...] discards 14a82c246e7f 439: onsuccess: #2143: 7: Success after gcc: 7 commits discards d77d810b8878 438: onsuccess: #2142: 7: Success after binutils/linux/gdb [...] discards 042a572621e1 437: onsuccess: #2141: 7: Success after binutils/gcc/linux [...] discards ed8b55ad7fe5 436: onsuccess: #2140: 7: Success after binutils/gcc/linux [...] discards 2f9105c266cc 435: onsuccess: #2139: 7: Success after binutils/gcc/gdb/q [...] discards 92f1a4a913c1 434: onsuccess: #2138: 7: Success after binutils/gcc/linux [...] discards 81cacea0d491 433: onsuccess: #2137: 7: Success after binutils/gcc/linux [...] discards ed4893cbdd4b 432: onsuccess: #2136: 7: Success after binutils/gcc/glibc [...] discards 562356712deb 431: onsuccess: #2135: 7: Success after binutils/gcc/glibc [...] discards 4e0542c86722 430: onsuccess: #2134: 7: Success after binutils/gdb: 2 commits discards b14de5d20385 429: onsuccess: #2133: 7: Success after binutils/gcc/linux [...] discards e77351e2e78b 428: onsuccess: #2132: 7: Success after binutils/linux/gdb [...] discards 7cd2a842d302 427: onsuccess: #2131: 7: Success after binutils/gcc/linux [...] discards d1c690efa2eb 426: onsuccess: #2130: 7: Success after gcc: 7 commits discards 7f1f39630839 425: onsuccess: #2129: 7: Success after gcc/linux: 9 commits discards 74afd9ce26d2 424: onsuccess: #2128: 7: Success after binutils/gcc/linux [...] discards 084e444682f6 423: onsuccess: #2127: 7: Success after binutils/gcc/glibc [...] discards 5c281966da80 422: onsuccess: #2126: 7: Success after gcc/glibc: 5 commits discards d0b2797c7ac8 421: onsuccess: #2125: 7: Success after binutils/gcc/linux [...] discards 8f2c487db77e 420: onsuccess: #2124: 7: Success after binutils/gcc/linux [...] discards d7797adb2389 419: onsuccess: #2123: 7: Success after binutils/gcc/gdb/q [...] discards 01c31ac5b885 418: onsuccess: #2122: 7: Success after binutils/gcc/gdb/q [...] discards dd34b711d945 417: onsuccess: #2121: 7: Success after binutils/gcc/linux [...] discards 34ccafb03663 416: onsuccess: #2120: 7: Success after binutils/gcc/glibc [...] discards a273d6866451 415: onsuccess: #2119: 7: Success after gcc: 37 commits discards 7535a4527818 414: onsuccess: #2118: 7: Success after binutils: 5 commits discards 3d30030003b0 413: onsuccess: #2116: 7: Success after binutils/gdb: 4 commits discards b83137e89871 412: onsuccess: #2115: 7: Success after binutils/gcc/glibc [...] discards ed8bdd756a69 411: onsuccess: #2114: 7: Success after binutils/gcc/linux [...] discards f9b150095727 410: onsuccess: #2113: 7: Success after binutils/gcc/glibc [...] discards 97078f182d0a 409: onsuccess: #2112: 7: Success after gcc: 3 commits discards 03d512740ce7 408: onsuccess: #2111: 7: Success after binutils/gcc/linux [...] discards 73ecd326ddd5 407: onsuccess: #2110: 7: Success after binutils/gcc/glibc [...] discards 5f365ef203de 406: onsuccess: #2109: 7: Success after binutils/gcc/gdb: [...] discards 7266cc08a05a 405: onsuccess: #2108: 7: Success after binutils/gcc/gdb: [...] discards e78420dff041 404: onsuccess: #2107: 7: Success after binutils/gcc/linux [...] discards 19960586b06e 403: onsuccess: #2106: 7: Success after glibc: 12 commits discards 743575e70323 402: onsuccess: #2105: 7: Success after binutils/gcc/gdb: [...] discards fa85507c952b 401: onsuccess: #2104: 7: Success after binutils/gcc/gdb: [...] discards 6c81ce751da7 400: onsuccess: #2103: 7: Success after binutils/gcc/linux [...] discards 2270e4d0a0fb 399: onsuccess: #2102: 7: Success after binutils/gcc/gdb: [...] discards 54b5f36e3fd1 398: onsuccess: #2101: 7: Success after binutils/gcc/gdb: [...] discards d5dbb8490d67 397: onsuccess: #2100: 7: Success after binutils/gcc/gdb: [...] discards 1109261cccd8 396: onsuccess: #2099: 7: Success after binutils/gcc/linux [...] discards bd57b0774c1d 395: onsuccess: #2098: 7: Success after binutils/gcc/linux [...] discards bff50ddbb2c0 394: onsuccess: #2097: 7: Success after binutils/gcc/gdb/q [...] discards 4dee7b5874d6 393: onsuccess: #2096: 7: Success after gcc/linux: 45 commits discards 9791661f8a4a 392: onsuccess: #2095: 7: Success after binutils/gcc/linux [...] discards 4c612d18261c 391: onsuccess: #2094: 7: Success after binutils/gcc/linux [...] discards 6a0233cc7836 390: onsuccess: #2092: 7: Success after basepoints/gcc-13- [...] discards e57104926bca 389: onsuccess: #2091: 7: Success after binutils/gcc/gdb: [...] discards 4ef37cf3baf7 388: onsuccess: #2090: 7: Success after binutils/gcc/glibc [...] discards e4df62bb074b 387: onsuccess: #2089: 7: Success after binutils/gcc/gdb/q [...] discards 98e88c82aed7 386: onsuccess: #2087: 7: Success after binutils/gcc/linux [...] discards 564d2b36caef 385: onsuccess: #2086: 7: Success after binutils/gcc/linux [...] new 41796b740344 385: onsuccess: #2086: 7: Success after binutils/gcc/linux [...] new 80d54b448c5d 386: onsuccess: #2087: 7: Success after binutils/gcc/linux [...] new 393df7ea5d0f 387: onsuccess: #2089: 7: Success after binutils/gcc/gdb/q [...] new 83e119dbb920 388: onsuccess: #2090: 7: Success after binutils/gcc/glibc [...] new fe82916a066f 389: onsuccess: #2091: 7: Success after binutils/gcc/gdb: [...] new fdbc2685bbf5 390: onsuccess: #2092: 7: Success after basepoints/gcc-13- [...] new 60667cac22af 391: onsuccess: #2094: 7: Success after binutils/gcc/linux [...] new 0752ce84086e 392: onsuccess: #2095: 7: Success after binutils/gcc/linux [...] new fd1f4db3f9dc 393: onsuccess: #2096: 7: Success after gcc/linux: 45 commits new c23f2c04a63c 394: onsuccess: #2097: 7: Success after binutils/gcc/gdb/q [...] new 1f4cd521431c 395: onsuccess: #2098: 7: Success after binutils/gcc/linux [...] new 1c17a5ebb170 396: onsuccess: #2099: 7: Success after binutils/gcc/linux [...] new d3f2ff98a1f3 397: onsuccess: #2100: 7: Success after binutils/gcc/gdb: [...] new 19617c3e2002 398: onsuccess: #2101: 7: Success after binutils/gcc/gdb: [...] new 26f373abb8b8 399: onsuccess: #2102: 7: Success after binutils/gcc/gdb: [...] new a97da9f820b4 400: onsuccess: #2103: 7: Success after binutils/gcc/linux [...] new 8b822189cb97 401: onsuccess: #2104: 7: Success after binutils/gcc/gdb: [...] new 561d7463670a 402: onsuccess: #2105: 7: Success after binutils/gcc/gdb: [...] new adbf8ff5d3b3 403: onsuccess: #2106: 7: Success after glibc: 12 commits new 2541494905de 404: onsuccess: #2107: 7: Success after binutils/gcc/linux [...] new a4268bb2ece7 405: onsuccess: #2108: 7: Success after binutils/gcc/gdb: [...] new 73ff3f62f3db 406: onsuccess: #2109: 7: Success after binutils/gcc/gdb: [...] new 4c8458e288c2 407: onsuccess: #2110: 7: Success after binutils/gcc/glibc [...] new a5f5cb17e5f3 408: onsuccess: #2111: 7: Success after binutils/gcc/linux [...] new b0a0f3b0fe8c 409: onsuccess: #2112: 7: Success after gcc: 3 commits new 52e1b66e25f9 410: onsuccess: #2113: 7: Success after binutils/gcc/glibc [...] new 21bdd4e6a5f0 411: onsuccess: #2114: 7: Success after binutils/gcc/linux [...] new a47498bccccf 412: onsuccess: #2115: 7: Success after binutils/gcc/glibc [...] new 6db7632f4b21 413: onsuccess: #2116: 7: Success after binutils/gdb: 4 commits new 6cd42a8c30c1 414: onsuccess: #2118: 7: Success after binutils: 5 commits new 7376b92fad79 415: onsuccess: #2119: 7: Success after gcc: 37 commits new 1a142908c722 416: onsuccess: #2120: 7: Success after binutils/gcc/glibc [...] new f34207b25a07 417: onsuccess: #2121: 7: Success after binutils/gcc/linux [...] new 9350b15eaf69 418: onsuccess: #2122: 7: Success after binutils/gcc/gdb/q [...] new ceddf2e1377b 419: onsuccess: #2123: 7: Success after binutils/gcc/gdb/q [...] new ab126ce52d7e 420: onsuccess: #2124: 7: Success after binutils/gcc/linux [...] new 07a5daf2bfa5 421: onsuccess: #2125: 7: Success after binutils/gcc/linux [...] new 0937daf937e6 422: onsuccess: #2126: 7: Success after gcc/glibc: 5 commits new 1feef0dcc122 423: onsuccess: #2127: 7: Success after binutils/gcc/glibc [...] new 02749cdba821 424: onsuccess: #2128: 7: Success after binutils/gcc/linux [...] new 9d8016b2430f 425: onsuccess: #2129: 7: Success after gcc/linux: 9 commits new 7b7681fcd4dd 426: onsuccess: #2130: 7: Success after gcc: 7 commits new 44b243f5b4c8 427: onsuccess: #2131: 7: Success after binutils/gcc/linux [...] new d9ef352f0265 428: onsuccess: #2132: 7: Success after binutils/linux/gdb [...] new c4f1f709da27 429: onsuccess: #2133: 7: Success after binutils/gcc/linux [...] new fa4458f4de5e 430: onsuccess: #2134: 7: Success after binutils/gdb: 2 commits new dd370ffa4f03 431: onsuccess: #2135: 7: Success after binutils/gcc/glibc [...] new 4b5e71cbe7af 432: onsuccess: #2136: 7: Success after binutils/gcc/glibc [...] new 15caa3e86ea0 433: onsuccess: #2137: 7: Success after binutils/gcc/linux [...] new 694c61c80790 434: onsuccess: #2138: 7: Success after binutils/gcc/linux [...] new 50343e3820ef 435: onsuccess: #2139: 7: Success after binutils/gcc/gdb/q [...] new 29c5d2f06732 436: onsuccess: #2140: 7: Success after binutils/gcc/linux [...] new 2cb82ab83647 437: onsuccess: #2141: 7: Success after binutils/gcc/linux [...] new 31beeed46068 438: onsuccess: #2142: 7: Success after binutils/linux/gdb [...] new 2e655d77ab28 439: onsuccess: #2143: 7: Success after gcc: 7 commits new a7143852add6 440: onsuccess: #2144: 7: Success after binutils/gcc/glibc [...] new d7149c3884f8 441: onsuccess: #2145: 7: Success after binutils/gcc/linux [...] new 511c2594df0e 442: onsuccess: #2146: 7: Success after binutils/gcc/linux [...] new 150c50710e31 443: onsuccess: #2147: 7: Success after binutils/gcc/gdb: [...] new 2e3739a91b11 444: onsuccess: #1: 7: Success after binutils/gcc/gdb: 11 commits new f52bf7510ccf 445: onsuccess: #2148: 7: Success after binutils/gcc/linux [...] new 70d435da5271 446: onsuccess: #2: 7: Success after binutils/gcc/linux/gd [...] new a6828d6dc0e3 447: onsuccess: #2149: 7: Success after binutils/gcc/glibc [...] new 4f1612e48887 448: onsuccess: #3: 7: Success after binutils/gcc/glibc/gd [...] new c26bf306345a 449: onsuccess: #4: 7: Success after binutils/gcc/gdb/qemu [...] new 687d837b830d 450: onsuccess: #5: 7: Success after binutils/gcc/linux/gl [...] new e62c81c51bf3 451: onsuccess: #6: 7: Success after binutils/gcc/linux/gd [...] new cae0ccb02966 452: onsuccess: #7: 7: Success after baseline build: no ne [...] new 394ac49dab1a 453: onsuccess: #8: 7: Success after binutils/gcc/gdb: 6 commits new 60d03b3d63e7 454: onsuccess: #9: 7: Success after binutils/gcc/linux/gl [...] new 600765432f7e 455: onsuccess: #10: 7: Success after binutils/gcc/linux/g [...] new 4eac9085e6ff 456: onsuccess: #11: 7: Success after binutils/gcc/linux/g [...] new 7f6bb41e199b 457: onsuccess: #12: 7: Success after binutils/gcc/linux/g [...] new c61170579ef3 458: onsuccess: #13: 7: Success after binutils/gcc/linux/g [...] new 8572de963eec 459: onsuccess: #14: 7: Success after binutils/gcc/linux/g [...] new fd929496637a 460: onsuccess: #15: 7: Success after binutils/gcc/linux/g [...] new ecfc2548c34d 461: onsuccess: #16: 7: Success after binutils/gcc/linux/g [...] new c36596cde154 462: onsuccess: #17: 7: Success after binutils/gcc/linux/g [...] new ed7bd963917f 463: onsuccess: #18: 7: Success after binutils/gcc/linux/g [...] new 1a5ec97f7562 464: onsuccess: #19: 7: Success after binutils/gcc/linux/g [...] new 818e842d4fd4 465: onsuccess: #20: 7: Success after binutils/gcc/linux/g [...] new f1f91168800a 466: onsuccess: #21: 7: Success after binutils/gcc/linux/g [...] new addd81fbf732 467: onsuccess: #22: 7: Success after binutils/gcc/linux/g [...] new 760200a82d30 468: onsuccess: #23: 7: Success after binutils/gcc/linux/g [...] new 14cfee67df75 469: onsuccess: #24: 7: Success after binutils/gcc/linux/g [...] new 8838b47aa8fe 470: onsuccess: #25: 7: Success after binutils/gcc/linux/g [...] new ee4636f6a6bc 471: onsuccess: #26: 7: Success after binutils/gcc/linux/g [...] new 16c080e85008 472: onsuccess: #27: 7: Success after binutils/gcc/linux/g [...] new aa8823fd4b7c 473: onsuccess: #29: 7: Success after binutils/gcc/linux/g [...] new be8060f4473e 474: onsuccess: #30: 7: Success after binutils/gcc/linux/g [...] new b85adb41b54c 475: onsuccess: #31: 7: Success after binutils/gcc/linux/g [...] new 2017e533c2fc 476: onsuccess: #32: 7: Success after binutils/gcc/linux/g [...] new db5d56ce28c8 477: onsuccess: #33: 7: Success after binutils/gcc/linux/g [...] new eb44e5fcb75d 478: onsuccess: #34: 7: Success after binutils/gcc/linux/g [...] new 0268eb34ac4c 479: onsuccess: #36: 7: Success after binutils/gcc/linux/g [...] new b358b9e472c0 480: onsuccess: #37: 7: Success after binutils/gcc/linux/g [...] new f5e382fbeb3b 481: onsuccess: #39: 7: [TCWG CI] Success after binutils/g [...] new 92942d573e0f 482: onsuccess: #40: 7: [TCWG CI] Success after binutils/g [...] new ef039065a831 483: onsuccess: #41: 7: [TCWG CI] Success after binutils/g [...] new 269d00d916ea 484: onsuccess: #42: 7: [TCWG CI] Success after binutils/g [...] new e4cf8a18f378 485: onsuccess: #43: 7: [TCWG CI] Success after binutils/g [...] new 6801752f6958 486: onsuccess: #44: 7: [TCWG CI] Success after binutils/g [...] This update added new revisions after undoing existing revisions. That is to say, some revisions that were in the old version of the branch are not in the new version. This situation occurs when a user --force pushes a change and generates a repository containing something like this: * -- * -- B -- O -- O -- O (24f351b4fa4a) \ N -- N -- N refs/heads/linaro-local/ci/tcwg_gnu_cross_build/master-a [...] 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 2088 -> 2076 bytes 02-prepare_abe/console.log.xz | Bin 2536 -> 2516 bytes 04-build_abe-binutils/console.log.xz | Bin 27868 -> 27220 bytes 05-build_abe-stage1/console.log.xz | Bin 71736 -> 71672 bytes 07-build_abe-linux/console.log.xz | Bin 8904 -> 8628 bytes 08-build_abe-glibc/console.log.xz | Bin 241860 -> 241548 bytes 09-build_abe-stage2/console.log.xz | Bin 202824 -> 202256 bytes 10-build_abe-gdb/console.log.xz | Bin 35224 -> 34696 bytes 11-build_abe-qemu/console.log.xz | Bin 32480 -> 32564 bytes 12-check_regression/console.log.xz | Bin 4012 -> 3972 bytes 13-update_baseline/console.log | 34 +++++++++++++++---------------- dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- git/gdb_rev | 2 +- git/linux_rev | 2 +- mail/changes-list-long.txt | 28 +++++++++++--------------- mail/changes-list-short.txt | 2 +- mail/last_good.sh | 38 +++++++++++++++++------------------ manifest.sh | 38 +++++++++++++++++------------------ 20 files changed, 73 insertions(+), 77 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

1 year, 7 months

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_bmk-code_size-spec2k6/llvm-aarch64-master-Oz updated (9103a8117c6a -> 160c54b44399)

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-aarch64-master-Oz in repository toolchain/ci/base-artifacts. from 9103a8117c6a 52: onsuccess: #11: 1: [TCWG CI] No change after llvm: 292 [...] new 160c54b44399 53: force: #13: 1: [TCWG CI] Success after llvm: 469 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 1952 -> 1880 bytes 02-build_bmk_llvm/console.log.xz | Bin 98844 -> 99624 bytes 03-benchmark/benchmark-build.log | 126 +- 03-benchmark/benchmark.log | 124 +- 03-benchmark/console.log.xz | Bin 3780 -> 3828 bytes .../compare-results-vs-first-internal.csv | 131 +- .../compare-results-vs-prev-internal.csv | 149 +- 04-check_regression/console.log.xz | Bin 10448 -> 10596 bytes .../csv-results-vs-first-1/md5sum.csv | 1743 +- .../csv-results-vs-first-1/perf.csv | 1975 +- .../csv-results-vs-first-1/results.csv | 4467 +- .../csv-results-vs-first-1/size.csv | 92000 ++++++++++--------- 04-check_regression/csv-results-vs-first-1/sve.csv | 14 +- .../csv-results-vs-prev-0/md5sum.csv | 1321 +- 04-check_regression/csv-results-vs-prev-0/perf.csv | 1941 +- .../csv-results-vs-prev-0/results.csv | 2330 +- .../csv-results-vs-prev-1/md5sum.csv | 1743 +- 04-check_regression/csv-results-vs-prev-1/perf.csv | 1975 +- .../csv-results-vs-prev-1/results.csv | 4467 +- 04-check_regression/csv-results-vs-prev-1/size.csv | 92000 ++++++++++--------- 04-check_regression/csv-results-vs-prev-1/sve.csv | 14 +- 04-check_regression/results-vs-first-brief.csv | 42 +- 04-check_regression/results-vs-first-full.csv | 2025 +- 04-check_regression/results-vs-first-internal.csv | 131 +- 04-check_regression/results-vs-first.csv | 131 +- 04-check_regression/results-vs-first.log | 1010 +- 04-check_regression/results-vs-prev-brief.csv | 42 +- 04-check_regression/results-vs-prev-compare.csv | 17 +- 04-check_regression/results-vs-prev-full.csv | 2129 +- 04-check_regression/results-vs-prev-internal.csv | 139 +- 04-check_regression/results-vs-prev.csv | 139 +- 04-check_regression/results-vs-prev.log | 1008 +- 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 +- .../410.bwaves/results-metadata.json | 10 +- .../416.gamess/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 +- .../434.zeusmp/results-metadata.json | 10 +- .../435.gromacs/results-metadata.json | 10 +- .../436.cactusADM/results-metadata.json | 10 +- .../437.leslie3d/results-metadata.json | 10 +- .../squad-vs-first/444.namd/results-metadata.json | 10 +- .../squad-vs-first/445.gobmk/results-metadata.json | 10 +- .../squad-vs-first/445.gobmk/results-metrics.json | 2 +- .../447.dealII/results-metadata.json | 10 +- .../450.soplex/results-metadata.json | 10 +- .../squad-vs-first/450.soplex/results-metrics.json | 2 +- .../453.povray/results-metadata.json | 10 +- .../454.calculix/results-metadata.json | 10 +- .../squad-vs-first/456.hmmer/results-metadata.json | 10 +- .../squad-vs-first/458.sjeng/results-metadata.json | 10 +- .../459.GemsFDTD/results-metadata.json | 10 +- .../462.libquantum/results-metadata.json | 10 +- .../464.h264ref/results-metadata.json | 10 +- .../464.h264ref/results-metrics.json | 2 +- .../squad-vs-first/465.tonto/results-metadata.json | 10 +- .../squad-vs-first/470.lbm/results-metadata.json | 10 +- .../471.omnetpp/results-metadata.json | 10 +- .../squad-vs-first/473.astar/results-metadata.json | 10 +- .../squad-vs-first/473.astar/results-metrics.json | 2 +- .../squad-vs-first/481.wrf/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 | 122 +- git/llvm_rev | 2 +- mail/changes-list-long.txt | 8 + mail/changes-list-short.txt | 1 + manifest.sh => mail/last_good.sh | 0 mail/mail-body.txt | 19 - mail/mail-subject.txt | 1 - mail/short-diag.txt | 1 + manifest.sh | 16 +- results_id | 2 +- 81 files changed, 106889 insertions(+), 106934 deletions(-) create mode 100644 mail/changes-list-long.txt create mode 100644 mail/changes-list-short.txt copy manifest.sh => mail/last_good.sh (100%) delete mode 100644 mail/mail-body.txt delete mode 100644 mail/mail-subject.txt create mode 100644 mail/short-diag.txt -- To stop receiving notification emails like this one, please contact the administrator of this repository.

1 year, 7 months

Jump to page:

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

Tcwg-commits April 2023