Tcwg-commits October 2022

tcwg-commits@lists.linaro.org

6 participants
4723 discussions

[gcc] branch master updated (e9d50e7a4e2 -> 5fc4d3e1837)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. unknown user pushed a change to branch master in repository gcc. from e9d50e7a4e2 Setting explicit NANs sets UNDEFINED for -ffinite-math-only. new 5fc4d3e1837 cselib: Skip BImode while keeping track of subvalue relatio [...] The 1 revisions listed above as "new" are entirely new to this repository and will be described in separate emails. The revisions listed as "adds" were already present in the repository and have only been added to this reference. Summary of changes: gcc/cselib.cc | 1 + 1 file changed, 1 insertion(+) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 1 month

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_kernel/llvm-release-aarch64-next-allyesconfig updated (1a2b2870a5 -> b40458f298)

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-next-allyesconfig in repository toolchain/ci/base-artifacts. from 1a2b2870a5 23: force: #422: 21253: Failure after v6.0-rc7-4-ga3a956c78e [...] new b40458f298 24: onsuccess: #423: 21398: Success after linux: 12828 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 1708 -> 1676 bytes 02-prepare_abe/console.log.xz | Bin 2752 -> 2732 bytes 03-build_abe-binutils/console.log.xz | Bin 30408 -> 30212 bytes 04-build_kernel_llvm/console.log.xz | Bin 63768 -> 63848 bytes 05-build_abe-qemu/console.log.xz | Bin 32152 -> 31720 bytes 06-build_linux/console.log.xz | Bin 3560 -> 3508 bytes 08-check_regression/console.log.xz | Bin 3732 -> 2944 bytes 08-check_regression/jira-body.txt | 2 +- 08-check_regression/mail-body.txt | 20 +- 08-check_regression/mail-subject.txt | 2 +- 08-check_regression/results.regressions | 6 - 08-check_regression/trigger-bisect | 2 - 08-check_regression/trigger-notify | 0 09-update_baseline/console.log | 2 +- dashboard/dashboard-generate.sh | 2 +- git/linux_rev | 2 +- jenkins/jira-status.draft | 4 - jenkins/mail-body.draft | 341 -------------------------------- jenkins/mail-recipients.draft | 1 - jenkins/mail-subject.draft | 1 - jenkins/notify.sh | 3 - mail/jira-body.txt | 2 +- mail/mail-body.txt | 20 +- mail/mail-subject.txt | 2 +- manifest.sh | 16 +- results | 8 +- 26 files changed, 34 insertions(+), 402 deletions(-) delete mode 100644 08-check_regression/results.regressions delete mode 100644 08-check_regression/trigger-bisect delete mode 100644 08-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, 1 month

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_bmk_gnu_eabi_stm32/gnu_eabi-master-arm_eabi-coremark-Os updated (921f4aa8d0 -> bf0056ce53)

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_gnu_eabi_stm32/gnu_eabi-master-arm_eabi-coremark-Os in repository toolchain/ci/base-artifacts. from 921f4aa8d0 15: onsuccess: #319: 1: [TCWG CI] No change after binutils: [...] new bf0056ce53 16: onsuccess: #322: 1: [TCWG CI] No change after binutils/g [...] The 1 revisions listed above as "new" are entirely new to this repository and will be described in separate emails. The revisions listed as "adds" were already present in the repository and have only been added to this reference. Summary of changes: 01-reset_artifacts/console.log.xz | Bin 1724 -> 1704 bytes 02-prepare_abe/console.log.xz | Bin 2736 -> 2752 bytes 03-build_abe-binutils/console.log.xz | Bin 30412 -> 30616 bytes 04-build_abe-stage1/console.log.xz | Bin 89036 -> 90192 bytes 06-build_abe-newlib/console.log.xz | Bin 16644 -> 16972 bytes 07-build_abe-stage2/console.log.xz | Bin 160752 -> 161400 bytes 08-benchmark/benchmark-build.log | 96 ++++++++++++------------- 08-benchmark/benchmark.log | 94 ++++++++++++------------ 08-benchmark/console.log.xz | Bin 3764 -> 3748 bytes 09-check_regression/console.log.xz | Bin 3848 -> 4584 bytes 09-check_regression/csv-results-0/results.csv | 6 +- 09-check_regression/csv-results-1/results.csv | 6 +- 09-check_regression/results-brief.csv | 6 +- 09-check_regression/results-full.csv | 6 +- 09-check_regression/results-internal.csv | 6 +- 09-check_regression/results.csv | 6 +- 09-check_regression/results.log | 8 +-- dashboard/dashboard-generate.sh | 2 +- dashboard/squad/Mean/results-functional.json | 4 -- dashboard/squad/Mean/results-metadata.json | 10 --- dashboard/squad/Mean/results-metrics.json | 3 - dashboard/squad/coremark/results-metadata.json | 12 ++-- dashboard/squad/dashboard-push-squad.sh | 13 +--- git/binutils_rev | 2 +- git/gcc_rev | 2 +- git/newlib_rev | 2 +- mail/jira-body.txt | 24 +++++-- mail/mail-body.txt | 24 +++++-- mail/mail-subject.txt | 2 +- manifest.sh | 30 ++++---- results_id | 2 +- 31 files changed, 184 insertions(+), 182 deletions(-) delete mode 100644 dashboard/squad/Mean/results-functional.json delete mode 100644 dashboard/squad/Mean/results-metadata.json delete mode 100644 dashboard/squad/Mean/results-metrics.json -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 1 month

