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 cdd8ee3bd2 197: onsuccess: #2348: 1: Success after linux: 190 commits discards 148cdeda71 196: onsuccess: #2342: 1: Success after binutils/gcc/gdb: 41 [...] discards c29dee51a2 195: onsuccess: #2341: 1: Success after binutils/gcc/linux/g [...] discards fa12f1f19a 194: onsuccess: #2340: 1: Success after binutils/gcc/linux/g [...] discards 3496f8c28c 193: onsuccess: #2339: 1: Success after binutils/gcc/glibc/g [...] discards 8a4304ed17 192: onsuccess: #2338: 1: Success after binutils/gcc/linux/g [...] discards 14101faf42 191: onsuccess: #2331: 1: Success after gcc/qemu: 90 commits discards e8fe2ee4d9 190: onsuccess: #2330: 1: Success after binutils/gcc/linux/g [...] discards 21967e4d31 189: onsuccess: #2299: 1: Success after binutils/gcc/linux/g [...] discards c1a30f311f 188: onsuccess: #2295: 1: Success after binutils/gcc/linux/g [...] discards aedb4d1693 187: onsuccess: #2294: 1: Success after binutils/gcc/linux/g [...] discards a1a1d5a980 186: onsuccess: #2291: 1: Success after binutils/gcc/linux/g [...] discards 47ac42b221 185: onsuccess: #2290: 1: Success after binutils/gcc/linux/g [...] discards bef55fed9b 184: onsuccess: #2288: 1: Success after binutils/gcc/linux/g [...] discards 9ce93ba86b 183: onsuccess: #2270: 1: Success after binutils/gcc/linux/g [...] discards e63d19d0d2 182: onsuccess: #2247: 1: Success after binutils/gcc/linux/g [...] discards f6ff92ae54 181: onsuccess: #2239: 1: Success after binutils/gcc/linux/g [...] discards 6cffa88e5b 180: onsuccess: #2232: 1: Success after binutils/gcc/glibc/g [...] discards 3609de9006 179: onsuccess: #2230: 1: Success after binutils/gcc/linux/g [...] discards b2699d7493 178: onsuccess: #2217: 1: Success after binutils/gcc/linux/g [...] discards bde4a1aa6f 177: onsuccess: #2212: 1: Success after binutils/gdb: 2 commits discards cde64cbf36 176: onsuccess: #2211: 1: Success after binutils/gcc/linux/g [...] discards f65d18c4c9 175: onsuccess: #2210: 1: Success after binutils/gcc/linux/g [...] discards 1af0bed481 174: onsuccess: #2209: 1: Success after binutils/gcc/gdb: 20 [...] discards 92b9fdc31a 173: onsuccess: #2208: 1: Success after gcc: 10 commits discards 322b4bb7c3 172: onsuccess: #2207: 1: Success after binutils/gcc/linux/g [...] discards 594eb0d031 171: onsuccess: #2206: 1: Success after binutils/gcc/linux/g [...] discards 37b9b7e759 170: onsuccess: #2205: 1: Success after binutils/gcc/glibc/g [...] discards 4291e475d6 169: onsuccess: #2204: 1: Success after binutils/gcc/glibc/g [...] discards 4a78ad11e4 168: onsuccess: #2203: 1: Success after binutils/gcc/glibc/g [...] discards ab7500e46e 167: onsuccess: #2202: 1: Success after gcc/linux/glibc/qemu [...] discards 470776c176 166: onsuccess: #2201: 1: Success after gcc/glibc/qemu: 40 commits discards 5e9236beea 165: onsuccess: #2200: 1: Success after binutils/gdb: 8 commits discards 211b1f405f 164: onsuccess: #2199: 1: Success after binutils/gcc/linux/g [...] discards b73855af08 163: onsuccess: #2198: 1: Success after binutils/gcc/linux/g [...] discards fdac6447f0 162: onsuccess: #2197: 1: Success after binutils/gcc/glibc/g [...] discards 875bd0bca9 161: onsuccess: #2196: 1: Success after binutils/gcc/linux/g [...] discards e7d3242d4c 160: onsuccess: #2195: 1: Success after binutils/gcc/linux/g [...] discards 4340257808 159: onsuccess: #2194: 1: Success after gcc/linux/glibc: 197 [...] discards 2e1ed56918 158: onsuccess: #2193: 1: Success after binutils/gcc/glibc/g [...] discards 17c579c46c 157: onsuccess: #2192: 1: Success after binutils/gcc/gdb: 8 commits discards 224bb47e60 156: onsuccess: #2191: 1: Success after binutils/gcc/linux/g [...] discards c1f96cd0f3 155: onsuccess: #2190: 1: Success after binutils/gcc/linux/g [...] discards ed062a0663 154: onsuccess: #2189: 1: Success after binutils/gcc/gdb: 18 [...] discards bd93c80d93 153: onsuccess: #2188: 1: Success after binutils/gcc/gdb: 3 commits discards 8391d2358b 152: onsuccess: #2187: 1: Success after gcc/linux/glibc: 22 commits discards 43bc857bbc 151: onsuccess: #2186: 1: Success after gcc: 2 commits discards e5a3609b9b 150: onsuccess: #2185: 1: Success after gcc: 3 commits discards 99991c2b08 149: onsuccess: #2184: 1: Success after binutils/gcc/linux/g [...] discards 2be5437052 148: onsuccess: #2183: 1: Success after gcc/linux/glibc: 64 commits discards 3740c27d80 147: onsuccess: #2182: 1: Success after binutils/gcc/gdb: 18 [...] discards 857531f131 146: onsuccess: #2181: 1: Success after binutils/glibc/gdb: [...] discards 9c077cd85d 145: onsuccess: #2180: 1: Success after binutils/gcc/linux/g [...] discards 9121f4b673 144: onsuccess: #2179: 1: Success after binutils/gcc/linux/g [...] discards 6f29809566 143: onsuccess: #2178: 1: Success after binutils/gcc/gdb/qem [...] discards 43d88e736a 142: onsuccess: #2177: 1: Success after gcc/glibc: 4 commits discards 4079a7a069 141: onsuccess: #2176: 1: Success after binutils/gcc/gdb: 6 commits discards a9927c1cc2 140: onsuccess: #2175: 1: Success after binutils/gcc/linux/g [...] discards 5a1b1f78d5 139: onsuccess: #2174: 1: Success after binutils/gcc/gdb: 13 [...] discards ee1cf5d71d 138: onsuccess: #2173: 1: Success after binutils/gcc/gdb: 5 commits discards 6b24760b84 137: onsuccess: #2172: 1: Success after binutils/gcc/linux/g [...] discards 862262d2fc 136: onsuccess: #2171: 1: Success after binutils/gcc/gdb/qem [...] discards 8bc3928f29 135: onsuccess: #2170: 1: Success after gcc/linux/qemu: 63 commits discards b81ec570c7 134: onsuccess: #2169: 1: Success after binutils/gcc/gdb: 13 [...] discards 5e8362a8a6 133: onsuccess: #2168: 1: Success after binutils/gcc/linux/g [...] discards 578bdc811d 132: onsuccess: #2167: 1: Success after binutils/gcc/glibc/g [...] discards d858c8ec04 131: onsuccess: #2166: 1: Success after binutils/gcc/gdb: 12 [...] discards a98d2c9fd7 130: onsuccess: #2165: 1: Success after binutils/gcc/gdb: 32 [...] discards ef7aeba346 129: onsuccess: #2164: 1: Success after binutils/gcc/linux/g [...] discards ff51604914 128: onsuccess: #2163: 1: Success after linux: 23 commits discards 3195f54efc 127: onsuccess: #2162: 1: Success after gcc: 9 commits discards b60e4fbe71 126: onsuccess: #2161: 1: Success after basepoints/gcc-13-28 [...] discards 99b590d13f 125: onsuccess: #2160: 1: Success after binutils/gcc/linux/g [...] discards d89aad479a 124: onsuccess: #2159: 1: Success after linux: 23 commits discards 31f2b82384 123: onsuccess: #2158: 1: Success after basepoints/gcc-13-28 [...] discards 8a61b6eff3 122: onsuccess: #2157: 1: Success after binutils/gcc/gdb: 6 commits discards 32035d56a0 121: onsuccess: #2156: 1: Success after binutils/gcc/linux/g [...] discards cb24ef69e9 120: onsuccess: #2155: 1: Success after binutils/gcc/linux/g [...] discards 1a195ccf2c 119: onsuccess: #2154: 1: Success after binutils/gcc/linux/g [...] discards 8895b7f3ab 118: onsuccess: #2151: 1: Success after binutils/gcc/linux/g [...] discards ac0a14bee2 117: onsuccess: #2150: 1: Success after binutils/gcc/glibc/g [...] discards 0016c027be 116: onsuccess: #2148: 1: Success after binutils/gcc/gdb: 7 commits discards fa3414147f 115: onsuccess: #2147: 1: Success after binutils/linux/glibc [...] discards d13c0cc66e 114: onsuccess: #2146: 1: Success after binutils/gcc/glibc/g [...] discards 08ead3ab40 113: onsuccess: #2145: 1: Success after binutils/gcc/glibc/g [...] discards 4bde9eaf08 112: onsuccess: #2144: 1: Success after binutils/gcc/glibc/g [...] discards 2350db6b29 111: onsuccess: #2143: 1: Success after binutils/gcc/linux/g [...] discards 483d9a9802 110: onsuccess: #2142: 1: Success after binutils/gcc/glibc/g [...] discards 3f1a9385bc 109: onsuccess: #2141: 1: Success after gcc/glibc: 6 commits discards 3900ecfa7e 108: onsuccess: #2140: 1: Success after binutils/gcc/gdb: 5 commits discards 7def63a7af 107: onsuccess: #2139: 1: Success after binutils/gcc/gdb: 3 commits discards bb661d19ea 106: onsuccess: #2138: 1: Success after binutils/gcc/glibc/g [...] discards 00b6009511 105: onsuccess: #2137: 1: Success after basepoints/gcc-13-27 [...] discards 43b74b7109 104: onsuccess: #2136: 1: Success after binutils/gcc/gdb: 3 commits discards ad61cd3b30 103: onsuccess: #2135: 1: Success after gcc/linux/glibc/gdb/ [...] discards 56bb28da1e 102: onsuccess: #2133: 1: Success after gdb-12-branchpoint-1 [...] discards 8280fe801c 101: onsuccess: #2130: 1: Success after binutils: 81 commits discards 6c4752a182 100: onsuccess: #2077: 1: Success after binutils/gcc/linux/g [...] discards 0673100d7a 99: onsuccess: #2074: 1: Success after baseline build: no ne [...] discards ffa4d35cba 98: onsuccess: #2073: 1: Success after gcc/linux: 11 commits discards 4943098fdc 97: onsuccess: #2072: 1: Success after binutils/gcc/gdb: 3 commits new 6d501f74cc 97: onsuccess: #2072: 1: Success after binutils/gcc/gdb: 3 commits new c33b2b6814 98: onsuccess: #2073: 1: Success after gcc/linux: 11 commits new ff7c2100e0 99: onsuccess: #2074: 1: Success after baseline build: no ne [...] new 7af235f696 100: onsuccess: #2077: 1: Success after binutils/gcc/linux/g [...] new daed771369 101: onsuccess: #2130: 1: Success after binutils: 81 commits new 317c8f565b 102: onsuccess: #2133: 1: Success after gdb-12-branchpoint-1 [...] new 91ebf37f82 103: onsuccess: #2135: 1: Success after gcc/linux/glibc/gdb/ [...] new d538494860 104: onsuccess: #2136: 1: Success after binutils/gcc/gdb: 3 commits new 94fe858e39 105: onsuccess: #2137: 1: Success after basepoints/gcc-13-27 [...] new c922352e3b 106: onsuccess: #2138: 1: Success after binutils/gcc/glibc/g [...] new abce38dea2 107: onsuccess: #2139: 1: Success after binutils/gcc/gdb: 3 commits new 716b8ae25a 108: onsuccess: #2140: 1: Success after binutils/gcc/gdb: 5 commits new e0122567ac 109: onsuccess: #2141: 1: Success after gcc/glibc: 6 commits new 73760d1d30 110: onsuccess: #2142: 1: Success after binutils/gcc/glibc/g [...] new e3700260d5 111: onsuccess: #2143: 1: Success after binutils/gcc/linux/g [...] new 3e16397dfd 112: onsuccess: #2144: 1: Success after binutils/gcc/glibc/g [...] new cd3277c532 113: onsuccess: #2145: 1: Success after binutils/gcc/glibc/g [...] new 4394cc2d1c 114: onsuccess: #2146: 1: Success after binutils/gcc/glibc/g [...] new c3c161a27d 115: onsuccess: #2147: 1: Success after binutils/linux/glibc [...] new e1bfb5bc1b 116: onsuccess: #2148: 1: Success after binutils/gcc/gdb: 7 commits new 764767072a 117: onsuccess: #2150: 1: Success after binutils/gcc/glibc/g [...] new 9219635765 118: onsuccess: #2151: 1: Success after binutils/gcc/linux/g [...] new 3665a98b5a 119: onsuccess: #2154: 1: Success after binutils/gcc/linux/g [...] new 0db98ef53c 120: onsuccess: #2155: 1: Success after binutils/gcc/linux/g [...] new 80d8e31893 121: onsuccess: #2156: 1: Success after binutils/gcc/linux/g [...] new 82e670ba8c 122: onsuccess: #2157: 1: Success after binutils/gcc/gdb: 6 commits new d752cd8086 123: onsuccess: #2158: 1: Success after basepoints/gcc-13-28 [...] new a1cd563d03 124: onsuccess: #2159: 1: Success after linux: 23 commits new 1451fef41b 125: onsuccess: #2160: 1: Success after binutils/gcc/linux/g [...] new 151fabde82 126: onsuccess: #2161: 1: Success after basepoints/gcc-13-28 [...] new 0c1c01472b 127: onsuccess: #2162: 1: Success after gcc: 9 commits new 4142716f3f 128: onsuccess: #2163: 1: Success after linux: 23 commits new f26b8fb3d9 129: onsuccess: #2164: 1: Success after binutils/gcc/linux/g [...] new 2efe8b00c9 130: onsuccess: #2165: 1: Success after binutils/gcc/gdb: 32 [...] new b18606808e 131: onsuccess: #2166: 1: Success after binutils/gcc/gdb: 12 [...] new 31419a566b 132: onsuccess: #2167: 1: Success after binutils/gcc/glibc/g [...] new 1c4c2781a4 133: onsuccess: #2168: 1: Success after binutils/gcc/linux/g [...] new c9b5f609d4 134: onsuccess: #2169: 1: Success after binutils/gcc/gdb: 13 [...] new f3345d0c37 135: onsuccess: #2170: 1: Success after gcc/linux/qemu: 63 commits new 8b547b9ab4 136: onsuccess: #2171: 1: Success after binutils/gcc/gdb/qem [...] new a53f1e1e46 137: onsuccess: #2172: 1: Success after binutils/gcc/linux/g [...] new cd349df131 138: onsuccess: #2173: 1: Success after binutils/gcc/gdb: 5 commits new 8f4a5d3545 139: onsuccess: #2174: 1: Success after binutils/gcc/gdb: 13 [...] new 4c4c49fd61 140: onsuccess: #2175: 1: Success after binutils/gcc/linux/g [...] new d436353eb5 141: onsuccess: #2176: 1: Success after binutils/gcc/gdb: 6 commits new 7249a32999 142: onsuccess: #2177: 1: Success after gcc/glibc: 4 commits new a6725ed2cb 143: onsuccess: #2178: 1: Success after binutils/gcc/gdb/qem [...] new 25d6a28532 144: onsuccess: #2179: 1: Success after binutils/gcc/linux/g [...] new 456f928c91 145: onsuccess: #2180: 1: Success after binutils/gcc/linux/g [...] new 1caa1cda6a 146: onsuccess: #2181: 1: Success after binutils/glibc/gdb: [...] new 5948e8d582 147: onsuccess: #2182: 1: Success after binutils/gcc/gdb: 18 [...] new e28b7c7c7c 148: onsuccess: #2183: 1: Success after gcc/linux/glibc: 64 commits new 73a41822aa 149: onsuccess: #2184: 1: Success after binutils/gcc/linux/g [...] new f2b4907206 150: onsuccess: #2185: 1: Success after gcc: 3 commits new 424e975f68 151: onsuccess: #2186: 1: Success after gcc: 2 commits new 21a45b8b0a 152: onsuccess: #2187: 1: Success after gcc/linux/glibc: 22 commits new f7fceb41d6 153: onsuccess: #2188: 1: Success after binutils/gcc/gdb: 3 commits new e7021505fa 154: onsuccess: #2189: 1: Success after binutils/gcc/gdb: 18 [...] new fc344932e2 155: onsuccess: #2190: 1: Success after binutils/gcc/linux/g [...] new 77a4fb329a 156: onsuccess: #2191: 1: Success after binutils/gcc/linux/g [...] new 5fb259007a 157: onsuccess: #2192: 1: Success after binutils/gcc/gdb: 8 commits new 17468a7192 158: onsuccess: #2193: 1: Success after binutils/gcc/glibc/g [...] new 3dca5797fd 159: onsuccess: #2194: 1: Success after gcc/linux/glibc: 197 [...] new 0b8e35c4a1 160: onsuccess: #2195: 1: Success after binutils/gcc/linux/g [...] new 2445d2b49b 161: onsuccess: #2196: 1: Success after binutils/gcc/linux/g [...] new 18164824a2 162: onsuccess: #2197: 1: Success after binutils/gcc/glibc/g [...] new cf16d25c97 163: onsuccess: #2198: 1: Success after binutils/gcc/linux/g [...] new 76ddde8e86 164: onsuccess: #2199: 1: Success after binutils/gcc/linux/g [...] new 905525e38c 165: onsuccess: #2200: 1: Success after binutils/gdb: 8 commits new 4c9cac08cd 166: onsuccess: #2201: 1: Success after gcc/glibc/qemu: 40 commits new aadd80c320 167: onsuccess: #2202: 1: Success after gcc/linux/glibc/qemu [...] new e421a67116 168: onsuccess: #2203: 1: Success after binutils/gcc/glibc/g [...] new 32713b1c3e 169: onsuccess: #2204: 1: Success after binutils/gcc/glibc/g [...] new 37e10ba978 170: onsuccess: #2205: 1: Success after binutils/gcc/glibc/g [...] new 44972995f6 171: onsuccess: #2206: 1: Success after binutils/gcc/linux/g [...] new 41ff22f501 172: onsuccess: #2207: 1: Success after binutils/gcc/linux/g [...] new 7c7b9f4850 173: onsuccess: #2208: 1: Success after gcc: 10 commits new 7ea64ab81f 174: onsuccess: #2209: 1: Success after binutils/gcc/gdb: 20 [...] new 0bd017d6ca 175: onsuccess: #2210: 1: Success after binutils/gcc/linux/g [...] new bbcaa150f5 176: onsuccess: #2211: 1: Success after binutils/gcc/linux/g [...] new 1629808b51 177: onsuccess: #2212: 1: Success after binutils/gdb: 2 commits new 77c7f0cdb3 178: onsuccess: #2217: 1: Success after binutils/gcc/linux/g [...] new d5eb583956 179: onsuccess: #2230: 1: Success after binutils/gcc/linux/g [...] new ddec1f30a8 180: onsuccess: #2232: 1: Success after binutils/gcc/glibc/g [...] new 78feedb726 181: onsuccess: #2239: 1: Success after binutils/gcc/linux/g [...] new 907b3e2275 182: onsuccess: #2247: 1: Success after binutils/gcc/linux/g [...] new eaefdfdc2a 183: onsuccess: #2270: 1: Success after binutils/gcc/linux/g [...] new d011156889 184: onsuccess: #2288: 1: Success after binutils/gcc/linux/g [...] new 132b6bdaf2 185: onsuccess: #2290: 1: Success after binutils/gcc/linux/g [...] new a09fd91123 186: onsuccess: #2291: 1: Success after binutils/gcc/linux/g [...] new 27b9f6cfde 187: onsuccess: #2294: 1: Success after binutils/gcc/linux/g [...] new 5f9691a066 188: onsuccess: #2295: 1: Success after binutils/gcc/linux/g [...] new ebd5463179 189: onsuccess: #2299: 1: Success after binutils/gcc/linux/g [...] new 8a736e702e 190: onsuccess: #2330: 1: Success after binutils/gcc/linux/g [...] new 981a72a170 191: onsuccess: #2331: 1: Success after gcc/qemu: 90 commits new 3117d32adf 192: onsuccess: #2338: 1: Success after binutils/gcc/linux/g [...] new 8132e02cdf 193: onsuccess: #2339: 1: Success after binutils/gcc/glibc/g [...] new 3d4a5acfc9 194: onsuccess: #2340: 1: Success after binutils/gcc/linux/g [...] new ce931d86e7 195: onsuccess: #2341: 1: Success after binutils/gcc/linux/g [...] new 066c8652d4 196: onsuccess: #2342: 1: Success after binutils/gcc/gdb: 41 [...] new 2b8500e71c 197: onsuccess: #2348: 1: Success after linux: 190 commits new 67851a3a25 198: onsuccess: #2360: 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 (cdd8ee3bd2) \ 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 1744 -> 1728 bytes 02-prepare_abe/console.log.xz | Bin 2724 -> 2732 bytes 03-build_abe-binutils/console.log.xz | Bin 30580 -> 30696 bytes 04-build_abe-stage1/console.log.xz | Bin 71736 -> 73000 bytes 06-build_abe-linux/console.log.xz | Bin 9124 -> 8340 bytes 07-build_abe-glibc/console.log.xz | Bin 244740 -> 244268 bytes 08-build_abe-stage2/console.log.xz | Bin 202416 -> 203532 bytes 09-build_abe-gdb/console.log.xz | Bin 38228 -> 37876 bytes 10-build_abe-qemu/console.log.xz | Bin 31484 -> 31300 bytes 11-build_abe-dejagnu/console.log.xz | Bin 3932 -> 3888 bytes 12-build_abe-check_gcc/console.log.xz | Bin 2692 -> 2836 bytes 13-check_regression/console.log.xz | Bin 14260 -> 11600 bytes 13-check_regression/extra-bisect-params | 2 +- 13-check_regression/fails.sum | 56 +- 13-check_regression/mail-body.txt | 166 +- 13-check_regression/results.compare | 98 +- 13-check_regression/results.compare2 | 2848 ++++--------------- 13-check_regression/results.regressions | 98 +- 14-update_baseline/console.log | 58 +- 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 +- git/qemu_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 168 +- mail/mail-subject.txt | 2 +- manifest.sh | 43 +- results | 98 +- sumfiles/g++.log.xz | Bin 3457988 -> 3438172 bytes sumfiles/g++.sum | 181 +- sumfiles/gcc.log.xz | Bin 3030424 -> 3057456 bytes sumfiles/gcc.sum | 4724 +++++++++++++++++-------------- sumfiles/gfortran.log.xz | Bin 1045872 -> 1039284 bytes sumfiles/gfortran.sum | 49 +- sumfiles/libatomic.log.xz | Bin 2288 -> 2300 bytes sumfiles/libatomic.sum | 2 +- sumfiles/libgomp.log.xz | Bin 213656 -> 213648 bytes sumfiles/libgomp.sum | 2 +- sumfiles/libitm.log.xz | Bin 2696 -> 2692 bytes sumfiles/libitm.sum | 2 +- sumfiles/libstdc++.log.xz | Bin 432008 -> 428312 bytes sumfiles/libstdc++.sum | 36 +- 45 files changed, 3827 insertions(+), 4822 deletions(-)