Tcwg-commits October 2022

tcwg-commits@lists.linaro.org

6 participants
4723 discussions

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_kernel/gnu-master-arm-stable-defconfig updated (9a5eed2716 -> 1ce40f7642)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. tcwg-buildslave pushed a change to branch linaro-local/ci/tcwg_kernel/gnu-master-arm-stable-defconfig in repository toolchain/ci/base-artifacts. from 9a5eed2716 13: onsuccess: #414: boot: Success after binutils/gcc/qemu: [...] new 1ce40f7642 14: onsuccess: #415: boot: Success after binutils/gcc/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 1704 -> 1688 bytes 02-prepare_abe/console.log.xz | Bin 2740 -> 2756 bytes 03-build_abe-binutils/console.log.xz | Bin 30600 -> 31300 bytes 04-build_abe-stage1/console.log.xz | Bin 91700 -> 92576 bytes 05-build_abe-qemu/console.log.xz | Bin 31880 -> 31756 bytes 06-build_linux/console.log.xz | Bin 5224 -> 5252 bytes 07-boot_linux/console.log.xz | Bin 5832 -> 5896 bytes 08-check_regression/console.log.xz | Bin 4092 -> 4368 bytes dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- git/linux_rev | 2 +- git/qemu_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 2 +- mail/mail-subject.txt | 2 +- manifest.sh | 30 +++++++++++++++--------------- 17 files changed, 23 insertions(+), 23 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_O1 updated (36f1570f0a -> b9bc4f710c)

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_O1 in repository toolchain/ci/base-artifacts. from 36f1570f0a 59: force: #453: 2: Success after gcc: 29 commits new b9bc4f710c 60: force: #454: 1: Failure after basepoints/gcc-13-3172-gf3 [...] 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 1752 -> 1620 bytes 02-prepare_abe/console.log.xz | Bin 2740 -> 2744 bytes 04-build_abe-binutils/console.log.xz | Bin 38028 -> 38664 bytes 05-build_abe-bootstrap_O1/console.log.xz | Bin 275632 -> 159700 bytes 06-check_regression/console.log.xz | Bin 2752 -> 3424 bytes 06-check_regression/jira-body.txt | 2 +- 06-check_regression/mail-body.txt | 14 +++- 06-check_regression/mail-subject.txt | 2 +- 06-check_regression/results.regressions | 10 +++ 06-check_regression/trigger-bisect | 2 + 06-check_regression/trigger-notify | 0 07-update_baseline/console.log | 9 --- dashboard/dashboard-generate.sh | 2 +- git/gcc_rev | 2 +- jenkins/jira-status.draft | 4 + jenkins/mail-body.draft | 129 +++++++++++++++++++++++++++++++ jenkins/mail-recipients.draft | 1 + jenkins/mail-subject.draft | 1 + jenkins/notify.sh | 3 + mail/jira-body.txt | 2 +- mail/mail-body.txt | 14 +++- mail/mail-subject.txt | 2 +- manifest.sh | 14 ++-- results | 12 ++- 24 files changed, 198 insertions(+), 27 deletions(-) create mode 100644 06-check_regression/results.regressions create mode 100644 06-check_regression/trigger-bisect create mode 100644 06-check_regression/trigger-notify create mode 100644 jenkins/jira-status.draft create mode 100644 jenkins/mail-body.draft create mode 100644 jenkins/mail-recipients.draft create mode 100644 jenkins/mail-subject.draft create 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/interesting-commits] branch master updated (7b3a66f -> 48d7225)

by tcwg-buildslave

