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 10d1816627 141: onsuccess: #2176: 1: Success after binutils/gcc/gdb: 6 commits discards 11da134dd0 140: onsuccess: #2175: 1: Success after binutils/gcc/linux/g [...] discards 2e54f72a69 139: onsuccess: #2174: 1: Success after binutils/gcc/gdb: 13 [...] discards 17ccc7b3dc 138: onsuccess: #2173: 1: Success after binutils/gcc/gdb: 5 commits discards a2f21db290 137: onsuccess: #2172: 1: Success after binutils/gcc/linux/g [...] discards 7e86d3dbf0 136: onsuccess: #2171: 1: Success after binutils/gcc/gdb/qem [...] discards 67d81f7394 135: onsuccess: #2170: 1: Success after gcc/linux/qemu: 63 commits discards 307475a6cb 134: onsuccess: #2169: 1: Success after binutils/gcc/gdb: 13 [...] discards 7478abb5ec 133: onsuccess: #2168: 1: Success after binutils/gcc/linux/g [...] discards 4832b9f0e7 132: onsuccess: #2167: 1: Success after binutils/gcc/glibc/g [...] discards d47a8cb388 131: onsuccess: #2166: 1: Success after binutils/gcc/gdb: 12 [...] discards 15d3b375f5 130: onsuccess: #2165: 1: Success after binutils/gcc/gdb: 32 [...] discards ed4be7e2f8 129: onsuccess: #2164: 1: Success after binutils/gcc/linux/g [...] discards 2098c90a09 128: onsuccess: #2163: 1: Success after linux: 23 commits discards e3b8a3ff39 127: onsuccess: #2162: 1: Success after gcc: 9 commits discards 7211a661a1 126: onsuccess: #2161: 1: Success after basepoints/gcc-13-28 [...] discards 31ac2d584a 125: onsuccess: #2160: 1: Success after binutils/gcc/linux/g [...] discards e0171c1113 124: onsuccess: #2159: 1: Success after linux: 23 commits discards 3b42233454 123: onsuccess: #2158: 1: Success after basepoints/gcc-13-28 [...] discards 5784221756 122: onsuccess: #2157: 1: Success after binutils/gcc/gdb: 6 commits discards 23ee3af466 121: onsuccess: #2156: 1: Success after binutils/gcc/linux/g [...] discards 6849480045 120: onsuccess: #2155: 1: Success after binutils/gcc/linux/g [...] discards a8c4f499ae 119: onsuccess: #2154: 1: Success after binutils/gcc/linux/g [...] discards b677870f8c 118: onsuccess: #2151: 1: Success after binutils/gcc/linux/g [...] discards 704e6cf58f 117: onsuccess: #2150: 1: Success after binutils/gcc/glibc/g [...] discards 054927852c 116: onsuccess: #2148: 1: Success after binutils/gcc/gdb: 7 commits discards 1fd0ab8298 115: onsuccess: #2147: 1: Success after binutils/linux/glibc [...] discards 0b064598b2 114: onsuccess: #2146: 1: Success after binutils/gcc/glibc/g [...] discards 8ed571f30b 113: onsuccess: #2145: 1: Success after binutils/gcc/glibc/g [...] discards edeeecdac8 112: onsuccess: #2144: 1: Success after binutils/gcc/glibc/g [...] discards 9701187827 111: onsuccess: #2143: 1: Success after binutils/gcc/linux/g [...] discards f722ec8a3c 110: onsuccess: #2142: 1: Success after binutils/gcc/glibc/g [...] discards 8b506db7e7 109: onsuccess: #2141: 1: Success after gcc/glibc: 6 commits discards 6b7dadc842 108: onsuccess: #2140: 1: Success after binutils/gcc/gdb: 5 commits discards 1467f7f69c 107: onsuccess: #2139: 1: Success after binutils/gcc/gdb: 3 commits discards a1176844f0 106: onsuccess: #2138: 1: Success after binutils/gcc/glibc/g [...] discards f1cfe38791 105: onsuccess: #2137: 1: Success after basepoints/gcc-13-27 [...] discards ef378a55ce 104: onsuccess: #2136: 1: Success after binutils/gcc/gdb: 3 commits discards ed1d09cdf1 103: onsuccess: #2135: 1: Success after gcc/linux/glibc/gdb/ [...] discards 141f727347 102: onsuccess: #2133: 1: Success after gdb-12-branchpoint-1 [...] discards df331d3b08 101: onsuccess: #2130: 1: Success after binutils: 81 commits discards b32549dd2e 100: onsuccess: #2077: 1: Success after binutils/gcc/linux/g [...] discards 3f2deb50b2 99: onsuccess: #2074: 1: Success after baseline build: no ne [...] discards 078a5f6d28 98: onsuccess: #2073: 1: Success after gcc/linux: 11 commits discards fca3856a80 97: onsuccess: #2072: 1: Success after binutils/gcc/gdb: 3 commits discards 36b1e24bf9 96: onsuccess: #2071: 1: Success after gcc/linux: 56 commits discards bf15ca1202 95: onsuccess: #2070: 1: Success after basepoints/gcc-13-238 [...] discards cc8d276911 94: onsuccess: 1: Success after gcc: openmp: Partial OpenMP [...] discards f2ee325ccf 93: onsuccess: 1: Success after binutils/gcc/linux/gdb: 88 commits discards 66f87caf4a 92: onsuccess: 1: Success after binutils/gcc/linux/gdb/qemu: [...] discards 76e69a80cd 91: onsuccess: 1: Success after binutils/gcc/gdb: 8 commits discards cc87a1acd4 90: onsuccess: 1: Success after binutils/gcc/gdb: 19 commits discards 31c0be90b3 89: onsuccess: 1: Success after binutils/gcc/gdb: 5 commits discards ede016ed43 88: onsuccess: 1: Success after gcc/linux/qemu: 149 commits discards 3e07639222 87: onsuccess: 1: Success after binutils/gcc/gdb: 14 commits discards 210a239a63 86: onsuccess: 1: Success after binutils/gcc/gdb: 7 commits discards 801faa2123 85: onsuccess: 1: Success after binutils/gcc/glibc/gdb/qemu: [...] discards 4738742b2f 84: onsuccess: 1: Success after binutils/gcc/linux/gdb: 68 commits discards 0f2552c4b5 83: onsuccess: 1: Success after binutils/gcc/glibc/gdb: 17 commits discards 3d54447f71 82: onsuccess: 1: Successful build after binutils/gcc/gdb: 1 [...] discards bc0eb001f6 81: onsuccess: 1: Successful build after binutils/gcc/gdb: 6 [...] discards 4e8aa1faaa 80: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] discards e04fee8247 79: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] discards 51ffadaa3f 78: onsuccess: 1: Successful build after binutils/gcc/gdb: 4 [...] discards 146f426708 77: onsuccess: 1: Successful build after gcc/linux/glibc: 22 [...] discards cfe5d3cef6 76: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards c3816fe2ce 75: onsuccess: 1: Successful build after linux: 44 commits discards 16ce320760 74: onsuccess: 1: Successful build after binutils/gdb: 2 commits discards 1706192c3e 73: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 3fa226fffb 72: onsuccess: 1: Successful build after linux: 12 commits discards 4710148579 71: onsuccess: 1: Successful build after gcc/glibc: 3 commits discards b0aa1895b1 70: onsuccess: 1: Successful build after binutils/gcc/gdb: 4 [...] discards 1432166b35 69: onsuccess: 1: Successful build after binutils/gcc/gdb: 5 [...] discards f75bb89acc 68: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 10f70c3ff7 67: onsuccess: 1: Successful build after binutils/gcc/gdb: 1 [...] discards 3b493e8a8c 66: onsuccess: 1: Successful build after gcc/glibc: 10 commits discards 24dd4c9489 65: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 33a218cdc4 64: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 8a23a3c045 63: onsuccess: 1: Successful build after binutils/gcc/gdb: 8 [...] discards 4903446c15 62: onsuccess: 1: Successful build after binutils/gcc/gdb: 2 [...] discards 75e51acb66 61: onsuccess: 1: Successful build after binutils/gcc/gdb/qe [...] discards b40262ff7b 60: onsuccess: 1: Successful build after glibc: 2 commits discards b5e9fddb2a 59: onsuccess: 1: Successful build after binutils: 2 commits discards c345d91720 58: onsuccess: 1: Successful build after binutils: gdb: new [...] discards 17fe9d2c9f 57: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] discards de844407a2 56: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 2b00d9a9f9 55: onsuccess: 1: Successful build after gcc/linux/glibc/qem [...] discards 2c000c4bcf 54: onsuccess: 1: Successful build after binutils/gcc/gdb: 8 [...] discards 9ed32bc9a0 53: onsuccess: 1: Successful build after binutils/gcc/gdb: 8 [...] discards c54588ad85 52: onsuccess: 1: Successful build after binutils/gcc/gdb: 7 [...] discards 02e393cc1e 51: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards cf4acf9bab 50: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] discards a03befecb3 49: onsuccess: 1: Successful build after gcc/glibc: 5 commits discards 8d300b6f15 48: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 3f6c2c991a 47: onsuccess: 1: Successful build after linux: 10 commits discards 7e04321469 46: onsuccess: 1: Successful build after binutils/gdb: 2 commits discards 64becad8be 45: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 6f0f5a21d0 44: onsuccess: 1: Successful build after gcc/linux: 35 commits discards e512667d39 43: onsuccess: 1: Successful build after gcc: LoongArch: Add [...] discards 7b76e5991b 42: onsuccess: 1: Successful build after gcc: libcpp: Implem [...] discards a167d8c1f8 41: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new b064de26b3 41: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new b5cd59862c 42: onsuccess: 1: Successful build after gcc: libcpp: Implem [...] new 0a431ca1dd 43: onsuccess: 1: Successful build after gcc: LoongArch: Add [...] new 8261438c0a 44: onsuccess: 1: Successful build after gcc/linux: 35 commits new a57542f186 45: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 29fa249e2d 46: onsuccess: 1: Successful build after binutils/gdb: 2 commits new b461d47beb 47: onsuccess: 1: Successful build after linux: 10 commits new 820ce7c279 48: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new ac77be0d40 49: onsuccess: 1: Successful build after gcc/glibc: 5 commits new 19b9b4e3bc 50: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] new a11525b0b6 51: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new b6b516fefe 52: onsuccess: 1: Successful build after binutils/gcc/gdb: 7 [...] new 8473b11d85 53: onsuccess: 1: Successful build after binutils/gcc/gdb: 8 [...] new 80a5e10ed8 54: onsuccess: 1: Successful build after binutils/gcc/gdb: 8 [...] new e0ca61a40d 55: onsuccess: 1: Successful build after gcc/linux/glibc/qem [...] new 549fd99005 56: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new dd01bbf5ba 57: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] new 9dd34eb721 58: onsuccess: 1: Successful build after binutils: gdb: new [...] new d3fee574a1 59: onsuccess: 1: Successful build after binutils: 2 commits new 11a8745103 60: onsuccess: 1: Successful build after glibc: 2 commits new 9a8d644aa6 61: onsuccess: 1: Successful build after binutils/gcc/gdb/qe [...] new 4f698996d5 62: onsuccess: 1: Successful build after binutils/gcc/gdb: 2 [...] new 413a6668ec 63: onsuccess: 1: Successful build after binutils/gcc/gdb: 8 [...] new 1a8bdec5d0 64: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 05884f1409 65: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 0ef6c90f2e 66: onsuccess: 1: Successful build after gcc/glibc: 10 commits new b3ef27fbb9 67: onsuccess: 1: Successful build after binutils/gcc/gdb: 1 [...] new 6df35b5c8b 68: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 43061e04d3 69: onsuccess: 1: Successful build after binutils/gcc/gdb: 5 [...] new 520997a4ab 70: onsuccess: 1: Successful build after binutils/gcc/gdb: 4 [...] new 08c73d493e 71: onsuccess: 1: Successful build after gcc/glibc: 3 commits new 1aafb05c0e 72: onsuccess: 1: Successful build after linux: 12 commits new 8b35518804 73: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 615ea1fa4a 74: onsuccess: 1: Successful build after binutils/gdb: 2 commits new 27a1d6ce31 75: onsuccess: 1: Successful build after linux: 44 commits new 7ca312b261 76: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 96b8e88b5b 77: onsuccess: 1: Successful build after gcc/linux/glibc: 22 [...] new 19bc8f956d 78: onsuccess: 1: Successful build after binutils/gcc/gdb: 4 [...] new 236a897d35 79: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] new c6ea422775 80: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] new 4f414b0c48 81: onsuccess: 1: Successful build after binutils/gcc/gdb: 6 [...] new e9cc93bbb9 82: onsuccess: 1: Successful build after binutils/gcc/gdb: 1 [...] new 760082891f 83: onsuccess: 1: Success after binutils/gcc/glibc/gdb: 17 commits new b196f32102 84: onsuccess: 1: Success after binutils/gcc/linux/gdb: 68 commits new 3c93aa4062 85: onsuccess: 1: Success after binutils/gcc/glibc/gdb/qemu: [...] new 94b50b4f0b 86: onsuccess: 1: Success after binutils/gcc/gdb: 7 commits new ca0ae02b29 87: onsuccess: 1: Success after binutils/gcc/gdb: 14 commits new 819b82d191 88: onsuccess: 1: Success after gcc/linux/qemu: 149 commits new 3462c82861 89: onsuccess: 1: Success after binutils/gcc/gdb: 5 commits new 068add0064 90: onsuccess: 1: Success after binutils/gcc/gdb: 19 commits new 7949e76a3c 91: onsuccess: 1: Success after binutils/gcc/gdb: 8 commits new dd206cfdef 92: onsuccess: 1: Success after binutils/gcc/linux/gdb/qemu: [...] new fed515a485 93: onsuccess: 1: Success after binutils/gcc/linux/gdb: 88 commits new db65bda313 94: onsuccess: 1: Success after gcc: openmp: Partial OpenMP [...] new aba6821d6a 95: onsuccess: #2070: 1: Success after basepoints/gcc-13-238 [...] new 1496d35907 96: onsuccess: #2071: 1: Success after gcc/linux: 56 commits new 4417a91f6f 97: onsuccess: #2072: 1: Success after binutils/gcc/gdb: 3 commits new e971a43e96 98: onsuccess: #2073: 1: Success after gcc/linux: 11 commits new a201202d17 99: onsuccess: #2074: 1: Success after baseline build: no ne [...] new ce39e6bb0e 100: onsuccess: #2077: 1: Success after binutils/gcc/linux/g [...] new 91bd13d6c7 101: onsuccess: #2130: 1: Success after binutils: 81 commits new 390e1ae644 102: onsuccess: #2133: 1: Success after gdb-12-branchpoint-1 [...] new 0635b3bc05 103: onsuccess: #2135: 1: Success after gcc/linux/glibc/gdb/ [...] new bfb13c1d0d 104: onsuccess: #2136: 1: Success after binutils/gcc/gdb: 3 commits new a3a588dd4e 105: onsuccess: #2137: 1: Success after basepoints/gcc-13-27 [...] new fbf398dcb9 106: onsuccess: #2138: 1: Success after binutils/gcc/glibc/g [...] new 2e5fcf8cd5 107: onsuccess: #2139: 1: Success after binutils/gcc/gdb: 3 commits new 172b3c1a70 108: onsuccess: #2140: 1: Success after binutils/gcc/gdb: 5 commits new ff234d6d00 109: onsuccess: #2141: 1: Success after gcc/glibc: 6 commits new 80e0578881 110: onsuccess: #2142: 1: Success after binutils/gcc/glibc/g [...] new 4b0f5dc98d 111: onsuccess: #2143: 1: Success after binutils/gcc/linux/g [...] new ba8186cee2 112: onsuccess: #2144: 1: Success after binutils/gcc/glibc/g [...] new a33e44ae70 113: onsuccess: #2145: 1: Success after binutils/gcc/glibc/g [...] new 4db62fae35 114: onsuccess: #2146: 1: Success after binutils/gcc/glibc/g [...] new 0d3af21973 115: onsuccess: #2147: 1: Success after binutils/linux/glibc [...] new 46264c099d 116: onsuccess: #2148: 1: Success after binutils/gcc/gdb: 7 commits new 364f6f8a63 117: onsuccess: #2150: 1: Success after binutils/gcc/glibc/g [...] new f8a7b074fa 118: onsuccess: #2151: 1: Success after binutils/gcc/linux/g [...] new 213d27fb8d 119: onsuccess: #2154: 1: Success after binutils/gcc/linux/g [...] new 3e5c9093bb 120: onsuccess: #2155: 1: Success after binutils/gcc/linux/g [...] new 6f227221a6 121: onsuccess: #2156: 1: Success after binutils/gcc/linux/g [...] new 9e4288984d 122: onsuccess: #2157: 1: Success after binutils/gcc/gdb: 6 commits new f6920a1454 123: onsuccess: #2158: 1: Success after basepoints/gcc-13-28 [...] new c85006db9e 124: onsuccess: #2159: 1: Success after linux: 23 commits new a46d41df12 125: onsuccess: #2160: 1: Success after binutils/gcc/linux/g [...] new aefd63be58 126: onsuccess: #2161: 1: Success after basepoints/gcc-13-28 [...] new b8d04cfbcd 127: onsuccess: #2162: 1: Success after gcc: 9 commits new b1ae24d315 128: onsuccess: #2163: 1: Success after linux: 23 commits new a57ecc5ffb 129: onsuccess: #2164: 1: Success after binutils/gcc/linux/g [...] new f620b0aaf7 130: onsuccess: #2165: 1: Success after binutils/gcc/gdb: 32 [...] new 107c55658e 131: onsuccess: #2166: 1: Success after binutils/gcc/gdb: 12 [...] new 9b5fb6074b 132: onsuccess: #2167: 1: Success after binutils/gcc/glibc/g [...] new da2b820046 133: onsuccess: #2168: 1: Success after binutils/gcc/linux/g [...] new ef242e106a 134: onsuccess: #2169: 1: Success after binutils/gcc/gdb: 13 [...] new 858ba6a5b1 135: onsuccess: #2170: 1: Success after gcc/linux/qemu: 63 commits new 1dbadf452e 136: onsuccess: #2171: 1: Success after binutils/gcc/gdb/qem [...] new e7328bea59 137: onsuccess: #2172: 1: Success after binutils/gcc/linux/g [...] new e37b518cc2 138: onsuccess: #2173: 1: Success after binutils/gcc/gdb: 5 commits new 69828f0afd 139: onsuccess: #2174: 1: Success after binutils/gcc/gdb: 13 [...] new 19bdbbc8ef 140: onsuccess: #2175: 1: Success after binutils/gcc/linux/g [...] new 5991096b94 141: onsuccess: #2176: 1: Success after binutils/gcc/gdb: 6 commits new c3e3423c2c 142: onsuccess: #2177: 1: Success after gcc/glibc: 4 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 (10d1816627) \ 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 1696 -> 1712 bytes 02-prepare_abe/console.log.xz | Bin 2748 -> 2748 bytes 03-build_abe-binutils/console.log.xz | Bin 30228 -> 30224 bytes 04-build_abe-stage1/console.log.xz | Bin 72388 -> 72588 bytes 05-clean_sysroot/console.log.xz | Bin 328 -> 328 bytes 06-build_abe-linux/console.log.xz | Bin 8728 -> 8716 bytes 07-build_abe-glibc/console.log.xz | Bin 240676 -> 239724 bytes 08-build_abe-stage2/console.log.xz | Bin 202640 -> 203176 bytes 09-build_abe-gdb/console.log.xz | Bin 37460 -> 37372 bytes 10-build_abe-qemu/console.log.xz | Bin 31180 -> 31140 bytes 11-build_abe-dejagnu/console.log.xz | Bin 3880 -> 3896 bytes 12-build_abe-check_gcc/console.log.xz | Bin 2460 -> 2916 bytes 13-check_regression/console.log.xz | Bin 5872 -> 5844 bytes 13-check_regression/results.compare | 30 +- 13-check_regression/results.compare2 | 80 +- 14-update_baseline/console.log | 40 +- dashboard/dashboard-generate.sh | 2 +- git/gcc_rev | 2 +- git/glibc_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 2 +- mail/mail-subject.txt | 2 +- manifest.sh | 28 +- sumfiles/g++.log.xz | Bin 3410432 -> 3415560 bytes sumfiles/g++.sum | 211 +- sumfiles/gcc.log.xz | Bin 3035140 -> 3017972 bytes sumfiles/gcc.sum | 4953 ++++++++++++++++----------------- sumfiles/gfortran.log.xz | Bin 1028168 -> 1033552 bytes sumfiles/gfortran.sum | 42 +- sumfiles/libatomic.log.xz | Bin 2288 -> 2300 bytes sumfiles/libatomic.sum | 4 +- sumfiles/libgomp.log.xz | Bin 202040 -> 201968 bytes sumfiles/libgomp.sum | 16 +- sumfiles/libitm.log.xz | Bin 2660 -> 2656 bytes sumfiles/libitm.sum | 6 +- sumfiles/libstdc++.log.xz | Bin 421128 -> 429304 bytes sumfiles/libstdc++.sum | 10 +- 37 files changed, 2707 insertions(+), 2725 deletions(-)