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 3943ef17c3 145: onsuccess: #2180: 1: Success after binutils/gcc/linux/g [...] discards 787481397c 144: onsuccess: #2179: 1: Success after binutils/gcc/linux/g [...] discards 5dfe1e8c9d 143: onsuccess: #2178: 1: Success after binutils/gcc/gdb/qem [...] discards dc2283d773 142: onsuccess: #2177: 1: Success after gcc/glibc: 4 commits discards e7d681620f 141: onsuccess: #2176: 1: Success after binutils/gcc/gdb: 6 commits discards 5431a7d60f 140: onsuccess: #2175: 1: Success after binutils/gcc/linux/g [...] discards 99f1bb7fec 139: onsuccess: #2174: 1: Success after binutils/gcc/gdb: 13 [...] discards 16b9b0c344 138: onsuccess: #2173: 1: Success after binutils/gcc/gdb: 5 commits discards 505b00255f 137: onsuccess: #2172: 1: Success after binutils/gcc/linux/g [...] discards 3d99b06d8a 136: onsuccess: #2171: 1: Success after binutils/gcc/gdb/qem [...] discards 8beaa9ac8c 135: onsuccess: #2170: 1: Success after gcc/linux/qemu: 63 commits discards 64a71d5d96 134: onsuccess: #2169: 1: Success after binutils/gcc/gdb: 13 [...] discards 8fbb5b9f96 133: onsuccess: #2168: 1: Success after binutils/gcc/linux/g [...] discards c60979b242 132: onsuccess: #2167: 1: Success after binutils/gcc/glibc/g [...] discards 1f106314c6 131: onsuccess: #2166: 1: Success after binutils/gcc/gdb: 12 [...] discards dc2d559315 130: onsuccess: #2165: 1: Success after binutils/gcc/gdb: 32 [...] discards 3cc39e45d8 129: onsuccess: #2164: 1: Success after binutils/gcc/linux/g [...] discards 1cedef2da6 128: onsuccess: #2163: 1: Success after linux: 23 commits discards 5f9a3b9946 127: onsuccess: #2162: 1: Success after gcc: 9 commits discards b36a3219e6 126: onsuccess: #2161: 1: Success after basepoints/gcc-13-28 [...] discards 9059c2b63b 125: onsuccess: #2160: 1: Success after binutils/gcc/linux/g [...] discards 7484b3c9c7 124: onsuccess: #2159: 1: Success after linux: 23 commits discards 901d3006af 123: onsuccess: #2158: 1: Success after basepoints/gcc-13-28 [...] discards 4348a3c025 122: onsuccess: #2157: 1: Success after binutils/gcc/gdb: 6 commits discards 0e44afa5ae 121: onsuccess: #2156: 1: Success after binutils/gcc/linux/g [...] discards 69935ab006 120: onsuccess: #2155: 1: Success after binutils/gcc/linux/g [...] discards 0f9cbcfe65 119: onsuccess: #2154: 1: Success after binutils/gcc/linux/g [...] discards a905f9eb34 118: onsuccess: #2151: 1: Success after binutils/gcc/linux/g [...] discards 986702590c 117: onsuccess: #2150: 1: Success after binutils/gcc/glibc/g [...] discards f9dbedf1c8 116: onsuccess: #2148: 1: Success after binutils/gcc/gdb: 7 commits discards 0156404bc9 115: onsuccess: #2147: 1: Success after binutils/linux/glibc [...] discards 53f41d8e41 114: onsuccess: #2146: 1: Success after binutils/gcc/glibc/g [...] discards 5181a21259 113: onsuccess: #2145: 1: Success after binutils/gcc/glibc/g [...] discards 4a2e9decc2 112: onsuccess: #2144: 1: Success after binutils/gcc/glibc/g [...] discards e3e912cf3f 111: onsuccess: #2143: 1: Success after binutils/gcc/linux/g [...] discards b05dfc05d3 110: onsuccess: #2142: 1: Success after binutils/gcc/glibc/g [...] discards e595e5ffd4 109: onsuccess: #2141: 1: Success after gcc/glibc: 6 commits discards cd45df225a 108: onsuccess: #2140: 1: Success after binutils/gcc/gdb: 5 commits discards 0d19cdf1f2 107: onsuccess: #2139: 1: Success after binutils/gcc/gdb: 3 commits discards 39acccc973 106: onsuccess: #2138: 1: Success after binutils/gcc/glibc/g [...] discards c4d2350b3c 105: onsuccess: #2137: 1: Success after basepoints/gcc-13-27 [...] discards ba073081f2 104: onsuccess: #2136: 1: Success after binutils/gcc/gdb: 3 commits discards ddd8788c48 103: onsuccess: #2135: 1: Success after gcc/linux/glibc/gdb/ [...] discards 878127e2d0 102: onsuccess: #2133: 1: Success after gdb-12-branchpoint-1 [...] discards cf6413bf20 101: onsuccess: #2130: 1: Success after binutils: 81 commits discards dc320e504a 100: onsuccess: #2077: 1: Success after binutils/gcc/linux/g [...] discards 51e592e2f1 99: onsuccess: #2074: 1: Success after baseline build: no ne [...] discards 1654b1d68b 98: onsuccess: #2073: 1: Success after gcc/linux: 11 commits discards f9a032c510 97: onsuccess: #2072: 1: Success after binutils/gcc/gdb: 3 commits discards e6c47c7bf6 96: onsuccess: #2071: 1: Success after gcc/linux: 56 commits discards 89d38dcad3 95: onsuccess: #2070: 1: Success after basepoints/gcc-13-238 [...] discards 43bfd02c40 94: onsuccess: 1: Success after gcc: openmp: Partial OpenMP [...] discards 6e41d0dbc8 93: onsuccess: 1: Success after binutils/gcc/linux/gdb: 88 commits discards 04cb8b2b6a 92: onsuccess: 1: Success after binutils/gcc/linux/gdb/qemu: [...] discards cba44c13f4 91: onsuccess: 1: Success after binutils/gcc/gdb: 8 commits discards da3f10b913 90: onsuccess: 1: Success after binutils/gcc/gdb: 19 commits discards 8665cdc360 89: onsuccess: 1: Success after binutils/gcc/gdb: 5 commits discards 5d39123d1d 88: onsuccess: 1: Success after gcc/linux/qemu: 149 commits discards 89cea660f7 87: onsuccess: 1: Success after binutils/gcc/gdb: 14 commits discards 593d153e9b 86: onsuccess: 1: Success after binutils/gcc/gdb: 7 commits discards 1f5ee70afe 85: onsuccess: 1: Success after binutils/gcc/glibc/gdb/qemu: [...] discards 785deca647 84: onsuccess: 1: Success after binutils/gcc/linux/gdb: 68 commits discards 2077b478bd 83: onsuccess: 1: Success after binutils/gcc/glibc/gdb: 17 commits discards 2e19f43b5e 82: onsuccess: 1: Successful build after binutils/gcc/gdb: 1 [...] discards 137da7954d 81: onsuccess: 1: Successful build after binutils/gcc/gdb: 6 [...] discards d1cc036524 80: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] discards 70e87cb461 79: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] discards 3f5ea8ccf3 78: onsuccess: 1: Successful build after binutils/gcc/gdb: 4 [...] discards 0e87defb6d 77: onsuccess: 1: Successful build after gcc/linux/glibc: 22 [...] discards 0c08bef861 76: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 7dc0771d39 75: onsuccess: 1: Successful build after linux: 44 commits discards 8ed00318f2 74: onsuccess: 1: Successful build after binutils/gdb: 2 commits discards 5148cc9cfc 73: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards bb29e2732e 72: onsuccess: 1: Successful build after linux: 12 commits discards 84494f2f72 71: onsuccess: 1: Successful build after gcc/glibc: 3 commits discards a2de583ccf 70: onsuccess: 1: Successful build after binutils/gcc/gdb: 4 [...] discards 75d33ee957 69: onsuccess: 1: Successful build after binutils/gcc/gdb: 5 [...] discards cfa25305ab 68: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 1b68c19ffa 67: onsuccess: 1: Successful build after binutils/gcc/gdb: 1 [...] discards d439142b2e 66: onsuccess: 1: Successful build after gcc/glibc: 10 commits discards 08155e106c 65: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards d62e56a854 64: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards b9def31c05 63: onsuccess: 1: Successful build after binutils/gcc/gdb: 8 [...] discards 88bc304076 62: onsuccess: 1: Successful build after binutils/gcc/gdb: 2 [...] discards 17775cfbad 61: onsuccess: 1: Successful build after binutils/gcc/gdb/qe [...] discards ee141547be 60: onsuccess: 1: Successful build after glibc: 2 commits discards e08e809406 59: onsuccess: 1: Successful build after binutils: 2 commits discards 408a03c40b 58: onsuccess: 1: Successful build after binutils: gdb: new [...] discards 750b7d20db 57: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] discards 9e629da782 56: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards a02e4b37cc 55: onsuccess: 1: Successful build after gcc/linux/glibc/qem [...] discards 3b72d5e8f2 54: onsuccess: 1: Successful build after binutils/gcc/gdb: 8 [...] discards c1c2961d04 53: onsuccess: 1: Successful build after binutils/gcc/gdb: 8 [...] discards 74d6dfc93b 52: onsuccess: 1: Successful build after binutils/gcc/gdb: 7 [...] discards 540dd0d969 51: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards a96bbf4538 50: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] discards 866a8a9e4b 49: onsuccess: 1: Successful build after gcc/glibc: 5 commits discards a7954c698e 48: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 9a46de5cb9 47: onsuccess: 1: Successful build after linux: 10 commits discards 8cd2a5c101 46: onsuccess: 1: Successful build after binutils/gdb: 2 commits discards b3b34b6601 45: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 2ef72516c7 45: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new a695757ec4 46: onsuccess: 1: Successful build after binutils/gdb: 2 commits new 5960da2622 47: onsuccess: 1: Successful build after linux: 10 commits new cb99b1e51b 48: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new e14194f051 49: onsuccess: 1: Successful build after gcc/glibc: 5 commits new 83c3e83347 50: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] new b6edb5a4c3 51: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new c477254496 52: onsuccess: 1: Successful build after binutils/gcc/gdb: 7 [...] new 038acc2abe 53: onsuccess: 1: Successful build after binutils/gcc/gdb: 8 [...] new 2624f828fa 54: onsuccess: 1: Successful build after binutils/gcc/gdb: 8 [...] new ca110a7e51 55: onsuccess: 1: Successful build after gcc/linux/glibc/qem [...] new 2bb14a88c9 56: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 85ecac66dd 57: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] new 465b185a13 58: onsuccess: 1: Successful build after binutils: gdb: new [...] new a4bb5182b1 59: onsuccess: 1: Successful build after binutils: 2 commits new a7f482a89a 60: onsuccess: 1: Successful build after glibc: 2 commits new 856e9bd614 61: onsuccess: 1: Successful build after binutils/gcc/gdb/qe [...] new 3adcfae811 62: onsuccess: 1: Successful build after binutils/gcc/gdb: 2 [...] new 0481103e1f 63: onsuccess: 1: Successful build after binutils/gcc/gdb: 8 [...] new 4e30d63fcc 64: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 65f4bb13b3 65: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 65b9da04d6 66: onsuccess: 1: Successful build after gcc/glibc: 10 commits new 6b8d5f5fcb 67: onsuccess: 1: Successful build after binutils/gcc/gdb: 1 [...] new aa8b0bcf5c 68: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new ae485b8a65 69: onsuccess: 1: Successful build after binutils/gcc/gdb: 5 [...] new a6ce167a72 70: onsuccess: 1: Successful build after binutils/gcc/gdb: 4 [...] new 26559f8df7 71: onsuccess: 1: Successful build after gcc/glibc: 3 commits new 195c2dc6bf 72: onsuccess: 1: Successful build after linux: 12 commits new b070241808 73: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new f6031352a9 74: onsuccess: 1: Successful build after binutils/gdb: 2 commits new 088c8d79eb 75: onsuccess: 1: Successful build after linux: 44 commits new 0f218c61ae 76: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 1091bd92c2 77: onsuccess: 1: Successful build after gcc/linux/glibc: 22 [...] new a325b28438 78: onsuccess: 1: Successful build after binutils/gcc/gdb: 4 [...] new b8548e5629 79: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] new bbb617d110 80: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] new 393f1385a3 81: onsuccess: 1: Successful build after binutils/gcc/gdb: 6 [...] new 735409b1c0 82: onsuccess: 1: Successful build after binutils/gcc/gdb: 1 [...] new 499e525f55 83: onsuccess: 1: Success after binutils/gcc/glibc/gdb: 17 commits new 6505f81338 84: onsuccess: 1: Success after binutils/gcc/linux/gdb: 68 commits new f9deeebfde 85: onsuccess: 1: Success after binutils/gcc/glibc/gdb/qemu: [...] new e4d501029d 86: onsuccess: 1: Success after binutils/gcc/gdb: 7 commits new 44cbb6f96a 87: onsuccess: 1: Success after binutils/gcc/gdb: 14 commits new 05c29611ad 88: onsuccess: 1: Success after gcc/linux/qemu: 149 commits new 0ab04b094f 89: onsuccess: 1: Success after binutils/gcc/gdb: 5 commits new 5e023ffd5f 90: onsuccess: 1: Success after binutils/gcc/gdb: 19 commits new 787fa0bb2f 91: onsuccess: 1: Success after binutils/gcc/gdb: 8 commits new 3cb40ffd40 92: onsuccess: 1: Success after binutils/gcc/linux/gdb/qemu: [...] new eb10c166e8 93: onsuccess: 1: Success after binutils/gcc/linux/gdb: 88 commits new 670abe78f7 94: onsuccess: 1: Success after gcc: openmp: Partial OpenMP [...] new 2aab5aa631 95: onsuccess: #2070: 1: Success after basepoints/gcc-13-238 [...] new 07b72a3121 96: onsuccess: #2071: 1: Success after gcc/linux: 56 commits new bd672fd8eb 97: onsuccess: #2072: 1: Success after binutils/gcc/gdb: 3 commits new b4dec405d7 98: onsuccess: #2073: 1: Success after gcc/linux: 11 commits new 193b53cea9 99: onsuccess: #2074: 1: Success after baseline build: no ne [...] new a0933cf32e 100: onsuccess: #2077: 1: Success after binutils/gcc/linux/g [...] new bad8bc65ca 101: onsuccess: #2130: 1: Success after binutils: 81 commits new cd91565b42 102: onsuccess: #2133: 1: Success after gdb-12-branchpoint-1 [...] new ba3540a46f 103: onsuccess: #2135: 1: Success after gcc/linux/glibc/gdb/ [...] new 1f8a394fcd 104: onsuccess: #2136: 1: Success after binutils/gcc/gdb: 3 commits new 021b28098f 105: onsuccess: #2137: 1: Success after basepoints/gcc-13-27 [...] new e28b50f915 106: onsuccess: #2138: 1: Success after binutils/gcc/glibc/g [...] new 76a9633b1c 107: onsuccess: #2139: 1: Success after binutils/gcc/gdb: 3 commits new 4a2a8017aa 108: onsuccess: #2140: 1: Success after binutils/gcc/gdb: 5 commits new f6c395c20c 109: onsuccess: #2141: 1: Success after gcc/glibc: 6 commits new 19aa25fadb 110: onsuccess: #2142: 1: Success after binutils/gcc/glibc/g [...] new 8b7a16c9f8 111: onsuccess: #2143: 1: Success after binutils/gcc/linux/g [...] new 7dff448db6 112: onsuccess: #2144: 1: Success after binutils/gcc/glibc/g [...] new dc7a58411c 113: onsuccess: #2145: 1: Success after binutils/gcc/glibc/g [...] new cf969cf480 114: onsuccess: #2146: 1: Success after binutils/gcc/glibc/g [...] new 9734bad17a 115: onsuccess: #2147: 1: Success after binutils/linux/glibc [...] new ae140e38bd 116: onsuccess: #2148: 1: Success after binutils/gcc/gdb: 7 commits new 5e5edfa25d 117: onsuccess: #2150: 1: Success after binutils/gcc/glibc/g [...] new 76f7a2420a 118: onsuccess: #2151: 1: Success after binutils/gcc/linux/g [...] new 695f1e5ca3 119: onsuccess: #2154: 1: Success after binutils/gcc/linux/g [...] new 804460c7a7 120: onsuccess: #2155: 1: Success after binutils/gcc/linux/g [...] new e49f69bd77 121: onsuccess: #2156: 1: Success after binutils/gcc/linux/g [...] new e0211ec63b 122: onsuccess: #2157: 1: Success after binutils/gcc/gdb: 6 commits new 0fb72c13f7 123: onsuccess: #2158: 1: Success after basepoints/gcc-13-28 [...] new c7a803fbde 124: onsuccess: #2159: 1: Success after linux: 23 commits new 989a64da38 125: onsuccess: #2160: 1: Success after binutils/gcc/linux/g [...] new afd72f6849 126: onsuccess: #2161: 1: Success after basepoints/gcc-13-28 [...] new 92beeec99c 127: onsuccess: #2162: 1: Success after gcc: 9 commits new 41db5ca3ba 128: onsuccess: #2163: 1: Success after linux: 23 commits new dfa85ca827 129: onsuccess: #2164: 1: Success after binutils/gcc/linux/g [...] new cb5b05b93b 130: onsuccess: #2165: 1: Success after binutils/gcc/gdb: 32 [...] new 057b30ba76 131: onsuccess: #2166: 1: Success after binutils/gcc/gdb: 12 [...] new 56da5b2424 132: onsuccess: #2167: 1: Success after binutils/gcc/glibc/g [...] new 0318f655ee 133: onsuccess: #2168: 1: Success after binutils/gcc/linux/g [...] new c9566ff76e 134: onsuccess: #2169: 1: Success after binutils/gcc/gdb: 13 [...] new 28f296f525 135: onsuccess: #2170: 1: Success after gcc/linux/qemu: 63 commits new f53f625404 136: onsuccess: #2171: 1: Success after binutils/gcc/gdb/qem [...] new 34f6d3ceed 137: onsuccess: #2172: 1: Success after binutils/gcc/linux/g [...] new 488c7164e9 138: onsuccess: #2173: 1: Success after binutils/gcc/gdb: 5 commits new a1873116c7 139: onsuccess: #2174: 1: Success after binutils/gcc/gdb: 13 [...] new 4640c42d5b 140: onsuccess: #2175: 1: Success after binutils/gcc/linux/g [...] new 0fd7c8e4cd 141: onsuccess: #2176: 1: Success after binutils/gcc/gdb: 6 commits new d0f0ea2279 142: onsuccess: #2177: 1: Success after gcc/glibc: 4 commits new 83b8444a9b 143: onsuccess: #2178: 1: Success after binutils/gcc/gdb/qem [...] new 00b5a297ae 144: onsuccess: #2179: 1: Success after binutils/gcc/linux/g [...] new 2d06ee2311 145: onsuccess: #2180: 1: Success after binutils/gcc/linux/g [...] new 2215e7f30b 146: onsuccess: #2181: 1: Success after binutils/glibc/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 (3943ef17c3) \ 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 1696 -> 1700 bytes 02-prepare_abe/console.log.xz | Bin 2728 -> 2740 bytes 03-build_abe-binutils/console.log.xz | Bin 30300 -> 30304 bytes 04-build_abe-stage1/console.log.xz | Bin 72300 -> 72600 bytes 06-build_abe-linux/console.log.xz | Bin 8472 -> 8484 bytes 07-build_abe-glibc/console.log.xz | Bin 239608 -> 239776 bytes 08-build_abe-stage2/console.log.xz | Bin 202884 -> 203040 bytes 09-build_abe-gdb/console.log.xz | Bin 37496 -> 37412 bytes 10-build_abe-qemu/console.log.xz | Bin 31904 -> 31900 bytes 11-build_abe-dejagnu/console.log.xz | Bin 3876 -> 3888 bytes 12-build_abe-check_gcc/console.log.xz | Bin 2784 -> 2808 bytes 13-check_regression/console.log.xz | Bin 8936 -> 8132 bytes 13-check_regression/extra-bisect-params | 2 +- 13-check_regression/fails.sum | 49 +- 13-check_regression/mail-body.txt | 126 +- 13-check_regression/results.compare | 49 +- 13-check_regression/results.compare2 | 314 +-- 13-check_regression/results.regressions | 49 +- 14-update_baseline/console.log | 58 +- dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gdb_rev | 2 +- git/glibc_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 128 +- mail/mail-subject.txt | 2 +- manifest.sh | 34 +- results | 49 +- sumfiles/g++.log.xz | Bin 3439504 -> 3408532 bytes sumfiles/g++.sum | 63 +- sumfiles/gcc.log.xz | Bin 3011328 -> 3029088 bytes sumfiles/gcc.sum | 4603 +++++++++++++++---------------- sumfiles/gfortran.log.xz | Bin 1035292 -> 1028292 bytes sumfiles/gfortran.sum | 2 +- sumfiles/libatomic.log.xz | Bin 2288 -> 2300 bytes sumfiles/libatomic.sum | 2 +- sumfiles/libgomp.log.xz | Bin 202308 -> 202120 bytes sumfiles/libgomp.sum | 2 +- sumfiles/libitm.log.xz | Bin 2660 -> 2664 bytes sumfiles/libitm.sum | 2 +- sumfiles/libstdc++.log.xz | Bin 425728 -> 428316 bytes sumfiles/libstdc++.sum | 8 +- 42 files changed, 2734 insertions(+), 2818 deletions(-)