This is an automated email from the git hooks/post-receive script. "tcwg-buildslave pushed a change to branch master in repository toolchain/ci/interesting-commits. from 7b3a66f Add entry f30e9fd33e56a5a721346ea6140722e1b193db42 from https [...] new 48d7225 Add entry f30e9fd33e56a5a721346ea6140722e1b193db42 from https [...] The 1 revisions listed above as "new" are entirely new to this repository and will be described in separate emails. The revisions listed as "adds" were already present in the repository and have only been added to this reference. Summary of changes: .../tcwg_gcc_bootstrap/master-aarch64-bootstrap_O1}/build_url | 2 +- .../last_good | 0 .../summary.txt | 0 .../tcwg_gcc_bootstrap/status.txt | 3 +++ 4 files changed, 4 insertions(+), 1 deletion(-) copy gcc/sha1/{953e08fde44a596e4ec2491efd15cd645e1ddc48/tcwg_gcc_bootstrap/master- [...] copy gcc/sha1/f30e9fd33e56a5a721346ea6140722e1b193db42/tcwg_gcc_bootstrap/{master- [...] copy gcc/sha1/f30e9fd33e56a5a721346ea6140722e1b193db42/tcwg_gcc_bootstrap/{master- [...] -- 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_profiled_lto updated (31ad35abf0 -> 9d65dbeb20)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. tcwg-buildslave pushed a change to branch linaro-local/ci/tcwg_gcc_bootstrap/master-arm-bootstrap_profiled_lto in repository toolchain/ci/base-artifacts. from 31ad35abf0 56: onsuccess: #452: 2: Success after binutils/gcc: 54 commits new 9d65dbeb20 57: onsuccess: #454: 2: Success after binutils: 8 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 -> 1648 bytes 02-prepare_abe/console.log.xz | Bin 2728 -> 2732 bytes 04-build_abe-binutils/console.log.xz | Bin 50772 -> 51052 bytes 05-build_abe-bootstrap_profiled_lto/console.log.xz | Bin 954652 -> 957200 bytes 06-check_regression/console.log.xz | Bin 3060 -> 2740 bytes dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 2 +- mail/mail-subject.txt | 2 +- manifest.sh | 17 ++++++++--------- 11 files changed, 13 insertions(+), 14 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 (19a1909b8b -> 202d8774df)

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 19a1909b8b 176: onsuccess: #2211: 1: Success after binutils/gcc/linux/g [...] discards fd6319c799 175: onsuccess: #2210: 1: Success after binutils/gcc/linux/g [...] discards cd30d35efb 174: onsuccess: #2209: 1: Success after binutils/gcc/gdb: 20 [...] discards b33a8eba9e 173: onsuccess: #2208: 1: Success after gcc: 10 commits discards b2f32c5837 172: onsuccess: #2207: 1: Success after binutils/gcc/linux/g [...] discards a791fc71cc 171: onsuccess: #2206: 1: Success after binutils/gcc/linux/g [...] discards ab83d54e18 170: onsuccess: #2205: 1: Success after binutils/gcc/glibc/g [...] discards d98f35c58d 169: onsuccess: #2204: 1: Success after binutils/gcc/glibc/g [...] discards e574fd7ef5 168: onsuccess: #2203: 1: Success after binutils/gcc/glibc/g [...] discards d14da345a5 167: onsuccess: #2202: 1: Success after gcc/linux/glibc/qemu [...] discards fa0fb3ab77 166: onsuccess: #2201: 1: Success after gcc/glibc/qemu: 40 commits discards ed5de251ed 165: onsuccess: #2200: 1: Success after binutils/gdb: 8 commits discards a73101c555 164: onsuccess: #2199: 1: Success after binutils/gcc/linux/g [...] discards 3f6ae22dc6 163: onsuccess: #2198: 1: Success after binutils/gcc/linux/g [...] discards 194c84eadf 162: onsuccess: #2197: 1: Success after binutils/gcc/glibc/g [...] discards e9e07e49ca 161: onsuccess: #2196: 1: Success after binutils/gcc/linux/g [...] discards 46708f3151 160: onsuccess: #2195: 1: Success after binutils/gcc/linux/g [...] discards 655d588be9 159: onsuccess: #2194: 1: Success after gcc/linux/glibc: 197 [...] discards e3818046f8 158: onsuccess: #2193: 1: Success after binutils/gcc/glibc/g [...] discards d13758f6e7 157: onsuccess: #2192: 1: Success after binutils/gcc/gdb: 8 commits discards 3214c3fd58 156: onsuccess: #2191: 1: Success after binutils/gcc/linux/g [...] discards 8488f77197 155: onsuccess: #2190: 1: Success after binutils/gcc/linux/g [...] discards 924eb10eb4 154: onsuccess: #2189: 1: Success after binutils/gcc/gdb: 18 [...] discards cf92d332d9 153: onsuccess: #2188: 1: Success after binutils/gcc/gdb: 3 commits discards 6ebd35f1b3 152: onsuccess: #2187: 1: Success after gcc/linux/glibc: 22 commits discards 555bf676c6 151: onsuccess: #2186: 1: Success after gcc: 2 commits discards 351544510e 150: onsuccess: #2185: 1: Success after gcc: 3 commits discards ba22dd1df9 149: onsuccess: #2184: 1: Success after binutils/gcc/linux/g [...] discards cfbd2d0c55 148: onsuccess: #2183: 1: Success after gcc/linux/glibc: 64 commits discards 2197e4dabc 147: onsuccess: #2182: 1: Success after binutils/gcc/gdb: 18 [...] discards cd3a596e0d 146: onsuccess: #2181: 1: Success after binutils/glibc/gdb: [...] discards fb05391b41 145: onsuccess: #2180: 1: Success after binutils/gcc/linux/g [...] discards b7258c87d4 144: onsuccess: #2179: 1: Success after binutils/gcc/linux/g [...] discards 9a1d16493b 143: onsuccess: #2178: 1: Success after binutils/gcc/gdb/qem [...] discards 9d11439f1f 142: onsuccess: #2177: 1: Success after gcc/glibc: 4 commits discards 7e2602bdc0 141: onsuccess: #2176: 1: Success after binutils/gcc/gdb: 6 commits discards 81401379c5 140: onsuccess: #2175: 1: Success after binutils/gcc/linux/g [...] discards 6d85e978bb 139: onsuccess: #2174: 1: Success after binutils/gcc/gdb: 13 [...] discards 3c6dd08535 138: onsuccess: #2173: 1: Success after binutils/gcc/gdb: 5 commits discards 12d30c91f8 137: onsuccess: #2172: 1: Success after binutils/gcc/linux/g [...] discards c7baa4f85a 136: onsuccess: #2171: 1: Success after binutils/gcc/gdb/qem [...] discards 0dc7ca4d91 135: onsuccess: #2170: 1: Success after gcc/linux/qemu: 63 commits discards db35c06119 134: onsuccess: #2169: 1: Success after binutils/gcc/gdb: 13 [...] discards adc8b0725b 133: onsuccess: #2168: 1: Success after binutils/gcc/linux/g [...] discards 48da575c22 132: onsuccess: #2167: 1: Success after binutils/gcc/glibc/g [...] discards 3287920274 131: onsuccess: #2166: 1: Success after binutils/gcc/gdb: 12 [...] discards e805d7f386 130: onsuccess: #2165: 1: Success after binutils/gcc/gdb: 32 [...] discards fd531b9cfe 129: onsuccess: #2164: 1: Success after binutils/gcc/linux/g [...] discards db1b0c9029 128: onsuccess: #2163: 1: Success after linux: 23 commits discards 184285697f 127: onsuccess: #2162: 1: Success after gcc: 9 commits discards 8f2b0a770f 126: onsuccess: #2161: 1: Success after basepoints/gcc-13-28 [...] discards c63957deb0 125: onsuccess: #2160: 1: Success after binutils/gcc/linux/g [...] discards 8a3cd82e98 124: onsuccess: #2159: 1: Success after linux: 23 commits discards 91f6c52c98 123: onsuccess: #2158: 1: Success after basepoints/gcc-13-28 [...] discards 6fe414c055 122: onsuccess: #2157: 1: Success after binutils/gcc/gdb: 6 commits discards d30693f4d7 121: onsuccess: #2156: 1: Success after binutils/gcc/linux/g [...] discards 62be23dfce 120: onsuccess: #2155: 1: Success after binutils/gcc/linux/g [...] discards 6b7e318cfe 119: onsuccess: #2154: 1: Success after binutils/gcc/linux/g [...] discards 8a6e839b7f 118: onsuccess: #2151: 1: Success after binutils/gcc/linux/g [...] discards a26f74d75d 117: onsuccess: #2150: 1: Success after binutils/gcc/glibc/g [...] discards 642c75aac9 116: onsuccess: #2148: 1: Success after binutils/gcc/gdb: 7 commits discards b0fa7bed55 115: onsuccess: #2147: 1: Success after binutils/linux/glibc [...] discards 61b94c2575 114: onsuccess: #2146: 1: Success after binutils/gcc/glibc/g [...] discards 819c712f27 113: onsuccess: #2145: 1: Success after binutils/gcc/glibc/g [...] discards bca6124e86 112: onsuccess: #2144: 1: Success after binutils/gcc/glibc/g [...] discards 7c254b46b8 111: onsuccess: #2143: 1: Success after binutils/gcc/linux/g [...] discards f660066145 110: onsuccess: #2142: 1: Success after binutils/gcc/glibc/g [...] discards a3833a4d97 109: onsuccess: #2141: 1: Success after gcc/glibc: 6 commits discards 2e9f468705 108: onsuccess: #2140: 1: Success after binutils/gcc/gdb: 5 commits discards 4d50fd23ea 107: onsuccess: #2139: 1: Success after binutils/gcc/gdb: 3 commits discards bc5a9315c7 106: onsuccess: #2138: 1: Success after binutils/gcc/glibc/g [...] discards 6d656c802f 105: onsuccess: #2137: 1: Success after basepoints/gcc-13-27 [...] discards b2b2dfb136 104: onsuccess: #2136: 1: Success after binutils/gcc/gdb: 3 commits discards abe3035f55 103: onsuccess: #2135: 1: Success after gcc/linux/glibc/gdb/ [...] discards 00235d1f93 102: onsuccess: #2133: 1: Success after gdb-12-branchpoint-1 [...] discards bdbd84caf6 101: onsuccess: #2130: 1: Success after binutils: 81 commits discards f88336034b 100: onsuccess: #2077: 1: Success after binutils/gcc/linux/g [...] discards 45db185a5b 99: onsuccess: #2074: 1: Success after baseline build: no ne [...] discards 84738e472a 98: onsuccess: #2073: 1: Success after gcc/linux: 11 commits discards 21d10c223a 97: onsuccess: #2072: 1: Success after binutils/gcc/gdb: 3 commits discards beeb15d4f1 96: onsuccess: #2071: 1: Success after gcc/linux: 56 commits discards 5e82128882 95: onsuccess: #2070: 1: Success after basepoints/gcc-13-238 [...] discards ae5fcf5a24 94: onsuccess: 1: Success after gcc: openmp: Partial OpenMP [...] discards 3c8f3cf064 93: onsuccess: 1: Success after binutils/gcc/linux/gdb: 88 commits discards 90c4a82b22 92: onsuccess: 1: Success after binutils/gcc/linux/gdb/qemu: [...] discards 8eda5e8c96 91: onsuccess: 1: Success after binutils/gcc/gdb: 8 commits discards 33d1fa1f9d 90: onsuccess: 1: Success after binutils/gcc/gdb: 19 commits discards 06bddf40bf 89: onsuccess: 1: Success after binutils/gcc/gdb: 5 commits discards f1c3e6dd20 88: onsuccess: 1: Success after gcc/linux/qemu: 149 commits discards 7a6a6dbc94 87: onsuccess: 1: Success after binutils/gcc/gdb: 14 commits discards 50e4c51a96 86: onsuccess: 1: Success after binutils/gcc/gdb: 7 commits discards 81935a3f1a 85: onsuccess: 1: Success after binutils/gcc/glibc/gdb/qemu: [...] discards 0bea8fa7ee 84: onsuccess: 1: Success after binutils/gcc/linux/gdb: 68 commits discards fcbefa43b7 83: onsuccess: 1: Success after binutils/gcc/glibc/gdb: 17 commits discards ab88fcf918 82: onsuccess: 1: Successful build after binutils/gcc/gdb: 1 [...] discards 1dfdae1ce0 81: onsuccess: 1: Successful build after binutils/gcc/gdb: 6 [...] discards 9b4158a5e7 80: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] discards 0599a70943 79: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] discards 128da2251c 78: onsuccess: 1: Successful build after binutils/gcc/gdb: 4 [...] discards 420ad251c7 77: onsuccess: 1: Successful build after gcc/linux/glibc: 22 [...] discards 39b7336e9e 76: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 916a2a4756 76: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 81c8430e17 77: onsuccess: 1: Successful build after gcc/linux/glibc: 22 [...] new 478799528a 78: onsuccess: 1: Successful build after binutils/gcc/gdb: 4 [...] new b50991bf43 79: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] new 0a1f988dee 80: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] new d390159fd2 81: onsuccess: 1: Successful build after binutils/gcc/gdb: 6 [...] new 282d176f7c 82: onsuccess: 1: Successful build after binutils/gcc/gdb: 1 [...] new ce582a9267 83: onsuccess: 1: Success after binutils/gcc/glibc/gdb: 17 commits new a99138df2e 84: onsuccess: 1: Success after binutils/gcc/linux/gdb: 68 commits new f65b4ad853 85: onsuccess: 1: Success after binutils/gcc/glibc/gdb/qemu: [...] new 0ca0f15e88 86: onsuccess: 1: Success after binutils/gcc/gdb: 7 commits new d095f3d3d0 87: onsuccess: 1: Success after binutils/gcc/gdb: 14 commits new 46fd6a46c2 88: onsuccess: 1: Success after gcc/linux/qemu: 149 commits new caa037ed8d 89: onsuccess: 1: Success after binutils/gcc/gdb: 5 commits new c0043cafcc 90: onsuccess: 1: Success after binutils/gcc/gdb: 19 commits new 746689909e 91: onsuccess: 1: Success after binutils/gcc/gdb: 8 commits new 136de1e7dc 92: onsuccess: 1: Success after binutils/gcc/linux/gdb/qemu: [...] new fa73eae87a 93: onsuccess: 1: Success after binutils/gcc/linux/gdb: 88 commits new 594c19f8f5 94: onsuccess: 1: Success after gcc: openmp: Partial OpenMP [...] new 1a45308ed5 95: onsuccess: #2070: 1: Success after basepoints/gcc-13-238 [...] new 1e25e8c42f 96: onsuccess: #2071: 1: Success after gcc/linux: 56 commits new c2186e7398 97: onsuccess: #2072: 1: Success after binutils/gcc/gdb: 3 commits new d04bea00bb 98: onsuccess: #2073: 1: Success after gcc/linux: 11 commits new bbe627138f 99: onsuccess: #2074: 1: Success after baseline build: no ne [...] new f3c9c31e7c 100: onsuccess: #2077: 1: Success after binutils/gcc/linux/g [...] new bb728033bf 101: onsuccess: #2130: 1: Success after binutils: 81 commits new 848d3e334a 102: onsuccess: #2133: 1: Success after gdb-12-branchpoint-1 [...] new 2216852a9b 103: onsuccess: #2135: 1: Success after gcc/linux/glibc/gdb/ [...] new ca859bc6c5 104: onsuccess: #2136: 1: Success after binutils/gcc/gdb: 3 commits new b6baa39fb6 105: onsuccess: #2137: 1: Success after basepoints/gcc-13-27 [...] new 0f16dd621f 106: onsuccess: #2138: 1: Success after binutils/gcc/glibc/g [...] new 6b1572d10d 107: onsuccess: #2139: 1: Success after binutils/gcc/gdb: 3 commits new 4fd60c3cc4 108: onsuccess: #2140: 1: Success after binutils/gcc/gdb: 5 commits new 7aa2c22165 109: onsuccess: #2141: 1: Success after gcc/glibc: 6 commits new a5585a0179 110: onsuccess: #2142: 1: Success after binutils/gcc/glibc/g [...] new 072847d0d0 111: onsuccess: #2143: 1: Success after binutils/gcc/linux/g [...] new 8cfb8f8a52 112: onsuccess: #2144: 1: Success after binutils/gcc/glibc/g [...] new fc519d413c 113: onsuccess: #2145: 1: Success after binutils/gcc/glibc/g [...] new a5671ab8c4 114: onsuccess: #2146: 1: Success after binutils/gcc/glibc/g [...] new a486eee2ef 115: onsuccess: #2147: 1: Success after binutils/linux/glibc [...] new 61ae6c428b 116: onsuccess: #2148: 1: Success after binutils/gcc/gdb: 7 commits new 1cb3821203 117: onsuccess: #2150: 1: Success after binutils/gcc/glibc/g [...] new 3b5d248844 118: onsuccess: #2151: 1: Success after binutils/gcc/linux/g [...] new fd2b14c14f 119: onsuccess: #2154: 1: Success after binutils/gcc/linux/g [...] new 03baa9368a 120: onsuccess: #2155: 1: Success after binutils/gcc/linux/g [...] new c9aaa3a76d 121: onsuccess: #2156: 1: Success after binutils/gcc/linux/g [...] new a6cbd98d74 122: onsuccess: #2157: 1: Success after binutils/gcc/gdb: 6 commits new d3908de23f 123: onsuccess: #2158: 1: Success after basepoints/gcc-13-28 [...] new d13464a4de 124: onsuccess: #2159: 1: Success after linux: 23 commits new fe033e7896 125: onsuccess: #2160: 1: Success after binutils/gcc/linux/g [...] new 03de3d50e0 126: onsuccess: #2161: 1: Success after basepoints/gcc-13-28 [...] new fb4988aeff 127: onsuccess: #2162: 1: Success after gcc: 9 commits new 0e6729a30b 128: onsuccess: #2163: 1: Success after linux: 23 commits new 50d65417af 129: onsuccess: #2164: 1: Success after binutils/gcc/linux/g [...] new a6c892fc5b 130: onsuccess: #2165: 1: Success after binutils/gcc/gdb: 32 [...] new c1aaa1a202 131: onsuccess: #2166: 1: Success after binutils/gcc/gdb: 12 [...] new 512c1e87b4 132: onsuccess: #2167: 1: Success after binutils/gcc/glibc/g [...] new c548940ec2 133: onsuccess: #2168: 1: Success after binutils/gcc/linux/g [...] new 9e576be037 134: onsuccess: #2169: 1: Success after binutils/gcc/gdb: 13 [...] new 67594c5078 135: onsuccess: #2170: 1: Success after gcc/linux/qemu: 63 commits new 8313847b31 136: onsuccess: #2171: 1: Success after binutils/gcc/gdb/qem [...] new 43264a1f7b 137: onsuccess: #2172: 1: Success after binutils/gcc/linux/g [...] new e37a7c3ffa 138: onsuccess: #2173: 1: Success after binutils/gcc/gdb: 5 commits new c984aed774 139: onsuccess: #2174: 1: Success after binutils/gcc/gdb: 13 [...] new 4a685d5495 140: onsuccess: #2175: 1: Success after binutils/gcc/linux/g [...] new 344f852c0e 141: onsuccess: #2176: 1: Success after binutils/gcc/gdb: 6 commits new 9003597a4d 142: onsuccess: #2177: 1: Success after gcc/glibc: 4 commits new 6d7118e39f 143: onsuccess: #2178: 1: Success after binutils/gcc/gdb/qem [...] new 54dc3b769e 144: onsuccess: #2179: 1: Success after binutils/gcc/linux/g [...] new ed2f59dfa6 145: onsuccess: #2180: 1: Success after binutils/gcc/linux/g [...] new f53f7276a8 146: onsuccess: #2181: 1: Success after binutils/glibc/gdb: [...] new 1555df62c5 147: onsuccess: #2182: 1: Success after binutils/gcc/gdb: 18 [...] new 4ca2fef580 148: onsuccess: #2183: 1: Success after gcc/linux/glibc: 64 commits new f1c36e269a 149: onsuccess: #2184: 1: Success after binutils/gcc/linux/g [...] new 3eea3b175c 150: onsuccess: #2185: 1: Success after gcc: 3 commits new 5544098cf2 151: onsuccess: #2186: 1: Success after gcc: 2 commits new d4eb458162 152: onsuccess: #2187: 1: Success after gcc/linux/glibc: 22 commits new 6ea8bedc6b 153: onsuccess: #2188: 1: Success after binutils/gcc/gdb: 3 commits new ae1cfcabd0 154: onsuccess: #2189: 1: Success after binutils/gcc/gdb: 18 [...] new 87a311925b 155: onsuccess: #2190: 1: Success after binutils/gcc/linux/g [...] new e0186f38ec 156: onsuccess: #2191: 1: Success after binutils/gcc/linux/g [...] new 71e2980184 157: onsuccess: #2192: 1: Success after binutils/gcc/gdb: 8 commits new baded9400d 158: onsuccess: #2193: 1: Success after binutils/gcc/glibc/g [...] new 69e7a39532 159: onsuccess: #2194: 1: Success after gcc/linux/glibc: 197 [...] new 73e56aa0aa 160: onsuccess: #2195: 1: Success after binutils/gcc/linux/g [...] new 785fa9f16b 161: onsuccess: #2196: 1: Success after binutils/gcc/linux/g [...] new 1394c43443 162: onsuccess: #2197: 1: Success after binutils/gcc/glibc/g [...] new fd87d7001b 163: onsuccess: #2198: 1: Success after binutils/gcc/linux/g [...] new 4a7e5e6f1b 164: onsuccess: #2199: 1: Success after binutils/gcc/linux/g [...] new b180d8567d 165: onsuccess: #2200: 1: Success after binutils/gdb: 8 commits new 4ac278687f 166: onsuccess: #2201: 1: Success after gcc/glibc/qemu: 40 commits new 8282eb35ac 167: onsuccess: #2202: 1: Success after gcc/linux/glibc/qemu [...] new 5aa70db960 168: onsuccess: #2203: 1: Success after binutils/gcc/glibc/g [...] new f873501e2d 169: onsuccess: #2204: 1: Success after binutils/gcc/glibc/g [...] new 3543f72128 170: onsuccess: #2205: 1: Success after binutils/gcc/glibc/g [...] new f83af64af2 171: onsuccess: #2206: 1: Success after binutils/gcc/linux/g [...] new 931deb5cff 172: onsuccess: #2207: 1: Success after binutils/gcc/linux/g [...] new b722228722 173: onsuccess: #2208: 1: Success after gcc: 10 commits new 5f95b7308d 174: onsuccess: #2209: 1: Success after binutils/gcc/gdb: 20 [...] new c38af139f9 175: onsuccess: #2210: 1: Success after binutils/gcc/linux/g [...] new e405efcf88 176: onsuccess: #2211: 1: Success after binutils/gcc/linux/g [...] new 202d8774df 177: onsuccess: #2212: 1: Success after binutils/gdb: 2 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 (19a1909b8b) \ 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 1708 -> 1716 bytes 02-prepare_abe/console.log.xz | Bin 2756 -> 2732 bytes 03-build_abe-binutils/console.log.xz | Bin 30960 -> 30876 bytes 04-build_abe-stage1/console.log.xz | Bin 74712 -> 73548 bytes 05-clean_sysroot/console.log.xz | Bin 328 -> 328 bytes 06-build_abe-linux/console.log.xz | Bin 9204 -> 9168 bytes 07-build_abe-glibc/console.log.xz | Bin 240712 -> 240512 bytes 08-build_abe-stage2/console.log.xz | Bin 204396 -> 204252 bytes 09-build_abe-gdb/console.log.xz | Bin 37424 -> 38004 bytes 10-build_abe-qemu/console.log.xz | Bin 32052 -> 32008 bytes 11-build_abe-dejagnu/console.log.xz | Bin 3884 -> 3876 bytes 12-build_abe-check_gcc/console.log.xz | Bin 3668 -> 3680 bytes 13-check_regression/console.log.xz | Bin 6212 -> 5692 bytes 13-check_regression/extra-bisect-params | 1 + 13-check_regression/fails.sum | 7 + 13-check_regression/mail-body.txt | 67 +- 13-check_regression/results.compare | 35 +- 13-check_regression/results.compare2 | 53 +- 13-check_regression/results.regressions | 41 + 14-update_baseline/console.log | 46 +- dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gdb_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 69 +- mail/mail-subject.txt | 2 +- manifest.sh | 26 +- results | 41 + sumfiles/g++.log.xz | Bin 3428376 -> 3413608 bytes sumfiles/g++.sum | 180 +- sumfiles/gcc.log.xz | Bin 3030436 -> 3031992 bytes sumfiles/gcc.sum | 5161 +++++++++++++++---------------- sumfiles/gfortran.log.xz | Bin 1032772 -> 1035388 bytes sumfiles/gfortran.sum | 46 +- sumfiles/libatomic.log.xz | Bin 2288 -> 2288 bytes sumfiles/libatomic.sum | 4 +- sumfiles/libgomp.log.xz | Bin 202468 -> 202480 bytes sumfiles/libgomp.sum | 16 +- sumfiles/libitm.log.xz | Bin 2696 -> 2696 bytes sumfiles/libitm.sum | 6 +- sumfiles/libstdc++.log.xz | Bin 430016 -> 428752 bytes sumfiles/libstdc++.sum | 14 +- 42 files changed, 2963 insertions(+), 2860 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_gcc_check_bootstrap/release-arm-check_bootstrap_lto updated (dd10f0ace9 -> 240eedf1bd)

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_bootstrap/release-arm-check_bootstrap_lto in repository toolchain/ci/base-artifacts. from dd10f0ace9 16: onsuccess: #131: 1: Success after binutils/gcc: 7 commits new 240eedf1bd 17: onsuccess: #132: 1: Success after binutils/gcc: 7 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 1680 -> 1700 bytes 02-prepare_abe/console.log.xz | Bin 2736 -> 2724 bytes 03-build_abe-binutils/console.log.xz | Bin 52000 -> 51844 bytes 04-build_abe-bootstrap_lto/console.log.xz | Bin 469296 -> 469676 bytes 05-build_abe-dejagnu/console.log.xz | Bin 3860 -> 3852 bytes 06-build_abe-check_bootstrap_lto/console.log.xz | Bin 2444 -> 2436 bytes 07-check_regression/console.log.xz | Bin 4628 -> 5064 bytes 07-check_regression/extra-bisect-params | 1 + 07-check_regression/fails.sum | 7 + 07-check_regression/mail-body.txt | 27 + 07-check_regression/results.compare | 26 +- 07-check_regression/results.compare2 | 40 +- 07-check_regression/results.regressions | 27 + dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- mail/mail-body.txt | 27 + manifest.sh | 18 +- results | 27 + sumfiles/g++.log.xz | Bin 2800120 -> 2822072 bytes sumfiles/g++.sum | 128 +- sumfiles/gcc.log.xz | Bin 2464344 -> 2500780 bytes sumfiles/gcc.sum | 4370 +++++++++++------------ sumfiles/gfortran.log.xz | Bin 946756 -> 934984 bytes sumfiles/gfortran.sum | 40 +- sumfiles/libatomic.log.xz | Bin 2312 -> 2304 bytes sumfiles/libatomic.sum | 4 +- sumfiles/libgomp.log.xz | Bin 206156 -> 206560 bytes sumfiles/libgomp.sum | 16 +- sumfiles/libitm.log.xz | Bin 2724 -> 2720 bytes sumfiles/libitm.sum | 6 +- sumfiles/libstdc++.log.xz | Bin 462100 -> 473004 bytes sumfiles/libstdc++.sum | 12 +- 33 files changed, 2463 insertions(+), 2319 deletions(-) create mode 100644 07-check_regression/extra-bisect-params create mode 100644 07-check_regression/fails.sum create mode 100644 07-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_gcc_check/master-arm updated (d90b3e00c2 -> b34f132ae5)

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 d90b3e00c2 176: onsuccess: #1796: 1: Success after binutils/gcc: 3 commits discards 5135aae741 175: onsuccess: #1795: 1: Success after binutils/gcc: 7 commits discards e61ce88b65 174: onsuccess: #1794: 1: Success after binutils/gcc: 17 commits discards 9ba80d5e45 173: onsuccess: #1793: 1: Success after gcc: 12 commits discards c6637849e0 172: onsuccess: #1792: 1: Success after binutils/gcc: 4 commits discards 62e1794f3d 171: onsuccess: #1791: 1: Success after binutils/gcc: 7 commits discards 4a824284ef 170: onsuccess: #1790: 1: Success after binutils/gcc: 9 commits discards 771923087a 169: onsuccess: #1789: 1: Success after binutils/gcc: 30 commits discards 1839463965 168: onsuccess: #1788: 1: Success after binutils/gcc: 9 commits discards df6dba7504 167: onsuccess: #1787: 1: Success after gcc: 8 commits discards 7a710ebfc5 166: onsuccess: #1786: 1: Success after gcc: 10 commits discards c6ed0937ba 165: onsuccess: #1785: 1: Success after binutils/gcc: 6 commits discards 5acf4ab954 164: onsuccess: #1784: 1: Success after binutils/gcc: 11 commits discards e81b9d08b4 163: onsuccess: #1783: 1: Success after binutils/gcc: 8 commits discards 7f6c2548de 162: onsuccess: #1782: 1: Success after binutils/gcc: 14 commits discards 8dc5308d16 161: onsuccess: #1781: 1: Success after binutils/gcc: 16 commits discards b5c0092301 160: onsuccess: #1780: 1: Success after binutils/gcc: 4 commits discards 41a1f804f4 159: onsuccess: #1779: 1: Success after gcc: 2 commits discards bc61943692 158: onsuccess: #1778: 1: Success after binutils/gcc: 30 commits discards c49d14180c 157: onsuccess: #1777: 1: Success after binutils/gcc: 3 commits discards 68d965219e 156: onsuccess: #1776: 1: Success after binutils/gcc: 4 commits discards 937e6e148a 155: onsuccess: #1775: 1: Success after binutils: 2 commits discards 06b291ca22 154: onsuccess: #1774: 1: Success after binutils/gcc: 20 commits discards 2b0108d054 153: onsuccess: #1773: 1: Success after gcc: 4 commits discards 8d223f4766 152: onsuccess: #1772: 1: Success after binutils/gcc: 2 commits discards 37fb39185f 151: onsuccess: #1771: 1: Success after basepoints/gcc-13-30 [...] discards 4c324ec616 150: onsuccess: #1770: 1: Success after basepoints/gcc-13-30 [...] discards 6ee61f7aa9 149: onsuccess: #1769: 1: Success after gcc: 3 commits discards f46b6a7bac 148: onsuccess: #1768: 1: Success after binutils/gcc: 18 commits discards 99e3ffa425 147: onsuccess: #1766: 1: Success after binutils/gcc: 16 commits discards 570101c49c 146: onsuccess: #1765: 1: Success after binutils/gcc: 11 commits discards fedc7529b1 145: onsuccess: #1764: 1: Success after binutils/gcc: 13 commits discards 230cd5d0fb 144: onsuccess: #1763: 1: Success after binutils/gcc: 16 commits discards e796d972e6 143: onsuccess: #1762: 1: Success after binutils/gcc: 12 commits discards a63cf9b421 142: onsuccess: #1761: 1: Success after gcc: 83 commits discards 45a325d248 141: onsuccess: #1759: 1: Success after gdb-12-branchpoint-2 [...] discards c87e1ba598 140: onsuccess: #1756: 1: Success after binutils: 3 commits discards 3d62c8c3b5 139: onsuccess: #1753: 1: Success after binutils: 5 commits discards e045233620 138: onsuccess: #1749: 1: Success after binutils: 5 commits discards 12bf124d59 137: onsuccess: #1746: 1: Success after gdb-12-branchpoint-2 [...] discards 73e1c434a3 136: onsuccess: #1742: 1: Success after gdb-12-branchpoint-2 [...] discards 0f847dc067 135: onsuccess: #1739: 1: Success after binutils: 4 commits discards 6babdd5f75 134: onsuccess: #1736: 1: Success after binutils: 3 commits discards 9a77bc911e 133: onsuccess: #1733: 1: Success after binutils: 3 commits discards e74c098101 132: onsuccess: #1731: 1: Success after binutils/gcc: 28 commits discards 857d28c7c2 131: onsuccess: #1730: 1: Success after binutils/gcc: 4 commits discards e90fabee32 130: onsuccess: #1729: 1: Success after gcc: 9 commits discards 418cdb45b8 129: onsuccess: #1728: 1: Success after basepoints/gcc-13-28 [...] discards e707b33b93 128: onsuccess: #1727: 1: Success after binutils/gcc: 2 commits discards 32452662a8 127: onsuccess: #1726: 1: Success after basepoints/gcc-13-28 [...] discards 1f90718fd9 126: onsuccess: #1725: 1: Success after binutils/gcc: 3 commits discards d96c939f03 125: onsuccess: #1724: 1: Success after binutils/gcc: 7 commits discards 6f30bedab0 124: onsuccess: #1723: 1: Success after binutils/gcc: 4 commits discards 5caa2e9d7d 123: onsuccess: #1722: 1: Success after binutils/gcc: 48 commits discards 104c163ed1 122: onsuccess: #1718: 1: Success after binutils/gcc: 25 commits discards 38858fb9a9 121: onsuccess: #1717: 1: Success after binutils/gcc: 17 commits discards a9bd906539 120: onsuccess: #1716: 1: Success after binutils/gcc: 4 commits discards 927ca46bcd 119: onsuccess: #1715: 1: Success after binutils: 4 commits discards 5b859cc12f 118: onsuccess: #1714: 1: Success after binutils/gcc: 13 commits discards 38feedcb28 117: onsuccess: #1713: 1: Success after binutils/gcc: 15 commits discards dd14216aca 116: onsuccess: #1712: 1: Success after binutils/gcc: 6 commits discards a9353efa95 115: onsuccess: #1711: 1: Success after binutils/gcc: 13 commits discards 33637620d6 114: onsuccess: #1710: 1: Success after binutils/gcc: 11 commits discards c1dfc9134e 113: onsuccess: #1709: 1: Success after binutils/gcc: 10 commits discards 4aa46f77e4 112: onsuccess: #1708: 1: Success after binutils/gcc: 4 commits discards 1642747b6e 111: onsuccess: #1707: 1: Success after binutils/gcc: 2 commits discards 0ff82bb951 110: onsuccess: #1706: 1: Success after binutils/gcc: 4 commits discards aeb0c28ace 109: onsuccess: #1705: 1: Success after basepoints/gcc-13-27 [...] discards a0f38b403c 108: onsuccess: #1704: 1: Success after binutils/gcc: 2 commits discards 4defcd1a68 107: onsuccess: #1703: 1: Success after basepoints/gcc-13-27 [...] discards 87af378b59 106: onsuccess: #1702: 1: Success after gcc: 4 commits discards d370ea5cab 105: onsuccess: #1701: 1: Success after binutils/gcc: 2 commits discards aacd77c830 104: onsuccess: #1700: 1: Success after gcc: 2 commits discards 9a0a51adf6 103: onsuccess: #1699: 1: Success after binutils/gcc: 2 commits discards 3241f2b9bd 102: onsuccess: #1698: 1: Success after binutils/gcc: 6 commits discards 90047282d0 101: onsuccess: #1697: 1: Success after binutils/gcc: 271 commits discards ff6fbf78e1 100: onsuccess: #1658: 1: Success after basepoints/gcc-13-25 [...] discards 30fdf37fe1 99: onsuccess: #1657: 1: Success after binutils/gcc: 8 commits discards 7e56d81cf3 98: onsuccess: #1656: 1: Success after binutils/gcc: 48 commits discards 902d04919e 97: onsuccess: #1655: 1: Success after binutils/gcc: 3 commits discards 98be224779 96: onsuccess: #1654: 1: Success after gcc: 5 commits discards b3aff31b48 95: onsuccess: #1653: 1: Success after gcc: 13 commits discards 1a8a94424f 94: onsuccess: #1652: 1: Success after binutils/gcc: 43 commits discards d86ad8b4d8 93: onsuccess: #1648: 1: Success after basepoints/gcc-13-239 [...] discards aa87d461ae 92: onsuccess: #1647: 1: Success after binutils/gcc: 2 commits discards 085781dc93 91: onsuccess: #1646: 1: Success after basepoints/gcc-13-239 [...] discards ae1d3a773e 90: onsuccess: #1645: 1: Success after gcc: 2 commits discards 54d0eecf58 89: onsuccess: #1644: 1: Success after basepoints/gcc-13-238 [...] discards 38a8985a23 88: onsuccess: 1: Success after binutils/gcc: 2 commits discards 50554c6be4 87: onsuccess: 1: Success after gcc: 6 commits discards a4933cd65e 86: onsuccess: 1: Success after binutils/gcc: 8 commits discards aa6aed3b18 85: onsuccess: 1: Success after binutils/gcc: 19 commits discards f7a99345f9 84: onsuccess: 1: Success after binutils/gcc: 2 commits discards 9e5bd6da1f 83: onsuccess: 1: Success after gcc: 14 commits discards 188b64488a 82: onsuccess: 1: Success after binutils/gcc: 9 commits discards efa9f464de 81: onsuccess: 1: Success after binutils/gcc: 8 commits discards 4041e54398 80: onsuccess: 1: Success after binutils/gcc: 8 commits discards 82e70f8633 79: onsuccess: 1: Success after binutils/gcc: 23 commits discards 85b2831756 78: onsuccess: 1: Success after binutils/gcc: 17 commits discards 8a4b91acd0 77: onsuccess: 1: Successful build after binutils/gcc: 10 commits discards 5d272699df 76: onsuccess: 1: Successful build after binutils/gcc: 3 commits new 9ca81f3be6 76: onsuccess: 1: Successful build after binutils/gcc: 3 commits new 27c1ed946f 77: onsuccess: 1: Successful build after binutils/gcc: 10 commits new 66982641ee 78: onsuccess: 1: Success after binutils/gcc: 17 commits new 6509825430 79: onsuccess: 1: Success after binutils/gcc: 23 commits new 542e20307f 80: onsuccess: 1: Success after binutils/gcc: 8 commits new 643a68c894 81: onsuccess: 1: Success after binutils/gcc: 8 commits new ad60764dcc 82: onsuccess: 1: Success after binutils/gcc: 9 commits new 013cbdd7ec 83: onsuccess: 1: Success after gcc: 14 commits new 3bfbe58072 84: onsuccess: 1: Success after binutils/gcc: 2 commits new 5ce11c2afb 85: onsuccess: 1: Success after binutils/gcc: 19 commits new 3d7412a57d 86: onsuccess: 1: Success after binutils/gcc: 8 commits new 45a6488e9b 87: onsuccess: 1: Success after gcc: 6 commits new 7b5b774a4d 88: onsuccess: 1: Success after binutils/gcc: 2 commits new 734152e0ef 89: onsuccess: #1644: 1: Success after basepoints/gcc-13-238 [...] new 9c2444d86d 90: onsuccess: #1645: 1: Success after gcc: 2 commits new 5a0d538688 91: onsuccess: #1646: 1: Success after basepoints/gcc-13-239 [...] new 13eaec032a 92: onsuccess: #1647: 1: Success after binutils/gcc: 2 commits new 1f7a32bece 93: onsuccess: #1648: 1: Success after basepoints/gcc-13-239 [...] new 0d9b518408 94: onsuccess: #1652: 1: Success after binutils/gcc: 43 commits new 2f6df97c54 95: onsuccess: #1653: 1: Success after gcc: 13 commits new 69c78a7bbc 96: onsuccess: #1654: 1: Success after gcc: 5 commits new 0fa16cb24a 97: onsuccess: #1655: 1: Success after binutils/gcc: 3 commits new 0c8b37a3ae 98: onsuccess: #1656: 1: Success after binutils/gcc: 48 commits new 72efb5b01d 99: onsuccess: #1657: 1: Success after binutils/gcc: 8 commits new 3572b5ff7a 100: onsuccess: #1658: 1: Success after basepoints/gcc-13-25 [...] new ce04f08f3f 101: onsuccess: #1697: 1: Success after binutils/gcc: 271 commits new 50e2cf2432 102: onsuccess: #1698: 1: Success after binutils/gcc: 6 commits new cc1e44d551 103: onsuccess: #1699: 1: Success after binutils/gcc: 2 commits new 7fb342bce8 104: onsuccess: #1700: 1: Success after gcc: 2 commits new 59017e5131 105: onsuccess: #1701: 1: Success after binutils/gcc: 2 commits new e57c0d0978 106: onsuccess: #1702: 1: Success after gcc: 4 commits new b596dc5ff0 107: onsuccess: #1703: 1: Success after basepoints/gcc-13-27 [...] new e2c59bac80 108: onsuccess: #1704: 1: Success after binutils/gcc: 2 commits new 5407e0357a 109: onsuccess: #1705: 1: Success after basepoints/gcc-13-27 [...] new 479e0056a0 110: onsuccess: #1706: 1: Success after binutils/gcc: 4 commits new 6dfcab141a 111: onsuccess: #1707: 1: Success after binutils/gcc: 2 commits new 146864d343 112: onsuccess: #1708: 1: Success after binutils/gcc: 4 commits new a5aab03248 113: onsuccess: #1709: 1: Success after binutils/gcc: 10 commits new 3b7b662d0e 114: onsuccess: #1710: 1: Success after binutils/gcc: 11 commits new a7d117102a 115: onsuccess: #1711: 1: Success after binutils/gcc: 13 commits new 12478e34aa 116: onsuccess: #1712: 1: Success after binutils/gcc: 6 commits new 650b037588 117: onsuccess: #1713: 1: Success after binutils/gcc: 15 commits new b413ae5171 118: onsuccess: #1714: 1: Success after binutils/gcc: 13 commits new 8fed36ca60 119: onsuccess: #1715: 1: Success after binutils: 4 commits new 6cd45ecf9b 120: onsuccess: #1716: 1: Success after binutils/gcc: 4 commits new 531e23a9e1 121: onsuccess: #1717: 1: Success after binutils/gcc: 17 commits new edb3cf1214 122: onsuccess: #1718: 1: Success after binutils/gcc: 25 commits new cffc1cb138 123: onsuccess: #1722: 1: Success after binutils/gcc: 48 commits new 4ff456b6ad 124: onsuccess: #1723: 1: Success after binutils/gcc: 4 commits new c621805887 125: onsuccess: #1724: 1: Success after binutils/gcc: 7 commits new 768807d1ff 126: onsuccess: #1725: 1: Success after binutils/gcc: 3 commits new a1077bdbcd 127: onsuccess: #1726: 1: Success after basepoints/gcc-13-28 [...] new 453876af4f 128: onsuccess: #1727: 1: Success after binutils/gcc: 2 commits new dcd833ca71 129: onsuccess: #1728: 1: Success after basepoints/gcc-13-28 [...] new bc483e4b8b 130: onsuccess: #1729: 1: Success after gcc: 9 commits new 47b25e986c 131: onsuccess: #1730: 1: Success after binutils/gcc: 4 commits new c9373a0081 132: onsuccess: #1731: 1: Success after binutils/gcc: 28 commits new fc4cc9b1ae 133: onsuccess: #1733: 1: Success after binutils: 3 commits new bece777f92 134: onsuccess: #1736: 1: Success after binutils: 3 commits new 570d992660 135: onsuccess: #1739: 1: Success after binutils: 4 commits new f596d9c4c9 136: onsuccess: #1742: 1: Success after gdb-12-branchpoint-2 [...] new b5a1ea37ed 137: onsuccess: #1746: 1: Success after gdb-12-branchpoint-2 [...] new 2440e2db9e 138: onsuccess: #1749: 1: Success after binutils: 5 commits new ba883f7d1f 139: onsuccess: #1753: 1: Success after binutils: 5 commits new cb88e9bf29 140: onsuccess: #1756: 1: Success after binutils: 3 commits new 4003870776 141: onsuccess: #1759: 1: Success after gdb-12-branchpoint-2 [...] new 511de435b5 142: onsuccess: #1761: 1: Success after gcc: 83 commits new 784a74f7c8 143: onsuccess: #1762: 1: Success after binutils/gcc: 12 commits new d2913f3ce0 144: onsuccess: #1763: 1: Success after binutils/gcc: 16 commits new 25242088d8 145: onsuccess: #1764: 1: Success after binutils/gcc: 13 commits new d5d48ca1c2 146: onsuccess: #1765: 1: Success after binutils/gcc: 11 commits new 1f78edd4a9 147: onsuccess: #1766: 1: Success after binutils/gcc: 16 commits new 9c035f8a58 148: onsuccess: #1768: 1: Success after binutils/gcc: 18 commits new 2bb5db5ac2 149: onsuccess: #1769: 1: Success after gcc: 3 commits new 4f9892ba3b 150: onsuccess: #1770: 1: Success after basepoints/gcc-13-30 [...] new e11c13a177 151: onsuccess: #1771: 1: Success after basepoints/gcc-13-30 [...] new e37afeb7f8 152: onsuccess: #1772: 1: Success after binutils/gcc: 2 commits new bbf9d1ad61 153: onsuccess: #1773: 1: Success after gcc: 4 commits new f928baa460 154: onsuccess: #1774: 1: Success after binutils/gcc: 20 commits new babc2ae8d0 155: onsuccess: #1775: 1: Success after binutils: 2 commits new eeb1790cbd 156: onsuccess: #1776: 1: Success after binutils/gcc: 4 commits new d3b4a9c417 157: onsuccess: #1777: 1: Success after binutils/gcc: 3 commits new 75103d3dae 158: onsuccess: #1778: 1: Success after binutils/gcc: 30 commits new f12a6d6e33 159: onsuccess: #1779: 1: Success after gcc: 2 commits new 38a1af1bb3 160: onsuccess: #1780: 1: Success after binutils/gcc: 4 commits new 493418ab1c 161: onsuccess: #1781: 1: Success after binutils/gcc: 16 commits new 1d115e054a 162: onsuccess: #1782: 1: Success after binutils/gcc: 14 commits new d960c7b8ad 163: onsuccess: #1783: 1: Success after binutils/gcc: 8 commits new 0fe8705ea3 164: onsuccess: #1784: 1: Success after binutils/gcc: 11 commits new d0c700b180 165: onsuccess: #1785: 1: Success after binutils/gcc: 6 commits new a6efbc9872 166: onsuccess: #1786: 1: Success after gcc: 10 commits new 1be4d9b9d6 167: onsuccess: #1787: 1: Success after gcc: 8 commits new 0008129acd 168: onsuccess: #1788: 1: Success after binutils/gcc: 9 commits new c6ccf17808 169: onsuccess: #1789: 1: Success after binutils/gcc: 30 commits new c11c25df2a 170: onsuccess: #1790: 1: Success after binutils/gcc: 9 commits new cb58e4e565 171: onsuccess: #1791: 1: Success after binutils/gcc: 7 commits new 2d051eb778 172: onsuccess: #1792: 1: Success after binutils/gcc: 4 commits new adb0493f2d 173: onsuccess: #1793: 1: Success after gcc: 12 commits new 26838663e8 174: onsuccess: #1794: 1: Success after binutils/gcc: 17 commits new 7db10e4b24 175: onsuccess: #1795: 1: Success after binutils/gcc: 7 commits new 6d25fa0401 176: onsuccess: #1796: 1: Success after binutils/gcc: 3 commits new b34f132ae5 177: onsuccess: #1797: 1: Success after gdb-12-branchpoint-2 [...] 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 (d90b3e00c2) \ N -- N -- N refs/heads/linaro-local/ci/tcwg_gcc_check/master-arm (b3 [...] 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 1664 -> 1684 bytes 02-prepare_abe/console.log.xz | Bin 2732 -> 2736 bytes 03-build_abe-binutils/console.log.xz | Bin 52708 -> 50768 bytes 04-build_abe-gcc/console.log.xz | Bin 238068 -> 235948 bytes 05-build_abe-dejagnu/console.log.xz | Bin 3856 -> 3832 bytes 06-build_abe-check_gcc/console.log.xz | Bin 3392 -> 3488 bytes 07-check_regression/console.log.xz | Bin 4544 -> 4404 bytes 07-check_regression/results.compare | 16 +- 07-check_regression/results.compare2 | 6 +- 08-update_baseline/console.log | 66 +- dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 2 +- mail/mail-subject.txt | 2 +- manifest.sh | 14 +- sumfiles/g++.log.xz | Bin 2774268 -> 2799780 bytes sumfiles/g++.sum | 140 +- sumfiles/gcc.log.xz | Bin 2380644 -> 2365036 bytes sumfiles/gcc.sum | 4364 ++++++++++++++++----------------- sumfiles/gfortran.log.xz | Bin 911692 -> 909252 bytes sumfiles/gfortran.sum | 40 +- sumfiles/libatomic.log.xz | Bin 2172 -> 2160 bytes sumfiles/libatomic.sum | 4 +- sumfiles/libgomp.log.xz | Bin 204704 -> 204728 bytes sumfiles/libgomp.sum | 16 +- sumfiles/libitm.log.xz | Bin 2544 -> 2544 bytes sumfiles/libitm.sum | 6 +- sumfiles/libstdc++.log.xz | Bin 468404 -> 470580 bytes sumfiles/libstdc++.sum | 10 +- 30 files changed, 2346 insertions(+), 2346 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_kernel/llvm-master-arm-norov-allmodconfig updated (14ceba9ed3 -> 71353582ee)

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-norov-allmodconfig in repository toolchain/ci/base-artifacts. from 14ceba9ed3 17: onsuccess: #64: 23021: Success after binutils/llvm/linux [...] new 71353582ee 18: onsuccess: #65: 23021: 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 1700 -> 1708 bytes 02-prepare_abe/console.log.xz | Bin 2756 -> 2744 bytes 03-build_abe-binutils/console.log.xz | Bin 30128 -> 31196 bytes 04-build_kernel_llvm/console.log.xz | Bin 65280 -> 64368 bytes 05-build_abe-qemu/console.log.xz | Bin 31704 -> 31816 bytes 06-build_linux/console.log.xz | Bin 5012 -> 5040 bytes 08-check_regression/console.log.xz | Bin 4748 -> 4468 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 ++++++++++++++++---------------- 17 files changed, 28 insertions(+), 28 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_O1 updated (86324ba198 -> 36f1570f0a)