[gcc] branch master updated (966010b2eb4 -> e9d50e7a4e2)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. unknown user pushed a change to branch master in repository gcc. from 966010b2eb4 Daily bump. new ab4909fd8f5 Do not double print INF and NAN in frange pretty printer. new 9eab8e45dd1 Do not check finite_operands_p twice in range-ops-float. new e9d50e7a4e2 Setting explicit NANs sets UNDEFINED for -ffinite-math-only. The 3 revisions listed above as "new" are entirely new to this repository and will be described in separate emails. The revisions listed as "adds" were already present in the repository and have only been added to this reference. Summary of changes: gcc/range-op-float.cc | 12 +++------ gcc/value-range-pretty-print.cc | 6 ++++- gcc/value-range.cc | 59 ++++++++++++++++++++-------------------- gcc/value-range.h | 60 ++++++++++++++++++++++++++--------------- 4 files changed, 76 insertions(+), 61 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 1 month

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_gcc_bootstrap/master-arm-bootstrap_O1 updated (603e86459f -> 8e7057de77)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. tcwg-buildslave pushed a change to branch linaro-local/ci/tcwg_gcc_bootstrap/master-arm-bootstrap_O1 in repository toolchain/ci/base-artifacts. from 603e86459f 55: onsuccess: #447: 2: Success after binutils/gcc: 49 commits new 8e7057de77 56: onsuccess: #448: 2: Success after binutils/gcc: 33 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 -> 1688 bytes 02-prepare_abe/console.log.xz | Bin 2740 -> 2724 bytes 04-build_abe-binutils/console.log.xz | Bin 51968 -> 51708 bytes 05-build_abe-bootstrap_O1/console.log.xz | Bin 471624 -> 470032 bytes 06-check_regression/console.log.xz | Bin 3112 -> 3068 bytes 07-update_baseline/console.log | 2 +- 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 | 18 +++++++++--------- 13 files changed, 16 insertions(+), 16 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 1 month

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_gcc_bootstrap/master-aarch64-bootstrap_profiled updated (90749f1c2b -> d2e6984b14)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. tcwg-buildslave pushed a change to branch linaro-local/ci/tcwg_gcc_bootstrap/master-aarch64-bootstrap_profiled in repository toolchain/ci/base-artifacts. from 90749f1c2b 53: onsuccess: #449: 2: Success after binutils/gcc: 39 commits new d2e6984b14 54: onsuccess: #450: 2: Success after binutils/gcc: 32 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 1712 -> 1672 bytes 02-prepare_abe/console.log.xz | Bin 2736 -> 2736 bytes 04-build_abe-binutils/console.log.xz | Bin 38228 -> 38624 bytes 05-build_abe-bootstrap_profiled/console.log.xz | Bin 513324 -> 515276 bytes 06-check_regression/console.log.xz | Bin 3180 -> 3196 bytes 07-update_baseline/console.log | 9 --------- 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 | 18 +++++++++--------- 13 files changed, 15 insertions(+), 24 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 1 month

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_gnu_cross_check_gcc/master-aarch64 updated (071f9fe81c -> e18d6daa24)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. tcwg-buildslave pushed a change to branch linaro-local/ci/tcwg_gnu_cross_check_gcc/master-aarch64 in repository toolchain/ci/base-artifacts. discards 071f9fe81c 167: onsuccess: #2202: 1: Success after gcc/linux/glibc/qemu [...] discards 2aecdab5d0 166: onsuccess: #2201: 1: Success after gcc/glibc/qemu: 40 commits discards 62c1c20679 165: onsuccess: #2200: 1: Success after binutils/gdb: 8 commits discards 0d5deabaf6 164: onsuccess: #2199: 1: Success after binutils/gcc/linux/g [...] discards b2d581b648 163: onsuccess: #2198: 1: Success after binutils/gcc/linux/g [...] discards b64ca4a460 162: onsuccess: #2197: 1: Success after binutils/gcc/glibc/g [...] discards 48affeb78e 161: onsuccess: #2196: 1: Success after binutils/gcc/linux/g [...] discards 58080615ee 160: onsuccess: #2195: 1: Success after binutils/gcc/linux/g [...] discards 6bb117065b 159: onsuccess: #2194: 1: Success after gcc/linux/glibc: 197 [...] discards 0b7b6173e9 158: onsuccess: #2193: 1: Success after binutils/gcc/glibc/g [...] discards 6fa36010b1 157: onsuccess: #2192: 1: Success after binutils/gcc/gdb: 8 commits discards 13fbe50d93 156: onsuccess: #2191: 1: Success after binutils/gcc/linux/g [...] discards 3763506211 155: onsuccess: #2190: 1: Success after binutils/gcc/linux/g [...] discards 60af5076d1 154: onsuccess: #2189: 1: Success after binutils/gcc/gdb: 18 [...] discards 0321d1f524 153: onsuccess: #2188: 1: Success after binutils/gcc/gdb: 3 commits discards 19b0772c0e 152: onsuccess: #2187: 1: Success after gcc/linux/glibc: 22 commits discards a200b51305 151: onsuccess: #2186: 1: Success after gcc: 2 commits discards 2e2fac2d3f 150: onsuccess: #2185: 1: Success after gcc: 3 commits discards 344dc2f1ba 149: onsuccess: #2184: 1: Success after binutils/gcc/linux/g [...] discards a2b5be8550 148: onsuccess: #2183: 1: Success after gcc/linux/glibc: 64 commits discards 2535232b84 147: onsuccess: #2182: 1: Success after binutils/gcc/gdb: 18 [...] discards 1e425354e5 146: onsuccess: #2181: 1: Success after binutils/glibc/gdb: [...] discards 3b7c16890a 145: onsuccess: #2180: 1: Success after binutils/gcc/linux/g [...] discards 143378cd8e 144: onsuccess: #2179: 1: Success after binutils/gcc/linux/g [...] discards c032eb24a7 143: onsuccess: #2178: 1: Success after binutils/gcc/gdb/qem [...] discards 09c558d64d 142: onsuccess: #2177: 1: Success after gcc/glibc: 4 commits discards 454c317925 141: onsuccess: #2176: 1: Success after binutils/gcc/gdb: 6 commits discards 70ff120b3d 140: onsuccess: #2175: 1: Success after binutils/gcc/linux/g [...] discards 9dffde6211 139: onsuccess: #2174: 1: Success after binutils/gcc/gdb: 13 [...] discards d1829fcfc2 138: onsuccess: #2173: 1: Success after binutils/gcc/gdb: 5 commits discards 89663073eb 137: onsuccess: #2172: 1: Success after binutils/gcc/linux/g [...] discards 094eefa034 136: onsuccess: #2171: 1: Success after binutils/gcc/gdb/qem [...] discards 60db054673 135: onsuccess: #2170: 1: Success after gcc/linux/qemu: 63 commits discards 9c200b6df8 134: onsuccess: #2169: 1: Success after binutils/gcc/gdb: 13 [...] discards 1a404845bf 133: onsuccess: #2168: 1: Success after binutils/gcc/linux/g [...] discards 62a33d02a1 132: onsuccess: #2167: 1: Success after binutils/gcc/glibc/g [...] discards ca56548d27 131: onsuccess: #2166: 1: Success after binutils/gcc/gdb: 12 [...] discards f906d2a6d0 130: onsuccess: #2165: 1: Success after binutils/gcc/gdb: 32 [...] discards 9d1e986f3f 129: onsuccess: #2164: 1: Success after binutils/gcc/linux/g [...] discards dc6e260328 128: onsuccess: #2163: 1: Success after linux: 23 commits discards 93883717a1 127: onsuccess: #2162: 1: Success after gcc: 9 commits discards 8967f46214 126: onsuccess: #2161: 1: Success after basepoints/gcc-13-28 [...] discards 4990eca4c7 125: onsuccess: #2160: 1: Success after binutils/gcc/linux/g [...] discards 64ffaf4331 124: onsuccess: #2159: 1: Success after linux: 23 commits discards 0d8a8dd038 123: onsuccess: #2158: 1: Success after basepoints/gcc-13-28 [...] discards 7b209f6ef0 122: onsuccess: #2157: 1: Success after binutils/gcc/gdb: 6 commits discards 85579b6d98 121: onsuccess: #2156: 1: Success after binutils/gcc/linux/g [...] discards 874646175d 120: onsuccess: #2155: 1: Success after binutils/gcc/linux/g [...] discards 9a8e82ac75 119: onsuccess: #2154: 1: Success after binutils/gcc/linux/g [...] discards f469bf2fa7 118: onsuccess: #2151: 1: Success after binutils/gcc/linux/g [...] discards 0b54db629b 117: onsuccess: #2150: 1: Success after binutils/gcc/glibc/g [...] discards dbea7713ad 116: onsuccess: #2148: 1: Success after binutils/gcc/gdb: 7 commits discards 39656a5eb4 115: onsuccess: #2147: 1: Success after binutils/linux/glibc [...] discards 8b02383e8b 114: onsuccess: #2146: 1: Success after binutils/gcc/glibc/g [...] discards e5a897a0e3 113: onsuccess: #2145: 1: Success after binutils/gcc/glibc/g [...] discards db9ce9fac7 112: onsuccess: #2144: 1: Success after binutils/gcc/glibc/g [...] discards 5bb2785cdd 111: onsuccess: #2143: 1: Success after binutils/gcc/linux/g [...] discards 8d6dff6b8b 110: onsuccess: #2142: 1: Success after binutils/gcc/glibc/g [...] discards c4bf6412e7 109: onsuccess: #2141: 1: Success after gcc/glibc: 6 commits discards 21fae951cd 108: onsuccess: #2140: 1: Success after binutils/gcc/gdb: 5 commits discards 48483804fc 107: onsuccess: #2139: 1: Success after binutils/gcc/gdb: 3 commits discards 8deb52e74d 106: onsuccess: #2138: 1: Success after binutils/gcc/glibc/g [...] discards 305a6914d7 105: onsuccess: #2137: 1: Success after basepoints/gcc-13-27 [...] discards eadf00b3a1 104: onsuccess: #2136: 1: Success after binutils/gcc/gdb: 3 commits discards ede47a6e8d 103: onsuccess: #2135: 1: Success after gcc/linux/glibc/gdb/ [...] discards 6bb1f093cb 102: onsuccess: #2133: 1: Success after gdb-12-branchpoint-1 [...] discards 62d4ed0d59 101: onsuccess: #2130: 1: Success after binutils: 81 commits discards 7a9f925cca 100: onsuccess: #2077: 1: Success after binutils/gcc/linux/g [...] discards 3aae0c1005 99: onsuccess: #2074: 1: Success after baseline build: no ne [...] discards 5f653f45a1 98: onsuccess: #2073: 1: Success after gcc/linux: 11 commits discards 2ae54d8ff6 97: onsuccess: #2072: 1: Success after binutils/gcc/gdb: 3 commits discards 1295fb9196 96: onsuccess: #2071: 1: Success after gcc/linux: 56 commits discards fa5eef648d 95: onsuccess: #2070: 1: Success after basepoints/gcc-13-238 [...] discards 15c02147ce 94: onsuccess: 1: Success after gcc: openmp: Partial OpenMP [...] discards 3db96e734e 93: onsuccess: 1: Success after binutils/gcc/linux/gdb: 88 commits discards bb54266af7 92: onsuccess: 1: Success after binutils/gcc/linux/gdb/qemu: [...] discards 23f695fde9 91: onsuccess: 1: Success after binutils/gcc/gdb: 8 commits discards a72287906d 90: onsuccess: 1: Success after binutils/gcc/gdb: 19 commits discards 16802c5b4d 89: onsuccess: 1: Success after binutils/gcc/gdb: 5 commits discards 5ad24e3b3e 88: onsuccess: 1: Success after gcc/linux/qemu: 149 commits discards 3b03645566 87: onsuccess: 1: Success after binutils/gcc/gdb: 14 commits discards 7fec6691ae 86: onsuccess: 1: Success after binutils/gcc/gdb: 7 commits discards 41f8984d0c 85: onsuccess: 1: Success after binutils/gcc/glibc/gdb/qemu: [...] discards b51b6fca60 84: onsuccess: 1: Success after binutils/gcc/linux/gdb: 68 commits discards 8b2ff1eccc 83: onsuccess: 1: Success after binutils/gcc/glibc/gdb: 17 commits discards c1c6bc72c9 82: onsuccess: 1: Successful build after binutils/gcc/gdb: 1 [...] discards b3a72dcbef 81: onsuccess: 1: Successful build after binutils/gcc/gdb: 6 [...] discards 752facc15b 80: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] discards cc0406817a 79: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] discards 4066ec7914 78: onsuccess: 1: Successful build after binutils/gcc/gdb: 4 [...] discards 29aa62165d 77: onsuccess: 1: Successful build after gcc/linux/glibc: 22 [...] discards 9a4ad1ab5e 76: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 8813be423c 75: onsuccess: 1: Successful build after linux: 44 commits discards 03db72c66c 74: onsuccess: 1: Successful build after binutils/gdb: 2 commits discards 00ef89321d 73: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 9e0e9cd1cb 72: onsuccess: 1: Successful build after linux: 12 commits discards 19d80c21c3 71: onsuccess: 1: Successful build after gcc/glibc: 3 commits discards cd14098c1b 70: onsuccess: 1: Successful build after binutils/gcc/gdb: 4 [...] discards dcdfd99573 69: onsuccess: 1: Successful build after binutils/gcc/gdb: 5 [...] discards 303e370a82 68: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 33984b6383 67: onsuccess: 1: Successful build after binutils/gcc/gdb: 1 [...] new f0a5f24a44 67: onsuccess: 1: Successful build after binutils/gcc/gdb: 1 [...] new 8fefcf48b0 68: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 5c11a675b2 69: onsuccess: 1: Successful build after binutils/gcc/gdb: 5 [...] new c69d6497e3 70: onsuccess: 1: Successful build after binutils/gcc/gdb: 4 [...] new 242af325d3 71: onsuccess: 1: Successful build after gcc/glibc: 3 commits new 8d4ebcfcbf 72: onsuccess: 1: Successful build after linux: 12 commits new 830496133e 73: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 458b65aa96 74: onsuccess: 1: Successful build after binutils/gdb: 2 commits new 39a7e3bee3 75: onsuccess: 1: Successful build after linux: 44 commits new 91ea91fd94 76: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 01873480a6 77: onsuccess: 1: Successful build after gcc/linux/glibc: 22 [...] new 503febccbd 78: onsuccess: 1: Successful build after binutils/gcc/gdb: 4 [...] new 484ba5ae18 79: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] new ac0152c59d 80: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] new ed3f60a930 81: onsuccess: 1: Successful build after binutils/gcc/gdb: 6 [...] new 848c3a470c 82: onsuccess: 1: Successful build after binutils/gcc/gdb: 1 [...] new dc7e0d8a98 83: onsuccess: 1: Success after binutils/gcc/glibc/gdb: 17 commits new 1027e8d691 84: onsuccess: 1: Success after binutils/gcc/linux/gdb: 68 commits new e1385db204 85: onsuccess: 1: Success after binutils/gcc/glibc/gdb/qemu: [...] new 4fc3690a9b 86: onsuccess: 1: Success after binutils/gcc/gdb: 7 commits new 60e760c285 87: onsuccess: 1: Success after binutils/gcc/gdb: 14 commits new 8cc7353f56 88: onsuccess: 1: Success after gcc/linux/qemu: 149 commits new 06b0404741 89: onsuccess: 1: Success after binutils/gcc/gdb: 5 commits new 4198919a83 90: onsuccess: 1: Success after binutils/gcc/gdb: 19 commits new 798df13a5a 91: onsuccess: 1: Success after binutils/gcc/gdb: 8 commits new 88e6a82edd 92: onsuccess: 1: Success after binutils/gcc/linux/gdb/qemu: [...] new 0dd27c0cf8 93: onsuccess: 1: Success after binutils/gcc/linux/gdb: 88 commits new 7a296ca038 94: onsuccess: 1: Success after gcc: openmp: Partial OpenMP [...] new d91b4de0cc 95: onsuccess: #2070: 1: Success after basepoints/gcc-13-238 [...] new a455d7d603 96: onsuccess: #2071: 1: Success after gcc/linux: 56 commits new 17930ed0b7 97: onsuccess: #2072: 1: Success after binutils/gcc/gdb: 3 commits new 3379109346 98: onsuccess: #2073: 1: Success after gcc/linux: 11 commits new ecba86c5c8 99: onsuccess: #2074: 1: Success after baseline build: no ne [...] new 20dd0aeaea 100: onsuccess: #2077: 1: Success after binutils/gcc/linux/g [...] new 790dffe978 101: onsuccess: #2130: 1: Success after binutils: 81 commits new 5430c691f6 102: onsuccess: #2133: 1: Success after gdb-12-branchpoint-1 [...] new fad593599b 103: onsuccess: #2135: 1: Success after gcc/linux/glibc/gdb/ [...] new b2497a9718 104: onsuccess: #2136: 1: Success after binutils/gcc/gdb: 3 commits new 51f3228056 105: onsuccess: #2137: 1: Success after basepoints/gcc-13-27 [...] new f0873b63c0 106: onsuccess: #2138: 1: Success after binutils/gcc/glibc/g [...] new 0ae0b09ded 107: onsuccess: #2139: 1: Success after binutils/gcc/gdb: 3 commits new dbb042f0fe 108: onsuccess: #2140: 1: Success after binutils/gcc/gdb: 5 commits new 7478b50a97 109: onsuccess: #2141: 1: Success after gcc/glibc: 6 commits new 2a1e600fa3 110: onsuccess: #2142: 1: Success after binutils/gcc/glibc/g [...] new 21a3ba8ceb 111: onsuccess: #2143: 1: Success after binutils/gcc/linux/g [...] new 3925fed944 112: onsuccess: #2144: 1: Success after binutils/gcc/glibc/g [...] new 5c85382a78 113: onsuccess: #2145: 1: Success after binutils/gcc/glibc/g [...] new 3d15d1822f 114: onsuccess: #2146: 1: Success after binutils/gcc/glibc/g [...] new c0fa9f1f50 115: onsuccess: #2147: 1: Success after binutils/linux/glibc [...] new 3e5bf61a7b 116: onsuccess: #2148: 1: Success after binutils/gcc/gdb: 7 commits new 34a0f2a046 117: onsuccess: #2150: 1: Success after binutils/gcc/glibc/g [...] new b3ffa4d7df 118: onsuccess: #2151: 1: Success after binutils/gcc/linux/g [...] new 329cb6c5f3 119: onsuccess: #2154: 1: Success after binutils/gcc/linux/g [...] new 728be28c77 120: onsuccess: #2155: 1: Success after binutils/gcc/linux/g [...] new 50925b503f 121: onsuccess: #2156: 1: Success after binutils/gcc/linux/g [...] new df2b71fac2 122: onsuccess: #2157: 1: Success after binutils/gcc/gdb: 6 commits new 0435bca341 123: onsuccess: #2158: 1: Success after basepoints/gcc-13-28 [...] new 6769d555f0 124: onsuccess: #2159: 1: Success after linux: 23 commits new 6877f7a418 125: onsuccess: #2160: 1: Success after binutils/gcc/linux/g [...] new fc2699cfa2 126: onsuccess: #2161: 1: Success after basepoints/gcc-13-28 [...] new 0dd86766a7 127: onsuccess: #2162: 1: Success after gcc: 9 commits new 7fb40cc54c 128: onsuccess: #2163: 1: Success after linux: 23 commits new 809b3241c6 129: onsuccess: #2164: 1: Success after binutils/gcc/linux/g [...] new 2ea701dd33 130: onsuccess: #2165: 1: Success after binutils/gcc/gdb: 32 [...] new 875c9ef0d2 131: onsuccess: #2166: 1: Success after binutils/gcc/gdb: 12 [...] new 8514d48403 132: onsuccess: #2167: 1: Success after binutils/gcc/glibc/g [...] new 5680f760e8 133: onsuccess: #2168: 1: Success after binutils/gcc/linux/g [...] new e79832f07f 134: onsuccess: #2169: 1: Success after binutils/gcc/gdb: 13 [...] new a9c378a4aa 135: onsuccess: #2170: 1: Success after gcc/linux/qemu: 63 commits new 3419c2bbf7 136: onsuccess: #2171: 1: Success after binutils/gcc/gdb/qem [...] new c95358486e 137: onsuccess: #2172: 1: Success after binutils/gcc/linux/g [...] new 5e45b6d5f9 138: onsuccess: #2173: 1: Success after binutils/gcc/gdb: 5 commits new 2a7f3babad 139: onsuccess: #2174: 1: Success after binutils/gcc/gdb: 13 [...] new 851981a1fc 140: onsuccess: #2175: 1: Success after binutils/gcc/linux/g [...] new b7ed1a9a2f 141: onsuccess: #2176: 1: Success after binutils/gcc/gdb: 6 commits new 3605df8610 142: onsuccess: #2177: 1: Success after gcc/glibc: 4 commits new 5088c378cb 143: onsuccess: #2178: 1: Success after binutils/gcc/gdb/qem [...] new 5f8b71c40a 144: onsuccess: #2179: 1: Success after binutils/gcc/linux/g [...] new 163fffdc8e 145: onsuccess: #2180: 1: Success after binutils/gcc/linux/g [...] new ea4f9d04d6 146: onsuccess: #2181: 1: Success after binutils/glibc/gdb: [...] new e6448de526 147: onsuccess: #2182: 1: Success after binutils/gcc/gdb: 18 [...] new 6bd3f33ae2 148: onsuccess: #2183: 1: Success after gcc/linux/glibc: 64 commits new 77b8765cee 149: onsuccess: #2184: 1: Success after binutils/gcc/linux/g [...] new d9070cfc69 150: onsuccess: #2185: 1: Success after gcc: 3 commits new 3f332cd4c5 151: onsuccess: #2186: 1: Success after gcc: 2 commits new 1edf1366c0 152: onsuccess: #2187: 1: Success after gcc/linux/glibc: 22 commits new ac91615e37 153: onsuccess: #2188: 1: Success after binutils/gcc/gdb: 3 commits new b7f7f4a43d 154: onsuccess: #2189: 1: Success after binutils/gcc/gdb: 18 [...] new 4d9f7af32d 155: onsuccess: #2190: 1: Success after binutils/gcc/linux/g [...] new db3c83745b 156: onsuccess: #2191: 1: Success after binutils/gcc/linux/g [...] new 4b6ea9ac2a 157: onsuccess: #2192: 1: Success after binutils/gcc/gdb: 8 commits new 83c7b85621 158: onsuccess: #2193: 1: Success after binutils/gcc/glibc/g [...] new 99bef2312a 159: onsuccess: #2194: 1: Success after gcc/linux/glibc: 197 [...] new b6153acd4f 160: onsuccess: #2195: 1: Success after binutils/gcc/linux/g [...] new c2765a2fb5 161: onsuccess: #2196: 1: Success after binutils/gcc/linux/g [...] new 1e993eed7b 162: onsuccess: #2197: 1: Success after binutils/gcc/glibc/g [...] new 777eaffdd2 163: onsuccess: #2198: 1: Success after binutils/gcc/linux/g [...] new 5006cb03e1 164: onsuccess: #2199: 1: Success after binutils/gcc/linux/g [...] new 69a39416ea 165: onsuccess: #2200: 1: Success after binutils/gdb: 8 commits new 7ac3f867b8 166: onsuccess: #2201: 1: Success after gcc/glibc/qemu: 40 commits new 853e7c7717 167: onsuccess: #2202: 1: Success after gcc/linux/glibc/qemu [...] new e18d6daa24 168: onsuccess: #2203: 1: Success after binutils/gcc/glibc/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 (071f9fe81c) \ N -- N -- N refs/heads/linaro-local/ci/tcwg_gnu_cross_check_gcc/mast [...] 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 1700 -> 1708 bytes 02-prepare_abe/console.log.xz | Bin 2748 -> 2728 bytes 03-build_abe-binutils/console.log.xz | Bin 30540 -> 30136 bytes 04-build_abe-stage1/console.log.xz | Bin 72488 -> 72176 bytes 05-clean_sysroot/console.log.xz | Bin 328 -> 328 bytes 06-build_abe-linux/console.log.xz | Bin 9536 -> 9468 bytes 07-build_abe-glibc/console.log.xz | Bin 239692 -> 240004 bytes 08-build_abe-stage2/console.log.xz | Bin 204848 -> 202628 bytes 09-build_abe-gdb/console.log.xz | Bin 37660 -> 37372 bytes 10-build_abe-qemu/console.log.xz | Bin 31428 -> 31792 bytes 11-build_abe-dejagnu/console.log.xz | Bin 3880 -> 3904 bytes 12-build_abe-check_gcc/console.log.xz | Bin 2544 -> 2464 bytes 13-check_regression/console.log.xz | Bin 7628 -> 6384 bytes 13-check_regression/extra-bisect-params | 1 + 13-check_regression/fails.sum | 11 + 13-check_regression/mail-body.txt | 82 +- 13-check_regression/results.compare | 41 +- 13-check_regression/results.compare2 | 314 +-- 13-check_regression/results.regressions | 31 + 14-update_baseline/console.log | 38 +- dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- git/gdb_rev | 2 +- git/glibc_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 84 +- mail/mail-subject.txt | 2 +- manifest.sh | 38 +- results | 31 + sumfiles/g++.log.xz | Bin 3417424 -> 3443748 bytes sumfiles/g++.sum | 185 +- sumfiles/gcc.log.xz | Bin 3023120 -> 3017360 bytes sumfiles/gcc.sum | 3956 +++++++++++++++---------------- sumfiles/gfortran.log.xz | Bin 1028440 -> 1032696 bytes sumfiles/gfortran.sum | 46 +- sumfiles/libatomic.log.xz | Bin 2292 -> 2296 bytes sumfiles/libatomic.sum | 4 +- sumfiles/libgomp.log.xz | Bin 202268 -> 202740 bytes sumfiles/libgomp.sum | 16 +- sumfiles/libitm.log.xz | Bin 2656 -> 2656 bytes sumfiles/libitm.sum | 6 +- sumfiles/libstdc++.log.xz | Bin 422452 -> 424924 bytes sumfiles/libstdc++.sum | 18 +- 44 files changed, 2347 insertions(+), 2569 deletions(-) create mode 100644 13-check_regression/extra-bisect-params create mode 100644 13-check_regression/fails.sum create mode 100644 13-check_regression/results.regressions -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 1 month

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_kernel/llvm-master-arm-stable-allyesconfig updated (0de52c4df5 -> 2f08983b30)

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 0de52c4df5 28: onsuccess: #496: 20661: Success after binutils/llvm/linu [...] new 2f08983b30 29: onsuccess: #497: 20661: Success after binutils/llvm/linu [...] 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 1728 -> 1696 bytes 02-prepare_abe/console.log.xz | Bin 2756 -> 2752 bytes 03-build_abe-binutils/console.log.xz | Bin 29840 -> 30168 bytes 04-build_kernel_llvm/console.log.xz | Bin 64744 -> 65304 bytes 05-build_abe-qemu/console.log.xz | Bin 31716 -> 30908 bytes 06-build_linux/console.log.xz | Bin 5052 -> 4768 bytes 08-check_regression/console.log.xz | Bin 4496 -> 4508 bytes 08-check_regression/mail-body.txt | 2 +- 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 | 4 ++-- mail/mail-subject.txt | 2 +- manifest.sh | 32 ++++++++++++++++---------------- 17 files changed, 26 insertions(+), 26 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 1 month

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_gcc_check/master-arm updated (5bad0beb57 -> 9f158895b8)

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_check/master-arm in repository toolchain/ci/base-artifacts. discards 5bad0beb57 167: onsuccess: #1787: 1: Success after gcc: 8 commits discards 04b09152a3 166: onsuccess: #1786: 1: Success after gcc: 10 commits discards 033b35de86 165: onsuccess: #1785: 1: Success after binutils/gcc: 6 commits discards 0d87d7f549 164: onsuccess: #1784: 1: Success after binutils/gcc: 11 commits discards 149ddd4385 163: onsuccess: #1783: 1: Success after binutils/gcc: 8 commits discards 24e7fc5db0 162: onsuccess: #1782: 1: Success after binutils/gcc: 14 commits discards ea8f45c849 161: onsuccess: #1781: 1: Success after binutils/gcc: 16 commits discards 3c7b1cf8f3 160: onsuccess: #1780: 1: Success after binutils/gcc: 4 commits discards 8a8b9446ab 159: onsuccess: #1779: 1: Success after gcc: 2 commits discards 746bf90c96 158: onsuccess: #1778: 1: Success after binutils/gcc: 30 commits discards 37558a6aa8 157: onsuccess: #1777: 1: Success after binutils/gcc: 3 commits discards 5ba6e6c58a 156: onsuccess: #1776: 1: Success after binutils/gcc: 4 commits discards 9b0bd8f1d8 155: onsuccess: #1775: 1: Success after binutils: 2 commits discards 0faf79e057 154: onsuccess: #1774: 1: Success after binutils/gcc: 20 commits discards fcd49ce5cf 153: onsuccess: #1773: 1: Success after gcc: 4 commits discards 215a2ffa91 152: onsuccess: #1772: 1: Success after binutils/gcc: 2 commits discards f78eed9027 151: onsuccess: #1771: 1: Success after basepoints/gcc-13-30 [...] discards 93f4714738 150: onsuccess: #1770: 1: Success after basepoints/gcc-13-30 [...] discards 1d876ea27e 149: onsuccess: #1769: 1: Success after gcc: 3 commits discards 86a2a89bb8 148: onsuccess: #1768: 1: Success after binutils/gcc: 18 commits discards e5689b17b0 147: onsuccess: #1766: 1: Success after binutils/gcc: 16 commits discards 9f45c98b0a 146: onsuccess: #1765: 1: Success after binutils/gcc: 11 commits discards 056970cc7e 145: onsuccess: #1764: 1: Success after binutils/gcc: 13 commits discards 7eb8608f10 144: onsuccess: #1763: 1: Success after binutils/gcc: 16 commits discards 1d6b15c417 143: onsuccess: #1762: 1: Success after binutils/gcc: 12 commits discards 541e565909 142: onsuccess: #1761: 1: Success after gcc: 83 commits discards acbabd0160 141: onsuccess: #1759: 1: Success after gdb-12-branchpoint-2 [...] discards d9dfea0fa7 140: onsuccess: #1756: 1: Success after binutils: 3 commits discards 28fc09375e 139: onsuccess: #1753: 1: Success after binutils: 5 commits discards b57d9c08be 138: onsuccess: #1749: 1: Success after binutils: 5 commits discards a86b771948 137: onsuccess: #1746: 1: Success after gdb-12-branchpoint-2 [...] discards f6a8e3ed8a 136: onsuccess: #1742: 1: Success after gdb-12-branchpoint-2 [...] discards ea2885acee 135: onsuccess: #1739: 1: Success after binutils: 4 commits discards 47385a45a5 134: onsuccess: #1736: 1: Success after binutils: 3 commits discards ffff521439 133: onsuccess: #1733: 1: Success after binutils: 3 commits discards 7b23a53be3 132: onsuccess: #1731: 1: Success after binutils/gcc: 28 commits discards 9eef936586 131: onsuccess: #1730: 1: Success after binutils/gcc: 4 commits discards 17c4bae1e1 130: onsuccess: #1729: 1: Success after gcc: 9 commits discards e9137de842 129: onsuccess: #1728: 1: Success after basepoints/gcc-13-28 [...] discards d7b1d74d1f 128: onsuccess: #1727: 1: Success after binutils/gcc: 2 commits discards 902d8e4ef1 127: onsuccess: #1726: 1: Success after basepoints/gcc-13-28 [...] discards 1e51b16b4e 126: onsuccess: #1725: 1: Success after binutils/gcc: 3 commits discards 0238e925a3 125: onsuccess: #1724: 1: Success after binutils/gcc: 7 commits discards 4325ad7514 124: onsuccess: #1723: 1: Success after binutils/gcc: 4 commits discards 7850258122 123: onsuccess: #1722: 1: Success after binutils/gcc: 48 commits discards b087a65393 122: onsuccess: #1718: 1: Success after binutils/gcc: 25 commits discards 879ec555ce 121: onsuccess: #1717: 1: Success after binutils/gcc: 17 commits discards 33ca0e282e 120: onsuccess: #1716: 1: Success after binutils/gcc: 4 commits discards 4e42419acb 119: onsuccess: #1715: 1: Success after binutils: 4 commits discards 32259caa79 118: onsuccess: #1714: 1: Success after binutils/gcc: 13 commits discards 24211e73c3 117: onsuccess: #1713: 1: Success after binutils/gcc: 15 commits discards a005ac6182 116: onsuccess: #1712: 1: Success after binutils/gcc: 6 commits discards 3951e9a0fb 115: onsuccess: #1711: 1: Success after binutils/gcc: 13 commits discards a88673dcf9 114: onsuccess: #1710: 1: Success after binutils/gcc: 11 commits discards 2495009a6a 113: onsuccess: #1709: 1: Success after binutils/gcc: 10 commits discards 83973abffa 112: onsuccess: #1708: 1: Success after binutils/gcc: 4 commits discards b9e82ed0f2 111: onsuccess: #1707: 1: Success after binutils/gcc: 2 commits discards 1abc06ea1d 110: onsuccess: #1706: 1: Success after binutils/gcc: 4 commits discards 81304fae10 109: onsuccess: #1705: 1: Success after basepoints/gcc-13-27 [...] discards fd25d95451 108: onsuccess: #1704: 1: Success after binutils/gcc: 2 commits discards 308a0ca5ab 107: onsuccess: #1703: 1: Success after basepoints/gcc-13-27 [...] discards c771a6692c 106: onsuccess: #1702: 1: Success after gcc: 4 commits discards f9aaf61c00 105: onsuccess: #1701: 1: Success after binutils/gcc: 2 commits discards adb12e7a94 104: onsuccess: #1700: 1: Success after gcc: 2 commits discards 480adc02be 103: onsuccess: #1699: 1: Success after binutils/gcc: 2 commits discards 5e39e793fb 102: onsuccess: #1698: 1: Success after binutils/gcc: 6 commits discards 30c38d4611 101: onsuccess: #1697: 1: Success after binutils/gcc: 271 commits discards 261bc053ae 100: onsuccess: #1658: 1: Success after basepoints/gcc-13-25 [...] discards 6fa4e89308 99: onsuccess: #1657: 1: Success after binutils/gcc: 8 commits discards cb2c3da16d 98: onsuccess: #1656: 1: Success after binutils/gcc: 48 commits discards 86c839a3c9 97: onsuccess: #1655: 1: Success after binutils/gcc: 3 commits discards 2457fe1642 96: onsuccess: #1654: 1: Success after gcc: 5 commits discards 3c344d4043 95: onsuccess: #1653: 1: Success after gcc: 13 commits discards a5a3a050e0 94: onsuccess: #1652: 1: Success after binutils/gcc: 43 commits discards 287c3d00cd 93: onsuccess: #1648: 1: Success after basepoints/gcc-13-239 [...] discards 8caa592e76 92: onsuccess: #1647: 1: Success after binutils/gcc: 2 commits discards fafa3c2fab 91: onsuccess: #1646: 1: Success after basepoints/gcc-13-239 [...] discards aca5304bad 90: onsuccess: #1645: 1: Success after gcc: 2 commits discards fcae34bea5 89: onsuccess: #1644: 1: Success after basepoints/gcc-13-238 [...] discards acb700f194 88: onsuccess: 1: Success after binutils/gcc: 2 commits discards 8216822127 87: onsuccess: 1: Success after gcc: 6 commits discards d95354ec5a 86: onsuccess: 1: Success after binutils/gcc: 8 commits discards 41377cde43 85: onsuccess: 1: Success after binutils/gcc: 19 commits discards e6b9f8fc4d 84: onsuccess: 1: Success after binutils/gcc: 2 commits discards c71e61d387 83: onsuccess: 1: Success after gcc: 14 commits discards edfd32cb49 82: onsuccess: 1: Success after binutils/gcc: 9 commits discards 58c5988e23 81: onsuccess: 1: Success after binutils/gcc: 8 commits discards 5846a44d65 80: onsuccess: 1: Success after binutils/gcc: 8 commits discards 9ba0c07b49 79: onsuccess: 1: Success after binutils/gcc: 23 commits discards 106f44a6fd 78: onsuccess: 1: Success after binutils/gcc: 17 commits discards d2d29f826e 77: onsuccess: 1: Successful build after binutils/gcc: 10 commits discards c6bdb702f1 76: onsuccess: 1: Successful build after binutils/gcc: 3 commits discards 08de2b3629 75: onsuccess: 1: Successful build after binutils/gcc: 6 commits discards 1c0ede444e 74: onsuccess: 1: Successful build after binutils/gcc: 44 commits discards ea91c681ef 73: onsuccess: 1: Successful build after binutils/gcc: 18 commits discards 6fc45c14d8 72: onsuccess: 1: Successful build after baseline build: no [...] discards 65db9bbb57 71: onsuccess: 1: Successful build after binutils: PR29494 T [...] discards 46b4306189 70: onsuccess: 1: Successful build after binutils/gcc: 3 commits discards 6a13a4d496 69: onsuccess: 1: Successful build after gcc: d: Merge upstr [...] discards d9a3a66968 68: onsuccess: 1: Successful build after gcc: 2 commits discards 6a88516d28 67: onsuccess: 1: Successful build after binutils/gcc: 6 commits new 7dc46f80ef 67: onsuccess: 1: Successful build after binutils/gcc: 6 commits new 2fc92f428b 68: onsuccess: 1: Successful build after gcc: 2 commits new ede1e1bf3e 69: onsuccess: 1: Successful build after gcc: d: Merge upstr [...] new e9ab9d5025 70: onsuccess: 1: Successful build after binutils/gcc: 3 commits new 295af0df38 71: onsuccess: 1: Successful build after binutils: PR29494 T [...] new ba2052d163 72: onsuccess: 1: Successful build after baseline build: no [...] new f4c308b56b 73: onsuccess: 1: Successful build after binutils/gcc: 18 commits new cdaa153866 74: onsuccess: 1: Successful build after binutils/gcc: 44 commits new a5420546ec 75: onsuccess: 1: Successful build after binutils/gcc: 6 commits new c22dc5c6e4 76: onsuccess: 1: Successful build after binutils/gcc: 3 commits new f468b2d1a1 77: onsuccess: 1: Successful build after binutils/gcc: 10 commits new 34e370ec64 78: onsuccess: 1: Success after binutils/gcc: 17 commits new a7f9c5ad78 79: onsuccess: 1: Success after binutils/gcc: 23 commits new ad8c9b9017 80: onsuccess: 1: Success after binutils/gcc: 8 commits new b29166b9ff 81: onsuccess: 1: Success after binutils/gcc: 8 commits new f4cb92ef70 82: onsuccess: 1: Success after binutils/gcc: 9 commits new 3fd4021729 83: onsuccess: 1: Success after gcc: 14 commits new 7e5c020731 84: onsuccess: 1: Success after binutils/gcc: 2 commits new 2235dda643 85: onsuccess: 1: Success after binutils/gcc: 19 commits new 7231b03159 86: onsuccess: 1: Success after binutils/gcc: 8 commits new 8873b53c7a 87: onsuccess: 1: Success after gcc: 6 commits new cc907c9707 88: onsuccess: 1: Success after binutils/gcc: 2 commits new 1723f3c6b6 89: onsuccess: #1644: 1: Success after basepoints/gcc-13-238 [...] new 009630ba18 90: onsuccess: #1645: 1: Success after gcc: 2 commits new dcd608c158 91: onsuccess: #1646: 1: Success after basepoints/gcc-13-239 [...] new daa50233ef 92: onsuccess: #1647: 1: Success after binutils/gcc: 2 commits new 0ea199ee00 93: onsuccess: #1648: 1: Success after basepoints/gcc-13-239 [...] new 9b2e813330 94: onsuccess: #1652: 1: Success after binutils/gcc: 43 commits new 2c4bfac900 95: onsuccess: #1653: 1: Success after gcc: 13 commits new e1741a63a3 96: onsuccess: #1654: 1: Success after gcc: 5 commits new 8cfec6c2e4 97: onsuccess: #1655: 1: Success after binutils/gcc: 3 commits new b13831e14c 98: onsuccess: #1656: 1: Success after binutils/gcc: 48 commits new 0501624de2 99: onsuccess: #1657: 1: Success after binutils/gcc: 8 commits new 28ec380fdd 100: onsuccess: #1658: 1: Success after basepoints/gcc-13-25 [...] new 730084cf07 101: onsuccess: #1697: 1: Success after binutils/gcc: 271 commits new b6ea442c24 102: onsuccess: #1698: 1: Success after binutils/gcc: 6 commits new cb9064b20f 103: onsuccess: #1699: 1: Success after binutils/gcc: 2 commits new a02225949a 104: onsuccess: #1700: 1: Success after gcc: 2 commits new 32da515523 105: onsuccess: #1701: 1: Success after binutils/gcc: 2 commits new 0c478abd70 106: onsuccess: #1702: 1: Success after gcc: 4 commits new 41b814daef 107: onsuccess: #1703: 1: Success after basepoints/gcc-13-27 [...] new 7c86518d29 108: onsuccess: #1704: 1: Success after binutils/gcc: 2 commits new 0c0d53e043 109: onsuccess: #1705: 1: Success after basepoints/gcc-13-27 [...] new cdb1cbb11b 110: onsuccess: #1706: 1: Success after binutils/gcc: 4 commits new e549ce4241 111: onsuccess: #1707: 1: Success after binutils/gcc: 2 commits new ad20706e0c 112: onsuccess: #1708: 1: Success after binutils/gcc: 4 commits new e41aa03c23 113: onsuccess: #1709: 1: Success after binutils/gcc: 10 commits new 00838c7057 114: onsuccess: #1710: 1: Success after binutils/gcc: 11 commits new 899ce65906 115: onsuccess: #1711: 1: Success after binutils/gcc: 13 commits new 48ed620886 116: onsuccess: #1712: 1: Success after binutils/gcc: 6 commits new 8cda1f2836 117: onsuccess: #1713: 1: Success after binutils/gcc: 15 commits new 82a534d699 118: onsuccess: #1714: 1: Success after binutils/gcc: 13 commits new 4190d348e0 119: onsuccess: #1715: 1: Success after binutils: 4 commits new 25ad5ddd05 120: onsuccess: #1716: 1: Success after binutils/gcc: 4 commits new d9fb335be4 121: onsuccess: #1717: 1: Success after binutils/gcc: 17 commits new df3668be18 122: onsuccess: #1718: 1: Success after binutils/gcc: 25 commits new 38433078e9 123: onsuccess: #1722: 1: Success after binutils/gcc: 48 commits new d1b0c3eea7 124: onsuccess: #1723: 1: Success after binutils/gcc: 4 commits new b5ece0be15 125: onsuccess: #1724: 1: Success after binutils/gcc: 7 commits new 04e650b38e 126: onsuccess: #1725: 1: Success after binutils/gcc: 3 commits new dca3726ad4 127: onsuccess: #1726: 1: Success after basepoints/gcc-13-28 [...] new 231439fbd6 128: onsuccess: #1727: 1: Success after binutils/gcc: 2 commits new fa8136f045 129: onsuccess: #1728: 1: Success after basepoints/gcc-13-28 [...] new 68fab5beba 130: onsuccess: #1729: 1: Success after gcc: 9 commits new 6e57695e5c 131: onsuccess: #1730: 1: Success after binutils/gcc: 4 commits new 8b85b6cb04 132: onsuccess: #1731: 1: Success after binutils/gcc: 28 commits new 684d6bbad3 133: onsuccess: #1733: 1: Success after binutils: 3 commits new d857c319d2 134: onsuccess: #1736: 1: Success after binutils: 3 commits new e568966874 135: onsuccess: #1739: 1: Success after binutils: 4 commits new 8aad108522 136: onsuccess: #1742: 1: Success after gdb-12-branchpoint-2 [...] new 4e8a7c004d 137: onsuccess: #1746: 1: Success after gdb-12-branchpoint-2 [...] new 8e477fca0e 138: onsuccess: #1749: 1: Success after binutils: 5 commits new bc3cd31779 139: onsuccess: #1753: 1: Success after binutils: 5 commits new a223b05ebe 140: onsuccess: #1756: 1: Success after binutils: 3 commits new dad2c1bba1 141: onsuccess: #1759: 1: Success after gdb-12-branchpoint-2 [...] new 4043b53682 142: onsuccess: #1761: 1: Success after gcc: 83 commits new a27532c462 143: onsuccess: #1762: 1: Success after binutils/gcc: 12 commits new d365b0f18a 144: onsuccess: #1763: 1: Success after binutils/gcc: 16 commits new 5dd8569cf4 145: onsuccess: #1764: 1: Success after binutils/gcc: 13 commits new df49be1487 146: onsuccess: #1765: 1: Success after binutils/gcc: 11 commits new 51dff6780f 147: onsuccess: #1766: 1: Success after binutils/gcc: 16 commits new cbb1700038 148: onsuccess: #1768: 1: Success after binutils/gcc: 18 commits new 4138c5b125 149: onsuccess: #1769: 1: Success after gcc: 3 commits new 2644f651f0 150: onsuccess: #1770: 1: Success after basepoints/gcc-13-30 [...] new db0d5fb0b2 151: onsuccess: #1771: 1: Success after basepoints/gcc-13-30 [...] new a0a59e6a08 152: onsuccess: #1772: 1: Success after binutils/gcc: 2 commits new e835892a98 153: onsuccess: #1773: 1: Success after gcc: 4 commits new edeba39e1e 154: onsuccess: #1774: 1: Success after binutils/gcc: 20 commits new 6cc3c780f6 155: onsuccess: #1775: 1: Success after binutils: 2 commits new 203888c288 156: onsuccess: #1776: 1: Success after binutils/gcc: 4 commits new d9e2a14ff8 157: onsuccess: #1777: 1: Success after binutils/gcc: 3 commits new ac66a6e7cb 158: onsuccess: #1778: 1: Success after binutils/gcc: 30 commits new f52ad5daa2 159: onsuccess: #1779: 1: Success after gcc: 2 commits new aa2679f891 160: onsuccess: #1780: 1: Success after binutils/gcc: 4 commits new 86008eddcc 161: onsuccess: #1781: 1: Success after binutils/gcc: 16 commits new 7a7824b7d3 162: onsuccess: #1782: 1: Success after binutils/gcc: 14 commits new 2a0f7a9911 163: onsuccess: #1783: 1: Success after binutils/gcc: 8 commits new 713a982df3 164: onsuccess: #1784: 1: Success after binutils/gcc: 11 commits new f8717f5efa 165: onsuccess: #1785: 1: Success after binutils/gcc: 6 commits new 186ecd66da 166: onsuccess: #1786: 1: Success after gcc: 10 commits new b806ca6fe2 167: onsuccess: #1787: 1: Success after gcc: 8 commits new 9f158895b8 168: onsuccess: #1788: 1: Success after binutils/gcc: 9 commits This update added new revisions after undoing existing revisions. That is to say, some revisions that were in the old version of the branch are not in the new version. This situation occurs when a user --force pushes a change and generates a repository containing something like this: * -- * -- B -- O -- O -- O (5bad0beb57) \ N -- N -- N refs/heads/linaro-local/ci/tcwg_gcc_check/master-arm (9f [...] 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 1660 -> 1664 bytes 02-prepare_abe/console.log.xz | Bin 2720 -> 2720 bytes 03-build_abe-binutils/console.log.xz | Bin 50460 -> 50816 bytes 04-build_abe-gcc/console.log.xz | Bin 232220 -> 234080 bytes 05-build_abe-dejagnu/console.log.xz | Bin 3816 -> 3860 bytes 06-build_abe-check_gcc/console.log.xz | Bin 2424 -> 2388 bytes 07-check_regression/console.log.xz | Bin 5420 -> 4608 bytes 07-check_regression/results.compare | 16 +- 07-check_regression/results.compare2 | 273 +- 08-update_baseline/console.log | 40 +- 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 | 18 +- sumfiles/g++.log.xz | Bin 2781160 -> 2785020 bytes sumfiles/g++.sum | 122 +- sumfiles/gcc.log.xz | Bin 2366864 -> 2407348 bytes sumfiles/gcc.sum | 4374 ++++++++++++++++----------------- sumfiles/gfortran.log.xz | Bin 906640 -> 908220 bytes sumfiles/gfortran.sum | 40 +- sumfiles/libatomic.log.xz | Bin 2168 -> 2172 bytes sumfiles/libatomic.sum | 4 +- sumfiles/libgomp.log.xz | Bin 204572 -> 204624 bytes sumfiles/libgomp.sum | 16 +- sumfiles/libitm.log.xz | Bin 2544 -> 2532 bytes sumfiles/libitm.sum | 6 +- sumfiles/libstdc++.log.xz | Bin 458164 -> 468848 bytes sumfiles/libstdc++.sum | 10 +- 31 files changed, 2336 insertions(+), 2595 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 1 month

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_gnu_native_check_gdb/master-aarch64 updated (100a5305d -> 121dd2c06)

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. from 100a5305d 51: onsuccess: #824: 1: Success after binutils/gcc/linux/glib [...] new 121dd2c06 52: onsuccess: #826: 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 1696 -> 1680 bytes 02-prepare_abe/console.log.xz | Bin 2736 -> 2720 bytes 03-build_abe-binutils/console.log.xz | Bin 38572 -> 37772 bytes 04-build_abe-gcc/console.log.xz | Bin 213712 -> 212476 bytes 06-build_abe-linux/console.log.xz | Bin 9192 -> 9400 bytes 07-build_abe-glibc/console.log.xz | Bin 240196 -> 239296 bytes 08-build_abe-gdb/console.log.xz | Bin 37444 -> 37692 bytes 09-build_abe-dejagnu/console.log.xz | Bin 3876 -> 3820 bytes 10-build_abe-check_gdb/console.log.xz | Bin 2008 -> 2232 bytes 11-check_regression/console.log.xz | Bin 25760 -> 13184 bytes 11-check_regression/extra-bisect-params | 2 +- 11-check_regression/fails.sum | 46 +- 11-check_regression/mail-body.txt | 179 +- 11-check_regression/results.compare | 89 +- 11-check_regression/results.compare2 | 5909 +++++++++---------------------- 11-check_regression/results.regressions | 89 +- 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 | 181 +- mail/mail-subject.txt | 2 +- manifest.sh | 38 +- results | 89 +- sumfiles/gdb.log.xz | Bin 1929884 -> 1903096 bytes sumfiles/gdb.sum | 2943 +-------------- 29 files changed, 1999 insertions(+), 7582 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 1 month

Jump to page:

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

Tcwg-commits October 2022