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 2f2bec6cfe 195: onsuccess: #2341: 1: Success after binutils/gcc/linux/g [...] discards 49ec0a81f7 194: onsuccess: #2340: 1: Success after binutils/gcc/linux/g [...] discards aed67338a3 193: onsuccess: #2339: 1: Success after binutils/gcc/glibc/g [...] discards 9a677a9e24 192: onsuccess: #2338: 1: Success after binutils/gcc/linux/g [...] discards 798796adea 191: onsuccess: #2331: 1: Success after gcc/qemu: 90 commits discards c43c4e465a 190: onsuccess: #2330: 1: Success after binutils/gcc/linux/g [...] discards 5087171931 189: onsuccess: #2299: 1: Success after binutils/gcc/linux/g [...] discards d6560c2512 188: onsuccess: #2295: 1: Success after binutils/gcc/linux/g [...] discards 5b3f609a8b 187: onsuccess: #2294: 1: Success after binutils/gcc/linux/g [...] discards 0e3abd2589 186: onsuccess: #2291: 1: Success after binutils/gcc/linux/g [...] discards 37740556da 185: onsuccess: #2290: 1: Success after binutils/gcc/linux/g [...] discards a5a2509bd0 184: onsuccess: #2288: 1: Success after binutils/gcc/linux/g [...] discards 71c00032e1 183: onsuccess: #2270: 1: Success after binutils/gcc/linux/g [...] discards 4c8fe84a19 182: onsuccess: #2247: 1: Success after binutils/gcc/linux/g [...] discards 0e1c9d4ad0 181: onsuccess: #2239: 1: Success after binutils/gcc/linux/g [...] discards 96ba924266 180: onsuccess: #2232: 1: Success after binutils/gcc/glibc/g [...] discards faa347d16c 179: onsuccess: #2230: 1: Success after binutils/gcc/linux/g [...] discards 59ad96262a 178: onsuccess: #2217: 1: Success after binutils/gcc/linux/g [...] discards 9bfc56f449 177: onsuccess: #2212: 1: Success after binutils/gdb: 2 commits discards c644b98807 176: onsuccess: #2211: 1: Success after binutils/gcc/linux/g [...] discards c878692f2d 175: onsuccess: #2210: 1: Success after binutils/gcc/linux/g [...] discards e71cfe9ce5 174: onsuccess: #2209: 1: Success after binutils/gcc/gdb: 20 [...] discards f978795607 173: onsuccess: #2208: 1: Success after gcc: 10 commits discards bb37b4c8f9 172: onsuccess: #2207: 1: Success after binutils/gcc/linux/g [...] discards 6c62ff0ff4 171: onsuccess: #2206: 1: Success after binutils/gcc/linux/g [...] discards d908f480a9 170: onsuccess: #2205: 1: Success after binutils/gcc/glibc/g [...] discards 1753d30c26 169: onsuccess: #2204: 1: Success after binutils/gcc/glibc/g [...] discards b829d22719 168: onsuccess: #2203: 1: Success after binutils/gcc/glibc/g [...] discards 9206980048 167: onsuccess: #2202: 1: Success after gcc/linux/glibc/qemu [...] discards 50356d4c47 166: onsuccess: #2201: 1: Success after gcc/glibc/qemu: 40 commits discards eaadb00d2b 165: onsuccess: #2200: 1: Success after binutils/gdb: 8 commits discards 1d0cc11f92 164: onsuccess: #2199: 1: Success after binutils/gcc/linux/g [...] discards 409898a247 163: onsuccess: #2198: 1: Success after binutils/gcc/linux/g [...] discards c68740fd53 162: onsuccess: #2197: 1: Success after binutils/gcc/glibc/g [...] discards 3d754f3f5f 161: onsuccess: #2196: 1: Success after binutils/gcc/linux/g [...] discards 2f62562e74 160: onsuccess: #2195: 1: Success after binutils/gcc/linux/g [...] discards 07ec8fa71b 159: onsuccess: #2194: 1: Success after gcc/linux/glibc: 197 [...] discards edfdacb7de 158: onsuccess: #2193: 1: Success after binutils/gcc/glibc/g [...] discards 0e92fd7ce1 157: onsuccess: #2192: 1: Success after binutils/gcc/gdb: 8 commits discards 01ffdcf033 156: onsuccess: #2191: 1: Success after binutils/gcc/linux/g [...] discards 7cad52ec33 155: onsuccess: #2190: 1: Success after binutils/gcc/linux/g [...] discards 64d69ddada 154: onsuccess: #2189: 1: Success after binutils/gcc/gdb: 18 [...] discards 7bd570a11a 153: onsuccess: #2188: 1: Success after binutils/gcc/gdb: 3 commits discards 8c9ee7f523 152: onsuccess: #2187: 1: Success after gcc/linux/glibc: 22 commits discards 00a15426f3 151: onsuccess: #2186: 1: Success after gcc: 2 commits discards c46072d750 150: onsuccess: #2185: 1: Success after gcc: 3 commits discards 9fd3efcf0f 149: onsuccess: #2184: 1: Success after binutils/gcc/linux/g [...] discards cece0c6f3b 148: onsuccess: #2183: 1: Success after gcc/linux/glibc: 64 commits discards 4dd399de1a 147: onsuccess: #2182: 1: Success after binutils/gcc/gdb: 18 [...] discards 0d0e5bec9e 146: onsuccess: #2181: 1: Success after binutils/glibc/gdb: [...] discards af1d11b916 145: onsuccess: #2180: 1: Success after binutils/gcc/linux/g [...] discards 1399663b25 144: onsuccess: #2179: 1: Success after binutils/gcc/linux/g [...] discards 5fd9080521 143: onsuccess: #2178: 1: Success after binutils/gcc/gdb/qem [...] discards 48284fbd6b 142: onsuccess: #2177: 1: Success after gcc/glibc: 4 commits discards e8680df484 141: onsuccess: #2176: 1: Success after binutils/gcc/gdb: 6 commits discards 5fd543ed00 140: onsuccess: #2175: 1: Success after binutils/gcc/linux/g [...] discards 7b9cb4e7db 139: onsuccess: #2174: 1: Success after binutils/gcc/gdb: 13 [...] discards 5d86ea00a2 138: onsuccess: #2173: 1: Success after binutils/gcc/gdb: 5 commits discards 917c486505 137: onsuccess: #2172: 1: Success after binutils/gcc/linux/g [...] discards 17f35497cc 136: onsuccess: #2171: 1: Success after binutils/gcc/gdb/qem [...] discards fd9b6aa26d 135: onsuccess: #2170: 1: Success after gcc/linux/qemu: 63 commits discards 8960c89f94 134: onsuccess: #2169: 1: Success after binutils/gcc/gdb: 13 [...] discards 14363d8269 133: onsuccess: #2168: 1: Success after binutils/gcc/linux/g [...] discards 88d9501fda 132: onsuccess: #2167: 1: Success after binutils/gcc/glibc/g [...] discards 5c6cc54e58 131: onsuccess: #2166: 1: Success after binutils/gcc/gdb: 12 [...] discards 097eb542d0 130: onsuccess: #2165: 1: Success after binutils/gcc/gdb: 32 [...] discards ca13c7f321 129: onsuccess: #2164: 1: Success after binutils/gcc/linux/g [...] discards 6df618e17b 128: onsuccess: #2163: 1: Success after linux: 23 commits discards edfaebb6ea 127: onsuccess: #2162: 1: Success after gcc: 9 commits discards 9193345d7b 126: onsuccess: #2161: 1: Success after basepoints/gcc-13-28 [...] discards 03c9dce30a 125: onsuccess: #2160: 1: Success after binutils/gcc/linux/g [...] discards c8c313b90a 124: onsuccess: #2159: 1: Success after linux: 23 commits discards d5a63884d8 123: onsuccess: #2158: 1: Success after basepoints/gcc-13-28 [...] discards df85d3a8fa 122: onsuccess: #2157: 1: Success after binutils/gcc/gdb: 6 commits discards c06abd080f 121: onsuccess: #2156: 1: Success after binutils/gcc/linux/g [...] discards 9bf7c6dbe5 120: onsuccess: #2155: 1: Success after binutils/gcc/linux/g [...] discards 0e4b1ff2a5 119: onsuccess: #2154: 1: Success after binutils/gcc/linux/g [...] discards 14aade8eb0 118: onsuccess: #2151: 1: Success after binutils/gcc/linux/g [...] discards 51acf8a0e3 117: onsuccess: #2150: 1: Success after binutils/gcc/glibc/g [...] discards 9962f503ac 116: onsuccess: #2148: 1: Success after binutils/gcc/gdb: 7 commits discards 327b1f867c 115: onsuccess: #2147: 1: Success after binutils/linux/glibc [...] discards 6a2e42df33 114: onsuccess: #2146: 1: Success after binutils/gcc/glibc/g [...] discards 8f21935884 113: onsuccess: #2145: 1: Success after binutils/gcc/glibc/g [...] discards 0914341f1c 112: onsuccess: #2144: 1: Success after binutils/gcc/glibc/g [...] discards d9851baf47 111: onsuccess: #2143: 1: Success after binutils/gcc/linux/g [...] discards aef91621f9 110: onsuccess: #2142: 1: Success after binutils/gcc/glibc/g [...] discards 00d9d29cdb 109: onsuccess: #2141: 1: Success after gcc/glibc: 6 commits discards 3a680f75d2 108: onsuccess: #2140: 1: Success after binutils/gcc/gdb: 5 commits discards a8a077c7c2 107: onsuccess: #2139: 1: Success after binutils/gcc/gdb: 3 commits discards eef7726585 106: onsuccess: #2138: 1: Success after binutils/gcc/glibc/g [...] discards 374a6655e6 105: onsuccess: #2137: 1: Success after basepoints/gcc-13-27 [...] discards d509ad5f53 104: onsuccess: #2136: 1: Success after binutils/gcc/gdb: 3 commits discards bbfaa50182 103: onsuccess: #2135: 1: Success after gcc/linux/glibc/gdb/ [...] discards f08f90154c 102: onsuccess: #2133: 1: Success after gdb-12-branchpoint-1 [...] discards ef5fb32526 101: onsuccess: #2130: 1: Success after binutils: 81 commits discards ecd697ad0f 100: onsuccess: #2077: 1: Success after binutils/gcc/linux/g [...] discards a5ea7f91e0 99: onsuccess: #2074: 1: Success after baseline build: no ne [...] discards 9754adffbe 98: onsuccess: #2073: 1: Success after gcc/linux: 11 commits discards 63c326f01c 97: onsuccess: #2072: 1: Success after binutils/gcc/gdb: 3 commits discards 9d26ee0fed 96: onsuccess: #2071: 1: Success after gcc/linux: 56 commits discards 9e8c62db13 95: onsuccess: #2070: 1: Success after basepoints/gcc-13-238 [...] new 6bb28ef54c 95: onsuccess: #2070: 1: Success after basepoints/gcc-13-238 [...] new 60cd512aea 96: onsuccess: #2071: 1: Success after gcc/linux: 56 commits new c605831d84 97: onsuccess: #2072: 1: Success after binutils/gcc/gdb: 3 commits new 4e1397e440 98: onsuccess: #2073: 1: Success after gcc/linux: 11 commits new e6c9a7bd95 99: onsuccess: #2074: 1: Success after baseline build: no ne [...] new fb670afe10 100: onsuccess: #2077: 1: Success after binutils/gcc/linux/g [...] new c77e7c65a7 101: onsuccess: #2130: 1: Success after binutils: 81 commits new c4948cc07e 102: onsuccess: #2133: 1: Success after gdb-12-branchpoint-1 [...] new a3474b0f36 103: onsuccess: #2135: 1: Success after gcc/linux/glibc/gdb/ [...] new 6ce921df35 104: onsuccess: #2136: 1: Success after binutils/gcc/gdb: 3 commits new 1bb674f467 105: onsuccess: #2137: 1: Success after basepoints/gcc-13-27 [...] new 5e0f3ebec9 106: onsuccess: #2138: 1: Success after binutils/gcc/glibc/g [...] new 8ee9041590 107: onsuccess: #2139: 1: Success after binutils/gcc/gdb: 3 commits new 8b7ec3034e 108: onsuccess: #2140: 1: Success after binutils/gcc/gdb: 5 commits new ea487daff6 109: onsuccess: #2141: 1: Success after gcc/glibc: 6 commits new e0652d095b 110: onsuccess: #2142: 1: Success after binutils/gcc/glibc/g [...] new ab05c5b961 111: onsuccess: #2143: 1: Success after binutils/gcc/linux/g [...] new d84d327a8d 112: onsuccess: #2144: 1: Success after binutils/gcc/glibc/g [...] new 5dd4aeef48 113: onsuccess: #2145: 1: Success after binutils/gcc/glibc/g [...] new 52484e1242 114: onsuccess: #2146: 1: Success after binutils/gcc/glibc/g [...] new d29f2d0201 115: onsuccess: #2147: 1: Success after binutils/linux/glibc [...] new 5ace30c2c6 116: onsuccess: #2148: 1: Success after binutils/gcc/gdb: 7 commits new facc70e956 117: onsuccess: #2150: 1: Success after binutils/gcc/glibc/g [...] new 8ea9064c46 118: onsuccess: #2151: 1: Success after binutils/gcc/linux/g [...] new 0131c13ebe 119: onsuccess: #2154: 1: Success after binutils/gcc/linux/g [...] new 88e3eefc89 120: onsuccess: #2155: 1: Success after binutils/gcc/linux/g [...] new f671b051a6 121: onsuccess: #2156: 1: Success after binutils/gcc/linux/g [...] new a23bd5c22b 122: onsuccess: #2157: 1: Success after binutils/gcc/gdb: 6 commits new c742b7ac96 123: onsuccess: #2158: 1: Success after basepoints/gcc-13-28 [...] new 8736958129 124: onsuccess: #2159: 1: Success after linux: 23 commits new 7c6a6c0d49 125: onsuccess: #2160: 1: Success after binutils/gcc/linux/g [...] new 95541e7605 126: onsuccess: #2161: 1: Success after basepoints/gcc-13-28 [...] new bfb0dc47e9 127: onsuccess: #2162: 1: Success after gcc: 9 commits new 2e5854452c 128: onsuccess: #2163: 1: Success after linux: 23 commits new f3c0975582 129: onsuccess: #2164: 1: Success after binutils/gcc/linux/g [...] new 2e35a93bc2 130: onsuccess: #2165: 1: Success after binutils/gcc/gdb: 32 [...] new 010dee64b5 131: onsuccess: #2166: 1: Success after binutils/gcc/gdb: 12 [...] new e441c39990 132: onsuccess: #2167: 1: Success after binutils/gcc/glibc/g [...] new 3af086bfbe 133: onsuccess: #2168: 1: Success after binutils/gcc/linux/g [...] new 0a9eb9e58e 134: onsuccess: #2169: 1: Success after binutils/gcc/gdb: 13 [...] new a67dbc47bf 135: onsuccess: #2170: 1: Success after gcc/linux/qemu: 63 commits new f3c2250eb6 136: onsuccess: #2171: 1: Success after binutils/gcc/gdb/qem [...] new a3dfbb282b 137: onsuccess: #2172: 1: Success after binutils/gcc/linux/g [...] new 02ea4fcd09 138: onsuccess: #2173: 1: Success after binutils/gcc/gdb: 5 commits new 6720dc10e1 139: onsuccess: #2174: 1: Success after binutils/gcc/gdb: 13 [...] new cc8075876f 140: onsuccess: #2175: 1: Success after binutils/gcc/linux/g [...] new 46b3897e82 141: onsuccess: #2176: 1: Success after binutils/gcc/gdb: 6 commits new b3e077200a 142: onsuccess: #2177: 1: Success after gcc/glibc: 4 commits new f20ecb2c99 143: onsuccess: #2178: 1: Success after binutils/gcc/gdb/qem [...] new dae5d6a295 144: onsuccess: #2179: 1: Success after binutils/gcc/linux/g [...] new 0c79323868 145: onsuccess: #2180: 1: Success after binutils/gcc/linux/g [...] new eed28ab554 146: onsuccess: #2181: 1: Success after binutils/glibc/gdb: [...] new 3b032182f6 147: onsuccess: #2182: 1: Success after binutils/gcc/gdb: 18 [...] new 370348dcf1 148: onsuccess: #2183: 1: Success after gcc/linux/glibc: 64 commits new d013ab8f25 149: onsuccess: #2184: 1: Success after binutils/gcc/linux/g [...] new d5a9e5146e 150: onsuccess: #2185: 1: Success after gcc: 3 commits new 8fcaa6172a 151: onsuccess: #2186: 1: Success after gcc: 2 commits new 33c718b57a 152: onsuccess: #2187: 1: Success after gcc/linux/glibc: 22 commits new 9d1d07b7e7 153: onsuccess: #2188: 1: Success after binutils/gcc/gdb: 3 commits new 4aecef3194 154: onsuccess: #2189: 1: Success after binutils/gcc/gdb: 18 [...] new b27a1794f2 155: onsuccess: #2190: 1: Success after binutils/gcc/linux/g [...] new b315eea48c 156: onsuccess: #2191: 1: Success after binutils/gcc/linux/g [...] new dea37c21b3 157: onsuccess: #2192: 1: Success after binutils/gcc/gdb: 8 commits new 55c3531f7f 158: onsuccess: #2193: 1: Success after binutils/gcc/glibc/g [...] new ec43c20720 159: onsuccess: #2194: 1: Success after gcc/linux/glibc: 197 [...] new 30b66dbb17 160: onsuccess: #2195: 1: Success after binutils/gcc/linux/g [...] new 7ce1ddfc84 161: onsuccess: #2196: 1: Success after binutils/gcc/linux/g [...] new 27fe29a6c6 162: onsuccess: #2197: 1: Success after binutils/gcc/glibc/g [...] new 39f526cb6d 163: onsuccess: #2198: 1: Success after binutils/gcc/linux/g [...] new f8ff0e65cc 164: onsuccess: #2199: 1: Success after binutils/gcc/linux/g [...] new 62ec62e2c9 165: onsuccess: #2200: 1: Success after binutils/gdb: 8 commits new 2be55f7e5a 166: onsuccess: #2201: 1: Success after gcc/glibc/qemu: 40 commits new 64f2c5924b 167: onsuccess: #2202: 1: Success after gcc/linux/glibc/qemu [...] new 2124c889d5 168: onsuccess: #2203: 1: Success after binutils/gcc/glibc/g [...] new c98e2bb1b7 169: onsuccess: #2204: 1: Success after binutils/gcc/glibc/g [...] new 0541815068 170: onsuccess: #2205: 1: Success after binutils/gcc/glibc/g [...] new e23596369c 171: onsuccess: #2206: 1: Success after binutils/gcc/linux/g [...] new 651d0f37fc 172: onsuccess: #2207: 1: Success after binutils/gcc/linux/g [...] new 2c6f2f5747 173: onsuccess: #2208: 1: Success after gcc: 10 commits new cd4899444f 174: onsuccess: #2209: 1: Success after binutils/gcc/gdb: 20 [...] new 52216e9d24 175: onsuccess: #2210: 1: Success after binutils/gcc/linux/g [...] new d7a2dd37e4 176: onsuccess: #2211: 1: Success after binutils/gcc/linux/g [...] new 736ea3e8fc 177: onsuccess: #2212: 1: Success after binutils/gdb: 2 commits new b294c89779 178: onsuccess: #2217: 1: Success after binutils/gcc/linux/g [...] new d692b74b81 179: onsuccess: #2230: 1: Success after binutils/gcc/linux/g [...] new 1241678a39 180: onsuccess: #2232: 1: Success after binutils/gcc/glibc/g [...] new a922cdc855 181: onsuccess: #2239: 1: Success after binutils/gcc/linux/g [...] new 0dff77cebb 182: onsuccess: #2247: 1: Success after binutils/gcc/linux/g [...] new abefb7baee 183: onsuccess: #2270: 1: Success after binutils/gcc/linux/g [...] new 21455d9f0f 184: onsuccess: #2288: 1: Success after binutils/gcc/linux/g [...] new e4dd25c7ba 185: onsuccess: #2290: 1: Success after binutils/gcc/linux/g [...] new 8e8e4fd72a 186: onsuccess: #2291: 1: Success after binutils/gcc/linux/g [...] new ed95cc7d5d 187: onsuccess: #2294: 1: Success after binutils/gcc/linux/g [...] new bf6bfd66a9 188: onsuccess: #2295: 1: Success after binutils/gcc/linux/g [...] new 0aeed13d90 189: onsuccess: #2299: 1: Success after binutils/gcc/linux/g [...] new 4ae18496c4 190: onsuccess: #2330: 1: Success after binutils/gcc/linux/g [...] new 6a4aa83fdf 191: onsuccess: #2331: 1: Success after gcc/qemu: 90 commits new 7703fa30b4 192: onsuccess: #2338: 1: Success after binutils/gcc/linux/g [...] new 3b32e32133 193: onsuccess: #2339: 1: Success after binutils/gcc/glibc/g [...] new bc6e2483eb 194: onsuccess: #2340: 1: Success after binutils/gcc/linux/g [...] new 63a909abb2 195: onsuccess: #2341: 1: Success after binutils/gcc/linux/g [...] new 09236f63e6 196: onsuccess: #2342: 1: Success after binutils/gcc/gdb: 41 [...]

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 (2f2bec6cfe) \ 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 1700 -> 1696 bytes 02-prepare_abe/console.log.xz | Bin 2744 -> 2728 bytes 03-build_abe-binutils/console.log.xz | Bin 30484 -> 30568 bytes 04-build_abe-stage1/console.log.xz | Bin 71712 -> 71620 bytes 06-build_abe-linux/console.log.xz | Bin 9684 -> 9644 bytes 07-build_abe-glibc/console.log.xz | Bin 243868 -> 244300 bytes 08-build_abe-stage2/console.log.xz | Bin 202748 -> 202736 bytes 09-build_abe-gdb/console.log.xz | Bin 37892 -> 37916 bytes 10-build_abe-qemu/console.log.xz | Bin 31316 -> 31812 bytes 11-build_abe-dejagnu/console.log.xz | Bin 3884 -> 3884 bytes 12-build_abe-check_gcc/console.log.xz | Bin 3060 -> 2680 bytes 13-check_regression/console.log.xz | Bin 6512 -> 15268 bytes 13-check_regression/extra-bisect-params | 2 +- 13-check_regression/fails.sum | 37 +- 13-check_regression/mail-body.txt | 101 +- 13-check_regression/results.compare | 65 +- 13-check_regression/results.compare2 | 2297 ++++++++++++++- 13-check_regression/results.regressions | 65 +- 14-update_baseline/console.log | 58 +- dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- git/gdb_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 103 +- mail/mail-subject.txt | 2 +- manifest.sh | 36 +- results | 65 +- sumfiles/g++.log.xz | Bin 3425084 -> 3424888 bytes sumfiles/g++.sum | 2352 +++++++-------- sumfiles/gcc.log.xz | Bin 3032464 -> 3043492 bytes sumfiles/gcc.sum | 4870 ++++++++++++++++--------------- sumfiles/gfortran.log.xz | Bin 1032044 -> 1032104 bytes sumfiles/gfortran.sum | 2 +- sumfiles/libatomic.log.xz | Bin 2288 -> 2288 bytes sumfiles/libatomic.sum | 2 +- sumfiles/libgomp.log.xz | Bin 213624 -> 213512 bytes sumfiles/libgomp.sum | 2 +- sumfiles/libitm.log.xz | Bin 2692 -> 2692 bytes sumfiles/libitm.sum | 2 +- sumfiles/libstdc++.log.xz | Bin 426532 -> 426540 bytes sumfiles/libstdc++.sum | 28 +- 42 files changed, 6269 insertions(+), 3830 deletions(-)