by git＠git.linaro.org

2 years, 1 month

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_kernel/llvm-master-aarch64-norov-allyesconfig updated (2399e6c69d -> 844e9afcdf)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. tcwg-buildslave pushed a change to branch linaro-local/ci/tcwg_kernel/llvm-master-aarch64-norov-allyesconfig in repository toolchain/ci/base-artifacts. from 2399e6c69d 20: onsuccess: #62: 21247: Success after llvmorg-16-init-657 [...] new 844e9afcdf 21: onsuccess: #63: 21254: 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 -> 1788 bytes 02-prepare_abe/console.log.xz | Bin 2756 -> 2744 bytes 03-build_abe-binutils/console.log.xz | Bin 30744 -> 30220 bytes 04-build_kernel_llvm/console.log.xz | Bin 65908 -> 66512 bytes 05-build_abe-qemu/console.log.xz | Bin 32156 -> 32052 bytes 06-build_linux/console.log.xz | Bin 9852 -> 3760 bytes 08-check_regression/console.log.xz | Bin 2760 -> 4436 bytes 08-check_regression/mail-body.txt | 13 +------------ 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 | 15 ++------------- mail/mail-subject.txt | 2 +- manifest.sh | 29 ++++++++++++++++------------- results | 2 +- 19 files changed, 31 insertions(+), 50 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