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 38c938016 110: onsuccess: #2142: 1: Success after binutils/gcc/glibc/gd [...] discards c187aa268 109: onsuccess: #2141: 1: Success after gcc/glibc: 6 commits discards becbf2222 108: onsuccess: #2140: 1: Success after binutils/gcc/gdb: 5 commits discards c03e17349 107: onsuccess: #2139: 1: Success after binutils/gcc/gdb: 3 commits discards d96d0ed09 106: onsuccess: #2138: 1: Success after binutils/gcc/glibc/gd [...] discards 123718927 105: onsuccess: #2137: 1: Success after basepoints/gcc-13-271 [...] discards 06b0ba82a 104: onsuccess: #2136: 1: Success after binutils/gcc/gdb: 3 commits discards a599fa2b4 103: onsuccess: #2135: 1: Success after gcc/linux/glibc/gdb/q [...] discards a1bf6a6f2 102: onsuccess: #2133: 1: Success after gdb-12-branchpoint-19 [...] discards e068e3265 101: onsuccess: #2130: 1: Success after binutils: 81 commits discards 5d8e79a8f 100: onsuccess: #2077: 1: Success after binutils/gcc/linux/gd [...] discards 17f459729 99: onsuccess: #2074: 1: Success after baseline build: no new [...] discards 864e596b3 98: onsuccess: #2073: 1: Success after gcc/linux: 11 commits discards 3645d46ed 97: onsuccess: #2072: 1: Success after binutils/gcc/gdb: 3 commits discards 4bb63c625 96: onsuccess: #2071: 1: Success after gcc/linux: 56 commits discards 3108e25db 95: onsuccess: #2070: 1: Success after basepoints/gcc-13-2389 [...] discards fa1d76b2f 94: onsuccess: 1: Success after gcc: openmp: Partial OpenMP 5 [...] discards 4038d48dd 93: onsuccess: 1: Success after binutils/gcc/linux/gdb: 88 commits discards e3d97b25c 92: onsuccess: 1: Success after binutils/gcc/linux/gdb/qemu: [...] discards 3d73c9734 91: onsuccess: 1: Success after binutils/gcc/gdb: 8 commits discards dc4e962b5 90: onsuccess: 1: Success after binutils/gcc/gdb: 19 commits discards 9402b6003 89: onsuccess: 1: Success after binutils/gcc/gdb: 5 commits discards 045d15e97 88: onsuccess: 1: Success after gcc/linux/qemu: 149 commits discards 460ca8aec 87: onsuccess: 1: Success after binutils/gcc/gdb: 14 commits discards bb6421df5 86: onsuccess: 1: Success after binutils/gcc/gdb: 7 commits discards 88a433939 85: onsuccess: 1: Success after binutils/gcc/glibc/gdb/qemu: [...] discards dfc650105 84: onsuccess: 1: Success after binutils/gcc/linux/gdb: 68 commits discards 6c218e8d7 83: onsuccess: 1: Success after binutils/gcc/glibc/gdb: 17 commits discards 980f16d27 82: onsuccess: 1: Successful build after binutils/gcc/gdb: 11 [...] discards 7572e63dc 81: onsuccess: 1: Successful build after binutils/gcc/gdb: 6 commits discards b2ff276ce 80: onsuccess: 1: Successful build after binutils/gcc/glibc/g [...] discards 184e98e7e 79: onsuccess: 1: Successful build after binutils/gcc/glibc/g [...] discards 5bad0cc71 78: onsuccess: 1: Successful build after binutils/gcc/gdb: 4 commits discards a6e5bcd77 77: onsuccess: 1: Successful build after gcc/linux/glibc: 22 commits discards 0ae01d55e 76: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] discards cfe488de6 75: onsuccess: 1: Successful build after linux: 44 commits discards 1c0606b46 74: onsuccess: 1: Successful build after binutils/gdb: 2 commits discards d1bed5486 73: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] discards 443970e54 72: onsuccess: 1: Successful build after linux: 12 commits discards ef62e3b6c 71: onsuccess: 1: Successful build after gcc/glibc: 3 commits discards f5c49ea6d 70: onsuccess: 1: Successful build after binutils/gcc/gdb: 4 commits discards a6b698a16 69: onsuccess: 1: Successful build after binutils/gcc/gdb: 5 commits discards 4af94ef4e 68: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] discards e61cb7123 67: onsuccess: 1: Successful build after binutils/gcc/gdb: 10 [...] discards 3f95ff0ff 66: onsuccess: 1: Successful build after gcc/glibc: 10 commits discards 288723b13 65: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] discards abe3ea425 64: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] discards 43a32fa0d 63: onsuccess: 1: Successful build after binutils/gcc/gdb: 8 commits discards 1865821cc 62: onsuccess: 1: Successful build after binutils/gcc/gdb: 22 [...] discards 608f1898a 61: onsuccess: 1: Successful build after binutils/gcc/gdb/qem [...] discards b376bceaa 60: onsuccess: 1: Successful build after glibc: 2 commits discards 7242771ee 59: onsuccess: 1: Successful build after binutils: 2 commits discards 1a12e1dd3 58: onsuccess: 1: Successful build after binutils: gdb: new ' [...] discards 86f09d0ec 57: onsuccess: 1: Successful build after binutils/gcc/glibc/g [...] discards 51f37fddf 56: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] discards 9b96cbb23 55: onsuccess: 1: Successful build after gcc/linux/glibc/qemu [...] discards bb46c1123 54: onsuccess: 1: Successful build after binutils/gcc/gdb: 8 commits discards dc8db3b38 53: onsuccess: 1: Successful build after binutils/gcc/gdb: 8 commits discards 9065a1c12 52: onsuccess: 1: Successful build after binutils/gcc/gdb: 7 commits discards 2a9a12fed 51: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] discards bc3099adf 50: onsuccess: 1: Successful build after binutils/gcc/glibc/g [...] discards 7a4deb6c7 49: onsuccess: 1: Successful build after gcc/glibc: 5 commits discards 56b01ba37 48: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] discards e12d3d917 47: onsuccess: 1: Successful build after linux: 10 commits discards cd312007b 46: onsuccess: 1: Successful build after binutils/gdb: 2 commits discards bb557981e 45: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] discards f3a62b2cd 44: onsuccess: 1: Successful build after gcc/linux: 35 commits discards 43e594e85 43: onsuccess: 1: Successful build after gcc: LoongArch: Add [...] discards 0ec8088ad 42: onsuccess: 1: Successful build after gcc: libcpp: Impleme [...] discards ecab89e08 41: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] discards adff658d2 40: onsuccess: 1: Successful build after linux/qemu: 147 commits discards b85c2f9d3 39: onsuccess: 1: Successful build after binutils/gcc/gdb/qem [...] discards 19f2fb7a8 38: onsuccess: 1: Successful build after gcc/linux: 95 commits discards 74900233f 37: onsuccess: 1: Successful build after binutils/gcc/glibc/g [...] discards 87837ced4 36: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] discards ad79e8ab6 35: onsuccess: 1: Successful build after binutils/gcc/glibc/g [...] discards 53b0d1d4b 34: onsuccess: 1: Successful build after binutils/gcc/glibc/g [...] discards 3055bd492 33: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] discards 541763329 32: onsuccess: 1: Successful build after gcc: 7 commits discards 4a638f984 31: onsuccess: 1: Successful build after binutils/gcc/glibc/g [...] discards d5222cca6 30: onsuccess: 1: Successful build after binutils/gcc/gdb/qem [...] discards 1c7528519 29: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] discards 793f7d35d 28: onsuccess: 1: Successful build after binutils/gcc/glibc/g [...] discards b80d9e1cc 27: onsuccess: 1: Successful build after binutils/gcc/gdb: 25 [...] discards 4df0fe610 26: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards 5a8f82dab 25: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards b11b97052 24: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards 15f8cd145 23: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards 2fa3feba0 22: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards 3e3506e3c 21: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards 6922d7ea4 20: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards 0b1c5099f 19: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards 775bd7d3d 18: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards d4bba6d8d 17: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards f75ad1e51 16: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards 77bf2711a 15: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards 69e139340 14: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards 8edd3bcc2 13: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards 9d02ef179 12: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards 8fc41c4b6 11: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards 788e7ba0b 10: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new 5758065cb 10: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new ca986dffa 11: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new 3f7f53b1c 12: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new 143b3d9f9 13: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new 5fa6d24b0 14: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new 624580fad 15: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new 675d725f3 16: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new 29f2bbc46 17: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new 1c117646a 18: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new ecb52ce30 19: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new c900d104d 20: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new 0e6416cbc 21: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new c99c1f9e1 22: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new 7bc174183 23: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new a3b7d2aec 24: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new 14b4cafaa 25: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new f481e29f8 26: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new f24acb4b8 27: onsuccess: 1: Successful build after binutils/gcc/gdb: 25 [...] new 1efc808db 28: onsuccess: 1: Successful build after binutils/gcc/glibc/g [...] new 4d90ffa20 29: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] new e98e1f78e 30: onsuccess: 1: Successful build after binutils/gcc/gdb/qem [...] new cc35a2975 31: onsuccess: 1: Successful build after binutils/gcc/glibc/g [...] new abaa9a3f8 32: onsuccess: 1: Successful build after gcc: 7 commits new 97f4a7e30 33: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] new f6d474e28 34: onsuccess: 1: Successful build after binutils/gcc/glibc/g [...] new 7da3e40bf 35: onsuccess: 1: Successful build after binutils/gcc/glibc/g [...] new dec1cc71d 36: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] new 071cb2bbd 37: onsuccess: 1: Successful build after binutils/gcc/glibc/g [...] new 3ac54a639 38: onsuccess: 1: Successful build after gcc/linux: 95 commits new 9b2adb2ef 39: onsuccess: 1: Successful build after binutils/gcc/gdb/qem [...] new d40935fea 40: onsuccess: 1: Successful build after linux/qemu: 147 commits new c92ea736d 41: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] new a41b2263c 42: onsuccess: 1: Successful build after gcc: libcpp: Impleme [...] new 88dae402a 43: onsuccess: 1: Successful build after gcc: LoongArch: Add [...] new cd3a11647 44: onsuccess: 1: Successful build after gcc/linux: 35 commits new 8e684deee 45: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] new e4595e336 46: onsuccess: 1: Successful build after binutils/gdb: 2 commits new 47136dcc7 47: onsuccess: 1: Successful build after linux: 10 commits new 39e6c5c9c 48: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] new bab98fcc4 49: onsuccess: 1: Successful build after gcc/glibc: 5 commits new f3b9a0663 50: onsuccess: 1: Successful build after binutils/gcc/glibc/g [...] new e2eba2e8f 51: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] new f50f59897 52: onsuccess: 1: Successful build after binutils/gcc/gdb: 7 commits new 51586a020 53: onsuccess: 1: Successful build after binutils/gcc/gdb: 8 commits new 94fa97566 54: onsuccess: 1: Successful build after binutils/gcc/gdb: 8 commits new 0628b15cc 55: onsuccess: 1: Successful build after gcc/linux/glibc/qemu [...] new a222f1aad 56: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] new 8e75422a4 57: onsuccess: 1: Successful build after binutils/gcc/glibc/g [...] new 2d4036bac 58: onsuccess: 1: Successful build after binutils: gdb: new ' [...] new 2b3b72954 59: onsuccess: 1: Successful build after binutils: 2 commits new 9cc7e079b 60: onsuccess: 1: Successful build after glibc: 2 commits new c21db4ad8 61: onsuccess: 1: Successful build after binutils/gcc/gdb/qem [...] new edcd5486b 62: onsuccess: 1: Successful build after binutils/gcc/gdb: 22 [...] new 2a7cdbcfb 63: onsuccess: 1: Successful build after binutils/gcc/gdb: 8 commits new 1a6081f31 64: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] new e3c6b6567 65: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] new 135ac0367 66: onsuccess: 1: Successful build after gcc/glibc: 10 commits new e2c395de0 67: onsuccess: 1: Successful build after binutils/gcc/gdb: 10 [...] new 8311c5bff 68: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] new 55f2b668a 69: onsuccess: 1: Successful build after binutils/gcc/gdb: 5 commits new 0e9446045 70: onsuccess: 1: Successful build after binutils/gcc/gdb: 4 commits new 068eaab05 71: onsuccess: 1: Successful build after gcc/glibc: 3 commits new c8be3b384 72: onsuccess: 1: Successful build after linux: 12 commits new 5efba6823 73: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] new 7f355febc 74: onsuccess: 1: Successful build after binutils/gdb: 2 commits new 047710a83 75: onsuccess: 1: Successful build after linux: 44 commits new 41821a79b 76: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] new 9389cd788 77: onsuccess: 1: Successful build after gcc/linux/glibc: 22 commits new 6ca3abf12 78: onsuccess: 1: Successful build after binutils/gcc/gdb: 4 commits new 6b1b486f2 79: onsuccess: 1: Successful build after binutils/gcc/glibc/g [...] new 60cc4d2c4 80: onsuccess: 1: Successful build after binutils/gcc/glibc/g [...] new c907db4ca 81: onsuccess: 1: Successful build after binutils/gcc/gdb: 6 commits new 4e79309fc 82: onsuccess: 1: Successful build after binutils/gcc/gdb: 11 [...] new e75b3e271 83: onsuccess: 1: Success after binutils/gcc/glibc/gdb: 17 commits new 99af54616 84: onsuccess: 1: Success after binutils/gcc/linux/gdb: 68 commits new 2d90a19f0 85: onsuccess: 1: Success after binutils/gcc/glibc/gdb/qemu: [...] new 85127a184 86: onsuccess: 1: Success after binutils/gcc/gdb: 7 commits new b4cff5625 87: onsuccess: 1: Success after binutils/gcc/gdb: 14 commits new e1ca3e484 88: onsuccess: 1: Success after gcc/linux/qemu: 149 commits new 76b91940d 89: onsuccess: 1: Success after binutils/gcc/gdb: 5 commits new 9aeea71db 90: onsuccess: 1: Success after binutils/gcc/gdb: 19 commits new e01f5f8d4 91: onsuccess: 1: Success after binutils/gcc/gdb: 8 commits new e67a34fa3 92: onsuccess: 1: Success after binutils/gcc/linux/gdb/qemu: [...] new 1c53d9ffa 93: onsuccess: 1: Success after binutils/gcc/linux/gdb: 88 commits new c0b943914 94: onsuccess: 1: Success after gcc: openmp: Partial OpenMP 5 [...] new 42476c346 95: onsuccess: #2070: 1: Success after basepoints/gcc-13-2389 [...] new 3952ce803 96: onsuccess: #2071: 1: Success after gcc/linux: 56 commits new c3e9d7a57 97: onsuccess: #2072: 1: Success after binutils/gcc/gdb: 3 commits new d1b48d073 98: onsuccess: #2073: 1: Success after gcc/linux: 11 commits new d2e976a3c 99: onsuccess: #2074: 1: Success after baseline build: no new [...] new 218e36284 100: onsuccess: #2077: 1: Success after binutils/gcc/linux/gd [...] new 986ea19a6 101: onsuccess: #2130: 1: Success after binutils: 81 commits new 4bcd9f261 102: onsuccess: #2133: 1: Success after gdb-12-branchpoint-19 [...] new 4d898d903 103: onsuccess: #2135: 1: Success after gcc/linux/glibc/gdb/q [...] new 1e6cd54f9 104: onsuccess: #2136: 1: Success after binutils/gcc/gdb: 3 commits new 58a9e80c9 105: onsuccess: #2137: 1: Success after basepoints/gcc-13-271 [...] new e44a25506 106: onsuccess: #2138: 1: Success after binutils/gcc/glibc/gd [...] new 0987eee3d 107: onsuccess: #2139: 1: Success after binutils/gcc/gdb: 3 commits new d93c05a4f 108: onsuccess: #2140: 1: Success after binutils/gcc/gdb: 5 commits new d88d6ae58 109: onsuccess: #2141: 1: Success after gcc/glibc: 6 commits new efb2474af 110: onsuccess: #2142: 1: Success after binutils/gcc/glibc/gd [...] new 83f268f67 111: onsuccess: #2143: 1: Success after binutils/gcc/linux/gl [...]
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 (38c938016) \ 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 1744 -> 1696 bytes 02-prepare_abe/console.log.xz | Bin 2736 -> 2752 bytes 03-build_abe-binutils/console.log.xz | Bin 30740 -> 30240 bytes 04-build_abe-stage1/console.log.xz | Bin 72836 -> 72400 bytes 05-clean_sysroot/console.log.xz | Bin 328 -> 328 bytes 06-build_abe-linux/console.log.xz | Bin 8316 -> 8604 bytes 07-build_abe-glibc/console.log.xz | Bin 239796 -> 239816 bytes 08-build_abe-stage2/console.log.xz | Bin 203140 -> 203388 bytes 09-build_abe-gdb/console.log.xz | Bin 37844 -> 37336 bytes 10-build_abe-qemu/console.log.xz | Bin 31760 -> 31340 bytes 11-build_abe-dejagnu/console.log.xz | Bin 3884 -> 3884 bytes 12-build_abe-check_gcc/console.log.xz | Bin 3016 -> 2604 bytes 13-check_regression/console.log.xz | Bin 6304 -> 6368 bytes 13-check_regression/extra-bisect-params | 1 - 13-check_regression/fails.sum | 11 - 13-check_regression/mail-body.txt | 110 +- 13-check_regression/results.compare | 78 +- 13-check_regression/results.compare2 | 124 +- 13-check_regression/results.regressions | 85 - 14-update_baseline/console.log | 66 +- dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- git/gdb_rev | 2 +- git/glibc_rev | 2 +- git/linux_rev | 2 +- git/qemu_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 112 +- mail/mail-subject.txt | 2 +- manifest.sh | 46 +- results | 85 - sumfiles/g++.log.xz | Bin 3418228 -> 3423984 bytes sumfiles/g++.sum | 263 +- sumfiles/gcc.log.xz | Bin 3000048 -> 3008684 bytes sumfiles/gcc.sum | 5102 ++++++++++++++++--------------- sumfiles/gfortran.log.xz | Bin 1024840 -> 1033044 bytes sumfiles/gfortran.sum | 110 +- sumfiles/libatomic.log.xz | Bin 2288 -> 2292 bytes sumfiles/libatomic.sum | 4 +- sumfiles/libgomp.log.xz | Bin 201892 -> 202180 bytes sumfiles/libgomp.sum | 16 +- sumfiles/libitm.log.xz | Bin 2656 -> 2656 bytes sumfiles/libitm.sum | 6 +- sumfiles/libstdc++.log.xz | Bin 424084 -> 427992 bytes sumfiles/libstdc++.sum | 19 +- 46 files changed, 2940 insertions(+), 3316 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