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 41ad731891 185: onsuccess: #2290: 1: Success after binutils/gcc/linux/g [...] discards 753aa65469 184: onsuccess: #2288: 1: Success after binutils/gcc/linux/g [...] discards 0856aad4ff 183: onsuccess: #2270: 1: Success after binutils/gcc/linux/g [...] discards f51ff1431f 182: onsuccess: #2247: 1: Success after binutils/gcc/linux/g [...] discards ab6b668c3e 181: onsuccess: #2239: 1: Success after binutils/gcc/linux/g [...] discards 882750ee62 180: onsuccess: #2232: 1: Success after binutils/gcc/glibc/g [...] discards c642e04dc5 179: onsuccess: #2230: 1: Success after binutils/gcc/linux/g [...] discards 52dbc42669 178: onsuccess: #2217: 1: Success after binutils/gcc/linux/g [...] discards 326a82e342 177: onsuccess: #2212: 1: Success after binutils/gdb: 2 commits discards 6a061ccf35 176: onsuccess: #2211: 1: Success after binutils/gcc/linux/g [...] discards 77b8330d76 175: onsuccess: #2210: 1: Success after binutils/gcc/linux/g [...] discards 17fe549eec 174: onsuccess: #2209: 1: Success after binutils/gcc/gdb: 20 [...] discards daa89bb38b 173: onsuccess: #2208: 1: Success after gcc: 10 commits discards 53e7731484 172: onsuccess: #2207: 1: Success after binutils/gcc/linux/g [...] discards 20b6496a20 171: onsuccess: #2206: 1: Success after binutils/gcc/linux/g [...] discards db40b73f65 170: onsuccess: #2205: 1: Success after binutils/gcc/glibc/g [...] discards b97e24a7e0 169: onsuccess: #2204: 1: Success after binutils/gcc/glibc/g [...] discards bdfa895998 168: onsuccess: #2203: 1: Success after binutils/gcc/glibc/g [...] discards 50705d9bf1 167: onsuccess: #2202: 1: Success after gcc/linux/glibc/qemu [...] discards 5b523a5935 166: onsuccess: #2201: 1: Success after gcc/glibc/qemu: 40 commits discards 901d9a8fb3 165: onsuccess: #2200: 1: Success after binutils/gdb: 8 commits discards 7df2c82842 164: onsuccess: #2199: 1: Success after binutils/gcc/linux/g [...] discards 88e9c4a542 163: onsuccess: #2198: 1: Success after binutils/gcc/linux/g [...] discards 219009b990 162: onsuccess: #2197: 1: Success after binutils/gcc/glibc/g [...] discards bfd6f35d5c 161: onsuccess: #2196: 1: Success after binutils/gcc/linux/g [...] discards bd97bc639e 160: onsuccess: #2195: 1: Success after binutils/gcc/linux/g [...] discards 70a6d665aa 159: onsuccess: #2194: 1: Success after gcc/linux/glibc: 197 [...] discards fb9e1b846c 158: onsuccess: #2193: 1: Success after binutils/gcc/glibc/g [...] discards af0ecb06f2 157: onsuccess: #2192: 1: Success after binutils/gcc/gdb: 8 commits discards 2410ba3e48 156: onsuccess: #2191: 1: Success after binutils/gcc/linux/g [...] discards 774d667166 155: onsuccess: #2190: 1: Success after binutils/gcc/linux/g [...] discards fc32e4c69e 154: onsuccess: #2189: 1: Success after binutils/gcc/gdb: 18 [...] discards 9698f72926 153: onsuccess: #2188: 1: Success after binutils/gcc/gdb: 3 commits discards 3364e353bf 152: onsuccess: #2187: 1: Success after gcc/linux/glibc: 22 commits discards fc4c2b126d 151: onsuccess: #2186: 1: Success after gcc: 2 commits discards 27d625f037 150: onsuccess: #2185: 1: Success after gcc: 3 commits discards 3c20950a80 149: onsuccess: #2184: 1: Success after binutils/gcc/linux/g [...] discards 085e3e34f9 148: onsuccess: #2183: 1: Success after gcc/linux/glibc: 64 commits discards 4ade955916 147: onsuccess: #2182: 1: Success after binutils/gcc/gdb: 18 [...] discards cbfd369cfe 146: onsuccess: #2181: 1: Success after binutils/glibc/gdb: [...] discards 04838d9e7d 145: onsuccess: #2180: 1: Success after binutils/gcc/linux/g [...] discards 4b30e5fa51 144: onsuccess: #2179: 1: Success after binutils/gcc/linux/g [...] discards 928dedfa6b 143: onsuccess: #2178: 1: Success after binutils/gcc/gdb/qem [...] discards 0a63688ffe 142: onsuccess: #2177: 1: Success after gcc/glibc: 4 commits discards 091b739f94 141: onsuccess: #2176: 1: Success after binutils/gcc/gdb: 6 commits discards 3f0be535ad 140: onsuccess: #2175: 1: Success after binutils/gcc/linux/g [...] discards 750612b2c5 139: onsuccess: #2174: 1: Success after binutils/gcc/gdb: 13 [...] discards 3d38fae4d8 138: onsuccess: #2173: 1: Success after binutils/gcc/gdb: 5 commits discards f836ea54d1 137: onsuccess: #2172: 1: Success after binutils/gcc/linux/g [...] discards e9c00f5850 136: onsuccess: #2171: 1: Success after binutils/gcc/gdb/qem [...] discards 228037905f 135: onsuccess: #2170: 1: Success after gcc/linux/qemu: 63 commits discards e9074e1998 134: onsuccess: #2169: 1: Success after binutils/gcc/gdb: 13 [...] discards 68cd8f0ac6 133: onsuccess: #2168: 1: Success after binutils/gcc/linux/g [...] discards c118702180 132: onsuccess: #2167: 1: Success after binutils/gcc/glibc/g [...] discards 1ab265ea0f 131: onsuccess: #2166: 1: Success after binutils/gcc/gdb: 12 [...] discards 054313bfe4 130: onsuccess: #2165: 1: Success after binutils/gcc/gdb: 32 [...] discards 88fb483d70 129: onsuccess: #2164: 1: Success after binutils/gcc/linux/g [...] discards 48c65f4bfa 128: onsuccess: #2163: 1: Success after linux: 23 commits discards 8a42ce3c83 127: onsuccess: #2162: 1: Success after gcc: 9 commits discards 800c21ad89 126: onsuccess: #2161: 1: Success after basepoints/gcc-13-28 [...] discards e3a6bde2cc 125: onsuccess: #2160: 1: Success after binutils/gcc/linux/g [...] discards b3c5a3bf9d 124: onsuccess: #2159: 1: Success after linux: 23 commits discards 49cb69220f 123: onsuccess: #2158: 1: Success after basepoints/gcc-13-28 [...] discards 6758d2afa9 122: onsuccess: #2157: 1: Success after binutils/gcc/gdb: 6 commits discards 0d97d58a7c 121: onsuccess: #2156: 1: Success after binutils/gcc/linux/g [...] discards f33c16fef9 120: onsuccess: #2155: 1: Success after binutils/gcc/linux/g [...] discards b1d2246d78 119: onsuccess: #2154: 1: Success after binutils/gcc/linux/g [...] discards 242f3704a0 118: onsuccess: #2151: 1: Success after binutils/gcc/linux/g [...] discards 564f0b32ad 117: onsuccess: #2150: 1: Success after binutils/gcc/glibc/g [...] discards 0059bc65e1 116: onsuccess: #2148: 1: Success after binutils/gcc/gdb: 7 commits discards 74adc05d7d 115: onsuccess: #2147: 1: Success after binutils/linux/glibc [...] discards 46cd96ed63 114: onsuccess: #2146: 1: Success after binutils/gcc/glibc/g [...] discards 9060659fb5 113: onsuccess: #2145: 1: Success after binutils/gcc/glibc/g [...] discards 55c71eccf5 112: onsuccess: #2144: 1: Success after binutils/gcc/glibc/g [...] discards 934d518d55 111: onsuccess: #2143: 1: Success after binutils/gcc/linux/g [...] discards 2cac1aee19 110: onsuccess: #2142: 1: Success after binutils/gcc/glibc/g [...] discards b598817a14 109: onsuccess: #2141: 1: Success after gcc/glibc: 6 commits discards c22b7c891e 108: onsuccess: #2140: 1: Success after binutils/gcc/gdb: 5 commits discards fe36add65e 107: onsuccess: #2139: 1: Success after binutils/gcc/gdb: 3 commits discards d8cd2b3794 106: onsuccess: #2138: 1: Success after binutils/gcc/glibc/g [...] discards 583849fc46 105: onsuccess: #2137: 1: Success after basepoints/gcc-13-27 [...] discards 7decdf432a 104: onsuccess: #2136: 1: Success after binutils/gcc/gdb: 3 commits discards acacb42c1d 103: onsuccess: #2135: 1: Success after gcc/linux/glibc/gdb/ [...] discards ddc99a5cc1 102: onsuccess: #2133: 1: Success after gdb-12-branchpoint-1 [...] discards 67f6b52666 101: onsuccess: #2130: 1: Success after binutils: 81 commits discards aecf401a8b 100: onsuccess: #2077: 1: Success after binutils/gcc/linux/g [...] discards d97a00965a 99: onsuccess: #2074: 1: Success after baseline build: no ne [...] discards 5f8941e1a4 98: onsuccess: #2073: 1: Success after gcc/linux: 11 commits discards d9d0bc449d 97: onsuccess: #2072: 1: Success after binutils/gcc/gdb: 3 commits discards ebea578df9 96: onsuccess: #2071: 1: Success after gcc/linux: 56 commits discards fe1f413555 95: onsuccess: #2070: 1: Success after basepoints/gcc-13-238 [...] discards 9666822c05 94: onsuccess: 1: Success after gcc: openmp: Partial OpenMP [...] discards 645610f784 93: onsuccess: 1: Success after binutils/gcc/linux/gdb: 88 commits discards a008552b98 92: onsuccess: 1: Success after binutils/gcc/linux/gdb/qemu: [...] discards 6c64fdf441 91: onsuccess: 1: Success after binutils/gcc/gdb: 8 commits discards 396a549163 90: onsuccess: 1: Success after binutils/gcc/gdb: 19 commits discards f530bc1b27 89: onsuccess: 1: Success after binutils/gcc/gdb: 5 commits discards faf110862e 88: onsuccess: 1: Success after gcc/linux/qemu: 149 commits discards de8122ed78 87: onsuccess: 1: Success after binutils/gcc/gdb: 14 commits discards 0d6dd897c2 86: onsuccess: 1: Success after binutils/gcc/gdb: 7 commits discards 622281ae0d 85: onsuccess: 1: Success after binutils/gcc/glibc/gdb/qemu: [...] new 40d52982ff 85: onsuccess: 1: Success after binutils/gcc/glibc/gdb/qemu: [...] new d82eee8311 86: onsuccess: 1: Success after binutils/gcc/gdb: 7 commits new 31bf5abe97 87: onsuccess: 1: Success after binutils/gcc/gdb: 14 commits new f6f3a4eac1 88: onsuccess: 1: Success after gcc/linux/qemu: 149 commits new 6bd3ba0d01 89: onsuccess: 1: Success after binutils/gcc/gdb: 5 commits new 16d7d0b746 90: onsuccess: 1: Success after binutils/gcc/gdb: 19 commits new 837389dd17 91: onsuccess: 1: Success after binutils/gcc/gdb: 8 commits new 2bf23f2bd0 92: onsuccess: 1: Success after binutils/gcc/linux/gdb/qemu: [...] new c0bb46fb0e 93: onsuccess: 1: Success after binutils/gcc/linux/gdb: 88 commits new f373bbe963 94: onsuccess: 1: Success after gcc: openmp: Partial OpenMP [...] new 45f8d80da1 95: onsuccess: #2070: 1: Success after basepoints/gcc-13-238 [...] new bce0613ee9 96: onsuccess: #2071: 1: Success after gcc/linux: 56 commits new d200d32120 97: onsuccess: #2072: 1: Success after binutils/gcc/gdb: 3 commits new 5b5c3154c8 98: onsuccess: #2073: 1: Success after gcc/linux: 11 commits new 43b15ab548 99: onsuccess: #2074: 1: Success after baseline build: no ne [...] new f21a82d2ef 100: onsuccess: #2077: 1: Success after binutils/gcc/linux/g [...] new b4e175811f 101: onsuccess: #2130: 1: Success after binutils: 81 commits new e72f80b24b 102: onsuccess: #2133: 1: Success after gdb-12-branchpoint-1 [...] new 5f0b9d1568 103: onsuccess: #2135: 1: Success after gcc/linux/glibc/gdb/ [...] new f9a5c69406 104: onsuccess: #2136: 1: Success after binutils/gcc/gdb: 3 commits new 11ab54e4bb 105: onsuccess: #2137: 1: Success after basepoints/gcc-13-27 [...] new b90f121b98 106: onsuccess: #2138: 1: Success after binutils/gcc/glibc/g [...] new ec9be47718 107: onsuccess: #2139: 1: Success after binutils/gcc/gdb: 3 commits new b638a369da 108: onsuccess: #2140: 1: Success after binutils/gcc/gdb: 5 commits new b9ed71420c 109: onsuccess: #2141: 1: Success after gcc/glibc: 6 commits new 3669588843 110: onsuccess: #2142: 1: Success after binutils/gcc/glibc/g [...] new 329f3cd17c 111: onsuccess: #2143: 1: Success after binutils/gcc/linux/g [...] new 17020e22ff 112: onsuccess: #2144: 1: Success after binutils/gcc/glibc/g [...] new f3ab1d1f31 113: onsuccess: #2145: 1: Success after binutils/gcc/glibc/g [...] new 07990ab4e9 114: onsuccess: #2146: 1: Success after binutils/gcc/glibc/g [...] new bc1316964f 115: onsuccess: #2147: 1: Success after binutils/linux/glibc [...] new c27f380623 116: onsuccess: #2148: 1: Success after binutils/gcc/gdb: 7 commits new 35d66e2357 117: onsuccess: #2150: 1: Success after binutils/gcc/glibc/g [...] new 97a9b10f69 118: onsuccess: #2151: 1: Success after binutils/gcc/linux/g [...] new 72ff8df929 119: onsuccess: #2154: 1: Success after binutils/gcc/linux/g [...] new de3e7e3446 120: onsuccess: #2155: 1: Success after binutils/gcc/linux/g [...] new 3b30063588 121: onsuccess: #2156: 1: Success after binutils/gcc/linux/g [...] new 2d5d10ebda 122: onsuccess: #2157: 1: Success after binutils/gcc/gdb: 6 commits new f5d8517376 123: onsuccess: #2158: 1: Success after basepoints/gcc-13-28 [...] new a8933ca906 124: onsuccess: #2159: 1: Success after linux: 23 commits new a031725507 125: onsuccess: #2160: 1: Success after binutils/gcc/linux/g [...] new 3e32781ec0 126: onsuccess: #2161: 1: Success after basepoints/gcc-13-28 [...] new 17d3fc17b5 127: onsuccess: #2162: 1: Success after gcc: 9 commits new 2e3aa2aadc 128: onsuccess: #2163: 1: Success after linux: 23 commits new 5e5e45d764 129: onsuccess: #2164: 1: Success after binutils/gcc/linux/g [...] new 1885d4a52d 130: onsuccess: #2165: 1: Success after binutils/gcc/gdb: 32 [...] new 540f965339 131: onsuccess: #2166: 1: Success after binutils/gcc/gdb: 12 [...] new ee15e4fd64 132: onsuccess: #2167: 1: Success after binutils/gcc/glibc/g [...] new 983fac4ad8 133: onsuccess: #2168: 1: Success after binutils/gcc/linux/g [...] new 12ac6ee2a7 134: onsuccess: #2169: 1: Success after binutils/gcc/gdb: 13 [...] new a5cb041c8d 135: onsuccess: #2170: 1: Success after gcc/linux/qemu: 63 commits new 0f136db770 136: onsuccess: #2171: 1: Success after binutils/gcc/gdb/qem [...] new b194dfcd1b 137: onsuccess: #2172: 1: Success after binutils/gcc/linux/g [...] new d20f641880 138: onsuccess: #2173: 1: Success after binutils/gcc/gdb: 5 commits new e6a3922e08 139: onsuccess: #2174: 1: Success after binutils/gcc/gdb: 13 [...] new 332d582e06 140: onsuccess: #2175: 1: Success after binutils/gcc/linux/g [...] new 933769ad60 141: onsuccess: #2176: 1: Success after binutils/gcc/gdb: 6 commits new d9bd9c3515 142: onsuccess: #2177: 1: Success after gcc/glibc: 4 commits new 2b0b40b8a1 143: onsuccess: #2178: 1: Success after binutils/gcc/gdb/qem [...] new e29ad8c667 144: onsuccess: #2179: 1: Success after binutils/gcc/linux/g [...] new 3c35c2985b 145: onsuccess: #2180: 1: Success after binutils/gcc/linux/g [...] new 7cd55020b5 146: onsuccess: #2181: 1: Success after binutils/glibc/gdb: [...] new 92f5fbe0dc 147: onsuccess: #2182: 1: Success after binutils/gcc/gdb: 18 [...] new c75c1ce155 148: onsuccess: #2183: 1: Success after gcc/linux/glibc: 64 commits new e82a74bf25 149: onsuccess: #2184: 1: Success after binutils/gcc/linux/g [...] new 961edbd3a4 150: onsuccess: #2185: 1: Success after gcc: 3 commits new 6b8b0a4044 151: onsuccess: #2186: 1: Success after gcc: 2 commits new 8729fc4965 152: onsuccess: #2187: 1: Success after gcc/linux/glibc: 22 commits new 74bba532b3 153: onsuccess: #2188: 1: Success after binutils/gcc/gdb: 3 commits new afbf4e62c8 154: onsuccess: #2189: 1: Success after binutils/gcc/gdb: 18 [...] new f76fc06258 155: onsuccess: #2190: 1: Success after binutils/gcc/linux/g [...] new 651791535e 156: onsuccess: #2191: 1: Success after binutils/gcc/linux/g [...] new 857e7a13ca 157: onsuccess: #2192: 1: Success after binutils/gcc/gdb: 8 commits new 6061d11d99 158: onsuccess: #2193: 1: Success after binutils/gcc/glibc/g [...] new db561daf2a 159: onsuccess: #2194: 1: Success after gcc/linux/glibc: 197 [...] new c02a85c816 160: onsuccess: #2195: 1: Success after binutils/gcc/linux/g [...] new 2b70740254 161: onsuccess: #2196: 1: Success after binutils/gcc/linux/g [...] new fb9a1bf81c 162: onsuccess: #2197: 1: Success after binutils/gcc/glibc/g [...] new 103a95ab94 163: onsuccess: #2198: 1: Success after binutils/gcc/linux/g [...] new 61a3b3c8cb 164: onsuccess: #2199: 1: Success after binutils/gcc/linux/g [...] new 3fe7b7b1ca 165: onsuccess: #2200: 1: Success after binutils/gdb: 8 commits new e252c7cbfd 166: onsuccess: #2201: 1: Success after gcc/glibc/qemu: 40 commits new f75064a27b 167: onsuccess: #2202: 1: Success after gcc/linux/glibc/qemu [...] new 890233a870 168: onsuccess: #2203: 1: Success after binutils/gcc/glibc/g [...] new ce5f078594 169: onsuccess: #2204: 1: Success after binutils/gcc/glibc/g [...] new 06848091f9 170: onsuccess: #2205: 1: Success after binutils/gcc/glibc/g [...] new 5e793e914a 171: onsuccess: #2206: 1: Success after binutils/gcc/linux/g [...] new 713c9401ea 172: onsuccess: #2207: 1: Success after binutils/gcc/linux/g [...] new 2f0432970d 173: onsuccess: #2208: 1: Success after gcc: 10 commits new cdd91a26c6 174: onsuccess: #2209: 1: Success after binutils/gcc/gdb: 20 [...] new ca543cf7f4 175: onsuccess: #2210: 1: Success after binutils/gcc/linux/g [...] new 7262e9a152 176: onsuccess: #2211: 1: Success after binutils/gcc/linux/g [...] new 0cb3c872df 177: onsuccess: #2212: 1: Success after binutils/gdb: 2 commits new d4150e471b 178: onsuccess: #2217: 1: Success after binutils/gcc/linux/g [...] new 2d8745a556 179: onsuccess: #2230: 1: Success after binutils/gcc/linux/g [...] new d9afbbdb32 180: onsuccess: #2232: 1: Success after binutils/gcc/glibc/g [...] new 631b754a51 181: onsuccess: #2239: 1: Success after binutils/gcc/linux/g [...] new d2dd5094ba 182: onsuccess: #2247: 1: Success after binutils/gcc/linux/g [...] new 2aa1b4f0a6 183: onsuccess: #2270: 1: Success after binutils/gcc/linux/g [...] new af8e7dc7f2 184: onsuccess: #2288: 1: Success after binutils/gcc/linux/g [...] new 17eaf0c340 185: onsuccess: #2290: 1: Success after binutils/gcc/linux/g [...] new c3a83d104f 186: onsuccess: #2291: 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 (41ad731891) \ 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 1724 -> 1720 bytes 02-prepare_abe/console.log.xz | Bin 2752 -> 2744 bytes 03-build_abe-binutils/console.log.xz | Bin 30972 -> 30188 bytes 04-build_abe-stage1/console.log.xz | Bin 73320 -> 72632 bytes 05-clean_sysroot/console.log.xz | Bin 328 -> 328 bytes 06-build_abe-linux/console.log.xz | Bin 8512 -> 8696 bytes 07-build_abe-glibc/console.log.xz | Bin 241464 -> 239700 bytes 08-build_abe-stage2/console.log.xz | Bin 207012 -> 202784 bytes 09-build_abe-gdb/console.log.xz | Bin 38188 -> 37528 bytes 10-build_abe-qemu/console.log.xz | Bin 32472 -> 31728 bytes 11-build_abe-dejagnu/console.log.xz | Bin 3956 -> 3888 bytes 12-build_abe-check_gcc/console.log.xz | Bin 3252 -> 2600 bytes 13-check_regression/console.log.xz | Bin 8564 -> 11736 bytes 13-check_regression/extra-bisect-params | 2 +- 13-check_regression/fails.sum | 125 +- 13-check_regression/mail-body.txt | 244 +- 13-check_regression/results.compare | 127 +- 13-check_regression/results.compare2 | 1065 ++++-- 13-check_regression/results.regressions | 124 +- 14-update_baseline/console.log | 60 +- 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 | 246 +- mail/mail-subject.txt | 2 +- manifest.sh | 42 +- results | 120 +- sumfiles/g++.log.xz | Bin 3431572 -> 3449744 bytes sumfiles/g++.sum | 213 +- sumfiles/gcc.log.xz | Bin 3042760 -> 3024396 bytes sumfiles/gcc.sum | 5438 +++++++++++++++---------------- sumfiles/gfortran.log.xz | Bin 1030816 -> 1033272 bytes sumfiles/gfortran.sum | 40 +- sumfiles/libatomic.log.xz | Bin 2288 -> 2292 bytes sumfiles/libatomic.sum | 4 +- sumfiles/libgomp.log.xz | Bin 204136 -> 204188 bytes sumfiles/libgomp.sum | 16 +- sumfiles/libitm.log.xz | Bin 2700 -> 2696 bytes sumfiles/libitm.sum | 6 +- sumfiles/libstdc++.log.xz | Bin 423764 -> 427452 bytes sumfiles/libstdc++.sum | 33 +- 45 files changed, 4289 insertions(+), 3632 deletions(-)