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 45020f34d0 104: onsuccess: #2136: 1: Success after binutils/gcc/gdb: 3 commits discards 99014c7e0c 103: onsuccess: #2135: 1: Success after gcc/linux/glibc/gdb/ [...] discards c7f970b7c7 102: onsuccess: #2133: 1: Success after gdb-12-branchpoint-1 [...] discards 568605654c 101: onsuccess: #2130: 1: Success after binutils: 81 commits discards 18926d292f 100: onsuccess: #2077: 1: Success after binutils/gcc/linux/g [...] discards ed6873a4f8 99: onsuccess: #2074: 1: Success after baseline build: no ne [...] discards 4c8356fad6 98: onsuccess: #2073: 1: Success after gcc/linux: 11 commits discards 437618c9b8 97: onsuccess: #2072: 1: Success after binutils/gcc/gdb: 3 commits discards 852edd0c83 96: onsuccess: #2071: 1: Success after gcc/linux: 56 commits discards 745dd9acfc 95: onsuccess: #2070: 1: Success after basepoints/gcc-13-238 [...] discards b1d2f643fd 94: onsuccess: 1: Success after gcc: openmp: Partial OpenMP [...] discards 0c2e4aa1a8 93: onsuccess: 1: Success after binutils/gcc/linux/gdb: 88 commits discards e307765eae 92: onsuccess: 1: Success after binutils/gcc/linux/gdb/qemu: [...] discards 299fc2bffc 91: onsuccess: 1: Success after binutils/gcc/gdb: 8 commits discards 4635aa2b0a 90: onsuccess: 1: Success after binutils/gcc/gdb: 19 commits discards 45f2cc8f17 89: onsuccess: 1: Success after binutils/gcc/gdb: 5 commits discards c396730a6e 88: onsuccess: 1: Success after gcc/linux/qemu: 149 commits discards c458837b25 87: onsuccess: 1: Success after binutils/gcc/gdb: 14 commits discards e04eb61a89 86: onsuccess: 1: Success after binutils/gcc/gdb: 7 commits discards 8d6defd5ab 85: onsuccess: 1: Success after binutils/gcc/glibc/gdb/qemu: [...] discards e7312a59e6 84: onsuccess: 1: Success after binutils/gcc/linux/gdb: 68 commits discards 4f7eb7ff34 83: onsuccess: 1: Success after binutils/gcc/glibc/gdb: 17 commits discards ac520b8c2d 82: onsuccess: 1: Successful build after binutils/gcc/gdb: 1 [...] discards 6225578963 81: onsuccess: 1: Successful build after binutils/gcc/gdb: 6 [...] discards 7fa7a207cc 80: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] discards 0c37730747 79: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] discards 6eb7fc6a35 78: onsuccess: 1: Successful build after binutils/gcc/gdb: 4 [...] discards 0bc0588e82 77: onsuccess: 1: Successful build after gcc/linux/glibc: 22 [...] discards d2b3aa78e5 76: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards eb32b86bd5 75: onsuccess: 1: Successful build after linux: 44 commits discards 0e05460e55 74: onsuccess: 1: Successful build after binutils/gdb: 2 commits discards 3208ac0ef2 73: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 5f4aeecd5e 72: onsuccess: 1: Successful build after linux: 12 commits discards 0fc0b2da5e 71: onsuccess: 1: Successful build after gcc/glibc: 3 commits discards a55f3ec615 70: onsuccess: 1: Successful build after binutils/gcc/gdb: 4 [...] discards c9731fe4b9 69: onsuccess: 1: Successful build after binutils/gcc/gdb: 5 [...] discards 7b992426fe 68: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards d956fd0831 67: onsuccess: 1: Successful build after binutils/gcc/gdb: 1 [...] discards 6430c03fc5 66: onsuccess: 1: Successful build after gcc/glibc: 10 commits discards e018518dbe 65: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards c0ace55024 64: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards e4881a00bb 63: onsuccess: 1: Successful build after binutils/gcc/gdb: 8 [...] discards 32221aeb0d 62: onsuccess: 1: Successful build after binutils/gcc/gdb: 2 [...] discards f86495a552 61: onsuccess: 1: Successful build after binutils/gcc/gdb/qe [...] discards bf9aa60dae 60: onsuccess: 1: Successful build after glibc: 2 commits discards 10d7aac36f 59: onsuccess: 1: Successful build after binutils: 2 commits discards f7b839d818 58: onsuccess: 1: Successful build after binutils: gdb: new [...] discards 3f42e8ff3a 57: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] discards d6db006c44 56: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards d5c46b1088 55: onsuccess: 1: Successful build after gcc/linux/glibc/qem [...] discards 5b6dc2bfd1 54: onsuccess: 1: Successful build after binutils/gcc/gdb: 8 [...] discards 91db0876a1 53: onsuccess: 1: Successful build after binutils/gcc/gdb: 8 [...] discards 10a055d9fa 52: onsuccess: 1: Successful build after binutils/gcc/gdb: 7 [...] discards 690ba621c7 51: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards a9b3a9178e 50: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] discards 574106f368 49: onsuccess: 1: Successful build after gcc/glibc: 5 commits discards 85ecc4b47d 48: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards a4c7d7203b 47: onsuccess: 1: Successful build after linux: 10 commits discards fde66caa19 46: onsuccess: 1: Successful build after binutils/gdb: 2 commits discards ae6124db37 45: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 875e5092bc 44: onsuccess: 1: Successful build after gcc/linux: 35 commits discards 14fb7966da 43: onsuccess: 1: Successful build after gcc: LoongArch: Add [...] discards 6a16f012d8 42: onsuccess: 1: Successful build after gcc: libcpp: Implem [...] discards cea48ee304 41: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 93938e2582 40: onsuccess: 1: Successful build after linux/qemu: 147 commits discards 7e853c0ac2 39: onsuccess: 1: Successful build after binutils/gcc/gdb/qe [...] discards 1047f41699 38: onsuccess: 1: Successful build after gcc/linux: 95 commits discards 527338c674 37: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] discards a6c7516ecb 36: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 020b4997c4 35: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] discards 73fd346cfc 34: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] discards cc1ecba6d7 33: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 458780e136 32: onsuccess: 1: Successful build after gcc: 7 commits discards 691f4220a8 31: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] discards 934a77c510 30: onsuccess: 1: Successful build after binutils/gcc/gdb/qe [...] discards 806380c91e 29: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 052f5163e2 28: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] discards fd209840ed 27: onsuccess: 1: Successful build after binutils/gcc/gdb: 2 [...] discards 50c59327a1 26: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards e4f2bf8d42 25: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards ecf20ed80b 24: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards a04050b6f2 23: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards 34dd89cc0d 22: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards 4ba8eadb10 21: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards 0e328036f1 20: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards 3e3eeed126 19: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards 1f577d4cea 18: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards 5ef25e911f 17: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards 922abae4a2 16: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards fabe8a83ac 15: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards a68fbd038b 14: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards a70e0f2b63 13: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards 5f6b456f7f 12: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards 5c4c94a0c7 11: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards 5179317be8 10: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards 30a185d5c9 9: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards 63e6ed3cf0 8: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards 102b1edb89 7: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards 9271d7c22f 6: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards 3545f76cc0 5: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards ae0005f6be 4: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new 3c62da0e8b 4: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new 603ceaa44f 5: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new dea337014e 6: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new db563beb80 7: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new 69c297eb5f 8: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new 484ec13c9c 9: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new 62c1ab55e0 10: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new 5307eca9a3 11: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new c67c895bcd 12: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new bcfd409e37 13: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new ef70b4fcfe 14: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new 56e3c60069 15: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new 9d31fc08c3 16: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new c24393a0f9 17: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new 1129c8ccda 18: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new 2ce79dd36b 19: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new 83ac82d926 20: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new aaa0d045e6 21: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new 07ce72db3e 22: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new 6ee1c1c507 23: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new 511826be5a 24: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new 35b1c02f93 25: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new 401f7e7868 26: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new 87c45af026 27: onsuccess: 1: Successful build after binutils/gcc/gdb: 2 [...] new 9b6fcd9b77 28: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] new 3cee446ddd 29: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 2ff4ab1147 30: onsuccess: 1: Successful build after binutils/gcc/gdb/qe [...] new 1c34002179 31: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] new 59e8c0ecfe 32: onsuccess: 1: Successful build after gcc: 7 commits new 40b4ba3448 33: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new ab873ad90c 34: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] new 506ba0449d 35: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] new 238a7f36aa 36: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 8392151d85 37: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] new 90b004972b 38: onsuccess: 1: Successful build after gcc/linux: 95 commits new a38e82e4a7 39: onsuccess: 1: Successful build after binutils/gcc/gdb/qe [...] new ee78ece841 40: onsuccess: 1: Successful build after linux/qemu: 147 commits new dccf18e682 41: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 860612f2e5 42: onsuccess: 1: Successful build after gcc: libcpp: Implem [...] new 19b0aed7fe 43: onsuccess: 1: Successful build after gcc: LoongArch: Add [...] new 97c464458a 44: onsuccess: 1: Successful build after gcc/linux: 35 commits new e620bd218a 45: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new e9863f5a94 46: onsuccess: 1: Successful build after binutils/gdb: 2 commits new 9256a17d70 47: onsuccess: 1: Successful build after linux: 10 commits new 2010e839a8 48: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new ca65dce66f 49: onsuccess: 1: Successful build after gcc/glibc: 5 commits new e30e5d9f16 50: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] new 742639e2f9 51: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 5d974e3fe9 52: onsuccess: 1: Successful build after binutils/gcc/gdb: 7 [...] new 5264c44d9d 53: onsuccess: 1: Successful build after binutils/gcc/gdb: 8 [...] new bc1d5b72d2 54: onsuccess: 1: Successful build after binutils/gcc/gdb: 8 [...] new 99f47319ec 55: onsuccess: 1: Successful build after gcc/linux/glibc/qem [...] new eaa762106b 56: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 7c6268806b 57: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] new 55c8581c8c 58: onsuccess: 1: Successful build after binutils: gdb: new [...] new e7f413771d 59: onsuccess: 1: Successful build after binutils: 2 commits new ece04834cc 60: onsuccess: 1: Successful build after glibc: 2 commits new 984567d701 61: onsuccess: 1: Successful build after binutils/gcc/gdb/qe [...] new 10c6f74e32 62: onsuccess: 1: Successful build after binutils/gcc/gdb: 2 [...] new adc9eb1cf6 63: onsuccess: 1: Successful build after binutils/gcc/gdb: 8 [...] new c4a3015260 64: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new d04739e100 65: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 411012e190 66: onsuccess: 1: Successful build after gcc/glibc: 10 commits new 2a3d44397d 67: onsuccess: 1: Successful build after binutils/gcc/gdb: 1 [...] new 265b50eb22 68: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 39a0ed210b 69: onsuccess: 1: Successful build after binutils/gcc/gdb: 5 [...] new 8ada391c1b 70: onsuccess: 1: Successful build after binutils/gcc/gdb: 4 [...] new 41ba6725c7 71: onsuccess: 1: Successful build after gcc/glibc: 3 commits new ce450fef36 72: onsuccess: 1: Successful build after linux: 12 commits new 904d283383 73: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 1b2dbd458a 74: onsuccess: 1: Successful build after binutils/gdb: 2 commits new baab571988 75: onsuccess: 1: Successful build after linux: 44 commits new 0eec472c39 76: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 7a88352587 77: onsuccess: 1: Successful build after gcc/linux/glibc: 22 [...] new 724ecc8e52 78: onsuccess: 1: Successful build after binutils/gcc/gdb: 4 [...] new 559b9a6ec5 79: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] new ae868fb2d7 80: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] new aecdc79c3e 81: onsuccess: 1: Successful build after binutils/gcc/gdb: 6 [...] new bcd3ef07ab 82: onsuccess: 1: Successful build after binutils/gcc/gdb: 1 [...] new 95628b3647 83: onsuccess: 1: Success after binutils/gcc/glibc/gdb: 17 commits new 14574dbcf3 84: onsuccess: 1: Success after binutils/gcc/linux/gdb: 68 commits new 1e8ec4260f 85: onsuccess: 1: Success after binutils/gcc/glibc/gdb/qemu: [...] new cc5efc7d04 86: onsuccess: 1: Success after binutils/gcc/gdb: 7 commits new 1fb4179f75 87: onsuccess: 1: Success after binutils/gcc/gdb: 14 commits new c40eefacc9 88: onsuccess: 1: Success after gcc/linux/qemu: 149 commits new b117f50350 89: onsuccess: 1: Success after binutils/gcc/gdb: 5 commits new e5403a1965 90: onsuccess: 1: Success after binutils/gcc/gdb: 19 commits new ee5e1bd0c5 91: onsuccess: 1: Success after binutils/gcc/gdb: 8 commits new 059b1a837d 92: onsuccess: 1: Success after binutils/gcc/linux/gdb/qemu: [...] new ae71f023c2 93: onsuccess: 1: Success after binutils/gcc/linux/gdb: 88 commits new 83477f8676 94: onsuccess: 1: Success after gcc: openmp: Partial OpenMP [...] new 9005615be2 95: onsuccess: #2070: 1: Success after basepoints/gcc-13-238 [...] new 44bf4667b2 96: onsuccess: #2071: 1: Success after gcc/linux: 56 commits new da25d42625 97: onsuccess: #2072: 1: Success after binutils/gcc/gdb: 3 commits new c04ba429c0 98: onsuccess: #2073: 1: Success after gcc/linux: 11 commits new 250626bcd1 99: onsuccess: #2074: 1: Success after baseline build: no ne [...] new 4de786d1ff 100: onsuccess: #2077: 1: Success after binutils/gcc/linux/g [...] new fee71f0820 101: onsuccess: #2130: 1: Success after binutils: 81 commits new e6f56cb8e0 102: onsuccess: #2133: 1: Success after gdb-12-branchpoint-1 [...] new ce1100d749 103: onsuccess: #2135: 1: Success after gcc/linux/glibc/gdb/ [...] new d3914ab5c5 104: onsuccess: #2136: 1: Success after binutils/gcc/gdb: 3 commits new e5874dcdd0 105: onsuccess: #2137: 1: Success after basepoints/gcc-13-27 [...]

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 (45020f34d0) \ 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 1776 -> 1676 bytes 02-prepare_abe/console.log.xz | Bin 2720 -> 2740 bytes 03-build_abe-binutils/console.log.xz | Bin 30044 -> 30100 bytes 04-build_abe-stage1/console.log.xz | Bin 71732 -> 72664 bytes 06-build_abe-linux/console.log.xz | Bin 8336 -> 8332 bytes 07-build_abe-glibc/console.log.xz | Bin 239628 -> 239940 bytes 08-build_abe-stage2/console.log.xz | Bin 203736 -> 203432 bytes 09-build_abe-gdb/console.log.xz | Bin 37292 -> 37464 bytes 10-build_abe-qemu/console.log.xz | Bin 31592 -> 31592 bytes 11-build_abe-dejagnu/console.log.xz | Bin 3892 -> 3880 bytes 12-build_abe-check_gcc/console.log.xz | Bin 2456 -> 2820 bytes 13-check_regression/console.log.xz | Bin 4848 -> 4436 bytes 13-check_regression/extra-bisect-params | 1 + 13-check_regression/fails.sum | 6 + 13-check_regression/mail-body.txt | 105 +- 13-check_regression/results.compare | 46 +- 13-check_regression/results.compare2 | 69 +- 13-check_regression/results.regressions | 26 + 14-update_baseline/console.log | 70 +- dashboard/dashboard-generate.sh | 2 +- git/gcc_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 107 +- mail/mail-subject.txt | 2 +- manifest.sh | 24 +- results | 26 + sumfiles/g++.log.xz | Bin 3401680 -> 3426496 bytes sumfiles/g++.sum | 54 +- sumfiles/gcc.log.xz | Bin 3021536 -> 2998976 bytes sumfiles/gcc.sum | 4056 +++++++++++++++---------------- sumfiles/gfortran.log.xz | Bin 1028312 -> 1030600 bytes sumfiles/gfortran.sum | 2 +- sumfiles/libatomic.log.xz | Bin 2292 -> 2296 bytes sumfiles/libatomic.sum | 2 +- sumfiles/libgomp.log.xz | Bin 202116 -> 201956 bytes sumfiles/libgomp.sum | 9 +- sumfiles/libitm.log.xz | Bin 2656 -> 2656 bytes sumfiles/libitm.sum | 2 +- sumfiles/libstdc++.log.xz | Bin 424996 -> 426332 bytes sumfiles/libstdc++.sum | 8 +- 40 files changed, 2238 insertions(+), 2383 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