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 e9a7b56e7 101: onsuccess: #2130: 1: Success after binutils: 81 commits discards f4bf6ad7a 100: onsuccess: #2077: 1: Success after binutils/gcc/linux/gd [...] discards b26a23609 99: onsuccess: #2074: 1: Success after baseline build: no new [...] discards ff87fa492 98: onsuccess: #2073: 1: Success after gcc/linux: 11 commits discards 526911cf0 97: onsuccess: #2072: 1: Success after binutils/gcc/gdb: 3 commits discards aa3f225c5 96: onsuccess: #2071: 1: Success after gcc/linux: 56 commits discards c78823320 95: onsuccess: #2070: 1: Success after basepoints/gcc-13-2389 [...] discards 1da510b6c 94: onsuccess: 1: Success after gcc: openmp: Partial OpenMP 5 [...] discards 2b882c0e0 93: onsuccess: 1: Success after binutils/gcc/linux/gdb: 88 commits discards 2b944190d 92: onsuccess: 1: Success after binutils/gcc/linux/gdb/qemu: [...] discards 8c17959ad 91: onsuccess: 1: Success after binutils/gcc/gdb: 8 commits discards 1d5aad55b 90: onsuccess: 1: Success after binutils/gcc/gdb: 19 commits discards 847059e9d 89: onsuccess: 1: Success after binutils/gcc/gdb: 5 commits discards cf14659d7 88: onsuccess: 1: Success after gcc/linux/qemu: 149 commits discards 2b75f8db8 87: onsuccess: 1: Success after binutils/gcc/gdb: 14 commits discards c3df05af8 86: onsuccess: 1: Success after binutils/gcc/gdb: 7 commits discards 5c3eb66e9 85: onsuccess: 1: Success after binutils/gcc/glibc/gdb/qemu: [...] discards 843f3fdfe 84: onsuccess: 1: Success after binutils/gcc/linux/gdb: 68 commits discards eabf755c8 83: onsuccess: 1: Success after binutils/gcc/glibc/gdb: 17 commits discards 10a357f58 82: onsuccess: 1: Successful build after binutils/gcc/gdb: 11 [...] discards 8b7f85fa3 81: onsuccess: 1: Successful build after binutils/gcc/gdb: 6 commits discards ec3c3f012 80: onsuccess: 1: Successful build after binutils/gcc/glibc/g [...] discards 7374fe6a3 79: onsuccess: 1: Successful build after binutils/gcc/glibc/g [...] discards 494e04510 78: onsuccess: 1: Successful build after binutils/gcc/gdb: 4 commits discards 8c1c3be9f 77: onsuccess: 1: Successful build after gcc/linux/glibc: 22 commits discards 33df202e8 76: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] discards 1137a04c4 75: onsuccess: 1: Successful build after linux: 44 commits discards a0003fe86 74: onsuccess: 1: Successful build after binutils/gdb: 2 commits discards 4bb8fb91a 73: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] discards f697e8bf3 72: onsuccess: 1: Successful build after linux: 12 commits discards 89901294d 71: onsuccess: 1: Successful build after gcc/glibc: 3 commits discards add8c492a 70: onsuccess: 1: Successful build after binutils/gcc/gdb: 4 commits discards 8143ba5a4 69: onsuccess: 1: Successful build after binutils/gcc/gdb: 5 commits discards 98462f272 68: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] discards 581af9895 67: onsuccess: 1: Successful build after binutils/gcc/gdb: 10 [...] discards 8c4622578 66: onsuccess: 1: Successful build after gcc/glibc: 10 commits discards c6f111e54 65: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] discards f5905f18d 64: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] discards 53718168d 63: onsuccess: 1: Successful build after binutils/gcc/gdb: 8 commits discards d92f208d2 62: onsuccess: 1: Successful build after binutils/gcc/gdb: 22 [...] discards d3b2e2182 61: onsuccess: 1: Successful build after binutils/gcc/gdb/qem [...] discards feb80378a 60: onsuccess: 1: Successful build after glibc: 2 commits discards afa64b187 59: onsuccess: 1: Successful build after binutils: 2 commits discards 93a6c7825 58: onsuccess: 1: Successful build after binutils: gdb: new ' [...] discards e107f28ac 57: onsuccess: 1: Successful build after binutils/gcc/glibc/g [...] discards 84771f642 56: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] discards a16ece0e7 55: onsuccess: 1: Successful build after gcc/linux/glibc/qemu [...] discards 76de4e3b8 54: onsuccess: 1: Successful build after binutils/gcc/gdb: 8 commits discards 8d6160011 53: onsuccess: 1: Successful build after binutils/gcc/gdb: 8 commits discards 1b2e0d514 52: onsuccess: 1: Successful build after binutils/gcc/gdb: 7 commits discards 5d5e53cb3 51: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] discards 07a3843a4 50: onsuccess: 1: Successful build after binutils/gcc/glibc/g [...] discards c19b9dbb2 49: onsuccess: 1: Successful build after gcc/glibc: 5 commits discards b91392046 48: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] discards c14108649 47: onsuccess: 1: Successful build after linux: 10 commits discards d378e646a 46: onsuccess: 1: Successful build after binutils/gdb: 2 commits discards 06b96c4c2 45: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] discards 79e40d499 44: onsuccess: 1: Successful build after gcc/linux: 35 commits discards da1e632db 43: onsuccess: 1: Successful build after gcc: LoongArch: Add [...] discards e0f592c2b 42: onsuccess: 1: Successful build after gcc: libcpp: Impleme [...] discards a710ad32c 41: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] discards 38a0801a5 40: onsuccess: 1: Successful build after linux/qemu: 147 commits discards d7a885e33 39: onsuccess: 1: Successful build after binutils/gcc/gdb/qem [...] discards 447d5ea79 38: onsuccess: 1: Successful build after gcc/linux: 95 commits discards 2e395adf6 37: onsuccess: 1: Successful build after binutils/gcc/glibc/g [...] discards eddd34bea 36: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] discards e80f5df43 35: onsuccess: 1: Successful build after binutils/gcc/glibc/g [...] discards 2cb8a1d9c 34: onsuccess: 1: Successful build after binutils/gcc/glibc/g [...] discards 79fde465f 33: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] discards 43f94fc14 32: onsuccess: 1: Successful build after gcc: 7 commits discards c7094eafe 31: onsuccess: 1: Successful build after binutils/gcc/glibc/g [...] discards 9b3d63303 30: onsuccess: 1: Successful build after binutils/gcc/gdb/qem [...] discards 02b6a2933 29: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] discards e5514cec9 28: onsuccess: 1: Successful build after binutils/gcc/glibc/g [...] discards 610b2c92e 27: onsuccess: 1: Successful build after binutils/gcc/gdb: 25 [...] discards d8e04a7f5 26: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards bfb259e8b 25: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards 805cf595a 24: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards 9fd7e1852 23: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards 9d464892e 22: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards 55b309020 21: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards 99d45d4b7 20: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards abfacde7f 19: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards e690823e7 18: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards f5c83d44e 17: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards cf9b4e0f0 16: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards cf840cc52 15: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards f939024ab 14: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards 83f06f7cf 13: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards 5c4b411e2 12: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards 42863783f 11: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards d4971e6ea 10: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards 34011e530 9: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards b4755a4a7 8: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards 6487f6de0 7: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards 2185071dc 6: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards 9cac9ddd9 5: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards 044c7b5f2 4: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards 314bedafc 3: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards 6791892ab 2: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards 6bd93579f 1: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new edc4ab8ff 1: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new 9f6f5409b 2: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new 5a4f58c00 3: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new f75e51221 4: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new a367e6c6a 5: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new 5761bd014 6: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new 3255aeaf2 7: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new 3a9bf755a 8: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new 78580e81a 9: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new 088d9f54a 10: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new 8aaa5160a 11: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new 431c4e17b 12: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new 89a5e27da 13: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new 6e52d4ec4 14: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new 7a589388c 15: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new 7c91225bf 16: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new 9ab0e8e0d 17: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new b0954e98b 18: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new b1360c592 19: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new f7f36b4e3 20: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new cdca181ff 21: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new f7ff8218f 22: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new af9f3a483 23: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new 2cf51b80f 24: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new 039cff954 25: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new dde4a1626 26: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new 4d6777338 27: onsuccess: 1: Successful build after binutils/gcc/gdb: 25 [...] new 7ad4b117c 28: onsuccess: 1: Successful build after binutils/gcc/glibc/g [...] new bea70fa04 29: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] new 86c0b51ea 30: onsuccess: 1: Successful build after binutils/gcc/gdb/qem [...] new 703f7e2f7 31: onsuccess: 1: Successful build after binutils/gcc/glibc/g [...] new 5bf3388f9 32: onsuccess: 1: Successful build after gcc: 7 commits new 9a324ea2e 33: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] new e4397607b 34: onsuccess: 1: Successful build after binutils/gcc/glibc/g [...] new 76d0518cc 35: onsuccess: 1: Successful build after binutils/gcc/glibc/g [...] new d80b8f981 36: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] new 813d359d7 37: onsuccess: 1: Successful build after binutils/gcc/glibc/g [...] new 284313757 38: onsuccess: 1: Successful build after gcc/linux: 95 commits new 2eb0ae4aa 39: onsuccess: 1: Successful build after binutils/gcc/gdb/qem [...] new a51ee3ef6 40: onsuccess: 1: Successful build after linux/qemu: 147 commits new 10758ea5a 41: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] new ab6c96d19 42: onsuccess: 1: Successful build after gcc: libcpp: Impleme [...] new 5609d411b 43: onsuccess: 1: Successful build after gcc: LoongArch: Add [...] new c158d6e12 44: onsuccess: 1: Successful build after gcc/linux: 35 commits new a6a299a0e 45: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] new cf99878fd 46: onsuccess: 1: Successful build after binutils/gdb: 2 commits new 28068461d 47: onsuccess: 1: Successful build after linux: 10 commits new fae3ab234 48: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] new 833b645c8 49: onsuccess: 1: Successful build after gcc/glibc: 5 commits new de41114a5 50: onsuccess: 1: Successful build after binutils/gcc/glibc/g [...] new f658ba8e4 51: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] new 5a3cc6558 52: onsuccess: 1: Successful build after binutils/gcc/gdb: 7 commits new 703a744ad 53: onsuccess: 1: Successful build after binutils/gcc/gdb: 8 commits new 05493529d 54: onsuccess: 1: Successful build after binutils/gcc/gdb: 8 commits new 9f204a4b3 55: onsuccess: 1: Successful build after gcc/linux/glibc/qemu [...] new 475526cfa 56: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] new 481051845 57: onsuccess: 1: Successful build after binutils/gcc/glibc/g [...] new 829442fe0 58: onsuccess: 1: Successful build after binutils: gdb: new ' [...] new 68c830ba5 59: onsuccess: 1: Successful build after binutils: 2 commits new d9acc583c 60: onsuccess: 1: Successful build after glibc: 2 commits new d0c1d10a6 61: onsuccess: 1: Successful build after binutils/gcc/gdb/qem [...] new 6665a543d 62: onsuccess: 1: Successful build after binutils/gcc/gdb: 22 [...] new 4b57b2073 63: onsuccess: 1: Successful build after binutils/gcc/gdb: 8 commits new 282317fb0 64: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] new cca5ece86 65: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] new 38d34f15a 66: onsuccess: 1: Successful build after gcc/glibc: 10 commits new 5fe07b29b 67: onsuccess: 1: Successful build after binutils/gcc/gdb: 10 [...] new 2e9bb0602 68: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] new 5c5dfa0b4 69: onsuccess: 1: Successful build after binutils/gcc/gdb: 5 commits new 8c6affd01 70: onsuccess: 1: Successful build after binutils/gcc/gdb: 4 commits new 3ccaf6a22 71: onsuccess: 1: Successful build after gcc/glibc: 3 commits new b11988902 72: onsuccess: 1: Successful build after linux: 12 commits new 052ec8381 73: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] new 740b5bc5a 74: onsuccess: 1: Successful build after binutils/gdb: 2 commits new 1a745425e 75: onsuccess: 1: Successful build after linux: 44 commits new 03268e289 76: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] new 4ccea2e96 77: onsuccess: 1: Successful build after gcc/linux/glibc: 22 commits new 5ea1f7cb4 78: onsuccess: 1: Successful build after binutils/gcc/gdb: 4 commits new 2e4996f48 79: onsuccess: 1: Successful build after binutils/gcc/glibc/g [...] new 8de2e1476 80: onsuccess: 1: Successful build after binutils/gcc/glibc/g [...] new 9c469cbcd 81: onsuccess: 1: Successful build after binutils/gcc/gdb: 6 commits new c003b305d 82: onsuccess: 1: Successful build after binutils/gcc/gdb: 11 [...] new da37e2b16 83: onsuccess: 1: Success after binutils/gcc/glibc/gdb: 17 commits new 8397d403f 84: onsuccess: 1: Success after binutils/gcc/linux/gdb: 68 commits new a141eb1a9 85: onsuccess: 1: Success after binutils/gcc/glibc/gdb/qemu: [...] new 13310567d 86: onsuccess: 1: Success after binutils/gcc/gdb: 7 commits new 11532411c 87: onsuccess: 1: Success after binutils/gcc/gdb: 14 commits new 221a6f716 88: onsuccess: 1: Success after gcc/linux/qemu: 149 commits new 80af09fac 89: onsuccess: 1: Success after binutils/gcc/gdb: 5 commits new 05502f703 90: onsuccess: 1: Success after binutils/gcc/gdb: 19 commits new 09d63a244 91: onsuccess: 1: Success after binutils/gcc/gdb: 8 commits new 9935e89aa 92: onsuccess: 1: Success after binutils/gcc/linux/gdb/qemu: [...] new c3c0b2b74 93: onsuccess: 1: Success after binutils/gcc/linux/gdb: 88 commits new 186a0940e 94: onsuccess: 1: Success after gcc: openmp: Partial OpenMP 5 [...] new a938fbccc 95: onsuccess: #2070: 1: Success after basepoints/gcc-13-2389 [...] new 0586da351 96: onsuccess: #2071: 1: Success after gcc/linux: 56 commits new 5fd1bd3ff 97: onsuccess: #2072: 1: Success after binutils/gcc/gdb: 3 commits new d08229a95 98: onsuccess: #2073: 1: Success after gcc/linux: 11 commits new b7f2ac6f2 99: onsuccess: #2074: 1: Success after baseline build: no new [...] new 58c991731 100: onsuccess: #2077: 1: Success after binutils/gcc/linux/gd [...] new b63c242d5 101: onsuccess: #2130: 1: Success after binutils: 81 commits new c467df3e2 102: onsuccess: #2133: 1: Success after gdb-12-branchpoint-19 [...]

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 (e9a7b56e7) \ 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 1764 -> 1696 bytes 02-prepare_abe/console.log.xz | Bin 2728 -> 2736 bytes 03-build_abe-binutils/console.log.xz | Bin 30404 -> 30116 bytes 04-build_abe-stage1/console.log.xz | Bin 73592 -> 73408 bytes 05-clean_sysroot/console.log.xz | Bin 328 -> 328 bytes 06-build_abe-linux/console.log.xz | Bin 8456 -> 8472 bytes 07-build_abe-glibc/console.log.xz | Bin 240100 -> 239744 bytes 08-build_abe-stage2/console.log.xz | Bin 206936 -> 203960 bytes 09-build_abe-gdb/console.log.xz | Bin 38308 -> 37512 bytes 10-build_abe-qemu/console.log.xz | Bin 32132 -> 31900 bytes 11-build_abe-dejagnu/console.log.xz | Bin 3876 -> 3876 bytes 12-build_abe-check_gcc/console.log.xz | Bin 3448 -> 3464 bytes 13-check_regression/console.log.xz | Bin 4196 -> 3844 bytes 13-check_regression/extra-bisect-params | 1 - 13-check_regression/fails.sum | 6 - 13-check_regression/mail-body.txt | 42 +- 13-check_regression/results.compare | 26 +- 13-check_regression/results.compare2 | 39 +- 13-check_regression/results.regressions | 26 - 14-update_baseline/console.log | 66 +- dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 44 +- mail/mail-subject.txt | 2 +- manifest.sh | 12 +- results | 26 - sumfiles/g++.log.xz | Bin 3393248 -> 3403724 bytes sumfiles/g++.sum | 178 +- sumfiles/gcc.log.xz | Bin 3011160 -> 3005912 bytes sumfiles/gcc.sum | 5070 +++++++++++++++---------------- sumfiles/gfortran.log.xz | Bin 1025640 -> 1026720 bytes sumfiles/gfortran.sum | 42 +- sumfiles/libatomic.log.xz | Bin 2292 -> 2288 bytes sumfiles/libatomic.sum | 4 +- sumfiles/libgomp.log.xz | Bin 200376 -> 200664 bytes sumfiles/libgomp.sum | 16 +- sumfiles/libitm.log.xz | Bin 2660 -> 2656 bytes sumfiles/libitm.sum | 6 +- sumfiles/libstdc++.log.xz | Bin 426528 -> 418796 bytes sumfiles/libstdc++.sum | 10 +- 41 files changed, 2788 insertions(+), 2834 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