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 015e2681d 116: onsuccess: #2148: 1: Success after binutils/gcc/gdb: 7 commits discards aae629445 115: onsuccess: #2147: 1: Success after binutils/linux/glibc/ [...] discards f5251855e 114: onsuccess: #2146: 1: Success after binutils/gcc/glibc/gd [...] discards ac7454376 113: onsuccess: #2145: 1: Success after binutils/gcc/glibc/gd [...] discards d5b00b232 112: onsuccess: #2144: 1: Success after binutils/gcc/glibc/gd [...] discards c711ea032 111: onsuccess: #2143: 1: Success after binutils/gcc/linux/gl [...] discards 471fcceb5 110: onsuccess: #2142: 1: Success after binutils/gcc/glibc/gd [...] discards 4cb0f93a2 109: onsuccess: #2141: 1: Success after gcc/glibc: 6 commits discards 66c91b318 108: onsuccess: #2140: 1: Success after binutils/gcc/gdb: 5 commits discards 065b6d7ab 107: onsuccess: #2139: 1: Success after binutils/gcc/gdb: 3 commits discards 92dc08ff7 106: onsuccess: #2138: 1: Success after binutils/gcc/glibc/gd [...] discards 8dd53eecd 105: onsuccess: #2137: 1: Success after basepoints/gcc-13-271 [...] discards 265d0fd1c 104: onsuccess: #2136: 1: Success after binutils/gcc/gdb: 3 commits discards 386a8a9f7 103: onsuccess: #2135: 1: Success after gcc/linux/glibc/gdb/q [...] discards 37b615af1 102: onsuccess: #2133: 1: Success after gdb-12-branchpoint-19 [...] discards cd8b0d6b4 101: onsuccess: #2130: 1: Success after binutils: 81 commits discards 0b9d36d6e 100: onsuccess: #2077: 1: Success after binutils/gcc/linux/gd [...] discards 63807f330 99: onsuccess: #2074: 1: Success after baseline build: no new [...] discards 7bd7725b2 98: onsuccess: #2073: 1: Success after gcc/linux: 11 commits discards 9f78a3b42 97: onsuccess: #2072: 1: Success after binutils/gcc/gdb: 3 commits discards 873dab46a 96: onsuccess: #2071: 1: Success after gcc/linux: 56 commits discards ee8e2b376 95: onsuccess: #2070: 1: Success after basepoints/gcc-13-2389 [...] discards e8bb3708d 94: onsuccess: 1: Success after gcc: openmp: Partial OpenMP 5 [...] discards a05e0bcdc 93: onsuccess: 1: Success after binutils/gcc/linux/gdb: 88 commits discards 6fd23c41b 92: onsuccess: 1: Success after binutils/gcc/linux/gdb/qemu: [...] discards be79915fe 91: onsuccess: 1: Success after binutils/gcc/gdb: 8 commits discards ece0569fd 90: onsuccess: 1: Success after binutils/gcc/gdb: 19 commits discards 2c9170ddc 89: onsuccess: 1: Success after binutils/gcc/gdb: 5 commits discards ca77ded4b 88: onsuccess: 1: Success after gcc/linux/qemu: 149 commits discards 453b0b101 87: onsuccess: 1: Success after binutils/gcc/gdb: 14 commits discards 04256a27a 86: onsuccess: 1: Success after binutils/gcc/gdb: 7 commits discards cd4474c28 85: onsuccess: 1: Success after binutils/gcc/glibc/gdb/qemu: [...] discards c7f31dfb8 84: onsuccess: 1: Success after binutils/gcc/linux/gdb: 68 commits discards 1a6034d2b 83: onsuccess: 1: Success after binutils/gcc/glibc/gdb: 17 commits discards ec8c3a373 82: onsuccess: 1: Successful build after binutils/gcc/gdb: 11 [...] discards c406682cc 81: onsuccess: 1: Successful build after binutils/gcc/gdb: 6 commits discards 889104dff 80: onsuccess: 1: Successful build after binutils/gcc/glibc/g [...] discards a1df81348 79: onsuccess: 1: Successful build after binutils/gcc/glibc/g [...] discards cca7c0330 78: onsuccess: 1: Successful build after binutils/gcc/gdb: 4 commits discards be8528b8e 77: onsuccess: 1: Successful build after gcc/linux/glibc: 22 commits discards 55a606ff2 76: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] discards 456318e99 75: onsuccess: 1: Successful build after linux: 44 commits discards 07e5734b1 74: onsuccess: 1: Successful build after binutils/gdb: 2 commits discards d969f5c24 73: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] discards b7ac45258 72: onsuccess: 1: Successful build after linux: 12 commits discards 0a0e04093 71: onsuccess: 1: Successful build after gcc/glibc: 3 commits discards 5979c3210 70: onsuccess: 1: Successful build after binutils/gcc/gdb: 4 commits discards e37240dab 69: onsuccess: 1: Successful build after binutils/gcc/gdb: 5 commits discards c92542a66 68: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] discards 55e8422a4 67: onsuccess: 1: Successful build after binutils/gcc/gdb: 10 [...] discards 986213faa 66: onsuccess: 1: Successful build after gcc/glibc: 10 commits discards 5dd8d030e 65: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] discards d33781355 64: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] discards cba4e37fc 63: onsuccess: 1: Successful build after binutils/gcc/gdb: 8 commits discards c5577919a 62: onsuccess: 1: Successful build after binutils/gcc/gdb: 22 [...] discards aac18a27d 61: onsuccess: 1: Successful build after binutils/gcc/gdb/qem [...] discards 103ff6a7a 60: onsuccess: 1: Successful build after glibc: 2 commits discards 6ecc4482c 59: onsuccess: 1: Successful build after binutils: 2 commits discards 61b14d971 58: onsuccess: 1: Successful build after binutils: gdb: new ' [...] discards e47d023de 57: onsuccess: 1: Successful build after binutils/gcc/glibc/g [...] discards c9cd4eba7 56: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] discards cbbc6b418 55: onsuccess: 1: Successful build after gcc/linux/glibc/qemu [...] discards 9f71e3f83 54: onsuccess: 1: Successful build after binutils/gcc/gdb: 8 commits discards d6fde7795 53: onsuccess: 1: Successful build after binutils/gcc/gdb: 8 commits discards 3223ea8aa 52: onsuccess: 1: Successful build after binutils/gcc/gdb: 7 commits discards 637a35be7 51: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] discards 3054a77e0 50: onsuccess: 1: Successful build after binutils/gcc/glibc/g [...] discards 63adb85f3 49: onsuccess: 1: Successful build after gcc/glibc: 5 commits discards 769148b87 48: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] discards 69ef5deca 47: onsuccess: 1: Successful build after linux: 10 commits discards dbda06ce1 46: onsuccess: 1: Successful build after binutils/gdb: 2 commits discards 0dfa6d5b1 45: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] discards ff1af852c 44: onsuccess: 1: Successful build after gcc/linux: 35 commits discards efe0bb221 43: onsuccess: 1: Successful build after gcc: LoongArch: Add [...] discards 8fb31c730 42: onsuccess: 1: Successful build after gcc: libcpp: Impleme [...] discards d91e99947 41: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] discards 62919cb73 40: onsuccess: 1: Successful build after linux/qemu: 147 commits discards 433977ed8 39: onsuccess: 1: Successful build after binutils/gcc/gdb/qem [...] discards 2bcd5a925 38: onsuccess: 1: Successful build after gcc/linux: 95 commits discards af680789d 37: onsuccess: 1: Successful build after binutils/gcc/glibc/g [...] discards dc772bfd6 36: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] discards 596aa7346 35: onsuccess: 1: Successful build after binutils/gcc/glibc/g [...] discards 840b51800 34: onsuccess: 1: Successful build after binutils/gcc/glibc/g [...] discards f7191d71f 33: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] discards 54d74765a 32: onsuccess: 1: Successful build after gcc: 7 commits discards cb1d37358 31: onsuccess: 1: Successful build after binutils/gcc/glibc/g [...] discards a5f88015e 30: onsuccess: 1: Successful build after binutils/gcc/gdb/qem [...] discards c4d8b1740 29: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] discards e3417f74b 28: onsuccess: 1: Successful build after binutils/gcc/glibc/g [...] discards a6da18668 27: onsuccess: 1: Successful build after binutils/gcc/gdb: 25 [...] discards f814f2b3c 26: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards 7ebf9afdc 25: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards 3b3749da9 24: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards 6a3da5a3f 23: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards c157ce703 22: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards e9d1f715f 21: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards 880c8a4c6 20: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards 87d329534 19: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards c21246225 18: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards 52411e4ff 17: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards 9b3c886fc 16: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new 643a85820 16: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new f83c93ee6 17: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new dbbeb56d6 18: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new 50728143c 19: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new bdaa3fb96 20: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new e4351d388 21: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new b2b4b332e 22: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new 14fe4dbee 23: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new 41929529c 24: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new 89c23686d 25: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new 134f80c97 26: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new 34d18bf4c 27: onsuccess: 1: Successful build after binutils/gcc/gdb: 25 [...] new b20d419d3 28: onsuccess: 1: Successful build after binutils/gcc/glibc/g [...] new d7366528c 29: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] new d53d49848 30: onsuccess: 1: Successful build after binutils/gcc/gdb/qem [...] new 2b909680f 31: onsuccess: 1: Successful build after binutils/gcc/glibc/g [...] new 02093b6d6 32: onsuccess: 1: Successful build after gcc: 7 commits new 66127fea1 33: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] new 8dde42108 34: onsuccess: 1: Successful build after binutils/gcc/glibc/g [...] new d9eb0e4c8 35: onsuccess: 1: Successful build after binutils/gcc/glibc/g [...] new 995c03902 36: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] new b8efbe5b8 37: onsuccess: 1: Successful build after binutils/gcc/glibc/g [...] new 959242dfd 38: onsuccess: 1: Successful build after gcc/linux: 95 commits new e6fb28e84 39: onsuccess: 1: Successful build after binutils/gcc/gdb/qem [...] new 7c28b8d87 40: onsuccess: 1: Successful build after linux/qemu: 147 commits new d122d08b6 41: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] new 35dd75984 42: onsuccess: 1: Successful build after gcc: libcpp: Impleme [...] new 63f2e8ee7 43: onsuccess: 1: Successful build after gcc: LoongArch: Add [...] new 9b4a9c9b0 44: onsuccess: 1: Successful build after gcc/linux: 35 commits new e08db7af5 45: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] new edbc27d8e 46: onsuccess: 1: Successful build after binutils/gdb: 2 commits new 84df3632e 47: onsuccess: 1: Successful build after linux: 10 commits new c2dfca246 48: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] new 15ec701a3 49: onsuccess: 1: Successful build after gcc/glibc: 5 commits new 20085dbb3 50: onsuccess: 1: Successful build after binutils/gcc/glibc/g [...] new aec529e0a 51: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] new 34878d227 52: onsuccess: 1: Successful build after binutils/gcc/gdb: 7 commits new 131e90014 53: onsuccess: 1: Successful build after binutils/gcc/gdb: 8 commits new 427fb0434 54: onsuccess: 1: Successful build after binutils/gcc/gdb: 8 commits new f76e9292a 55: onsuccess: 1: Successful build after gcc/linux/glibc/qemu [...] new 1a36beda6 56: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] new a4ac71ec2 57: onsuccess: 1: Successful build after binutils/gcc/glibc/g [...] new b3a5b7598 58: onsuccess: 1: Successful build after binutils: gdb: new ' [...] new de2394cd3 59: onsuccess: 1: Successful build after binutils: 2 commits new d25f2fb25 60: onsuccess: 1: Successful build after glibc: 2 commits new 3a605614b 61: onsuccess: 1: Successful build after binutils/gcc/gdb/qem [...] new 268666226 62: onsuccess: 1: Successful build after binutils/gcc/gdb: 22 [...] new 9bd528059 63: onsuccess: 1: Successful build after binutils/gcc/gdb: 8 commits new fdb59583b 64: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] new 70c01fddc 65: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] new f69486387 66: onsuccess: 1: Successful build after gcc/glibc: 10 commits new b8188a60c 67: onsuccess: 1: Successful build after binutils/gcc/gdb: 10 [...] new 582aaa4c2 68: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] new 1468e6e20 69: onsuccess: 1: Successful build after binutils/gcc/gdb: 5 commits new 4b9a7d813 70: onsuccess: 1: Successful build after binutils/gcc/gdb: 4 commits new d6ffaa4bd 71: onsuccess: 1: Successful build after gcc/glibc: 3 commits new 4d0408440 72: onsuccess: 1: Successful build after linux: 12 commits new 084a98cae 73: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] new 9daa54045 74: onsuccess: 1: Successful build after binutils/gdb: 2 commits new 29f46c2f8 75: onsuccess: 1: Successful build after linux: 44 commits new 20a8326a6 76: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] new 0ce4e7bd2 77: onsuccess: 1: Successful build after gcc/linux/glibc: 22 commits new b956ac095 78: onsuccess: 1: Successful build after binutils/gcc/gdb: 4 commits new 3528e9dcd 79: onsuccess: 1: Successful build after binutils/gcc/glibc/g [...] new 73ec6820b 80: onsuccess: 1: Successful build after binutils/gcc/glibc/g [...] new b035d4e55 81: onsuccess: 1: Successful build after binutils/gcc/gdb: 6 commits new df5a3af07 82: onsuccess: 1: Successful build after binutils/gcc/gdb: 11 [...] new 269877d04 83: onsuccess: 1: Success after binutils/gcc/glibc/gdb: 17 commits new 714e5d6fd 84: onsuccess: 1: Success after binutils/gcc/linux/gdb: 68 commits new ce5ec23a3 85: onsuccess: 1: Success after binutils/gcc/glibc/gdb/qemu: [...] new 71fc138b0 86: onsuccess: 1: Success after binutils/gcc/gdb: 7 commits new c6a19ef93 87: onsuccess: 1: Success after binutils/gcc/gdb: 14 commits new 07eece83c 88: onsuccess: 1: Success after gcc/linux/qemu: 149 commits new 2a5695ce8 89: onsuccess: 1: Success after binutils/gcc/gdb: 5 commits new 46692828a 90: onsuccess: 1: Success after binutils/gcc/gdb: 19 commits new c705461d1 91: onsuccess: 1: Success after binutils/gcc/gdb: 8 commits new 02d6a051b 92: onsuccess: 1: Success after binutils/gcc/linux/gdb/qemu: [...] new 981f7d3e9 93: onsuccess: 1: Success after binutils/gcc/linux/gdb: 88 commits new 99117e3d8 94: onsuccess: 1: Success after gcc: openmp: Partial OpenMP 5 [...] new 8745e2cfb 95: onsuccess: #2070: 1: Success after basepoints/gcc-13-2389 [...] new 886a167a4 96: onsuccess: #2071: 1: Success after gcc/linux: 56 commits new 1ef78cfce 97: onsuccess: #2072: 1: Success after binutils/gcc/gdb: 3 commits new e22377087 98: onsuccess: #2073: 1: Success after gcc/linux: 11 commits new 35255fd4d 99: onsuccess: #2074: 1: Success after baseline build: no new [...] new 6d85b7804 100: onsuccess: #2077: 1: Success after binutils/gcc/linux/gd [...] new 6cad75c6a 101: onsuccess: #2130: 1: Success after binutils: 81 commits new 8d5d17093 102: onsuccess: #2133: 1: Success after gdb-12-branchpoint-19 [...] new ba5a29bb1 103: onsuccess: #2135: 1: Success after gcc/linux/glibc/gdb/q [...] new 2f80714ab 104: onsuccess: #2136: 1: Success after binutils/gcc/gdb: 3 commits new bbdb252ea 105: onsuccess: #2137: 1: Success after basepoints/gcc-13-271 [...] new a95ba3c79 106: onsuccess: #2138: 1: Success after binutils/gcc/glibc/gd [...] new d2d543cc0 107: onsuccess: #2139: 1: Success after binutils/gcc/gdb: 3 commits new 7056efbc1 108: onsuccess: #2140: 1: Success after binutils/gcc/gdb: 5 commits new 45d202168 109: onsuccess: #2141: 1: Success after gcc/glibc: 6 commits new e106bce88 110: onsuccess: #2142: 1: Success after binutils/gcc/glibc/gd [...] new ec475b228 111: onsuccess: #2143: 1: Success after binutils/gcc/linux/gl [...] new 5c812d12e 112: onsuccess: #2144: 1: Success after binutils/gcc/glibc/gd [...] new f78ba0fce 113: onsuccess: #2145: 1: Success after binutils/gcc/glibc/gd [...] new ef6014a44 114: onsuccess: #2146: 1: Success after binutils/gcc/glibc/gd [...] new 7742bac72 115: onsuccess: #2147: 1: Success after binutils/linux/glibc/ [...] new 71441e7ce 116: onsuccess: #2148: 1: Success after binutils/gcc/gdb: 7 commits new bd46f7434 117: onsuccess: #2150: 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 (015e2681d) \ 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 1764 -> 1644 bytes 02-prepare_abe/console.log.xz | Bin 2740 -> 2748 bytes 03-build_abe-binutils/console.log.xz | Bin 30060 -> 30148 bytes 04-build_abe-stage1/console.log.xz | Bin 72048 -> 72172 bytes 06-build_abe-linux/console.log.xz | Bin 8568 -> 8592 bytes 07-build_abe-glibc/console.log.xz | Bin 239784 -> 239496 bytes 08-build_abe-stage2/console.log.xz | Bin 202020 -> 202780 bytes 09-build_abe-gdb/console.log.xz | Bin 37472 -> 37476 bytes 10-build_abe-qemu/console.log.xz | Bin 32472 -> 31752 bytes 11-build_abe-dejagnu/console.log.xz | Bin 3880 -> 3880 bytes 12-build_abe-check_gcc/console.log.xz | Bin 2456 -> 2548 bytes 13-check_regression/console.log.xz | Bin 9284 -> 10896 bytes 13-check_regression/extra-bisect-params | 2 +- 13-check_regression/fails.sum | 577 +++- 13-check_regression/mail-body.txt | 208 +- 13-check_regression/results.compare | 715 ++++- 13-check_regression/results.compare2 | 1648 +++++----- 13-check_regression/results.regressions | 162 +- 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 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 210 +- mail/mail-subject.txt | 2 +- manifest.sh | 38 +- results | 162 +- sumfiles/g++.log.xz | Bin 3428824 -> 3397660 bytes sumfiles/g++.sum | 620 ++-- sumfiles/gcc.log.xz | Bin 2996556 -> 3016212 bytes sumfiles/gcc.sum | 4977 ++++++++++++++++--------------- sumfiles/gfortran.log.xz | Bin 1032452 -> 1025040 bytes sumfiles/gfortran.sum | 2 +- sumfiles/libatomic.log.xz | Bin 2288 -> 2284 bytes sumfiles/libatomic.sum | 2 +- sumfiles/libgomp.log.xz | Bin 201816 -> 201764 bytes sumfiles/libgomp.sum | 2 +- sumfiles/libitm.log.xz | Bin 2660 -> 2668 bytes sumfiles/libitm.sum | 2 +- sumfiles/libstdc++.log.xz | Bin 428756 -> 423416 bytes sumfiles/libstdc++.sum | 129 +- 43 files changed, 5269 insertions(+), 4267 deletions(-)