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 09236f63e6 196: onsuccess: #2342: 1: Success after binutils/gcc/gdb: 41 [...] discards 63a909abb2 195: onsuccess: #2341: 1: Success after binutils/gcc/linux/g [...] discards bc6e2483eb 194: onsuccess: #2340: 1: Success after binutils/gcc/linux/g [...] discards 3b32e32133 193: onsuccess: #2339: 1: Success after binutils/gcc/glibc/g [...] discards 7703fa30b4 192: onsuccess: #2338: 1: Success after binutils/gcc/linux/g [...] discards 6a4aa83fdf 191: onsuccess: #2331: 1: Success after gcc/qemu: 90 commits discards 4ae18496c4 190: onsuccess: #2330: 1: Success after binutils/gcc/linux/g [...] discards 0aeed13d90 189: onsuccess: #2299: 1: Success after binutils/gcc/linux/g [...] discards bf6bfd66a9 188: onsuccess: #2295: 1: Success after binutils/gcc/linux/g [...] discards ed95cc7d5d 187: onsuccess: #2294: 1: Success after binutils/gcc/linux/g [...] discards 8e8e4fd72a 186: onsuccess: #2291: 1: Success after binutils/gcc/linux/g [...] discards e4dd25c7ba 185: onsuccess: #2290: 1: Success after binutils/gcc/linux/g [...] discards 21455d9f0f 184: onsuccess: #2288: 1: Success after binutils/gcc/linux/g [...] discards abefb7baee 183: onsuccess: #2270: 1: Success after binutils/gcc/linux/g [...] discards 0dff77cebb 182: onsuccess: #2247: 1: Success after binutils/gcc/linux/g [...] discards a922cdc855 181: onsuccess: #2239: 1: Success after binutils/gcc/linux/g [...] discards 1241678a39 180: onsuccess: #2232: 1: Success after binutils/gcc/glibc/g [...] discards d692b74b81 179: onsuccess: #2230: 1: Success after binutils/gcc/linux/g [...] discards b294c89779 178: onsuccess: #2217: 1: Success after binutils/gcc/linux/g [...] discards 736ea3e8fc 177: onsuccess: #2212: 1: Success after binutils/gdb: 2 commits discards d7a2dd37e4 176: onsuccess: #2211: 1: Success after binutils/gcc/linux/g [...] discards 52216e9d24 175: onsuccess: #2210: 1: Success after binutils/gcc/linux/g [...] discards cd4899444f 174: onsuccess: #2209: 1: Success after binutils/gcc/gdb: 20 [...] discards 2c6f2f5747 173: onsuccess: #2208: 1: Success after gcc: 10 commits discards 651d0f37fc 172: onsuccess: #2207: 1: Success after binutils/gcc/linux/g [...] discards e23596369c 171: onsuccess: #2206: 1: Success after binutils/gcc/linux/g [...] discards 0541815068 170: onsuccess: #2205: 1: Success after binutils/gcc/glibc/g [...] discards c98e2bb1b7 169: onsuccess: #2204: 1: Success after binutils/gcc/glibc/g [...] discards 2124c889d5 168: onsuccess: #2203: 1: Success after binutils/gcc/glibc/g [...] discards 64f2c5924b 167: onsuccess: #2202: 1: Success after gcc/linux/glibc/qemu [...] discards 2be55f7e5a 166: onsuccess: #2201: 1: Success after gcc/glibc/qemu: 40 commits discards 62ec62e2c9 165: onsuccess: #2200: 1: Success after binutils/gdb: 8 commits discards f8ff0e65cc 164: onsuccess: #2199: 1: Success after binutils/gcc/linux/g [...] discards 39f526cb6d 163: onsuccess: #2198: 1: Success after binutils/gcc/linux/g [...] discards 27fe29a6c6 162: onsuccess: #2197: 1: Success after binutils/gcc/glibc/g [...] discards 7ce1ddfc84 161: onsuccess: #2196: 1: Success after binutils/gcc/linux/g [...] discards 30b66dbb17 160: onsuccess: #2195: 1: Success after binutils/gcc/linux/g [...] discards ec43c20720 159: onsuccess: #2194: 1: Success after gcc/linux/glibc: 197 [...] discards 55c3531f7f 158: onsuccess: #2193: 1: Success after binutils/gcc/glibc/g [...] discards dea37c21b3 157: onsuccess: #2192: 1: Success after binutils/gcc/gdb: 8 commits discards b315eea48c 156: onsuccess: #2191: 1: Success after binutils/gcc/linux/g [...] discards b27a1794f2 155: onsuccess: #2190: 1: Success after binutils/gcc/linux/g [...] discards 4aecef3194 154: onsuccess: #2189: 1: Success after binutils/gcc/gdb: 18 [...] discards 9d1d07b7e7 153: onsuccess: #2188: 1: Success after binutils/gcc/gdb: 3 commits discards 33c718b57a 152: onsuccess: #2187: 1: Success after gcc/linux/glibc: 22 commits discards 8fcaa6172a 151: onsuccess: #2186: 1: Success after gcc: 2 commits discards d5a9e5146e 150: onsuccess: #2185: 1: Success after gcc: 3 commits discards d013ab8f25 149: onsuccess: #2184: 1: Success after binutils/gcc/linux/g [...] discards 370348dcf1 148: onsuccess: #2183: 1: Success after gcc/linux/glibc: 64 commits discards 3b032182f6 147: onsuccess: #2182: 1: Success after binutils/gcc/gdb: 18 [...] discards eed28ab554 146: onsuccess: #2181: 1: Success after binutils/glibc/gdb: [...] discards 0c79323868 145: onsuccess: #2180: 1: Success after binutils/gcc/linux/g [...] discards dae5d6a295 144: onsuccess: #2179: 1: Success after binutils/gcc/linux/g [...] discards f20ecb2c99 143: onsuccess: #2178: 1: Success after binutils/gcc/gdb/qem [...] discards b3e077200a 142: onsuccess: #2177: 1: Success after gcc/glibc: 4 commits discards 46b3897e82 141: onsuccess: #2176: 1: Success after binutils/gcc/gdb: 6 commits discards cc8075876f 140: onsuccess: #2175: 1: Success after binutils/gcc/linux/g [...] discards 6720dc10e1 139: onsuccess: #2174: 1: Success after binutils/gcc/gdb: 13 [...] discards 02ea4fcd09 138: onsuccess: #2173: 1: Success after binutils/gcc/gdb: 5 commits discards a3dfbb282b 137: onsuccess: #2172: 1: Success after binutils/gcc/linux/g [...] discards f3c2250eb6 136: onsuccess: #2171: 1: Success after binutils/gcc/gdb/qem [...] discards a67dbc47bf 135: onsuccess: #2170: 1: Success after gcc/linux/qemu: 63 commits discards 0a9eb9e58e 134: onsuccess: #2169: 1: Success after binutils/gcc/gdb: 13 [...] discards 3af086bfbe 133: onsuccess: #2168: 1: Success after binutils/gcc/linux/g [...] discards e441c39990 132: onsuccess: #2167: 1: Success after binutils/gcc/glibc/g [...] discards 010dee64b5 131: onsuccess: #2166: 1: Success after binutils/gcc/gdb: 12 [...] discards 2e35a93bc2 130: onsuccess: #2165: 1: Success after binutils/gcc/gdb: 32 [...] discards f3c0975582 129: onsuccess: #2164: 1: Success after binutils/gcc/linux/g [...] discards 2e5854452c 128: onsuccess: #2163: 1: Success after linux: 23 commits discards bfb0dc47e9 127: onsuccess: #2162: 1: Success after gcc: 9 commits discards 95541e7605 126: onsuccess: #2161: 1: Success after basepoints/gcc-13-28 [...] discards 7c6a6c0d49 125: onsuccess: #2160: 1: Success after binutils/gcc/linux/g [...] discards 8736958129 124: onsuccess: #2159: 1: Success after linux: 23 commits discards c742b7ac96 123: onsuccess: #2158: 1: Success after basepoints/gcc-13-28 [...] discards a23bd5c22b 122: onsuccess: #2157: 1: Success after binutils/gcc/gdb: 6 commits discards f671b051a6 121: onsuccess: #2156: 1: Success after binutils/gcc/linux/g [...] discards 88e3eefc89 120: onsuccess: #2155: 1: Success after binutils/gcc/linux/g [...] discards 0131c13ebe 119: onsuccess: #2154: 1: Success after binutils/gcc/linux/g [...] discards 8ea9064c46 118: onsuccess: #2151: 1: Success after binutils/gcc/linux/g [...] discards facc70e956 117: onsuccess: #2150: 1: Success after binutils/gcc/glibc/g [...] discards 5ace30c2c6 116: onsuccess: #2148: 1: Success after binutils/gcc/gdb: 7 commits discards d29f2d0201 115: onsuccess: #2147: 1: Success after binutils/linux/glibc [...] discards 52484e1242 114: onsuccess: #2146: 1: Success after binutils/gcc/glibc/g [...] discards 5dd4aeef48 113: onsuccess: #2145: 1: Success after binutils/gcc/glibc/g [...] discards d84d327a8d 112: onsuccess: #2144: 1: Success after binutils/gcc/glibc/g [...] discards ab05c5b961 111: onsuccess: #2143: 1: Success after binutils/gcc/linux/g [...] discards e0652d095b 110: onsuccess: #2142: 1: Success after binutils/gcc/glibc/g [...] discards ea487daff6 109: onsuccess: #2141: 1: Success after gcc/glibc: 6 commits discards 8b7ec3034e 108: onsuccess: #2140: 1: Success after binutils/gcc/gdb: 5 commits discards 8ee9041590 107: onsuccess: #2139: 1: Success after binutils/gcc/gdb: 3 commits discards 5e0f3ebec9 106: onsuccess: #2138: 1: Success after binutils/gcc/glibc/g [...] discards 1bb674f467 105: onsuccess: #2137: 1: Success after basepoints/gcc-13-27 [...] discards 6ce921df35 104: onsuccess: #2136: 1: Success after binutils/gcc/gdb: 3 commits discards a3474b0f36 103: onsuccess: #2135: 1: Success after gcc/linux/glibc/gdb/ [...] discards c4948cc07e 102: onsuccess: #2133: 1: Success after gdb-12-branchpoint-1 [...] discards c77e7c65a7 101: onsuccess: #2130: 1: Success after binutils: 81 commits discards fb670afe10 100: onsuccess: #2077: 1: Success after binutils/gcc/linux/g [...] discards e6c9a7bd95 99: onsuccess: #2074: 1: Success after baseline build: no ne [...] discards 4e1397e440 98: onsuccess: #2073: 1: Success after gcc/linux: 11 commits discards c605831d84 97: onsuccess: #2072: 1: Success after binutils/gcc/gdb: 3 commits discards 60cd512aea 96: onsuccess: #2071: 1: Success after gcc/linux: 56 commits new 4c541446ea 96: onsuccess: #2071: 1: Success after gcc/linux: 56 commits new 4943098fdc 97: onsuccess: #2072: 1: Success after binutils/gcc/gdb: 3 commits new ffa4d35cba 98: onsuccess: #2073: 1: Success after gcc/linux: 11 commits new 0673100d7a 99: onsuccess: #2074: 1: Success after baseline build: no ne [...] new 6c4752a182 100: onsuccess: #2077: 1: Success after binutils/gcc/linux/g [...] new 8280fe801c 101: onsuccess: #2130: 1: Success after binutils: 81 commits new 56bb28da1e 102: onsuccess: #2133: 1: Success after gdb-12-branchpoint-1 [...] new ad61cd3b30 103: onsuccess: #2135: 1: Success after gcc/linux/glibc/gdb/ [...] new 43b74b7109 104: onsuccess: #2136: 1: Success after binutils/gcc/gdb: 3 commits new 00b6009511 105: onsuccess: #2137: 1: Success after basepoints/gcc-13-27 [...] new bb661d19ea 106: onsuccess: #2138: 1: Success after binutils/gcc/glibc/g [...] new 7def63a7af 107: onsuccess: #2139: 1: Success after binutils/gcc/gdb: 3 commits new 3900ecfa7e 108: onsuccess: #2140: 1: Success after binutils/gcc/gdb: 5 commits new 3f1a9385bc 109: onsuccess: #2141: 1: Success after gcc/glibc: 6 commits new 483d9a9802 110: onsuccess: #2142: 1: Success after binutils/gcc/glibc/g [...] new 2350db6b29 111: onsuccess: #2143: 1: Success after binutils/gcc/linux/g [...] new 4bde9eaf08 112: onsuccess: #2144: 1: Success after binutils/gcc/glibc/g [...] new 08ead3ab40 113: onsuccess: #2145: 1: Success after binutils/gcc/glibc/g [...] new d13c0cc66e 114: onsuccess: #2146: 1: Success after binutils/gcc/glibc/g [...] new fa3414147f 115: onsuccess: #2147: 1: Success after binutils/linux/glibc [...] new 0016c027be 116: onsuccess: #2148: 1: Success after binutils/gcc/gdb: 7 commits new ac0a14bee2 117: onsuccess: #2150: 1: Success after binutils/gcc/glibc/g [...] new 8895b7f3ab 118: onsuccess: #2151: 1: Success after binutils/gcc/linux/g [...] new 1a195ccf2c 119: onsuccess: #2154: 1: Success after binutils/gcc/linux/g [...] new cb24ef69e9 120: onsuccess: #2155: 1: Success after binutils/gcc/linux/g [...] new 32035d56a0 121: onsuccess: #2156: 1: Success after binutils/gcc/linux/g [...] new 8a61b6eff3 122: onsuccess: #2157: 1: Success after binutils/gcc/gdb: 6 commits new 31f2b82384 123: onsuccess: #2158: 1: Success after basepoints/gcc-13-28 [...] new d89aad479a 124: onsuccess: #2159: 1: Success after linux: 23 commits new 99b590d13f 125: onsuccess: #2160: 1: Success after binutils/gcc/linux/g [...] new b60e4fbe71 126: onsuccess: #2161: 1: Success after basepoints/gcc-13-28 [...] new 3195f54efc 127: onsuccess: #2162: 1: Success after gcc: 9 commits new ff51604914 128: onsuccess: #2163: 1: Success after linux: 23 commits new ef7aeba346 129: onsuccess: #2164: 1: Success after binutils/gcc/linux/g [...] new a98d2c9fd7 130: onsuccess: #2165: 1: Success after binutils/gcc/gdb: 32 [...] new d858c8ec04 131: onsuccess: #2166: 1: Success after binutils/gcc/gdb: 12 [...] new 578bdc811d 132: onsuccess: #2167: 1: Success after binutils/gcc/glibc/g [...] new 5e8362a8a6 133: onsuccess: #2168: 1: Success after binutils/gcc/linux/g [...] new b81ec570c7 134: onsuccess: #2169: 1: Success after binutils/gcc/gdb: 13 [...] new 8bc3928f29 135: onsuccess: #2170: 1: Success after gcc/linux/qemu: 63 commits new 862262d2fc 136: onsuccess: #2171: 1: Success after binutils/gcc/gdb/qem [...] new 6b24760b84 137: onsuccess: #2172: 1: Success after binutils/gcc/linux/g [...] new ee1cf5d71d 138: onsuccess: #2173: 1: Success after binutils/gcc/gdb: 5 commits new 5a1b1f78d5 139: onsuccess: #2174: 1: Success after binutils/gcc/gdb: 13 [...] new a9927c1cc2 140: onsuccess: #2175: 1: Success after binutils/gcc/linux/g [...] new 4079a7a069 141: onsuccess: #2176: 1: Success after binutils/gcc/gdb: 6 commits new 43d88e736a 142: onsuccess: #2177: 1: Success after gcc/glibc: 4 commits new 6f29809566 143: onsuccess: #2178: 1: Success after binutils/gcc/gdb/qem [...] new 9121f4b673 144: onsuccess: #2179: 1: Success after binutils/gcc/linux/g [...] new 9c077cd85d 145: onsuccess: #2180: 1: Success after binutils/gcc/linux/g [...] new 857531f131 146: onsuccess: #2181: 1: Success after binutils/glibc/gdb: [...] new 3740c27d80 147: onsuccess: #2182: 1: Success after binutils/gcc/gdb: 18 [...] new 2be5437052 148: onsuccess: #2183: 1: Success after gcc/linux/glibc: 64 commits new 99991c2b08 149: onsuccess: #2184: 1: Success after binutils/gcc/linux/g [...] new e5a3609b9b 150: onsuccess: #2185: 1: Success after gcc: 3 commits new 43bc857bbc 151: onsuccess: #2186: 1: Success after gcc: 2 commits new 8391d2358b 152: onsuccess: #2187: 1: Success after gcc/linux/glibc: 22 commits new bd93c80d93 153: onsuccess: #2188: 1: Success after binutils/gcc/gdb: 3 commits new ed062a0663 154: onsuccess: #2189: 1: Success after binutils/gcc/gdb: 18 [...] new c1f96cd0f3 155: onsuccess: #2190: 1: Success after binutils/gcc/linux/g [...] new 224bb47e60 156: onsuccess: #2191: 1: Success after binutils/gcc/linux/g [...] new 17c579c46c 157: onsuccess: #2192: 1: Success after binutils/gcc/gdb: 8 commits new 2e1ed56918 158: onsuccess: #2193: 1: Success after binutils/gcc/glibc/g [...] new 4340257808 159: onsuccess: #2194: 1: Success after gcc/linux/glibc: 197 [...] new e7d3242d4c 160: onsuccess: #2195: 1: Success after binutils/gcc/linux/g [...] new 875bd0bca9 161: onsuccess: #2196: 1: Success after binutils/gcc/linux/g [...] new fdac6447f0 162: onsuccess: #2197: 1: Success after binutils/gcc/glibc/g [...] new b73855af08 163: onsuccess: #2198: 1: Success after binutils/gcc/linux/g [...] new 211b1f405f 164: onsuccess: #2199: 1: Success after binutils/gcc/linux/g [...] new 5e9236beea 165: onsuccess: #2200: 1: Success after binutils/gdb: 8 commits new 470776c176 166: onsuccess: #2201: 1: Success after gcc/glibc/qemu: 40 commits new ab7500e46e 167: onsuccess: #2202: 1: Success after gcc/linux/glibc/qemu [...] new 4a78ad11e4 168: onsuccess: #2203: 1: Success after binutils/gcc/glibc/g [...] new 4291e475d6 169: onsuccess: #2204: 1: Success after binutils/gcc/glibc/g [...] new 37b9b7e759 170: onsuccess: #2205: 1: Success after binutils/gcc/glibc/g [...] new 594eb0d031 171: onsuccess: #2206: 1: Success after binutils/gcc/linux/g [...] new 322b4bb7c3 172: onsuccess: #2207: 1: Success after binutils/gcc/linux/g [...] new 92b9fdc31a 173: onsuccess: #2208: 1: Success after gcc: 10 commits new 1af0bed481 174: onsuccess: #2209: 1: Success after binutils/gcc/gdb: 20 [...] new f65d18c4c9 175: onsuccess: #2210: 1: Success after binutils/gcc/linux/g [...] new cde64cbf36 176: onsuccess: #2211: 1: Success after binutils/gcc/linux/g [...] new bde4a1aa6f 177: onsuccess: #2212: 1: Success after binutils/gdb: 2 commits new b2699d7493 178: onsuccess: #2217: 1: Success after binutils/gcc/linux/g [...] new 3609de9006 179: onsuccess: #2230: 1: Success after binutils/gcc/linux/g [...] new 6cffa88e5b 180: onsuccess: #2232: 1: Success after binutils/gcc/glibc/g [...] new f6ff92ae54 181: onsuccess: #2239: 1: Success after binutils/gcc/linux/g [...] new e63d19d0d2 182: onsuccess: #2247: 1: Success after binutils/gcc/linux/g [...] new 9ce93ba86b 183: onsuccess: #2270: 1: Success after binutils/gcc/linux/g [...] new bef55fed9b 184: onsuccess: #2288: 1: Success after binutils/gcc/linux/g [...] new 47ac42b221 185: onsuccess: #2290: 1: Success after binutils/gcc/linux/g [...] new a1a1d5a980 186: onsuccess: #2291: 1: Success after binutils/gcc/linux/g [...] new aedb4d1693 187: onsuccess: #2294: 1: Success after binutils/gcc/linux/g [...] new c1a30f311f 188: onsuccess: #2295: 1: Success after binutils/gcc/linux/g [...] new 21967e4d31 189: onsuccess: #2299: 1: Success after binutils/gcc/linux/g [...] new e8fe2ee4d9 190: onsuccess: #2330: 1: Success after binutils/gcc/linux/g [...] new 14101faf42 191: onsuccess: #2331: 1: Success after gcc/qemu: 90 commits new 8a4304ed17 192: onsuccess: #2338: 1: Success after binutils/gcc/linux/g [...] new 3496f8c28c 193: onsuccess: #2339: 1: Success after binutils/gcc/glibc/g [...] new fa12f1f19a 194: onsuccess: #2340: 1: Success after binutils/gcc/linux/g [...] new c29dee51a2 195: onsuccess: #2341: 1: Success after binutils/gcc/linux/g [...] new 148cdeda71 196: onsuccess: #2342: 1: Success after binutils/gcc/gdb: 41 [...] new cdd8ee3bd2 197: onsuccess: #2348: 1: Success after linux: 190 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 (09236f63e6) \ 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 -> 1744 bytes 02-prepare_abe/console.log.xz | Bin 2728 -> 2724 bytes 03-build_abe-binutils/console.log.xz | Bin 30568 -> 30580 bytes 04-build_abe-stage1/console.log.xz | Bin 71620 -> 71736 bytes 05-clean_sysroot/console.log.xz | Bin 328 -> 328 bytes 06-build_abe-linux/console.log.xz | Bin 9644 -> 9124 bytes 07-build_abe-glibc/console.log.xz | Bin 244300 -> 244740 bytes 08-build_abe-stage2/console.log.xz | Bin 202736 -> 202416 bytes 09-build_abe-gdb/console.log.xz | Bin 37916 -> 38228 bytes 10-build_abe-qemu/console.log.xz | Bin 31812 -> 31484 bytes 11-build_abe-dejagnu/console.log.xz | Bin 3884 -> 3932 bytes 12-build_abe-check_gcc/console.log.xz | Bin 2680 -> 2692 bytes 13-check_regression/console.log.xz | Bin 15268 -> 14260 bytes 13-check_regression/extra-bisect-params | 2 +- 13-check_regression/fails.sum | 36 +- 13-check_regression/mail-body.txt | 127 +- 13-check_regression/results.compare | 62 +- 13-check_regression/results.compare2 | 2459 +++++++++-------- 13-check_regression/results.regressions | 62 +- 14-update_baseline/console.log | 66 +- dashboard/dashboard-generate.sh | 2 +- git/linux_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 129 +- mail/mail-subject.txt | 2 +- manifest.sh | 29 +- results | 62 +- sumfiles/g++.log.xz | Bin 3424888 -> 3457988 bytes sumfiles/g++.sum | 2408 ++++++++--------- sumfiles/gcc.log.xz | Bin 3043492 -> 3030424 bytes sumfiles/gcc.sum | 4450 +++++++++++++++---------------- sumfiles/gfortran.log.xz | Bin 1032104 -> 1045872 bytes sumfiles/gfortran.sum | 42 +- sumfiles/libatomic.log.xz | Bin 2288 -> 2288 bytes sumfiles/libatomic.sum | 4 +- sumfiles/libgomp.log.xz | Bin 213512 -> 213656 bytes sumfiles/libgomp.sum | 16 +- sumfiles/libitm.log.xz | Bin 2692 -> 2696 bytes sumfiles/libitm.sum | 6 +- sumfiles/libstdc++.log.xz | Bin 426540 -> 432008 bytes sumfiles/libstdc++.sum | 14 +- 41 files changed, 4960 insertions(+), 5022 deletions(-)