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 38de7d267d 140: onsuccess: #2175: 1: Success after binutils/gcc/linux/g [...] discards ef04a833e2 139: onsuccess: #2174: 1: Success after binutils/gcc/gdb: 13 [...] discards 16d8cb0893 138: onsuccess: #2173: 1: Success after binutils/gcc/gdb: 5 commits discards 02ab90f984 137: onsuccess: #2172: 1: Success after binutils/gcc/linux/g [...] discards f66f703013 136: onsuccess: #2171: 1: Success after binutils/gcc/gdb/qem [...] discards d98470100a 135: onsuccess: #2170: 1: Success after gcc/linux/qemu: 63 commits discards e994945042 134: onsuccess: #2169: 1: Success after binutils/gcc/gdb: 13 [...] discards 71780998a5 133: onsuccess: #2168: 1: Success after binutils/gcc/linux/g [...] discards 15663f57a3 132: onsuccess: #2167: 1: Success after binutils/gcc/glibc/g [...] discards 5914263c85 131: onsuccess: #2166: 1: Success after binutils/gcc/gdb: 12 [...] discards c755390aca 130: onsuccess: #2165: 1: Success after binutils/gcc/gdb: 32 [...] discards f387cc5e22 129: onsuccess: #2164: 1: Success after binutils/gcc/linux/g [...] discards 5496d26224 128: onsuccess: #2163: 1: Success after linux: 23 commits discards 5d3bd713c8 127: onsuccess: #2162: 1: Success after gcc: 9 commits discards 8b497a51a1 126: onsuccess: #2161: 1: Success after basepoints/gcc-13-28 [...] discards bea9075d3d 125: onsuccess: #2160: 1: Success after binutils/gcc/linux/g [...] discards 1a41eda35c 124: onsuccess: #2159: 1: Success after linux: 23 commits discards b0dc7745e7 123: onsuccess: #2158: 1: Success after basepoints/gcc-13-28 [...] discards 40eabdac44 122: onsuccess: #2157: 1: Success after binutils/gcc/gdb: 6 commits discards 77da1d8ef2 121: onsuccess: #2156: 1: Success after binutils/gcc/linux/g [...] discards 681430a012 120: onsuccess: #2155: 1: Success after binutils/gcc/linux/g [...] discards 369aaacf42 119: onsuccess: #2154: 1: Success after binutils/gcc/linux/g [...] discards 2ae849728b 118: onsuccess: #2151: 1: Success after binutils/gcc/linux/g [...] discards 68d151ede0 117: onsuccess: #2150: 1: Success after binutils/gcc/glibc/g [...] discards eebf3a15d2 116: onsuccess: #2148: 1: Success after binutils/gcc/gdb: 7 commits discards a791da04a7 115: onsuccess: #2147: 1: Success after binutils/linux/glibc [...] discards f63bf6fa30 114: onsuccess: #2146: 1: Success after binutils/gcc/glibc/g [...] discards 948d67d832 113: onsuccess: #2145: 1: Success after binutils/gcc/glibc/g [...] discards a1abfd262e 112: onsuccess: #2144: 1: Success after binutils/gcc/glibc/g [...] discards b3f3dc80c3 111: onsuccess: #2143: 1: Success after binutils/gcc/linux/g [...] discards a85bd70783 110: onsuccess: #2142: 1: Success after binutils/gcc/glibc/g [...] discards 61747f198d 109: onsuccess: #2141: 1: Success after gcc/glibc: 6 commits discards a1ded338ed 108: onsuccess: #2140: 1: Success after binutils/gcc/gdb: 5 commits discards 5a384ba38f 107: onsuccess: #2139: 1: Success after binutils/gcc/gdb: 3 commits discards 729ae34657 106: onsuccess: #2138: 1: Success after binutils/gcc/glibc/g [...] discards e467b646e6 105: onsuccess: #2137: 1: Success after basepoints/gcc-13-27 [...] discards 90c01e991e 104: onsuccess: #2136: 1: Success after binutils/gcc/gdb: 3 commits discards 23963eaf1e 103: onsuccess: #2135: 1: Success after gcc/linux/glibc/gdb/ [...] discards 874dc0548b 102: onsuccess: #2133: 1: Success after gdb-12-branchpoint-1 [...] discards e0595bfa3c 101: onsuccess: #2130: 1: Success after binutils: 81 commits discards 77b735b487 100: onsuccess: #2077: 1: Success after binutils/gcc/linux/g [...] discards d925d54a5e 99: onsuccess: #2074: 1: Success after baseline build: no ne [...] discards 6ed44424cb 98: onsuccess: #2073: 1: Success after gcc/linux: 11 commits discards 1d22d50b8e 97: onsuccess: #2072: 1: Success after binutils/gcc/gdb: 3 commits discards 9285437987 96: onsuccess: #2071: 1: Success after gcc/linux: 56 commits discards ea79fbfbf7 95: onsuccess: #2070: 1: Success after basepoints/gcc-13-238 [...] discards 9714a6dfe8 94: onsuccess: 1: Success after gcc: openmp: Partial OpenMP [...] discards e330b75c5c 93: onsuccess: 1: Success after binutils/gcc/linux/gdb: 88 commits discards ea9bb0408b 92: onsuccess: 1: Success after binutils/gcc/linux/gdb/qemu: [...] discards 4268844807 91: onsuccess: 1: Success after binutils/gcc/gdb: 8 commits discards e4e8562a2b 90: onsuccess: 1: Success after binutils/gcc/gdb: 19 commits discards dc3fb38bb4 89: onsuccess: 1: Success after binutils/gcc/gdb: 5 commits discards 32a36ecfc1 88: onsuccess: 1: Success after gcc/linux/qemu: 149 commits discards a761bd2f6f 87: onsuccess: 1: Success after binutils/gcc/gdb: 14 commits discards 02e4c0d484 86: onsuccess: 1: Success after binutils/gcc/gdb: 7 commits discards 32ded68430 85: onsuccess: 1: Success after binutils/gcc/glibc/gdb/qemu: [...] discards 803f2abc1d 84: onsuccess: 1: Success after binutils/gcc/linux/gdb: 68 commits discards 08e6639e86 83: onsuccess: 1: Success after binutils/gcc/glibc/gdb: 17 commits discards a7d88a121a 82: onsuccess: 1: Successful build after binutils/gcc/gdb: 1 [...] discards 2c08910c30 81: onsuccess: 1: Successful build after binutils/gcc/gdb: 6 [...] discards 21bb330c66 80: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] discards 530cd80ab0 79: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] discards 2fc5d08cd3 78: onsuccess: 1: Successful build after binutils/gcc/gdb: 4 [...] discards fcc1397e64 77: onsuccess: 1: Successful build after gcc/linux/glibc: 22 [...] discards cf8ac6c680 76: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 1f21ff6400 75: onsuccess: 1: Successful build after linux: 44 commits discards 51004375a5 74: onsuccess: 1: Successful build after binutils/gdb: 2 commits discards fd8bc62491 73: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards c9d3df4831 72: onsuccess: 1: Successful build after linux: 12 commits discards 3e6edad1a5 71: onsuccess: 1: Successful build after gcc/glibc: 3 commits discards 1c28025b57 70: onsuccess: 1: Successful build after binutils/gcc/gdb: 4 [...] discards c12825aeee 69: onsuccess: 1: Successful build after binutils/gcc/gdb: 5 [...] discards fb46729c20 68: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 16dd72db71 67: onsuccess: 1: Successful build after binutils/gcc/gdb: 1 [...] discards d4bd4d0a38 66: onsuccess: 1: Successful build after gcc/glibc: 10 commits discards c5c760165e 65: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards c4213c0bbd 64: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards c41823c9a2 63: onsuccess: 1: Successful build after binutils/gcc/gdb: 8 [...] discards 1bdbc100b2 62: onsuccess: 1: Successful build after binutils/gcc/gdb: 2 [...] discards 4f8e12d3e4 61: onsuccess: 1: Successful build after binutils/gcc/gdb/qe [...] discards 5ab6ba0eff 60: onsuccess: 1: Successful build after glibc: 2 commits discards 5c924c1d0b 59: onsuccess: 1: Successful build after binutils: 2 commits discards d79d219a21 58: onsuccess: 1: Successful build after binutils: gdb: new [...] discards 791333ccd0 57: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] discards 7869c77db1 56: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 4855714ea8 55: onsuccess: 1: Successful build after gcc/linux/glibc/qem [...] discards 9efef54265 54: onsuccess: 1: Successful build after binutils/gcc/gdb: 8 [...] discards 7df6cf9065 53: onsuccess: 1: Successful build after binutils/gcc/gdb: 8 [...] discards 3c4b46e809 52: onsuccess: 1: Successful build after binutils/gcc/gdb: 7 [...] discards 3e4e269439 51: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 3e0454c730 50: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] discards 9ed95e11cc 49: onsuccess: 1: Successful build after gcc/glibc: 5 commits discards 806703b2fb 48: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards d28b31de0f 47: onsuccess: 1: Successful build after linux: 10 commits discards d0ff91acf2 46: onsuccess: 1: Successful build after binutils/gdb: 2 commits discards 6a1512cd37 45: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 2b14ca160d 44: onsuccess: 1: Successful build after gcc/linux: 35 commits discards 9bf447e4fd 43: onsuccess: 1: Successful build after gcc: LoongArch: Add [...] discards 8479a8c218 42: onsuccess: 1: Successful build after gcc: libcpp: Implem [...] discards d416f636e8 41: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards e0f4372173 40: onsuccess: 1: Successful build after linux/qemu: 147 commits new d9a130033d 40: onsuccess: 1: Successful build after linux/qemu: 147 commits new a167d8c1f8 41: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 7b76e5991b 42: onsuccess: 1: Successful build after gcc: libcpp: Implem [...] new e512667d39 43: onsuccess: 1: Successful build after gcc: LoongArch: Add [...] new 6f0f5a21d0 44: onsuccess: 1: Successful build after gcc/linux: 35 commits new 64becad8be 45: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 7e04321469 46: onsuccess: 1: Successful build after binutils/gdb: 2 commits new 3f6c2c991a 47: onsuccess: 1: Successful build after linux: 10 commits new 8d300b6f15 48: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new a03befecb3 49: onsuccess: 1: Successful build after gcc/glibc: 5 commits new cf4acf9bab 50: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] new 02e393cc1e 51: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new c54588ad85 52: onsuccess: 1: Successful build after binutils/gcc/gdb: 7 [...] new 9ed32bc9a0 53: onsuccess: 1: Successful build after binutils/gcc/gdb: 8 [...] new 2c000c4bcf 54: onsuccess: 1: Successful build after binutils/gcc/gdb: 8 [...] new 2b00d9a9f9 55: onsuccess: 1: Successful build after gcc/linux/glibc/qem [...] new de844407a2 56: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 17fe9d2c9f 57: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] new c345d91720 58: onsuccess: 1: Successful build after binutils: gdb: new [...] new b5e9fddb2a 59: onsuccess: 1: Successful build after binutils: 2 commits new b40262ff7b 60: onsuccess: 1: Successful build after glibc: 2 commits new 75e51acb66 61: onsuccess: 1: Successful build after binutils/gcc/gdb/qe [...] new 4903446c15 62: onsuccess: 1: Successful build after binutils/gcc/gdb: 2 [...] new 8a23a3c045 63: onsuccess: 1: Successful build after binutils/gcc/gdb: 8 [...] new 33a218cdc4 64: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 24dd4c9489 65: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 3b493e8a8c 66: onsuccess: 1: Successful build after gcc/glibc: 10 commits new 10f70c3ff7 67: onsuccess: 1: Successful build after binutils/gcc/gdb: 1 [...] new f75bb89acc 68: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 1432166b35 69: onsuccess: 1: Successful build after binutils/gcc/gdb: 5 [...] new b0aa1895b1 70: onsuccess: 1: Successful build after binutils/gcc/gdb: 4 [...] new 4710148579 71: onsuccess: 1: Successful build after gcc/glibc: 3 commits new 3fa226fffb 72: onsuccess: 1: Successful build after linux: 12 commits new 1706192c3e 73: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 16ce320760 74: onsuccess: 1: Successful build after binutils/gdb: 2 commits new c3816fe2ce 75: onsuccess: 1: Successful build after linux: 44 commits new cfe5d3cef6 76: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 146f426708 77: onsuccess: 1: Successful build after gcc/linux/glibc: 22 [...] new 51ffadaa3f 78: onsuccess: 1: Successful build after binutils/gcc/gdb: 4 [...] new e04fee8247 79: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] new 4e8aa1faaa 80: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] new bc0eb001f6 81: onsuccess: 1: Successful build after binutils/gcc/gdb: 6 [...] new 3d54447f71 82: onsuccess: 1: Successful build after binutils/gcc/gdb: 1 [...] new 0f2552c4b5 83: onsuccess: 1: Success after binutils/gcc/glibc/gdb: 17 commits new 4738742b2f 84: onsuccess: 1: Success after binutils/gcc/linux/gdb: 68 commits new 801faa2123 85: onsuccess: 1: Success after binutils/gcc/glibc/gdb/qemu: [...] new 210a239a63 86: onsuccess: 1: Success after binutils/gcc/gdb: 7 commits new 3e07639222 87: onsuccess: 1: Success after binutils/gcc/gdb: 14 commits new ede016ed43 88: onsuccess: 1: Success after gcc/linux/qemu: 149 commits new 31c0be90b3 89: onsuccess: 1: Success after binutils/gcc/gdb: 5 commits new cc87a1acd4 90: onsuccess: 1: Success after binutils/gcc/gdb: 19 commits new 76e69a80cd 91: onsuccess: 1: Success after binutils/gcc/gdb: 8 commits new 66f87caf4a 92: onsuccess: 1: Success after binutils/gcc/linux/gdb/qemu: [...] new f2ee325ccf 93: onsuccess: 1: Success after binutils/gcc/linux/gdb: 88 commits new cc8d276911 94: onsuccess: 1: Success after gcc: openmp: Partial OpenMP [...] new bf15ca1202 95: onsuccess: #2070: 1: Success after basepoints/gcc-13-238 [...] new 36b1e24bf9 96: onsuccess: #2071: 1: Success after gcc/linux: 56 commits new fca3856a80 97: onsuccess: #2072: 1: Success after binutils/gcc/gdb: 3 commits new 078a5f6d28 98: onsuccess: #2073: 1: Success after gcc/linux: 11 commits new 3f2deb50b2 99: onsuccess: #2074: 1: Success after baseline build: no ne [...] new b32549dd2e 100: onsuccess: #2077: 1: Success after binutils/gcc/linux/g [...] new df331d3b08 101: onsuccess: #2130: 1: Success after binutils: 81 commits new 141f727347 102: onsuccess: #2133: 1: Success after gdb-12-branchpoint-1 [...] new ed1d09cdf1 103: onsuccess: #2135: 1: Success after gcc/linux/glibc/gdb/ [...] new ef378a55ce 104: onsuccess: #2136: 1: Success after binutils/gcc/gdb: 3 commits new f1cfe38791 105: onsuccess: #2137: 1: Success after basepoints/gcc-13-27 [...] new a1176844f0 106: onsuccess: #2138: 1: Success after binutils/gcc/glibc/g [...] new 1467f7f69c 107: onsuccess: #2139: 1: Success after binutils/gcc/gdb: 3 commits new 6b7dadc842 108: onsuccess: #2140: 1: Success after binutils/gcc/gdb: 5 commits new 8b506db7e7 109: onsuccess: #2141: 1: Success after gcc/glibc: 6 commits new f722ec8a3c 110: onsuccess: #2142: 1: Success after binutils/gcc/glibc/g [...] new 9701187827 111: onsuccess: #2143: 1: Success after binutils/gcc/linux/g [...] new edeeecdac8 112: onsuccess: #2144: 1: Success after binutils/gcc/glibc/g [...] new 8ed571f30b 113: onsuccess: #2145: 1: Success after binutils/gcc/glibc/g [...] new 0b064598b2 114: onsuccess: #2146: 1: Success after binutils/gcc/glibc/g [...] new 1fd0ab8298 115: onsuccess: #2147: 1: Success after binutils/linux/glibc [...] new 054927852c 116: onsuccess: #2148: 1: Success after binutils/gcc/gdb: 7 commits new 704e6cf58f 117: onsuccess: #2150: 1: Success after binutils/gcc/glibc/g [...] new b677870f8c 118: onsuccess: #2151: 1: Success after binutils/gcc/linux/g [...] new a8c4f499ae 119: onsuccess: #2154: 1: Success after binutils/gcc/linux/g [...] new 6849480045 120: onsuccess: #2155: 1: Success after binutils/gcc/linux/g [...] new 23ee3af466 121: onsuccess: #2156: 1: Success after binutils/gcc/linux/g [...] new 5784221756 122: onsuccess: #2157: 1: Success after binutils/gcc/gdb: 6 commits new 3b42233454 123: onsuccess: #2158: 1: Success after basepoints/gcc-13-28 [...] new e0171c1113 124: onsuccess: #2159: 1: Success after linux: 23 commits new 31ac2d584a 125: onsuccess: #2160: 1: Success after binutils/gcc/linux/g [...] new 7211a661a1 126: onsuccess: #2161: 1: Success after basepoints/gcc-13-28 [...] new e3b8a3ff39 127: onsuccess: #2162: 1: Success after gcc: 9 commits new 2098c90a09 128: onsuccess: #2163: 1: Success after linux: 23 commits new ed4be7e2f8 129: onsuccess: #2164: 1: Success after binutils/gcc/linux/g [...] new 15d3b375f5 130: onsuccess: #2165: 1: Success after binutils/gcc/gdb: 32 [...] new d47a8cb388 131: onsuccess: #2166: 1: Success after binutils/gcc/gdb: 12 [...] new 4832b9f0e7 132: onsuccess: #2167: 1: Success after binutils/gcc/glibc/g [...] new 7478abb5ec 133: onsuccess: #2168: 1: Success after binutils/gcc/linux/g [...] new 307475a6cb 134: onsuccess: #2169: 1: Success after binutils/gcc/gdb: 13 [...] new 67d81f7394 135: onsuccess: #2170: 1: Success after gcc/linux/qemu: 63 commits new 7e86d3dbf0 136: onsuccess: #2171: 1: Success after binutils/gcc/gdb/qem [...] new a2f21db290 137: onsuccess: #2172: 1: Success after binutils/gcc/linux/g [...] new 17ccc7b3dc 138: onsuccess: #2173: 1: Success after binutils/gcc/gdb: 5 commits new 2e54f72a69 139: onsuccess: #2174: 1: Success after binutils/gcc/gdb: 13 [...] new 11da134dd0 140: onsuccess: #2175: 1: Success after binutils/gcc/linux/g [...] new 10d1816627 141: onsuccess: #2176: 1: Success after binutils/gcc/gdb: 6 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 (38de7d267d) \ 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 1748 -> 1696 bytes 02-prepare_abe/console.log.xz | Bin 2748 -> 2748 bytes 03-build_abe-binutils/console.log.xz | Bin 31696 -> 30228 bytes 04-build_abe-stage1/console.log.xz | Bin 73648 -> 72388 bytes 06-build_abe-linux/console.log.xz | Bin 8712 -> 8728 bytes 07-build_abe-glibc/console.log.xz | Bin 240720 -> 240676 bytes 08-build_abe-stage2/console.log.xz | Bin 203236 -> 202640 bytes 09-build_abe-gdb/console.log.xz | Bin 38264 -> 37460 bytes 10-build_abe-qemu/console.log.xz | Bin 31184 -> 31180 bytes 11-build_abe-dejagnu/console.log.xz | Bin 3880 -> 3880 bytes 12-build_abe-check_gcc/console.log.xz | Bin 2916 -> 2460 bytes 13-check_regression/console.log.xz | Bin 6912 -> 5872 bytes 13-check_regression/mail-body.txt | 26 - 13-check_regression/results.compare | 30 +- 13-check_regression/results.compare2 | 76 +- 14-update_baseline/console.log | 64 +- 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 | 28 +- mail/mail-subject.txt | 2 +- manifest.sh | 34 +- sumfiles/g++.log.xz | Bin 3409060 -> 3410432 bytes sumfiles/g++.sum | 66 +- sumfiles/gcc.log.xz | Bin 3033704 -> 3035140 bytes sumfiles/gcc.sum | 3670 ++++++++++++++++----------------- sumfiles/gfortran.log.xz | Bin 1031216 -> 1028168 bytes sumfiles/gfortran.sum | 6 +- sumfiles/libatomic.log.xz | Bin 2292 -> 2288 bytes sumfiles/libatomic.sum | 2 +- sumfiles/libgomp.log.xz | Bin 201944 -> 202040 bytes sumfiles/libgomp.sum | 2 +- sumfiles/libitm.log.xz | Bin 2656 -> 2660 bytes sumfiles/libitm.sum | 2 +- sumfiles/libstdc++.log.xz | Bin 417924 -> 421128 bytes sumfiles/libstdc++.sum | 30 +- 38 files changed, 2007 insertions(+), 2041 deletions(-)