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 9416a86be 107: onsuccess: #2139: 1: Success after binutils/gcc/gdb: 3 commits discards 5b8e0f9b7 106: onsuccess: #2138: 1: Success after binutils/gcc/glibc/gd [...] discards f34f00460 105: onsuccess: #2137: 1: Success after basepoints/gcc-13-271 [...] discards 3392a0c3f 104: onsuccess: #2136: 1: Success after binutils/gcc/gdb: 3 commits discards 7719e0c6c 103: onsuccess: #2135: 1: Success after gcc/linux/glibc/gdb/q [...] discards b1142c295 102: onsuccess: #2133: 1: Success after gdb-12-branchpoint-19 [...] discards ef74ada7a 101: onsuccess: #2130: 1: Success after binutils: 81 commits discards da1702944 100: onsuccess: #2077: 1: Success after binutils/gcc/linux/gd [...] discards 1e6a48a2e 99: onsuccess: #2074: 1: Success after baseline build: no new [...] discards 493d3ca5a 98: onsuccess: #2073: 1: Success after gcc/linux: 11 commits discards 5c78900df 97: onsuccess: #2072: 1: Success after binutils/gcc/gdb: 3 commits discards 03986490d 96: onsuccess: #2071: 1: Success after gcc/linux: 56 commits discards 6a92026f8 95: onsuccess: #2070: 1: Success after basepoints/gcc-13-2389 [...] discards 4d94f6300 94: onsuccess: 1: Success after gcc: openmp: Partial OpenMP 5 [...] discards 3594bbfeb 93: onsuccess: 1: Success after binutils/gcc/linux/gdb: 88 commits discards 373dab9f5 92: onsuccess: 1: Success after binutils/gcc/linux/gdb/qemu: [...] discards c68c53abf 91: onsuccess: 1: Success after binutils/gcc/gdb: 8 commits discards 0ddcd9a6c 90: onsuccess: 1: Success after binutils/gcc/gdb: 19 commits discards 366a1785f 89: onsuccess: 1: Success after binutils/gcc/gdb: 5 commits discards 4b2ade4bd 88: onsuccess: 1: Success after gcc/linux/qemu: 149 commits discards 4fd57f85a 87: onsuccess: 1: Success after binutils/gcc/gdb: 14 commits discards d733f889b 86: onsuccess: 1: Success after binutils/gcc/gdb: 7 commits discards 005f1677e 85: onsuccess: 1: Success after binutils/gcc/glibc/gdb/qemu: [...] discards 8146e8b44 84: onsuccess: 1: Success after binutils/gcc/linux/gdb: 68 commits discards b1ab5095c 83: onsuccess: 1: Success after binutils/gcc/glibc/gdb: 17 commits discards 26075481d 82: onsuccess: 1: Successful build after binutils/gcc/gdb: 11 [...] discards aa4d6b8f9 81: onsuccess: 1: Successful build after binutils/gcc/gdb: 6 commits discards bb9ae965c 80: onsuccess: 1: Successful build after binutils/gcc/glibc/g [...] discards a098db2d3 79: onsuccess: 1: Successful build after binutils/gcc/glibc/g [...] discards d29528eb9 78: onsuccess: 1: Successful build after binutils/gcc/gdb: 4 commits discards a6afd9bb5 77: onsuccess: 1: Successful build after gcc/linux/glibc: 22 commits discards 20643375b 76: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] discards 1ecf4f2b2 75: onsuccess: 1: Successful build after linux: 44 commits discards c0933daaf 74: onsuccess: 1: Successful build after binutils/gdb: 2 commits discards 4e3d61b94 73: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] discards b4c9ced72 72: onsuccess: 1: Successful build after linux: 12 commits discards 29c0d0fcc 71: onsuccess: 1: Successful build after gcc/glibc: 3 commits discards 6a4be8ca0 70: onsuccess: 1: Successful build after binutils/gcc/gdb: 4 commits discards ca767a80b 69: onsuccess: 1: Successful build after binutils/gcc/gdb: 5 commits discards de1523952 68: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] discards 87c5648e1 67: onsuccess: 1: Successful build after binutils/gcc/gdb: 10 [...] discards a68305050 66: onsuccess: 1: Successful build after gcc/glibc: 10 commits discards e549dfb0f 65: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] discards 7af305e92 64: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] discards 03601dadd 63: onsuccess: 1: Successful build after binutils/gcc/gdb: 8 commits discards d9f79836c 62: onsuccess: 1: Successful build after binutils/gcc/gdb: 22 [...] discards 9008bf7f2 61: onsuccess: 1: Successful build after binutils/gcc/gdb/qem [...] discards c06c83470 60: onsuccess: 1: Successful build after glibc: 2 commits discards 4b0d5fd3d 59: onsuccess: 1: Successful build after binutils: 2 commits discards 1e4c28d13 58: onsuccess: 1: Successful build after binutils: gdb: new ' [...] discards 2c7eb20b5 57: onsuccess: 1: Successful build after binutils/gcc/glibc/g [...] discards b78d9f1e1 56: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] discards b1456bd3e 55: onsuccess: 1: Successful build after gcc/linux/glibc/qemu [...] discards f65df45bf 54: onsuccess: 1: Successful build after binutils/gcc/gdb: 8 commits discards 4111b409d 53: onsuccess: 1: Successful build after binutils/gcc/gdb: 8 commits discards 14e72b375 52: onsuccess: 1: Successful build after binutils/gcc/gdb: 7 commits discards c24b46515 51: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] discards a34e5b90a 50: onsuccess: 1: Successful build after binutils/gcc/glibc/g [...] discards e4a23f26a 49: onsuccess: 1: Successful build after gcc/glibc: 5 commits discards ffb4da601 48: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] discards 9834cab65 47: onsuccess: 1: Successful build after linux: 10 commits discards 9d4f18caa 46: onsuccess: 1: Successful build after binutils/gdb: 2 commits discards 8a3976bec 45: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] discards 39f2831bb 44: onsuccess: 1: Successful build after gcc/linux: 35 commits discards b9b95ea1d 43: onsuccess: 1: Successful build after gcc: LoongArch: Add [...] discards 3e439555e 42: onsuccess: 1: Successful build after gcc: libcpp: Impleme [...] discards 5cdb9c856 41: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] discards 6b8b316fc 40: onsuccess: 1: Successful build after linux/qemu: 147 commits discards 51db3509c 39: onsuccess: 1: Successful build after binutils/gcc/gdb/qem [...] discards 7afa1eede 38: onsuccess: 1: Successful build after gcc/linux: 95 commits discards b92b7c487 37: onsuccess: 1: Successful build after binutils/gcc/glibc/g [...] discards 6ac3514a5 36: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] discards c62b4b2e6 35: onsuccess: 1: Successful build after binutils/gcc/glibc/g [...] discards 29d7df31d 34: onsuccess: 1: Successful build after binutils/gcc/glibc/g [...] discards ef2b87bd0 33: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] discards 58f355441 32: onsuccess: 1: Successful build after gcc: 7 commits discards c1959c3a4 31: onsuccess: 1: Successful build after binutils/gcc/glibc/g [...] discards 821030dcd 30: onsuccess: 1: Successful build after binutils/gcc/gdb/qem [...] discards acc3b54b4 29: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] discards 7ae8dc7a1 28: onsuccess: 1: Successful build after binutils/gcc/glibc/g [...] discards 4e5d05e4e 27: onsuccess: 1: Successful build after binutils/gcc/gdb: 25 [...] discards e4050fc5e 26: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards 433d1e422 25: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards 784278090 24: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards cd872822f 23: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards 1e1ab7709 22: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards dc3f087f0 21: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards efc23b5b5 20: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards 5144ee1ea 19: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards d0343751c 18: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards f98475877 17: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards 8e508fd46 16: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards eed29c4f5 15: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards 43f85b2f2 14: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards 1faeaabe2 13: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards 21dfb544b 12: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards 39934fa0b 11: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards 686e61210 10: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards 3741a81da 9: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards f05b28e3d 8: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards 624496d8c 7: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new 1739ddc82 7: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new b8056f648 8: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new f2a687b58 9: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new 07ede4c31 10: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new 89498ddbb 11: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new 91d4999f4 12: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new fbac8c5ef 13: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new 57b5e006a 14: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new 8ad523641 15: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new bc14256a3 16: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new 97e142c52 17: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new bf477cf43 18: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new b9cf0c240 19: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new c055f11d0 20: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new d963e055e 21: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new f6128d2c8 22: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new 1c677d453 23: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new da142e0bd 24: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new bb3643fe1 25: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new 15ba86c91 26: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new 4fbda78dc 27: onsuccess: 1: Successful build after binutils/gcc/gdb: 25 [...] new c8fdfbfea 28: onsuccess: 1: Successful build after binutils/gcc/glibc/g [...] new 3a720d98a 29: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] new 5ef6252ea 30: onsuccess: 1: Successful build after binutils/gcc/gdb/qem [...] new 9a1050e98 31: onsuccess: 1: Successful build after binutils/gcc/glibc/g [...] new add7d8bc5 32: onsuccess: 1: Successful build after gcc: 7 commits new f72898035 33: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] new 64a3a8149 34: onsuccess: 1: Successful build after binutils/gcc/glibc/g [...] new 4123e2f1f 35: onsuccess: 1: Successful build after binutils/gcc/glibc/g [...] new 2364f85fc 36: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] new 027aa1004 37: onsuccess: 1: Successful build after binutils/gcc/glibc/g [...] new c3e0b4380 38: onsuccess: 1: Successful build after gcc/linux: 95 commits new 1436a6727 39: onsuccess: 1: Successful build after binutils/gcc/gdb/qem [...] new 7f59ea9e0 40: onsuccess: 1: Successful build after linux/qemu: 147 commits new 2766b0a05 41: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] new 79b2214e3 42: onsuccess: 1: Successful build after gcc: libcpp: Impleme [...] new ecbb9f14b 43: onsuccess: 1: Successful build after gcc: LoongArch: Add [...] new 34855c146 44: onsuccess: 1: Successful build after gcc/linux: 35 commits new 8f08a258d 45: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] new 977ef268e 46: onsuccess: 1: Successful build after binutils/gdb: 2 commits new f45ded6a2 47: onsuccess: 1: Successful build after linux: 10 commits new 79d9b05f6 48: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] new 7a7713b89 49: onsuccess: 1: Successful build after gcc/glibc: 5 commits new 4dc5d7a4f 50: onsuccess: 1: Successful build after binutils/gcc/glibc/g [...] new d0e64122e 51: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] new 98fb4ed1d 52: onsuccess: 1: Successful build after binutils/gcc/gdb: 7 commits new 438a0dafa 53: onsuccess: 1: Successful build after binutils/gcc/gdb: 8 commits new cd723d1ca 54: onsuccess: 1: Successful build after binutils/gcc/gdb: 8 commits new 4749be071 55: onsuccess: 1: Successful build after gcc/linux/glibc/qemu [...] new aa1987291 56: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] new 3a8bc60dd 57: onsuccess: 1: Successful build after binutils/gcc/glibc/g [...] new 07379d41a 58: onsuccess: 1: Successful build after binutils: gdb: new ' [...] new 022326fe9 59: onsuccess: 1: Successful build after binutils: 2 commits new d330a43b0 60: onsuccess: 1: Successful build after glibc: 2 commits new 9d43c1877 61: onsuccess: 1: Successful build after binutils/gcc/gdb/qem [...] new 3bcc2f616 62: onsuccess: 1: Successful build after binutils/gcc/gdb: 22 [...] new 4275658a6 63: onsuccess: 1: Successful build after binutils/gcc/gdb: 8 commits new 20dca5d28 64: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] new d975e26d6 65: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] new 3b30df9e9 66: onsuccess: 1: Successful build after gcc/glibc: 10 commits new 527af5c0b 67: onsuccess: 1: Successful build after binutils/gcc/gdb: 10 [...] new 84af50aea 68: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] new 480259dfb 69: onsuccess: 1: Successful build after binutils/gcc/gdb: 5 commits new ae5f39b7d 70: onsuccess: 1: Successful build after binutils/gcc/gdb: 4 commits new 68a001adf 71: onsuccess: 1: Successful build after gcc/glibc: 3 commits new 11609a576 72: onsuccess: 1: Successful build after linux: 12 commits new c4ec19092 73: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] new 1d872369f 74: onsuccess: 1: Successful build after binutils/gdb: 2 commits new 653e95838 75: onsuccess: 1: Successful build after linux: 44 commits new 00663f320 76: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] new f65109eba 77: onsuccess: 1: Successful build after gcc/linux/glibc: 22 commits new 1a45628dd 78: onsuccess: 1: Successful build after binutils/gcc/gdb: 4 commits new 925d331e8 79: onsuccess: 1: Successful build after binutils/gcc/glibc/g [...] new 39c064baf 80: onsuccess: 1: Successful build after binutils/gcc/glibc/g [...] new f1bd832c1 81: onsuccess: 1: Successful build after binutils/gcc/gdb: 6 commits new b7b1d9e5e 82: onsuccess: 1: Successful build after binutils/gcc/gdb: 11 [...] new b4f66bf14 83: onsuccess: 1: Success after binutils/gcc/glibc/gdb: 17 commits new 91d834319 84: onsuccess: 1: Success after binutils/gcc/linux/gdb: 68 commits new a46b40400 85: onsuccess: 1: Success after binutils/gcc/glibc/gdb/qemu: [...] new 09677a4ee 86: onsuccess: 1: Success after binutils/gcc/gdb: 7 commits new 05c813ae2 87: onsuccess: 1: Success after binutils/gcc/gdb: 14 commits new 15611a6d6 88: onsuccess: 1: Success after gcc/linux/qemu: 149 commits new e9efa5a51 89: onsuccess: 1: Success after binutils/gcc/gdb: 5 commits new befd70f33 90: onsuccess: 1: Success after binutils/gcc/gdb: 19 commits new 935d676fb 91: onsuccess: 1: Success after binutils/gcc/gdb: 8 commits new 6bfd4f8e1 92: onsuccess: 1: Success after binutils/gcc/linux/gdb/qemu: [...] new d6deb98e7 93: onsuccess: 1: Success after binutils/gcc/linux/gdb: 88 commits new f631a890c 94: onsuccess: 1: Success after gcc: openmp: Partial OpenMP 5 [...] new 029e7e4ab 95: onsuccess: #2070: 1: Success after basepoints/gcc-13-2389 [...] new cc47eae7a 96: onsuccess: #2071: 1: Success after gcc/linux: 56 commits new f4bbe9fbe 97: onsuccess: #2072: 1: Success after binutils/gcc/gdb: 3 commits new 20dd824ca 98: onsuccess: #2073: 1: Success after gcc/linux: 11 commits new 0fd9d69cc 99: onsuccess: #2074: 1: Success after baseline build: no new [...] new 80cb40715 100: onsuccess: #2077: 1: Success after binutils/gcc/linux/gd [...] new 815068f08 101: onsuccess: #2130: 1: Success after binutils: 81 commits new e6efc1a07 102: onsuccess: #2133: 1: Success after gdb-12-branchpoint-19 [...] new cc08fe0b8 103: onsuccess: #2135: 1: Success after gcc/linux/glibc/gdb/q [...] new 6c83ac808 104: onsuccess: #2136: 1: Success after binutils/gcc/gdb: 3 commits new a8395a740 105: onsuccess: #2137: 1: Success after basepoints/gcc-13-271 [...] new 2346a15f6 106: onsuccess: #2138: 1: Success after binutils/gcc/glibc/gd [...] new cb58d21e9 107: onsuccess: #2139: 1: Success after binutils/gcc/gdb: 3 commits new 886c9ebd0 108: onsuccess: #2140: 1: Success after binutils/gcc/gdb: 5 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 (9416a86be) \ 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 1704 -> 1740 bytes 02-prepare_abe/console.log.xz | Bin 2736 -> 2740 bytes 03-build_abe-binutils/console.log.xz | Bin 30304 -> 30144 bytes 04-build_abe-stage1/console.log.xz | Bin 72232 -> 72308 bytes 06-build_abe-linux/console.log.xz | Bin 8332 -> 8260 bytes 07-build_abe-glibc/console.log.xz | Bin 240112 -> 240280 bytes 08-build_abe-stage2/console.log.xz | Bin 203184 -> 202856 bytes 09-build_abe-gdb/console.log.xz | Bin 37436 -> 37328 bytes 10-build_abe-qemu/console.log.xz | Bin 31564 -> 31844 bytes 11-build_abe-dejagnu/console.log.xz | Bin 3880 -> 3876 bytes 12-build_abe-check_gcc/console.log.xz | Bin 2660 -> 2580 bytes 13-check_regression/console.log.xz | Bin 18840 -> 18312 bytes 13-check_regression/extra-bisect-params | 1 - 13-check_regression/fails.sum | 552 --- 13-check_regression/mail-body.txt | 93 +- 13-check_regression/results.compare | 25 +- 13-check_regression/results.compare2 | 2429 +++++----- 13-check_regression/results.regressions | 101 - 14-update_baseline/console.log | 60 +- dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- git/gdb_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 95 +- mail/mail-subject.txt | 2 +- manifest.sh | 32 +- results | 101 - sumfiles/g++.log.xz | Bin 3396056 -> 3396064 bytes sumfiles/g++.sum | 49 +- sumfiles/gcc.log.xz | Bin 2984812 -> 3019024 bytes sumfiles/gcc.sum | 7656 +++++++++++++++++-------------- sumfiles/gfortran.log.xz | Bin 1027268 -> 1024948 bytes sumfiles/gfortran.sum | 4 +- sumfiles/libatomic.log.xz | Bin 2292 -> 2292 bytes sumfiles/libatomic.sum | 2 +- sumfiles/libgomp.log.xz | Bin 202228 -> 202216 bytes sumfiles/libgomp.sum | 2 +- sumfiles/libitm.log.xz | Bin 2656 -> 2660 bytes sumfiles/libitm.sum | 2 +- sumfiles/libstdc++.log.xz | Bin 426180 -> 422776 bytes sumfiles/libstdc++.sum | 8 +- 42 files changed, 5446 insertions(+), 5778 deletions(-) delete mode 100644 13-check_regression/extra-bisect-params delete mode 100644 13-check_regression/fails.sum delete mode 100644 13-check_regression/results.regressions