Tcwg-commits December 2022

tcwg-commits@lists.linaro.org

5 participants
4659 discussions

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_gnu_cross_check_gcc/master-aarch64 updated (3920d93326bc -> 207e17e93701)

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 3920d93326bc 233: onsuccess: #2481: 1: Success after binutils/gcc/gdb/q [...] discards e0a361875528 232: onsuccess: #2480: 1: Success after binutils/gcc/linux [...] discards 1684c468e945 231: onsuccess: #2479: 1: Success after binutils/gcc/gdb/q [...] discards 5281c09e6ba5 230: onsuccess: #2477: 1: Success after binutils/gcc/linux [...] discards 6fea4d022fab 229: onsuccess: #2476: 1: Success after binutils/gcc/linux [...] discards 2c304c6a5a39 228: onsuccess: #2475: 1: Success after binutils/gcc/gdb/q [...] discards 20ffee17a251 227: onsuccess: #2474: 1: Success after gcc: 2 commits discards bed3f20976a2 226: onsuccess: #2473: 1: Success after binutils/gcc/linux [...] discards 0305867565f7 225: onsuccess: #2472: 1: Success after gcc/linux: 532 commits discards ce5b27a1413a 224: onsuccess: #2471: 1: Success after binutils/gcc/gdb: [...] discards 304c145903f7 223: onsuccess: #2470: 1: Success after binutils/gcc/linux [...] discards 5a8c3974c1d1 222: onsuccess: #2469: 1: Success after binutils/gcc/linux [...] discards 6da52110e7dd 221: onsuccess: #2467: 1: Success after binutils: 3 commits discards 507d5b536199 220: onsuccess: #2465: 1: Success after linux: 572 commits discards 8654ca1e6d27 219: onsuccess: #2463: 1: Success after binutils: 3 commits discards 085db6b0e7c3 218: onsuccess: #2461: 1: Success after linux: 916 commits discards e28ccc238a05 217: onsuccess: #2459: 1: Success after binutils: 3 commits discards 2b51e21bc0c5 216: onsuccess: #2457: 1: Success after linux: 1736 commits discards e3cd8b02d8ae 215: onsuccess: #2455: 1: Success after binutils: 3 commits discards 0faf97a2de06 214: onsuccess: #2453: 1: Success after binutils/gcc/glibc [...] discards 1f9e29294936 213: onsuccess: #2452: 1: Success after binutils/gcc/gdb: [...] discards 828f6ccd7c31 212: onsuccess: #2451: 1: Success after binutils/gcc/linux [...] discards 60657d20013c 211: onsuccess: #2450: 1: Success after gcc/linux: 7 commits discards 145cf55cfe59 210: onsuccess: #2449: 1: Success after binutils/gcc/gdb: [...] discards ce93923de972 209: onsuccess: #2448: 1: Success after binutils/gcc/linux [...] discards 2b321bfe0fb1 208: onsuccess: #2447: 1: Success after binutils/gcc/gdb: [...] discards 686bb691496d 207: onsuccess: #2446: 1: Success after binutils/gcc/linux [...] discards f54f9db3948d 206: onsuccess: #2445: 1: Success after binutils/gcc/glibc [...] discards 39f22d8afa23 205: onsuccess: #2444: 1: Success after binutils/gcc/linux [...] discards dc727fb608d8 204: onsuccess: #2435: 1: Success after linux: 3 commits discards de57565ba26c 203: onsuccess: #2433: 1: Success after binutils: 27 commits discards 1ac1d7887636 202: onsuccess: #2431: 1: Success after linux: 944 commits discards d3e67fdf3afd 201: onsuccess: #2430: 1: Success after glibc: 26 commits discards e106017ae43a 200: onsuccess: #2427: 1: Success after binutils: 274 commits discards 0fa2e500a2db 199: onsuccess: #2363: 1: Success after binutils/gcc/linux [...] discards a40edc298082 198: onsuccess: #2360: 1: Success after binutils/gcc/linux [...] discards ef70baed61f1 197: onsuccess: #2348: 1: Success after linux: 190 commits discards da9d76830a7d 196: onsuccess: #2342: 1: Success after binutils/gcc/gdb: [...] discards 1bbee6225568 195: onsuccess: #2341: 1: Success after binutils/gcc/linux [...] discards 8d1fa7deaf20 194: onsuccess: #2340: 1: Success after binutils/gcc/linux [...] discards 62c3a5f70495 193: onsuccess: #2339: 1: Success after binutils/gcc/glibc [...] discards 4cd6828bcde8 192: onsuccess: #2338: 1: Success after binutils/gcc/linux [...] discards 6f169e1029df 191: onsuccess: #2331: 1: Success after gcc/qemu: 90 commits discards 0b9688854c53 190: onsuccess: #2330: 1: Success after binutils/gcc/linux [...] discards c08aa138e38b 189: onsuccess: #2299: 1: Success after binutils/gcc/linux [...] discards e86e9b3ffcf3 188: onsuccess: #2295: 1: Success after binutils/gcc/linux [...] discards 6deb4aa4a9f0 187: onsuccess: #2294: 1: Success after binutils/gcc/linux [...] discards 39f8d697c5cd 186: onsuccess: #2291: 1: Success after binutils/gcc/linux [...] discards 2169f8321ca9 185: onsuccess: #2290: 1: Success after binutils/gcc/linux [...] discards 9b2f421da0d9 184: onsuccess: #2288: 1: Success after binutils/gcc/linux [...] discards 8304d271f33b 183: onsuccess: #2270: 1: Success after binutils/gcc/linux [...] discards fa60c2c23125 182: onsuccess: #2247: 1: Success after binutils/gcc/linux [...] discards 9510ea580f3c 181: onsuccess: #2239: 1: Success after binutils/gcc/linux [...] discards d2943be5a315 180: onsuccess: #2232: 1: Success after binutils/gcc/glibc [...] discards bfe690db4bd1 179: onsuccess: #2230: 1: Success after binutils/gcc/linux [...] discards 949a7de5e3c9 178: onsuccess: #2217: 1: Success after binutils/gcc/linux [...] discards 696b516fe725 177: onsuccess: #2212: 1: Success after binutils/gdb: 2 commits discards 31a970f7021e 176: onsuccess: #2211: 1: Success after binutils/gcc/linux [...] discards ce01188d880d 175: onsuccess: #2210: 1: Success after binutils/gcc/linux [...] discards 752cd56036cc 174: onsuccess: #2209: 1: Success after binutils/gcc/gdb: [...] discards 5d9323ab7585 173: onsuccess: #2208: 1: Success after gcc: 10 commits discards 607094718fcc 172: onsuccess: #2207: 1: Success after binutils/gcc/linux [...] discards c663576d1a86 171: onsuccess: #2206: 1: Success after binutils/gcc/linux [...] discards 4296b82838fb 170: onsuccess: #2205: 1: Success after binutils/gcc/glibc [...] discards ec9b5311a207 169: onsuccess: #2204: 1: Success after binutils/gcc/glibc [...] discards fade38242c97 168: onsuccess: #2203: 1: Success after binutils/gcc/glibc [...] discards caa3fb6eea5f 167: onsuccess: #2202: 1: Success after gcc/linux/glibc/qe [...] discards e8b72ce02f30 166: onsuccess: #2201: 1: Success after gcc/glibc/qemu: 40 [...] discards 5df8305c275b 165: onsuccess: #2200: 1: Success after binutils/gdb: 8 commits discards 9dc66131afb0 164: onsuccess: #2199: 1: Success after binutils/gcc/linux [...] discards b813011f8503 163: onsuccess: #2198: 1: Success after binutils/gcc/linux [...] discards 4f5f74b0759b 162: onsuccess: #2197: 1: Success after binutils/gcc/glibc [...] discards c28a2637c4af 161: onsuccess: #2196: 1: Success after binutils/gcc/linux [...] discards 7cad5c155e79 160: onsuccess: #2195: 1: Success after binutils/gcc/linux [...] discards 2913672251e8 159: onsuccess: #2194: 1: Success after gcc/linux/glibc: 1 [...] discards dedbecaf689c 158: onsuccess: #2193: 1: Success after binutils/gcc/glibc [...] discards 5ba0e6b72bf5 157: onsuccess: #2192: 1: Success after binutils/gcc/gdb: [...] discards 6cb928b461bb 156: onsuccess: #2191: 1: Success after binutils/gcc/linux [...] discards 3c392eb74c49 155: onsuccess: #2190: 1: Success after binutils/gcc/linux [...] discards b971614861b7 154: onsuccess: #2189: 1: Success after binutils/gcc/gdb: [...] discards 56808cb84ce7 153: onsuccess: #2188: 1: Success after binutils/gcc/gdb: [...] discards 1194076a6d3a 152: onsuccess: #2187: 1: Success after gcc/linux/glibc: 2 [...] discards 99c2581cabda 151: onsuccess: #2186: 1: Success after gcc: 2 commits discards 45d2f0722112 150: onsuccess: #2185: 1: Success after gcc: 3 commits discards 14e959d416d3 149: onsuccess: #2184: 1: Success after binutils/gcc/linux [...] discards 9846a92d6e7f 148: onsuccess: #2183: 1: Success after gcc/linux/glibc: 6 [...] discards 259ff32a2ab9 147: onsuccess: #2182: 1: Success after binutils/gcc/gdb: [...] discards d5b77105b37f 146: onsuccess: #2181: 1: Success after binutils/glibc/gdb [...] discards 50a8d29db5c3 145: onsuccess: #2180: 1: Success after binutils/gcc/linux [...] discards 0230b7d5bf84 144: onsuccess: #2179: 1: Success after binutils/gcc/linux [...] discards 8c5d6efdfd6e 143: onsuccess: #2178: 1: Success after binutils/gcc/gdb/q [...] discards 7a4a6160c992 142: onsuccess: #2177: 1: Success after gcc/glibc: 4 commits discards 4a00c3d79373 141: onsuccess: #2176: 1: Success after binutils/gcc/gdb: [...] discards 3020d7b85504 140: onsuccess: #2175: 1: Success after binutils/gcc/linux [...] discards 2a52af7c6f4e 139: onsuccess: #2174: 1: Success after binutils/gcc/gdb: [...] discards 15167ffdeabe 138: onsuccess: #2173: 1: Success after binutils/gcc/gdb: [...] discards b18f91b88867 137: onsuccess: #2172: 1: Success after binutils/gcc/linux [...] discards 018483b13845 136: onsuccess: #2171: 1: Success after binutils/gcc/gdb/q [...] discards d82fca74bf88 135: onsuccess: #2170: 1: Success after gcc/linux/qemu: 63 [...] discards 891708a7167a 134: onsuccess: #2169: 1: Success after binutils/gcc/gdb: [...] discards 8469396760d9 133: onsuccess: #2168: 1: Success after binutils/gcc/linux [...] new bb5c785a25f4 133: onsuccess: #2168: 1: Success after binutils/gcc/linux [...] new c738c8f40945 134: onsuccess: #2169: 1: Success after binutils/gcc/gdb: [...] new 898747d9a0b5 135: onsuccess: #2170: 1: Success after gcc/linux/qemu: 63 [...] new 0ce48efebe6c 136: onsuccess: #2171: 1: Success after binutils/gcc/gdb/q [...] new c89ccef1c16a 137: onsuccess: #2172: 1: Success after binutils/gcc/linux [...] new 8248c921eac6 138: onsuccess: #2173: 1: Success after binutils/gcc/gdb: [...] new 926b7f33801a 139: onsuccess: #2174: 1: Success after binutils/gcc/gdb: [...] new 92583adf52a5 140: onsuccess: #2175: 1: Success after binutils/gcc/linux [...] new 0fe8a1ee2767 141: onsuccess: #2176: 1: Success after binutils/gcc/gdb: [...] new 77d2c3bce187 142: onsuccess: #2177: 1: Success after gcc/glibc: 4 commits new 4fe6b7bcc18f 143: onsuccess: #2178: 1: Success after binutils/gcc/gdb/q [...] new db4f7698d6a4 144: onsuccess: #2179: 1: Success after binutils/gcc/linux [...] new 677cb66040c2 145: onsuccess: #2180: 1: Success after binutils/gcc/linux [...] new 4a070f4f3a27 146: onsuccess: #2181: 1: Success after binutils/glibc/gdb [...] new d633bb54de86 147: onsuccess: #2182: 1: Success after binutils/gcc/gdb: [...] new f5b3ad9921ea 148: onsuccess: #2183: 1: Success after gcc/linux/glibc: 6 [...] new dfb7bd29e10b 149: onsuccess: #2184: 1: Success after binutils/gcc/linux [...] new 1e279c6d3563 150: onsuccess: #2185: 1: Success after gcc: 3 commits new 0f2caf2555fa 151: onsuccess: #2186: 1: Success after gcc: 2 commits new 1f35ef60a200 152: onsuccess: #2187: 1: Success after gcc/linux/glibc: 2 [...] new 882965d303a5 153: onsuccess: #2188: 1: Success after binutils/gcc/gdb: [...] new 1ed1429afc19 154: onsuccess: #2189: 1: Success after binutils/gcc/gdb: [...] new 0209a1e2fb26 155: onsuccess: #2190: 1: Success after binutils/gcc/linux [...] new fb03d2d0023d 156: onsuccess: #2191: 1: Success after binutils/gcc/linux [...] new eeddc3c034dd 157: onsuccess: #2192: 1: Success after binutils/gcc/gdb: [...] new 2d363c30767d 158: onsuccess: #2193: 1: Success after binutils/gcc/glibc [...] new 72a286da56f1 159: onsuccess: #2194: 1: Success after gcc/linux/glibc: 1 [...] new 62c6ea3f2d5d 160: onsuccess: #2195: 1: Success after binutils/gcc/linux [...] new df4c7b3d089a 161: onsuccess: #2196: 1: Success after binutils/gcc/linux [...] new a2fab2bfec9e 162: onsuccess: #2197: 1: Success after binutils/gcc/glibc [...] new 2cb868594fbd 163: onsuccess: #2198: 1: Success after binutils/gcc/linux [...] new 431d89b0f4dd 164: onsuccess: #2199: 1: Success after binutils/gcc/linux [...] new c4153ea97469 165: onsuccess: #2200: 1: Success after binutils/gdb: 8 commits new 234468194013 166: onsuccess: #2201: 1: Success after gcc/glibc/qemu: 40 [...] new 9f0aa7ec89f0 167: onsuccess: #2202: 1: Success after gcc/linux/glibc/qe [...] new 3daa7ffead2e 168: onsuccess: #2203: 1: Success after binutils/gcc/glibc [...] new 3104956bfdfe 169: onsuccess: #2204: 1: Success after binutils/gcc/glibc [...] new 2fb6174fbb60 170: onsuccess: #2205: 1: Success after binutils/gcc/glibc [...] new 8d4890da199a 171: onsuccess: #2206: 1: Success after binutils/gcc/linux [...] new b655daf71db5 172: onsuccess: #2207: 1: Success after binutils/gcc/linux [...] new 197593ec44be 173: onsuccess: #2208: 1: Success after gcc: 10 commits new 9a114d9ef684 174: onsuccess: #2209: 1: Success after binutils/gcc/gdb: [...] new 7e13ba5ae199 175: onsuccess: #2210: 1: Success after binutils/gcc/linux [...] new a71cb8c54857 176: onsuccess: #2211: 1: Success after binutils/gcc/linux [...] new 1451c1d1b445 177: onsuccess: #2212: 1: Success after binutils/gdb: 2 commits new 93f3e3ad9c9b 178: onsuccess: #2217: 1: Success after binutils/gcc/linux [...] new e38db73e939a 179: onsuccess: #2230: 1: Success after binutils/gcc/linux [...] new 4680c7ce8bec 180: onsuccess: #2232: 1: Success after binutils/gcc/glibc [...] new 552ce1429939 181: onsuccess: #2239: 1: Success after binutils/gcc/linux [...] new 5b235b1e73fc 182: onsuccess: #2247: 1: Success after binutils/gcc/linux [...] new 2628d7a18947 183: onsuccess: #2270: 1: Success after binutils/gcc/linux [...] new 3cc5dbf3f68c 184: onsuccess: #2288: 1: Success after binutils/gcc/linux [...] new d7045841e9e5 185: onsuccess: #2290: 1: Success after binutils/gcc/linux [...] new b363c8b4e45f 186: onsuccess: #2291: 1: Success after binutils/gcc/linux [...] new 3be796bcf963 187: onsuccess: #2294: 1: Success after binutils/gcc/linux [...] new f9241927099c 188: onsuccess: #2295: 1: Success after binutils/gcc/linux [...] new 42de3670c615 189: onsuccess: #2299: 1: Success after binutils/gcc/linux [...] new 714e78af139a 190: onsuccess: #2330: 1: Success after binutils/gcc/linux [...] new db20c4f374fd 191: onsuccess: #2331: 1: Success after gcc/qemu: 90 commits new e6b0c1f889a9 192: onsuccess: #2338: 1: Success after binutils/gcc/linux [...] new 9aba0821cf19 193: onsuccess: #2339: 1: Success after binutils/gcc/glibc [...] new 7be37e225cad 194: onsuccess: #2340: 1: Success after binutils/gcc/linux [...] new 221f27d599c8 195: onsuccess: #2341: 1: Success after binutils/gcc/linux [...] new e3633db1d663 196: onsuccess: #2342: 1: Success after binutils/gcc/gdb: [...] new 1ce4b74a1a20 197: onsuccess: #2348: 1: Success after linux: 190 commits new a707b5b2ae3c 198: onsuccess: #2360: 1: Success after binutils/gcc/linux [...] new d6ba0909861c 199: onsuccess: #2363: 1: Success after binutils/gcc/linux [...] new d2b5e7e4501a 200: onsuccess: #2427: 1: Success after binutils: 274 commits new fde600b0eb8c 201: onsuccess: #2430: 1: Success after glibc: 26 commits new c2dcbd65da99 202: onsuccess: #2431: 1: Success after linux: 944 commits new 8d0f1da0397a 203: onsuccess: #2433: 1: Success after binutils: 27 commits new 1a523d1fae6a 204: onsuccess: #2435: 1: Success after linux: 3 commits new 467ee76be507 205: onsuccess: #2444: 1: Success after binutils/gcc/linux [...] new 5c8961ee4015 206: onsuccess: #2445: 1: Success after binutils/gcc/glibc [...] new 7e8c5a4a8678 207: onsuccess: #2446: 1: Success after binutils/gcc/linux [...] new 7c4dc103c2c9 208: onsuccess: #2447: 1: Success after binutils/gcc/gdb: [...] new 32dc6edf67a5 209: onsuccess: #2448: 1: Success after binutils/gcc/linux [...] new b5fc36c5951a 210: onsuccess: #2449: 1: Success after binutils/gcc/gdb: [...] new f959826c2923 211: onsuccess: #2450: 1: Success after gcc/linux: 7 commits new 5b6f2c84dcde 212: onsuccess: #2451: 1: Success after binutils/gcc/linux [...] new cf1501437b89 213: onsuccess: #2452: 1: Success after binutils/gcc/gdb: [...] new 9bebbc9ada98 214: onsuccess: #2453: 1: Success after binutils/gcc/glibc [...] new adc792cbae3a 215: onsuccess: #2455: 1: Success after binutils: 3 commits new b82efa7cec77 216: onsuccess: #2457: 1: Success after linux: 1736 commits new bf46f5935291 217: onsuccess: #2459: 1: Success after binutils: 3 commits new 5ec2b3383648 218: onsuccess: #2461: 1: Success after linux: 916 commits new 0fbe37ce36ec 219: onsuccess: #2463: 1: Success after binutils: 3 commits new 4f8b690df6b6 220: onsuccess: #2465: 1: Success after linux: 572 commits new a9da820af5ae 221: onsuccess: #2467: 1: Success after binutils: 3 commits new b454c414630d 222: onsuccess: #2469: 1: Success after binutils/gcc/linux [...] new 789686712d0e 223: onsuccess: #2470: 1: Success after binutils/gcc/linux [...] new ef6715bf9063 224: onsuccess: #2471: 1: Success after binutils/gcc/gdb: [...] new 7e665a1bd813 225: onsuccess: #2472: 1: Success after gcc/linux: 532 commits new 9126899afc71 226: onsuccess: #2473: 1: Success after binutils/gcc/linux [...] new 6ea41f5872ba 227: onsuccess: #2474: 1: Success after gcc: 2 commits new 0f620649397c 228: onsuccess: #2475: 1: Success after binutils/gcc/gdb/q [...] new 1edde54cf84e 229: onsuccess: #2476: 1: Success after binutils/gcc/linux [...] new 26c7c7ffb401 230: onsuccess: #2477: 1: Success after binutils/gcc/linux [...] new 8cb36cbf3524 231: onsuccess: #2479: 1: Success after binutils/gcc/gdb/q [...] new 75e5b40fa045 232: onsuccess: #2480: 1: Success after binutils/gcc/linux [...] new ad87fb95b4b6 233: onsuccess: #2481: 1: Success after binutils/gcc/gdb/q [...] new 207e17e93701 234: onsuccess: #2482: 1: Success after binutils/gdb: 18 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 (3920d93326bc) \ 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 1760 -> 1752 bytes 02-prepare_abe/console.log.xz | Bin 2800 -> 2776 bytes 03-build_abe-binutils/console.log.xz | Bin 31960 -> 32948 bytes 04-build_abe-stage1/console.log.xz | Bin 73492 -> 73124 bytes 05-clean_sysroot/console.log.xz | Bin 328 -> 328 bytes 06-build_abe-linux/console.log.xz | Bin 8696 -> 8696 bytes 07-build_abe-glibc/console.log.xz | Bin 244712 -> 243424 bytes 08-build_abe-stage2/console.log.xz | Bin 205812 -> 204344 bytes 09-build_abe-gdb/console.log.xz | Bin 39120 -> 39640 bytes 10-build_abe-qemu/console.log.xz | Bin 32136 -> 31444 bytes 11-build_abe-dejagnu/console.log.xz | Bin 3908 -> 3912 bytes 12-build_abe-check_gcc/console.log.xz | Bin 2948 -> 2868 bytes 13-check_regression/console.log.xz | Bin 13184 -> 10684 bytes 13-check_regression/extra-bisect-params | 2 +- 13-check_regression/fails.sum | 104 +- 13-check_regression/mail-body.txt | 244 +- 13-check_regression/results.compare | 209 +- 13-check_regression/results.compare2 | 1837 ++++------ 13-check_regression/results.regressions | 142 +- 14-update_baseline/console.log | 70 +- dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gdb_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 246 +- mail/mail-subject.txt | 2 +- manifest.sh | 28 +- results | 142 +- sumfiles/g++.log.xz | Bin 3429720 -> 3411632 bytes sumfiles/g++.sum | 174 +- sumfiles/gcc.log.xz | Bin 3043248 -> 3034356 bytes sumfiles/gcc.sum | 5686 +++++++++++++++---------------- sumfiles/gfortran.log.xz | Bin 1046088 -> 1037988 bytes sumfiles/gfortran.sum | 40 +- sumfiles/libatomic.log.xz | Bin 2288 -> 2288 bytes sumfiles/libatomic.sum | 4 +- sumfiles/libgomp.log.xz | Bin 214620 -> 214596 bytes sumfiles/libgomp.sum | 21 +- sumfiles/libitm.log.xz | Bin 2692 -> 2692 bytes sumfiles/libitm.sum | 6 +- sumfiles/libstdc++.log.xz | Bin 437308 -> 426080 bytes sumfiles/libstdc++.sum | 25 +- 42 files changed, 4206 insertions(+), 4784 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 5 months

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_gcc_check_bootstrap/release-arm-check_bootstrap_lto updated (61c496e95ac5 -> 4a58c41371ce)

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 61c496e95ac5 36: onsuccess: #152: 1: Success after binutils/gcc: 19 commits new 4a58c41371ce 37: onsuccess: #153: 1: Success after binutils/gcc: 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 1740 -> 1756 bytes 02-prepare_abe/console.log.xz | Bin 2752 -> 2760 bytes 03-build_abe-binutils/console.log.xz | Bin 52280 -> 52524 bytes 04-build_abe-bootstrap_lto/console.log.xz | Bin 472904 -> 469756 bytes 05-build_abe-dejagnu/console.log.xz | Bin 3852 -> 3824 bytes 06-build_abe-check_bootstrap_lto/console.log.xz | Bin 2448 -> 2456 bytes 07-check_regression/console.log.xz | Bin 5136 -> 4576 bytes 07-check_regression/results.compare | 16 +- 07-check_regression/results.compare2 | 70 +- 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 2834244 -> 2822208 bytes sumfiles/g++.sum | 112 +- sumfiles/gcc.log.xz | Bin 2479056 -> 2509360 bytes sumfiles/gcc.sum | 4402 +++++++++++------------ sumfiles/gfortran.log.xz | Bin 947872 -> 948976 bytes sumfiles/gfortran.sum | 42 +- sumfiles/libatomic.log.xz | Bin 2300 -> 2300 bytes sumfiles/libatomic.sum | 4 +- sumfiles/libgomp.log.xz | Bin 207404 -> 207292 bytes sumfiles/libgomp.sum | 16 +- sumfiles/libitm.log.xz | Bin 2720 -> 2728 bytes sumfiles/libitm.sum | 6 +- sumfiles/libstdc++.log.xz | Bin 464340 -> 472436 bytes sumfiles/libstdc++.sum | 10 +- 30 files changed, 2326 insertions(+), 2382 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 5 months

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_kernel/llvm-master-aarch64-lts-allmodconfig updated (e7d3304cd52b -> e0426ca19027)

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-lts-allmodconfig in repository toolchain/ci/base-artifacts. from e7d3304cd52b 40: onsuccess: #522: boot: Success after binutils/llvm: 42 [...] new e0426ca19027 41: onsuccess: #523: boot: Success after binutils/llvm/lin [...] 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 1748 -> 1776 bytes 02-prepare_abe/console.log.xz | Bin 2768 -> 2796 bytes 03-build_abe-binutils/console.log.xz | Bin 31840 -> 32288 bytes 04-build_kernel_llvm/console.log.xz | Bin 66856 -> 66696 bytes 05-build_abe-qemu/console.log.xz | Bin 30756 -> 32408 bytes 06-build_linux/console.log.xz | Bin 3468 -> 3552 bytes 07-boot_linux/console.log.xz | Bin 508 -> 508 bytes 08-check_regression/console.log.xz | Bin 3568 -> 4524 bytes dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/linux_rev | 2 +- git/llvm_rev | 2 +- git/qemu_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 2 +- mail/mail-subject.txt | 2 +- manifest.sh | 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, 5 months

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_gnu_cross_build/release-arm updated (29e142e4ae08 -> 5d4473c6c422)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. tcwg-buildslave pushed a change to branch linaro-local/ci/tcwg_gnu_cross_build/release-arm in repository toolchain/ci/base-artifacts. from 29e142e4ae08 24: onsuccess: #145: 7: Success after binutils/gcc/gdb/qem [...] new 5d4473c6c422 25: onsuccess: #146: 7: Success after binutils/gcc/linux/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 1744 -> 1772 bytes 02-prepare_abe/console.log.xz | Bin 2784 -> 2792 bytes 04-build_abe-binutils/console.log.xz | Bin 30496 -> 30224 bytes 05-build_abe-stage1/console.log.xz | Bin 86772 -> 87208 bytes 07-build_abe-linux/console.log.xz | Bin 8708 -> 8700 bytes 08-build_abe-glibc/console.log.xz | Bin 229256 -> 230332 bytes 09-build_abe-stage2/console.log.xz | Bin 221032 -> 224132 bytes 10-build_abe-gdb/console.log.xz | Bin 36992 -> 37924 bytes 11-build_abe-qemu/console.log.xz | Bin 30668 -> 31652 bytes 12-check_regression/console.log.xz | Bin 4032 -> 4648 bytes 13-update_baseline/console.log | 8 +++---- dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- git/gdb_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 | 42 +++++++++++++++++------------------ 21 files changed, 34 insertions(+), 34 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 5 months

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_gnu_native_check_gdb/release-arm updated (40fe4d391b33 -> 3694a5d98fef)

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/release-arm in repository toolchain/ci/base-artifacts. from 40fe4d391b33 35: onsuccess: #189: 1: Success after binutils/gcc/gdb: 22 [...] new 3694a5d98fef 36: onsuccess: #190: 1: Success after binutils/gcc/linux/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 1736 -> 1724 bytes 02-prepare_abe/console.log.xz | Bin 2744 -> 2756 bytes 03-build_abe-binutils/console.log.xz | Bin 51956 -> 51756 bytes 04-build_abe-gcc/console.log.xz | Bin 228568 -> 230212 bytes 05-clean_sysroot/console.log.xz | Bin 316 -> 316 bytes 06-build_abe-linux/console.log.xz | Bin 8700 -> 8820 bytes 07-build_abe-glibc/console.log.xz | Bin 232360 -> 232800 bytes 08-build_abe-gdb/console.log.xz | Bin 46568 -> 46608 bytes 09-build_abe-dejagnu/console.log.xz | Bin 3896 -> 3840 bytes 10-build_abe-check_gdb/console.log.xz | Bin 2052 -> 2140 bytes 11-check_regression/console.log.xz | Bin 12748 -> 15280 bytes 11-check_regression/extra-bisect-params | 2 +- 11-check_regression/fails.sum | 54 +- 11-check_regression/mail-body.txt | 191 +- 11-check_regression/results.compare | 97 +- 11-check_regression/results.compare2 | 5821 ++++++++++++--------- 11-check_regression/results.regressions | 97 +- dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- git/gdb_rev | 2 +- git/linux_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 193 +- mail/mail-subject.txt | 2 +- manifest.sh | 32 +- results | 97 +- sumfiles/gdb.log.xz | Bin 1621436 -> 1667792 bytes sumfiles/gdb.sum | 8468 ++++++++++++++++++++----------- 29 files changed, 9227 insertions(+), 5839 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 5 months

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_gcc_bootstrap/master-aarch64-bootstrap_profiled_lto updated (bb5db2e9e2b7 -> 756a10b2a0a9)

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_lto in repository toolchain/ci/base-artifacts. discards bb5db2e9e2b7 121: onsuccess: #536: 1: Success after binutils/gcc: 76 commits discards 0c47f84821ac 120: onsuccess: #535: 1: Success after binutils: 10 commits discards b6b31a1d2850 119: force: #534: 1: Failure after gdb-12-branchpoint-3046 [...] discards cc65c4d53894 118: force: #533: 2: Success after binutils: 4 commits discards b2f3053f4fe5 117: onsuccess: #531: 2: Success after gcc: 65 commits discards ed5c9d82921c 116: onsuccess: #528: 2: Success after binutils/gcc: 48 commits discards 3c222bf7a9aa 115: onsuccess: #527: 2: Success after binutils/gcc: 11 commits discards 09b447eefc79 114: onsuccess: #526: 2: Success after binutils/gcc: 3 commits discards e971c1512f92 113: onsuccess: #525: 2: Success after binutils/gcc: 35 commits discards f71de52ff789 112: onsuccess: #524: 2: Success after binutils/gcc: 32 commits discards 880c6319f46a 111: onsuccess: #523: 2: Success after binutils/gcc: 26 commits discards 48c4a5a4aa11 110: onsuccess: #522: 2: Success after binutils/gcc: 47 commits discards 8c70de67682e 109: onsuccess: #521: 2: Success after binutils/gcc: 32 commits discards 0d6877bb0da2 108: onsuccess: #520: 2: Success after binutils/gcc: 13 commits discards 25e27950fd37 107: onsuccess: #519: 2: Success after binutils/gcc: 8 commits discards 08560c78f4ce 106: onsuccess: #518: 2: Success after binutils/gcc: 31 commits discards c5e525fcab48 105: onsuccess: #517: 2: Success after binutils/gcc: 52 commits discards bc15dc6f8ddb 104: onsuccess: #516: 2: Success after binutils/gcc: 44 commits discards f530fa8a8b7e 103: onsuccess: #515: 2: Success after binutils/gcc: 22 commits discards 17b329df5616 102: onsuccess: #514: 2: Success after binutils/gcc: 118 commits discards 85738ab6d799 101: onsuccess: #513: 2: Success after binutils/gcc: 6 commits discards 1eb57c0b35ff 100: onsuccess: #512: 2: Success after binutils/gcc: 27 commits discards 80d984d2c9fb 99: onsuccess: #510: 2: Success after binutils/gcc: 48 commits discards b2a14ee567c0 98: onsuccess: #509: 2: Success after binutils/gcc: 27 commits discards 61e8e96d25b7 97: onsuccess: #508: 2: Success after binutils/gcc: 46 commits discards 5d48c7b86451 96: onsuccess: #507: 2: Success after binutils/gcc: 55 commits discards 2f4142dcd835 95: onsuccess: #506: 2: Success after binutils/gcc: 29 commits discards 7b392233be0e 94: onsuccess: #502: 2: Success after binutils/gcc: 37 commits discards e73507973b98 93: onsuccess: #501: 2: Success after binutils/gcc: 301 commits discards 22a62cdae688 92: onsuccess: #499: 2: Success after binutils: 4 commits discards dbc8740f9139 91: onsuccess: #497: 2: Success after binutils/gcc: 58 commits discards 29c3d5e02a31 90: onsuccess: #496: 2: Success after binutils/gcc: 49 commits discards b21f0b50270e 89: onsuccess: #495: 2: Success after binutils/gcc: 62 commits discards 695f408fac23 88: onsuccess: #494: 2: Success after binutils/gcc: 139 commits discards f73c200edb63 87: onsuccess: #493: 2: Success after binutils/gcc: 13 commits discards c6884f4e7125 86: onsuccess: #492: 2: Success after binutils/gcc: 22 commits discards 08116e296e74 85: onsuccess: #491: 2: Success after binutils/gcc: 71 commits discards 545064335ce1 84: onsuccess: #490: 2: Success after binutils/gcc: 42 commits discards ed2990c138fb 83: onsuccess: #489: 2: Success after binutils/gcc: 33 commits discards e9b355bda65a 82: onsuccess: #488: 2: Success after binutils/gcc: 65 commits discards 501004bb36c3 81: onsuccess: #486: 2: Success after binutils/gcc: 3 commits discards bcdb3a215188 80: onsuccess: #485: 2: Success after binutils/gcc: 24 commits discards a4682abfe27a 79: onsuccess: #484: 2: Success after binutils/gcc: 34 commits discards 554f49407a3a 78: onsuccess: #483: 2: Success after binutils/gcc: 30 commits discards 3b1e3d9ffc83 77: onsuccess: #482: 2: Success after binutils/gcc: 34 commits discards 84624985aab6 76: onsuccess: #481: 2: Success after binutils/gcc: 76 commits discards 33baea6d9f43 75: onsuccess: #480: 2: Success after binutils/gcc: 6 commits discards 6544c39a0e55 74: onsuccess: #479: 2: Success after binutils/gcc: 6 commits discards a9e86c2c4d81 73: onsuccess: #478: 2: Success after binutils/gcc: 39 commits discards ade7815ac4df 72: onsuccess: #477: 2: Success after binutils/gcc: 47 commits discards a10b1b91c145 71: onsuccess: #476: 2: Success after binutils/gcc: 47 commits discards ffb0cec57c48 70: onsuccess: #475: 2: Success after binutils/gcc: 44 commits discards 1ce300e7802a 69: onsuccess: #474: 2: Success after binutils/gcc: 46 commits discards 66f10a49d01d 68: onsuccess: #473: 2: Success after binutils/gcc: 9 commits discards 20ed735cc471 67: onsuccess: #472: 2: Success after binutils/gcc: 5 commits discards 101e2528d64e 66: onsuccess: #471: 2: Success after binutils/gcc: 53 commits discards dd1027e134f2 65: onsuccess: #470: 2: Success after binutils/gcc: 28 commits discards a878600bba2c 64: onsuccess: #469: 2: Success after binutils/gcc: 41 commits discards 53714df78415 63: onsuccess: #468: 2: Success after binutils/gcc: 61 commits discards 10f9ff578ddd 62: onsuccess: #467: 1: Success after binutils/gcc: 50 commits discards d7f620446145 61: onsuccess: #466: 1: Success after binutils/gcc: 12 commits discards fe2d2c788686 60: onsuccess: #465: 1: Success after basepoints/gcc-13-31 [...] discards ad9a27dcfdfb 59: force: #464: 1: Failure after basepoints/gcc-13-3172-g [...] discards 249199a41ae9 58: force: #463: 2: Success after gcc: 30 commits discards e48befe984ad 57: onsuccess: #460: 2: Success after binutils: 8 commits discards 935fcaa67f76 56: onsuccess: #458: 2: Success after binutils/gcc: 54 commits discards 0a903008963c 55: onsuccess: #457: 2: Success after binutils/gcc: 30 commits discards 1e39ca4f89b6 54: onsuccess: #456: 2: Success after binutils/gcc: 47 commits discards 53e8e187bce7 53: onsuccess: #455: 2: Success after binutils/gcc: 34 commits discards 2dfa01125e77 52: onsuccess: #454: 2: Success after binutils/gcc: 183 commits discards 689dcbd8aadc 51: onsuccess: #453: 1: Success after gcc: 20 commits discards 5ef4915f052b 50: force: #452: 1: Failure after basepoints/gcc-13-2887-g [...] discards 3c03a1ec62bd 49: force: #451: 2: Success after basepoints/gcc-13-2886-g [...] discards c632cedb485a 48: onsuccess: #448: 2: Success after binutils: 6 commits discards 8a6fb42f5a82 47: onsuccess: #446: 2: Success after binutils/gcc: 54 commits discards 74630dfb58a2 46: onsuccess: #445: 2: Success after binutils/gcc: 12 commits discards 6159cf938ba1 45: onsuccess: #444: 2: Success after binutils/gcc: 9 commits discards d6dcae0855e2 44: onsuccess: #443: 2: Success after binutils/gcc: 100 commits discards 64addf04e552 43: onsuccess: #441: 2: Success after binutils/gcc: 36 commits discards c7eab0ad015f 42: onsuccess: #440: 2: Success after binutils/gcc: 41 commits discards 21c1624c36b2 41: onsuccess: #439: 2: Success after binutils/gcc: 8 commits discards 8605455ec2f5 40: onsuccess: #438: 2: Success after binutils/gcc: 7 commits discards 879da0f6276d 39: onsuccess: #437: 2: Success after binutils/gcc: 6 commits discards a9b65605d4bd 38: onsuccess: #436: 2: Success after binutils/gcc: 25 commits discards 9a38ae5365c6 37: onsuccess: #435: 2: Success after binutils/gcc: 19 commits discards 23b36e7acc60 36: onsuccess: #434: 2: Success after binutils/gcc: 34 commits discards 04b7c7bbaf0b 35: onsuccess: #433: 2: Success after binutils/gcc: 29 commits discards fdf6dc65c502 34: onsuccess: #432: 2: Success after binutils/gcc: 68 commits discards 7bd17061d860 33: onsuccess: #431: 2: Success after binutils/gcc: 4 commits discards f30fb058fcd5 32: onsuccess: #430: 2: Success after binutils/gcc: 7 commits discards 9407a4a6226a 31: onsuccess: #429: 2: Success after binutils/gcc: 25 commits discards 2d3b2e84247b 30: onsuccess: #428: 2: Success after binutils/gcc: 30 commits discards cad3e31ad4a5 29: onsuccess: #427: 2: Success after binutils/gcc: 34 commits discards 0bfdb1e932b5 28: onsuccess: #426: 2: Success after binutils/gcc: 60 commits discards 23f02b7f743e 27: onsuccess: #425: 2: Success after binutils/gcc: 64 commits discards f5db66f4a775 26: onsuccess: #423: 2: Success after binutils/gcc: 6 commits discards d34268de7d79 25: onsuccess: 2: Success after binutils/gcc: 35 commits discards bf6cef30278b 24: onsuccess: 2: Success after binutils/gcc: 39 commits discards 260a40020486 23: onsuccess: 2: Success after binutils/gcc: 52 commits discards 856761bdd865 22: onsuccess: 2: Successful build after binutils/gcc: 51 commits discards d0fc88849519 21: onsuccess: 2: Successful build after binutils/gcc: 18 commits new 3ca611286cd4 21: onsuccess: 2: Successful build after binutils/gcc: 18 commits new 70f49f998591 22: onsuccess: 2: Successful build after binutils/gcc: 51 commits new 0d86928974ca 23: onsuccess: 2: Success after binutils/gcc: 52 commits new d57db65dcf11 24: onsuccess: 2: Success after binutils/gcc: 39 commits new 2df97549e2bb 25: onsuccess: 2: Success after binutils/gcc: 35 commits new cf9018170664 26: onsuccess: #423: 2: Success after binutils/gcc: 6 commits new fd834c562371 27: onsuccess: #425: 2: Success after binutils/gcc: 64 commits new f44a9a03368c 28: onsuccess: #426: 2: Success after binutils/gcc: 60 commits new 44ad2839de5f 29: onsuccess: #427: 2: Success after binutils/gcc: 34 commits new 1c1c9ade131f 30: onsuccess: #428: 2: Success after binutils/gcc: 30 commits new a8e331beafa3 31: onsuccess: #429: 2: Success after binutils/gcc: 25 commits new a316d877fe4e 32: onsuccess: #430: 2: Success after binutils/gcc: 7 commits new 722a482ada56 33: onsuccess: #431: 2: Success after binutils/gcc: 4 commits new 271ca5f64923 34: onsuccess: #432: 2: Success after binutils/gcc: 68 commits new 9e1a968a7f47 35: onsuccess: #433: 2: Success after binutils/gcc: 29 commits new 2eb44578ff70 36: onsuccess: #434: 2: Success after binutils/gcc: 34 commits new 1cc72f98155c 37: onsuccess: #435: 2: Success after binutils/gcc: 19 commits new ae61318b04f7 38: onsuccess: #436: 2: Success after binutils/gcc: 25 commits new 62906e9b2e5b 39: onsuccess: #437: 2: Success after binutils/gcc: 6 commits new 877aa8b6a615 40: onsuccess: #438: 2: Success after binutils/gcc: 7 commits new 334659b3ff7a 41: onsuccess: #439: 2: Success after binutils/gcc: 8 commits new c76791c7b960 42: onsuccess: #440: 2: Success after binutils/gcc: 41 commits new 900fb2b443a3 43: onsuccess: #441: 2: Success after binutils/gcc: 36 commits new d72bbe5807ea 44: onsuccess: #443: 2: Success after binutils/gcc: 100 commits new 6064e06e5058 45: onsuccess: #444: 2: Success after binutils/gcc: 9 commits new fdf8bb9a4d37 46: onsuccess: #445: 2: Success after binutils/gcc: 12 commits new f963b066d130 47: onsuccess: #446: 2: Success after binutils/gcc: 54 commits new 75b6dc6dbfc8 48: onsuccess: #448: 2: Success after binutils: 6 commits new 8bca4e09dd8d 49: force: #451: 2: Success after basepoints/gcc-13-2886-g [...] new 2c51f632ab15 50: force: #452: 1: Failure after basepoints/gcc-13-2887-g [...] new 1c8d385b5f4c 51: onsuccess: #453: 1: Success after gcc: 20 commits new 47f198fa69a9 52: onsuccess: #454: 2: Success after binutils/gcc: 183 commits new 09cdbd117a28 53: onsuccess: #455: 2: Success after binutils/gcc: 34 commits new 7bc8fcd5c21e 54: onsuccess: #456: 2: Success after binutils/gcc: 47 commits new 11a34b431388 55: onsuccess: #457: 2: Success after binutils/gcc: 30 commits new 83759cd9e6df 56: onsuccess: #458: 2: Success after binutils/gcc: 54 commits new 11dfcfde4da7 57: onsuccess: #460: 2: Success after binutils: 8 commits new 975878c76428 58: force: #463: 2: Success after gcc: 30 commits new 6110b89461fe 59: force: #464: 1: Failure after basepoints/gcc-13-3172-g [...] new b987b940608d 60: onsuccess: #465: 1: Success after basepoints/gcc-13-31 [...] new dae6fe31185c 61: onsuccess: #466: 1: Success after binutils/gcc: 12 commits new 7c9fa5dd8686 62: onsuccess: #467: 1: Success after binutils/gcc: 50 commits new 052a8d65e8a7 63: onsuccess: #468: 2: Success after binutils/gcc: 61 commits new 7f96b78e7150 64: onsuccess: #469: 2: Success after binutils/gcc: 41 commits new 1e6dcec6b110 65: onsuccess: #470: 2: Success after binutils/gcc: 28 commits new 4900c7534825 66: onsuccess: #471: 2: Success after binutils/gcc: 53 commits new 33d4ef2d7f00 67: onsuccess: #472: 2: Success after binutils/gcc: 5 commits new 376beb0a3f48 68: onsuccess: #473: 2: Success after binutils/gcc: 9 commits new cbec56b8f926 69: onsuccess: #474: 2: Success after binutils/gcc: 46 commits new c0daed3f7667 70: onsuccess: #475: 2: Success after binutils/gcc: 44 commits new c5069b670c7f 71: onsuccess: #476: 2: Success after binutils/gcc: 47 commits new 9ad33912a11c 72: onsuccess: #477: 2: Success after binutils/gcc: 47 commits new ba03978c75d0 73: onsuccess: #478: 2: Success after binutils/gcc: 39 commits new 0628a9871b8b 74: onsuccess: #479: 2: Success after binutils/gcc: 6 commits new cf616413c90b 75: onsuccess: #480: 2: Success after binutils/gcc: 6 commits new 4564f662857b 76: onsuccess: #481: 2: Success after binutils/gcc: 76 commits new c6c9b2f43b17 77: onsuccess: #482: 2: Success after binutils/gcc: 34 commits new 43e33dcdcc9b 78: onsuccess: #483: 2: Success after binutils/gcc: 30 commits new 76dd83a6f917 79: onsuccess: #484: 2: Success after binutils/gcc: 34 commits new 531764e745e6 80: onsuccess: #485: 2: Success after binutils/gcc: 24 commits new 016297c74fc8 81: onsuccess: #486: 2: Success after binutils/gcc: 3 commits new 501482cafc56 82: onsuccess: #488: 2: Success after binutils/gcc: 65 commits new 4a01359dde71 83: onsuccess: #489: 2: Success after binutils/gcc: 33 commits new f0d6fad5019c 84: onsuccess: #490: 2: Success after binutils/gcc: 42 commits new a3eaa417426f 85: onsuccess: #491: 2: Success after binutils/gcc: 71 commits new b9bbd24fa218 86: onsuccess: #492: 2: Success after binutils/gcc: 22 commits new b79ea6993767 87: onsuccess: #493: 2: Success after binutils/gcc: 13 commits new 9bd113700d6e 88: onsuccess: #494: 2: Success after binutils/gcc: 139 commits new 9bd34b1d75f4 89: onsuccess: #495: 2: Success after binutils/gcc: 62 commits new 955bdaed1987 90: onsuccess: #496: 2: Success after binutils/gcc: 49 commits new 9463d46a3da5 91: onsuccess: #497: 2: Success after binutils/gcc: 58 commits new d4d1b3b69a56 92: onsuccess: #499: 2: Success after binutils: 4 commits new 686e6f43ece8 93: onsuccess: #501: 2: Success after binutils/gcc: 301 commits new 1b8cbf966654 94: onsuccess: #502: 2: Success after binutils/gcc: 37 commits new aa10e0468619 95: onsuccess: #506: 2: Success after binutils/gcc: 29 commits new 381a5db1f122 96: onsuccess: #507: 2: Success after binutils/gcc: 55 commits new a8d32475ad15 97: onsuccess: #508: 2: Success after binutils/gcc: 46 commits new 9c5a88eb7508 98: onsuccess: #509: 2: Success after binutils/gcc: 27 commits new a04f2abd173f 99: onsuccess: #510: 2: Success after binutils/gcc: 48 commits new f138a4dab53d 100: onsuccess: #512: 2: Success after binutils/gcc: 27 commits new e57777f95ebb 101: onsuccess: #513: 2: Success after binutils/gcc: 6 commits new 88d6dfa09f27 102: onsuccess: #514: 2: Success after binutils/gcc: 118 commits new 96741357dc6a 103: onsuccess: #515: 2: Success after binutils/gcc: 22 commits new 4fbcfef3e16b 104: onsuccess: #516: 2: Success after binutils/gcc: 44 commits new 70265c790260 105: onsuccess: #517: 2: Success after binutils/gcc: 52 commits new b804565ed840 106: onsuccess: #518: 2: Success after binutils/gcc: 31 commits new cd7f3dc114e3 107: onsuccess: #519: 2: Success after binutils/gcc: 8 commits new 74e7f9fe9af9 108: onsuccess: #520: 2: Success after binutils/gcc: 13 commits new e71d3e0e3f51 109: onsuccess: #521: 2: Success after binutils/gcc: 32 commits new 2e4bbb81879a 110: onsuccess: #522: 2: Success after binutils/gcc: 47 commits new 6e16212390b3 111: onsuccess: #523: 2: Success after binutils/gcc: 26 commits new 3dab57ef35d8 112: onsuccess: #524: 2: Success after binutils/gcc: 32 commits new 750a772a1884 113: onsuccess: #525: 2: Success after binutils/gcc: 35 commits new 23e2a1bccff6 114: onsuccess: #526: 2: Success after binutils/gcc: 3 commits new 386e1c4164d4 115: onsuccess: #527: 2: Success after binutils/gcc: 11 commits new 65f36b2b07e0 116: onsuccess: #528: 2: Success after binutils/gcc: 48 commits new 1b2baacee888 117: onsuccess: #531: 2: Success after gcc: 65 commits new 5ea7e1a3cc0b 118: force: #533: 2: Success after binutils: 4 commits new 3c8b9895bc06 119: force: #534: 1: Failure after gdb-12-branchpoint-3046 [...] new 6100d64d5c7a 120: onsuccess: #535: 1: Success after binutils: 10 commits new e5798a68b586 121: onsuccess: #536: 1: Success after binutils/gcc: 76 commits new 756a10b2a0a9 122: onsuccess: #537: 2: Success after binutils/gcc: 36 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 (bb5db2e9e2b7) \ N -- N -- N refs/heads/linaro-local/ci/tcwg_gcc_bootstrap/master-aar [...] 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 1704 -> 1752 bytes 02-prepare_abe/console.log.xz | Bin 2760 -> 2744 bytes 04-build_abe-binutils/console.log.xz | Bin 39872 -> 39456 bytes 05-build_abe-bootstrap_profiled_lto/console.log.xz | Bin 164328 -> 531732 bytes 06-check_regression/console.log.xz | Bin 3016 -> 3080 bytes 06-check_regression/mail-body.txt | 2 +- 07-update_baseline/console.log | 34 ++++++++++----------- dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 4 +-- mail/mail-subject.txt | 2 +- manifest.sh | 18 +++++------ results | 2 +- 15 files changed, 35 insertions(+), 35 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 5 months

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_kernel/llvm-master-aarch64-mainline-allyesconfig updated (eaa9597bea89 -> 33e5815047d9)

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-mainline-allyesconfig in repository toolchain/ci/base-artifacts. from eaa9597bea89 38: force: #532: 21442: Failure after v6.1-rc4-1107-g8cab7 [...] new 33e5815047d9 39: onsuccess: #533: 21611: Success after linux: 11895 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 1724 -> 1776 bytes 02-prepare_abe/console.log.xz | Bin 2796 -> 2796 bytes 03-build_abe-binutils/console.log.xz | Bin 32384 -> 32228 bytes 04-build_kernel_llvm/console.log.xz | Bin 65056 -> 65376 bytes 05-build_abe-qemu/console.log.xz | Bin 32136 -> 31864 bytes 06-build_linux/console.log.xz | Bin 3568 -> 3756 bytes 08-check_regression/console.log.xz | Bin 3856 -> 3068 bytes 08-check_regression/jira-body.txt | 2 +- 08-check_regression/mail-body.txt | 22 +- 08-check_regression/mail-subject.txt | 2 +- 08-check_regression/results.regressions | 7 - 08-check_regression/trigger-bisect | 2 - 08-check_regression/trigger-notify | 0 09-update_baseline/console.log | 10 +- dashboard/dashboard-generate.sh | 2 +- git/linux_rev | 2 +- jenkins/jira-status.draft | 4 - jenkins/mail-body.draft | 609 -------------------------------- jenkins/mail-recipients.draft | 1 - jenkins/mail-subject.draft | 1 - jenkins/notify.sh | 3 - mail/jira-body.txt | 2 +- mail/mail-body.txt | 22 +- mail/mail-subject.txt | 2 +- manifest.sh | 16 +- results | 9 +- 26 files changed, 40 insertions(+), 678 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, 5 months

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_gnu_cross_check_gcc/master-arm updated (d7ad7a397f72 -> 129e48b732fc)

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-arm in repository toolchain/ci/base-artifacts. discards d7ad7a397f72 250: onsuccess: #2066: 1: Success after binutils/gcc/linux [...] discards bd090c8567ee 249: onsuccess: #2065: 1: Success after binutils/gcc/linux [...] discards 9ad4e6b78649 248: onsuccess: #2064: 1: Success after binutils/gcc/gdb/q [...] discards 96525e2573fc 247: onsuccess: #2063: 1: Success after binutils/gcc/linux [...] discards ac0fd2d76ac0 246: onsuccess: #2062: 1: Success after binutils/gcc/linux [...] discards f9fbbfef2dff 245: onsuccess: #2061: 1: Success after binutils/gcc/linux [...] discards f979389bf2a6 244: onsuccess: #2060: 1: Success after binutils/gcc/gdb/q [...] discards 9061afb3199f 243: onsuccess: #2059: 1: Success after basepoints/gcc-13- [...] discards 1285b4f91031 242: onsuccess: #2058: 1: Success after binutils/gcc/linux [...] discards 2b2994eef8ad 241: onsuccess: #2057: 1: Success after binutils/gcc/linux [...] discards 1784b127d780 240: onsuccess: #2056: 1: Success after binutils/gcc/gdb: [...] discards 1c52ec65ad2c 239: onsuccess: #2055: 1: Success after binutils/gcc/linux [...] discards f35b8fef6a0b 238: onsuccess: #2054: 1: Success after binutils/gcc/linux [...] discards 2a2873bed511 237: onsuccess: #2053: 1: Success after binutils/gcc/linux [...] discards 50c30b59653f 236: onsuccess: #2052: 1: Success after binutils/gcc/gdb: [...] discards f27ca2705c9a 235: onsuccess: #2051: 1: Success after binutils/linux/gdb [...] discards c073e309f48f 234: onsuccess: #2050: 1: Success after binutils/gcc/linux [...] discards 13d029a6fdbd 233: onsuccess: #2049: 1: Success after binutils/gcc/linux [...] discards f1ceb4e05fab 232: onsuccess: #2048: 1: Success after glibc: 2 commits discards 139176510976 231: onsuccess: #2047: 1: Success after gcc: 4 commits discards 7299d54234e1 230: onsuccess: #2044: 1: Success after binutils/gcc/linux [...] discards 8ef40a95f95d 229: onsuccess: #2043: 1: Success after binutils/gcc/linux [...] discards 07923b19c020 228: onsuccess: #2042: 1: Success after basepoints/gcc-13- [...] discards 95b0d8a89e76 227: onsuccess: #2041: 1: Success after binutils/gcc/linux [...] discards 62bcb20bb243 226: onsuccess: #2040: 1: Success after binutils/gcc/gdb: [...] discards 47cf2a7a2778 225: onsuccess: #2039: 1: Success after binutils/linux/gli [...] discards 60806d72efda 224: onsuccess: #2038: 1: Success after binutils/gcc/linux [...] discards 37283eacbc5f 223: onsuccess: #2036: 1: Success after binutils/gcc/linux [...] discards c47b23af178a 222: onsuccess: #2035: 1: Success after binutils/gcc/glibc [...] discards 5f109e19fa21 221: onsuccess: #2033: 1: Success after binutils/gdb: 2 commits discards f22a32930a4e 220: onsuccess: #2032: 1: Success after binutils/gcc/linux [...] discards 5ae26f010f3a 219: onsuccess: #2031: 1: Success after binutils/gcc/glibc [...] discards 176fecbab806 218: onsuccess: #2030: 1: Success after gcc: 5 commits discards 9fb34c2941e3 217: onsuccess: #2029: 1: Success after binutils/gcc/glibc [...] discards 6ae0e9f84665 216: onsuccess: #2028: 1: Success after binutils/gcc/linux [...] discards 1940cd420dcd 215: onsuccess: #2027: 1: Success after binutils/gcc/glibc [...] discards d4ff1ebd9c7c 214: onsuccess: #2026: 1: Success after binutils/gcc/gdb/q [...] discards f839f0a4f425 213: onsuccess: #2024: 1: Success after binutils: 3 commits discards 5982686cf0cb 212: onsuccess: #2022: 1: Success after linux: 3 commits discards c24888e6d148 211: onsuccess: #2020: 1: Success after binutils: 10 commits discards 49bf27a30e23 210: onsuccess: #2017: 1: Success after binutils: 6 commits discards fe60b74d1fe4 209: onsuccess: #2014: 1: Success after binutils: 12 commits discards 6000f3e7ed5e 208: onsuccess: #2012: 1: Success after linux: 12 commits discards c16043f3c111 207: onsuccess: #2010: 1: Success after gcc: 4 commits discards d6cc7ef82e92 206: onsuccess: #2007: 1: Success after gcc: 2 commits discards b2fc45b788eb 205: onsuccess: #2006: 1: Success after gcc: 3 commits discards 905f772b17dd 204: onsuccess: #2005: 1: Success after binutils/gcc/linux [...] discards 4e168576d641 203: onsuccess: #2004: 1: Success after binutils/gcc/gdb: [...] discards 32e4e6d98f09 202: onsuccess: #2003: 1: Success after binutils/gcc/linux [...] discards a2f2153e45d5 201: onsuccess: #2002: 1: Success after gcc/glibc: 5 commits discards 1421cb78fbe9 200: onsuccess: #2001: 1: Success after binutils/gcc/gdb: [...] discards 54d945e69dfb 199: onsuccess: #2000: 1: Success after gcc: 5 commits discards a55617534d66 198: onsuccess: #1999: 1: Success after binutils/gcc/linux [...] discards 43a3d05cb86e 197: onsuccess: #1998: 1: Success after binutils/gcc/gdb: [...] discards 035c9dfd6c20 196: onsuccess: #1997: 1: Success after binutils/gcc/gdb: [...] discards 800fcf8a7ccc 195: onsuccess: #1996: 1: Success after binutils/gcc/glibc [...] discards 9218f0891f32 194: onsuccess: #1995: 1: Success after linux: 517 commits discards 1e1ce9c91ed4 193: onsuccess: #1992: 1: Success after binutils: 151 commits discards e4fd8ed5810f 192: onsuccess: #1951: 1: Success after binutils/gcc/gdb: [...] discards 52de999f5a6c 191: onsuccess: #1949: 1: Success after binutils/gcc/linux [...] discards 1671d359729b 190: onsuccess: #1913: 1: Success after binutils/gcc/linux [...] discards 7635b66d604a 189: onsuccess: #1912: 1: Success after binutils/gcc/linux [...] discards bc8825da9999 188: onsuccess: #1909: 1: Success after binutils/gcc/gdb: [...] discards 65f690c25898 187: onsuccess: #1908: 1: Success after binutils/gcc/linux [...] discards 8518edb64b85 186: onsuccess: #1907: 1: Success after binutils/gcc/gdb: [...] discards 45dcdbb2bf3f 185: onsuccess: #1906: 1: Success after binutils/gcc/linux [...] discards 858e0e726fb3 184: onsuccess: #1898: 1: Success after binutils/gcc/gdb: [...] discards 08b01b9d1faf 183: onsuccess: #1897: 1: Success after binutils/gcc/linux [...] discards cffbb5020a80 182: onsuccess: #1860: 1: Success after binutils/gcc/linux [...] discards 5dbb4b050e1f 181: onsuccess: #1857: 1: Success after binutils/gcc/linux [...] discards 85712818fddf 180: onsuccess: #1831: 1: Success after binutils/gcc/linux [...] discards 5ed8d7fb4dd8 179: onsuccess: #1810: 1: Success after binutils/gcc/linux [...] discards d5dcc1780a8e 178: onsuccess: #1799: 1: Success after binutils/gcc/linux [...] discards 6df9c490e484 177: onsuccess: #1793: 1: Success after binutils/gcc/linux [...] discards 760262dd7481 176: onsuccess: #1791: 1: Success after binutils/gcc/linux [...] discards 3a69ba2fda06 175: onsuccess: #1776: 1: Success after binutils/gcc/linux [...] discards d04a5cdde038 174: onsuccess: #1775: 1: Success after binutils/gcc/linux [...] discards 45e8537e6603 173: onsuccess: #1774: 1: Success after binutils/gcc/glibc [...] discards 1e6703ff6cf1 172: onsuccess: #1773: 1: Success after binutils/gcc/glibc [...] discards c625c5654548 171: onsuccess: #1772: 1: Success after binutils/gcc/gdb: [...] discards c0fa322e178e 170: onsuccess: #1771: 1: Success after binutils/gcc/linux [...] discards ceb45f47bccb 169: onsuccess: #1770: 1: Success after gcc/linux/glibc/qe [...] discards 9014b4fd750c 168: onsuccess: #1769: 1: Success after binutils/gcc/gdb: [...] discards 8c749d625702 167: onsuccess: #1768: 1: Success after binutils/gcc/linux [...] discards a758d5a4d3ee 166: onsuccess: #1767: 1: Success after binutils/gcc/linux [...] discards bc22f8857cc2 165: onsuccess: #1766: 1: Success after binutils/gcc/linux [...] discards 1f81a1a66d8a 164: onsuccess: #1765: 1: Success after binutils/gcc/gdb: [...] discards 67fb83e3dcf7 163: onsuccess: #1764: 1: Success after gcc/linux: 141 commits discards ba9c0c3d82ac 162: onsuccess: #1763: 1: Success after binutils/gcc/linux [...] discards 1e14881db9d2 161: onsuccess: #1762: 1: Success after binutils/gcc/linux [...] discards c4b40b5e0094 160: onsuccess: #1761: 1: Success after binutils/gcc/gdb: [...] discards 1718dc72d6a7 159: onsuccess: #1760: 1: Success after binutils/gcc/gdb: [...] discards 2ad389cdaa20 158: onsuccess: #1759: 1: Success after binutils/gcc/linux [...] discards 24d5125e01c5 157: onsuccess: #1758: 1: Success after binutils/gcc/linux [...] discards bcd9a15ad28b 156: onsuccess: #1757: 1: Success after gcc: 4 commits discards c670ebb8a605 155: onsuccess: #1756: 1: Success after binutils/gcc/glibc [...] discards c0ec92fdf39e 154: onsuccess: #1755: 1: Success after gcc/linux: 21 commits discards 7b2d9e4e5e58 153: onsuccess: #1754: 1: Success after gcc: 2 commits discards 18686176b12c 152: onsuccess: #1753: 1: Success after gcc/linux/glibc/gd [...] discards 0af33cc6a538 151: onsuccess: #1751: 1: Success after gdb-12-branchpoint [...] discards e37931a516f3 150: onsuccess: #1749: 1: Success after binutils/gcc/linux [...] new 9a35d2b9963c 150: onsuccess: #1749: 1: Success after binutils/gcc/linux [...] new 478fbec4653c 151: onsuccess: #1751: 1: Success after gdb-12-branchpoint [...] new a45f0d7013f4 152: onsuccess: #1753: 1: Success after gcc/linux/glibc/gd [...] new f96119795824 153: onsuccess: #1754: 1: Success after gcc: 2 commits new d70aad100480 154: onsuccess: #1755: 1: Success after gcc/linux: 21 commits new 91e88e6f6aab 155: onsuccess: #1756: 1: Success after binutils/gcc/glibc [...] new 7a6ac19f2339 156: onsuccess: #1757: 1: Success after gcc: 4 commits new a53689798f2f 157: onsuccess: #1758: 1: Success after binutils/gcc/linux [...] new a414a30f2a5d 158: onsuccess: #1759: 1: Success after binutils/gcc/linux [...] new 5206b8321db4 159: onsuccess: #1760: 1: Success after binutils/gcc/gdb: [...] new 6f29de6ec50e 160: onsuccess: #1761: 1: Success after binutils/gcc/gdb: [...] new 86e47d6f64fb 161: onsuccess: #1762: 1: Success after binutils/gcc/linux [...] new 672143ba3476 162: onsuccess: #1763: 1: Success after binutils/gcc/linux [...] new b6d569cf1516 163: onsuccess: #1764: 1: Success after gcc/linux: 141 commits new bf75c0b4300d 164: onsuccess: #1765: 1: Success after binutils/gcc/gdb: [...] new 527ff5e6f308 165: onsuccess: #1766: 1: Success after binutils/gcc/linux [...] new 5bc639670fff 166: onsuccess: #1767: 1: Success after binutils/gcc/linux [...] new c9d51f37f6e9 167: onsuccess: #1768: 1: Success after binutils/gcc/linux [...] new 03a4acc8a836 168: onsuccess: #1769: 1: Success after binutils/gcc/gdb: [...] new 3b32280af239 169: onsuccess: #1770: 1: Success after gcc/linux/glibc/qe [...] new 4e66faacb818 170: onsuccess: #1771: 1: Success after binutils/gcc/linux [...] new 0ff95510fa8d 171: onsuccess: #1772: 1: Success after binutils/gcc/gdb: [...] new 6f9929b35c59 172: onsuccess: #1773: 1: Success after binutils/gcc/glibc [...] new ea53c5692d62 173: onsuccess: #1774: 1: Success after binutils/gcc/glibc [...] new af380bd4c3c7 174: onsuccess: #1775: 1: Success after binutils/gcc/linux [...] new 2be30fe83b68 175: onsuccess: #1776: 1: Success after binutils/gcc/linux [...] new 19710419d3be 176: onsuccess: #1791: 1: Success after binutils/gcc/linux [...] new 32087d4531f5 177: onsuccess: #1793: 1: Success after binutils/gcc/linux [...] new a702bdaecae0 178: onsuccess: #1799: 1: Success after binutils/gcc/linux [...] new 185bf47adb08 179: onsuccess: #1810: 1: Success after binutils/gcc/linux [...] new d9c20b0d8584 180: onsuccess: #1831: 1: Success after binutils/gcc/linux [...] new 99ecf0c01a78 181: onsuccess: #1857: 1: Success after binutils/gcc/linux [...] new f88e4f6a5c6f 182: onsuccess: #1860: 1: Success after binutils/gcc/linux [...] new ab0ebf298ea1 183: onsuccess: #1897: 1: Success after binutils/gcc/linux [...] new c55baca1aea1 184: onsuccess: #1898: 1: Success after binutils/gcc/gdb: [...] new fd44afc83688 185: onsuccess: #1906: 1: Success after binutils/gcc/linux [...] new df3edba4365a 186: onsuccess: #1907: 1: Success after binutils/gcc/gdb: [...] new c17ab2c37d46 187: onsuccess: #1908: 1: Success after binutils/gcc/linux [...] new c922db00258a 188: onsuccess: #1909: 1: Success after binutils/gcc/gdb: [...] new 34b0c3980622 189: onsuccess: #1912: 1: Success after binutils/gcc/linux [...] new 905782c85012 190: onsuccess: #1913: 1: Success after binutils/gcc/linux [...] new 5215990d1052 191: onsuccess: #1949: 1: Success after binutils/gcc/linux [...] new 4a691cea0296 192: onsuccess: #1951: 1: Success after binutils/gcc/gdb: [...] new b3c02b8b54f2 193: onsuccess: #1992: 1: Success after binutils: 151 commits new 9dbf2053f905 194: onsuccess: #1995: 1: Success after linux: 517 commits new b21d9efc77b9 195: onsuccess: #1996: 1: Success after binutils/gcc/glibc [...] new 9b2755c2f32e 196: onsuccess: #1997: 1: Success after binutils/gcc/gdb: [...] new 1f344202b9d1 197: onsuccess: #1998: 1: Success after binutils/gcc/gdb: [...] new 29485ac7e648 198: onsuccess: #1999: 1: Success after binutils/gcc/linux [...] new cd6f691c6cae 199: onsuccess: #2000: 1: Success after gcc: 5 commits new 4941f7e0a172 200: onsuccess: #2001: 1: Success after binutils/gcc/gdb: [...] new a88c0c68f794 201: onsuccess: #2002: 1: Success after gcc/glibc: 5 commits new 9a2d1384724d 202: onsuccess: #2003: 1: Success after binutils/gcc/linux [...] new 70b6dec08d90 203: onsuccess: #2004: 1: Success after binutils/gcc/gdb: [...] new 1045654762d1 204: onsuccess: #2005: 1: Success after binutils/gcc/linux [...] new 01c0505eb294 205: onsuccess: #2006: 1: Success after gcc: 3 commits new d8e2a3f46add 206: onsuccess: #2007: 1: Success after gcc: 2 commits new 4a78e7e96659 207: onsuccess: #2010: 1: Success after gcc: 4 commits new 1c70979aa652 208: onsuccess: #2012: 1: Success after linux: 12 commits new f9f12c77ed4e 209: onsuccess: #2014: 1: Success after binutils: 12 commits new 0f5cb12627ef 210: onsuccess: #2017: 1: Success after binutils: 6 commits new 9593bc3d8918 211: onsuccess: #2020: 1: Success after binutils: 10 commits new 925e12444f63 212: onsuccess: #2022: 1: Success after linux: 3 commits new 309c6e483d24 213: onsuccess: #2024: 1: Success after binutils: 3 commits new 01f9a7e36b52 214: onsuccess: #2026: 1: Success after binutils/gcc/gdb/q [...] new 90319bfb5b94 215: onsuccess: #2027: 1: Success after binutils/gcc/glibc [...] new 026c3c9f0570 216: onsuccess: #2028: 1: Success after binutils/gcc/linux [...] new cb880b4d1e18 217: onsuccess: #2029: 1: Success after binutils/gcc/glibc [...] new 62c20ce37e3b 218: onsuccess: #2030: 1: Success after gcc: 5 commits new 1b9e63b20231 219: onsuccess: #2031: 1: Success after binutils/gcc/glibc [...] new b8e7ef16d08a 220: onsuccess: #2032: 1: Success after binutils/gcc/linux [...] new 6b2b16b05ddc 221: onsuccess: #2033: 1: Success after binutils/gdb: 2 commits new 5d31982f37de 222: onsuccess: #2035: 1: Success after binutils/gcc/glibc [...] new f50cce888e21 223: onsuccess: #2036: 1: Success after binutils/gcc/linux [...] new fdf3664397a2 224: onsuccess: #2038: 1: Success after binutils/gcc/linux [...] new faf74236d7dd 225: onsuccess: #2039: 1: Success after binutils/linux/gli [...] new 6f59e171eea5 226: onsuccess: #2040: 1: Success after binutils/gcc/gdb: [...] new 9581f50a3276 227: onsuccess: #2041: 1: Success after binutils/gcc/linux [...] new 087f502a48ef 228: onsuccess: #2042: 1: Success after basepoints/gcc-13- [...] new d6b85de78e64 229: onsuccess: #2043: 1: Success after binutils/gcc/linux [...] new eebd14c58b19 230: onsuccess: #2044: 1: Success after binutils/gcc/linux [...] new 0156b37d9663 231: onsuccess: #2047: 1: Success after gcc: 4 commits new d23665fb5f4c 232: onsuccess: #2048: 1: Success after glibc: 2 commits new b925faa25ad8 233: onsuccess: #2049: 1: Success after binutils/gcc/linux [...] new 9baa7eada5f4 234: onsuccess: #2050: 1: Success after binutils/gcc/linux [...] new 8e35e3fe175b 235: onsuccess: #2051: 1: Success after binutils/linux/gdb [...] new f7571785f83f 236: onsuccess: #2052: 1: Success after binutils/gcc/gdb: [...] new f6ffd704c029 237: onsuccess: #2053: 1: Success after binutils/gcc/linux [...] new 396ae99add23 238: onsuccess: #2054: 1: Success after binutils/gcc/linux [...] new d055b6f1d478 239: onsuccess: #2055: 1: Success after binutils/gcc/linux [...] new 568e188496a4 240: onsuccess: #2056: 1: Success after binutils/gcc/gdb: [...] new 75370d801ab1 241: onsuccess: #2057: 1: Success after binutils/gcc/linux [...] new d6d95d2b3bf2 242: onsuccess: #2058: 1: Success after binutils/gcc/linux [...] new 8504d30b8844 243: onsuccess: #2059: 1: Success after basepoints/gcc-13- [...] new 03b4ecf589a2 244: onsuccess: #2060: 1: Success after binutils/gcc/gdb/q [...] new 4b99e8f1b814 245: onsuccess: #2061: 1: Success after binutils/gcc/linux [...] new e7a92078c4d8 246: onsuccess: #2062: 1: Success after binutils/gcc/linux [...] new 897670a50ac2 247: onsuccess: #2063: 1: Success after binutils/gcc/linux [...] new 38be421951a0 248: onsuccess: #2064: 1: Success after binutils/gcc/gdb/q [...] new 503e35f40b01 249: onsuccess: #2065: 1: Success after binutils/gcc/linux [...] new 8496fe3bc1a7 250: onsuccess: #2066: 1: Success after binutils/gcc/linux [...] new 129e48b732fc 251: onsuccess: #2067: 1: Success after binutils/gcc/gdb: [...] 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 (d7ad7a397f72) \ 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 1776 -> 1808 bytes 02-prepare_abe/console.log.xz | Bin 2788 -> 2800 bytes 03-build_abe-binutils/console.log.xz | Bin 31832 -> 32068 bytes 04-build_abe-stage1/console.log.xz | Bin 92060 -> 92232 bytes 06-build_abe-linux/console.log.xz | Bin 8716 -> 8716 bytes 07-build_abe-glibc/console.log.xz | Bin 236008 -> 235744 bytes 08-build_abe-stage2/console.log.xz | Bin 223876 -> 225704 bytes 09-build_abe-gdb/console.log.xz | Bin 39064 -> 39268 bytes 10-build_abe-qemu/console.log.xz | Bin 31544 -> 31316 bytes 11-build_abe-dejagnu/console.log.xz | Bin 3888 -> 3896 bytes 12-build_abe-check_gcc/console.log.xz | Bin 2528 -> 2760 bytes 13-check_regression/console.log.xz | Bin 6976 -> 6040 bytes 13-check_regression/extra-bisect-params | 1 + 13-check_regression/fails.sum | 7 + 13-check_regression/mail-body.txt | 57 +- 13-check_regression/results.compare | 26 +- 13-check_regression/results.compare2 | 50 +- 13-check_regression/results.regressions | 27 + 14-update_baseline/console.log | 66 +- dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- git/gdb_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 59 +- mail/mail-subject.txt | 2 +- manifest.sh | 34 +- results | 27 + sumfiles/g++.log.xz | Bin 2676612 -> 2657400 bytes sumfiles/g++.sum | 22 +- sumfiles/gcc.log.xz | Bin 2246304 -> 2276332 bytes sumfiles/gcc.sum | 2546 +++++++++++++++---------------- sumfiles/gfortran.log.xz | Bin 898060 -> 901568 bytes sumfiles/gfortran.sum | 2 +- sumfiles/libatomic.log.xz | Bin 2264 -> 2264 bytes sumfiles/libatomic.sum | 2 +- sumfiles/libgomp.log.xz | Bin 214104 -> 214092 bytes sumfiles/libgomp.sum | 2 +- sumfiles/libitm.log.xz | Bin 2668 -> 2664 bytes sumfiles/libitm.sum | 2 +- sumfiles/libstdc++.log.xz | Bin 436908 -> 435628 bytes sumfiles/libstdc++.sum | 10 +- 42 files changed, 1494 insertions(+), 1458 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, 5 months

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_gnu_native_check_binutils/master-arm updated (7a9c1a2b4c64 -> 9e45d4f8e96b)

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_binutils/master-arm in repository toolchain/ci/base-artifacts. discards 7a9c1a2b4c64 133: onsuccess: #560: 1: Success after binutils/gcc/linux/ [...] discards 5223c6ed3052 132: onsuccess: #559: 1: Success after binutils/gcc/linux/ [...] discards 30f19af5888f 131: onsuccess: #558: 1: Success after binutils/gcc/linux/ [...] discards 2fde9244b638 130: onsuccess: #557: 1: Success after binutils/gcc/linux/ [...] discards 3ebfe7c5c0c1 129: onsuccess: #556: 1: Success after binutils/gcc/linux/ [...] discards 74fe88fafbe4 128: onsuccess: #555: 1: Success after binutils/gcc/linux/ [...] discards 9914923e4eb3 127: onsuccess: #554: 1: Success after binutils/gcc/linux/ [...] discards 50e35d9783a6 126: onsuccess: #553: 1: Success after binutils/gcc/linux/ [...] discards 12db70d44034 125: onsuccess: #552: 1: Success after binutils/gcc/linux/ [...] discards 0a9704970d17 124: onsuccess: #551: 1: Success after binutils/gcc/linux/ [...] discards 91e75f19ec07 123: onsuccess: #550: 1: Success after binutils/gcc/linux/ [...] discards b52d9ecb6a1f 122: onsuccess: #549: 1: Success after binutils/gcc/linux/ [...] discards 46eb06e2a035 121: onsuccess: #548: 1: Success after binutils/gcc/linux/ [...] discards 53980337aed1 120: onsuccess: #547: 1: Success after binutils/gcc/linux/ [...] discards 639701292231 119: onsuccess: #546: 1: Success after binutils/gcc/linux/ [...] discards 888e566c333e 118: onsuccess: #545: 1: Success after binutils/gcc/linux/ [...] discards 68061ec4a98a 117: onsuccess: #544: 1: Success after binutils/gcc/linux/ [...] discards aa3c30230ce9 116: onsuccess: #543: 1: Success after binutils/gcc/linux/ [...] discards ecc30acdba74 115: onsuccess: #542: 1: Success after binutils/gcc/linux/ [...] discards 63800cdda9ef 114: onsuccess: #541: 1: Success after binutils/gcc/linux/ [...] discards 411e376602c3 113: onsuccess: #539: 1: Success after binutils/gcc/linux/ [...] discards d00c0d735e2e 112: onsuccess: #538: 1: Success after binutils/gcc/linux/ [...] discards 955733fe3b72 111: onsuccess: #537: 1: Success after binutils/gcc/gdb: 6 [...] discards 7b2f2c4e2da8 110: onsuccess: #536: 1: Success after binutils/gcc/glibc/ [...] discards 7984d206e87f 109: onsuccess: #535: 1: Success after binutils/gcc/linux/ [...] discards 201cd62292a1 108: onsuccess: #534: 1: Success after binutils/gcc/linux/ [...] discards 4110114132fc 107: onsuccess: #533: 1: Success after binutils/gcc/linux/ [...] discards 18ee23db1411 106: onsuccess: #532: 1: Success after binutils/gcc/linux/ [...] discards 95d4a76f4786 105: onsuccess: #531: 1: Success after binutils/gcc/linux/ [...] discards f2ee2bfb96f4 104: onsuccess: #530: 1: Success after gcc: 7 commits discards b0c8157e9b9d 103: onsuccess: #529: 1: Success after binutils/gcc/linux/ [...] discards 93e66b0acb71 102: onsuccess: #527: 1: Success after binutils: 5 commits discards cd89ee051bdf 101: onsuccess: #524: 1: Success after binutils: 2 commits discards 3f74a5266495 100: onsuccess: #521: 1: Success after binutils: 10 commits discards 76caa0eff154 99: onsuccess: #519: 1: Success after binutils/gcc/linux/g [...] discards 0e6de8c6a90b 98: onsuccess: #518: 1: Success after binutils/gcc/linux/g [...] discards a99b3f37a072 97: onsuccess: #517: 1: Success after binutils/gcc/linux/g [...] discards c088e328ec7e 96: onsuccess: #516: 1: Success after binutils/gcc/linux/g [...] discards 8d50f4b73861 95: onsuccess: #515: 1: Success after binutils/gcc/linux/g [...] discards 1d0e47e95519 94: onsuccess: #514: 1: Success after binutils/gcc/linux/g [...] discards 84e301e53d2d 93: onsuccess: #513: 1: Success after binutils/gcc/linux/g [...] discards cf309a10c621 92: onsuccess: #512: 1: Success after binutils/gcc/linux/g [...] discards 4f1245164aeb 91: onsuccess: #511: 1: Success after linux: 27 commits discards 538dfe5fc285 90: onsuccess: #510: 1: Success after glibc: 5 commits discards 3e1ba27017a7 89: onsuccess: #508: 1: Success after binutils: 12 commits discards 1938e21383ab 88: onsuccess: #506: 1: Success after linux: 34 commits discards a9e7efa1d268 87: onsuccess: #505: 1: Success after glibc: 7 commits discards dde5501fcdca 86: onsuccess: #503: 1: Success after binutils: 12 commits discards dd634d0ba88f 85: onsuccess: #501: 1: Success after binutils/gcc/linux/g [...] discards 9c742624ff13 84: onsuccess: #500: 1: Success after binutils/gcc/linux/g [...] discards 96d264b2b7c3 83: onsuccess: #499: 1: Success after binutils/gcc/linux/g [...] discards f34e5eeb33b1 82: onsuccess: #498: 1: Success after binutils/gcc/linux/g [...] discards ba255fc9e8e3 81: onsuccess: #497: 1: Success after binutils/gcc/linux/g [...] discards 3f60bf39194d 80: onsuccess: #496: 1: Success after binutils/gcc/linux/g [...] discards dd195f1e6159 79: onsuccess: #495: 1: Success after binutils/gcc/linux/g [...] discards 1905456dc6ad 78: onsuccess: #494: 1: Success after binutils/gcc/linux/g [...] discards 923f902617ed 77: onsuccess: #493: 1: Success after binutils/gcc/linux/g [...] discards 4d11d821df31 76: onsuccess: #492: 1: Success after binutils/gcc/linux/g [...] discards c127e1d9d320 75: onsuccess: #491: 1: Success after binutils/gcc/linux/g [...] discards 569a63a1a910 74: onsuccess: #490: 1: Success after binutils/gcc/linux/g [...] discards a20bf74ce0d0 73: onsuccess: #489: 1: Success after binutils/gcc/glibc/g [...] discards 91de8dad797b 72: onsuccess: #488: 1: Success after binutils/gcc/linux/g [...] discards 3178be2066dc 71: onsuccess: #487: 1: Success after binutils/gcc/linux/g [...] discards 097c287c7027 70: onsuccess: #486: 1: Success after binutils/gcc/linux/g [...] discards 4eb682b49a98 69: onsuccess: #485: 1: Success after binutils/gcc/linux/g [...] discards 1920271f141f 68: onsuccess: #484: 1: Success after binutils/gcc/linux/g [...] discards 7ef700a6d738 67: onsuccess: #483: 1: Success after binutils/gcc/linux/g [...] discards 80ff1dd40786 66: onsuccess: #482: 1: Success after binutils/gcc/linux/g [...] discards dd9299ba57df 65: onsuccess: #481: 1: Success after binutils/gcc/linux/g [...] discards fc07457fab14 64: onsuccess: #480: 1: Success after binutils/gcc/linux/g [...] discards df7e9ee3256e 63: onsuccess: #479: 1: Success after binutils/gcc/linux/g [...] discards 83f997f569c7 62: onsuccess: #478: 1: Success after binutils/gcc/linux/g [...] discards 622b914f47d5 61: onsuccess: #477: 1: Success after binutils/gcc/linux/g [...] discards 9af8583fc357 60: onsuccess: #476: 1: Success after binutils/gcc/linux/g [...] discards 7d7522952b41 59: onsuccess: #475: 1: Success after binutils/gcc/linux/g [...] discards c5be521ec2fa 58: onsuccess: #474: 1: Success after binutils/gcc/linux/g [...] discards 5af8d9608157 57: onsuccess: #473: 1: Success after binutils/gcc/linux/g [...] discards 86185577ecca 56: onsuccess: #472: 1: Success after binutils/gcc/linux/g [...] discards a118d715e3dc 55: onsuccess: #471: 1: Success after binutils/gcc/linux/g [...] discards 3d98169cbb99 54: onsuccess: #470: 1: Success after binutils/gcc/linux/g [...] discards e9cfe01c8017 53: onsuccess: #469: 1: Success after binutils/gcc/linux/g [...] discards c4bddc9375fb 52: onsuccess: #467: 1: Success after binutils: 9 commits discards dd1289761e42 51: onsuccess: #464: 1: Success after binutils: 6 commits discards a8a512c3acf9 50: onsuccess: #461: 1: Success after binutils: 12 commits discards 93d4bce7d4f1 49: onsuccess: #459: 1: Success after binutils/gcc/linux/g [...] discards 2fd54201ce2a 48: onsuccess: #458: 1: Success after binutils/gcc/linux/g [...] discards 2b0b12067877 47: onsuccess: #457: 1: Success after binutils/gcc/linux/g [...] discards bccf461b36a6 46: onsuccess: #455: 1: Success after binutils/gcc/linux/g [...] discards 1e46995f1754 45: onsuccess: #454: 1: Success after binutils/gcc/linux/g [...] discards fc3dc72efaee 44: onsuccess: #453: 1: Success after binutils/gcc/glibc/g [...] discards 15499c459145 43: onsuccess: #452: 1: Success after binutils/gcc/linux/g [...] discards 15b6c8a0bd6d 42: onsuccess: #451: 1: Success after binutils/gcc/glibc/g [...] discards fd17274d72f1 41: onsuccess: #450: 1: Success after binutils/gcc/linux/g [...] discards e609be111406 40: onsuccess: #449: 1: Success after glibc-2.36.9000-121- [...] discards 37e68296bf08 39: onsuccess: #447: 1: Success after binutils: 5 commits discards 63b066baadc0 38: onsuccess: #445: 1: Success after glibc-2.36.9000-120- [...] discards 38e139d8dbec 37: onsuccess: #443: 1: Success after binutils: 2 commits discards b2931f68788b 36: onsuccess: #441: 1: Success after binutils/gcc/linux/g [...] discards 44e84bc02aa6 35: onsuccess: #440: 1: Success after binutils/gcc/linux/g [...] discards a56c11a10f30 34: onsuccess: #439: 1: Success after binutils/gcc/linux/g [...] discards fca14f57c720 33: onsuccess: #438: 1: Success after binutils/gcc/linux/g [...] new 0c51c456f4e5 33: onsuccess: #438: 1: Success after binutils/gcc/linux/g [...] new debbdf6fec87 34: onsuccess: #439: 1: Success after binutils/gcc/linux/g [...] new 74e180f528d0 35: onsuccess: #440: 1: Success after binutils/gcc/linux/g [...] new 37d5895fd3d4 36: onsuccess: #441: 1: Success after binutils/gcc/linux/g [...] new 1fccfc7635e8 37: onsuccess: #443: 1: Success after binutils: 2 commits new 4d4fa62eab4c 38: onsuccess: #445: 1: Success after glibc-2.36.9000-120- [...] new 0f88895e59a2 39: onsuccess: #447: 1: Success after binutils: 5 commits new b28ef193affc 40: onsuccess: #449: 1: Success after glibc-2.36.9000-121- [...] new 790b3ee81ec9 41: onsuccess: #450: 1: Success after binutils/gcc/linux/g [...] new e2ab3e5decb4 42: onsuccess: #451: 1: Success after binutils/gcc/glibc/g [...] new 1525447adc1a 43: onsuccess: #452: 1: Success after binutils/gcc/linux/g [...] new 6e20208b0986 44: onsuccess: #453: 1: Success after binutils/gcc/glibc/g [...] new 0b608f931681 45: onsuccess: #454: 1: Success after binutils/gcc/linux/g [...] new 82ee4ea00774 46: onsuccess: #455: 1: Success after binutils/gcc/linux/g [...] new 118f09826b4b 47: onsuccess: #457: 1: Success after binutils/gcc/linux/g [...] new 2d79c9188c07 48: onsuccess: #458: 1: Success after binutils/gcc/linux/g [...] new af55e0ed116e 49: onsuccess: #459: 1: Success after binutils/gcc/linux/g [...] new ae6d2ce8ead7 50: onsuccess: #461: 1: Success after binutils: 12 commits new dce3306fff5a 51: onsuccess: #464: 1: Success after binutils: 6 commits new abe128478517 52: onsuccess: #467: 1: Success after binutils: 9 commits new f47be0348588 53: onsuccess: #469: 1: Success after binutils/gcc/linux/g [...] new 6e4f0a406c9a 54: onsuccess: #470: 1: Success after binutils/gcc/linux/g [...] new 080ab395dc62 55: onsuccess: #471: 1: Success after binutils/gcc/linux/g [...] new 5c007c0858e0 56: onsuccess: #472: 1: Success after binutils/gcc/linux/g [...] new d796275db320 57: onsuccess: #473: 1: Success after binutils/gcc/linux/g [...] new 44cd662e5eed 58: onsuccess: #474: 1: Success after binutils/gcc/linux/g [...] new 07e12dcbcf09 59: onsuccess: #475: 1: Success after binutils/gcc/linux/g [...] new d505e7989ddc 60: onsuccess: #476: 1: Success after binutils/gcc/linux/g [...] new d1702b1c2db4 61: onsuccess: #477: 1: Success after binutils/gcc/linux/g [...] new 48a59c656f3c 62: onsuccess: #478: 1: Success after binutils/gcc/linux/g [...] new 38a06828fc49 63: onsuccess: #479: 1: Success after binutils/gcc/linux/g [...] new add8173434b0 64: onsuccess: #480: 1: Success after binutils/gcc/linux/g [...] new 1e8cff21a164 65: onsuccess: #481: 1: Success after binutils/gcc/linux/g [...] new d8cf22fea5c3 66: onsuccess: #482: 1: Success after binutils/gcc/linux/g [...] new 65580a123bde 67: onsuccess: #483: 1: Success after binutils/gcc/linux/g [...] new 63c31fc0e46c 68: onsuccess: #484: 1: Success after binutils/gcc/linux/g [...] new 490ede91d07f 69: onsuccess: #485: 1: Success after binutils/gcc/linux/g [...] new 77c4364d0ad7 70: onsuccess: #486: 1: Success after binutils/gcc/linux/g [...] new 078311204a09 71: onsuccess: #487: 1: Success after binutils/gcc/linux/g [...] new f52ec0066562 72: onsuccess: #488: 1: Success after binutils/gcc/linux/g [...] new b0e7bedcc7b8 73: onsuccess: #489: 1: Success after binutils/gcc/glibc/g [...] new bed67bee838f 74: onsuccess: #490: 1: Success after binutils/gcc/linux/g [...] new da2095167dd7 75: onsuccess: #491: 1: Success after binutils/gcc/linux/g [...] new 9b82393d2468 76: onsuccess: #492: 1: Success after binutils/gcc/linux/g [...] new 42cbf86e3bd9 77: onsuccess: #493: 1: Success after binutils/gcc/linux/g [...] new 117d78ebbdf8 78: onsuccess: #494: 1: Success after binutils/gcc/linux/g [...] new c6cd4e4c2a63 79: onsuccess: #495: 1: Success after binutils/gcc/linux/g [...] new 8f2422098e9b 80: onsuccess: #496: 1: Success after binutils/gcc/linux/g [...] new 143abc0bb0b2 81: onsuccess: #497: 1: Success after binutils/gcc/linux/g [...] new 0fa68e3d503d 82: onsuccess: #498: 1: Success after binutils/gcc/linux/g [...] new b635aeb1fd4b 83: onsuccess: #499: 1: Success after binutils/gcc/linux/g [...] new 94425cc3f68f 84: onsuccess: #500: 1: Success after binutils/gcc/linux/g [...] new dce3f68ddb53 85: onsuccess: #501: 1: Success after binutils/gcc/linux/g [...] new 8552ab43e583 86: onsuccess: #503: 1: Success after binutils: 12 commits new 375f504a145f 87: onsuccess: #505: 1: Success after glibc: 7 commits new 0418e4eb62a3 88: onsuccess: #506: 1: Success after linux: 34 commits new 5c38a39f9382 89: onsuccess: #508: 1: Success after binutils: 12 commits new 9e69f4d24f87 90: onsuccess: #510: 1: Success after glibc: 5 commits new 78714e597419 91: onsuccess: #511: 1: Success after linux: 27 commits new 498d6d6a0464 92: onsuccess: #512: 1: Success after binutils/gcc/linux/g [...] new 579392452ce1 93: onsuccess: #513: 1: Success after binutils/gcc/linux/g [...] new ab3a8c4189b2 94: onsuccess: #514: 1: Success after binutils/gcc/linux/g [...] new 6eea2149eb01 95: onsuccess: #515: 1: Success after binutils/gcc/linux/g [...] new 2be185d9de16 96: onsuccess: #516: 1: Success after binutils/gcc/linux/g [...] new 6347d051d894 97: onsuccess: #517: 1: Success after binutils/gcc/linux/g [...] new be6b9ba0d058 98: onsuccess: #518: 1: Success after binutils/gcc/linux/g [...] new fd0e46e2a1ef 99: onsuccess: #519: 1: Success after binutils/gcc/linux/g [...] new 28568691eae4 100: onsuccess: #521: 1: Success after binutils: 10 commits new 8ace3b5b06fe 101: onsuccess: #524: 1: Success after binutils: 2 commits new 614b4bcd7faa 102: onsuccess: #527: 1: Success after binutils: 5 commits new 16d5d2118649 103: onsuccess: #529: 1: Success after binutils/gcc/linux/ [...] new cb396d49e99b 104: onsuccess: #530: 1: Success after gcc: 7 commits new bf7ceed54571 105: onsuccess: #531: 1: Success after binutils/gcc/linux/ [...] new cfceaac147f2 106: onsuccess: #532: 1: Success after binutils/gcc/linux/ [...] new 241cf1b412ed 107: onsuccess: #533: 1: Success after binutils/gcc/linux/ [...] new fe6dd4e54d8e 108: onsuccess: #534: 1: Success after binutils/gcc/linux/ [...] new 5990f67c7766 109: onsuccess: #535: 1: Success after binutils/gcc/linux/ [...] new 97c2e79c29c3 110: onsuccess: #536: 1: Success after binutils/gcc/glibc/ [...] new 27c3971f5cb4 111: onsuccess: #537: 1: Success after binutils/gcc/gdb: 6 [...] new 19d67c9fbb3a 112: onsuccess: #538: 1: Success after binutils/gcc/linux/ [...] new 240eccf21ce0 113: onsuccess: #539: 1: Success after binutils/gcc/linux/ [...] new 4c4e7f6b3dfb 114: onsuccess: #541: 1: Success after binutils/gcc/linux/ [...] new a2a9f234284f 115: onsuccess: #542: 1: Success after binutils/gcc/linux/ [...] new 42199b8af0b2 116: onsuccess: #543: 1: Success after binutils/gcc/linux/ [...] new c99565536efd 117: onsuccess: #544: 1: Success after binutils/gcc/linux/ [...] new 4db0d310dfa4 118: onsuccess: #545: 1: Success after binutils/gcc/linux/ [...] new 70033d85242c 119: onsuccess: #546: 1: Success after binutils/gcc/linux/ [...] new d3b0527f3dcc 120: onsuccess: #547: 1: Success after binutils/gcc/linux/ [...] new ff748e5ab126 121: onsuccess: #548: 1: Success after binutils/gcc/linux/ [...] new 0696d52d5204 122: onsuccess: #549: 1: Success after binutils/gcc/linux/ [...] new 968d1e64e66f 123: onsuccess: #550: 1: Success after binutils/gcc/linux/ [...] new 8282a44dd96d 124: onsuccess: #551: 1: Success after binutils/gcc/linux/ [...] new f17333b4bfe4 125: onsuccess: #552: 1: Success after binutils/gcc/linux/ [...] new 60204071b2a0 126: onsuccess: #553: 1: Success after binutils/gcc/linux/ [...] new cc89c34c0f4e 127: onsuccess: #554: 1: Success after binutils/gcc/linux/ [...] new 9f55e9f3f06a 128: onsuccess: #555: 1: Success after binutils/gcc/linux/ [...] new d66e8acad7fe 129: onsuccess: #556: 1: Success after binutils/gcc/linux/ [...] new 474123d23f54 130: onsuccess: #557: 1: Success after binutils/gcc/linux/ [...] new 75fb6a8bd63c 131: onsuccess: #558: 1: Success after binutils/gcc/linux/ [...] new 213a224afa11 132: onsuccess: #559: 1: Success after binutils/gcc/linux/ [...] new f0d470245b29 133: onsuccess: #560: 1: Success after binutils/gcc/linux/ [...] new 9e45d4f8e96b 134: onsuccess: #561: 1: Success after binutils/gcc/linux/ [...] 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 (7a9c1a2b4c64) \ N -- N -- N refs/heads/linaro-local/ci/tcwg_gnu_native_check_binutil [...] 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 1732 -> 1728 bytes 02-prepare_abe/console.log.xz | Bin 2752 -> 2768 bytes 03-build_abe-binutils/console.log.xz | Bin 53040 -> 54160 bytes 04-build_abe-gcc/console.log.xz | Bin 233880 -> 234536 bytes 05-clean_sysroot/console.log.xz | Bin 316 -> 316 bytes 06-build_abe-linux/console.log.xz | Bin 8836 -> 8692 bytes 07-build_abe-glibc/console.log.xz | Bin 236408 -> 234588 bytes 08-build_abe-gdb/console.log.xz | Bin 51920 -> 52504 bytes 09-build_abe-dejagnu/console.log.xz | Bin 3840 -> 3824 bytes 10-build_abe-check_binutils/console.log.xz | Bin 2448 -> 2628 bytes 11-check_regression/console.log.xz | Bin 6280 -> 5932 bytes 11-check_regression/results.compare | 8 +- 11-check_regression/results.compare2 | 16 +- 12-update_baseline/console.log | 60 ++--- dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- git/gdb_rev | 2 +- git/linux_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 2 +- mail/mail-subject.txt | 2 +- manifest.sh | 32 +-- sumfiles/binutils.log.xz | Bin 62488 -> 62996 bytes sumfiles/binutils.sum | 65 +++--- sumfiles/gas.log.xz | Bin 100532 -> 100400 bytes sumfiles/gas.sum | 272 +++++++++++------------ sumfiles/ld.log.xz | Bin 131620 -> 131564 bytes sumfiles/ld.sum | 344 ++++++++++++++--------------- 29 files changed, 407 insertions(+), 406 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 5 months

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_kernel/gnu-master-aarch64-stable-allnoconfig updated (cdeca3422d22 -> 052e20688f3c)

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-aarch64-stable-allnoconfig in repository toolchain/ci/base-artifacts. from cdeca3422d22 28: onsuccess: #478: boot: Success after binutils/gcc: 94 commits new 052e20688f3c 29: onsuccess: #479: boot: Success after binutils/gcc/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 1748 -> 1760 bytes 02-prepare_abe/console.log.xz | Bin 2776 -> 2760 bytes 03-build_abe-binutils/console.log.xz | Bin 32268 -> 32360 bytes 04-build_abe-stage1/console.log.xz | Bin 73264 -> 73456 bytes 05-build_abe-qemu/console.log.xz | Bin 30916 -> 31836 bytes 06-build_linux/console.log.xz | Bin 4924 -> 4908 bytes 08-check_regression/console.log.xz | Bin 3404 -> 4408 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 +++++++++++++++--------------- 16 files changed, 23 insertions(+), 23 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 5 months

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

Tcwg-commits December 2022