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 69f73d9795 139: onsuccess: #2174: 1: Success after binutils/gcc/gdb: 13 [...] discards 06cd6faa85 138: onsuccess: #2173: 1: Success after binutils/gcc/gdb: 5 commits discards 7cd2e15403 137: onsuccess: #2172: 1: Success after binutils/gcc/linux/g [...] discards 4e6b207a21 136: onsuccess: #2171: 1: Success after binutils/gcc/gdb/qem [...] discards 60b9037c42 135: onsuccess: #2170: 1: Success after gcc/linux/qemu: 63 commits discards a84ad074fd 134: onsuccess: #2169: 1: Success after binutils/gcc/gdb: 13 [...] discards 7e07b06b77 133: onsuccess: #2168: 1: Success after binutils/gcc/linux/g [...] discards 8aba7c088f 132: onsuccess: #2167: 1: Success after binutils/gcc/glibc/g [...] discards 7c10f5281e 131: onsuccess: #2166: 1: Success after binutils/gcc/gdb: 12 [...] discards faf237ad82 130: onsuccess: #2165: 1: Success after binutils/gcc/gdb: 32 [...] discards 797b5a3450 129: onsuccess: #2164: 1: Success after binutils/gcc/linux/g [...] discards 92a15c9c49 128: onsuccess: #2163: 1: Success after linux: 23 commits discards d28b0dbfa3 127: onsuccess: #2162: 1: Success after gcc: 9 commits discards 8c5ddc89c2 126: onsuccess: #2161: 1: Success after basepoints/gcc-13-28 [...] discards b46c2dab2e 125: onsuccess: #2160: 1: Success after binutils/gcc/linux/g [...] discards 7e31e44fc5 124: onsuccess: #2159: 1: Success after linux: 23 commits discards f0889d9fca 123: onsuccess: #2158: 1: Success after basepoints/gcc-13-28 [...] discards f819b7313b 122: onsuccess: #2157: 1: Success after binutils/gcc/gdb: 6 commits discards 81db3484bc 121: onsuccess: #2156: 1: Success after binutils/gcc/linux/g [...] discards 3fdc9e3d32 120: onsuccess: #2155: 1: Success after binutils/gcc/linux/g [...] discards 10637df200 119: onsuccess: #2154: 1: Success after binutils/gcc/linux/g [...] discards d171b633aa 118: onsuccess: #2151: 1: Success after binutils/gcc/linux/g [...] discards 72fc453c62 117: onsuccess: #2150: 1: Success after binutils/gcc/glibc/g [...] discards be6fb482ab 116: onsuccess: #2148: 1: Success after binutils/gcc/gdb: 7 commits discards e559a385a1 115: onsuccess: #2147: 1: Success after binutils/linux/glibc [...] discards 28fcf058f9 114: onsuccess: #2146: 1: Success after binutils/gcc/glibc/g [...] discards b469269ff9 113: onsuccess: #2145: 1: Success after binutils/gcc/glibc/g [...] discards 96d1c54057 112: onsuccess: #2144: 1: Success after binutils/gcc/glibc/g [...] discards 10ef29a7ca 111: onsuccess: #2143: 1: Success after binutils/gcc/linux/g [...] discards 64f38f8608 110: onsuccess: #2142: 1: Success after binutils/gcc/glibc/g [...] discards f760b09089 109: onsuccess: #2141: 1: Success after gcc/glibc: 6 commits discards 9b632f6114 108: onsuccess: #2140: 1: Success after binutils/gcc/gdb: 5 commits discards 572ee4e788 107: onsuccess: #2139: 1: Success after binutils/gcc/gdb: 3 commits discards 919be69eee 106: onsuccess: #2138: 1: Success after binutils/gcc/glibc/g [...] discards 66283ecc7d 105: onsuccess: #2137: 1: Success after basepoints/gcc-13-27 [...] discards 23b866e7ed 104: onsuccess: #2136: 1: Success after binutils/gcc/gdb: 3 commits discards 7169b786ba 103: onsuccess: #2135: 1: Success after gcc/linux/glibc/gdb/ [...] discards c0a845b919 102: onsuccess: #2133: 1: Success after gdb-12-branchpoint-1 [...] discards d85792145a 101: onsuccess: #2130: 1: Success after binutils: 81 commits discards 94d83e6c06 100: onsuccess: #2077: 1: Success after binutils/gcc/linux/g [...] discards f73a462df2 99: onsuccess: #2074: 1: Success after baseline build: no ne [...] discards 5051b57d87 98: onsuccess: #2073: 1: Success after gcc/linux: 11 commits discards a248bf38ce 97: onsuccess: #2072: 1: Success after binutils/gcc/gdb: 3 commits discards 158668c3d0 96: onsuccess: #2071: 1: Success after gcc/linux: 56 commits discards 52b97f2c8e 95: onsuccess: #2070: 1: Success after basepoints/gcc-13-238 [...] discards ae774e7fc3 94: onsuccess: 1: Success after gcc: openmp: Partial OpenMP [...] discards 68945a0e3e 93: onsuccess: 1: Success after binutils/gcc/linux/gdb: 88 commits discards 17b505317d 92: onsuccess: 1: Success after binutils/gcc/linux/gdb/qemu: [...] discards 06c732fd8e 91: onsuccess: 1: Success after binutils/gcc/gdb: 8 commits discards 258a3687a1 90: onsuccess: 1: Success after binutils/gcc/gdb: 19 commits discards 1c950584c9 89: onsuccess: 1: Success after binutils/gcc/gdb: 5 commits discards 0591079fbf 88: onsuccess: 1: Success after gcc/linux/qemu: 149 commits discards 639f70679a 87: onsuccess: 1: Success after binutils/gcc/gdb: 14 commits discards 39cb4c1361 86: onsuccess: 1: Success after binutils/gcc/gdb: 7 commits discards 315a5e0c1e 85: onsuccess: 1: Success after binutils/gcc/glibc/gdb/qemu: [...] discards 25861d686e 84: onsuccess: 1: Success after binutils/gcc/linux/gdb: 68 commits discards 446192d391 83: onsuccess: 1: Success after binutils/gcc/glibc/gdb: 17 commits discards ae14dac0ab 82: onsuccess: 1: Successful build after binutils/gcc/gdb: 1 [...] discards 599f4fe34d 81: onsuccess: 1: Successful build after binutils/gcc/gdb: 6 [...] discards 9ce820e7cf 80: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] discards 2aef72dd85 79: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] discards 6e045b8196 78: onsuccess: 1: Successful build after binutils/gcc/gdb: 4 [...] discards bb29ee7a29 77: onsuccess: 1: Successful build after gcc/linux/glibc: 22 [...] discards 9124173bcb 76: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 20b357faf7 75: onsuccess: 1: Successful build after linux: 44 commits discards 7232817438 74: onsuccess: 1: Successful build after binutils/gdb: 2 commits discards 0bf8aa8e96 73: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 568a1e85a0 72: onsuccess: 1: Successful build after linux: 12 commits discards 651411b5d9 71: onsuccess: 1: Successful build after gcc/glibc: 3 commits discards b8e3936508 70: onsuccess: 1: Successful build after binutils/gcc/gdb: 4 [...] discards 5eb66a528b 69: onsuccess: 1: Successful build after binutils/gcc/gdb: 5 [...] discards fc5850dc70 68: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 6a482db7a4 67: onsuccess: 1: Successful build after binutils/gcc/gdb: 1 [...] discards 46245355c1 66: onsuccess: 1: Successful build after gcc/glibc: 10 commits discards d4f36a8b78 65: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards a822de45c2 64: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards ec01ff9095 63: onsuccess: 1: Successful build after binutils/gcc/gdb: 8 [...] discards e9ea2f1058 62: onsuccess: 1: Successful build after binutils/gcc/gdb: 2 [...] discards 449b40237c 61: onsuccess: 1: Successful build after binutils/gcc/gdb/qe [...] discards 95ca43bcb3 60: onsuccess: 1: Successful build after glibc: 2 commits discards 428724546e 59: onsuccess: 1: Successful build after binutils: 2 commits discards 628714356d 58: onsuccess: 1: Successful build after binutils: gdb: new [...] discards ad610c3cb4 57: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] discards ed116af7a9 56: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 5b20e84bf1 55: onsuccess: 1: Successful build after gcc/linux/glibc/qem [...] discards c0f923c01e 54: onsuccess: 1: Successful build after binutils/gcc/gdb: 8 [...] discards 7df69e7e90 53: onsuccess: 1: Successful build after binutils/gcc/gdb: 8 [...] discards 4936c6c92e 52: onsuccess: 1: Successful build after binutils/gcc/gdb: 7 [...] discards a4679f20c4 51: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 3f08932939 50: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] discards cf64b59d2d 49: onsuccess: 1: Successful build after gcc/glibc: 5 commits discards 51491ea66a 48: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards ae2d36e74f 47: onsuccess: 1: Successful build after linux: 10 commits discards 4ef3768ed7 46: onsuccess: 1: Successful build after binutils/gdb: 2 commits discards 6378b5d6e9 45: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 81c81ed735 44: onsuccess: 1: Successful build after gcc/linux: 35 commits discards 5ad567a827 43: onsuccess: 1: Successful build after gcc: LoongArch: Add [...] discards 5233713bef 42: onsuccess: 1: Successful build after gcc: libcpp: Implem [...] discards f466793e27 41: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards a099bf322c 40: onsuccess: 1: Successful build after linux/qemu: 147 commits discards 6d03ed6947 39: onsuccess: 1: Successful build after binutils/gcc/gdb/qe [...] new 1003267568 39: onsuccess: 1: Successful build after binutils/gcc/gdb/qe [...] new e0f4372173 40: onsuccess: 1: Successful build after linux/qemu: 147 commits new d416f636e8 41: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 8479a8c218 42: onsuccess: 1: Successful build after gcc: libcpp: Implem [...] new 9bf447e4fd 43: onsuccess: 1: Successful build after gcc: LoongArch: Add [...] new 2b14ca160d 44: onsuccess: 1: Successful build after gcc/linux: 35 commits new 6a1512cd37 45: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new d0ff91acf2 46: onsuccess: 1: Successful build after binutils/gdb: 2 commits new d28b31de0f 47: onsuccess: 1: Successful build after linux: 10 commits new 806703b2fb 48: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 9ed95e11cc 49: onsuccess: 1: Successful build after gcc/glibc: 5 commits new 3e0454c730 50: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] new 3e4e269439 51: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 3c4b46e809 52: onsuccess: 1: Successful build after binutils/gcc/gdb: 7 [...] new 7df6cf9065 53: onsuccess: 1: Successful build after binutils/gcc/gdb: 8 [...] new 9efef54265 54: onsuccess: 1: Successful build after binutils/gcc/gdb: 8 [...] new 4855714ea8 55: onsuccess: 1: Successful build after gcc/linux/glibc/qem [...] new 7869c77db1 56: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 791333ccd0 57: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] new d79d219a21 58: onsuccess: 1: Successful build after binutils: gdb: new [...] new 5c924c1d0b 59: onsuccess: 1: Successful build after binutils: 2 commits new 5ab6ba0eff 60: onsuccess: 1: Successful build after glibc: 2 commits new 4f8e12d3e4 61: onsuccess: 1: Successful build after binutils/gcc/gdb/qe [...] new 1bdbc100b2 62: onsuccess: 1: Successful build after binutils/gcc/gdb: 2 [...] new c41823c9a2 63: onsuccess: 1: Successful build after binutils/gcc/gdb: 8 [...] new c4213c0bbd 64: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new c5c760165e 65: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new d4bd4d0a38 66: onsuccess: 1: Successful build after gcc/glibc: 10 commits new 16dd72db71 67: onsuccess: 1: Successful build after binutils/gcc/gdb: 1 [...] new fb46729c20 68: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new c12825aeee 69: onsuccess: 1: Successful build after binutils/gcc/gdb: 5 [...] new 1c28025b57 70: onsuccess: 1: Successful build after binutils/gcc/gdb: 4 [...] new 3e6edad1a5 71: onsuccess: 1: Successful build after gcc/glibc: 3 commits new c9d3df4831 72: onsuccess: 1: Successful build after linux: 12 commits new fd8bc62491 73: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 51004375a5 74: onsuccess: 1: Successful build after binutils/gdb: 2 commits new 1f21ff6400 75: onsuccess: 1: Successful build after linux: 44 commits new cf8ac6c680 76: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new fcc1397e64 77: onsuccess: 1: Successful build after gcc/linux/glibc: 22 [...] new 2fc5d08cd3 78: onsuccess: 1: Successful build after binutils/gcc/gdb: 4 [...] new 530cd80ab0 79: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] new 21bb330c66 80: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] new 2c08910c30 81: onsuccess: 1: Successful build after binutils/gcc/gdb: 6 [...] new a7d88a121a 82: onsuccess: 1: Successful build after binutils/gcc/gdb: 1 [...] new 08e6639e86 83: onsuccess: 1: Success after binutils/gcc/glibc/gdb: 17 commits new 803f2abc1d 84: onsuccess: 1: Success after binutils/gcc/linux/gdb: 68 commits new 32ded68430 85: onsuccess: 1: Success after binutils/gcc/glibc/gdb/qemu: [...] new 02e4c0d484 86: onsuccess: 1: Success after binutils/gcc/gdb: 7 commits new a761bd2f6f 87: onsuccess: 1: Success after binutils/gcc/gdb: 14 commits new 32a36ecfc1 88: onsuccess: 1: Success after gcc/linux/qemu: 149 commits new dc3fb38bb4 89: onsuccess: 1: Success after binutils/gcc/gdb: 5 commits new e4e8562a2b 90: onsuccess: 1: Success after binutils/gcc/gdb: 19 commits new 4268844807 91: onsuccess: 1: Success after binutils/gcc/gdb: 8 commits new ea9bb0408b 92: onsuccess: 1: Success after binutils/gcc/linux/gdb/qemu: [...] new e330b75c5c 93: onsuccess: 1: Success after binutils/gcc/linux/gdb: 88 commits new 9714a6dfe8 94: onsuccess: 1: Success after gcc: openmp: Partial OpenMP [...] new ea79fbfbf7 95: onsuccess: #2070: 1: Success after basepoints/gcc-13-238 [...] new 9285437987 96: onsuccess: #2071: 1: Success after gcc/linux: 56 commits new 1d22d50b8e 97: onsuccess: #2072: 1: Success after binutils/gcc/gdb: 3 commits new 6ed44424cb 98: onsuccess: #2073: 1: Success after gcc/linux: 11 commits new d925d54a5e 99: onsuccess: #2074: 1: Success after baseline build: no ne [...] new 77b735b487 100: onsuccess: #2077: 1: Success after binutils/gcc/linux/g [...] new e0595bfa3c 101: onsuccess: #2130: 1: Success after binutils: 81 commits new 874dc0548b 102: onsuccess: #2133: 1: Success after gdb-12-branchpoint-1 [...] new 23963eaf1e 103: onsuccess: #2135: 1: Success after gcc/linux/glibc/gdb/ [...] new 90c01e991e 104: onsuccess: #2136: 1: Success after binutils/gcc/gdb: 3 commits new e467b646e6 105: onsuccess: #2137: 1: Success after basepoints/gcc-13-27 [...] new 729ae34657 106: onsuccess: #2138: 1: Success after binutils/gcc/glibc/g [...] new 5a384ba38f 107: onsuccess: #2139: 1: Success after binutils/gcc/gdb: 3 commits new a1ded338ed 108: onsuccess: #2140: 1: Success after binutils/gcc/gdb: 5 commits new 61747f198d 109: onsuccess: #2141: 1: Success after gcc/glibc: 6 commits new a85bd70783 110: onsuccess: #2142: 1: Success after binutils/gcc/glibc/g [...] new b3f3dc80c3 111: onsuccess: #2143: 1: Success after binutils/gcc/linux/g [...] new a1abfd262e 112: onsuccess: #2144: 1: Success after binutils/gcc/glibc/g [...] new 948d67d832 113: onsuccess: #2145: 1: Success after binutils/gcc/glibc/g [...] new f63bf6fa30 114: onsuccess: #2146: 1: Success after binutils/gcc/glibc/g [...] new a791da04a7 115: onsuccess: #2147: 1: Success after binutils/linux/glibc [...] new eebf3a15d2 116: onsuccess: #2148: 1: Success after binutils/gcc/gdb: 7 commits new 68d151ede0 117: onsuccess: #2150: 1: Success after binutils/gcc/glibc/g [...] new 2ae849728b 118: onsuccess: #2151: 1: Success after binutils/gcc/linux/g [...] new 369aaacf42 119: onsuccess: #2154: 1: Success after binutils/gcc/linux/g [...] new 681430a012 120: onsuccess: #2155: 1: Success after binutils/gcc/linux/g [...] new 77da1d8ef2 121: onsuccess: #2156: 1: Success after binutils/gcc/linux/g [...] new 40eabdac44 122: onsuccess: #2157: 1: Success after binutils/gcc/gdb: 6 commits new b0dc7745e7 123: onsuccess: #2158: 1: Success after basepoints/gcc-13-28 [...] new 1a41eda35c 124: onsuccess: #2159: 1: Success after linux: 23 commits new bea9075d3d 125: onsuccess: #2160: 1: Success after binutils/gcc/linux/g [...] new 8b497a51a1 126: onsuccess: #2161: 1: Success after basepoints/gcc-13-28 [...] new 5d3bd713c8 127: onsuccess: #2162: 1: Success after gcc: 9 commits new 5496d26224 128: onsuccess: #2163: 1: Success after linux: 23 commits new f387cc5e22 129: onsuccess: #2164: 1: Success after binutils/gcc/linux/g [...] new c755390aca 130: onsuccess: #2165: 1: Success after binutils/gcc/gdb: 32 [...] new 5914263c85 131: onsuccess: #2166: 1: Success after binutils/gcc/gdb: 12 [...] new 15663f57a3 132: onsuccess: #2167: 1: Success after binutils/gcc/glibc/g [...] new 71780998a5 133: onsuccess: #2168: 1: Success after binutils/gcc/linux/g [...] new e994945042 134: onsuccess: #2169: 1: Success after binutils/gcc/gdb: 13 [...] new d98470100a 135: onsuccess: #2170: 1: Success after gcc/linux/qemu: 63 commits new f66f703013 136: onsuccess: #2171: 1: Success after binutils/gcc/gdb/qem [...] new 02ab90f984 137: onsuccess: #2172: 1: Success after binutils/gcc/linux/g [...] new 16d8cb0893 138: onsuccess: #2173: 1: Success after binutils/gcc/gdb: 5 commits new ef04a833e2 139: onsuccess: #2174: 1: Success after binutils/gcc/gdb: 13 [...] new 38de7d267d 140: onsuccess: #2175: 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 (69f73d9795) \ 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 1704 -> 1748 bytes 02-prepare_abe/console.log.xz | Bin 2740 -> 2748 bytes 03-build_abe-binutils/console.log.xz | Bin 30228 -> 31696 bytes 04-build_abe-stage1/console.log.xz | Bin 72456 -> 73648 bytes 05-clean_sysroot/console.log.xz | Bin 328 -> 328 bytes 06-build_abe-linux/console.log.xz | Bin 9260 -> 8712 bytes 07-build_abe-glibc/console.log.xz | Bin 239744 -> 240720 bytes 08-build_abe-stage2/console.log.xz | Bin 202620 -> 203236 bytes 09-build_abe-gdb/console.log.xz | Bin 37500 -> 38264 bytes 10-build_abe-qemu/console.log.xz | Bin 31168 -> 31184 bytes 11-build_abe-dejagnu/console.log.xz | Bin 3880 -> 3880 bytes 12-build_abe-check_gcc/console.log.xz | Bin 2748 -> 2916 bytes 13-check_regression/console.log.xz | Bin 6000 -> 6912 bytes 13-check_regression/extra-bisect-params | 1 - 13-check_regression/fails.sum | 6 - 13-check_regression/mail-body.txt | 42 +- 13-check_regression/results.compare | 33 +- 13-check_regression/results.compare2 | 56 +- 13-check_regression/results.regressions | 26 - 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 | 44 +- mail/mail-subject.txt | 2 +- manifest.sh | 42 +- results | 26 - sumfiles/g++.log.xz | Bin 3443048 -> 3409060 bytes sumfiles/g++.sum | 181 +- sumfiles/gcc.log.xz | Bin 3000652 -> 3033704 bytes sumfiles/gcc.sum | 5059 ++++++++++++++++--------------- sumfiles/gfortran.log.xz | Bin 1032052 -> 1031216 bytes sumfiles/gfortran.sum | 42 +- sumfiles/libatomic.log.xz | Bin 2288 -> 2292 bytes sumfiles/libatomic.sum | 4 +- sumfiles/libgomp.log.xz | Bin 202160 -> 201944 bytes sumfiles/libgomp.sum | 23 +- sumfiles/libitm.log.xz | Bin 2652 -> 2656 bytes sumfiles/libitm.sum | 6 +- sumfiles/libstdc++.log.xz | Bin 427612 -> 417924 bytes sumfiles/libstdc++.sum | 18 +- 45 files changed, 2840 insertions(+), 2849 deletions(-) delete mode 100644 13-check_regression/extra-bisect-params delete mode 100644 13-check_regression/fails.sum delete mode 100644 13-check_regression/results.regressions