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 383699d8f7 184: onsuccess: #2288: 1: Success after binutils/gcc/linux/g [...] discards 63b884b89f 183: onsuccess: #2270: 1: Success after binutils/gcc/linux/g [...] discards 1279b0b5dc 182: onsuccess: #2247: 1: Success after binutils/gcc/linux/g [...] discards 70630e8a04 181: onsuccess: #2239: 1: Success after binutils/gcc/linux/g [...] discards 78639c79c9 180: onsuccess: #2232: 1: Success after binutils/gcc/glibc/g [...] discards ce5d84c863 179: onsuccess: #2230: 1: Success after binutils/gcc/linux/g [...] discards c136c7c65f 178: onsuccess: #2217: 1: Success after binutils/gcc/linux/g [...] discards 2312dc145f 177: onsuccess: #2212: 1: Success after binutils/gdb: 2 commits discards 86e84608b3 176: onsuccess: #2211: 1: Success after binutils/gcc/linux/g [...] discards cdfec58809 175: onsuccess: #2210: 1: Success after binutils/gcc/linux/g [...] discards e63bce3a3f 174: onsuccess: #2209: 1: Success after binutils/gcc/gdb: 20 [...] discards 81a084d602 173: onsuccess: #2208: 1: Success after gcc: 10 commits discards 40e4aeca60 172: onsuccess: #2207: 1: Success after binutils/gcc/linux/g [...] discards 0bccd32dd0 171: onsuccess: #2206: 1: Success after binutils/gcc/linux/g [...] discards 5da6ebd265 170: onsuccess: #2205: 1: Success after binutils/gcc/glibc/g [...] discards 759a212437 169: onsuccess: #2204: 1: Success after binutils/gcc/glibc/g [...] discards 5b4b4334be 168: onsuccess: #2203: 1: Success after binutils/gcc/glibc/g [...] discards 16330ac1c6 167: onsuccess: #2202: 1: Success after gcc/linux/glibc/qemu [...] discards e4427e6412 166: onsuccess: #2201: 1: Success after gcc/glibc/qemu: 40 commits discards 73558e8f82 165: onsuccess: #2200: 1: Success after binutils/gdb: 8 commits discards c9ef789a00 164: onsuccess: #2199: 1: Success after binutils/gcc/linux/g [...] discards 84dc18f124 163: onsuccess: #2198: 1: Success after binutils/gcc/linux/g [...] discards c2111d5a5f 162: onsuccess: #2197: 1: Success after binutils/gcc/glibc/g [...] discards c4dbe88bb8 161: onsuccess: #2196: 1: Success after binutils/gcc/linux/g [...] discards dbcb3b8553 160: onsuccess: #2195: 1: Success after binutils/gcc/linux/g [...] discards def5c1755b 159: onsuccess: #2194: 1: Success after gcc/linux/glibc: 197 [...] discards b28d28d89f 158: onsuccess: #2193: 1: Success after binutils/gcc/glibc/g [...] discards 2318252cca 157: onsuccess: #2192: 1: Success after binutils/gcc/gdb: 8 commits discards ec62d48000 156: onsuccess: #2191: 1: Success after binutils/gcc/linux/g [...] discards 5f679242e9 155: onsuccess: #2190: 1: Success after binutils/gcc/linux/g [...] discards 0a5d52e988 154: onsuccess: #2189: 1: Success after binutils/gcc/gdb: 18 [...] discards 7dbb069571 153: onsuccess: #2188: 1: Success after binutils/gcc/gdb: 3 commits discards a0c17159dc 152: onsuccess: #2187: 1: Success after gcc/linux/glibc: 22 commits discards 7d6f442ff1 151: onsuccess: #2186: 1: Success after gcc: 2 commits discards 0226adada9 150: onsuccess: #2185: 1: Success after gcc: 3 commits discards 1be63980a3 149: onsuccess: #2184: 1: Success after binutils/gcc/linux/g [...] discards 79c2a1ad26 148: onsuccess: #2183: 1: Success after gcc/linux/glibc: 64 commits discards 80f03bbe86 147: onsuccess: #2182: 1: Success after binutils/gcc/gdb: 18 [...] discards ab3c760ade 146: onsuccess: #2181: 1: Success after binutils/glibc/gdb: [...] discards 3e1c53b7d2 145: onsuccess: #2180: 1: Success after binutils/gcc/linux/g [...] discards 0108fece0d 144: onsuccess: #2179: 1: Success after binutils/gcc/linux/g [...] discards de53bcfba2 143: onsuccess: #2178: 1: Success after binutils/gcc/gdb/qem [...] discards db7b9122cd 142: onsuccess: #2177: 1: Success after gcc/glibc: 4 commits discards dd8b6c596b 141: onsuccess: #2176: 1: Success after binutils/gcc/gdb: 6 commits discards 761dab0b2b 140: onsuccess: #2175: 1: Success after binutils/gcc/linux/g [...] discards 72bd900481 139: onsuccess: #2174: 1: Success after binutils/gcc/gdb: 13 [...] discards adef381f16 138: onsuccess: #2173: 1: Success after binutils/gcc/gdb: 5 commits discards 2c4602ec63 137: onsuccess: #2172: 1: Success after binutils/gcc/linux/g [...] discards 4f7464d68a 136: onsuccess: #2171: 1: Success after binutils/gcc/gdb/qem [...] discards bcbd399319 135: onsuccess: #2170: 1: Success after gcc/linux/qemu: 63 commits discards 374526d474 134: onsuccess: #2169: 1: Success after binutils/gcc/gdb: 13 [...] discards d6bd09caae 133: onsuccess: #2168: 1: Success after binutils/gcc/linux/g [...] discards 750f48f612 132: onsuccess: #2167: 1: Success after binutils/gcc/glibc/g [...] discards 1032ebe30f 131: onsuccess: #2166: 1: Success after binutils/gcc/gdb: 12 [...] discards ef08b86179 130: onsuccess: #2165: 1: Success after binutils/gcc/gdb: 32 [...] discards 2f8aee780d 129: onsuccess: #2164: 1: Success after binutils/gcc/linux/g [...] discards 483ec00c82 128: onsuccess: #2163: 1: Success after linux: 23 commits discards 6d89a54beb 127: onsuccess: #2162: 1: Success after gcc: 9 commits discards 096c371683 126: onsuccess: #2161: 1: Success after basepoints/gcc-13-28 [...] discards a98b9ba295 125: onsuccess: #2160: 1: Success after binutils/gcc/linux/g [...] discards 33dd3fe765 124: onsuccess: #2159: 1: Success after linux: 23 commits discards cb3a6b1c3b 123: onsuccess: #2158: 1: Success after basepoints/gcc-13-28 [...] discards fb938c5205 122: onsuccess: #2157: 1: Success after binutils/gcc/gdb: 6 commits discards 7fd826deca 121: onsuccess: #2156: 1: Success after binutils/gcc/linux/g [...] discards a4fb6984c1 120: onsuccess: #2155: 1: Success after binutils/gcc/linux/g [...] discards 61cbd20406 119: onsuccess: #2154: 1: Success after binutils/gcc/linux/g [...] discards d9b741c2f5 118: onsuccess: #2151: 1: Success after binutils/gcc/linux/g [...] discards bbcac8ed52 117: onsuccess: #2150: 1: Success after binutils/gcc/glibc/g [...] discards 11de982c42 116: onsuccess: #2148: 1: Success after binutils/gcc/gdb: 7 commits discards 24abb9333a 115: onsuccess: #2147: 1: Success after binutils/linux/glibc [...] discards b15cad8ee3 114: onsuccess: #2146: 1: Success after binutils/gcc/glibc/g [...] discards 05fb58be8b 113: onsuccess: #2145: 1: Success after binutils/gcc/glibc/g [...] discards de5bf05de3 112: onsuccess: #2144: 1: Success after binutils/gcc/glibc/g [...] discards df0ae7ec05 111: onsuccess: #2143: 1: Success after binutils/gcc/linux/g [...] discards 5275b74533 110: onsuccess: #2142: 1: Success after binutils/gcc/glibc/g [...] discards 995ab3bce7 109: onsuccess: #2141: 1: Success after gcc/glibc: 6 commits discards e146ac504b 108: onsuccess: #2140: 1: Success after binutils/gcc/gdb: 5 commits discards e3477defbd 107: onsuccess: #2139: 1: Success after binutils/gcc/gdb: 3 commits discards 4c114ed50e 106: onsuccess: #2138: 1: Success after binutils/gcc/glibc/g [...] discards 4b0c5b0bc9 105: onsuccess: #2137: 1: Success after basepoints/gcc-13-27 [...] discards 4a3dc40ab2 104: onsuccess: #2136: 1: Success after binutils/gcc/gdb: 3 commits discards 84acc47491 103: onsuccess: #2135: 1: Success after gcc/linux/glibc/gdb/ [...] discards f5ad770f52 102: onsuccess: #2133: 1: Success after gdb-12-branchpoint-1 [...] discards cc7b7b54ca 101: onsuccess: #2130: 1: Success after binutils: 81 commits discards d267089fad 100: onsuccess: #2077: 1: Success after binutils/gcc/linux/g [...] discards 74e114f701 99: onsuccess: #2074: 1: Success after baseline build: no ne [...] discards d6de3649e9 98: onsuccess: #2073: 1: Success after gcc/linux: 11 commits discards 398e47cde0 97: onsuccess: #2072: 1: Success after binutils/gcc/gdb: 3 commits discards 93c6d976e2 96: onsuccess: #2071: 1: Success after gcc/linux: 56 commits discards af3f0b2d96 95: onsuccess: #2070: 1: Success after basepoints/gcc-13-238 [...] discards 328dba1666 94: onsuccess: 1: Success after gcc: openmp: Partial OpenMP [...] discards f725cbec53 93: onsuccess: 1: Success after binutils/gcc/linux/gdb: 88 commits discards 7255253583 92: onsuccess: 1: Success after binutils/gcc/linux/gdb/qemu: [...] discards 2680beba8f 91: onsuccess: 1: Success after binutils/gcc/gdb: 8 commits discards 2e4862b20f 90: onsuccess: 1: Success after binutils/gcc/gdb: 19 commits discards 070f78d0b4 89: onsuccess: 1: Success after binutils/gcc/gdb: 5 commits discards 5e527ba421 88: onsuccess: 1: Success after gcc/linux/qemu: 149 commits discards df0fc6e910 87: onsuccess: 1: Success after binutils/gcc/gdb: 14 commits discards ec7c073945 86: onsuccess: 1: Success after binutils/gcc/gdb: 7 commits discards caa700def0 85: onsuccess: 1: Success after binutils/gcc/glibc/gdb/qemu: [...] discards dc1b50e498 84: onsuccess: 1: Success after binutils/gcc/linux/gdb: 68 commits new a90f965286 84: onsuccess: 1: Success after binutils/gcc/linux/gdb: 68 commits new 622281ae0d 85: onsuccess: 1: Success after binutils/gcc/glibc/gdb/qemu: [...] new 0d6dd897c2 86: onsuccess: 1: Success after binutils/gcc/gdb: 7 commits new de8122ed78 87: onsuccess: 1: Success after binutils/gcc/gdb: 14 commits new faf110862e 88: onsuccess: 1: Success after gcc/linux/qemu: 149 commits new f530bc1b27 89: onsuccess: 1: Success after binutils/gcc/gdb: 5 commits new 396a549163 90: onsuccess: 1: Success after binutils/gcc/gdb: 19 commits new 6c64fdf441 91: onsuccess: 1: Success after binutils/gcc/gdb: 8 commits new a008552b98 92: onsuccess: 1: Success after binutils/gcc/linux/gdb/qemu: [...] new 645610f784 93: onsuccess: 1: Success after binutils/gcc/linux/gdb: 88 commits new 9666822c05 94: onsuccess: 1: Success after gcc: openmp: Partial OpenMP [...] new fe1f413555 95: onsuccess: #2070: 1: Success after basepoints/gcc-13-238 [...] new ebea578df9 96: onsuccess: #2071: 1: Success after gcc/linux: 56 commits new d9d0bc449d 97: onsuccess: #2072: 1: Success after binutils/gcc/gdb: 3 commits new 5f8941e1a4 98: onsuccess: #2073: 1: Success after gcc/linux: 11 commits new d97a00965a 99: onsuccess: #2074: 1: Success after baseline build: no ne [...] new aecf401a8b 100: onsuccess: #2077: 1: Success after binutils/gcc/linux/g [...] new 67f6b52666 101: onsuccess: #2130: 1: Success after binutils: 81 commits new ddc99a5cc1 102: onsuccess: #2133: 1: Success after gdb-12-branchpoint-1 [...] new acacb42c1d 103: onsuccess: #2135: 1: Success after gcc/linux/glibc/gdb/ [...] new 7decdf432a 104: onsuccess: #2136: 1: Success after binutils/gcc/gdb: 3 commits new 583849fc46 105: onsuccess: #2137: 1: Success after basepoints/gcc-13-27 [...] new d8cd2b3794 106: onsuccess: #2138: 1: Success after binutils/gcc/glibc/g [...] new fe36add65e 107: onsuccess: #2139: 1: Success after binutils/gcc/gdb: 3 commits new c22b7c891e 108: onsuccess: #2140: 1: Success after binutils/gcc/gdb: 5 commits new b598817a14 109: onsuccess: #2141: 1: Success after gcc/glibc: 6 commits new 2cac1aee19 110: onsuccess: #2142: 1: Success after binutils/gcc/glibc/g [...] new 934d518d55 111: onsuccess: #2143: 1: Success after binutils/gcc/linux/g [...] new 55c71eccf5 112: onsuccess: #2144: 1: Success after binutils/gcc/glibc/g [...] new 9060659fb5 113: onsuccess: #2145: 1: Success after binutils/gcc/glibc/g [...] new 46cd96ed63 114: onsuccess: #2146: 1: Success after binutils/gcc/glibc/g [...] new 74adc05d7d 115: onsuccess: #2147: 1: Success after binutils/linux/glibc [...] new 0059bc65e1 116: onsuccess: #2148: 1: Success after binutils/gcc/gdb: 7 commits new 564f0b32ad 117: onsuccess: #2150: 1: Success after binutils/gcc/glibc/g [...] new 242f3704a0 118: onsuccess: #2151: 1: Success after binutils/gcc/linux/g [...] new b1d2246d78 119: onsuccess: #2154: 1: Success after binutils/gcc/linux/g [...] new f33c16fef9 120: onsuccess: #2155: 1: Success after binutils/gcc/linux/g [...] new 0d97d58a7c 121: onsuccess: #2156: 1: Success after binutils/gcc/linux/g [...] new 6758d2afa9 122: onsuccess: #2157: 1: Success after binutils/gcc/gdb: 6 commits new 49cb69220f 123: onsuccess: #2158: 1: Success after basepoints/gcc-13-28 [...] new b3c5a3bf9d 124: onsuccess: #2159: 1: Success after linux: 23 commits new e3a6bde2cc 125: onsuccess: #2160: 1: Success after binutils/gcc/linux/g [...] new 800c21ad89 126: onsuccess: #2161: 1: Success after basepoints/gcc-13-28 [...] new 8a42ce3c83 127: onsuccess: #2162: 1: Success after gcc: 9 commits new 48c65f4bfa 128: onsuccess: #2163: 1: Success after linux: 23 commits new 88fb483d70 129: onsuccess: #2164: 1: Success after binutils/gcc/linux/g [...] new 054313bfe4 130: onsuccess: #2165: 1: Success after binutils/gcc/gdb: 32 [...] new 1ab265ea0f 131: onsuccess: #2166: 1: Success after binutils/gcc/gdb: 12 [...] new c118702180 132: onsuccess: #2167: 1: Success after binutils/gcc/glibc/g [...] new 68cd8f0ac6 133: onsuccess: #2168: 1: Success after binutils/gcc/linux/g [...] new e9074e1998 134: onsuccess: #2169: 1: Success after binutils/gcc/gdb: 13 [...] new 228037905f 135: onsuccess: #2170: 1: Success after gcc/linux/qemu: 63 commits new e9c00f5850 136: onsuccess: #2171: 1: Success after binutils/gcc/gdb/qem [...] new f836ea54d1 137: onsuccess: #2172: 1: Success after binutils/gcc/linux/g [...] new 3d38fae4d8 138: onsuccess: #2173: 1: Success after binutils/gcc/gdb: 5 commits new 750612b2c5 139: onsuccess: #2174: 1: Success after binutils/gcc/gdb: 13 [...] new 3f0be535ad 140: onsuccess: #2175: 1: Success after binutils/gcc/linux/g [...] new 091b739f94 141: onsuccess: #2176: 1: Success after binutils/gcc/gdb: 6 commits new 0a63688ffe 142: onsuccess: #2177: 1: Success after gcc/glibc: 4 commits new 928dedfa6b 143: onsuccess: #2178: 1: Success after binutils/gcc/gdb/qem [...] new 4b30e5fa51 144: onsuccess: #2179: 1: Success after binutils/gcc/linux/g [...] new 04838d9e7d 145: onsuccess: #2180: 1: Success after binutils/gcc/linux/g [...] new cbfd369cfe 146: onsuccess: #2181: 1: Success after binutils/glibc/gdb: [...] new 4ade955916 147: onsuccess: #2182: 1: Success after binutils/gcc/gdb: 18 [...] new 085e3e34f9 148: onsuccess: #2183: 1: Success after gcc/linux/glibc: 64 commits new 3c20950a80 149: onsuccess: #2184: 1: Success after binutils/gcc/linux/g [...] new 27d625f037 150: onsuccess: #2185: 1: Success after gcc: 3 commits new fc4c2b126d 151: onsuccess: #2186: 1: Success after gcc: 2 commits new 3364e353bf 152: onsuccess: #2187: 1: Success after gcc/linux/glibc: 22 commits new 9698f72926 153: onsuccess: #2188: 1: Success after binutils/gcc/gdb: 3 commits new fc32e4c69e 154: onsuccess: #2189: 1: Success after binutils/gcc/gdb: 18 [...] new 774d667166 155: onsuccess: #2190: 1: Success after binutils/gcc/linux/g [...] new 2410ba3e48 156: onsuccess: #2191: 1: Success after binutils/gcc/linux/g [...] new af0ecb06f2 157: onsuccess: #2192: 1: Success after binutils/gcc/gdb: 8 commits new fb9e1b846c 158: onsuccess: #2193: 1: Success after binutils/gcc/glibc/g [...] new 70a6d665aa 159: onsuccess: #2194: 1: Success after gcc/linux/glibc: 197 [...] new bd97bc639e 160: onsuccess: #2195: 1: Success after binutils/gcc/linux/g [...] new bfd6f35d5c 161: onsuccess: #2196: 1: Success after binutils/gcc/linux/g [...] new 219009b990 162: onsuccess: #2197: 1: Success after binutils/gcc/glibc/g [...] new 88e9c4a542 163: onsuccess: #2198: 1: Success after binutils/gcc/linux/g [...] new 7df2c82842 164: onsuccess: #2199: 1: Success after binutils/gcc/linux/g [...] new 901d9a8fb3 165: onsuccess: #2200: 1: Success after binutils/gdb: 8 commits new 5b523a5935 166: onsuccess: #2201: 1: Success after gcc/glibc/qemu: 40 commits new 50705d9bf1 167: onsuccess: #2202: 1: Success after gcc/linux/glibc/qemu [...] new bdfa895998 168: onsuccess: #2203: 1: Success after binutils/gcc/glibc/g [...] new b97e24a7e0 169: onsuccess: #2204: 1: Success after binutils/gcc/glibc/g [...] new db40b73f65 170: onsuccess: #2205: 1: Success after binutils/gcc/glibc/g [...] new 20b6496a20 171: onsuccess: #2206: 1: Success after binutils/gcc/linux/g [...] new 53e7731484 172: onsuccess: #2207: 1: Success after binutils/gcc/linux/g [...] new daa89bb38b 173: onsuccess: #2208: 1: Success after gcc: 10 commits new 17fe549eec 174: onsuccess: #2209: 1: Success after binutils/gcc/gdb: 20 [...] new 77b8330d76 175: onsuccess: #2210: 1: Success after binutils/gcc/linux/g [...] new 6a061ccf35 176: onsuccess: #2211: 1: Success after binutils/gcc/linux/g [...] new 326a82e342 177: onsuccess: #2212: 1: Success after binutils/gdb: 2 commits new 52dbc42669 178: onsuccess: #2217: 1: Success after binutils/gcc/linux/g [...] new c642e04dc5 179: onsuccess: #2230: 1: Success after binutils/gcc/linux/g [...] new 882750ee62 180: onsuccess: #2232: 1: Success after binutils/gcc/glibc/g [...] new ab6b668c3e 181: onsuccess: #2239: 1: Success after binutils/gcc/linux/g [...] new f51ff1431f 182: onsuccess: #2247: 1: Success after binutils/gcc/linux/g [...] new 0856aad4ff 183: onsuccess: #2270: 1: Success after binutils/gcc/linux/g [...] new 753aa65469 184: onsuccess: #2288: 1: Success after binutils/gcc/linux/g [...] new 41ad731891 185: onsuccess: #2290: 1: Success after binutils/gcc/linux/g [...]
This update added new revisions after undoing existing revisions. That is to say, some revisions that were in the old version of the branch are not in the new version. This situation occurs when a user --force pushes a change and generates a repository containing something like this:
* -- * -- B -- O -- O -- O (383699d8f7) \ 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 1828 -> 1724 bytes 02-prepare_abe/console.log.xz | Bin 2756 -> 2752 bytes 03-build_abe-binutils/console.log.xz | Bin 31132 -> 30972 bytes 04-build_abe-stage1/console.log.xz | Bin 72860 -> 73320 bytes 05-clean_sysroot/console.log.xz | Bin 328 -> 328 bytes 06-build_abe-linux/console.log.xz | Bin 9540 -> 8512 bytes 07-build_abe-glibc/console.log.xz | Bin 240364 -> 241464 bytes 08-build_abe-stage2/console.log.xz | Bin 206612 -> 207012 bytes 09-build_abe-gdb/console.log.xz | Bin 38184 -> 38188 bytes 10-build_abe-qemu/console.log.xz | Bin 32160 -> 32472 bytes 11-build_abe-dejagnu/console.log.xz | Bin 3892 -> 3956 bytes 12-build_abe-check_gcc/console.log.xz | Bin 2708 -> 3252 bytes 13-check_regression/console.log.xz | Bin 19788 -> 8564 bytes 13-check_regression/extra-bisect-params | 2 +- 13-check_regression/fails.sum | 33 +- 13-check_regression/mail-body.txt | 198 +- 13-check_regression/results.compare | 517 +-- 13-check_regression/results.compare2 | 2828 ++--------------- 13-check_regression/results.regressions | 132 +- 14-update_baseline/console.log | 64 +- dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- git/gdb_rev | 2 +- git/glibc_rev | 2 +- git/linux_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 200 +- mail/mail-subject.txt | 2 +- manifest.sh | 40 +- results | 130 +- sumfiles/g++.log.xz | Bin 3451364 -> 3431572 bytes sumfiles/g++.sum | 315 +- sumfiles/gcc.log.xz | Bin 3027976 -> 3042760 bytes sumfiles/gcc.sum | 5184 ++++++++++++++++--------------- sumfiles/gfortran.log.xz | Bin 1037932 -> 1030816 bytes sumfiles/gfortran.sum | 42 +- sumfiles/libatomic.log.xz | Bin 2288 -> 2288 bytes sumfiles/libatomic.sum | 4 +- sumfiles/libgomp.log.xz | Bin 203944 -> 204136 bytes sumfiles/libgomp.sum | 16 +- sumfiles/libitm.log.xz | Bin 2696 -> 2700 bytes sumfiles/libitm.sum | 6 +- sumfiles/libstdc++.log.xz | Bin 430644 -> 423764 bytes sumfiles/libstdc++.sum | 37 +- 45 files changed, 3484 insertions(+), 6280 deletions(-)