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 c467df3e2 102: onsuccess: #2133: 1: Success after gdb-12-branchpoint-19 [...] discards b63c242d5 101: onsuccess: #2130: 1: Success after binutils: 81 commits discards 58c991731 100: onsuccess: #2077: 1: Success after binutils/gcc/linux/gd [...] discards b7f2ac6f2 99: onsuccess: #2074: 1: Success after baseline build: no new [...] discards d08229a95 98: onsuccess: #2073: 1: Success after gcc/linux: 11 commits discards 5fd1bd3ff 97: onsuccess: #2072: 1: Success after binutils/gcc/gdb: 3 commits discards 0586da351 96: onsuccess: #2071: 1: Success after gcc/linux: 56 commits discards a938fbccc 95: onsuccess: #2070: 1: Success after basepoints/gcc-13-2389 [...] discards 186a0940e 94: onsuccess: 1: Success after gcc: openmp: Partial OpenMP 5 [...] discards c3c0b2b74 93: onsuccess: 1: Success after binutils/gcc/linux/gdb: 88 commits discards 9935e89aa 92: onsuccess: 1: Success after binutils/gcc/linux/gdb/qemu: [...] discards 09d63a244 91: onsuccess: 1: Success after binutils/gcc/gdb: 8 commits discards 05502f703 90: onsuccess: 1: Success after binutils/gcc/gdb: 19 commits discards 80af09fac 89: onsuccess: 1: Success after binutils/gcc/gdb: 5 commits discards 221a6f716 88: onsuccess: 1: Success after gcc/linux/qemu: 149 commits discards 11532411c 87: onsuccess: 1: Success after binutils/gcc/gdb: 14 commits discards 13310567d 86: onsuccess: 1: Success after binutils/gcc/gdb: 7 commits discards a141eb1a9 85: onsuccess: 1: Success after binutils/gcc/glibc/gdb/qemu: [...] discards 8397d403f 84: onsuccess: 1: Success after binutils/gcc/linux/gdb: 68 commits discards da37e2b16 83: onsuccess: 1: Success after binutils/gcc/glibc/gdb: 17 commits discards c003b305d 82: onsuccess: 1: Successful build after binutils/gcc/gdb: 11 [...] discards 9c469cbcd 81: onsuccess: 1: Successful build after binutils/gcc/gdb: 6 commits discards 8de2e1476 80: onsuccess: 1: Successful build after binutils/gcc/glibc/g [...] discards 2e4996f48 79: onsuccess: 1: Successful build after binutils/gcc/glibc/g [...] discards 5ea1f7cb4 78: onsuccess: 1: Successful build after binutils/gcc/gdb: 4 commits discards 4ccea2e96 77: onsuccess: 1: Successful build after gcc/linux/glibc: 22 commits discards 03268e289 76: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] discards 1a745425e 75: onsuccess: 1: Successful build after linux: 44 commits discards 740b5bc5a 74: onsuccess: 1: Successful build after binutils/gdb: 2 commits discards 052ec8381 73: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] discards b11988902 72: onsuccess: 1: Successful build after linux: 12 commits discards 3ccaf6a22 71: onsuccess: 1: Successful build after gcc/glibc: 3 commits discards 8c6affd01 70: onsuccess: 1: Successful build after binutils/gcc/gdb: 4 commits discards 5c5dfa0b4 69: onsuccess: 1: Successful build after binutils/gcc/gdb: 5 commits discards 2e9bb0602 68: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] discards 5fe07b29b 67: onsuccess: 1: Successful build after binutils/gcc/gdb: 10 [...] discards 38d34f15a 66: onsuccess: 1: Successful build after gcc/glibc: 10 commits discards cca5ece86 65: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] discards 282317fb0 64: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] discards 4b57b2073 63: onsuccess: 1: Successful build after binutils/gcc/gdb: 8 commits discards 6665a543d 62: onsuccess: 1: Successful build after binutils/gcc/gdb: 22 [...] discards d0c1d10a6 61: onsuccess: 1: Successful build after binutils/gcc/gdb/qem [...] discards d9acc583c 60: onsuccess: 1: Successful build after glibc: 2 commits discards 68c830ba5 59: onsuccess: 1: Successful build after binutils: 2 commits discards 829442fe0 58: onsuccess: 1: Successful build after binutils: gdb: new ' [...] discards 481051845 57: onsuccess: 1: Successful build after binutils/gcc/glibc/g [...] discards 475526cfa 56: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] discards 9f204a4b3 55: onsuccess: 1: Successful build after gcc/linux/glibc/qemu [...] discards 05493529d 54: onsuccess: 1: Successful build after binutils/gcc/gdb: 8 commits discards 703a744ad 53: onsuccess: 1: Successful build after binutils/gcc/gdb: 8 commits discards 5a3cc6558 52: onsuccess: 1: Successful build after binutils/gcc/gdb: 7 commits discards f658ba8e4 51: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] discards de41114a5 50: onsuccess: 1: Successful build after binutils/gcc/glibc/g [...] discards 833b645c8 49: onsuccess: 1: Successful build after gcc/glibc: 5 commits discards fae3ab234 48: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] discards 28068461d 47: onsuccess: 1: Successful build after linux: 10 commits discards cf99878fd 46: onsuccess: 1: Successful build after binutils/gdb: 2 commits discards a6a299a0e 45: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] discards c158d6e12 44: onsuccess: 1: Successful build after gcc/linux: 35 commits discards 5609d411b 43: onsuccess: 1: Successful build after gcc: LoongArch: Add [...] discards ab6c96d19 42: onsuccess: 1: Successful build after gcc: libcpp: Impleme [...] discards 10758ea5a 41: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] discards a51ee3ef6 40: onsuccess: 1: Successful build after linux/qemu: 147 commits discards 2eb0ae4aa 39: onsuccess: 1: Successful build after binutils/gcc/gdb/qem [...] discards 284313757 38: onsuccess: 1: Successful build after gcc/linux: 95 commits discards 813d359d7 37: onsuccess: 1: Successful build after binutils/gcc/glibc/g [...] discards d80b8f981 36: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] discards 76d0518cc 35: onsuccess: 1: Successful build after binutils/gcc/glibc/g [...] discards e4397607b 34: onsuccess: 1: Successful build after binutils/gcc/glibc/g [...] discards 9a324ea2e 33: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] discards 5bf3388f9 32: onsuccess: 1: Successful build after gcc: 7 commits discards 703f7e2f7 31: onsuccess: 1: Successful build after binutils/gcc/glibc/g [...] discards 86c0b51ea 30: onsuccess: 1: Successful build after binutils/gcc/gdb/qem [...] discards bea70fa04 29: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] discards 7ad4b117c 28: onsuccess: 1: Successful build after binutils/gcc/glibc/g [...] discards 4d6777338 27: onsuccess: 1: Successful build after binutils/gcc/gdb: 25 [...] discards dde4a1626 26: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards 039cff954 25: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards 2cf51b80f 24: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards af9f3a483 23: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards f7ff8218f 22: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards cdca181ff 21: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards f7f36b4e3 20: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards b1360c592 19: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards b0954e98b 18: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards 9ab0e8e0d 17: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards 7c91225bf 16: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards 7a589388c 15: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards 6e52d4ec4 14: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards 89a5e27da 13: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards 431c4e17b 12: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards 8aaa5160a 11: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards 088d9f54a 10: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards 78580e81a 9: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards 3a9bf755a 8: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards 3255aeaf2 7: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards 5761bd014 6: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards a367e6c6a 5: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards f75e51221 4: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards 5a4f58c00 3: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards 9f6f5409b 2: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new 8d4f71151 2: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new ca024b3ab 3: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new 061acf35c 4: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new c331224c5 5: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new a3c728d6d 6: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new e8be065ee 7: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new ce31b3eed 8: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new 1a5b69745 9: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new 89cbdd8a6 10: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new a29d87ee5 11: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new 474e67f8e 12: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new 20bb34feb 13: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new 313b81388 14: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new 6ea58bef6 15: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new a693f15ef 16: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new 787218674 17: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new 60813fb8e 18: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new 01d98662b 19: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new 08c1c4a38 20: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new 9449998ba 21: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new 1c9a5a0fa 22: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new c8fed8105 23: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new 415eae2cc 24: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new 0343e3ab6 25: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new 87d796a3e 26: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new a366573b8 27: onsuccess: 1: Successful build after binutils/gcc/gdb: 25 [...] new f0e98c29b 28: onsuccess: 1: Successful build after binutils/gcc/glibc/g [...] new 57b380d8a 29: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] new 1a165f5fd 30: onsuccess: 1: Successful build after binutils/gcc/gdb/qem [...] new f99df773f 31: onsuccess: 1: Successful build after binutils/gcc/glibc/g [...] new 22639cf93 32: onsuccess: 1: Successful build after gcc: 7 commits new f8d8aae87 33: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] new 373149645 34: onsuccess: 1: Successful build after binutils/gcc/glibc/g [...] new cbb568e74 35: onsuccess: 1: Successful build after binutils/gcc/glibc/g [...] new 09d700033 36: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] new 021f51014 37: onsuccess: 1: Successful build after binutils/gcc/glibc/g [...] new 00a7329c3 38: onsuccess: 1: Successful build after gcc/linux: 95 commits new 3d094517f 39: onsuccess: 1: Successful build after binutils/gcc/gdb/qem [...] new e0de59c0b 40: onsuccess: 1: Successful build after linux/qemu: 147 commits new 0249ee9d7 41: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] new 838af840a 42: onsuccess: 1: Successful build after gcc: libcpp: Impleme [...] new debef6b06 43: onsuccess: 1: Successful build after gcc: LoongArch: Add [...] new 170036e05 44: onsuccess: 1: Successful build after gcc/linux: 35 commits new 661df44fc 45: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] new c67e1511f 46: onsuccess: 1: Successful build after binutils/gdb: 2 commits new afedf4105 47: onsuccess: 1: Successful build after linux: 10 commits new 9e8c9393e 48: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] new 3214cc83f 49: onsuccess: 1: Successful build after gcc/glibc: 5 commits new 911bad054 50: onsuccess: 1: Successful build after binutils/gcc/glibc/g [...] new 9bab00580 51: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] new 96611400f 52: onsuccess: 1: Successful build after binutils/gcc/gdb: 7 commits new a8ef31b71 53: onsuccess: 1: Successful build after binutils/gcc/gdb: 8 commits new 576fedde5 54: onsuccess: 1: Successful build after binutils/gcc/gdb: 8 commits new 417e17ed6 55: onsuccess: 1: Successful build after gcc/linux/glibc/qemu [...] new ffd0c461c 56: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] new f3ad78604 57: onsuccess: 1: Successful build after binutils/gcc/glibc/g [...] new d07e6e2b3 58: onsuccess: 1: Successful build after binutils: gdb: new ' [...] new d958dfd0c 59: onsuccess: 1: Successful build after binutils: 2 commits new 6d70c6675 60: onsuccess: 1: Successful build after glibc: 2 commits new bb4c5d4f1 61: onsuccess: 1: Successful build after binutils/gcc/gdb/qem [...] new ddb1e6ce1 62: onsuccess: 1: Successful build after binutils/gcc/gdb: 22 [...] new 2e6886ee3 63: onsuccess: 1: Successful build after binutils/gcc/gdb: 8 commits new f2f8a82de 64: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] new 5de7e53b3 65: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] new e9e7e3e70 66: onsuccess: 1: Successful build after gcc/glibc: 10 commits new 201dff655 67: onsuccess: 1: Successful build after binutils/gcc/gdb: 10 [...] new 0e949275e 68: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] new 4d99fad60 69: onsuccess: 1: Successful build after binutils/gcc/gdb: 5 commits new e6cc9db0c 70: onsuccess: 1: Successful build after binutils/gcc/gdb: 4 commits new 300e0227f 71: onsuccess: 1: Successful build after gcc/glibc: 3 commits new 5fe6fe313 72: onsuccess: 1: Successful build after linux: 12 commits new 449b82e99 73: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] new dcd80d2a3 74: onsuccess: 1: Successful build after binutils/gdb: 2 commits new 0e5e4a608 75: onsuccess: 1: Successful build after linux: 44 commits new e8a32442c 76: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] new b8b8bea79 77: onsuccess: 1: Successful build after gcc/linux/glibc: 22 commits new d490393d9 78: onsuccess: 1: Successful build after binutils/gcc/gdb: 4 commits new a718bb85f 79: onsuccess: 1: Successful build after binutils/gcc/glibc/g [...] new f48d50771 80: onsuccess: 1: Successful build after binutils/gcc/glibc/g [...] new 80decc75c 81: onsuccess: 1: Successful build after binutils/gcc/gdb: 6 commits new 614483bb3 82: onsuccess: 1: Successful build after binutils/gcc/gdb: 11 [...] new 42c74bb19 83: onsuccess: 1: Success after binutils/gcc/glibc/gdb: 17 commits new 74283a3de 84: onsuccess: 1: Success after binutils/gcc/linux/gdb: 68 commits new 0e643ea36 85: onsuccess: 1: Success after binutils/gcc/glibc/gdb/qemu: [...] new 24e04ba27 86: onsuccess: 1: Success after binutils/gcc/gdb: 7 commits new 5be5bda38 87: onsuccess: 1: Success after binutils/gcc/gdb: 14 commits new a08df9764 88: onsuccess: 1: Success after gcc/linux/qemu: 149 commits new e266fc4b2 89: onsuccess: 1: Success after binutils/gcc/gdb: 5 commits new 5afd8b192 90: onsuccess: 1: Success after binutils/gcc/gdb: 19 commits new 81e9cb1ba 91: onsuccess: 1: Success after binutils/gcc/gdb: 8 commits new c15f41d4a 92: onsuccess: 1: Success after binutils/gcc/linux/gdb/qemu: [...] new ec54b3dbd 93: onsuccess: 1: Success after binutils/gcc/linux/gdb: 88 commits new 3d407e0d0 94: onsuccess: 1: Success after gcc: openmp: Partial OpenMP 5 [...] new b74950f05 95: onsuccess: #2070: 1: Success after basepoints/gcc-13-2389 [...] new 71876e358 96: onsuccess: #2071: 1: Success after gcc/linux: 56 commits new 8f613d3cb 97: onsuccess: #2072: 1: Success after binutils/gcc/gdb: 3 commits new 08cdebf0b 98: onsuccess: #2073: 1: Success after gcc/linux: 11 commits new afc93de53 99: onsuccess: #2074: 1: Success after baseline build: no new [...] new d18d8a05c 100: onsuccess: #2077: 1: Success after binutils/gcc/linux/gd [...] new 5a6aa92ce 101: onsuccess: #2130: 1: Success after binutils: 81 commits new f817ee633 102: onsuccess: #2133: 1: Success after gdb-12-branchpoint-19 [...] new 76fed31d3 103: onsuccess: #2135: 1: Success after gcc/linux/glibc/gdb/q [...]
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 (c467df3e2) \ 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 2736 -> 2748 bytes 03-build_abe-binutils/console.log.xz | Bin 30116 -> 30280 bytes 04-build_abe-stage1/console.log.xz | Bin 73408 -> 72488 bytes 05-clean_sysroot/console.log.xz | Bin 328 -> 328 bytes 06-build_abe-linux/console.log.xz | Bin 8472 -> 8284 bytes 07-build_abe-glibc/console.log.xz | Bin 239744 -> 239628 bytes 08-build_abe-stage2/console.log.xz | Bin 203960 -> 202560 bytes 09-build_abe-gdb/console.log.xz | Bin 37512 -> 37404 bytes 10-build_abe-qemu/console.log.xz | Bin 31900 -> 31684 bytes 11-build_abe-dejagnu/console.log.xz | Bin 3876 -> 3884 bytes 12-build_abe-check_gcc/console.log.xz | Bin 3464 -> 2896 bytes 13-check_regression/console.log.xz | Bin 3844 -> 14464 bytes 13-check_regression/extra-bisect-params | 1 + 13-check_regression/fails.sum | 45 + 13-check_regression/mail-body.txt | 105 +- 13-check_regression/results.compare | 77 +- 13-check_regression/results.compare2 | 1518 +++++++- 13-check_regression/results.regressions | 79 + 14-update_baseline/console.log | 64 +- dashboard/dashboard-generate.sh | 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 | 107 +- mail/mail-subject.txt | 2 +- manifest.sh | 37 +- results | 79 + sumfiles/g++.log.xz | Bin 3403724 -> 3413852 bytes sumfiles/g++.sum | 916 +++-- sumfiles/gcc.log.xz | Bin 3005912 -> 3002024 bytes sumfiles/gcc.sum | 6215 +++++++++++++++++-------------- sumfiles/gfortran.log.xz | Bin 1026720 -> 1021956 bytes sumfiles/gfortran.sum | 101 +- sumfiles/libatomic.log.xz | Bin 2288 -> 2292 bytes sumfiles/libatomic.sum | 4 +- sumfiles/libgomp.log.xz | Bin 200664 -> 202032 bytes sumfiles/libgomp.sum | 70 +- sumfiles/libitm.log.xz | Bin 2656 -> 2660 bytes sumfiles/libitm.sum | 6 +- sumfiles/libstdc++.log.xz | Bin 418796 -> 415632 bytes sumfiles/libstdc++.sum | 48 +- 45 files changed, 6170 insertions(+), 3318 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