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 9cdfca1bf9 115: onsuccess: #2147: 1: Success after binutils/linux/glibc [...] discards 91464cc5f2 114: onsuccess: #2146: 1: Success after binutils/gcc/glibc/g [...] discards d90fe54949 113: onsuccess: #2145: 1: Success after binutils/gcc/glibc/g [...] discards 9c8c13af3a 112: onsuccess: #2144: 1: Success after binutils/gcc/glibc/g [...] discards 6f56c266fd 111: onsuccess: #2143: 1: Success after binutils/gcc/linux/g [...] discards bff3eeb62c 110: onsuccess: #2142: 1: Success after binutils/gcc/glibc/g [...] discards e622ed6c7b 109: onsuccess: #2141: 1: Success after gcc/glibc: 6 commits discards 780459db2f 108: onsuccess: #2140: 1: Success after binutils/gcc/gdb: 5 commits discards b3df9c156d 107: onsuccess: #2139: 1: Success after binutils/gcc/gdb: 3 commits discards 20c6d422ee 106: onsuccess: #2138: 1: Success after binutils/gcc/glibc/g [...] discards 47d0a0ef1c 105: onsuccess: #2137: 1: Success after basepoints/gcc-13-27 [...] discards 590803e0d9 104: onsuccess: #2136: 1: Success after binutils/gcc/gdb: 3 commits discards 063c6a17d2 103: onsuccess: #2135: 1: Success after gcc/linux/glibc/gdb/ [...] discards 6e90689b35 102: onsuccess: #2133: 1: Success after gdb-12-branchpoint-1 [...] discards 983e0078b8 101: onsuccess: #2130: 1: Success after binutils: 81 commits discards 17b52ee7a7 100: onsuccess: #2077: 1: Success after binutils/gcc/linux/g [...] discards 590d2716a1 99: onsuccess: #2074: 1: Success after baseline build: no ne [...] discards c8f43e4e99 98: onsuccess: #2073: 1: Success after gcc/linux: 11 commits discards 1e44983b9f 97: onsuccess: #2072: 1: Success after binutils/gcc/gdb: 3 commits discards 33417f9489 96: onsuccess: #2071: 1: Success after gcc/linux: 56 commits discards 4b3b879ca2 95: onsuccess: #2070: 1: Success after basepoints/gcc-13-238 [...] discards af03199246 94: onsuccess: 1: Success after gcc: openmp: Partial OpenMP [...] discards bd101ea78a 93: onsuccess: 1: Success after binutils/gcc/linux/gdb: 88 commits discards 0a6894c923 92: onsuccess: 1: Success after binutils/gcc/linux/gdb/qemu: [...] discards f13468ee65 91: onsuccess: 1: Success after binutils/gcc/gdb: 8 commits discards 70fd88d0f5 90: onsuccess: 1: Success after binutils/gcc/gdb: 19 commits discards 7f1ab2696d 89: onsuccess: 1: Success after binutils/gcc/gdb: 5 commits discards 99dd8169d2 88: onsuccess: 1: Success after gcc/linux/qemu: 149 commits discards 362f50bb15 87: onsuccess: 1: Success after binutils/gcc/gdb: 14 commits discards a7e50604ea 86: onsuccess: 1: Success after binutils/gcc/gdb: 7 commits discards 16168588d9 85: onsuccess: 1: Success after binutils/gcc/glibc/gdb/qemu: [...] discards 77529d1dc9 84: onsuccess: 1: Success after binutils/gcc/linux/gdb: 68 commits discards b4291e2fb9 83: onsuccess: 1: Success after binutils/gcc/glibc/gdb: 17 commits discards 8025eb64ec 82: onsuccess: 1: Successful build after binutils/gcc/gdb: 1 [...] discards 91c69e3484 81: onsuccess: 1: Successful build after binutils/gcc/gdb: 6 [...] discards feb2a5a616 80: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] discards f8cd7c98cb 79: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] discards fd0feedbe7 78: onsuccess: 1: Successful build after binutils/gcc/gdb: 4 [...] discards 02ad0dfbe6 77: onsuccess: 1: Successful build after gcc/linux/glibc: 22 [...] discards ac4437895c 76: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 0410e76745 75: onsuccess: 1: Successful build after linux: 44 commits discards 5ffb7b1495 74: onsuccess: 1: Successful build after binutils/gdb: 2 commits discards 9513374ae2 73: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 671a4f11c1 72: onsuccess: 1: Successful build after linux: 12 commits discards c69057fbb8 71: onsuccess: 1: Successful build after gcc/glibc: 3 commits discards 4b53de69e8 70: onsuccess: 1: Successful build after binutils/gcc/gdb: 4 [...] discards 761f9921e2 69: onsuccess: 1: Successful build after binutils/gcc/gdb: 5 [...] discards 5a4bf97b95 68: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 0a0134d631 67: onsuccess: 1: Successful build after binutils/gcc/gdb: 1 [...] discards aacfa1d8fe 66: onsuccess: 1: Successful build after gcc/glibc: 10 commits discards 001f70a1dc 65: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 1293e46e2d 64: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 4c1f3d84c8 63: onsuccess: 1: Successful build after binutils/gcc/gdb: 8 [...] discards 5a94864ff2 62: onsuccess: 1: Successful build after binutils/gcc/gdb: 2 [...] discards 244e24aa34 61: onsuccess: 1: Successful build after binutils/gcc/gdb/qe [...] discards a3a501b0c6 60: onsuccess: 1: Successful build after glibc: 2 commits discards 9371baf8cf 59: onsuccess: 1: Successful build after binutils: 2 commits discards 581d054f21 58: onsuccess: 1: Successful build after binutils: gdb: new [...] discards 066a43881b 57: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] discards c77a6d6ea3 56: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 32e0d13608 55: onsuccess: 1: Successful build after gcc/linux/glibc/qem [...] discards b63dc201b1 54: onsuccess: 1: Successful build after binutils/gcc/gdb: 8 [...] discards ca7688d986 53: onsuccess: 1: Successful build after binutils/gcc/gdb: 8 [...] discards 4fdc7f0d45 52: onsuccess: 1: Successful build after binutils/gcc/gdb: 7 [...] discards 8d0c5dc7bf 51: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 4b19e96dd5 50: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] discards 0299b574ac 49: onsuccess: 1: Successful build after gcc/glibc: 5 commits discards bd3c568792 48: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards f6cbf55b00 47: onsuccess: 1: Successful build after linux: 10 commits discards 3965a24c8f 46: onsuccess: 1: Successful build after binutils/gdb: 2 commits discards 264bcfe35b 45: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards a732c939b4 44: onsuccess: 1: Successful build after gcc/linux: 35 commits discards 8ae4cfb4b7 43: onsuccess: 1: Successful build after gcc: LoongArch: Add [...] discards e48b8ec2ba 42: onsuccess: 1: Successful build after gcc: libcpp: Implem [...] discards dc54628643 41: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 3258f8c05b 40: onsuccess: 1: Successful build after linux/qemu: 147 commits discards af4a25f609 39: onsuccess: 1: Successful build after binutils/gcc/gdb/qe [...] discards 7f9697145d 38: onsuccess: 1: Successful build after gcc/linux: 95 commits discards 71bc5ed95d 37: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] discards de1d1d0cc6 36: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 348855d02c 35: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] discards c7f052a3cd 34: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] discards 836b8cd674 33: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 2dbceec75c 32: onsuccess: 1: Successful build after gcc: 7 commits discards e2bf426110 31: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] discards 801ce40e37 30: onsuccess: 1: Successful build after binutils/gcc/gdb/qe [...] discards 403ab8e451 29: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 6d90c453d6 28: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] discards 871e44dbe2 27: onsuccess: 1: Successful build after binutils/gcc/gdb: 2 [...] discards 7ace53ebb1 26: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards 0fd4418ccd 25: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards e55c20c2cf 24: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards cd82b898db 23: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards d4cec0d209 22: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards eb6c3f43eb 21: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards f092ed6434 20: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards abb905616a 19: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards c2a7fc2c6d 18: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards 510b198e62 17: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards 6fbe01c192 16: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards 71aea626b4 15: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new 23db498091 15: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new 9b3c886fc8 16: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new 52411e4ffe 17: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new c212462250 18: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new 87d3295347 19: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new 880c8a4c62 20: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new e9d1f715f4 21: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new c157ce703d 22: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new 6a3da5a3fb 23: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new 3b3749da97 24: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new 7ebf9afdc1 25: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new f814f2b3c9 26: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new a6da18668c 27: onsuccess: 1: Successful build after binutils/gcc/gdb: 2 [...] new e3417f74b0 28: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] new c4d8b17406 29: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new a5f88015e0 30: onsuccess: 1: Successful build after binutils/gcc/gdb/qe [...] new cb1d373580 31: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] new 54d74765a4 32: onsuccess: 1: Successful build after gcc: 7 commits new f7191d71fe 33: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 840b51800d 34: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] new 596aa73461 35: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] new dc772bfd65 36: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new af680789de 37: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] new 2bcd5a9253 38: onsuccess: 1: Successful build after gcc/linux: 95 commits new 433977ed88 39: onsuccess: 1: Successful build after binutils/gcc/gdb/qe [...] new 62919cb737 40: onsuccess: 1: Successful build after linux/qemu: 147 commits new d91e999470 41: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 8fb31c7306 42: onsuccess: 1: Successful build after gcc: libcpp: Implem [...] new efe0bb2213 43: onsuccess: 1: Successful build after gcc: LoongArch: Add [...] new ff1af852c3 44: onsuccess: 1: Successful build after gcc/linux: 35 commits new 0dfa6d5b12 45: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new dbda06ce14 46: onsuccess: 1: Successful build after binutils/gdb: 2 commits new 69ef5deca1 47: onsuccess: 1: Successful build after linux: 10 commits new 769148b87d 48: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 63adb85f3c 49: onsuccess: 1: Successful build after gcc/glibc: 5 commits new 3054a77e03 50: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] new 637a35be77 51: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 3223ea8aa6 52: onsuccess: 1: Successful build after binutils/gcc/gdb: 7 [...] new d6fde77958 53: onsuccess: 1: Successful build after binutils/gcc/gdb: 8 [...] new 9f71e3f831 54: onsuccess: 1: Successful build after binutils/gcc/gdb: 8 [...] new cbbc6b4181 55: onsuccess: 1: Successful build after gcc/linux/glibc/qem [...] new c9cd4eba72 56: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new e47d023de6 57: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] new 61b14d971e 58: onsuccess: 1: Successful build after binutils: gdb: new [...] new 6ecc4482c4 59: onsuccess: 1: Successful build after binutils: 2 commits new 103ff6a7aa 60: onsuccess: 1: Successful build after glibc: 2 commits new aac18a27da 61: onsuccess: 1: Successful build after binutils/gcc/gdb/qe [...] new c5577919a7 62: onsuccess: 1: Successful build after binutils/gcc/gdb: 2 [...] new cba4e37fc4 63: onsuccess: 1: Successful build after binutils/gcc/gdb: 8 [...] new d33781355e 64: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 5dd8d030e0 65: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 986213faa3 66: onsuccess: 1: Successful build after gcc/glibc: 10 commits new 55e8422a47 67: onsuccess: 1: Successful build after binutils/gcc/gdb: 1 [...] new c92542a66b 68: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new e37240dabf 69: onsuccess: 1: Successful build after binutils/gcc/gdb: 5 [...] new 5979c32104 70: onsuccess: 1: Successful build after binutils/gcc/gdb: 4 [...] new 0a0e040937 71: onsuccess: 1: Successful build after gcc/glibc: 3 commits new b7ac452585 72: onsuccess: 1: Successful build after linux: 12 commits new d969f5c24c 73: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 07e5734b1a 74: onsuccess: 1: Successful build after binutils/gdb: 2 commits new 456318e99e 75: onsuccess: 1: Successful build after linux: 44 commits new 55a606ff2e 76: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new be8528b8e1 77: onsuccess: 1: Successful build after gcc/linux/glibc: 22 [...] new cca7c03302 78: onsuccess: 1: Successful build after binutils/gcc/gdb: 4 [...] new a1df81348c 79: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] new 889104dff3 80: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] new c406682ccf 81: onsuccess: 1: Successful build after binutils/gcc/gdb: 6 [...] new ec8c3a3733 82: onsuccess: 1: Successful build after binutils/gcc/gdb: 1 [...] new 1a6034d2bc 83: onsuccess: 1: Success after binutils/gcc/glibc/gdb: 17 commits new c7f31dfb87 84: onsuccess: 1: Success after binutils/gcc/linux/gdb: 68 commits new cd4474c280 85: onsuccess: 1: Success after binutils/gcc/glibc/gdb/qemu: [...] new 04256a27aa 86: onsuccess: 1: Success after binutils/gcc/gdb: 7 commits new 453b0b1017 87: onsuccess: 1: Success after binutils/gcc/gdb: 14 commits new ca77ded4b8 88: onsuccess: 1: Success after gcc/linux/qemu: 149 commits new 2c9170ddce 89: onsuccess: 1: Success after binutils/gcc/gdb: 5 commits new ece0569fd0 90: onsuccess: 1: Success after binutils/gcc/gdb: 19 commits new be79915fe6 91: onsuccess: 1: Success after binutils/gcc/gdb: 8 commits new 6fd23c41b4 92: onsuccess: 1: Success after binutils/gcc/linux/gdb/qemu: [...] new a05e0bcdc4 93: onsuccess: 1: Success after binutils/gcc/linux/gdb: 88 commits new e8bb3708d2 94: onsuccess: 1: Success after gcc: openmp: Partial OpenMP [...] new ee8e2b3763 95: onsuccess: #2070: 1: Success after basepoints/gcc-13-238 [...] new 873dab46ae 96: onsuccess: #2071: 1: Success after gcc/linux: 56 commits new 9f78a3b42e 97: onsuccess: #2072: 1: Success after binutils/gcc/gdb: 3 commits new 7bd7725b2c 98: onsuccess: #2073: 1: Success after gcc/linux: 11 commits new 63807f3307 99: onsuccess: #2074: 1: Success after baseline build: no ne [...] new 0b9d36d6e1 100: onsuccess: #2077: 1: Success after binutils/gcc/linux/g [...] new cd8b0d6b42 101: onsuccess: #2130: 1: Success after binutils: 81 commits new 37b615af1e 102: onsuccess: #2133: 1: Success after gdb-12-branchpoint-1 [...] new 386a8a9f73 103: onsuccess: #2135: 1: Success after gcc/linux/glibc/gdb/ [...] new 265d0fd1c7 104: onsuccess: #2136: 1: Success after binutils/gcc/gdb: 3 commits new 8dd53eecdb 105: onsuccess: #2137: 1: Success after basepoints/gcc-13-27 [...] new 92dc08ff73 106: onsuccess: #2138: 1: Success after binutils/gcc/glibc/g [...] new 065b6d7ab3 107: onsuccess: #2139: 1: Success after binutils/gcc/gdb: 3 commits new 66c91b3186 108: onsuccess: #2140: 1: Success after binutils/gcc/gdb: 5 commits new 4cb0f93a2f 109: onsuccess: #2141: 1: Success after gcc/glibc: 6 commits new 471fcceb58 110: onsuccess: #2142: 1: Success after binutils/gcc/glibc/g [...] new c711ea032c 111: onsuccess: #2143: 1: Success after binutils/gcc/linux/g [...] new d5b00b2324 112: onsuccess: #2144: 1: Success after binutils/gcc/glibc/g [...] new ac7454376f 113: onsuccess: #2145: 1: Success after binutils/gcc/glibc/g [...] new f5251855e6 114: onsuccess: #2146: 1: Success after binutils/gcc/glibc/g [...] new aae629445c 115: onsuccess: #2147: 1: Success after binutils/linux/glibc [...] new 015e2681d8 116: onsuccess: #2148: 1: Success after binutils/gcc/gdb: 7 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 (9cdfca1bf9) \ 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 1708 -> 1764 bytes 02-prepare_abe/console.log.xz | Bin 2752 -> 2740 bytes 03-build_abe-binutils/console.log.xz | Bin 30456 -> 30060 bytes 04-build_abe-stage1/console.log.xz | Bin 72500 -> 72048 bytes 05-clean_sysroot/console.log.xz | Bin 328 -> 328 bytes 06-build_abe-linux/console.log.xz | Bin 8584 -> 8568 bytes 07-build_abe-glibc/console.log.xz | Bin 239968 -> 239784 bytes 08-build_abe-stage2/console.log.xz | Bin 202608 -> 202020 bytes 09-build_abe-gdb/console.log.xz | Bin 37532 -> 37472 bytes 10-build_abe-qemu/console.log.xz | Bin 31880 -> 32472 bytes 11-build_abe-dejagnu/console.log.xz | Bin 3896 -> 3880 bytes 12-build_abe-check_gcc/console.log.xz | Bin 2684 -> 2456 bytes 13-check_regression/console.log.xz | Bin 23140 -> 9284 bytes 13-check_regression/extra-bisect-params | 2 +- 13-check_regression/fails.sum | 136 +- 13-check_regression/mail-body.txt | 210 +- 13-check_regression/results.compare | 87 +- 13-check_regression/results.compare2 | 3848 ++-------------------- 13-check_regression/results.regressions | 46 +- 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 | 212 +- mail/mail-subject.txt | 2 +- manifest.sh | 32 +- results | 46 +- sumfiles/g++.log.xz | Bin 3410080 -> 3428824 bytes sumfiles/g++.sum | 187 +- sumfiles/gcc.log.xz | Bin 3013788 -> 2996556 bytes sumfiles/gcc.sum | 5320 ++++++++++++++++--------------- sumfiles/gfortran.log.xz | Bin 1030388 -> 1032452 bytes sumfiles/gfortran.sum | 40 +- sumfiles/libatomic.log.xz | Bin 2296 -> 2288 bytes sumfiles/libatomic.sum | 4 +- sumfiles/libgomp.log.xz | Bin 201992 -> 201816 bytes sumfiles/libgomp.sum | 16 +- sumfiles/libitm.log.xz | Bin 2652 -> 2660 bytes sumfiles/libitm.sum | 6 +- sumfiles/libstdc++.log.xz | Bin 416088 -> 428756 bytes sumfiles/libstdc++.sum | 16 +- 43 files changed, 3455 insertions(+), 6831 deletions(-)