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 559efce74e 143: onsuccess: #2178: 1: Success after binutils/gcc/gdb/qem [...] discards 63c1f018a9 142: onsuccess: #2177: 1: Success after gcc/glibc: 4 commits discards 176c309d2d 141: onsuccess: #2176: 1: Success after binutils/gcc/gdb: 6 commits discards 5d542afd47 140: onsuccess: #2175: 1: Success after binutils/gcc/linux/g [...] discards 1cbfaacdfe 139: onsuccess: #2174: 1: Success after binutils/gcc/gdb: 13 [...] discards 8d0e41657b 138: onsuccess: #2173: 1: Success after binutils/gcc/gdb: 5 commits discards 0aaa1ab8aa 137: onsuccess: #2172: 1: Success after binutils/gcc/linux/g [...] discards b220e4083f 136: onsuccess: #2171: 1: Success after binutils/gcc/gdb/qem [...] discards c601643a25 135: onsuccess: #2170: 1: Success after gcc/linux/qemu: 63 commits discards ab47990f00 134: onsuccess: #2169: 1: Success after binutils/gcc/gdb: 13 [...] discards 2546f96474 133: onsuccess: #2168: 1: Success after binutils/gcc/linux/g [...] discards a67877bbc1 132: onsuccess: #2167: 1: Success after binutils/gcc/glibc/g [...] discards 8a4ebec102 131: onsuccess: #2166: 1: Success after binutils/gcc/gdb: 12 [...] discards d81eab13c0 130: onsuccess: #2165: 1: Success after binutils/gcc/gdb: 32 [...] discards 5a5872fa27 129: onsuccess: #2164: 1: Success after binutils/gcc/linux/g [...] discards ae05f3b4b4 128: onsuccess: #2163: 1: Success after linux: 23 commits discards bfb1bfc0c9 127: onsuccess: #2162: 1: Success after gcc: 9 commits discards 9543eb0159 126: onsuccess: #2161: 1: Success after basepoints/gcc-13-28 [...] discards a6b098c118 125: onsuccess: #2160: 1: Success after binutils/gcc/linux/g [...] discards ac20a348e6 124: onsuccess: #2159: 1: Success after linux: 23 commits discards da46ab2e3a 123: onsuccess: #2158: 1: Success after basepoints/gcc-13-28 [...] discards 92150ed192 122: onsuccess: #2157: 1: Success after binutils/gcc/gdb: 6 commits discards 2bcef82760 121: onsuccess: #2156: 1: Success after binutils/gcc/linux/g [...] discards d4b22b51a9 120: onsuccess: #2155: 1: Success after binutils/gcc/linux/g [...] discards 7f4431c9c8 119: onsuccess: #2154: 1: Success after binutils/gcc/linux/g [...] discards d6db996dad 118: onsuccess: #2151: 1: Success after binutils/gcc/linux/g [...] discards 32f8f2f378 117: onsuccess: #2150: 1: Success after binutils/gcc/glibc/g [...] discards 3365ff707f 116: onsuccess: #2148: 1: Success after binutils/gcc/gdb: 7 commits discards 85293038a6 115: onsuccess: #2147: 1: Success after binutils/linux/glibc [...] discards 07dbed5b69 114: onsuccess: #2146: 1: Success after binutils/gcc/glibc/g [...] discards 478825db2a 113: onsuccess: #2145: 1: Success after binutils/gcc/glibc/g [...] discards bd98e208d9 112: onsuccess: #2144: 1: Success after binutils/gcc/glibc/g [...] discards 308183741a 111: onsuccess: #2143: 1: Success after binutils/gcc/linux/g [...] discards f528c4fd66 110: onsuccess: #2142: 1: Success after binutils/gcc/glibc/g [...] discards 621013332d 109: onsuccess: #2141: 1: Success after gcc/glibc: 6 commits discards 8a20128be9 108: onsuccess: #2140: 1: Success after binutils/gcc/gdb: 5 commits discards c81b8c2da0 107: onsuccess: #2139: 1: Success after binutils/gcc/gdb: 3 commits discards 4f348016c6 106: onsuccess: #2138: 1: Success after binutils/gcc/glibc/g [...] discards 720167d837 105: onsuccess: #2137: 1: Success after basepoints/gcc-13-27 [...] discards 17e024b2b9 104: onsuccess: #2136: 1: Success after binutils/gcc/gdb: 3 commits discards a0f4b39dcf 103: onsuccess: #2135: 1: Success after gcc/linux/glibc/gdb/ [...] discards dafbbe4143 102: onsuccess: #2133: 1: Success after gdb-12-branchpoint-1 [...] discards 77bf577d27 101: onsuccess: #2130: 1: Success after binutils: 81 commits discards 0f9db10030 100: onsuccess: #2077: 1: Success after binutils/gcc/linux/g [...] discards 594505c342 99: onsuccess: #2074: 1: Success after baseline build: no ne [...] discards 0b6afd01ba 98: onsuccess: #2073: 1: Success after gcc/linux: 11 commits discards d7e61d54c0 97: onsuccess: #2072: 1: Success after binutils/gcc/gdb: 3 commits discards 5072d07e29 96: onsuccess: #2071: 1: Success after gcc/linux: 56 commits discards 081b59a9e8 95: onsuccess: #2070: 1: Success after basepoints/gcc-13-238 [...] discards c6c5c9877b 94: onsuccess: 1: Success after gcc: openmp: Partial OpenMP [...] discards 2d3b9337ca 93: onsuccess: 1: Success after binutils/gcc/linux/gdb: 88 commits discards 713e9c0c0b 92: onsuccess: 1: Success after binutils/gcc/linux/gdb/qemu: [...] discards 1533711e42 91: onsuccess: 1: Success after binutils/gcc/gdb: 8 commits discards 7d19540397 90: onsuccess: 1: Success after binutils/gcc/gdb: 19 commits discards 083e10cb01 89: onsuccess: 1: Success after binutils/gcc/gdb: 5 commits discards 4160c37d91 88: onsuccess: 1: Success after gcc/linux/qemu: 149 commits discards 0aac634ee5 87: onsuccess: 1: Success after binutils/gcc/gdb: 14 commits discards 5ef1cce5bb 86: onsuccess: 1: Success after binutils/gcc/gdb: 7 commits discards 348b38e222 85: onsuccess: 1: Success after binutils/gcc/glibc/gdb/qemu: [...] discards d5fcdf90be 84: onsuccess: 1: Success after binutils/gcc/linux/gdb: 68 commits discards 95b06ad7db 83: onsuccess: 1: Success after binutils/gcc/glibc/gdb: 17 commits discards e20d0c88c5 82: onsuccess: 1: Successful build after binutils/gcc/gdb: 1 [...] discards 40cc24895d 81: onsuccess: 1: Successful build after binutils/gcc/gdb: 6 [...] discards d4c4383191 80: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] discards ecd34921a3 79: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] discards 3ea87441ae 78: onsuccess: 1: Successful build after binutils/gcc/gdb: 4 [...] discards ca0f783001 77: onsuccess: 1: Successful build after gcc/linux/glibc: 22 [...] discards 62e4dedefe 76: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 87e757f75f 75: onsuccess: 1: Successful build after linux: 44 commits discards 7b7cc76188 74: onsuccess: 1: Successful build after binutils/gdb: 2 commits discards f657699241 73: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 3e81242408 72: onsuccess: 1: Successful build after linux: 12 commits discards efa699ba65 71: onsuccess: 1: Successful build after gcc/glibc: 3 commits discards fbf6dcca5f 70: onsuccess: 1: Successful build after binutils/gcc/gdb: 4 [...] discards 089a7423a8 69: onsuccess: 1: Successful build after binutils/gcc/gdb: 5 [...] discards a632f57e6f 68: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 03e9305e26 67: onsuccess: 1: Successful build after binutils/gcc/gdb: 1 [...] discards b147fcc4f8 66: onsuccess: 1: Successful build after gcc/glibc: 10 commits discards 6c2756e778 65: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 8148c1e84f 64: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 060affc95c 63: onsuccess: 1: Successful build after binutils/gcc/gdb: 8 [...] discards af334d65f8 62: onsuccess: 1: Successful build after binutils/gcc/gdb: 2 [...] discards 7cca21bd1d 61: onsuccess: 1: Successful build after binutils/gcc/gdb/qe [...] discards 7a43f08e5a 60: onsuccess: 1: Successful build after glibc: 2 commits discards a0393d2280 59: onsuccess: 1: Successful build after binutils: 2 commits discards 51c303aefb 58: onsuccess: 1: Successful build after binutils: gdb: new [...] discards 06c8e6513c 57: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] discards 5718f2ca00 56: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 6c5d5ad949 55: onsuccess: 1: Successful build after gcc/linux/glibc/qem [...] discards 6914ef00c8 54: onsuccess: 1: Successful build after binutils/gcc/gdb: 8 [...] discards 2ddd6b907e 53: onsuccess: 1: Successful build after binutils/gcc/gdb: 8 [...] discards 7b1207843b 52: onsuccess: 1: Successful build after binutils/gcc/gdb: 7 [...] discards deea8520da 51: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 98c848a442 50: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] discards f28c6a17eb 49: onsuccess: 1: Successful build after gcc/glibc: 5 commits discards f8dc24ae5c 48: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 9edb09341d 47: onsuccess: 1: Successful build after linux: 10 commits discards a1ad0cf0bf 46: onsuccess: 1: Successful build after binutils/gdb: 2 commits discards 052647061a 45: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 7094c1ed0d 44: onsuccess: 1: Successful build after gcc/linux: 35 commits discards 1e87609169 43: onsuccess: 1: Successful build after gcc: LoongArch: Add [...] new 1dc07fe92b 43: onsuccess: 1: Successful build after gcc: LoongArch: Add [...] new 4c8e64bfeb 44: onsuccess: 1: Successful build after gcc/linux: 35 commits new 7d1aa79ddb 45: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new b794509600 46: onsuccess: 1: Successful build after binutils/gdb: 2 commits new e4c56ea6b4 47: onsuccess: 1: Successful build after linux: 10 commits new 5f56201ca0 48: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new df07fe6b22 49: onsuccess: 1: Successful build after gcc/glibc: 5 commits new a578111d8c 50: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] new 9cff3a5581 51: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 84c7016f0c 52: onsuccess: 1: Successful build after binutils/gcc/gdb: 7 [...] new 0dd6c6a1e4 53: onsuccess: 1: Successful build after binutils/gcc/gdb: 8 [...] new ec9b5c2ef3 54: onsuccess: 1: Successful build after binutils/gcc/gdb: 8 [...] new 633b3506cd 55: onsuccess: 1: Successful build after gcc/linux/glibc/qem [...] new 2447fe8794 56: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 7db3f0324b 57: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] new 075b818817 58: onsuccess: 1: Successful build after binutils: gdb: new [...] new ef01651b3e 59: onsuccess: 1: Successful build after binutils: 2 commits new 82b15dd902 60: onsuccess: 1: Successful build after glibc: 2 commits new 823a585d85 61: onsuccess: 1: Successful build after binutils/gcc/gdb/qe [...] new 802563cbad 62: onsuccess: 1: Successful build after binutils/gcc/gdb: 2 [...] new c8e9e63db1 63: onsuccess: 1: Successful build after binutils/gcc/gdb: 8 [...] new 92b2d448a6 64: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 17ff15c2e2 65: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 0a60a8b8c4 66: onsuccess: 1: Successful build after gcc/glibc: 10 commits new 75337e0acc 67: onsuccess: 1: Successful build after binutils/gcc/gdb: 1 [...] new 8811920845 68: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 28d74518b4 69: onsuccess: 1: Successful build after binutils/gcc/gdb: 5 [...] new 42c40d7b79 70: onsuccess: 1: Successful build after binutils/gcc/gdb: 4 [...] new 834dc23130 71: onsuccess: 1: Successful build after gcc/glibc: 3 commits new 81f8ea66b9 72: onsuccess: 1: Successful build after linux: 12 commits new 011ba2bf59 73: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 37c4d2042d 74: onsuccess: 1: Successful build after binutils/gdb: 2 commits new ae4a06046b 75: onsuccess: 1: Successful build after linux: 44 commits new e73bd2505d 76: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new d22e298b04 77: onsuccess: 1: Successful build after gcc/linux/glibc: 22 [...] new 013ac56063 78: onsuccess: 1: Successful build after binutils/gcc/gdb: 4 [...] new cce1c8d871 79: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] new a65a0159e7 80: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] new 4e7908b3dd 81: onsuccess: 1: Successful build after binutils/gcc/gdb: 6 [...] new 49a8ec890d 82: onsuccess: 1: Successful build after binutils/gcc/gdb: 1 [...] new 7324229d23 83: onsuccess: 1: Success after binutils/gcc/glibc/gdb: 17 commits new 4dcb0ee794 84: onsuccess: 1: Success after binutils/gcc/linux/gdb: 68 commits new d6e8ec44b0 85: onsuccess: 1: Success after binutils/gcc/glibc/gdb/qemu: [...] new b99ae2b216 86: onsuccess: 1: Success after binutils/gcc/gdb: 7 commits new 3699c9ad8b 87: onsuccess: 1: Success after binutils/gcc/gdb: 14 commits new dfb04e6904 88: onsuccess: 1: Success after gcc/linux/qemu: 149 commits new 720824ce7b 89: onsuccess: 1: Success after binutils/gcc/gdb: 5 commits new c44754c976 90: onsuccess: 1: Success after binutils/gcc/gdb: 19 commits new 23e74b3960 91: onsuccess: 1: Success after binutils/gcc/gdb: 8 commits new d35d9af008 92: onsuccess: 1: Success after binutils/gcc/linux/gdb/qemu: [...] new c97fbaadcd 93: onsuccess: 1: Success after binutils/gcc/linux/gdb: 88 commits new bc7fb63495 94: onsuccess: 1: Success after gcc: openmp: Partial OpenMP [...] new 4924a09012 95: onsuccess: #2070: 1: Success after basepoints/gcc-13-238 [...] new 8b0d4129a9 96: onsuccess: #2071: 1: Success after gcc/linux: 56 commits new b8ece9096a 97: onsuccess: #2072: 1: Success after binutils/gcc/gdb: 3 commits new 82c202a2f2 98: onsuccess: #2073: 1: Success after gcc/linux: 11 commits new ed58ee5769 99: onsuccess: #2074: 1: Success after baseline build: no ne [...] new 7429d6df35 100: onsuccess: #2077: 1: Success after binutils/gcc/linux/g [...] new 56200baf9a 101: onsuccess: #2130: 1: Success after binutils: 81 commits new 0ed4e327ce 102: onsuccess: #2133: 1: Success after gdb-12-branchpoint-1 [...] new 7c8abf8148 103: onsuccess: #2135: 1: Success after gcc/linux/glibc/gdb/ [...] new e7101e1f17 104: onsuccess: #2136: 1: Success after binutils/gcc/gdb: 3 commits new 329ac8f71e 105: onsuccess: #2137: 1: Success after basepoints/gcc-13-27 [...] new e8dbe7945c 106: onsuccess: #2138: 1: Success after binutils/gcc/glibc/g [...] new df0a126fbd 107: onsuccess: #2139: 1: Success after binutils/gcc/gdb: 3 commits new 1147a614ed 108: onsuccess: #2140: 1: Success after binutils/gcc/gdb: 5 commits new 0572a129ac 109: onsuccess: #2141: 1: Success after gcc/glibc: 6 commits new 732109ff19 110: onsuccess: #2142: 1: Success after binutils/gcc/glibc/g [...] new 333549c8e3 111: onsuccess: #2143: 1: Success after binutils/gcc/linux/g [...] new cc71706965 112: onsuccess: #2144: 1: Success after binutils/gcc/glibc/g [...] new b29cab3f3b 113: onsuccess: #2145: 1: Success after binutils/gcc/glibc/g [...] new 40ce0eb38a 114: onsuccess: #2146: 1: Success after binutils/gcc/glibc/g [...] new 0aab5795a1 115: onsuccess: #2147: 1: Success after binutils/linux/glibc [...] new 6698a29ca8 116: onsuccess: #2148: 1: Success after binutils/gcc/gdb: 7 commits new 1d05e93568 117: onsuccess: #2150: 1: Success after binutils/gcc/glibc/g [...] new 9353fd2f1c 118: onsuccess: #2151: 1: Success after binutils/gcc/linux/g [...] new de494da3aa 119: onsuccess: #2154: 1: Success after binutils/gcc/linux/g [...] new 3a36c6c046 120: onsuccess: #2155: 1: Success after binutils/gcc/linux/g [...] new 889a2782ef 121: onsuccess: #2156: 1: Success after binutils/gcc/linux/g [...] new 4f791791b7 122: onsuccess: #2157: 1: Success after binutils/gcc/gdb: 6 commits new dacf19a3c3 123: onsuccess: #2158: 1: Success after basepoints/gcc-13-28 [...] new 19fde11b1a 124: onsuccess: #2159: 1: Success after linux: 23 commits new db63b028b7 125: onsuccess: #2160: 1: Success after binutils/gcc/linux/g [...] new 104d0201e7 126: onsuccess: #2161: 1: Success after basepoints/gcc-13-28 [...] new 139b987915 127: onsuccess: #2162: 1: Success after gcc: 9 commits new 34c525236c 128: onsuccess: #2163: 1: Success after linux: 23 commits new 57a86c5120 129: onsuccess: #2164: 1: Success after binutils/gcc/linux/g [...] new 5dcfcdc07e 130: onsuccess: #2165: 1: Success after binutils/gcc/gdb: 32 [...] new 072bb16431 131: onsuccess: #2166: 1: Success after binutils/gcc/gdb: 12 [...] new af8166c7d5 132: onsuccess: #2167: 1: Success after binutils/gcc/glibc/g [...] new d8bae3f689 133: onsuccess: #2168: 1: Success after binutils/gcc/linux/g [...] new 863e5c781a 134: onsuccess: #2169: 1: Success after binutils/gcc/gdb: 13 [...] new ce45154710 135: onsuccess: #2170: 1: Success after gcc/linux/qemu: 63 commits new 776c75ef77 136: onsuccess: #2171: 1: Success after binutils/gcc/gdb/qem [...] new dd2518f5f9 137: onsuccess: #2172: 1: Success after binutils/gcc/linux/g [...] new 3d3d6ad826 138: onsuccess: #2173: 1: Success after binutils/gcc/gdb: 5 commits new 6ff51d2f77 139: onsuccess: #2174: 1: Success after binutils/gcc/gdb: 13 [...] new c1c9e285a3 140: onsuccess: #2175: 1: Success after binutils/gcc/linux/g [...] new 098c778525 141: onsuccess: #2176: 1: Success after binutils/gcc/gdb: 6 commits new 4a5f7126a3 142: onsuccess: #2177: 1: Success after gcc/glibc: 4 commits new 716e75cfe3 143: onsuccess: #2178: 1: Success after binutils/gcc/gdb/qem [...] new ca61c02b45 144: onsuccess: #2179: 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 (559efce74e) \ 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 1736 -> 1740 bytes 02-prepare_abe/console.log.xz | Bin 2748 -> 2752 bytes 03-build_abe-binutils/console.log.xz | Bin 30264 -> 30200 bytes 04-build_abe-stage1/console.log.xz | Bin 72448 -> 72464 bytes 06-build_abe-linux/console.log.xz | Bin 8716 -> 9288 bytes 07-build_abe-glibc/console.log.xz | Bin 239660 -> 240172 bytes 08-build_abe-stage2/console.log.xz | Bin 202688 -> 202948 bytes 09-build_abe-gdb/console.log.xz | Bin 37300 -> 37528 bytes 10-build_abe-qemu/console.log.xz | Bin 32124 -> 31820 bytes 11-build_abe-dejagnu/console.log.xz | Bin 3884 -> 3876 bytes 12-build_abe-check_gcc/console.log.xz | Bin 2628 -> 2660 bytes 13-check_regression/console.log.xz | Bin 11884 -> 7032 bytes 13-check_regression/extra-bisect-params | 2 +- 13-check_regression/fails.sum | 17 +- 13-check_regression/mail-body.txt | 73 +- 13-check_regression/results.compare | 615 +---- 13-check_regression/results.compare2 | 804 +----- 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/linux_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 75 +- mail/mail-subject.txt | 2 +- manifest.sh | 38 +- results | 98 +- sumfiles/g++.log.xz | Bin 3419800 -> 3413944 bytes sumfiles/g++.sum | 116 +- sumfiles/gcc.log.xz | Bin 3028080 -> 3024756 bytes sumfiles/gcc.sum | 4429 +++++++++++++++---------------- sumfiles/gfortran.log.xz | Bin 1035388 -> 1028436 bytes sumfiles/gfortran.sum | 4 +- sumfiles/libatomic.log.xz | Bin 2288 -> 2292 bytes sumfiles/libatomic.sum | 2 +- sumfiles/libgomp.log.xz | Bin 202004 -> 202196 bytes sumfiles/libgomp.sum | 12 +- sumfiles/libitm.log.xz | Bin 2656 -> 2660 bytes sumfiles/libitm.sum | 2 +- sumfiles/libstdc++.log.xz | Bin 431248 -> 424008 bytes sumfiles/libstdc++.sum | 6 +- 43 files changed, 2570 insertions(+), 3893 deletions(-)