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 019da947cc 134: onsuccess: #2169: 1: Success after binutils/gcc/gdb: 13 [...] discards 5c831adb46 133: onsuccess: #2168: 1: Success after binutils/gcc/linux/g [...] discards 198c48d635 132: onsuccess: #2167: 1: Success after binutils/gcc/glibc/g [...] discards 04a6883dd0 131: onsuccess: #2166: 1: Success after binutils/gcc/gdb: 12 [...] discards ed2477e07a 130: onsuccess: #2165: 1: Success after binutils/gcc/gdb: 32 [...] discards 812a4b96a4 129: onsuccess: #2164: 1: Success after binutils/gcc/linux/g [...] discards 11b6a4584c 128: onsuccess: #2163: 1: Success after linux: 23 commits discards 371c78a31f 127: onsuccess: #2162: 1: Success after gcc: 9 commits discards c473861967 126: onsuccess: #2161: 1: Success after basepoints/gcc-13-28 [...] discards f37f7721bd 125: onsuccess: #2160: 1: Success after binutils/gcc/linux/g [...] discards 3a8255b3bb 124: onsuccess: #2159: 1: Success after linux: 23 commits discards 4415410e5e 123: onsuccess: #2158: 1: Success after basepoints/gcc-13-28 [...] discards cb72e199c4 122: onsuccess: #2157: 1: Success after binutils/gcc/gdb: 6 commits discards 916c1becf5 121: onsuccess: #2156: 1: Success after binutils/gcc/linux/g [...] discards 2a5074b672 120: onsuccess: #2155: 1: Success after binutils/gcc/linux/g [...] discards e838430bf3 119: onsuccess: #2154: 1: Success after binutils/gcc/linux/g [...] discards 4a1e5d876f 118: onsuccess: #2151: 1: Success after binutils/gcc/linux/g [...] discards 48e8883396 117: onsuccess: #2150: 1: Success after binutils/gcc/glibc/g [...] discards 10c54e26b0 116: onsuccess: #2148: 1: Success after binutils/gcc/gdb: 7 commits discards 7e7185c300 115: onsuccess: #2147: 1: Success after binutils/linux/glibc [...] discards 592f3e1d42 114: onsuccess: #2146: 1: Success after binutils/gcc/glibc/g [...] discards 0da0e72176 113: onsuccess: #2145: 1: Success after binutils/gcc/glibc/g [...] discards 67a6660781 112: onsuccess: #2144: 1: Success after binutils/gcc/glibc/g [...] discards ae974a19a0 111: onsuccess: #2143: 1: Success after binutils/gcc/linux/g [...] discards daba6ed6cd 110: onsuccess: #2142: 1: Success after binutils/gcc/glibc/g [...] discards 27800a0a32 109: onsuccess: #2141: 1: Success after gcc/glibc: 6 commits discards eb0552d498 108: onsuccess: #2140: 1: Success after binutils/gcc/gdb: 5 commits discards b75c47bf41 107: onsuccess: #2139: 1: Success after binutils/gcc/gdb: 3 commits discards 776fb4a356 106: onsuccess: #2138: 1: Success after binutils/gcc/glibc/g [...] discards 366639db6a 105: onsuccess: #2137: 1: Success after basepoints/gcc-13-27 [...] discards 597e95cf33 104: onsuccess: #2136: 1: Success after binutils/gcc/gdb: 3 commits discards 91b11bc85a 103: onsuccess: #2135: 1: Success after gcc/linux/glibc/gdb/ [...] discards 4c63188ec7 102: onsuccess: #2133: 1: Success after gdb-12-branchpoint-1 [...] discards 49b50c244a 101: onsuccess: #2130: 1: Success after binutils: 81 commits discards fa5ef5d5c7 100: onsuccess: #2077: 1: Success after binutils/gcc/linux/g [...] discards f0f622032b 99: onsuccess: #2074: 1: Success after baseline build: no ne [...] discards 1c24652da8 98: onsuccess: #2073: 1: Success after gcc/linux: 11 commits discards 96276ac2dd 97: onsuccess: #2072: 1: Success after binutils/gcc/gdb: 3 commits discards 92cd5e0383 96: onsuccess: #2071: 1: Success after gcc/linux: 56 commits discards 52d93b6b63 95: onsuccess: #2070: 1: Success after basepoints/gcc-13-238 [...] discards 2e18269fde 94: onsuccess: 1: Success after gcc: openmp: Partial OpenMP [...] discards 40659591fa 93: onsuccess: 1: Success after binutils/gcc/linux/gdb: 88 commits discards 05fd6b79e7 92: onsuccess: 1: Success after binutils/gcc/linux/gdb/qemu: [...] discards 2b10facb9e 91: onsuccess: 1: Success after binutils/gcc/gdb: 8 commits discards 518c69e1ff 90: onsuccess: 1: Success after binutils/gcc/gdb: 19 commits discards e4889a7ed9 89: onsuccess: 1: Success after binutils/gcc/gdb: 5 commits discards 6e82955d0e 88: onsuccess: 1: Success after gcc/linux/qemu: 149 commits discards 67c8658c2a 87: onsuccess: 1: Success after binutils/gcc/gdb: 14 commits discards 7e9b76103c 86: onsuccess: 1: Success after binutils/gcc/gdb: 7 commits discards 53ee23727c 85: onsuccess: 1: Success after binutils/gcc/glibc/gdb/qemu: [...] discards 3df00a3067 84: onsuccess: 1: Success after binutils/gcc/linux/gdb: 68 commits discards a47c5f900b 83: onsuccess: 1: Success after binutils/gcc/glibc/gdb: 17 commits discards 39f9768473 82: onsuccess: 1: Successful build after binutils/gcc/gdb: 1 [...] discards 0c5be61cba 81: onsuccess: 1: Successful build after binutils/gcc/gdb: 6 [...] discards 5b7e25504b 80: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] discards b177199811 79: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] discards fe0b921d91 78: onsuccess: 1: Successful build after binutils/gcc/gdb: 4 [...] discards c7fe8b58bd 77: onsuccess: 1: Successful build after gcc/linux/glibc: 22 [...] discards 8e9c7f198c 76: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards c418f082e6 75: onsuccess: 1: Successful build after linux: 44 commits discards da2a9275e3 74: onsuccess: 1: Successful build after binutils/gdb: 2 commits discards b3d2031113 73: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 4be6fb3c3e 72: onsuccess: 1: Successful build after linux: 12 commits discards d62b893fee 71: onsuccess: 1: Successful build after gcc/glibc: 3 commits discards 1c85ca56ff 70: onsuccess: 1: Successful build after binutils/gcc/gdb: 4 [...] discards c27916147e 69: onsuccess: 1: Successful build after binutils/gcc/gdb: 5 [...] discards 677225498f 68: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 2400f04a7a 67: onsuccess: 1: Successful build after binutils/gcc/gdb: 1 [...] discards f33a1983c8 66: onsuccess: 1: Successful build after gcc/glibc: 10 commits discards 0b3de7eaaf 65: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 249ac207ca 64: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 78443c280e 63: onsuccess: 1: Successful build after binutils/gcc/gdb: 8 [...] discards 15563a043a 62: onsuccess: 1: Successful build after binutils/gcc/gdb: 2 [...] discards 04a3aa54c5 61: onsuccess: 1: Successful build after binutils/gcc/gdb/qe [...] discards 27f5278a0c 60: onsuccess: 1: Successful build after glibc: 2 commits discards 767186a22c 59: onsuccess: 1: Successful build after binutils: 2 commits discards 6cbda4b08c 58: onsuccess: 1: Successful build after binutils: gdb: new [...] discards b271b4949d 57: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] discards 134a43d14b 56: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 7fbc2b1d6a 55: onsuccess: 1: Successful build after gcc/linux/glibc/qem [...] discards 43cc36fffe 54: onsuccess: 1: Successful build after binutils/gcc/gdb: 8 [...] discards 05cec26b25 53: onsuccess: 1: Successful build after binutils/gcc/gdb: 8 [...] discards 93bbc470ed 52: onsuccess: 1: Successful build after binutils/gcc/gdb: 7 [...] discards 00e1a2b1b6 51: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 27717ef7a5 50: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] discards fbbcabfc07 49: onsuccess: 1: Successful build after gcc/glibc: 5 commits discards 29f0320d82 48: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards a9637a3355 47: onsuccess: 1: Successful build after linux: 10 commits discards b5763085fd 46: onsuccess: 1: Successful build after binutils/gdb: 2 commits discards 0f8abda8d8 45: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards aa490c7e66 44: onsuccess: 1: Successful build after gcc/linux: 35 commits discards 4278737ffe 43: onsuccess: 1: Successful build after gcc: LoongArch: Add [...] discards 659bb839bd 42: onsuccess: 1: Successful build after gcc: libcpp: Implem [...] discards 870970feb8 41: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards f4eee7398d 40: onsuccess: 1: Successful build after linux/qemu: 147 commits discards e080a425b2 39: onsuccess: 1: Successful build after binutils/gcc/gdb/qe [...] discards 5f054b0677 38: onsuccess: 1: Successful build after gcc/linux: 95 commits discards 008a14bf3d 37: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] discards 955c72c24f 36: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards c8d839f856 35: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] discards 331f9d98fb 34: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] new b44d324d19 34: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] new a15e011f19 35: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] new b2adbd9149 36: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 2cb57013db 37: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] new 59c541490c 38: onsuccess: 1: Successful build after gcc/linux: 95 commits new 1e643e6c22 39: onsuccess: 1: Successful build after binutils/gcc/gdb/qe [...] new 8050fccc30 40: onsuccess: 1: Successful build after linux/qemu: 147 commits new fb45e071c7 41: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 3208bf70a5 42: onsuccess: 1: Successful build after gcc: libcpp: Implem [...] new d43e2f5239 43: onsuccess: 1: Successful build after gcc: LoongArch: Add [...] new 896a759318 44: onsuccess: 1: Successful build after gcc/linux: 35 commits new fa114899a1 45: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new d25a8e6d14 46: onsuccess: 1: Successful build after binutils/gdb: 2 commits new 6f31c5a58f 47: onsuccess: 1: Successful build after linux: 10 commits new e46127cf7c 48: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 401715a4e7 49: onsuccess: 1: Successful build after gcc/glibc: 5 commits new 42de33aef4 50: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] new cd3fceed3d 51: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new ba1a814f6d 52: onsuccess: 1: Successful build after binutils/gcc/gdb: 7 [...] new ae94e33fa2 53: onsuccess: 1: Successful build after binutils/gcc/gdb: 8 [...] new 3c6128200c 54: onsuccess: 1: Successful build after binutils/gcc/gdb: 8 [...] new 9a4cbc10ab 55: onsuccess: 1: Successful build after gcc/linux/glibc/qem [...] new 5c37101179 56: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 96455411e4 57: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] new bb228ee27b 58: onsuccess: 1: Successful build after binutils: gdb: new [...] new 0b1c104818 59: onsuccess: 1: Successful build after binutils: 2 commits new d47de6aea2 60: onsuccess: 1: Successful build after glibc: 2 commits new 65b6862b03 61: onsuccess: 1: Successful build after binutils/gcc/gdb/qe [...] new 37b2127902 62: onsuccess: 1: Successful build after binutils/gcc/gdb: 2 [...] new f87e04aca3 63: onsuccess: 1: Successful build after binutils/gcc/gdb: 8 [...] new 6ffc54e8eb 64: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 29ec59f0a5 65: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 62fe75d5ae 66: onsuccess: 1: Successful build after gcc/glibc: 10 commits new a78609f97e 67: onsuccess: 1: Successful build after binutils/gcc/gdb: 1 [...] new 5c9e07c939 68: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new a59c34903e 69: onsuccess: 1: Successful build after binutils/gcc/gdb: 5 [...] new df79224cc8 70: onsuccess: 1: Successful build after binutils/gcc/gdb: 4 [...] new 9c3cbf7fe3 71: onsuccess: 1: Successful build after gcc/glibc: 3 commits new cd2d989825 72: onsuccess: 1: Successful build after linux: 12 commits new 2f4467ee09 73: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 9cf51b8668 74: onsuccess: 1: Successful build after binutils/gdb: 2 commits new dedc400435 75: onsuccess: 1: Successful build after linux: 44 commits new 92d6f99d46 76: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 52f694c1f7 77: onsuccess: 1: Successful build after gcc/linux/glibc: 22 [...] new e39a1408c7 78: onsuccess: 1: Successful build after binutils/gcc/gdb: 4 [...] new 164b190361 79: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] new 50bc3259fc 80: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] new 55fd3e0e27 81: onsuccess: 1: Successful build after binutils/gcc/gdb: 6 [...] new ea8600d38b 82: onsuccess: 1: Successful build after binutils/gcc/gdb: 1 [...] new 0c81ca466d 83: onsuccess: 1: Success after binutils/gcc/glibc/gdb: 17 commits new aae0bcafb7 84: onsuccess: 1: Success after binutils/gcc/linux/gdb: 68 commits new 265b4ec44b 85: onsuccess: 1: Success after binutils/gcc/glibc/gdb/qemu: [...] new 8b3de6190b 86: onsuccess: 1: Success after binutils/gcc/gdb: 7 commits new f8723e08d5 87: onsuccess: 1: Success after binutils/gcc/gdb: 14 commits new 30e0c293f1 88: onsuccess: 1: Success after gcc/linux/qemu: 149 commits new 6c9905168b 89: onsuccess: 1: Success after binutils/gcc/gdb: 5 commits new f0034ed5cb 90: onsuccess: 1: Success after binutils/gcc/gdb: 19 commits new a3a218fe97 91: onsuccess: 1: Success after binutils/gcc/gdb: 8 commits new 12c5ac38a1 92: onsuccess: 1: Success after binutils/gcc/linux/gdb/qemu: [...] new 1d385cf3e4 93: onsuccess: 1: Success after binutils/gcc/linux/gdb: 88 commits new a7dc8a36f3 94: onsuccess: 1: Success after gcc: openmp: Partial OpenMP [...] new d9cc374471 95: onsuccess: #2070: 1: Success after basepoints/gcc-13-238 [...] new e8e7ef384a 96: onsuccess: #2071: 1: Success after gcc/linux: 56 commits new 4988df60ca 97: onsuccess: #2072: 1: Success after binutils/gcc/gdb: 3 commits new 07b48016ff 98: onsuccess: #2073: 1: Success after gcc/linux: 11 commits new 7e49b68f49 99: onsuccess: #2074: 1: Success after baseline build: no ne [...] new ecc9092120 100: onsuccess: #2077: 1: Success after binutils/gcc/linux/g [...] new 23ed3cf174 101: onsuccess: #2130: 1: Success after binutils: 81 commits new 370482dada 102: onsuccess: #2133: 1: Success after gdb-12-branchpoint-1 [...] new cab4e97f1a 103: onsuccess: #2135: 1: Success after gcc/linux/glibc/gdb/ [...] new 252f85a428 104: onsuccess: #2136: 1: Success after binutils/gcc/gdb: 3 commits new 3b0d55ec82 105: onsuccess: #2137: 1: Success after basepoints/gcc-13-27 [...] new 146e114d40 106: onsuccess: #2138: 1: Success after binutils/gcc/glibc/g [...] new 04f8911da4 107: onsuccess: #2139: 1: Success after binutils/gcc/gdb: 3 commits new f5f141a16e 108: onsuccess: #2140: 1: Success after binutils/gcc/gdb: 5 commits new 19537d16ca 109: onsuccess: #2141: 1: Success after gcc/glibc: 6 commits new 8470f58c4a 110: onsuccess: #2142: 1: Success after binutils/gcc/glibc/g [...] new 277662ecce 111: onsuccess: #2143: 1: Success after binutils/gcc/linux/g [...] new 3cc5b185ad 112: onsuccess: #2144: 1: Success after binutils/gcc/glibc/g [...] new 77a2b99ef5 113: onsuccess: #2145: 1: Success after binutils/gcc/glibc/g [...] new 6b18f78d55 114: onsuccess: #2146: 1: Success after binutils/gcc/glibc/g [...] new 438fdbcae6 115: onsuccess: #2147: 1: Success after binutils/linux/glibc [...] new 7f26a6e141 116: onsuccess: #2148: 1: Success after binutils/gcc/gdb: 7 commits new 31a3fa309d 117: onsuccess: #2150: 1: Success after binutils/gcc/glibc/g [...] new 5f08c0177b 118: onsuccess: #2151: 1: Success after binutils/gcc/linux/g [...] new 0c8b07941f 119: onsuccess: #2154: 1: Success after binutils/gcc/linux/g [...] new 1171de5bda 120: onsuccess: #2155: 1: Success after binutils/gcc/linux/g [...] new 78cf9c35e1 121: onsuccess: #2156: 1: Success after binutils/gcc/linux/g [...] new 55a4323a3c 122: onsuccess: #2157: 1: Success after binutils/gcc/gdb: 6 commits new edcef5a3db 123: onsuccess: #2158: 1: Success after basepoints/gcc-13-28 [...] new cebeecc8f3 124: onsuccess: #2159: 1: Success after linux: 23 commits new ebe8e4cbb0 125: onsuccess: #2160: 1: Success after binutils/gcc/linux/g [...] new f394af14b0 126: onsuccess: #2161: 1: Success after basepoints/gcc-13-28 [...] new e1e16769f0 127: onsuccess: #2162: 1: Success after gcc: 9 commits new f5b3ddfaea 128: onsuccess: #2163: 1: Success after linux: 23 commits new 69108c2a55 129: onsuccess: #2164: 1: Success after binutils/gcc/linux/g [...] new 8a629c6dd3 130: onsuccess: #2165: 1: Success after binutils/gcc/gdb: 32 [...] new e8cd546055 131: onsuccess: #2166: 1: Success after binutils/gcc/gdb: 12 [...] new 69a498846e 132: onsuccess: #2167: 1: Success after binutils/gcc/glibc/g [...] new 46544bb0ce 133: onsuccess: #2168: 1: Success after binutils/gcc/linux/g [...] new 32663604b2 134: onsuccess: #2169: 1: Success after binutils/gcc/gdb: 13 [...] new b1e8a5d76c 135: onsuccess: #2170: 1: Success after gcc/linux/qemu: 63 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 (019da947cc) \ 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 1724 -> 1760 bytes 02-prepare_abe/console.log.xz | Bin 2728 -> 2740 bytes 03-build_abe-binutils/console.log.xz | Bin 30560 -> 30420 bytes 04-build_abe-stage1/console.log.xz | Bin 72556 -> 72380 bytes 05-clean_sysroot/console.log.xz | Bin 328 -> 328 bytes 06-build_abe-linux/console.log.xz | Bin 8768 -> 8600 bytes 07-build_abe-glibc/console.log.xz | Bin 239632 -> 239708 bytes 08-build_abe-stage2/console.log.xz | Bin 203016 -> 203172 bytes 09-build_abe-gdb/console.log.xz | Bin 37708 -> 37556 bytes 10-build_abe-qemu/console.log.xz | Bin 32420 -> 32088 bytes 11-build_abe-dejagnu/console.log.xz | Bin 3884 -> 3924 bytes 12-build_abe-check_gcc/console.log.xz | Bin 2712 -> 2772 bytes 13-check_regression/console.log.xz | Bin 19316 -> 82088 bytes 13-check_regression/extra-bisect-params | 2 +- 13-check_regression/fails.sum | 302 +- 13-check_regression/mail-body.txt | 205 +- 13-check_regression/results.compare | 497 +- 13-check_regression/results.compare2 | 18977 ++++++++++++++++++++++++---- 13-check_regression/results.regressions | 174 +- 14-update_baseline/console.log | 70 +- dashboard/dashboard-generate.sh | 2 +- git/gcc_rev | 2 +- git/linux_rev | 2 +- git/qemu_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 207 +- mail/mail-subject.txt | 2 +- manifest.sh | 34 +- results | 174 +- sumfiles/g++.log.xz | Bin 3416060 -> 3420708 bytes sumfiles/g++.sum | 2590 ++-- sumfiles/gcc.log.xz | Bin 3030340 -> 2935208 bytes sumfiles/gcc.sum | 20178 +++++++++++++----------------- sumfiles/gfortran.log.xz | Bin 1031928 -> 1028564 bytes sumfiles/gfortran.sum | 40 +- sumfiles/libatomic.log.xz | Bin 2300 -> 2296 bytes sumfiles/libatomic.sum | 4 +- sumfiles/libgomp.log.xz | Bin 201904 -> 202376 bytes sumfiles/libgomp.sum | 16 +- sumfiles/libitm.log.xz | Bin 2660 -> 2656 bytes sumfiles/libitm.sum | 6 +- sumfiles/libstdc++.log.xz | Bin 423916 -> 421572 bytes sumfiles/libstdc++.sum | 134 +- 43 files changed, 27882 insertions(+), 15740 deletions(-)