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 c3e3423c2c 142: onsuccess: #2177: 1: Success after gcc/glibc: 4 commits discards 5991096b94 141: onsuccess: #2176: 1: Success after binutils/gcc/gdb: 6 commits discards 19bdbbc8ef 140: onsuccess: #2175: 1: Success after binutils/gcc/linux/g [...] discards 69828f0afd 139: onsuccess: #2174: 1: Success after binutils/gcc/gdb: 13 [...] discards e37b518cc2 138: onsuccess: #2173: 1: Success after binutils/gcc/gdb: 5 commits discards e7328bea59 137: onsuccess: #2172: 1: Success after binutils/gcc/linux/g [...] discards 1dbadf452e 136: onsuccess: #2171: 1: Success after binutils/gcc/gdb/qem [...] discards 858ba6a5b1 135: onsuccess: #2170: 1: Success after gcc/linux/qemu: 63 commits discards ef242e106a 134: onsuccess: #2169: 1: Success after binutils/gcc/gdb: 13 [...] discards da2b820046 133: onsuccess: #2168: 1: Success after binutils/gcc/linux/g [...] discards 9b5fb6074b 132: onsuccess: #2167: 1: Success after binutils/gcc/glibc/g [...] discards 107c55658e 131: onsuccess: #2166: 1: Success after binutils/gcc/gdb: 12 [...] discards f620b0aaf7 130: onsuccess: #2165: 1: Success after binutils/gcc/gdb: 32 [...] discards a57ecc5ffb 129: onsuccess: #2164: 1: Success after binutils/gcc/linux/g [...] discards b1ae24d315 128: onsuccess: #2163: 1: Success after linux: 23 commits discards b8d04cfbcd 127: onsuccess: #2162: 1: Success after gcc: 9 commits discards aefd63be58 126: onsuccess: #2161: 1: Success after basepoints/gcc-13-28 [...] discards a46d41df12 125: onsuccess: #2160: 1: Success after binutils/gcc/linux/g [...] discards c85006db9e 124: onsuccess: #2159: 1: Success after linux: 23 commits discards f6920a1454 123: onsuccess: #2158: 1: Success after basepoints/gcc-13-28 [...] discards 9e4288984d 122: onsuccess: #2157: 1: Success after binutils/gcc/gdb: 6 commits discards 6f227221a6 121: onsuccess: #2156: 1: Success after binutils/gcc/linux/g [...] discards 3e5c9093bb 120: onsuccess: #2155: 1: Success after binutils/gcc/linux/g [...] discards 213d27fb8d 119: onsuccess: #2154: 1: Success after binutils/gcc/linux/g [...] discards f8a7b074fa 118: onsuccess: #2151: 1: Success after binutils/gcc/linux/g [...] discards 364f6f8a63 117: onsuccess: #2150: 1: Success after binutils/gcc/glibc/g [...] discards 46264c099d 116: onsuccess: #2148: 1: Success after binutils/gcc/gdb: 7 commits discards 0d3af21973 115: onsuccess: #2147: 1: Success after binutils/linux/glibc [...] discards 4db62fae35 114: onsuccess: #2146: 1: Success after binutils/gcc/glibc/g [...] discards a33e44ae70 113: onsuccess: #2145: 1: Success after binutils/gcc/glibc/g [...] discards ba8186cee2 112: onsuccess: #2144: 1: Success after binutils/gcc/glibc/g [...] discards 4b0f5dc98d 111: onsuccess: #2143: 1: Success after binutils/gcc/linux/g [...] discards 80e0578881 110: onsuccess: #2142: 1: Success after binutils/gcc/glibc/g [...] discards ff234d6d00 109: onsuccess: #2141: 1: Success after gcc/glibc: 6 commits discards 172b3c1a70 108: onsuccess: #2140: 1: Success after binutils/gcc/gdb: 5 commits discards 2e5fcf8cd5 107: onsuccess: #2139: 1: Success after binutils/gcc/gdb: 3 commits discards fbf398dcb9 106: onsuccess: #2138: 1: Success after binutils/gcc/glibc/g [...] discards a3a588dd4e 105: onsuccess: #2137: 1: Success after basepoints/gcc-13-27 [...] discards bfb13c1d0d 104: onsuccess: #2136: 1: Success after binutils/gcc/gdb: 3 commits discards 0635b3bc05 103: onsuccess: #2135: 1: Success after gcc/linux/glibc/gdb/ [...] discards 390e1ae644 102: onsuccess: #2133: 1: Success after gdb-12-branchpoint-1 [...] discards 91bd13d6c7 101: onsuccess: #2130: 1: Success after binutils: 81 commits discards ce39e6bb0e 100: onsuccess: #2077: 1: Success after binutils/gcc/linux/g [...] discards a201202d17 99: onsuccess: #2074: 1: Success after baseline build: no ne [...] discards e971a43e96 98: onsuccess: #2073: 1: Success after gcc/linux: 11 commits discards 4417a91f6f 97: onsuccess: #2072: 1: Success after binutils/gcc/gdb: 3 commits discards 1496d35907 96: onsuccess: #2071: 1: Success after gcc/linux: 56 commits discards aba6821d6a 95: onsuccess: #2070: 1: Success after basepoints/gcc-13-238 [...] discards db65bda313 94: onsuccess: 1: Success after gcc: openmp: Partial OpenMP [...] discards fed515a485 93: onsuccess: 1: Success after binutils/gcc/linux/gdb: 88 commits discards dd206cfdef 92: onsuccess: 1: Success after binutils/gcc/linux/gdb/qemu: [...] discards 7949e76a3c 91: onsuccess: 1: Success after binutils/gcc/gdb: 8 commits discards 068add0064 90: onsuccess: 1: Success after binutils/gcc/gdb: 19 commits discards 3462c82861 89: onsuccess: 1: Success after binutils/gcc/gdb: 5 commits discards 819b82d191 88: onsuccess: 1: Success after gcc/linux/qemu: 149 commits discards ca0ae02b29 87: onsuccess: 1: Success after binutils/gcc/gdb: 14 commits discards 94b50b4f0b 86: onsuccess: 1: Success after binutils/gcc/gdb: 7 commits discards 3c93aa4062 85: onsuccess: 1: Success after binutils/gcc/glibc/gdb/qemu: [...] discards b196f32102 84: onsuccess: 1: Success after binutils/gcc/linux/gdb: 68 commits discards 760082891f 83: onsuccess: 1: Success after binutils/gcc/glibc/gdb: 17 commits discards e9cc93bbb9 82: onsuccess: 1: Successful build after binutils/gcc/gdb: 1 [...] discards 4f414b0c48 81: onsuccess: 1: Successful build after binutils/gcc/gdb: 6 [...] discards c6ea422775 80: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] discards 236a897d35 79: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] discards 19bc8f956d 78: onsuccess: 1: Successful build after binutils/gcc/gdb: 4 [...] discards 96b8e88b5b 77: onsuccess: 1: Successful build after gcc/linux/glibc: 22 [...] discards 7ca312b261 76: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 27a1d6ce31 75: onsuccess: 1: Successful build after linux: 44 commits discards 615ea1fa4a 74: onsuccess: 1: Successful build after binutils/gdb: 2 commits discards 8b35518804 73: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 1aafb05c0e 72: onsuccess: 1: Successful build after linux: 12 commits discards 08c73d493e 71: onsuccess: 1: Successful build after gcc/glibc: 3 commits discards 520997a4ab 70: onsuccess: 1: Successful build after binutils/gcc/gdb: 4 [...] discards 43061e04d3 69: onsuccess: 1: Successful build after binutils/gcc/gdb: 5 [...] discards 6df35b5c8b 68: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards b3ef27fbb9 67: onsuccess: 1: Successful build after binutils/gcc/gdb: 1 [...] discards 0ef6c90f2e 66: onsuccess: 1: Successful build after gcc/glibc: 10 commits discards 05884f1409 65: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 1a8bdec5d0 64: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 413a6668ec 63: onsuccess: 1: Successful build after binutils/gcc/gdb: 8 [...] discards 4f698996d5 62: onsuccess: 1: Successful build after binutils/gcc/gdb: 2 [...] discards 9a8d644aa6 61: onsuccess: 1: Successful build after binutils/gcc/gdb/qe [...] discards 11a8745103 60: onsuccess: 1: Successful build after glibc: 2 commits discards d3fee574a1 59: onsuccess: 1: Successful build after binutils: 2 commits discards 9dd34eb721 58: onsuccess: 1: Successful build after binutils: gdb: new [...] discards dd01bbf5ba 57: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] discards 549fd99005 56: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards e0ca61a40d 55: onsuccess: 1: Successful build after gcc/linux/glibc/qem [...] discards 80a5e10ed8 54: onsuccess: 1: Successful build after binutils/gcc/gdb: 8 [...] discards 8473b11d85 53: onsuccess: 1: Successful build after binutils/gcc/gdb: 8 [...] discards b6b516fefe 52: onsuccess: 1: Successful build after binutils/gcc/gdb: 7 [...] discards a11525b0b6 51: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 19b9b4e3bc 50: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] discards ac77be0d40 49: onsuccess: 1: Successful build after gcc/glibc: 5 commits discards 820ce7c279 48: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards b461d47beb 47: onsuccess: 1: Successful build after linux: 10 commits discards 29fa249e2d 46: onsuccess: 1: Successful build after binutils/gdb: 2 commits discards a57542f186 45: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 8261438c0a 44: onsuccess: 1: Successful build after gcc/linux: 35 commits discards 0a431ca1dd 43: onsuccess: 1: Successful build after gcc: LoongArch: Add [...] discards b5cd59862c 42: onsuccess: 1: Successful build after gcc: libcpp: Implem [...] new ebb62ebd0e 42: onsuccess: 1: Successful build after gcc: libcpp: Implem [...] new 1e87609169 43: onsuccess: 1: Successful build after gcc: LoongArch: Add [...] new 7094c1ed0d 44: onsuccess: 1: Successful build after gcc/linux: 35 commits new 052647061a 45: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new a1ad0cf0bf 46: onsuccess: 1: Successful build after binutils/gdb: 2 commits new 9edb09341d 47: onsuccess: 1: Successful build after linux: 10 commits new f8dc24ae5c 48: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new f28c6a17eb 49: onsuccess: 1: Successful build after gcc/glibc: 5 commits new 98c848a442 50: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] new deea8520da 51: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 7b1207843b 52: onsuccess: 1: Successful build after binutils/gcc/gdb: 7 [...] new 2ddd6b907e 53: onsuccess: 1: Successful build after binutils/gcc/gdb: 8 [...] new 6914ef00c8 54: onsuccess: 1: Successful build after binutils/gcc/gdb: 8 [...] new 6c5d5ad949 55: onsuccess: 1: Successful build after gcc/linux/glibc/qem [...] new 5718f2ca00 56: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 06c8e6513c 57: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] new 51c303aefb 58: onsuccess: 1: Successful build after binutils: gdb: new [...] new a0393d2280 59: onsuccess: 1: Successful build after binutils: 2 commits new 7a43f08e5a 60: onsuccess: 1: Successful build after glibc: 2 commits new 7cca21bd1d 61: onsuccess: 1: Successful build after binutils/gcc/gdb/qe [...] new af334d65f8 62: onsuccess: 1: Successful build after binutils/gcc/gdb: 2 [...] new 060affc95c 63: onsuccess: 1: Successful build after binutils/gcc/gdb: 8 [...] new 8148c1e84f 64: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 6c2756e778 65: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new b147fcc4f8 66: onsuccess: 1: Successful build after gcc/glibc: 10 commits new 03e9305e26 67: onsuccess: 1: Successful build after binutils/gcc/gdb: 1 [...] new a632f57e6f 68: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 089a7423a8 69: onsuccess: 1: Successful build after binutils/gcc/gdb: 5 [...] new fbf6dcca5f 70: onsuccess: 1: Successful build after binutils/gcc/gdb: 4 [...] new efa699ba65 71: onsuccess: 1: Successful build after gcc/glibc: 3 commits new 3e81242408 72: onsuccess: 1: Successful build after linux: 12 commits new f657699241 73: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 7b7cc76188 74: onsuccess: 1: Successful build after binutils/gdb: 2 commits new 87e757f75f 75: onsuccess: 1: Successful build after linux: 44 commits new 62e4dedefe 76: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new ca0f783001 77: onsuccess: 1: Successful build after gcc/linux/glibc: 22 [...] new 3ea87441ae 78: onsuccess: 1: Successful build after binutils/gcc/gdb: 4 [...] new ecd34921a3 79: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] new d4c4383191 80: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] new 40cc24895d 81: onsuccess: 1: Successful build after binutils/gcc/gdb: 6 [...] new e20d0c88c5 82: onsuccess: 1: Successful build after binutils/gcc/gdb: 1 [...] new 95b06ad7db 83: onsuccess: 1: Success after binutils/gcc/glibc/gdb: 17 commits new d5fcdf90be 84: onsuccess: 1: Success after binutils/gcc/linux/gdb: 68 commits new 348b38e222 85: onsuccess: 1: Success after binutils/gcc/glibc/gdb/qemu: [...] new 5ef1cce5bb 86: onsuccess: 1: Success after binutils/gcc/gdb: 7 commits new 0aac634ee5 87: onsuccess: 1: Success after binutils/gcc/gdb: 14 commits new 4160c37d91 88: onsuccess: 1: Success after gcc/linux/qemu: 149 commits new 083e10cb01 89: onsuccess: 1: Success after binutils/gcc/gdb: 5 commits new 7d19540397 90: onsuccess: 1: Success after binutils/gcc/gdb: 19 commits new 1533711e42 91: onsuccess: 1: Success after binutils/gcc/gdb: 8 commits new 713e9c0c0b 92: onsuccess: 1: Success after binutils/gcc/linux/gdb/qemu: [...] new 2d3b9337ca 93: onsuccess: 1: Success after binutils/gcc/linux/gdb: 88 commits new c6c5c9877b 94: onsuccess: 1: Success after gcc: openmp: Partial OpenMP [...] new 081b59a9e8 95: onsuccess: #2070: 1: Success after basepoints/gcc-13-238 [...] new 5072d07e29 96: onsuccess: #2071: 1: Success after gcc/linux: 56 commits new d7e61d54c0 97: onsuccess: #2072: 1: Success after binutils/gcc/gdb: 3 commits new 0b6afd01ba 98: onsuccess: #2073: 1: Success after gcc/linux: 11 commits new 594505c342 99: onsuccess: #2074: 1: Success after baseline build: no ne [...] new 0f9db10030 100: onsuccess: #2077: 1: Success after binutils/gcc/linux/g [...] new 77bf577d27 101: onsuccess: #2130: 1: Success after binutils: 81 commits new dafbbe4143 102: onsuccess: #2133: 1: Success after gdb-12-branchpoint-1 [...] new a0f4b39dcf 103: onsuccess: #2135: 1: Success after gcc/linux/glibc/gdb/ [...] new 17e024b2b9 104: onsuccess: #2136: 1: Success after binutils/gcc/gdb: 3 commits new 720167d837 105: onsuccess: #2137: 1: Success after basepoints/gcc-13-27 [...] new 4f348016c6 106: onsuccess: #2138: 1: Success after binutils/gcc/glibc/g [...] new c81b8c2da0 107: onsuccess: #2139: 1: Success after binutils/gcc/gdb: 3 commits new 8a20128be9 108: onsuccess: #2140: 1: Success after binutils/gcc/gdb: 5 commits new 621013332d 109: onsuccess: #2141: 1: Success after gcc/glibc: 6 commits new f528c4fd66 110: onsuccess: #2142: 1: Success after binutils/gcc/glibc/g [...] new 308183741a 111: onsuccess: #2143: 1: Success after binutils/gcc/linux/g [...] new bd98e208d9 112: onsuccess: #2144: 1: Success after binutils/gcc/glibc/g [...] new 478825db2a 113: onsuccess: #2145: 1: Success after binutils/gcc/glibc/g [...] new 07dbed5b69 114: onsuccess: #2146: 1: Success after binutils/gcc/glibc/g [...] new 85293038a6 115: onsuccess: #2147: 1: Success after binutils/linux/glibc [...] new 3365ff707f 116: onsuccess: #2148: 1: Success after binutils/gcc/gdb: 7 commits new 32f8f2f378 117: onsuccess: #2150: 1: Success after binutils/gcc/glibc/g [...] new d6db996dad 118: onsuccess: #2151: 1: Success after binutils/gcc/linux/g [...] new 7f4431c9c8 119: onsuccess: #2154: 1: Success after binutils/gcc/linux/g [...] new d4b22b51a9 120: onsuccess: #2155: 1: Success after binutils/gcc/linux/g [...] new 2bcef82760 121: onsuccess: #2156: 1: Success after binutils/gcc/linux/g [...] new 92150ed192 122: onsuccess: #2157: 1: Success after binutils/gcc/gdb: 6 commits new da46ab2e3a 123: onsuccess: #2158: 1: Success after basepoints/gcc-13-28 [...] new ac20a348e6 124: onsuccess: #2159: 1: Success after linux: 23 commits new a6b098c118 125: onsuccess: #2160: 1: Success after binutils/gcc/linux/g [...] new 9543eb0159 126: onsuccess: #2161: 1: Success after basepoints/gcc-13-28 [...] new bfb1bfc0c9 127: onsuccess: #2162: 1: Success after gcc: 9 commits new ae05f3b4b4 128: onsuccess: #2163: 1: Success after linux: 23 commits new 5a5872fa27 129: onsuccess: #2164: 1: Success after binutils/gcc/linux/g [...] new d81eab13c0 130: onsuccess: #2165: 1: Success after binutils/gcc/gdb: 32 [...] new 8a4ebec102 131: onsuccess: #2166: 1: Success after binutils/gcc/gdb: 12 [...] new a67877bbc1 132: onsuccess: #2167: 1: Success after binutils/gcc/glibc/g [...] new 2546f96474 133: onsuccess: #2168: 1: Success after binutils/gcc/linux/g [...] new ab47990f00 134: onsuccess: #2169: 1: Success after binutils/gcc/gdb: 13 [...] new c601643a25 135: onsuccess: #2170: 1: Success after gcc/linux/qemu: 63 commits new b220e4083f 136: onsuccess: #2171: 1: Success after binutils/gcc/gdb/qem [...] new 0aaa1ab8aa 137: onsuccess: #2172: 1: Success after binutils/gcc/linux/g [...] new 8d0e41657b 138: onsuccess: #2173: 1: Success after binutils/gcc/gdb: 5 commits new 1cbfaacdfe 139: onsuccess: #2174: 1: Success after binutils/gcc/gdb: 13 [...] new 5d542afd47 140: onsuccess: #2175: 1: Success after binutils/gcc/linux/g [...] new 176c309d2d 141: onsuccess: #2176: 1: Success after binutils/gcc/gdb: 6 commits new 63c1f018a9 142: onsuccess: #2177: 1: Success after gcc/glibc: 4 commits new 559efce74e 143: onsuccess: #2178: 1: Success after binutils/gcc/gdb/qem [...]

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 (c3e3423c2c) \ 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 1712 -> 1736 bytes 02-prepare_abe/console.log.xz | Bin 2748 -> 2748 bytes 03-build_abe-binutils/console.log.xz | Bin 30224 -> 30264 bytes 04-build_abe-stage1/console.log.xz | Bin 72588 -> 72448 bytes 05-clean_sysroot/console.log.xz | Bin 328 -> 328 bytes 06-build_abe-linux/console.log.xz | Bin 8716 -> 8716 bytes 07-build_abe-glibc/console.log.xz | Bin 239724 -> 239660 bytes 08-build_abe-stage2/console.log.xz | Bin 203176 -> 202688 bytes 09-build_abe-gdb/console.log.xz | Bin 37372 -> 37300 bytes 10-build_abe-qemu/console.log.xz | Bin 31140 -> 32124 bytes 11-build_abe-dejagnu/console.log.xz | Bin 3896 -> 3884 bytes 12-build_abe-check_gcc/console.log.xz | Bin 2916 -> 2628 bytes 13-check_regression/console.log.xz | Bin 5844 -> 11884 bytes 13-check_regression/extra-bisect-params | 1 + 13-check_regression/fails.sum | 16 + 13-check_regression/mail-body.txt | 101 + 13-check_regression/results.compare | 619 +++- 13-check_regression/results.compare2 | 782 ++++- 13-check_regression/results.regressions | 101 + 14-update_baseline/console.log | 64 +- dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- git/gdb_rev | 2 +- git/qemu_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 103 +- mail/mail-subject.txt | 2 +- manifest.sh | 38 +- results | 101 + sumfiles/g++.log.xz | Bin 3415560 -> 3419800 bytes sumfiles/g++.sum | 805 ++--- sumfiles/gcc.log.xz | Bin 3017972 -> 3028080 bytes sumfiles/gcc.sum | 5653 +++++++++++++++---------------- sumfiles/gfortran.log.xz | Bin 1033552 -> 1035388 bytes sumfiles/gfortran.sum | 47 +- sumfiles/libatomic.log.xz | Bin 2300 -> 2288 bytes sumfiles/libatomic.sum | 4 +- sumfiles/libgomp.log.xz | Bin 201968 -> 202004 bytes sumfiles/libgomp.sum | 16 +- sumfiles/libitm.log.xz | Bin 2656 -> 2656 bytes sumfiles/libitm.sum | 6 +- sumfiles/libstdc++.log.xz | Bin 429304 -> 431248 bytes sumfiles/libstdc++.sum | 10 +- 44 files changed, 5107 insertions(+), 3374 deletions(-) create mode 100644 13-check_regression/extra-bisect-params create mode 100644 13-check_regression/fails.sum create mode 100644 13-check_regression/results.regressions