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 83f268f67 111: onsuccess: #2143: 1: Success after binutils/gcc/linux/gl [...] discards efb2474af 110: onsuccess: #2142: 1: Success after binutils/gcc/glibc/gd [...] discards d88d6ae58 109: onsuccess: #2141: 1: Success after gcc/glibc: 6 commits discards d93c05a4f 108: onsuccess: #2140: 1: Success after binutils/gcc/gdb: 5 commits discards 0987eee3d 107: onsuccess: #2139: 1: Success after binutils/gcc/gdb: 3 commits discards e44a25506 106: onsuccess: #2138: 1: Success after binutils/gcc/glibc/gd [...] discards 58a9e80c9 105: onsuccess: #2137: 1: Success after basepoints/gcc-13-271 [...] discards 1e6cd54f9 104: onsuccess: #2136: 1: Success after binutils/gcc/gdb: 3 commits discards 4d898d903 103: onsuccess: #2135: 1: Success after gcc/linux/glibc/gdb/q [...] discards 4bcd9f261 102: onsuccess: #2133: 1: Success after gdb-12-branchpoint-19 [...] discards 986ea19a6 101: onsuccess: #2130: 1: Success after binutils: 81 commits discards 218e36284 100: onsuccess: #2077: 1: Success after binutils/gcc/linux/gd [...] discards d2e976a3c 99: onsuccess: #2074: 1: Success after baseline build: no new [...] discards d1b48d073 98: onsuccess: #2073: 1: Success after gcc/linux: 11 commits discards c3e9d7a57 97: onsuccess: #2072: 1: Success after binutils/gcc/gdb: 3 commits discards 3952ce803 96: onsuccess: #2071: 1: Success after gcc/linux: 56 commits discards 42476c346 95: onsuccess: #2070: 1: Success after basepoints/gcc-13-2389 [...] discards c0b943914 94: onsuccess: 1: Success after gcc: openmp: Partial OpenMP 5 [...] discards 1c53d9ffa 93: onsuccess: 1: Success after binutils/gcc/linux/gdb: 88 commits discards e67a34fa3 92: onsuccess: 1: Success after binutils/gcc/linux/gdb/qemu: [...] discards e01f5f8d4 91: onsuccess: 1: Success after binutils/gcc/gdb: 8 commits discards 9aeea71db 90: onsuccess: 1: Success after binutils/gcc/gdb: 19 commits discards 76b91940d 89: onsuccess: 1: Success after binutils/gcc/gdb: 5 commits discards e1ca3e484 88: onsuccess: 1: Success after gcc/linux/qemu: 149 commits discards b4cff5625 87: onsuccess: 1: Success after binutils/gcc/gdb: 14 commits discards 85127a184 86: onsuccess: 1: Success after binutils/gcc/gdb: 7 commits discards 2d90a19f0 85: onsuccess: 1: Success after binutils/gcc/glibc/gdb/qemu: [...] discards 99af54616 84: onsuccess: 1: Success after binutils/gcc/linux/gdb: 68 commits discards e75b3e271 83: onsuccess: 1: Success after binutils/gcc/glibc/gdb: 17 commits discards 4e79309fc 82: onsuccess: 1: Successful build after binutils/gcc/gdb: 11 [...] discards c907db4ca 81: onsuccess: 1: Successful build after binutils/gcc/gdb: 6 commits discards 60cc4d2c4 80: onsuccess: 1: Successful build after binutils/gcc/glibc/g [...] discards 6b1b486f2 79: onsuccess: 1: Successful build after binutils/gcc/glibc/g [...] discards 6ca3abf12 78: onsuccess: 1: Successful build after binutils/gcc/gdb: 4 commits discards 9389cd788 77: onsuccess: 1: Successful build after gcc/linux/glibc: 22 commits discards 41821a79b 76: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] discards 047710a83 75: onsuccess: 1: Successful build after linux: 44 commits discards 7f355febc 74: onsuccess: 1: Successful build after binutils/gdb: 2 commits discards 5efba6823 73: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] discards c8be3b384 72: onsuccess: 1: Successful build after linux: 12 commits discards 068eaab05 71: onsuccess: 1: Successful build after gcc/glibc: 3 commits discards 0e9446045 70: onsuccess: 1: Successful build after binutils/gcc/gdb: 4 commits discards 55f2b668a 69: onsuccess: 1: Successful build after binutils/gcc/gdb: 5 commits discards 8311c5bff 68: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] discards e2c395de0 67: onsuccess: 1: Successful build after binutils/gcc/gdb: 10 [...] discards 135ac0367 66: onsuccess: 1: Successful build after gcc/glibc: 10 commits discards e3c6b6567 65: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] discards 1a6081f31 64: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] discards 2a7cdbcfb 63: onsuccess: 1: Successful build after binutils/gcc/gdb: 8 commits discards edcd5486b 62: onsuccess: 1: Successful build after binutils/gcc/gdb: 22 [...] discards c21db4ad8 61: onsuccess: 1: Successful build after binutils/gcc/gdb/qem [...] discards 9cc7e079b 60: onsuccess: 1: Successful build after glibc: 2 commits discards 2b3b72954 59: onsuccess: 1: Successful build after binutils: 2 commits discards 2d4036bac 58: onsuccess: 1: Successful build after binutils: gdb: new ' [...] discards 8e75422a4 57: onsuccess: 1: Successful build after binutils/gcc/glibc/g [...] discards a222f1aad 56: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] discards 0628b15cc 55: onsuccess: 1: Successful build after gcc/linux/glibc/qemu [...] discards 94fa97566 54: onsuccess: 1: Successful build after binutils/gcc/gdb: 8 commits discards 51586a020 53: onsuccess: 1: Successful build after binutils/gcc/gdb: 8 commits discards f50f59897 52: onsuccess: 1: Successful build after binutils/gcc/gdb: 7 commits discards e2eba2e8f 51: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] discards f3b9a0663 50: onsuccess: 1: Successful build after binutils/gcc/glibc/g [...] discards bab98fcc4 49: onsuccess: 1: Successful build after gcc/glibc: 5 commits discards 39e6c5c9c 48: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] discards 47136dcc7 47: onsuccess: 1: Successful build after linux: 10 commits discards e4595e336 46: onsuccess: 1: Successful build after binutils/gdb: 2 commits discards 8e684deee 45: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] discards cd3a11647 44: onsuccess: 1: Successful build after gcc/linux: 35 commits discards 88dae402a 43: onsuccess: 1: Successful build after gcc: LoongArch: Add [...] discards a41b2263c 42: onsuccess: 1: Successful build after gcc: libcpp: Impleme [...] discards c92ea736d 41: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] discards d40935fea 40: onsuccess: 1: Successful build after linux/qemu: 147 commits discards 9b2adb2ef 39: onsuccess: 1: Successful build after binutils/gcc/gdb/qem [...] discards 3ac54a639 38: onsuccess: 1: Successful build after gcc/linux: 95 commits discards 071cb2bbd 37: onsuccess: 1: Successful build after binutils/gcc/glibc/g [...] discards dec1cc71d 36: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] discards 7da3e40bf 35: onsuccess: 1: Successful build after binutils/gcc/glibc/g [...] discards f6d474e28 34: onsuccess: 1: Successful build after binutils/gcc/glibc/g [...] discards 97f4a7e30 33: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] discards abaa9a3f8 32: onsuccess: 1: Successful build after gcc: 7 commits discards cc35a2975 31: onsuccess: 1: Successful build after binutils/gcc/glibc/g [...] discards e98e1f78e 30: onsuccess: 1: Successful build after binutils/gcc/gdb/qem [...] discards 4d90ffa20 29: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] discards 1efc808db 28: onsuccess: 1: Successful build after binutils/gcc/glibc/g [...] discards f24acb4b8 27: onsuccess: 1: Successful build after binutils/gcc/gdb: 25 [...] discards f481e29f8 26: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards 14b4cafaa 25: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards a3b7d2aec 24: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards 7bc174183 23: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards c99c1f9e1 22: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards 0e6416cbc 21: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards c900d104d 20: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards ecb52ce30 19: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards 1c117646a 18: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards 29f2bbc46 17: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards 675d725f3 16: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards 624580fad 15: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards 5fa6d24b0 14: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards 143b3d9f9 13: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards 3f7f53b1c 12: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards ca986dffa 11: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new db66939a6 11: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new 39339671e 12: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new c1c9bec63 13: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new 674b74364 14: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new 5bd40189b 15: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new db44eee92 16: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new 37c15e44b 17: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new 9922de837 18: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new 8f0866864 19: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new 132fedab1 20: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new f5accfabb 21: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new ad374c034 22: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new 3fdc7d0ea 23: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new 834b25ba7 24: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new ae54648fb 25: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new a0fa50e77 26: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new 63fd6f01f 27: onsuccess: 1: Successful build after binutils/gcc/gdb: 25 [...] new 2647743d6 28: onsuccess: 1: Successful build after binutils/gcc/glibc/g [...] new 77a645721 29: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] new 06a51fd5f 30: onsuccess: 1: Successful build after binutils/gcc/gdb/qem [...] new e20ceb88e 31: onsuccess: 1: Successful build after binutils/gcc/glibc/g [...] new 38afbc216 32: onsuccess: 1: Successful build after gcc: 7 commits new c3608ce1e 33: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] new d8889d252 34: onsuccess: 1: Successful build after binutils/gcc/glibc/g [...] new 06e10dba8 35: onsuccess: 1: Successful build after binutils/gcc/glibc/g [...] new 4a049d325 36: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] new f144fc978 37: onsuccess: 1: Successful build after binutils/gcc/glibc/g [...] new e0686e370 38: onsuccess: 1: Successful build after gcc/linux: 95 commits new 586f6f6ac 39: onsuccess: 1: Successful build after binutils/gcc/gdb/qem [...] new 0adf98e65 40: onsuccess: 1: Successful build after linux/qemu: 147 commits new 6d8056f60 41: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] new e8b88e490 42: onsuccess: 1: Successful build after gcc: libcpp: Impleme [...] new 41b054a22 43: onsuccess: 1: Successful build after gcc: LoongArch: Add [...] new 6a2327642 44: onsuccess: 1: Successful build after gcc/linux: 35 commits new 1142b6096 45: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] new c6fc943fc 46: onsuccess: 1: Successful build after binutils/gdb: 2 commits new 21a30877c 47: onsuccess: 1: Successful build after linux: 10 commits new b7186f5e7 48: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] new cab810651 49: onsuccess: 1: Successful build after gcc/glibc: 5 commits new 96572a485 50: onsuccess: 1: Successful build after binutils/gcc/glibc/g [...] new e3a690405 51: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] new bc53bc630 52: onsuccess: 1: Successful build after binutils/gcc/gdb: 7 commits new db8c4c863 53: onsuccess: 1: Successful build after binutils/gcc/gdb: 8 commits new a828b55c1 54: onsuccess: 1: Successful build after binutils/gcc/gdb: 8 commits new aa01cc0ca 55: onsuccess: 1: Successful build after gcc/linux/glibc/qemu [...] new 775a44fa3 56: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] new c1abdb267 57: onsuccess: 1: Successful build after binutils/gcc/glibc/g [...] new 618e3d8e0 58: onsuccess: 1: Successful build after binutils: gdb: new ' [...] new c698ccbd8 59: onsuccess: 1: Successful build after binutils: 2 commits new f42c7bbb5 60: onsuccess: 1: Successful build after glibc: 2 commits new a68f0fa78 61: onsuccess: 1: Successful build after binutils/gcc/gdb/qem [...] new d06b222c2 62: onsuccess: 1: Successful build after binutils/gcc/gdb: 22 [...] new 586f07ba0 63: onsuccess: 1: Successful build after binutils/gcc/gdb: 8 commits new b6644be1c 64: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] new 9515cae6c 65: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] new b4a3fac70 66: onsuccess: 1: Successful build after gcc/glibc: 10 commits new 9acd549d9 67: onsuccess: 1: Successful build after binutils/gcc/gdb: 10 [...] new 2c4641bd1 68: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] new 7c4891b53 69: onsuccess: 1: Successful build after binutils/gcc/gdb: 5 commits new aaa96f856 70: onsuccess: 1: Successful build after binutils/gcc/gdb: 4 commits new 7c0fcb4b7 71: onsuccess: 1: Successful build after gcc/glibc: 3 commits new 9c98b1d1a 72: onsuccess: 1: Successful build after linux: 12 commits new 4338679e4 73: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] new 2c784794b 74: onsuccess: 1: Successful build after binutils/gdb: 2 commits new 1df35e12b 75: onsuccess: 1: Successful build after linux: 44 commits new fc2598cba 76: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] new 50912fd46 77: onsuccess: 1: Successful build after gcc/linux/glibc: 22 commits new 316602853 78: onsuccess: 1: Successful build after binutils/gcc/gdb: 4 commits new 5664e56e1 79: onsuccess: 1: Successful build after binutils/gcc/glibc/g [...] new 660da9b56 80: onsuccess: 1: Successful build after binutils/gcc/glibc/g [...] new db14ea16e 81: onsuccess: 1: Successful build after binutils/gcc/gdb: 6 commits new f4740634c 82: onsuccess: 1: Successful build after binutils/gcc/gdb: 11 [...] new 34e8c1386 83: onsuccess: 1: Success after binutils/gcc/glibc/gdb: 17 commits new 7e4fa19aa 84: onsuccess: 1: Success after binutils/gcc/linux/gdb: 68 commits new 741cf3d87 85: onsuccess: 1: Success after binutils/gcc/glibc/gdb/qemu: [...] new 32d6d49e0 86: onsuccess: 1: Success after binutils/gcc/gdb: 7 commits new 1878b7f75 87: onsuccess: 1: Success after binutils/gcc/gdb: 14 commits new 9086f63c2 88: onsuccess: 1: Success after gcc/linux/qemu: 149 commits new 0549e0abb 89: onsuccess: 1: Success after binutils/gcc/gdb: 5 commits new e22df442d 90: onsuccess: 1: Success after binutils/gcc/gdb: 19 commits new 35b4657f6 91: onsuccess: 1: Success after binutils/gcc/gdb: 8 commits new 1bb356551 92: onsuccess: 1: Success after binutils/gcc/linux/gdb/qemu: [...] new b173cd758 93: onsuccess: 1: Success after binutils/gcc/linux/gdb: 88 commits new e16bb40eb 94: onsuccess: 1: Success after gcc: openmp: Partial OpenMP 5 [...] new 3a6dce358 95: onsuccess: #2070: 1: Success after basepoints/gcc-13-2389 [...] new 8f6e73787 96: onsuccess: #2071: 1: Success after gcc/linux: 56 commits new 8f4ff3a3b 97: onsuccess: #2072: 1: Success after binutils/gcc/gdb: 3 commits new be6625f24 98: onsuccess: #2073: 1: Success after gcc/linux: 11 commits new d953fd9fb 99: onsuccess: #2074: 1: Success after baseline build: no new [...] new 3839bd840 100: onsuccess: #2077: 1: Success after binutils/gcc/linux/gd [...] new 4a47e8326 101: onsuccess: #2130: 1: Success after binutils: 81 commits new d74fb0c3d 102: onsuccess: #2133: 1: Success after gdb-12-branchpoint-19 [...] new 712ef0fa0 103: onsuccess: #2135: 1: Success after gcc/linux/glibc/gdb/q [...] new 7b4659897 104: onsuccess: #2136: 1: Success after binutils/gcc/gdb: 3 commits new da26c4225 105: onsuccess: #2137: 1: Success after basepoints/gcc-13-271 [...] new 74e750a25 106: onsuccess: #2138: 1: Success after binutils/gcc/glibc/gd [...] new c4bb930f5 107: onsuccess: #2139: 1: Success after binutils/gcc/gdb: 3 commits new 3ef2e50ed 108: onsuccess: #2140: 1: Success after binutils/gcc/gdb: 5 commits new 2629127df 109: onsuccess: #2141: 1: Success after gcc/glibc: 6 commits new ac027a537 110: onsuccess: #2142: 1: Success after binutils/gcc/glibc/gd [...] new 0bbd5931e 111: onsuccess: #2143: 1: Success after binutils/gcc/linux/gl [...] new 962710cd0 112: onsuccess: #2144: 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 (83f268f67) \ 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 1696 -> 1756 bytes 02-prepare_abe/console.log.xz | Bin 2752 -> 2740 bytes 03-build_abe-binutils/console.log.xz | Bin 30240 -> 30060 bytes 04-build_abe-stage1/console.log.xz | Bin 72400 -> 72140 bytes 05-clean_sysroot/console.log.xz | Bin 328 -> 328 bytes 06-build_abe-linux/console.log.xz | Bin 8604 -> 8628 bytes 07-build_abe-glibc/console.log.xz | Bin 239816 -> 239952 bytes 08-build_abe-stage2/console.log.xz | Bin 203388 -> 202296 bytes 09-build_abe-gdb/console.log.xz | Bin 37336 -> 37392 bytes 10-build_abe-qemu/console.log.xz | Bin 31340 -> 31180 bytes 11-build_abe-dejagnu/console.log.xz | Bin 3884 -> 3880 bytes 12-build_abe-check_gcc/console.log.xz | Bin 2604 -> 2452 bytes 13-check_regression/console.log.xz | Bin 6368 -> 5312 bytes 13-check_regression/extra-bisect-params | 1 + 13-check_regression/fails.sum | 7 + 13-check_regression/mail-body.txt | 112 +- 13-check_regression/results.compare | 38 +- 13-check_regression/results.compare2 | 76 +- 13-check_regression/results.regressions | 27 + 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 | 114 +- mail/mail-subject.txt | 2 +- manifest.sh | 36 +- results | 27 + sumfiles/g++.log.xz | Bin 3423984 -> 3428868 bytes sumfiles/g++.sum | 233 +- sumfiles/gcc.log.xz | Bin 3008684 -> 3005388 bytes sumfiles/gcc.sum | 5150 +++++++++++++++---------------- sumfiles/gfortran.log.xz | Bin 1033044 -> 1028812 bytes sumfiles/gfortran.sum | 51 +- sumfiles/libatomic.log.xz | Bin 2292 -> 2296 bytes sumfiles/libatomic.sum | 4 +- sumfiles/libgomp.log.xz | Bin 202180 -> 201956 bytes sumfiles/libgomp.sum | 16 +- sumfiles/libitm.log.xz | Bin 2656 -> 2656 bytes sumfiles/libitm.sum | 6 +- sumfiles/libstdc++.log.xz | Bin 427992 -> 426316 bytes sumfiles/libstdc++.sum | 14 +- 44 files changed, 2963 insertions(+), 3033 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