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 b1e8a5d76c 135: onsuccess: #2170: 1: Success after gcc/linux/qemu: 63 commits discards 32663604b2 134: onsuccess: #2169: 1: Success after binutils/gcc/gdb: 13 [...] discards 46544bb0ce 133: onsuccess: #2168: 1: Success after binutils/gcc/linux/g [...] discards 69a498846e 132: onsuccess: #2167: 1: Success after binutils/gcc/glibc/g [...] discards e8cd546055 131: onsuccess: #2166: 1: Success after binutils/gcc/gdb: 12 [...] discards 8a629c6dd3 130: onsuccess: #2165: 1: Success after binutils/gcc/gdb: 32 [...] discards 69108c2a55 129: onsuccess: #2164: 1: Success after binutils/gcc/linux/g [...] discards f5b3ddfaea 128: onsuccess: #2163: 1: Success after linux: 23 commits discards e1e16769f0 127: onsuccess: #2162: 1: Success after gcc: 9 commits discards f394af14b0 126: onsuccess: #2161: 1: Success after basepoints/gcc-13-28 [...] discards ebe8e4cbb0 125: onsuccess: #2160: 1: Success after binutils/gcc/linux/g [...] discards cebeecc8f3 124: onsuccess: #2159: 1: Success after linux: 23 commits discards edcef5a3db 123: onsuccess: #2158: 1: Success after basepoints/gcc-13-28 [...] discards 55a4323a3c 122: onsuccess: #2157: 1: Success after binutils/gcc/gdb: 6 commits discards 78cf9c35e1 121: onsuccess: #2156: 1: Success after binutils/gcc/linux/g [...] discards 1171de5bda 120: onsuccess: #2155: 1: Success after binutils/gcc/linux/g [...] discards 0c8b07941f 119: onsuccess: #2154: 1: Success after binutils/gcc/linux/g [...] discards 5f08c0177b 118: onsuccess: #2151: 1: Success after binutils/gcc/linux/g [...] discards 31a3fa309d 117: onsuccess: #2150: 1: Success after binutils/gcc/glibc/g [...] discards 7f26a6e141 116: onsuccess: #2148: 1: Success after binutils/gcc/gdb: 7 commits discards 438fdbcae6 115: onsuccess: #2147: 1: Success after binutils/linux/glibc [...] discards 6b18f78d55 114: onsuccess: #2146: 1: Success after binutils/gcc/glibc/g [...] discards 77a2b99ef5 113: onsuccess: #2145: 1: Success after binutils/gcc/glibc/g [...] discards 3cc5b185ad 112: onsuccess: #2144: 1: Success after binutils/gcc/glibc/g [...] discards 277662ecce 111: onsuccess: #2143: 1: Success after binutils/gcc/linux/g [...] discards 8470f58c4a 110: onsuccess: #2142: 1: Success after binutils/gcc/glibc/g [...] discards 19537d16ca 109: onsuccess: #2141: 1: Success after gcc/glibc: 6 commits discards f5f141a16e 108: onsuccess: #2140: 1: Success after binutils/gcc/gdb: 5 commits discards 04f8911da4 107: onsuccess: #2139: 1: Success after binutils/gcc/gdb: 3 commits discards 146e114d40 106: onsuccess: #2138: 1: Success after binutils/gcc/glibc/g [...] discards 3b0d55ec82 105: onsuccess: #2137: 1: Success after basepoints/gcc-13-27 [...] discards 252f85a428 104: onsuccess: #2136: 1: Success after binutils/gcc/gdb: 3 commits discards cab4e97f1a 103: onsuccess: #2135: 1: Success after gcc/linux/glibc/gdb/ [...] discards 370482dada 102: onsuccess: #2133: 1: Success after gdb-12-branchpoint-1 [...] discards 23ed3cf174 101: onsuccess: #2130: 1: Success after binutils: 81 commits discards ecc9092120 100: onsuccess: #2077: 1: Success after binutils/gcc/linux/g [...] discards 7e49b68f49 99: onsuccess: #2074: 1: Success after baseline build: no ne [...] discards 07b48016ff 98: onsuccess: #2073: 1: Success after gcc/linux: 11 commits discards 4988df60ca 97: onsuccess: #2072: 1: Success after binutils/gcc/gdb: 3 commits discards e8e7ef384a 96: onsuccess: #2071: 1: Success after gcc/linux: 56 commits discards d9cc374471 95: onsuccess: #2070: 1: Success after basepoints/gcc-13-238 [...] discards a7dc8a36f3 94: onsuccess: 1: Success after gcc: openmp: Partial OpenMP [...] discards 1d385cf3e4 93: onsuccess: 1: Success after binutils/gcc/linux/gdb: 88 commits discards 12c5ac38a1 92: onsuccess: 1: Success after binutils/gcc/linux/gdb/qemu: [...] discards a3a218fe97 91: onsuccess: 1: Success after binutils/gcc/gdb: 8 commits discards f0034ed5cb 90: onsuccess: 1: Success after binutils/gcc/gdb: 19 commits discards 6c9905168b 89: onsuccess: 1: Success after binutils/gcc/gdb: 5 commits discards 30e0c293f1 88: onsuccess: 1: Success after gcc/linux/qemu: 149 commits discards f8723e08d5 87: onsuccess: 1: Success after binutils/gcc/gdb: 14 commits discards 8b3de6190b 86: onsuccess: 1: Success after binutils/gcc/gdb: 7 commits discards 265b4ec44b 85: onsuccess: 1: Success after binutils/gcc/glibc/gdb/qemu: [...] discards aae0bcafb7 84: onsuccess: 1: Success after binutils/gcc/linux/gdb: 68 commits discards 0c81ca466d 83: onsuccess: 1: Success after binutils/gcc/glibc/gdb: 17 commits discards ea8600d38b 82: onsuccess: 1: Successful build after binutils/gcc/gdb: 1 [...] discards 55fd3e0e27 81: onsuccess: 1: Successful build after binutils/gcc/gdb: 6 [...] discards 50bc3259fc 80: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] discards 164b190361 79: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] discards e39a1408c7 78: onsuccess: 1: Successful build after binutils/gcc/gdb: 4 [...] discards 52f694c1f7 77: onsuccess: 1: Successful build after gcc/linux/glibc: 22 [...] discards 92d6f99d46 76: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards dedc400435 75: onsuccess: 1: Successful build after linux: 44 commits discards 9cf51b8668 74: onsuccess: 1: Successful build after binutils/gdb: 2 commits discards 2f4467ee09 73: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards cd2d989825 72: onsuccess: 1: Successful build after linux: 12 commits discards 9c3cbf7fe3 71: onsuccess: 1: Successful build after gcc/glibc: 3 commits discards df79224cc8 70: onsuccess: 1: Successful build after binutils/gcc/gdb: 4 [...] discards a59c34903e 69: onsuccess: 1: Successful build after binutils/gcc/gdb: 5 [...] discards 5c9e07c939 68: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards a78609f97e 67: onsuccess: 1: Successful build after binutils/gcc/gdb: 1 [...] discards 62fe75d5ae 66: onsuccess: 1: Successful build after gcc/glibc: 10 commits discards 29ec59f0a5 65: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 6ffc54e8eb 64: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards f87e04aca3 63: onsuccess: 1: Successful build after binutils/gcc/gdb: 8 [...] discards 37b2127902 62: onsuccess: 1: Successful build after binutils/gcc/gdb: 2 [...] discards 65b6862b03 61: onsuccess: 1: Successful build after binutils/gcc/gdb/qe [...] discards d47de6aea2 60: onsuccess: 1: Successful build after glibc: 2 commits discards 0b1c104818 59: onsuccess: 1: Successful build after binutils: 2 commits discards bb228ee27b 58: onsuccess: 1: Successful build after binutils: gdb: new [...] discards 96455411e4 57: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] discards 5c37101179 56: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 9a4cbc10ab 55: onsuccess: 1: Successful build after gcc/linux/glibc/qem [...] discards 3c6128200c 54: onsuccess: 1: Successful build after binutils/gcc/gdb: 8 [...] discards ae94e33fa2 53: onsuccess: 1: Successful build after binutils/gcc/gdb: 8 [...] discards ba1a814f6d 52: onsuccess: 1: Successful build after binutils/gcc/gdb: 7 [...] discards cd3fceed3d 51: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 42de33aef4 50: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] discards 401715a4e7 49: onsuccess: 1: Successful build after gcc/glibc: 5 commits discards e46127cf7c 48: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 6f31c5a58f 47: onsuccess: 1: Successful build after linux: 10 commits discards d25a8e6d14 46: onsuccess: 1: Successful build after binutils/gdb: 2 commits discards fa114899a1 45: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 896a759318 44: onsuccess: 1: Successful build after gcc/linux: 35 commits discards d43e2f5239 43: onsuccess: 1: Successful build after gcc: LoongArch: Add [...] discards 3208bf70a5 42: onsuccess: 1: Successful build after gcc: libcpp: Implem [...] discards fb45e071c7 41: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 8050fccc30 40: onsuccess: 1: Successful build after linux/qemu: 147 commits discards 1e643e6c22 39: onsuccess: 1: Successful build after binutils/gcc/gdb/qe [...] discards 59c541490c 38: onsuccess: 1: Successful build after gcc/linux: 95 commits discards 2cb57013db 37: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] discards b2adbd9149 36: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards a15e011f19 35: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] new 085207c6bb 35: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] new 360dc629de 36: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 61163f5fbc 37: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] new 7eb3ed195f 38: onsuccess: 1: Successful build after gcc/linux: 95 commits new e8d5e597e6 39: onsuccess: 1: Successful build after binutils/gcc/gdb/qe [...] new 3efe71a581 40: onsuccess: 1: Successful build after linux/qemu: 147 commits new e1b8dafe35 41: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new e0ca7ea642 42: onsuccess: 1: Successful build after gcc: libcpp: Implem [...] new fd9487b6a5 43: onsuccess: 1: Successful build after gcc: LoongArch: Add [...] new 5d91dffb26 44: onsuccess: 1: Successful build after gcc/linux: 35 commits new 4ea96c58ea 45: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 78505351b2 46: onsuccess: 1: Successful build after binutils/gdb: 2 commits new c67a1505b4 47: onsuccess: 1: Successful build after linux: 10 commits new a1c54c3027 48: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 37dd956bcb 49: onsuccess: 1: Successful build after gcc/glibc: 5 commits new 1698216bff 50: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] new 28917aefd5 51: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new c8ff032367 52: onsuccess: 1: Successful build after binutils/gcc/gdb: 7 [...] new ff88439f3d 53: onsuccess: 1: Successful build after binutils/gcc/gdb: 8 [...] new 1ba4bdb4de 54: onsuccess: 1: Successful build after binutils/gcc/gdb: 8 [...] new e4cce4407a 55: onsuccess: 1: Successful build after gcc/linux/glibc/qem [...] new 1bad3543fe 56: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new af71982b06 57: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] new a352478c19 58: onsuccess: 1: Successful build after binutils: gdb: new [...] new a08d5a3410 59: onsuccess: 1: Successful build after binutils: 2 commits new 6f9fdae999 60: onsuccess: 1: Successful build after glibc: 2 commits new 3b4e7cb816 61: onsuccess: 1: Successful build after binutils/gcc/gdb/qe [...] new 2323668a7a 62: onsuccess: 1: Successful build after binutils/gcc/gdb: 2 [...] new 7ab5a32133 63: onsuccess: 1: Successful build after binutils/gcc/gdb: 8 [...] new dc4a60c45a 64: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 72c434a7c7 65: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 2124b8a34c 66: onsuccess: 1: Successful build after gcc/glibc: 10 commits new 5b3f891c66 67: onsuccess: 1: Successful build after binutils/gcc/gdb: 1 [...] new edf1568939 68: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 7437d13e98 69: onsuccess: 1: Successful build after binutils/gcc/gdb: 5 [...] new 544f2dd42b 70: onsuccess: 1: Successful build after binutils/gcc/gdb: 4 [...] new d7a0eef58a 71: onsuccess: 1: Successful build after gcc/glibc: 3 commits new fac779b736 72: onsuccess: 1: Successful build after linux: 12 commits new 9a1fa3a474 73: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 1089286317 74: onsuccess: 1: Successful build after binutils/gdb: 2 commits new 7918aa952c 75: onsuccess: 1: Successful build after linux: 44 commits new 348cc62231 76: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new af6bc4187a 77: onsuccess: 1: Successful build after gcc/linux/glibc: 22 [...] new f7d5302c38 78: onsuccess: 1: Successful build after binutils/gcc/gdb: 4 [...] new 16b63c9612 79: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] new 181bb00769 80: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] new 14a4aea679 81: onsuccess: 1: Successful build after binutils/gcc/gdb: 6 [...] new 6929afa859 82: onsuccess: 1: Successful build after binutils/gcc/gdb: 1 [...] new 8a5abc7bb2 83: onsuccess: 1: Success after binutils/gcc/glibc/gdb: 17 commits new 132fcaf7bf 84: onsuccess: 1: Success after binutils/gcc/linux/gdb: 68 commits new 095aaa3120 85: onsuccess: 1: Success after binutils/gcc/glibc/gdb/qemu: [...] new fe06b51432 86: onsuccess: 1: Success after binutils/gcc/gdb: 7 commits new 861b1557f0 87: onsuccess: 1: Success after binutils/gcc/gdb: 14 commits new 89ba3bc252 88: onsuccess: 1: Success after gcc/linux/qemu: 149 commits new 7a50c29e17 89: onsuccess: 1: Success after binutils/gcc/gdb: 5 commits new 4f765e7320 90: onsuccess: 1: Success after binutils/gcc/gdb: 19 commits new f04e9ad027 91: onsuccess: 1: Success after binutils/gcc/gdb: 8 commits new a2b03adc22 92: onsuccess: 1: Success after binutils/gcc/linux/gdb/qemu: [...] new b23728a5ec 93: onsuccess: 1: Success after binutils/gcc/linux/gdb: 88 commits new d77cc9e653 94: onsuccess: 1: Success after gcc: openmp: Partial OpenMP [...] new 811e731bed 95: onsuccess: #2070: 1: Success after basepoints/gcc-13-238 [...] new a044f01739 96: onsuccess: #2071: 1: Success after gcc/linux: 56 commits new c306e01759 97: onsuccess: #2072: 1: Success after binutils/gcc/gdb: 3 commits new 856f822255 98: onsuccess: #2073: 1: Success after gcc/linux: 11 commits new fe0b812c6c 99: onsuccess: #2074: 1: Success after baseline build: no ne [...] new be223602e1 100: onsuccess: #2077: 1: Success after binutils/gcc/linux/g [...] new 62e166ec2f 101: onsuccess: #2130: 1: Success after binutils: 81 commits new c8dc08ffb2 102: onsuccess: #2133: 1: Success after gdb-12-branchpoint-1 [...] new 5f2b8c6f4d 103: onsuccess: #2135: 1: Success after gcc/linux/glibc/gdb/ [...] new e574656042 104: onsuccess: #2136: 1: Success after binutils/gcc/gdb: 3 commits new 4cd4574444 105: onsuccess: #2137: 1: Success after basepoints/gcc-13-27 [...] new a8b5a096ce 106: onsuccess: #2138: 1: Success after binutils/gcc/glibc/g [...] new 48131d5b71 107: onsuccess: #2139: 1: Success after binutils/gcc/gdb: 3 commits new 17597255fa 108: onsuccess: #2140: 1: Success after binutils/gcc/gdb: 5 commits new 0ceb9392aa 109: onsuccess: #2141: 1: Success after gcc/glibc: 6 commits new 7c70835d1b 110: onsuccess: #2142: 1: Success after binutils/gcc/glibc/g [...] new df6ec97f7e 111: onsuccess: #2143: 1: Success after binutils/gcc/linux/g [...] new bf2f166684 112: onsuccess: #2144: 1: Success after binutils/gcc/glibc/g [...] new d5fa55596c 113: onsuccess: #2145: 1: Success after binutils/gcc/glibc/g [...] new b9fa0b5aa7 114: onsuccess: #2146: 1: Success after binutils/gcc/glibc/g [...] new e34343872a 115: onsuccess: #2147: 1: Success after binutils/linux/glibc [...] new d3ada16de5 116: onsuccess: #2148: 1: Success after binutils/gcc/gdb: 7 commits new 724b863077 117: onsuccess: #2150: 1: Success after binutils/gcc/glibc/g [...] new 1c7a14beaf 118: onsuccess: #2151: 1: Success after binutils/gcc/linux/g [...] new 8dd0b6f83d 119: onsuccess: #2154: 1: Success after binutils/gcc/linux/g [...] new 0188e2b155 120: onsuccess: #2155: 1: Success after binutils/gcc/linux/g [...] new d6ddff5fd8 121: onsuccess: #2156: 1: Success after binutils/gcc/linux/g [...] new e841245aa5 122: onsuccess: #2157: 1: Success after binutils/gcc/gdb: 6 commits new d2c1352c17 123: onsuccess: #2158: 1: Success after basepoints/gcc-13-28 [...] new 8df7ee5828 124: onsuccess: #2159: 1: Success after linux: 23 commits new dd8ea9eaa5 125: onsuccess: #2160: 1: Success after binutils/gcc/linux/g [...] new b1a551287e 126: onsuccess: #2161: 1: Success after basepoints/gcc-13-28 [...] new d68a5e4ae7 127: onsuccess: #2162: 1: Success after gcc: 9 commits new 608f1e86b8 128: onsuccess: #2163: 1: Success after linux: 23 commits new cee5f9f500 129: onsuccess: #2164: 1: Success after binutils/gcc/linux/g [...] new 37862fc0be 130: onsuccess: #2165: 1: Success after binutils/gcc/gdb: 32 [...] new b1d8afa74d 131: onsuccess: #2166: 1: Success after binutils/gcc/gdb: 12 [...] new 8838883943 132: onsuccess: #2167: 1: Success after binutils/gcc/glibc/g [...] new 38f8e1bcf5 133: onsuccess: #2168: 1: Success after binutils/gcc/linux/g [...] new 01fb2b1d63 134: onsuccess: #2169: 1: Success after binutils/gcc/gdb: 13 [...] new 5e4136c6f8 135: onsuccess: #2170: 1: Success after gcc/linux/qemu: 63 commits new 60d0ea4eb3 136: onsuccess: #2171: 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 (b1e8a5d76c) \ 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 1760 -> 1720 bytes 02-prepare_abe/console.log.xz | Bin 2740 -> 2764 bytes 03-build_abe-binutils/console.log.xz | Bin 30420 -> 30472 bytes 04-build_abe-stage1/console.log.xz | Bin 72380 -> 72832 bytes 05-clean_sysroot/console.log.xz | Bin 328 -> 328 bytes 06-build_abe-linux/console.log.xz | Bin 8600 -> 8632 bytes 07-build_abe-glibc/console.log.xz | Bin 239708 -> 240280 bytes 08-build_abe-stage2/console.log.xz | Bin 203172 -> 203276 bytes 09-build_abe-gdb/console.log.xz | Bin 37556 -> 37800 bytes 10-build_abe-qemu/console.log.xz | Bin 32088 -> 31300 bytes 11-build_abe-dejagnu/console.log.xz | Bin 3924 -> 3880 bytes 12-build_abe-check_gcc/console.log.xz | Bin 2772 -> 2660 bytes 13-check_regression/console.log.xz | Bin 82088 -> 72748 bytes 13-check_regression/extra-bisect-params | 2 +- 13-check_regression/fails.sum | 148 +- 13-check_regression/mail-body.txt | 222 +- 13-check_regression/results.compare | 75 +- 13-check_regression/results.compare2 | 20333 +++++++++++++----------------- 13-check_regression/results.regressions | 46 +- 14-update_baseline/console.log | 70 +- 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 | 224 +- mail/mail-subject.txt | 2 +- manifest.sh | 40 +- results | 46 +- sumfiles/g++.log.xz | Bin 3420708 -> 3420960 bytes sumfiles/g++.sum | 165 +- sumfiles/gcc.log.xz | Bin 2935208 -> 3031424 bytes sumfiles/gcc.sum | 19512 +++++++++++++++------------- sumfiles/gfortran.log.xz | Bin 1028564 -> 1035640 bytes sumfiles/gfortran.sum | 45 +- sumfiles/libatomic.log.xz | Bin 2296 -> 2292 bytes sumfiles/libatomic.sum | 4 +- sumfiles/libgomp.log.xz | Bin 202376 -> 202548 bytes sumfiles/libgomp.sum | 16 +- sumfiles/libitm.log.xz | Bin 2656 -> 2656 bytes sumfiles/libitm.sum | 6 +- sumfiles/libstdc++.log.xz | Bin 421572 -> 420032 bytes sumfiles/libstdc++.sum | 16 +- 44 files changed, 20409 insertions(+), 20575 deletions(-)