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 e5874dcdd 105: onsuccess: #2137: 1: Success after basepoints/gcc-13-271 [...] discards d3914ab5c 104: onsuccess: #2136: 1: Success after binutils/gcc/gdb: 3 commits discards ce1100d74 103: onsuccess: #2135: 1: Success after gcc/linux/glibc/gdb/q [...] discards e6f56cb8e 102: onsuccess: #2133: 1: Success after gdb-12-branchpoint-19 [...] discards fee71f082 101: onsuccess: #2130: 1: Success after binutils: 81 commits discards 4de786d1f 100: onsuccess: #2077: 1: Success after binutils/gcc/linux/gd [...] discards 250626bcd 99: onsuccess: #2074: 1: Success after baseline build: no new [...] discards c04ba429c 98: onsuccess: #2073: 1: Success after gcc/linux: 11 commits discards da25d4262 97: onsuccess: #2072: 1: Success after binutils/gcc/gdb: 3 commits discards 44bf4667b 96: onsuccess: #2071: 1: Success after gcc/linux: 56 commits discards 9005615be 95: onsuccess: #2070: 1: Success after basepoints/gcc-13-2389 [...] discards 83477f867 94: onsuccess: 1: Success after gcc: openmp: Partial OpenMP 5 [...] discards ae71f023c 93: onsuccess: 1: Success after binutils/gcc/linux/gdb: 88 commits discards 059b1a837 92: onsuccess: 1: Success after binutils/gcc/linux/gdb/qemu: [...] discards ee5e1bd0c 91: onsuccess: 1: Success after binutils/gcc/gdb: 8 commits discards e5403a196 90: onsuccess: 1: Success after binutils/gcc/gdb: 19 commits discards b117f5035 89: onsuccess: 1: Success after binutils/gcc/gdb: 5 commits discards c40eefacc 88: onsuccess: 1: Success after gcc/linux/qemu: 149 commits discards 1fb4179f7 87: onsuccess: 1: Success after binutils/gcc/gdb: 14 commits discards cc5efc7d0 86: onsuccess: 1: Success after binutils/gcc/gdb: 7 commits discards 1e8ec4260 85: onsuccess: 1: Success after binutils/gcc/glibc/gdb/qemu: [...] discards 14574dbcf 84: onsuccess: 1: Success after binutils/gcc/linux/gdb: 68 commits discards 95628b364 83: onsuccess: 1: Success after binutils/gcc/glibc/gdb: 17 commits discards bcd3ef07a 82: onsuccess: 1: Successful build after binutils/gcc/gdb: 11 [...] discards aecdc79c3 81: onsuccess: 1: Successful build after binutils/gcc/gdb: 6 commits discards ae868fb2d 80: onsuccess: 1: Successful build after binutils/gcc/glibc/g [...] discards 559b9a6ec 79: onsuccess: 1: Successful build after binutils/gcc/glibc/g [...] discards 724ecc8e5 78: onsuccess: 1: Successful build after binutils/gcc/gdb: 4 commits discards 7a8835258 77: onsuccess: 1: Successful build after gcc/linux/glibc: 22 commits discards 0eec472c3 76: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] discards baab57198 75: onsuccess: 1: Successful build after linux: 44 commits discards 1b2dbd458 74: onsuccess: 1: Successful build after binutils/gdb: 2 commits discards 904d28338 73: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] discards ce450fef3 72: onsuccess: 1: Successful build after linux: 12 commits discards 41ba6725c 71: onsuccess: 1: Successful build after gcc/glibc: 3 commits discards 8ada391c1 70: onsuccess: 1: Successful build after binutils/gcc/gdb: 4 commits discards 39a0ed210 69: onsuccess: 1: Successful build after binutils/gcc/gdb: 5 commits discards 265b50eb2 68: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] discards 2a3d44397 67: onsuccess: 1: Successful build after binutils/gcc/gdb: 10 [...] discards 411012e19 66: onsuccess: 1: Successful build after gcc/glibc: 10 commits discards d04739e10 65: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] discards c4a301526 64: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] discards adc9eb1cf 63: onsuccess: 1: Successful build after binutils/gcc/gdb: 8 commits discards 10c6f74e3 62: onsuccess: 1: Successful build after binutils/gcc/gdb: 22 [...] discards 984567d70 61: onsuccess: 1: Successful build after binutils/gcc/gdb/qem [...] discards ece04834c 60: onsuccess: 1: Successful build after glibc: 2 commits discards e7f413771 59: onsuccess: 1: Successful build after binutils: 2 commits discards 55c8581c8 58: onsuccess: 1: Successful build after binutils: gdb: new ' [...] discards 7c6268806 57: onsuccess: 1: Successful build after binutils/gcc/glibc/g [...] discards eaa762106 56: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] discards 99f47319e 55: onsuccess: 1: Successful build after gcc/linux/glibc/qemu [...] discards bc1d5b72d 54: onsuccess: 1: Successful build after binutils/gcc/gdb: 8 commits discards 5264c44d9 53: onsuccess: 1: Successful build after binutils/gcc/gdb: 8 commits discards 5d974e3fe 52: onsuccess: 1: Successful build after binutils/gcc/gdb: 7 commits discards 742639e2f 51: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] discards e30e5d9f1 50: onsuccess: 1: Successful build after binutils/gcc/glibc/g [...] discards ca65dce66 49: onsuccess: 1: Successful build after gcc/glibc: 5 commits discards 2010e839a 48: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] discards 9256a17d7 47: onsuccess: 1: Successful build after linux: 10 commits discards e9863f5a9 46: onsuccess: 1: Successful build after binutils/gdb: 2 commits discards e620bd218 45: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] discards 97c464458 44: onsuccess: 1: Successful build after gcc/linux: 35 commits discards 19b0aed7f 43: onsuccess: 1: Successful build after gcc: LoongArch: Add [...] discards 860612f2e 42: onsuccess: 1: Successful build after gcc: libcpp: Impleme [...] discards dccf18e68 41: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] discards ee78ece84 40: onsuccess: 1: Successful build after linux/qemu: 147 commits discards a38e82e4a 39: onsuccess: 1: Successful build after binutils/gcc/gdb/qem [...] discards 90b004972 38: onsuccess: 1: Successful build after gcc/linux: 95 commits discards 8392151d8 37: onsuccess: 1: Successful build after binutils/gcc/glibc/g [...] discards 238a7f36a 36: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] discards 506ba0449 35: onsuccess: 1: Successful build after binutils/gcc/glibc/g [...] discards ab873ad90 34: onsuccess: 1: Successful build after binutils/gcc/glibc/g [...] discards 40b4ba344 33: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] discards 59e8c0ecf 32: onsuccess: 1: Successful build after gcc: 7 commits discards 1c3400217 31: onsuccess: 1: Successful build after binutils/gcc/glibc/g [...] discards 2ff4ab114 30: onsuccess: 1: Successful build after binutils/gcc/gdb/qem [...] discards 3cee446dd 29: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] discards 9b6fcd9b7 28: onsuccess: 1: Successful build after binutils/gcc/glibc/g [...] discards 87c45af02 27: onsuccess: 1: Successful build after binutils/gcc/gdb: 25 [...] discards 401f7e786 26: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards 35b1c02f9 25: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards 511826be5 24: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards 6ee1c1c50 23: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards 07ce72db3 22: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards aaa0d045e 21: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards 83ac82d92 20: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards 2ce79dd36 19: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards 1129c8ccd 18: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards c24393a0f 17: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards 9d31fc08c 16: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards 56e3c6006 15: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards ef70b4fcf 14: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards bcfd409e3 13: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards c67c895bc 12: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards 5307eca9a 11: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards 62c1ab55e 10: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards 484ec13c9 9: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards 69c297eb5 8: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards db563beb8 7: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards dea337014 6: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards 603ceaa44 5: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new 2b92c47f9 5: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new 6a60242ea 6: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new 26e3e529c 7: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new 48e912b7c 8: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new f55753c6e 9: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new 0d2f54193 10: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new 4e5edcd95 11: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new cfa6e7cc4 12: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new 123c27910 13: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new 955de72fd 14: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new e1275fa8c 15: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new 9668e4dd5 16: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new 8bc969403 17: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new b42bd8e02 18: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new 345f937ac 19: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new 376e87b40 20: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new b19cf4c7d 21: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new 9cc93272a 22: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new dcbb15b34 23: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new e6d389c82 24: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new 1d2773d11 25: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new a12344612 26: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new dccbb606d 27: onsuccess: 1: Successful build after binutils/gcc/gdb: 25 [...] new b9d6afdc0 28: onsuccess: 1: Successful build after binutils/gcc/glibc/g [...] new 70ccd1706 29: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] new dc4b4453d 30: onsuccess: 1: Successful build after binutils/gcc/gdb/qem [...] new 94a09ae15 31: onsuccess: 1: Successful build after binutils/gcc/glibc/g [...] new 8d7005652 32: onsuccess: 1: Successful build after gcc: 7 commits new 3b3a0cc37 33: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] new 22668ce26 34: onsuccess: 1: Successful build after binutils/gcc/glibc/g [...] new 19b0ae831 35: onsuccess: 1: Successful build after binutils/gcc/glibc/g [...] new c7bd62601 36: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] new de1a031fb 37: onsuccess: 1: Successful build after binutils/gcc/glibc/g [...] new b86d7d8be 38: onsuccess: 1: Successful build after gcc/linux: 95 commits new 1a7e099f6 39: onsuccess: 1: Successful build after binutils/gcc/gdb/qem [...] new 62f78d282 40: onsuccess: 1: Successful build after linux/qemu: 147 commits new b2d4a2305 41: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] new 128047938 42: onsuccess: 1: Successful build after gcc: libcpp: Impleme [...] new 20a97e0ff 43: onsuccess: 1: Successful build after gcc: LoongArch: Add [...] new f4ed93a3f 44: onsuccess: 1: Successful build after gcc/linux: 35 commits new 483719db9 45: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] new 0095d9535 46: onsuccess: 1: Successful build after binutils/gdb: 2 commits new faeaa9c76 47: onsuccess: 1: Successful build after linux: 10 commits new b9aecdd00 48: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] new 204be1c8f 49: onsuccess: 1: Successful build after gcc/glibc: 5 commits new 1f93bfda9 50: onsuccess: 1: Successful build after binutils/gcc/glibc/g [...] new 3665e6506 51: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] new 699db4ecc 52: onsuccess: 1: Successful build after binutils/gcc/gdb: 7 commits new 50446c867 53: onsuccess: 1: Successful build after binutils/gcc/gdb: 8 commits new 30164f4f2 54: onsuccess: 1: Successful build after binutils/gcc/gdb: 8 commits new f4fb8009b 55: onsuccess: 1: Successful build after gcc/linux/glibc/qemu [...] new e8572c9fc 56: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] new 4ddce5a5e 57: onsuccess: 1: Successful build after binutils/gcc/glibc/g [...] new 2b0e5db0c 58: onsuccess: 1: Successful build after binutils: gdb: new ' [...] new f5c8bbcfe 59: onsuccess: 1: Successful build after binutils: 2 commits new 4863b712b 60: onsuccess: 1: Successful build after glibc: 2 commits new 417a32484 61: onsuccess: 1: Successful build after binutils/gcc/gdb/qem [...] new 6cd682b75 62: onsuccess: 1: Successful build after binutils/gcc/gdb: 22 [...] new 040117f59 63: onsuccess: 1: Successful build after binutils/gcc/gdb: 8 commits new c919b02e0 64: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] new 3f2626f1e 65: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] new 3d1beffeb 66: onsuccess: 1: Successful build after gcc/glibc: 10 commits new 810b98eea 67: onsuccess: 1: Successful build after binutils/gcc/gdb: 10 [...] new 98143605c 68: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] new 69aa6bf37 69: onsuccess: 1: Successful build after binutils/gcc/gdb: 5 commits new 7ff50b960 70: onsuccess: 1: Successful build after binutils/gcc/gdb: 4 commits new 1aaaa2056 71: onsuccess: 1: Successful build after gcc/glibc: 3 commits new c6714f523 72: onsuccess: 1: Successful build after linux: 12 commits new d4d328cc0 73: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] new 2aed1a99c 74: onsuccess: 1: Successful build after binutils/gdb: 2 commits new 7c4831688 75: onsuccess: 1: Successful build after linux: 44 commits new 373449c31 76: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] new cc7bc622f 77: onsuccess: 1: Successful build after gcc/linux/glibc: 22 commits new c264160e9 78: onsuccess: 1: Successful build after binutils/gcc/gdb: 4 commits new 036dc66e9 79: onsuccess: 1: Successful build after binutils/gcc/glibc/g [...] new b41cb0be6 80: onsuccess: 1: Successful build after binutils/gcc/glibc/g [...] new 596dcb99c 81: onsuccess: 1: Successful build after binutils/gcc/gdb: 6 commits new 01f3615e0 82: onsuccess: 1: Successful build after binutils/gcc/gdb: 11 [...] new 171b0cd4f 83: onsuccess: 1: Success after binutils/gcc/glibc/gdb: 17 commits new 77372cd14 84: onsuccess: 1: Success after binutils/gcc/linux/gdb: 68 commits new 711643c5a 85: onsuccess: 1: Success after binutils/gcc/glibc/gdb/qemu: [...] new 17e81e985 86: onsuccess: 1: Success after binutils/gcc/gdb: 7 commits new 5e442502c 87: onsuccess: 1: Success after binutils/gcc/gdb: 14 commits new becdabdd4 88: onsuccess: 1: Success after gcc/linux/qemu: 149 commits new ff30f54fa 89: onsuccess: 1: Success after binutils/gcc/gdb: 5 commits new efb79c56a 90: onsuccess: 1: Success after binutils/gcc/gdb: 19 commits new 5b115ea76 91: onsuccess: 1: Success after binutils/gcc/gdb: 8 commits new b3b286588 92: onsuccess: 1: Success after binutils/gcc/linux/gdb/qemu: [...] new 8ad1bea64 93: onsuccess: 1: Success after binutils/gcc/linux/gdb: 88 commits new c85fe6bf2 94: onsuccess: 1: Success after gcc: openmp: Partial OpenMP 5 [...] new 60d5133c1 95: onsuccess: #2070: 1: Success after basepoints/gcc-13-2389 [...] new e0187b1e9 96: onsuccess: #2071: 1: Success after gcc/linux: 56 commits new d782b69a3 97: onsuccess: #2072: 1: Success after binutils/gcc/gdb: 3 commits new 852189791 98: onsuccess: #2073: 1: Success after gcc/linux: 11 commits new eb538367a 99: onsuccess: #2074: 1: Success after baseline build: no new [...] new 81b453d15 100: onsuccess: #2077: 1: Success after binutils/gcc/linux/gd [...] new 7a317d265 101: onsuccess: #2130: 1: Success after binutils: 81 commits new 600b24b60 102: onsuccess: #2133: 1: Success after gdb-12-branchpoint-19 [...] new 9d53340ef 103: onsuccess: #2135: 1: Success after gcc/linux/glibc/gdb/q [...] new 61664b549 104: onsuccess: #2136: 1: Success after binutils/gcc/gdb: 3 commits new 9922dba2d 105: onsuccess: #2137: 1: Success after basepoints/gcc-13-271 [...] new 06f59b34a 106: onsuccess: #2138: 1: Success after binutils/gcc/glibc/gd [...]

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 (e5874dcdd) \ 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 1676 -> 1800 bytes 02-prepare_abe/console.log.xz | Bin 2740 -> 2732 bytes 03-build_abe-binutils/console.log.xz | Bin 30100 -> 30412 bytes 04-build_abe-stage1/console.log.xz | Bin 72664 -> 72528 bytes 06-build_abe-linux/console.log.xz | Bin 8332 -> 8308 bytes 07-build_abe-glibc/console.log.xz | Bin 239940 -> 239664 bytes 08-build_abe-stage2/console.log.xz | Bin 203432 -> 203284 bytes 09-build_abe-gdb/console.log.xz | Bin 37464 -> 37580 bytes 10-build_abe-qemu/console.log.xz | Bin 31592 -> 31660 bytes 11-build_abe-dejagnu/console.log.xz | Bin 3880 -> 3932 bytes 12-build_abe-check_gcc/console.log.xz | Bin 2820 -> 2812 bytes 13-check_regression/console.log.xz | Bin 4436 -> 5300 bytes 13-check_regression/extra-bisect-params | 2 +- 13-check_regression/fails.sum | 17 +- 13-check_regression/mail-body.txt | 51 + 13-check_regression/results.compare | 25 + 13-check_regression/results.compare2 | 71 +- 13-check_regression/results.regressions | 25 + 14-update_baseline/console.log | 70 +- dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- git/gdb_rev | 2 +- git/glibc_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 53 +- mail/mail-subject.txt | 2 +- manifest.sh | 36 +- results | 25 + sumfiles/g++.log.xz | Bin 3426496 -> 3419000 bytes sumfiles/g++.sum | 109 +- sumfiles/gcc.log.xz | Bin 2998976 -> 3000224 bytes sumfiles/gcc.sum | 4688 ++++++++++++++++--------------- sumfiles/gfortran.log.xz | Bin 1030600 -> 1025580 bytes sumfiles/gfortran.sum | 83 +- sumfiles/libatomic.log.xz | Bin 2296 -> 2292 bytes sumfiles/libatomic.sum | 2 +- sumfiles/libgomp.log.xz | Bin 201956 -> 201860 bytes sumfiles/libgomp.sum | 9 +- sumfiles/libitm.log.xz | Bin 2656 -> 2656 bytes sumfiles/libitm.sum | 2 +- sumfiles/libstdc++.log.xz | Bin 426332 -> 423064 bytes sumfiles/libstdc++.sum | 8 +- 43 files changed, 2785 insertions(+), 2505 deletions(-)