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 76fed31d3d 103: onsuccess: #2135: 1: Success after gcc/linux/glibc/gdb/ [...] discards f817ee6337 102: onsuccess: #2133: 1: Success after gdb-12-branchpoint-1 [...] discards 5a6aa92cea 101: onsuccess: #2130: 1: Success after binutils: 81 commits discards d18d8a05cd 100: onsuccess: #2077: 1: Success after binutils/gcc/linux/g [...] discards afc93de53d 99: onsuccess: #2074: 1: Success after baseline build: no ne [...] discards 08cdebf0bd 98: onsuccess: #2073: 1: Success after gcc/linux: 11 commits discards 8f613d3cbe 97: onsuccess: #2072: 1: Success after binutils/gcc/gdb: 3 commits discards 71876e3583 96: onsuccess: #2071: 1: Success after gcc/linux: 56 commits discards b74950f054 95: onsuccess: #2070: 1: Success after basepoints/gcc-13-238 [...] discards 3d407e0d0a 94: onsuccess: 1: Success after gcc: openmp: Partial OpenMP [...] discards ec54b3dbda 93: onsuccess: 1: Success after binutils/gcc/linux/gdb: 88 commits discards c15f41d4ac 92: onsuccess: 1: Success after binutils/gcc/linux/gdb/qemu: [...] discards 81e9cb1baa 91: onsuccess: 1: Success after binutils/gcc/gdb: 8 commits discards 5afd8b192a 90: onsuccess: 1: Success after binutils/gcc/gdb: 19 commits discards e266fc4b29 89: onsuccess: 1: Success after binutils/gcc/gdb: 5 commits discards a08df9764a 88: onsuccess: 1: Success after gcc/linux/qemu: 149 commits discards 5be5bda38b 87: onsuccess: 1: Success after binutils/gcc/gdb: 14 commits discards 24e04ba27e 86: onsuccess: 1: Success after binutils/gcc/gdb: 7 commits discards 0e643ea362 85: onsuccess: 1: Success after binutils/gcc/glibc/gdb/qemu: [...] discards 74283a3de3 84: onsuccess: 1: Success after binutils/gcc/linux/gdb: 68 commits discards 42c74bb196 83: onsuccess: 1: Success after binutils/gcc/glibc/gdb: 17 commits discards 614483bb34 82: onsuccess: 1: Successful build after binutils/gcc/gdb: 1 [...] discards 80decc75c5 81: onsuccess: 1: Successful build after binutils/gcc/gdb: 6 [...] discards f48d50771e 80: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] discards a718bb85f2 79: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] discards d490393d90 78: onsuccess: 1: Successful build after binutils/gcc/gdb: 4 [...] discards b8b8bea798 77: onsuccess: 1: Successful build after gcc/linux/glibc: 22 [...] discards e8a32442c1 76: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 0e5e4a6086 75: onsuccess: 1: Successful build after linux: 44 commits discards dcd80d2a35 74: onsuccess: 1: Successful build after binutils/gdb: 2 commits discards 449b82e99d 73: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 5fe6fe3136 72: onsuccess: 1: Successful build after linux: 12 commits discards 300e0227fd 71: onsuccess: 1: Successful build after gcc/glibc: 3 commits discards e6cc9db0c9 70: onsuccess: 1: Successful build after binutils/gcc/gdb: 4 [...] discards 4d99fad60a 69: onsuccess: 1: Successful build after binutils/gcc/gdb: 5 [...] discards 0e949275e4 68: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 201dff655c 67: onsuccess: 1: Successful build after binutils/gcc/gdb: 1 [...] discards e9e7e3e70d 66: onsuccess: 1: Successful build after gcc/glibc: 10 commits discards 5de7e53b3e 65: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards f2f8a82de5 64: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 2e6886ee38 63: onsuccess: 1: Successful build after binutils/gcc/gdb: 8 [...] discards ddb1e6ce18 62: onsuccess: 1: Successful build after binutils/gcc/gdb: 2 [...] discards bb4c5d4f1a 61: onsuccess: 1: Successful build after binutils/gcc/gdb/qe [...] discards 6d70c66755 60: onsuccess: 1: Successful build after glibc: 2 commits discards d958dfd0c4 59: onsuccess: 1: Successful build after binutils: 2 commits discards d07e6e2b3c 58: onsuccess: 1: Successful build after binutils: gdb: new [...] discards f3ad78604f 57: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] discards ffd0c461c5 56: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 417e17ed64 55: onsuccess: 1: Successful build after gcc/linux/glibc/qem [...] discards 576fedde59 54: onsuccess: 1: Successful build after binutils/gcc/gdb: 8 [...] discards a8ef31b71c 53: onsuccess: 1: Successful build after binutils/gcc/gdb: 8 [...] discards 96611400f9 52: onsuccess: 1: Successful build after binutils/gcc/gdb: 7 [...] discards 9bab00580a 51: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 911bad054a 50: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] discards 3214cc83fc 49: onsuccess: 1: Successful build after gcc/glibc: 5 commits discards 9e8c9393e2 48: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards afedf4105e 47: onsuccess: 1: Successful build after linux: 10 commits discards c67e1511f5 46: onsuccess: 1: Successful build after binutils/gdb: 2 commits discards 661df44fcb 45: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 170036e054 44: onsuccess: 1: Successful build after gcc/linux: 35 commits discards debef6b061 43: onsuccess: 1: Successful build after gcc: LoongArch: Add [...] discards 838af840a1 42: onsuccess: 1: Successful build after gcc: libcpp: Implem [...] discards 0249ee9d76 41: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards e0de59c0b1 40: onsuccess: 1: Successful build after linux/qemu: 147 commits discards 3d094517fc 39: onsuccess: 1: Successful build after binutils/gcc/gdb/qe [...] discards 00a7329c36 38: onsuccess: 1: Successful build after gcc/linux: 95 commits discards 021f510149 37: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] discards 09d700033b 36: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards cbb568e746 35: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] discards 373149645a 34: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] discards f8d8aae870 33: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 22639cf936 32: onsuccess: 1: Successful build after gcc: 7 commits discards f99df773f4 31: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] discards 1a165f5fda 30: onsuccess: 1: Successful build after binutils/gcc/gdb/qe [...] discards 57b380d8aa 29: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards f0e98c29bf 28: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] discards a366573b83 27: onsuccess: 1: Successful build after binutils/gcc/gdb: 2 [...] discards 87d796a3e3 26: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards 0343e3ab63 25: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards 415eae2cc6 24: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards c8fed81058 23: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards 1c9a5a0fa6 22: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards 9449998bab 21: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards 08c1c4a38a 20: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards 01d98662bf 19: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards 60813fb8ea 18: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards 7872186741 17: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards a693f15efa 16: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards 6ea58bef60 15: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards 313b81388d 14: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards 20bb34febc 13: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards 474e67f8e8 12: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards a29d87ee53 11: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards 89cbdd8a68 10: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards 1a5b69745e 9: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards ce31b3eed9 8: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards e8be065ee5 7: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards a3c728d6dd 6: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards c331224c59 5: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards 061acf35c8 4: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards ca024b3ab8 3: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new 2150e17a87 3: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new ae0005f6be 4: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new 3545f76cc0 5: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new 9271d7c22f 6: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new 102b1edb89 7: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new 63e6ed3cf0 8: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new 30a185d5c9 9: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new 5179317be8 10: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new 5c4c94a0c7 11: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new 5f6b456f7f 12: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new a70e0f2b63 13: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new a68fbd038b 14: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new fabe8a83ac 15: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new 922abae4a2 16: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new 5ef25e911f 17: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new 1f577d4cea 18: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new 3e3eeed126 19: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new 0e328036f1 20: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new 4ba8eadb10 21: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new 34dd89cc0d 22: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new a04050b6f2 23: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new ecf20ed80b 24: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new e4f2bf8d42 25: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new 50c59327a1 26: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new fd209840ed 27: onsuccess: 1: Successful build after binutils/gcc/gdb: 2 [...] new 052f5163e2 28: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] new 806380c91e 29: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 934a77c510 30: onsuccess: 1: Successful build after binutils/gcc/gdb/qe [...] new 691f4220a8 31: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] new 458780e136 32: onsuccess: 1: Successful build after gcc: 7 commits new cc1ecba6d7 33: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 73fd346cfc 34: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] new 020b4997c4 35: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] new a6c7516ecb 36: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 527338c674 37: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] new 1047f41699 38: onsuccess: 1: Successful build after gcc/linux: 95 commits new 7e853c0ac2 39: onsuccess: 1: Successful build after binutils/gcc/gdb/qe [...] new 93938e2582 40: onsuccess: 1: Successful build after linux/qemu: 147 commits new cea48ee304 41: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 6a16f012d8 42: onsuccess: 1: Successful build after gcc: libcpp: Implem [...] new 14fb7966da 43: onsuccess: 1: Successful build after gcc: LoongArch: Add [...] new 875e5092bc 44: onsuccess: 1: Successful build after gcc/linux: 35 commits new ae6124db37 45: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new fde66caa19 46: onsuccess: 1: Successful build after binutils/gdb: 2 commits new a4c7d7203b 47: onsuccess: 1: Successful build after linux: 10 commits new 85ecc4b47d 48: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 574106f368 49: onsuccess: 1: Successful build after gcc/glibc: 5 commits new a9b3a9178e 50: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] new 690ba621c7 51: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 10a055d9fa 52: onsuccess: 1: Successful build after binutils/gcc/gdb: 7 [...] new 91db0876a1 53: onsuccess: 1: Successful build after binutils/gcc/gdb: 8 [...] new 5b6dc2bfd1 54: onsuccess: 1: Successful build after binutils/gcc/gdb: 8 [...] new d5c46b1088 55: onsuccess: 1: Successful build after gcc/linux/glibc/qem [...] new d6db006c44 56: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 3f42e8ff3a 57: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] new f7b839d818 58: onsuccess: 1: Successful build after binutils: gdb: new [...] new 10d7aac36f 59: onsuccess: 1: Successful build after binutils: 2 commits new bf9aa60dae 60: onsuccess: 1: Successful build after glibc: 2 commits new f86495a552 61: onsuccess: 1: Successful build after binutils/gcc/gdb/qe [...] new 32221aeb0d 62: onsuccess: 1: Successful build after binutils/gcc/gdb: 2 [...] new e4881a00bb 63: onsuccess: 1: Successful build after binutils/gcc/gdb: 8 [...] new c0ace55024 64: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new e018518dbe 65: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 6430c03fc5 66: onsuccess: 1: Successful build after gcc/glibc: 10 commits new d956fd0831 67: onsuccess: 1: Successful build after binutils/gcc/gdb: 1 [...] new 7b992426fe 68: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new c9731fe4b9 69: onsuccess: 1: Successful build after binutils/gcc/gdb: 5 [...] new a55f3ec615 70: onsuccess: 1: Successful build after binutils/gcc/gdb: 4 [...] new 0fc0b2da5e 71: onsuccess: 1: Successful build after gcc/glibc: 3 commits new 5f4aeecd5e 72: onsuccess: 1: Successful build after linux: 12 commits new 3208ac0ef2 73: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 0e05460e55 74: onsuccess: 1: Successful build after binutils/gdb: 2 commits new eb32b86bd5 75: onsuccess: 1: Successful build after linux: 44 commits new d2b3aa78e5 76: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 0bc0588e82 77: onsuccess: 1: Successful build after gcc/linux/glibc: 22 [...] new 6eb7fc6a35 78: onsuccess: 1: Successful build after binutils/gcc/gdb: 4 [...] new 0c37730747 79: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] new 7fa7a207cc 80: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] new 6225578963 81: onsuccess: 1: Successful build after binutils/gcc/gdb: 6 [...] new ac520b8c2d 82: onsuccess: 1: Successful build after binutils/gcc/gdb: 1 [...] new 4f7eb7ff34 83: onsuccess: 1: Success after binutils/gcc/glibc/gdb: 17 commits new e7312a59e6 84: onsuccess: 1: Success after binutils/gcc/linux/gdb: 68 commits new 8d6defd5ab 85: onsuccess: 1: Success after binutils/gcc/glibc/gdb/qemu: [...] new e04eb61a89 86: onsuccess: 1: Success after binutils/gcc/gdb: 7 commits new c458837b25 87: onsuccess: 1: Success after binutils/gcc/gdb: 14 commits new c396730a6e 88: onsuccess: 1: Success after gcc/linux/qemu: 149 commits new 45f2cc8f17 89: onsuccess: 1: Success after binutils/gcc/gdb: 5 commits new 4635aa2b0a 90: onsuccess: 1: Success after binutils/gcc/gdb: 19 commits new 299fc2bffc 91: onsuccess: 1: Success after binutils/gcc/gdb: 8 commits new e307765eae 92: onsuccess: 1: Success after binutils/gcc/linux/gdb/qemu: [...] new 0c2e4aa1a8 93: onsuccess: 1: Success after binutils/gcc/linux/gdb: 88 commits new b1d2f643fd 94: onsuccess: 1: Success after gcc: openmp: Partial OpenMP [...] new 745dd9acfc 95: onsuccess: #2070: 1: Success after basepoints/gcc-13-238 [...] new 852edd0c83 96: onsuccess: #2071: 1: Success after gcc/linux: 56 commits new 437618c9b8 97: onsuccess: #2072: 1: Success after binutils/gcc/gdb: 3 commits new 4c8356fad6 98: onsuccess: #2073: 1: Success after gcc/linux: 11 commits new ed6873a4f8 99: onsuccess: #2074: 1: Success after baseline build: no ne [...] new 18926d292f 100: onsuccess: #2077: 1: Success after binutils/gcc/linux/g [...] new 568605654c 101: onsuccess: #2130: 1: Success after binutils: 81 commits new c7f970b7c7 102: onsuccess: #2133: 1: Success after gdb-12-branchpoint-1 [...] new 99014c7e0c 103: onsuccess: #2135: 1: Success after gcc/linux/glibc/gdb/ [...] new 45020f34d0 104: onsuccess: #2136: 1: Success after binutils/gcc/gdb: 3 commits
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 (76fed31d3d) \ 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 1756 -> 1776 bytes 02-prepare_abe/console.log.xz | Bin 2748 -> 2720 bytes 03-build_abe-binutils/console.log.xz | Bin 30280 -> 30044 bytes 04-build_abe-stage1/console.log.xz | Bin 72488 -> 71732 bytes 06-build_abe-linux/console.log.xz | Bin 8284 -> 8336 bytes 07-build_abe-glibc/console.log.xz | Bin 239628 -> 239628 bytes 08-build_abe-stage2/console.log.xz | Bin 202560 -> 203736 bytes 09-build_abe-gdb/console.log.xz | Bin 37404 -> 37292 bytes 10-build_abe-qemu/console.log.xz | Bin 31684 -> 31592 bytes 11-build_abe-dejagnu/console.log.xz | Bin 3884 -> 3892 bytes 12-build_abe-check_gcc/console.log.xz | Bin 2896 -> 2456 bytes 13-check_regression/console.log.xz | Bin 14464 -> 4848 bytes 13-check_regression/extra-bisect-params | 1 - 13-check_regression/fails.sum | 45 - 13-check_regression/mail-body.txt | 42 +- 13-check_regression/results.compare | 49 +- 13-check_regression/results.compare2 | 1501 +--------- 13-check_regression/results.regressions | 79 - 14-update_baseline/console.log | 66 +- dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- git/gdb_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 44 +- mail/mail-subject.txt | 2 +- manifest.sh | 32 +- results | 79 - sumfiles/g++.log.xz | Bin 3413852 -> 3401680 bytes sumfiles/g++.sum | 198 +- sumfiles/gcc.log.xz | Bin 3002024 -> 3021536 bytes sumfiles/gcc.sum | 4756 ++++++++++++++++--------------- sumfiles/gfortran.log.xz | Bin 1021956 -> 1028312 bytes sumfiles/gfortran.sum | 4 +- sumfiles/libatomic.log.xz | Bin 2292 -> 2292 bytes sumfiles/libatomic.sum | 2 +- sumfiles/libgomp.log.xz | Bin 202032 -> 202116 bytes sumfiles/libgomp.sum | 7 +- sumfiles/libitm.log.xz | Bin 2660 -> 2656 bytes sumfiles/libitm.sum | 2 +- sumfiles/libstdc++.log.xz | Bin 415632 -> 424996 bytes sumfiles/libstdc++.sum | 8 +- 42 files changed, 2585 insertions(+), 4342 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