Tcwg-commits January 2023

tcwg-commits@lists.linaro.org

5 participants
4127 discussions

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_gcc_bootstrap/release-aarch64-bootstrap_profiled_lto_lean updated (df34daacb8 -> c3ce16189a)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. tcwg-buildslave pushed a change to branch linaro-local/ci/tcwg_gcc_bootstrap/release-aarch64-bootstrap_profiled_lto_lean in repository toolchain/ci/base-artifacts. from df34daacb8 43: onsuccess: #156: 2: Success after binutils/gcc: 13 commits new c3ce16189a 44: onsuccess: #161: 2: Success after binutils/gcc: 24 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 1740 -> 1740 bytes 02-prepare_abe/console.log.xz | Bin 2748 -> 2760 bytes 04-build_abe-binutils/console.log.xz | Bin 37836 -> 39088 bytes .../console.log.xz | Bin 509296 -> 508504 bytes 06-check_regression/console.log.xz | Bin 2784 -> 2932 bytes dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 2 +- mail/mail-subject.txt | 2 +- manifest.sh | 20 ++++++++++---------- 12 files changed, 16 insertions(+), 16 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 5 months

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_gnu_native_fast_check_gdb/master-aarch64 updated (2c6a9c2d4c -> 6f911f97a9)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. tcwg-buildslave pushed a change to branch linaro-local/ci/tcwg_gnu_native_fast_check_gdb/master-aarch64 in repository toolchain/ci/base-artifacts. from 2c6a9c2d4c 71: onsuccess: #84: 1: Success after binutils/gcc/linux/glib [...] new 6f911f97a9 72: onsuccess: #85: 1: Success after binutils/gcc/linux/glib [...] 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 1800 -> 1784 bytes 02-prepare_abe/console.log.xz | Bin 2748 -> 2744 bytes 03-build_abe-binutils/console.log.xz | Bin 40056 -> 39032 bytes 04-build_abe-gcc/console.log.xz | Bin 214872 -> 214116 bytes 06-build_abe-linux/console.log.xz | Bin 8676 -> 8660 bytes 07-build_abe-glibc/console.log.xz | Bin 245384 -> 245152 bytes 08-build_abe-gdb/console.log.xz | Bin 39972 -> 38716 bytes 09-build_abe-dejagnu/console.log.xz | Bin 3848 -> 3844 bytes 10-build_abe-check_gdb/console.log.xz | Bin 3280 -> 2468 bytes 11-check_regression/console.log.xz | Bin 6252 -> 6076 bytes 11-check_regression/results.compare2 | 18 ++++++++++++----- dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- git/gdb_rev | 2 +- git/glibc_rev | 2 +- git/linux_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 2 +- mail/mail-subject.txt | 2 +- manifest.sh | 36 +++++++++++++++++----------------- sumfiles/gdb.log.xz | Bin 14620 -> 14688 bytes sumfiles/gdb.sum | 7 ++++--- 23 files changed, 44 insertions(+), 35 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 5 months

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_bmk-code_speed-spec2k6/llvm-arm-master-O3_LTO updated (554b039e74 -> 1fe056045f)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. tcwg-buildslave pushed a change to branch linaro-local/ci/tcwg_bmk-code_speed-spec2k6/llvm-arm-master-O3_LTO in repository toolchain/ci/base-artifacts. from 554b039e74 51: force: #9: 1: [TCWG CI] 445.gobmk slowed down by 6% afte [...] new 1fe056045f 52: onsuccess: #10: 1: [TCWG CI] No change after llvm: 598 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 1832 -> 1892 bytes 02-prepare_abe/console.log.xz | Bin 2776 -> 2776 bytes 03-build_abe-binutils/console.log.xz | Bin 31916 -> 32032 bytes 04-build_abe-stage1/console.log.xz | Bin 92060 -> 92332 bytes 06-build_abe-linux/console.log.xz | Bin 8040 -> 8032 bytes 07-build_abe-glibc/console.log.xz | Bin 237508 -> 237656 bytes 08-build_abe-stage2/console.log.xz | Bin 213784 -> 216692 bytes 09-build_llvm-true-false-cflags-/console.log.xz | Bin 61196 -> 62512 bytes 10-benchmark/benchmark-build.log | 112 +- 10-benchmark/benchmark.log | 110 +- 10-benchmark/console.log.xz | Bin 3956 -> 3948 bytes 11-check_regression/console.log.xz | Bin 6616 -> 5948 bytes .../csv-results-vs-first-1/perf.csv | 117 +- .../csv-results-vs-first-1/results.csv | 24513 +- .../csv-results-vs-first-1/size.csv | 276146 +++++++-------- 11-check_regression/csv-results-vs-first-1/sve.csv | 20 +- 11-check_regression/csv-results-vs-prev-0/perf.csv | 118 +- .../csv-results-vs-prev-0/results.csv | 25308 +- 11-check_regression/csv-results-vs-prev-0/size.csv | 314609 +++++++++--------- 11-check_regression/csv-results-vs-prev-0/sve.csv | 20 +- 11-check_regression/csv-results-vs-prev-1/perf.csv | 117 +- .../csv-results-vs-prev-1/results.csv | 24513 +- 11-check_regression/csv-results-vs-prev-1/size.csv | 276146 +++++++-------- 11-check_regression/csv-results-vs-prev-1/sve.csv | 20 +- 11-check_regression/exe.regression | 1 - 11-check_regression/extra-bisect-params | 2 +- 11-check_regression/jira-body.txt | 3 - 11-check_regression/mail-body.txt | 3 - 11-check_regression/mail-subject.txt | 2 +- 11-check_regression/results-vs-first-brief.csv | 40 +- 11-check_regression/results-vs-first-full.csv | 117 +- 11-check_regression/results-vs-first-internal.csv | 50 +- 11-check_regression/results-vs-first.csv | 50 +- 11-check_regression/results-vs-first.log | 748 +- 11-check_regression/results-vs-prev-brief.csv | 40 +- 11-check_regression/results-vs-prev-compare.csv | 2 +- 11-check_regression/results-vs-prev-full.csv | 123 +- 11-check_regression/results-vs-prev-internal.csv | 50 +- 11-check_regression/results-vs-prev.csv | 50 +- 11-check_regression/results-vs-prev.log | 992 +- 11-check_regression/results.regressions | 5 - 11-check_regression/trigger-bisect | 3 - 11-check_regression/trigger-notify | 0 12-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/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 +- .../squad-vs-first/450.soplex/results-metrics.json | 2 +- .../453.povray/results-metadata.json | 10 +- .../squad-vs-first/453.povray/results-metrics.json | 2 +- .../squad-vs-first/456.hmmer/results-metadata.json | 10 +- .../squad-vs-first/458.sjeng/results-metadata.json | 10 +- .../462.libquantum/results-metadata.json | 10 +- .../464.h264ref/results-metadata.json | 10 +- .../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 | 88 +- dashboard/squad-vs-first/summary-annotation.txt | 1 - git/llvm_rev | 2 +- jenkins/jira-status.draft | 4 - jenkins/mail-body.draft | 1050 - jenkins/mail-recipients.draft | 1 - jenkins/mail-subject.draft | 1 - jenkins/notify.sh | 3 - mail/jira-body.txt | 14 +- mail/mail-body.txt | 14 +- mail/mail-subject.txt | 2 +- manifest.sh | 14 +- results | 5 - results_id | 2 +- 84 files changed, 482163 insertions(+), 463402 deletions(-) delete mode 100644 11-check_regression/exe.regression delete mode 100644 11-check_regression/results.regressions delete mode 100644 11-check_regression/trigger-bisect delete mode 100644 11-check_regression/trigger-notify delete mode 100644 jenkins/jira-status.draft delete mode 100644 jenkins/mail-body.draft delete mode 100644 jenkins/mail-recipients.draft delete mode 100644 jenkins/mail-subject.draft delete mode 100755 jenkins/notify.sh -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 5 months

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_gnu_native_check_gcc/master-aarch64 updated (2b4e9e9d13 -> bcd03da604)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. tcwg-buildslave pushed a change to branch linaro-local/ci/tcwg_gnu_native_check_gcc/master-aarch64 in repository toolchain/ci/base-artifacts. discards 2b4e9e9d13 161: onsuccess: #912: 1: Success after binutils/gcc/linux/gl [...] discards 3e5342502a 160: onsuccess: #911: 1: Success after binutils/gcc/linux/gl [...] discards 6688cee79b 159: onsuccess: #910: 1: Success after binutils/gcc/linux/gd [...] discards 399b11fda9 158: onsuccess: #909: 1: Success after binutils/gcc/linux/gd [...] discards dc38b366fd 157: onsuccess: #908: 1: Success after binutils/gcc/linux/gl [...] discards ae1448e3ea 156: onsuccess: #907: 1: Success after binutils/gcc/linux/gd [...] discards baf7daf47a 155: onsuccess: #906: 1: Success after binutils/gcc/linux/gl [...] discards e2b9a413b4 154: onsuccess: #905: 1: Success after binutils/gcc/glibc/gd [...] discards 4ab3613520 153: onsuccess: #904: 1: Success after binutils/gcc/linux/gl [...] discards f9dee73045 152: onsuccess: #903: 1: Success after linux: 22 commits discards d36d6cd416 151: onsuccess: #902: 1: Success after glibc: 8 commits discards 892d293ae2 150: onsuccess: #900: 1: Success after gcc: 11 commits discards 5114e16654 149: onsuccess: #899: 1: Success after binutils: 15 commits discards cc5ddd7405 148: onsuccess: #897: 1: Success after binutils/gcc/linux/gd [...] discards 3a124d7a03 147: onsuccess: #896: 1: Success after binutils/gcc/linux/gd [...] discards 32237e602b 146: onsuccess: #895: 1: Success after binutils/gcc/linux/gl [...] discards 4ceb48628a 145: onsuccess: #894: 1: Success after binutils/gcc/gdb: 9 commits discards 4b1c6fc16f 144: onsuccess: #893: 1: Success after binutils/gcc/gdb: 18 commits discards 5f95bbe2ee 143: onsuccess: #892: 1: Success after binutils/gcc/gdb: 36 commits discards 9ee5416312 142: onsuccess: #891: 1: Success after binutils/gcc/linux/gd [...] discards 0ede901acd 141: onsuccess: #890: 1: Success after binutils/gcc/gdb: 47 commits discards 9bce56f189 140: onsuccess: #889: 1: Success after binutils/gcc/linux/gd [...] discards 8401e35d97 139: onsuccess: #888: 1: Success after binutils/gcc/linux/gl [...] discards 52cb4d3dd7 138: onsuccess: #887: 1: Success after binutils/gcc/linux/gl [...] discards 430efa85f3 137: onsuccess: #886: 1: Success after binutils/gcc/linux/gl [...] discards 1aedeeb7c1 136: onsuccess: #885: 1: Success after binutils/gcc/linux/gl [...] discards cb054b63a2 135: onsuccess: #884: 1: Success after binutils/gcc/linux/gl [...] discards 3ff506703b 134: onsuccess: #883: 1: Success after binutils/gcc/gdb: 14 commits discards fd65ce2fd1 133: onsuccess: #882: 1: Success after binutils/gcc/linux/gd [...] discards 102090b3ff 132: onsuccess: #881: 1: Success after binutils/gcc/linux/gl [...] discards 9879482fcb 131: onsuccess: #880: 1: Success after binutils/gcc/linux/gl [...] discards 11b533c443 130: onsuccess: #879: 1: Success after binutils/gcc/linux/gl [...] discards cf7e88c4e1 129: onsuccess: #878: 1: Success after linux: 3008 commits discards 8a026f43de 128: onsuccess: #876: 1: Success after binutils: 12 commits discards 7e4e29aa8d 127: onsuccess: #874: 1: Success after linux: 219 commits discards cc8d975179 126: onsuccess: #873: 1: Success after glibc: 2 commits discards 71c11cb05a 125: onsuccess: #871: 1: Success after binutils: 26 commits discards ebee22730c 124: onsuccess: #869: 1: Success after binutils/gcc/linux/gd [...] discards 15d16c8578 123: onsuccess: #868: 1: Success after binutils/gcc/linux/gd [...] discards 097cc5fa0d 122: onsuccess: #867: 1: Success after binutils/gcc/linux/gl [...] discards 6002761119 121: onsuccess: #866: 1: Success after binutils/gcc/linux/gl [...] discards ad5c75ebd3 120: onsuccess: #865: 1: Success after binutils/gcc/linux/gl [...] discards 489a9a885e 119: onsuccess: #864: 1: Success after binutils/gcc/linux/gl [...] discards 226e93f252 118: onsuccess: #863: 1: Success after linux: 12 commits discards d5c19876a4 117: onsuccess: #861: 1: Success after binutils: 18 commits discards f02485ac4d 116: onsuccess: #859: 1: Success after binutils/gcc/linux/gd [...] discards 9a35db0adc 115: onsuccess: #858: 1: Success after binutils/gcc/linux/gl [...] discards 93edb679e5 114: onsuccess: #857: 1: Success after binutils/gcc/linux/gl [...] discards 22ab264cb5 113: onsuccess: #856: 1: Success after binutils/gcc/linux/gd [...] discards 4f29d3bc7f 112: onsuccess: #855: 1: Success after binutils/gcc/linux/gl [...] discards 9e259ad04d 111: onsuccess: #854: 1: Success after binutils/gcc/linux/gl [...] discards 1d53c830b6 110: onsuccess: #853: 1: Success after binutils/gcc/linux/gl [...] discards 2086219c8b 109: onsuccess: #852: 1: Success after binutils/gcc/linux/gd [...] discards 68995e200f 108: onsuccess: #850: 1: Success after gcc: 2 commits discards 8b5901289b 107: onsuccess: #849: 1: Success after binutils: 5 commits discards ab4ef0225a 106: onsuccess: #847: 1: Success after binutils/gcc/linux/gd [...] discards a801550d04 105: onsuccess: #846: 1: Success after binutils/gcc/linux/gd [...] discards dd846699b5 104: onsuccess: #845: 1: Success after binutils/gcc/gdb: 64 commits discards 32ae7b4ac4 103: onsuccess: #844: 1: Success after binutils/gcc/gdb: 52 commits discards e284b83486 102: onsuccess: #843: 1: Success after binutils/gcc/linux/gl [...] discards 0b170f6ef9 101: onsuccess: #842: 1: Success after binutils/gcc/linux/gd [...] discards 51f8d4f767 100: onsuccess: #841: 1: Success after binutils/gcc/linux/gd [...] discards fab4f9fcc1 99: onsuccess: #840: 1: Success after binutils/gcc/linux/gdb [...] discards 79353145ad 98: onsuccess: #839: 1: Success after binutils/gcc/linux/gli [...] discards cba9afed3a 97: onsuccess: #838: 1: Success after binutils/gcc/linux/gdb [...] discards c24a0e907d 96: onsuccess: #837: 1: Success after binutils/gcc/linux/gli [...] discards e70492e441 95: onsuccess: #835: 1: Success after binutils: 3 commits discards c6cc6a9616 94: onsuccess: #832: 1: Success after binutils: 5 commits discards 36d2c8f6c6 93: onsuccess: #830: 1: Success after binutils/gcc/linux/gdb [...] discards 76fb20ea0d 92: onsuccess: #829: 1: Success after binutils/gcc/linux/gli [...] discards 1da0d24c6e 91: onsuccess: #828: 1: Success after binutils/gcc/linux/gli [...] discards f8d07bb418 90: onsuccess: #827: 1: Success after binutils/gcc/linux/gli [...] discards 5b8d21aa42 89: onsuccess: #826: 1: Success after binutils/gcc/linux/gli [...] discards df4ebae523 88: onsuccess: #825: 1: Success after binutils/gcc/linux/gdb [...] discards 8dcf84603d 87: onsuccess: #824: 1: Success after binutils/gcc/linux/gli [...] discards 00e42c98e3 86: onsuccess: #823: 1: Success after binutils/gcc/linux/gli [...] discards 35aebf7af3 85: onsuccess: #822: 1: Success after binutils/gcc/linux/gli [...] discards 94060ae909 84: onsuccess: #821: 1: Success after binutils/gcc/linux/gli [...] discards f3f5597602 83: onsuccess: #820: 1: Success after binutils/gcc/linux/gli [...] discards 88cb9b092a 82: onsuccess: #819: 1: Success after binutils/gcc/linux/gli [...] discards 665804dccd 81: onsuccess: #818: 1: Success after binutils/gcc/linux/gdb [...] discards 65eaa6a1c6 80: onsuccess: #817: 1: Success after binutils/gcc/linux/gli [...] discards 79d65be530 79: onsuccess: #816: 1: Success after binutils/gcc/linux/gli [...] discards 550c2d9b7e 78: onsuccess: #815: 1: Success after binutils/gcc/linux/gli [...] discards 90b57b6963 77: onsuccess: #814: 1: Success after binutils/gcc/linux/gli [...] discards 79ca30e23f 76: onsuccess: #813: 1: Success after binutils/gcc/linux/gli [...] discards 2ef5a41eb7 75: onsuccess: #812: 1: Success after binutils/gcc/linux/gli [...] discards 7a9a6af5e4 74: onsuccess: #811: 1: Success after binutils/gcc/linux/gdb [...] discards c0a07f7818 73: onsuccess: #810: 1: Success after binutils/gcc/linux/gdb [...] discards c64bc0439c 72: onsuccess: #809: 1: Success after binutils/gcc/linux/gli [...] discards a91592788a 71: onsuccess: #808: 1: Success after binutils/gcc/glibc/gdb [...] discards b2ddc84c39 70: onsuccess: #807: 1: Success after binutils/gcc/linux/gli [...] discards 8224b31755 69: onsuccess: #806: 1: Success after binutils/gcc/linux/gli [...] discards d982ca11ea 68: onsuccess: #805: 1: Success after binutils/gcc/linux/gli [...] discards c95577f810 67: onsuccess: #804: 1: Success after binutils/gcc/linux/gdb [...] discards 779f68d894 66: onsuccess: #803: 1: Success after binutils/gcc/linux/gli [...] discards 50ef11400d 65: onsuccess: #802: 1: Success after binutils/gcc/linux/gli [...] discards 67c5d53a90 64: onsuccess: #801: 1: Success after binutils/gcc/linux/gli [...] discards 199a82387c 63: onsuccess: #800: 1: Success after binutils/gcc/linux/gli [...] discards 8ef8e16110 62: onsuccess: #799: 1: Success after binutils/gcc/linux/gdb [...] discards f064d2abba 61: onsuccess: #798: 1: Success after binutils/gcc/linux/gli [...] new 6161bcf127 61: onsuccess: #798: 1: Success after binutils/gcc/linux/gli [...] new ecc5d2ca55 62: onsuccess: #799: 1: Success after binutils/gcc/linux/gdb [...] new 51cdf75d4f 63: onsuccess: #800: 1: Success after binutils/gcc/linux/gli [...] new 9d60cafc21 64: onsuccess: #801: 1: Success after binutils/gcc/linux/gli [...] new 8e8e99542d 65: onsuccess: #802: 1: Success after binutils/gcc/linux/gli [...] new ad96d111b3 66: onsuccess: #803: 1: Success after binutils/gcc/linux/gli [...] new c01148ba9e 67: onsuccess: #804: 1: Success after binutils/gcc/linux/gdb [...] new 48eb12effe 68: onsuccess: #805: 1: Success after binutils/gcc/linux/gli [...] new 251df57877 69: onsuccess: #806: 1: Success after binutils/gcc/linux/gli [...] new da4933a34f 70: onsuccess: #807: 1: Success after binutils/gcc/linux/gli [...] new 71a443fbbc 71: onsuccess: #808: 1: Success after binutils/gcc/glibc/gdb [...] new 83a5b3f0a8 72: onsuccess: #809: 1: Success after binutils/gcc/linux/gli [...] new 2ad587cbdf 73: onsuccess: #810: 1: Success after binutils/gcc/linux/gdb [...] new 1c090b81bc 74: onsuccess: #811: 1: Success after binutils/gcc/linux/gdb [...] new dad35ea283 75: onsuccess: #812: 1: Success after binutils/gcc/linux/gli [...] new 850cd2615e 76: onsuccess: #813: 1: Success after binutils/gcc/linux/gli [...] new b52b9a26b9 77: onsuccess: #814: 1: Success after binutils/gcc/linux/gli [...] new 33f14640a1 78: onsuccess: #815: 1: Success after binutils/gcc/linux/gli [...] new 954eb04ec9 79: onsuccess: #816: 1: Success after binutils/gcc/linux/gli [...] new 17da679e10 80: onsuccess: #817: 1: Success after binutils/gcc/linux/gli [...] new abf964e546 81: onsuccess: #818: 1: Success after binutils/gcc/linux/gdb [...] new f08329f3b8 82: onsuccess: #819: 1: Success after binutils/gcc/linux/gli [...] new 21405af12c 83: onsuccess: #820: 1: Success after binutils/gcc/linux/gli [...] new eb4c5f5f17 84: onsuccess: #821: 1: Success after binutils/gcc/linux/gli [...] new 963713a2de 85: onsuccess: #822: 1: Success after binutils/gcc/linux/gli [...] new a86fbf98f1 86: onsuccess: #823: 1: Success after binutils/gcc/linux/gli [...] new 7b09297b1d 87: onsuccess: #824: 1: Success after binutils/gcc/linux/gli [...] new 4ac5be6049 88: onsuccess: #825: 1: Success after binutils/gcc/linux/gdb [...] new 71f4672791 89: onsuccess: #826: 1: Success after binutils/gcc/linux/gli [...] new c880868634 90: onsuccess: #827: 1: Success after binutils/gcc/linux/gli [...] new 05710d928a 91: onsuccess: #828: 1: Success after binutils/gcc/linux/gli [...] new 563a8aa1e7 92: onsuccess: #829: 1: Success after binutils/gcc/linux/gli [...] new e00585b684 93: onsuccess: #830: 1: Success after binutils/gcc/linux/gdb [...] new b8f76c15f6 94: onsuccess: #832: 1: Success after binutils: 5 commits new a5fa323ffc 95: onsuccess: #835: 1: Success after binutils: 3 commits new 5c8439d68e 96: onsuccess: #837: 1: Success after binutils/gcc/linux/gli [...] new 55d412fb71 97: onsuccess: #838: 1: Success after binutils/gcc/linux/gdb [...] new 45e2ab3d7e 98: onsuccess: #839: 1: Success after binutils/gcc/linux/gli [...] new 7623017e83 99: onsuccess: #840: 1: Success after binutils/gcc/linux/gdb [...] new a6547816ab 100: onsuccess: #841: 1: Success after binutils/gcc/linux/gd [...] new f4da090d8e 101: onsuccess: #842: 1: Success after binutils/gcc/linux/gd [...] new 2ca08f2968 102: onsuccess: #843: 1: Success after binutils/gcc/linux/gl [...] new d9f43abd66 103: onsuccess: #844: 1: Success after binutils/gcc/gdb: 52 commits new 8b53b0bb0f 104: onsuccess: #845: 1: Success after binutils/gcc/gdb: 64 commits new 143f6277e2 105: onsuccess: #846: 1: Success after binutils/gcc/linux/gd [...] new 3456115688 106: onsuccess: #847: 1: Success after binutils/gcc/linux/gd [...] new b06bb86f37 107: onsuccess: #849: 1: Success after binutils: 5 commits new 4cc746e346 108: onsuccess: #850: 1: Success after gcc: 2 commits new bfce982585 109: onsuccess: #852: 1: Success after binutils/gcc/linux/gd [...] new 9c4a85295b 110: onsuccess: #853: 1: Success after binutils/gcc/linux/gl [...] new 83c46d26de 111: onsuccess: #854: 1: Success after binutils/gcc/linux/gl [...] new 604dc3baa1 112: onsuccess: #855: 1: Success after binutils/gcc/linux/gl [...] new 005b7bc712 113: onsuccess: #856: 1: Success after binutils/gcc/linux/gd [...] new c34e3c3a62 114: onsuccess: #857: 1: Success after binutils/gcc/linux/gl [...] new 90598a5a4f 115: onsuccess: #858: 1: Success after binutils/gcc/linux/gl [...] new 43b132cedd 116: onsuccess: #859: 1: Success after binutils/gcc/linux/gd [...] new a73a80af5e 117: onsuccess: #861: 1: Success after binutils: 18 commits new 6c0afa29e0 118: onsuccess: #863: 1: Success after linux: 12 commits new 3da3713b81 119: onsuccess: #864: 1: Success after binutils/gcc/linux/gl [...] new ca38b287a5 120: onsuccess: #865: 1: Success after binutils/gcc/linux/gl [...] new 482e3ea180 121: onsuccess: #866: 1: Success after binutils/gcc/linux/gl [...] new e3c72a4118 122: onsuccess: #867: 1: Success after binutils/gcc/linux/gl [...] new 0c6778ca18 123: onsuccess: #868: 1: Success after binutils/gcc/linux/gd [...] new ec5c9b8129 124: onsuccess: #869: 1: Success after binutils/gcc/linux/gd [...] new bb85841637 125: onsuccess: #871: 1: Success after binutils: 26 commits new 4ac2972aa6 126: onsuccess: #873: 1: Success after glibc: 2 commits new f5aac2749c 127: onsuccess: #874: 1: Success after linux: 219 commits new 363a46854e 128: onsuccess: #876: 1: Success after binutils: 12 commits new 4ac61be587 129: onsuccess: #878: 1: Success after linux: 3008 commits new 81e3492514 130: onsuccess: #879: 1: Success after binutils/gcc/linux/gl [...] new e30d1ee6b1 131: onsuccess: #880: 1: Success after binutils/gcc/linux/gl [...] new a3e732b73e 132: onsuccess: #881: 1: Success after binutils/gcc/linux/gl [...] new 0caaf02ad1 133: onsuccess: #882: 1: Success after binutils/gcc/linux/gd [...] new 11c24011c6 134: onsuccess: #883: 1: Success after binutils/gcc/gdb: 14 commits new 16b5e47b94 135: onsuccess: #884: 1: Success after binutils/gcc/linux/gl [...] new b9f9146730 136: onsuccess: #885: 1: Success after binutils/gcc/linux/gl [...] new 046ab44f1e 137: onsuccess: #886: 1: Success after binutils/gcc/linux/gl [...] new bdb4dd4ac8 138: onsuccess: #887: 1: Success after binutils/gcc/linux/gl [...] new 1d7e568f2c 139: onsuccess: #888: 1: Success after binutils/gcc/linux/gl [...] new 6945e4e2ff 140: onsuccess: #889: 1: Success after binutils/gcc/linux/gd [...] new c590bb1e9d 141: onsuccess: #890: 1: Success after binutils/gcc/gdb: 47 commits new dedd3b55bf 142: onsuccess: #891: 1: Success after binutils/gcc/linux/gd [...] new 3c1c6ba5ad 143: onsuccess: #892: 1: Success after binutils/gcc/gdb: 36 commits new 0054c8fe5c 144: onsuccess: #893: 1: Success after binutils/gcc/gdb: 18 commits new e85235a54e 145: onsuccess: #894: 1: Success after binutils/gcc/gdb: 9 commits new 0702ca4e34 146: onsuccess: #895: 1: Success after binutils/gcc/linux/gl [...] new 52ac25e114 147: onsuccess: #896: 1: Success after binutils/gcc/linux/gd [...] new ef8b2eb548 148: onsuccess: #897: 1: Success after binutils/gcc/linux/gd [...] new c67b5e36d5 149: onsuccess: #899: 1: Success after binutils: 15 commits new 9389581b2d 150: onsuccess: #900: 1: Success after gcc: 11 commits new ef336fab79 151: onsuccess: #902: 1: Success after glibc: 8 commits new f268d33b2e 152: onsuccess: #903: 1: Success after linux: 22 commits new 9c08884758 153: onsuccess: #904: 1: Success after binutils/gcc/linux/gl [...] new f97666a421 154: onsuccess: #905: 1: Success after binutils/gcc/glibc/gd [...] new 4425793ab2 155: onsuccess: #906: 1: Success after binutils/gcc/linux/gl [...] new ebac7faefc 156: onsuccess: #907: 1: Success after binutils/gcc/linux/gd [...] new c99aebc288 157: onsuccess: #908: 1: Success after binutils/gcc/linux/gl [...] new f85e163943 158: onsuccess: #909: 1: Success after binutils/gcc/linux/gd [...] new 014c4ac866 159: onsuccess: #910: 1: Success after binutils/gcc/linux/gd [...] new 6d0414725b 160: onsuccess: #911: 1: Success after binutils/gcc/linux/gl [...] new 6409ccc2ea 161: onsuccess: #912: 1: Success after binutils/gcc/linux/gl [...] new bcd03da604 162: onsuccess: #913: 1: Success after binutils/gcc/linux/gl [...] This update added new revisions after undoing existing revisions. That is to say, some revisions that were in the old version of the branch are not in the new version. This situation occurs when a user --force pushes a change and generates a repository containing something like this: * -- * -- B -- O -- O -- O (2b4e9e9d13) \ N -- N -- N refs/heads/linaro-local/ci/tcwg_gnu_native_check_gcc/mas [...] You should already have received notification emails for all of the O revisions, and so the following emails describe only the N revisions from the common base, B. Any revisions marked "omits" are not gone; other references still refer to them. Any revisions marked "discards" are gone forever. The 102 revisions listed above as "new" are entirely new to this repository and will be described in separate emails. The revisions listed as "adds" were already present in the repository and have only been added to this reference. Summary of changes: 01-reset_artifacts/console.log.xz | Bin 1764 -> 1760 bytes 02-prepare_abe/console.log.xz | Bin 2748 -> 2748 bytes 03-build_abe-binutils/console.log.xz | Bin 39492 -> 39240 bytes 04-build_abe-gcc/console.log.xz | Bin 214216 -> 214484 bytes 06-build_abe-linux/console.log.xz | Bin 8672 -> 8684 bytes 07-build_abe-glibc/console.log.xz | Bin 245056 -> 245076 bytes 08-build_abe-gdb/console.log.xz | Bin 39196 -> 38600 bytes 09-build_abe-dejagnu/console.log.xz | Bin 3832 -> 3832 bytes 10-build_abe-check_gcc/console.log.xz | Bin 3448 -> 2856 bytes 11-check_regression/console.log.xz | Bin 12732 -> 7824 bytes 11-check_regression/extra-bisect-params | 2 +- 11-check_regression/fails.sum | 437 +-- 11-check_regression/mail-body.txt | 110 +- 11-check_regression/results.compare | 447 +-- 11-check_regression/results.compare2 | 1060 ++----- 11-check_regression/results.regressions | 100 +- 12-update_baseline/console.log | 56 +- dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- git/gdb_rev | 2 +- git/glibc_rev | 2 +- git/linux_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 112 +- mail/mail-subject.txt | 2 +- manifest.sh | 36 +- results | 100 +- sumfiles/g++.log.xz | Bin 3721936 -> 3745392 bytes sumfiles/g++.sum | 32 +- sumfiles/gcc.log.xz | Bin 3287360 -> 3297108 bytes sumfiles/gcc.sum | 4697 ++++++++++++++++--------------- sumfiles/gfortran.log.xz | Bin 1084364 -> 1085344 bytes sumfiles/gfortran.sum | 6 +- sumfiles/libatomic.log.xz | Bin 2272 -> 2268 bytes sumfiles/libatomic.sum | 2 +- sumfiles/libgomp.log.xz | Bin 232388 -> 232304 bytes sumfiles/libgomp.sum | 2 +- sumfiles/libitm.log.xz | Bin 2668 -> 2668 bytes sumfiles/libitm.sum | 2 +- sumfiles/libstdc++.log.xz | Bin 456056 -> 457404 bytes sumfiles/libstdc++.sum | 8 +- 42 files changed, 2860 insertions(+), 4365 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 5 months

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_kernel/llvm-master-arm-lts-allnoconfig updated (25bf166f9a -> da4a78958b)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. tcwg-buildslave pushed a change to branch linaro-local/ci/tcwg_kernel/llvm-master-arm-lts-allnoconfig in repository toolchain/ci/base-artifacts. from 25bf166f9a 36: onsuccess: #438: all: Success after binutils/llvm/qemu: [...] new da4a78958b 37: onsuccess: #439: all: Success after binutils/llvm/linux/ [...] The 1 revisions listed above as "new" are entirely new to this repository and will be described in separate emails. The revisions listed as "adds" were already present in the repository and have only been added to this reference. Summary of changes: 01-reset_artifacts/console.log.xz | Bin 1800 -> 1752 bytes 02-prepare_abe/console.log.xz | Bin 2804 -> 2772 bytes 03-build_abe-binutils/console.log.xz | Bin 32484 -> 31356 bytes 04-build_kernel_llvm/console.log.xz | Bin 65276 -> 63524 bytes 05-build_abe-qemu/console.log.xz | Bin 31452 -> 32020 bytes 06-build_linux/console.log.xz | Bin 3492 -> 3400 bytes 07-boot_linux/console.log.xz | Bin 496 -> 496 bytes 08-check_regression/console.log.xz | Bin 4008 -> 4328 bytes 09-update_baseline/console.log | 8 ++++---- dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/linux_rev | 2 +- git/llvm_rev | 2 +- git/qemu_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 2 +- mail/mail-subject.txt | 2 +- manifest.sh | 32 ++++++++++++++++---------------- 18 files changed, 28 insertions(+), 28 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 5 months

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_kernel/llvm-release-aarch64-lts-allyesconfig updated (f24aad06d0 -> 6770be7dd5)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. tcwg-buildslave pushed a change to branch linaro-local/ci/tcwg_kernel/llvm-release-aarch64-lts-allyesconfig in repository toolchain/ci/base-artifacts. from f24aad06d0 36: onsuccess: #257: all: Success after llvm/qemu: 261 commits new 6770be7dd5 37: onsuccess: #258: all: Success after binutils/llvm/linux/ [...] The 1 revisions listed above as "new" are entirely new to this repository and will be described in separate emails. The revisions listed as "adds" were already present in the repository and have only been added to this reference. Summary of changes: 01-reset_artifacts/console.log.xz | Bin 1772 -> 1956 bytes 02-prepare_abe/console.log.xz | Bin 2764 -> 2800 bytes 03-build_abe-binutils/console.log.xz | Bin 30572 -> 31384 bytes 04-build_kernel_llvm/console.log.xz | Bin 63272 -> 63432 bytes 05-build_abe-qemu/console.log.xz | Bin 31276 -> 32728 bytes 06-build_linux/console.log.xz | Bin 3480 -> 3484 bytes 07-boot_linux/console.log.xz | Bin 576 -> 576 bytes 08-check_regression/console.log.xz | Bin 3404 -> 4496 bytes dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/linux_rev | 2 +- git/llvm_rev | 2 +- git/qemu_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 2 +- mail/mail-subject.txt | 2 +- manifest.sh | 32 ++++++++++++++++---------------- 17 files changed, 24 insertions(+), 24 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 5 months

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_kernel/llvm-release-aarch64-lts-allnoconfig updated (d03917e734 -> 4a9f0c7039)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. tcwg-buildslave pushed a change to branch linaro-local/ci/tcwg_kernel/llvm-release-aarch64-lts-allnoconfig in repository toolchain/ci/base-artifacts. from d03917e734 36: onsuccess: #282: boot: Success after llvm/qemu: 261 commits new 4a9f0c7039 37: onsuccess: #283: boot: Success after binutils/llvm/linux [...] The 1 revisions listed above as "new" are entirely new to this repository and will be described in separate emails. The revisions listed as "adds" were already present in the repository and have only been added to this reference. Summary of changes: 01-reset_artifacts/console.log.xz | Bin 1788 -> 1792 bytes 02-prepare_abe/console.log.xz | Bin 2792 -> 2768 bytes 03-build_abe-binutils/console.log.xz | Bin 31076 -> 31104 bytes 04-build_kernel_llvm/console.log.xz | Bin 63464 -> 65520 bytes 05-build_abe-qemu/console.log.xz | Bin 31644 -> 32464 bytes 06-build_linux/console.log.xz | Bin 3436 -> 3348 bytes 07-boot_linux/console.log.xz | Bin 504 -> 504 bytes 08-check_regression/console.log.xz | Bin 3300 -> 4260 bytes dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/linux_rev | 2 +- git/llvm_rev | 2 +- git/qemu_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 2 +- mail/mail-subject.txt | 2 +- manifest.sh | 32 ++++++++++++++++---------------- 17 files changed, 24 insertions(+), 24 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 5 months

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_kernel/llvm-master-arm-stable-allyesconfig updated (407071ea2b -> 8826ab3ee9)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. tcwg-buildslave pushed a change to branch linaro-local/ci/tcwg_kernel/llvm-master-arm-stable-allyesconfig in repository toolchain/ci/base-artifacts. from 407071ea2b 54: onsuccess: #526: 20699: Success after binutils/llvm/linu [...] new 8826ab3ee9 55: onsuccess: #527: all: Success after binutils/llvm/linux/ [...] The 1 revisions listed above as "new" are entirely new to this repository and will be described in separate emails. The revisions listed as "adds" were already present in the repository and have only been added to this reference. Summary of changes: 01-reset_artifacts/console.log.xz | Bin 1780 -> 1768 bytes 02-prepare_abe/console.log.xz | Bin 2776 -> 2776 bytes 03-build_abe-binutils/console.log.xz | Bin 32088 -> 31500 bytes 04-build_kernel_llvm/console.log.xz | Bin 65056 -> 64888 bytes 05-build_abe-qemu/console.log.xz | Bin 30908 -> 32284 bytes 06-build_linux/console.log.xz | Bin 3928 -> 3736 bytes 07-boot_linux/console.log.xz | Bin 0 -> 496 bytes 08-check_regression/console.log.xz | Bin 4344 -> 4396 bytes 08-check_regression/mail-body.txt | 4 +++- dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/linux_rev | 2 +- git/llvm_rev | 2 +- git/qemu_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 6 ++++-- mail/mail-subject.txt | 2 +- manifest.sh | 32 ++++++++++++++++---------------- results | 4 +++- 19 files changed, 33 insertions(+), 27 deletions(-) create mode 100644 07-boot_linux/console.log.xz -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 5 months

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_gnu_native_build/master-arm updated (6e62ab740b -> a9b3734945)

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 6e62ab740b 170: onsuccess: #594: 6: Success after binutils/gcc/linux/gl [...] discards 2c75837e86 169: onsuccess: #593: 6: Success after binutils/gcc/linux/gl [...] discards 9468309a62 168: onsuccess: #591: 6: Success after binutils/gcc/linux/gd [...] discards 88c2b890d0 167: onsuccess: #590: 6: Success after binutils/gcc/linux/gl [...] discards ec67fcf42f 166: onsuccess: #589: 6: Success after binutils/gcc/linux/gl [...] discards 49d3ab9a56 165: onsuccess: #588: 6: Success after binutils/gcc/linux/gl [...] discards d8716a38fa 164: onsuccess: #587: 6: Success after binutils/gcc/glibc/gd [...] discards 26c3ea4ca7 163: onsuccess: #586: 6: Success after binutils/gcc/linux/gl [...] discards f55664ada3 162: onsuccess: #579: 6: Success after gcc: 11 commits discards c9d7b6f683 161: onsuccess: #578: 6: Success after binutils: 15 commits discards 188bb66d67 160: onsuccess: #576: 6: Success after binutils/gcc/linux/gd [...] discards fe0c6c6d14 159: onsuccess: #575: 6: Success after binutils/gcc/linux/gd [...] discards 57865bf165 158: onsuccess: #574: 6: Success after binutils/gcc/linux/gl [...] discards a1163f6743 157: onsuccess: #573: 6: Success after binutils/gcc/gdb: 9 commits discards 8fcb05ab3b 156: onsuccess: #572: 6: Success after binutils/gcc/gdb: 18 commits discards 7bffa2d3a0 155: onsuccess: #571: 6: Success after binutils/gcc/gdb: 36 commits discards 9944722909 154: onsuccess: #570: 6: Success after binutils/gcc/linux/gd [...] discards c4ced55c65 153: onsuccess: #569: 6: Success after binutils/gcc/gdb: 47 commits discards fbd2b3b4d9 152: onsuccess: #568: 6: Success after binutils/gcc/linux/gd [...] discards 723981cbe4 151: onsuccess: #567: 6: Success after binutils/gcc/linux/gl [...] discards 85a088fdd2 150: onsuccess: #566: 6: Success after binutils/gcc/linux/gl [...] discards a7b4a6e8c3 149: onsuccess: #565: 6: Success after binutils/gcc/linux/gl [...] discards 675181a3b0 148: onsuccess: #564: 6: Success after binutils/gcc/linux/gl [...] discards f2305d67af 147: onsuccess: #563: 6: Success after binutils/gcc/linux/gl [...] discards 3d5ef38691 146: onsuccess: #562: 6: Success after binutils/gcc/gdb: 14 commits discards 51cab6802e 145: onsuccess: #561: 6: Success after binutils/gcc/linux/gd [...] discards 2f663c4396 144: onsuccess: #560: 6: Success after binutils/gcc/linux/gl [...] discards df7aa76444 143: onsuccess: #559: 6: Success after binutils/gcc/linux/gl [...] discards af671d7417 142: onsuccess: #558: 6: Success after binutils/gcc/linux/gl [...] discards ba24623664 141: onsuccess: #557: 6: Success after binutils/gcc/linux/gd [...] discards f41b098ddf 140: onsuccess: #556: 6: Success after binutils/gcc/linux/gl [...] discards 30711340ed 139: onsuccess: #555: 6: Success after binutils/gcc/linux/gd [...] discards 620818aad6 138: onsuccess: #554: 6: Success after binutils/gcc/linux/gd [...] discards f19ee08bcf 137: onsuccess: #553: 6: Success after binutils/gcc/linux/gl [...] discards 81801fc809 136: onsuccess: #551: 6: Success after binutils/gcc/linux/gl [...] discards a83e6cb913 135: onsuccess: #550: 6: Success after binutils/gcc/linux/gl [...] discards 99e3c7fe50 134: onsuccess: #544: 6: Success after binutils: 18 commits discards f83786b4ed 133: onsuccess: #542: 6: Success after binutils/gcc/linux/gd [...] discards b8b30a02da 132: onsuccess: #541: 6: Success after binutils/gcc/linux/gl [...] discards fd1e0b82a4 131: onsuccess: #540: 6: Success after binutils/gcc/linux/gd [...] discards a3fdcf279a 130: onsuccess: #539: 6: Success after binutils/gcc/linux/gl [...] discards 2f80f5ac75 129: onsuccess: #538: 6: Success after binutils/gcc/linux/gl [...] discards d8bd2d6fca 128: onsuccess: #537: 6: Success after binutils/gcc/linux/gl [...] discards 18d59080a5 127: onsuccess: #536: 6: Success after binutils/gcc/linux/gd [...] discards dcdfd00e76 126: onsuccess: #535: 6: Success after binutils/gcc/linux/gd [...] discards 75d4b1dfc7 125: onsuccess: #534: 6: Success after binutils/gcc/linux/gd [...] discards b76659042f 124: onsuccess: #533: 6: Success after binutils/gcc/linux/gd [...] discards 369a15d6c9 123: onsuccess: #532: 6: Success after binutils/gcc/gdb: 64 commits discards 72dfcc0c8c 122: onsuccess: #531: 6: Success after binutils/gcc/gdb: 52 commits discards 859de2283a 121: onsuccess: #530: 6: Success after binutils/gcc/linux/gl [...] discards 0a0595f950 120: onsuccess: #529: 6: Success after binutils/gcc/linux/gd [...] discards 0efc2b5e29 119: onsuccess: #528: 6: Success after binutils/gcc/linux/gd [...] discards c86b5b0ed5 118: onsuccess: #527: 6: Success after binutils/gcc/linux/gl [...] discards 0f9066c504 117: onsuccess: #526: 6: Success after binutils/gcc/linux/gd [...] discards 872b82c4b9 116: onsuccess: #525: 6: Success after binutils/gcc/linux/gd [...] discards 8b890219dd 115: onsuccess: #524: 6: Success after binutils/gcc/linux/gl [...] discards 0c1446a36b 114: onsuccess: #523: 1: Success after binutils/gcc: 18 commits discards 4bc8db0c96 113: onsuccess: #522: 1: Success after gcc: 12 commits discards 1dc35b3d47 112: force: #521: 1: Failure after basepoints/gcc-13-3918-gb [...] discards a429a6d3e1 111: force: #520: 6: Success after gcc: 9 commits discards 7832eecaaf 110: onsuccess: #518: 6: Success after binutils: 5 commits discards 5a1988438f 109: onsuccess: #516: 6: Success after binutils/gcc/linux/gl [...] discards 999cbad3e1 108: onsuccess: #514: 6: Success after binutils/gcc/linux/gl [...] discards 5bcfb9a701 107: onsuccess: #513: 6: Success after binutils/gcc/linux/gl [...] discards ae69fd72cc 106: onsuccess: #512: 6: Success after binutils/gcc/linux/gl [...] discards 4c82360471 105: onsuccess: #511: 6: Success after binutils/gcc/linux/gd [...] discards 54d1db8495 104: onsuccess: #510: 6: Success after binutils/gcc/linux/gl [...] discards c30155e80e 103: onsuccess: #509: 6: Success after binutils/gcc/linux/gl [...] discards ee7dceaa1e 102: onsuccess: #508: 6: Success after binutils/gcc/linux/gl [...] discards 6d97ca30e2 101: onsuccess: #507: 4: Success after binutils/gcc/linux/gl [...] discards f88efdc638 100: onsuccess: #506: 4: Success after baseline build: no ne [...] discards 65478396ff 99: force: #505: 4: Failure after basepoints/gcc-13-3596-ge7 [...] discards 440a0043d8 98: force: #504: 6: Success after gcc: 18 commits discards bb9a17c04b 97: onsuccess: #503: 6: Success after linux: 11 commits discards 9c3bc7bb24 96: onsuccess: #502: 6: Success after glibc: 10 commits discards 76b38df206 95: onsuccess: #500: 6: Success after binutils: 8 commits discards 39bf0f9962 94: onsuccess: #498: 6: Success after binutils/gcc/linux/gli [...] discards 5cab52d1ac 93: onsuccess: #497: 6: Success after binutils/gcc/linux/gdb [...] discards 3a3b2fa947 92: onsuccess: #496: 6: Success after binutils/gcc/linux/gli [...] discards a0e245495b 91: onsuccess: #495: 6: Success after binutils/gcc/linux/gli [...] discards 82029a0d60 90: onsuccess: #494: 6: Success after binutils/gcc/linux/gli [...] discards fe3e79d2e8 89: onsuccess: #492: 6: Success after binutils/gcc/linux/gli [...] discards 4a0a1ec0f2 88: onsuccess: #491: 6: Success after binutils/gcc/linux/gli [...] discards 836cb70fbb 87: onsuccess: #490: 6: Success after binutils/gcc/linux/gdb [...] discards 56e62b6222 86: onsuccess: #489: 6: Success after binutils/gcc/linux/gdb [...] discards ccc678c380 85: onsuccess: #488: 6: Success after binutils/gcc/linux/gli [...] discards c323d537ab 84: onsuccess: #487: 6: Success after binutils/gcc/glibc/gdb [...] discards 4875baae5e 83: onsuccess: #486: 6: Success after binutils/gcc/linux/gli [...] discards ecaa78e214 82: onsuccess: #485: 6: Success after binutils/gcc/linux/gli [...] discards b1eca5c6b2 81: onsuccess: #484: 6: Success after binutils/gcc/linux/gli [...] discards b04e412b12 80: onsuccess: #483: 6: Success after binutils/gcc/linux/gdb [...] discards 2c0de3788b 79: onsuccess: #482: 6: Success after binutils/gcc/linux/gli [...] discards 1155179a5c 78: onsuccess: #481: 6: Success after binutils/gcc/linux/gli [...] discards 4e38e15793 77: onsuccess: #480: 6: Success after binutils/gcc/linux/gli [...] discards 818f462a9f 76: onsuccess: #479: 6: Success after binutils/gcc/linux/gli [...] discards 6280cade0c 75: onsuccess: #478: 6: Success after binutils/gcc/linux/gli [...] discards f71ccbb4df 74: onsuccess: #477: 6: Success after binutils/gcc/linux/gli [...] discards 023e4d8eb2 73: onsuccess: #476: 6: Success after binutils/gcc/linux/gli [...] discards 1ae6184e46 72: onsuccess: #475: 6: Success after binutils/gcc/linux/gli [...] discards bb90359e9f 71: onsuccess: #474: 6: Success after binutils/gcc/linux/gdb [...] discards a720618d70 70: onsuccess: #473: 6: Success after binutils/gcc/linux/gli [...] new 5a33a6fc8e 70: onsuccess: #473: 6: Success after binutils/gcc/linux/gli [...] new ac907879ea 71: onsuccess: #474: 6: Success after binutils/gcc/linux/gdb [...] new 519a25baf6 72: onsuccess: #475: 6: Success after binutils/gcc/linux/gli [...] new a4195d9f05 73: onsuccess: #476: 6: Success after binutils/gcc/linux/gli [...] new 3bfac5126c 74: onsuccess: #477: 6: Success after binutils/gcc/linux/gli [...] new 48ce857737 75: onsuccess: #478: 6: Success after binutils/gcc/linux/gli [...] new ae19bc55fd 76: onsuccess: #479: 6: Success after binutils/gcc/linux/gli [...] new 7ed6707342 77: onsuccess: #480: 6: Success after binutils/gcc/linux/gli [...] new be9520f583 78: onsuccess: #481: 6: Success after binutils/gcc/linux/gli [...] new 6a3f846a9f 79: onsuccess: #482: 6: Success after binutils/gcc/linux/gli [...] new dcbf50a274 80: onsuccess: #483: 6: Success after binutils/gcc/linux/gdb [...] new 685c0055cb 81: onsuccess: #484: 6: Success after binutils/gcc/linux/gli [...] new ae5ecf2cd6 82: onsuccess: #485: 6: Success after binutils/gcc/linux/gli [...] new 02314ee86d 83: onsuccess: #486: 6: Success after binutils/gcc/linux/gli [...] new ce42fd17ea 84: onsuccess: #487: 6: Success after binutils/gcc/glibc/gdb [...] new 647590df69 85: onsuccess: #488: 6: Success after binutils/gcc/linux/gli [...] new f8024a6e44 86: onsuccess: #489: 6: Success after binutils/gcc/linux/gdb [...] new 95f773274f 87: onsuccess: #490: 6: Success after binutils/gcc/linux/gdb [...] new 79daf336d6 88: onsuccess: #491: 6: Success after binutils/gcc/linux/gli [...] new dad6f77bf6 89: onsuccess: #492: 6: Success after binutils/gcc/linux/gli [...] new ff9d1c3385 90: onsuccess: #494: 6: Success after binutils/gcc/linux/gli [...] new 9163e46fd5 91: onsuccess: #495: 6: Success after binutils/gcc/linux/gli [...] new 1c4bd07bf2 92: onsuccess: #496: 6: Success after binutils/gcc/linux/gli [...] new 19ed8141aa 93: onsuccess: #497: 6: Success after binutils/gcc/linux/gdb [...] new bf13e77f97 94: onsuccess: #498: 6: Success after binutils/gcc/linux/gli [...] new 0ff65a6588 95: onsuccess: #500: 6: Success after binutils: 8 commits new e1165ae8e6 96: onsuccess: #502: 6: Success after glibc: 10 commits new 2284fe5dfa 97: onsuccess: #503: 6: Success after linux: 11 commits new 343bf4f3dc 98: force: #504: 6: Success after gcc: 18 commits new 172dbec98f 99: force: #505: 4: Failure after basepoints/gcc-13-3596-ge7 [...] new 1c29c84791 100: onsuccess: #506: 4: Success after baseline build: no ne [...] new 2b1073f224 101: onsuccess: #507: 4: Success after binutils/gcc/linux/gl [...] new 637b1ae2e6 102: onsuccess: #508: 6: Success after binutils/gcc/linux/gl [...] new 3fab7c9136 103: onsuccess: #509: 6: Success after binutils/gcc/linux/gl [...] new 72c307b980 104: onsuccess: #510: 6: Success after binutils/gcc/linux/gl [...] new 3923eb45da 105: onsuccess: #511: 6: Success after binutils/gcc/linux/gd [...] new 2676010fa6 106: onsuccess: #512: 6: Success after binutils/gcc/linux/gl [...] new b128869503 107: onsuccess: #513: 6: Success after binutils/gcc/linux/gl [...] new 8500a32a8f 108: onsuccess: #514: 6: Success after binutils/gcc/linux/gl [...] new 2e0bceec50 109: onsuccess: #516: 6: Success after binutils/gcc/linux/gl [...] new 7eb30d0a5a 110: onsuccess: #518: 6: Success after binutils: 5 commits new e5c99f7dd3 111: force: #520: 6: Success after gcc: 9 commits new 0ab4cbb552 112: force: #521: 1: Failure after basepoints/gcc-13-3918-gb [...] new d5919c9f61 113: onsuccess: #522: 1: Success after gcc: 12 commits new aaf9f8292f 114: onsuccess: #523: 1: Success after binutils/gcc: 18 commits new 1d8d123c5b 115: onsuccess: #524: 6: Success after binutils/gcc/linux/gl [...] new 6ee07149d4 116: onsuccess: #525: 6: Success after binutils/gcc/linux/gd [...] new 8d6b34c32f 117: onsuccess: #526: 6: Success after binutils/gcc/linux/gd [...] new f6e82bc022 118: onsuccess: #527: 6: Success after binutils/gcc/linux/gl [...] new 3a4fbd9543 119: onsuccess: #528: 6: Success after binutils/gcc/linux/gd [...] new 310696261c 120: onsuccess: #529: 6: Success after binutils/gcc/linux/gd [...] new 8a0b6c5458 121: onsuccess: #530: 6: Success after binutils/gcc/linux/gl [...] new c8499dd446 122: onsuccess: #531: 6: Success after binutils/gcc/gdb: 52 commits new ee38fe7abd 123: onsuccess: #532: 6: Success after binutils/gcc/gdb: 64 commits new 1ed1bfafca 124: onsuccess: #533: 6: Success after binutils/gcc/linux/gd [...] new 13c6c20dec 125: onsuccess: #534: 6: Success after binutils/gcc/linux/gd [...] new 5b032cffc5 126: onsuccess: #535: 6: Success after binutils/gcc/linux/gd [...] new 5e8144de31 127: onsuccess: #536: 6: Success after binutils/gcc/linux/gd [...] new 66427bc667 128: onsuccess: #537: 6: Success after binutils/gcc/linux/gl [...] new ef6085a6da 129: onsuccess: #538: 6: Success after binutils/gcc/linux/gl [...] new 1bb39993a9 130: onsuccess: #539: 6: Success after binutils/gcc/linux/gl [...] new 0f21651f54 131: onsuccess: #540: 6: Success after binutils/gcc/linux/gd [...] new be2c8ccb11 132: onsuccess: #541: 6: Success after binutils/gcc/linux/gl [...] new 73526d870e 133: onsuccess: #542: 6: Success after binutils/gcc/linux/gd [...] new f0115200be 134: onsuccess: #544: 6: Success after binutils: 18 commits new 5b8fa35cc0 135: onsuccess: #550: 6: Success after binutils/gcc/linux/gl [...] new 2ff2398686 136: onsuccess: #551: 6: Success after binutils/gcc/linux/gl [...] new c15c50ac05 137: onsuccess: #553: 6: Success after binutils/gcc/linux/gl [...] new 424df72832 138: onsuccess: #554: 6: Success after binutils/gcc/linux/gd [...] new 94665f2dbe 139: onsuccess: #555: 6: Success after binutils/gcc/linux/gd [...] new 59417f6c5f 140: onsuccess: #556: 6: Success after binutils/gcc/linux/gl [...] new 49d1e4564c 141: onsuccess: #557: 6: Success after binutils/gcc/linux/gd [...] new 683bf210b5 142: onsuccess: #558: 6: Success after binutils/gcc/linux/gl [...] new d787d1e698 143: onsuccess: #559: 6: Success after binutils/gcc/linux/gl [...] new 65f8e01294 144: onsuccess: #560: 6: Success after binutils/gcc/linux/gl [...] new 9e0c592b7d 145: onsuccess: #561: 6: Success after binutils/gcc/linux/gd [...] new 68352f0c93 146: onsuccess: #562: 6: Success after binutils/gcc/gdb: 14 commits new 320858729f 147: onsuccess: #563: 6: Success after binutils/gcc/linux/gl [...] new f5c3e330b0 148: onsuccess: #564: 6: Success after binutils/gcc/linux/gl [...] new cd53eea05a 149: onsuccess: #565: 6: Success after binutils/gcc/linux/gl [...] new 10be2f70fd 150: onsuccess: #566: 6: Success after binutils/gcc/linux/gl [...] new 8724bd4bbd 151: onsuccess: #567: 6: Success after binutils/gcc/linux/gl [...] new b056970131 152: onsuccess: #568: 6: Success after binutils/gcc/linux/gd [...] new 986cbc92ee 153: onsuccess: #569: 6: Success after binutils/gcc/gdb: 47 commits new 8a98ce1f5f 154: onsuccess: #570: 6: Success after binutils/gcc/linux/gd [...] new 791a540f38 155: onsuccess: #571: 6: Success after binutils/gcc/gdb: 36 commits new a0ff9b1052 156: onsuccess: #572: 6: Success after binutils/gcc/gdb: 18 commits new 7c226bf71f 157: onsuccess: #573: 6: Success after binutils/gcc/gdb: 9 commits new d5497ef469 158: onsuccess: #574: 6: Success after binutils/gcc/linux/gl [...] new a1ab26fcae 159: onsuccess: #575: 6: Success after binutils/gcc/linux/gd [...] new 1781a9c4d4 160: onsuccess: #576: 6: Success after binutils/gcc/linux/gd [...] new 052e73be85 161: onsuccess: #578: 6: Success after binutils: 15 commits new d494d0eb43 162: onsuccess: #579: 6: Success after gcc: 11 commits new cf6e2e8f2a 163: onsuccess: #586: 6: Success after binutils/gcc/linux/gl [...] new 579d92e075 164: onsuccess: #587: 6: Success after binutils/gcc/glibc/gd [...] new 2f6e61488f 165: onsuccess: #588: 6: Success after binutils/gcc/linux/gl [...] new ecb816ef16 166: onsuccess: #589: 6: Success after binutils/gcc/linux/gl [...] new 891cda3dc9 167: onsuccess: #590: 6: Success after binutils/gcc/linux/gl [...] new 1775c1c331 168: onsuccess: #591: 6: Success after binutils/gcc/linux/gd [...] new 3d2b04c43a 169: onsuccess: #593: 6: Success after binutils/gcc/linux/gl [...] new 4504f8bbe7 170: onsuccess: #594: 6: Success after binutils/gcc/linux/gl [...] new a9b3734945 171: onsuccess: #595: 6: Success after binutils/gcc/linux/gl [...] This update added new revisions after undoing existing revisions. That is to say, some revisions that were in the old version of the branch are not in the new version. This situation occurs when a user --force pushes a change and generates a repository containing something like this: * -- * -- B -- O -- O -- O (6e62ab740b) \ 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 1736 -> 1752 bytes 02-prepare_abe/console.log.xz | Bin 2736 -> 2760 bytes 04-build_abe-binutils/console.log.xz | Bin 52572 -> 52208 bytes 05-build_abe-gcc/console.log.xz | Bin 239116 -> 237616 bytes 07-build_abe-linux/console.log.xz | Bin 8728 -> 8728 bytes 08-build_abe-glibc/console.log.xz | Bin 236116 -> 236400 bytes 09-build_abe-gdb/console.log.xz | Bin 50928 -> 50712 bytes 10-check_regression/console.log.xz | Bin 4492 -> 4172 bytes 11-update_baseline/console.log | 36 +++++++++++++++++------------------ dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- git/gdb_rev | 2 +- git/glibc_rev | 2 +- git/linux_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 2 +- mail/mail-subject.txt | 2 +- manifest.sh | 36 +++++++++++++++++------------------ 19 files changed, 45 insertions(+), 45 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 5 months

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_gnu_native_check_gdb/master-arm updated (d2fe5a9747 -> 31b25c3f03)

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 d2fe5a9747 161: onsuccess: #655: 1: Success after binutils/gcc/linux/gl [...] discards 9d3930380b 160: onsuccess: #654: 1: Success after binutils/gcc/linux/gl [...] discards b0e873353c 159: onsuccess: #653: 1: Success after binutils/gcc/linux/gd [...] discards f5fe0dc45e 158: onsuccess: #652: 1: Success after binutils/gcc/linux/gd [...] discards 9255685a12 157: onsuccess: #651: 1: Success after binutils/gcc/linux/gl [...] discards e56d7e5ac2 156: onsuccess: #650: 1: Success after binutils/gcc/linux/gl [...] discards f606903cb2 155: onsuccess: #649: 1: Success after binutils/gcc/linux/gl [...] discards 27481ebde6 154: onsuccess: #648: 1: Success after binutils/gcc/glibc/gd [...] discards 3856496997 153: onsuccess: #647: 1: Success after binutils/gcc/linux/gl [...] discards 02bbcef193 152: onsuccess: #645: 1: Success after binutils/gcc/linux/gl [...] discards 8af0fbda5b 151: onsuccess: #643: 1: Success after binutils/gcc/linux/gd [...] discards ea16b5132a 150: onsuccess: #642: 1: Success after binutils/gcc/linux/gd [...] discards e26c18163d 149: onsuccess: #641: 1: Success after binutils/gcc/linux/gl [...] discards 75051431da 148: onsuccess: #640: 1: Success after binutils/gcc/gdb: 7 commits discards 1a84ed06b9 147: onsuccess: #639: 1: Success after binutils/gcc/gdb: 19 commits discards 69cf7ed163 146: onsuccess: #638: 1: Success after binutils/gcc/gdb: 35 commits discards bac1c5c1ea 145: onsuccess: #637: 1: Success after binutils/gcc/linux/gd [...] discards dfab5fcc0f 144: onsuccess: #636: 1: Success after binutils/gcc/gdb: 47 commits discards cd64bf104b 143: onsuccess: #635: 1: Success after binutils/gcc/linux/gd [...] discards 2c381ace70 142: onsuccess: #634: 1: Success after binutils/gcc/linux/gl [...] discards 4d32d30a2b 141: onsuccess: #633: 1: Success after binutils/gcc/linux/gl [...] discards b2d10062c5 140: onsuccess: #631: 1: Success after binutils/gcc/linux/gl [...] discards 02460a3747 139: onsuccess: #629: 1: Success after binutils/gcc/linux/gl [...] discards efd51058c1 138: onsuccess: #628: 1: Success after binutils/gcc/linux/gl [...] discards f5c0dfc4ba 137: onsuccess: #627: 1: Success after binutils/gcc/gdb: 14 commits discards 718dbf5a95 136: onsuccess: #626: 1: Success after binutils/gcc/linux/gd [...] discards eb60d6e7c6 135: onsuccess: #625: 1: Success after binutils/gcc/linux/gl [...] discards 20948a3cfb 134: onsuccess: #624: 1: Success after binutils/gcc/linux/gl [...] discards 72d1d080be 133: onsuccess: #623: 1: Success after binutils/gcc/linux/gl [...] discards 989b6ffafc 132: onsuccess: #622: 1: Success after binutils/gcc/linux/gd [...] discards bc14ec8a18 131: onsuccess: #621: 1: Success after binutils/gcc/linux/gl [...] discards 589b9386e4 130: onsuccess: #620: 1: Success after binutils/gcc/linux/gd [...] discards 8789aaa44b 129: onsuccess: #619: 1: Success after binutils/gcc/linux/gd [...] discards 8e911ab93b 128: onsuccess: #618: 1: Success after binutils/gcc/linux/gl [...] discards 4a280f4dd6 127: onsuccess: #616: 1: Success after binutils/gcc/linux/gl [...] discards 2d3384c78f 126: onsuccess: #615: 1: Success after binutils/gcc/linux/gl [...] discards 291070d179 125: onsuccess: #614: 1: Success after linux: 12 commits discards d14392c666 124: onsuccess: #612: 1: Success after binutils: 18 commits discards 191b119d12 123: onsuccess: #610: 1: Success after binutils/gcc/linux/gd [...] discards 95c40ac17b 122: onsuccess: #609: 1: Success after binutils/gcc/linux/gl [...] discards 24cfe3fecc 121: onsuccess: #608: 1: Success after binutils/gcc/linux/gl [...] discards dc4030f649 120: onsuccess: #607: 1: Success after binutils/gcc/linux/gd [...] discards 69885dbacb 119: onsuccess: #606: 1: Success after binutils/gcc/linux/gl [...] discards 13e9c049cf 118: onsuccess: #605: 1: Success after binutils/gcc/linux/gl [...] discards 0d831e1225 117: onsuccess: #604: 1: Success after binutils/gcc/linux/gl [...] discards 65c9cd972e 116: onsuccess: #603: 1: Success after binutils/gcc/linux/gd [...] discards 6487b4a433 115: onsuccess: #602: 1: Success after binutils/gcc/linux/gd [...] discards d041ce1aa8 114: onsuccess: #601: 1: Success after binutils/gcc/linux/gd [...] discards ef7f42e6b7 113: onsuccess: #600: 1: Success after binutils/gcc/linux/gd [...] discards 58d377f1ab 112: onsuccess: #599: 1: Success after binutils/gcc/gdb: 68 commits discards 2e395df91d 111: onsuccess: #598: 1: Success after binutils/gcc/gdb: 48 commits discards 3804785317 110: onsuccess: #597: 1: Success after binutils/gcc/linux/gl [...] discards f24e577f8e 109: onsuccess: #596: 1: Success after binutils/gcc/linux/gd [...] discards 14ca662def 108: onsuccess: #595: 1: Success after binutils/gcc/linux/gd [...] discards ede04c3323 107: onsuccess: #594: 1: Success after binutils/gcc/linux/gl [...] discards bb6d8623ef 106: onsuccess: #593: 1: Success after binutils/gcc/linux/gd [...] discards 169a8a6052 105: onsuccess: #592: 1: Success after binutils/gcc/linux/gd [...] discards c40847f2e2 104: onsuccess: #591: 1: Success after binutils/gcc/linux/gl [...] discards 62b3179357 103: onsuccess: #589: 1: Success after binutils: 3 commits discards 1acfeb13e6 102: onsuccess: #586: 1: Success after binutils: 5 commits discards a9b0b74c83 101: onsuccess: #584: 1: Success after binutils/gcc/linux/gd [...] discards 4fc296280e 100: onsuccess: #583: 1: Success after binutils/gcc/linux/gl [...] discards 9889830071 99: onsuccess: #582: 1: Success after binutils/gcc/linux/gli [...] discards 23be897298 98: onsuccess: #581: 1: Success after binutils/gcc/linux/gli [...] discards 5bfda2eb18 97: onsuccess: #580: 1: Success after binutils/gcc/linux/gli [...] discards 5b18119f30 96: onsuccess: #579: 1: Success after binutils/gcc/linux/gdb [...] discards 24f9d035f1 95: onsuccess: #578: 1: Success after binutils/gcc/linux/gli [...] discards 0b93f0ce7d 94: onsuccess: #577: 1: Success after binutils/gcc/linux/gli [...] discards 2a1a0331f7 93: onsuccess: #576: 1: Success after binutils/gcc/linux/gli [...] discards ec2c1328b2 92: onsuccess: #575: 1: Success after linux: 34 commits discards b7408284a1 91: onsuccess: #574: 1: Success after glibc: 3 commits discards b44d94e980 90: onsuccess: #572: 1: Success after binutils: 15 commits discards 26bca6642a 89: onsuccess: #570: 1: Success after linux: 11 commits discards bcc9c410ab 88: onsuccess: #569: 1: Success after glibc: 10 commits discards 386c544154 87: onsuccess: #567: 1: Success after binutils: 8 commits discards bedeff50c0 86: onsuccess: #565: 1: Success after binutils/gcc/linux/gli [...] discards 5f60fdab08 85: onsuccess: #564: 1: Success after binutils/gcc/linux/gdb [...] discards 7d6f46a110 84: onsuccess: #563: 1: Success after binutils/gcc/linux/gli [...] discards 2cb431b40d 83: onsuccess: #562: 1: Success after binutils/gcc/linux/gli [...] discards 828b07641e 82: onsuccess: #561: 1: Success after binutils/gcc/linux/gli [...] discards 00a193a229 81: onsuccess: #560: 1: Success after binutils/gcc/linux/gli [...] discards 46ba2b4653 80: onsuccess: #559: 1: Success after binutils/gcc/linux/gli [...] discards 64c63f537d 79: onsuccess: #558: 1: Success after binutils/gcc/linux/gli [...] discards c2b560e16f 78: onsuccess: #557: 1: Success after binutils/gcc/linux/gdb [...] discards 295727a898 77: onsuccess: #556: 1: Success after binutils/gcc/linux/gdb [...] discards 477e459ad5 76: onsuccess: #555: 1: Success after binutils/gcc/linux/gli [...] discards 114a966517 75: onsuccess: #554: 1: Success after binutils/gcc/glibc/gdb [...] discards acfc690e9b 74: onsuccess: #553: 1: Success after binutils/gcc/linux/gli [...] discards 57866eb1c5 73: onsuccess: #552: 1: Success after binutils/gcc/linux/gli [...] discards 12de286102 72: onsuccess: #551: 1: Success after binutils/gcc/linux/gli [...] discards 475cef5291 71: onsuccess: #550: 1: Success after binutils/gcc/linux/gdb [...] discards 0fb7985b2f 70: onsuccess: #549: 1: Success after binutils/gcc/linux/gli [...] discards d1ec6b21cc 69: onsuccess: #548: 1: Success after binutils/gcc/linux/gli [...] discards f8f7a8080b 68: onsuccess: #547: 1: Success after binutils/gcc/linux/gli [...] discards e174f49c8b 67: onsuccess: #546: 1: Success after binutils/gcc/linux/gli [...] discards d60de99b42 66: onsuccess: #545: 1: Success after binutils/gcc/linux/gli [...] discards 3bbbdc257f 65: onsuccess: #544: 1: Success after binutils/gcc/linux/gli [...] discards cefda1b7fd 64: onsuccess: #543: 1: Success after binutils/gcc/linux/gli [...] discards ef2e1744d6 63: onsuccess: #542: 1: Success after binutils/gcc/linux/gli [...] discards f392f1c119 62: onsuccess: #541: 1: Success after binutils/gcc/linux/gli [...] discards ff845d3d6f 61: onsuccess: #540: 1: Success after binutils/gcc/linux/gli [...] new f8a6a12723 61: onsuccess: #540: 1: Success after binutils/gcc/linux/gli [...] new 640f487fbf 62: onsuccess: #541: 1: Success after binutils/gcc/linux/gli [...] new f08c47bfe0 63: onsuccess: #542: 1: Success after binutils/gcc/linux/gli [...] new 4d4b852616 64: onsuccess: #543: 1: Success after binutils/gcc/linux/gli [...] new 579683e20d 65: onsuccess: #544: 1: Success after binutils/gcc/linux/gli [...] new 48060cca2e 66: onsuccess: #545: 1: Success after binutils/gcc/linux/gli [...] new 8d9fa288c9 67: onsuccess: #546: 1: Success after binutils/gcc/linux/gli [...] new 9e0cd893c0 68: onsuccess: #547: 1: Success after binutils/gcc/linux/gli [...] new 5964f624d2 69: onsuccess: #548: 1: Success after binutils/gcc/linux/gli [...] new 1c7f92f86e 70: onsuccess: #549: 1: Success after binutils/gcc/linux/gli [...] new 0129678ab2 71: onsuccess: #550: 1: Success after binutils/gcc/linux/gdb [...] new 5f0c7febb5 72: onsuccess: #551: 1: Success after binutils/gcc/linux/gli [...] new b1d46f1d18 73: onsuccess: #552: 1: Success after binutils/gcc/linux/gli [...] new 00015ec3dc 74: onsuccess: #553: 1: Success after binutils/gcc/linux/gli [...] new 5940d6d2ee 75: onsuccess: #554: 1: Success after binutils/gcc/glibc/gdb [...] new 6edb96f394 76: onsuccess: #555: 1: Success after binutils/gcc/linux/gli [...] new efeea0c50b 77: onsuccess: #556: 1: Success after binutils/gcc/linux/gdb [...] new 07ca0aebe7 78: onsuccess: #557: 1: Success after binutils/gcc/linux/gdb [...] new 3b3a4c49d6 79: onsuccess: #558: 1: Success after binutils/gcc/linux/gli [...] new 5a0cb92744 80: onsuccess: #559: 1: Success after binutils/gcc/linux/gli [...] new ff6d4c26fc 81: onsuccess: #560: 1: Success after binutils/gcc/linux/gli [...] new d51d872e42 82: onsuccess: #561: 1: Success after binutils/gcc/linux/gli [...] new c764f89aab 83: onsuccess: #562: 1: Success after binutils/gcc/linux/gli [...] new 798683d506 84: onsuccess: #563: 1: Success after binutils/gcc/linux/gli [...] new 02438c6894 85: onsuccess: #564: 1: Success after binutils/gcc/linux/gdb [...] new aea7783475 86: onsuccess: #565: 1: Success after binutils/gcc/linux/gli [...] new 1a02028241 87: onsuccess: #567: 1: Success after binutils: 8 commits new 68fd73c2f4 88: onsuccess: #569: 1: Success after glibc: 10 commits new 3a186b6487 89: onsuccess: #570: 1: Success after linux: 11 commits new 146bec34bb 90: onsuccess: #572: 1: Success after binutils: 15 commits new 417dd9a2f1 91: onsuccess: #574: 1: Success after glibc: 3 commits new 6bbcb21d40 92: onsuccess: #575: 1: Success after linux: 34 commits new 37cf2748c3 93: onsuccess: #576: 1: Success after binutils/gcc/linux/gli [...] new 683bc033ec 94: onsuccess: #577: 1: Success after binutils/gcc/linux/gli [...] new 5d9d65584b 95: onsuccess: #578: 1: Success after binutils/gcc/linux/gli [...] new b234858009 96: onsuccess: #579: 1: Success after binutils/gcc/linux/gdb [...] new 8c8f4421fb 97: onsuccess: #580: 1: Success after binutils/gcc/linux/gli [...] new 979bd89b19 98: onsuccess: #581: 1: Success after binutils/gcc/linux/gli [...] new 32f5e30866 99: onsuccess: #582: 1: Success after binutils/gcc/linux/gli [...] new c30f3dc4e9 100: onsuccess: #583: 1: Success after binutils/gcc/linux/gl [...] new d767f5d84a 101: onsuccess: #584: 1: Success after binutils/gcc/linux/gd [...] new 1b1772e830 102: onsuccess: #586: 1: Success after binutils: 5 commits new 8f92fad1f9 103: onsuccess: #589: 1: Success after binutils: 3 commits new 800f61f009 104: onsuccess: #591: 1: Success after binutils/gcc/linux/gl [...] new add5e748bc 105: onsuccess: #592: 1: Success after binutils/gcc/linux/gd [...] new 1e9c4d3368 106: onsuccess: #593: 1: Success after binutils/gcc/linux/gd [...] new 87274e6ec8 107: onsuccess: #594: 1: Success after binutils/gcc/linux/gl [...] new 3ac86b941f 108: onsuccess: #595: 1: Success after binutils/gcc/linux/gd [...] new f2fc97d453 109: onsuccess: #596: 1: Success after binutils/gcc/linux/gd [...] new 4cb709a2d8 110: onsuccess: #597: 1: Success after binutils/gcc/linux/gl [...] new 9663ee89da 111: onsuccess: #598: 1: Success after binutils/gcc/gdb: 48 commits new 0c746ff5dd 112: onsuccess: #599: 1: Success after binutils/gcc/gdb: 68 commits new 2a013c9ab6 113: onsuccess: #600: 1: Success after binutils/gcc/linux/gd [...] new e1c7b10110 114: onsuccess: #601: 1: Success after binutils/gcc/linux/gd [...] new f2dfabfc59 115: onsuccess: #602: 1: Success after binutils/gcc/linux/gd [...] new 70dc1c605c 116: onsuccess: #603: 1: Success after binutils/gcc/linux/gd [...] new 167e8e73a2 117: onsuccess: #604: 1: Success after binutils/gcc/linux/gl [...] new b2e28e4b20 118: onsuccess: #605: 1: Success after binutils/gcc/linux/gl [...] new 746545d6a8 119: onsuccess: #606: 1: Success after binutils/gcc/linux/gl [...] new 2f7aa94468 120: onsuccess: #607: 1: Success after binutils/gcc/linux/gd [...] new ae578a3967 121: onsuccess: #608: 1: Success after binutils/gcc/linux/gl [...] new 5e3555aca8 122: onsuccess: #609: 1: Success after binutils/gcc/linux/gl [...] new 737a069f39 123: onsuccess: #610: 1: Success after binutils/gcc/linux/gd [...] new e6ed06b36e 124: onsuccess: #612: 1: Success after binutils: 18 commits new 1f2faccf49 125: onsuccess: #614: 1: Success after linux: 12 commits new 0ee8c5bb06 126: onsuccess: #615: 1: Success after binutils/gcc/linux/gl [...] new 49e5bc3b2d 127: onsuccess: #616: 1: Success after binutils/gcc/linux/gl [...] new 19f1d6df76 128: onsuccess: #618: 1: Success after binutils/gcc/linux/gl [...] new 9276e996fa 129: onsuccess: #619: 1: Success after binutils/gcc/linux/gd [...] new 4a4b83487d 130: onsuccess: #620: 1: Success after binutils/gcc/linux/gd [...] new 3828d5dba6 131: onsuccess: #621: 1: Success after binutils/gcc/linux/gl [...] new 73579e9f12 132: onsuccess: #622: 1: Success after binutils/gcc/linux/gd [...] new 75f8a11770 133: onsuccess: #623: 1: Success after binutils/gcc/linux/gl [...] new b9af26e84a 134: onsuccess: #624: 1: Success after binutils/gcc/linux/gl [...] new 0b61c8a80f 135: onsuccess: #625: 1: Success after binutils/gcc/linux/gl [...] new 6119e24a47 136: onsuccess: #626: 1: Success after binutils/gcc/linux/gd [...] new db165698d9 137: onsuccess: #627: 1: Success after binutils/gcc/gdb: 14 commits new 7fa6362015 138: onsuccess: #628: 1: Success after binutils/gcc/linux/gl [...] new 4cf2ad9ce6 139: onsuccess: #629: 1: Success after binutils/gcc/linux/gl [...] new 119dfbbc12 140: onsuccess: #631: 1: Success after binutils/gcc/linux/gl [...] new e84b0fbaea 141: onsuccess: #633: 1: Success after binutils/gcc/linux/gl [...] new d3509e72d1 142: onsuccess: #634: 1: Success after binutils/gcc/linux/gl [...] new 293d225b5d 143: onsuccess: #635: 1: Success after binutils/gcc/linux/gd [...] new 8c197348c0 144: onsuccess: #636: 1: Success after binutils/gcc/gdb: 47 commits new a7466b6ab3 145: onsuccess: #637: 1: Success after binutils/gcc/linux/gd [...] new 2fba5f8bbc 146: onsuccess: #638: 1: Success after binutils/gcc/gdb: 35 commits new f72061f577 147: onsuccess: #639: 1: Success after binutils/gcc/gdb: 19 commits new 9c81302517 148: onsuccess: #640: 1: Success after binutils/gcc/gdb: 7 commits new 28bf9ac651 149: onsuccess: #641: 1: Success after binutils/gcc/linux/gl [...] new f29aa8a752 150: onsuccess: #642: 1: Success after binutils/gcc/linux/gd [...] new a526ad9d2a 151: onsuccess: #643: 1: Success after binutils/gcc/linux/gd [...] new ea078ffa13 152: onsuccess: #645: 1: Success after binutils/gcc/linux/gl [...] new b9d5639da3 153: onsuccess: #647: 1: Success after binutils/gcc/linux/gl [...] new 97a8aedebd 154: onsuccess: #648: 1: Success after binutils/gcc/glibc/gd [...] new e9e81727dc 155: onsuccess: #649: 1: Success after binutils/gcc/linux/gl [...] new bb5c5e9afb 156: onsuccess: #650: 1: Success after binutils/gcc/linux/gl [...] new 9344e6e0e7 157: onsuccess: #651: 1: Success after binutils/gcc/linux/gl [...] new 7947fd3e4a 158: onsuccess: #652: 1: Success after binutils/gcc/linux/gd [...] new 444a4176f0 159: onsuccess: #653: 1: Success after binutils/gcc/linux/gd [...] new 106bf38996 160: onsuccess: #654: 1: Success after binutils/gcc/linux/gl [...] new a028663677 161: onsuccess: #655: 1: Success after binutils/gcc/linux/gl [...] new 31b25c3f03 162: onsuccess: #656: 1: Success after binutils/gcc/linux/gl [...] This update added new revisions after undoing existing revisions. That is to say, some revisions that were in the old version of the branch are not in the new version. This situation occurs when a user --force pushes a change and generates a repository containing something like this: * -- * -- B -- O -- O -- O (d2fe5a9747) \ 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 1752 -> 1752 bytes 02-prepare_abe/console.log.xz | Bin 2736 -> 2756 bytes 03-build_abe-binutils/console.log.xz | Bin 53824 -> 52248 bytes 04-build_abe-gcc/console.log.xz | Bin 237612 -> 237408 bytes 06-build_abe-linux/console.log.xz | Bin 8736 -> 8740 bytes 07-build_abe-glibc/console.log.xz | Bin 236356 -> 236732 bytes 08-build_abe-gdb/console.log.xz | Bin 51708 -> 51716 bytes 09-build_abe-dejagnu/console.log.xz | Bin 3820 -> 3816 bytes 10-build_abe-check_gdb/console.log.xz | Bin 2348 -> 2028 bytes 11-check_regression/console.log.xz | Bin 8120 -> 18668 bytes 11-check_regression/extra-bisect-params | 2 +- 11-check_regression/fails.sum | 52 +- 11-check_regression/mail-body.txt | 158 +- 11-check_regression/results.compare | 83 +- 11-check_regression/results.compare2 | 4598 ++++++++++++++++++++++++++++++- 11-check_regression/results.regressions | 83 +- 12-update_baseline/console.log | 32 +- dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- git/gdb_rev | 2 +- git/glibc_rev | 2 +- git/linux_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 160 +- mail/mail-subject.txt | 2 +- manifest.sh | 36 +- results | 83 +- sumfiles/gdb.log.xz | Bin 1818484 -> 1796532 bytes sumfiles/gdb.sum | 4181 ++-------------------------- 30 files changed, 5153 insertions(+), 4331 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 5 months

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

Tcwg-commits January 2023