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 bd46f7434 117: onsuccess: #2150: 1: Success after binutils/gcc/glibc/gd [...] discards 71441e7ce 116: onsuccess: #2148: 1: Success after binutils/gcc/gdb: 7 commits discards 7742bac72 115: onsuccess: #2147: 1: Success after binutils/linux/glibc/ [...] discards ef6014a44 114: onsuccess: #2146: 1: Success after binutils/gcc/glibc/gd [...] discards f78ba0fce 113: onsuccess: #2145: 1: Success after binutils/gcc/glibc/gd [...] discards 5c812d12e 112: onsuccess: #2144: 1: Success after binutils/gcc/glibc/gd [...] discards ec475b228 111: onsuccess: #2143: 1: Success after binutils/gcc/linux/gl [...] discards e106bce88 110: onsuccess: #2142: 1: Success after binutils/gcc/glibc/gd [...] discards 45d202168 109: onsuccess: #2141: 1: Success after gcc/glibc: 6 commits discards 7056efbc1 108: onsuccess: #2140: 1: Success after binutils/gcc/gdb: 5 commits discards d2d543cc0 107: onsuccess: #2139: 1: Success after binutils/gcc/gdb: 3 commits discards a95ba3c79 106: onsuccess: #2138: 1: Success after binutils/gcc/glibc/gd [...] discards bbdb252ea 105: onsuccess: #2137: 1: Success after basepoints/gcc-13-271 [...] discards 2f80714ab 104: onsuccess: #2136: 1: Success after binutils/gcc/gdb: 3 commits discards ba5a29bb1 103: onsuccess: #2135: 1: Success after gcc/linux/glibc/gdb/q [...] discards 8d5d17093 102: onsuccess: #2133: 1: Success after gdb-12-branchpoint-19 [...] discards 6cad75c6a 101: onsuccess: #2130: 1: Success after binutils: 81 commits discards 6d85b7804 100: onsuccess: #2077: 1: Success after binutils/gcc/linux/gd [...] discards 35255fd4d 99: onsuccess: #2074: 1: Success after baseline build: no new [...] discards e22377087 98: onsuccess: #2073: 1: Success after gcc/linux: 11 commits discards 1ef78cfce 97: onsuccess: #2072: 1: Success after binutils/gcc/gdb: 3 commits discards 886a167a4 96: onsuccess: #2071: 1: Success after gcc/linux: 56 commits discards 8745e2cfb 95: onsuccess: #2070: 1: Success after basepoints/gcc-13-2389 [...] discards 99117e3d8 94: onsuccess: 1: Success after gcc: openmp: Partial OpenMP 5 [...] discards 981f7d3e9 93: onsuccess: 1: Success after binutils/gcc/linux/gdb: 88 commits discards 02d6a051b 92: onsuccess: 1: Success after binutils/gcc/linux/gdb/qemu: [...] discards c705461d1 91: onsuccess: 1: Success after binutils/gcc/gdb: 8 commits discards 46692828a 90: onsuccess: 1: Success after binutils/gcc/gdb: 19 commits discards 2a5695ce8 89: onsuccess: 1: Success after binutils/gcc/gdb: 5 commits discards 07eece83c 88: onsuccess: 1: Success after gcc/linux/qemu: 149 commits discards c6a19ef93 87: onsuccess: 1: Success after binutils/gcc/gdb: 14 commits discards 71fc138b0 86: onsuccess: 1: Success after binutils/gcc/gdb: 7 commits discards ce5ec23a3 85: onsuccess: 1: Success after binutils/gcc/glibc/gdb/qemu: [...] discards 714e5d6fd 84: onsuccess: 1: Success after binutils/gcc/linux/gdb: 68 commits discards 269877d04 83: onsuccess: 1: Success after binutils/gcc/glibc/gdb: 17 commits discards df5a3af07 82: onsuccess: 1: Successful build after binutils/gcc/gdb: 11 [...] discards b035d4e55 81: onsuccess: 1: Successful build after binutils/gcc/gdb: 6 commits discards 73ec6820b 80: onsuccess: 1: Successful build after binutils/gcc/glibc/g [...] discards 3528e9dcd 79: onsuccess: 1: Successful build after binutils/gcc/glibc/g [...] discards b956ac095 78: onsuccess: 1: Successful build after binutils/gcc/gdb: 4 commits discards 0ce4e7bd2 77: onsuccess: 1: Successful build after gcc/linux/glibc: 22 commits discards 20a8326a6 76: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] discards 29f46c2f8 75: onsuccess: 1: Successful build after linux: 44 commits discards 9daa54045 74: onsuccess: 1: Successful build after binutils/gdb: 2 commits discards 084a98cae 73: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] discards 4d0408440 72: onsuccess: 1: Successful build after linux: 12 commits discards d6ffaa4bd 71: onsuccess: 1: Successful build after gcc/glibc: 3 commits discards 4b9a7d813 70: onsuccess: 1: Successful build after binutils/gcc/gdb: 4 commits discards 1468e6e20 69: onsuccess: 1: Successful build after binutils/gcc/gdb: 5 commits discards 582aaa4c2 68: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] discards b8188a60c 67: onsuccess: 1: Successful build after binutils/gcc/gdb: 10 [...] discards f69486387 66: onsuccess: 1: Successful build after gcc/glibc: 10 commits discards 70c01fddc 65: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] discards fdb59583b 64: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] discards 9bd528059 63: onsuccess: 1: Successful build after binutils/gcc/gdb: 8 commits discards 268666226 62: onsuccess: 1: Successful build after binutils/gcc/gdb: 22 [...] discards 3a605614b 61: onsuccess: 1: Successful build after binutils/gcc/gdb/qem [...] discards d25f2fb25 60: onsuccess: 1: Successful build after glibc: 2 commits discards de2394cd3 59: onsuccess: 1: Successful build after binutils: 2 commits discards b3a5b7598 58: onsuccess: 1: Successful build after binutils: gdb: new ' [...] discards a4ac71ec2 57: onsuccess: 1: Successful build after binutils/gcc/glibc/g [...] discards 1a36beda6 56: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] discards f76e9292a 55: onsuccess: 1: Successful build after gcc/linux/glibc/qemu [...] discards 427fb0434 54: onsuccess: 1: Successful build after binutils/gcc/gdb: 8 commits discards 131e90014 53: onsuccess: 1: Successful build after binutils/gcc/gdb: 8 commits discards 34878d227 52: onsuccess: 1: Successful build after binutils/gcc/gdb: 7 commits discards aec529e0a 51: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] discards 20085dbb3 50: onsuccess: 1: Successful build after binutils/gcc/glibc/g [...] discards 15ec701a3 49: onsuccess: 1: Successful build after gcc/glibc: 5 commits discards c2dfca246 48: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] discards 84df3632e 47: onsuccess: 1: Successful build after linux: 10 commits discards edbc27d8e 46: onsuccess: 1: Successful build after binutils/gdb: 2 commits discards e08db7af5 45: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] discards 9b4a9c9b0 44: onsuccess: 1: Successful build after gcc/linux: 35 commits discards 63f2e8ee7 43: onsuccess: 1: Successful build after gcc: LoongArch: Add [...] discards 35dd75984 42: onsuccess: 1: Successful build after gcc: libcpp: Impleme [...] discards d122d08b6 41: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] discards 7c28b8d87 40: onsuccess: 1: Successful build after linux/qemu: 147 commits discards e6fb28e84 39: onsuccess: 1: Successful build after binutils/gcc/gdb/qem [...] discards 959242dfd 38: onsuccess: 1: Successful build after gcc/linux: 95 commits discards b8efbe5b8 37: onsuccess: 1: Successful build after binutils/gcc/glibc/g [...] discards 995c03902 36: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] discards d9eb0e4c8 35: onsuccess: 1: Successful build after binutils/gcc/glibc/g [...] discards 8dde42108 34: onsuccess: 1: Successful build after binutils/gcc/glibc/g [...] discards 66127fea1 33: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] discards 02093b6d6 32: onsuccess: 1: Successful build after gcc: 7 commits discards 2b909680f 31: onsuccess: 1: Successful build after binutils/gcc/glibc/g [...] discards d53d49848 30: onsuccess: 1: Successful build after binutils/gcc/gdb/qem [...] discards d7366528c 29: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] discards b20d419d3 28: onsuccess: 1: Successful build after binutils/gcc/glibc/g [...] discards 34d18bf4c 27: onsuccess: 1: Successful build after binutils/gcc/gdb: 25 [...] discards 134f80c97 26: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards 89c23686d 25: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards 41929529c 24: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards 14fe4dbee 23: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards b2b4b332e 22: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards e4351d388 21: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards bdaa3fb96 20: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards 50728143c 19: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards dbbeb56d6 18: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards f83c93ee6 17: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new 6652795ba 17: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new e2d34d677 18: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new c23709e3a 19: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new 38070dcbf 20: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new 632b0dc56 21: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new 31450e8bc 22: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new acefed904 23: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new 0c17acd41 24: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new b41d97135 25: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new eae3239f2 26: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new 8fa81d750 27: onsuccess: 1: Successful build after binutils/gcc/gdb: 25 [...] new b88dd5f01 28: onsuccess: 1: Successful build after binutils/gcc/glibc/g [...] new dfcfaf832 29: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] new 2f004874a 30: onsuccess: 1: Successful build after binutils/gcc/gdb/qem [...] new ab53287eb 31: onsuccess: 1: Successful build after binutils/gcc/glibc/g [...] new 6f97baf9e 32: onsuccess: 1: Successful build after gcc: 7 commits new 19cc38157 33: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] new d0ac952c1 34: onsuccess: 1: Successful build after binutils/gcc/glibc/g [...] new 809c47594 35: onsuccess: 1: Successful build after binutils/gcc/glibc/g [...] new 87b3d1f31 36: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] new b371b7f9e 37: onsuccess: 1: Successful build after binutils/gcc/glibc/g [...] new 99af086a8 38: onsuccess: 1: Successful build after gcc/linux: 95 commits new 179d184b5 39: onsuccess: 1: Successful build after binutils/gcc/gdb/qem [...] new bf984861e 40: onsuccess: 1: Successful build after linux/qemu: 147 commits new 06f8cc0dd 41: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] new 2de602947 42: onsuccess: 1: Successful build after gcc: libcpp: Impleme [...] new 7a8b29df7 43: onsuccess: 1: Successful build after gcc: LoongArch: Add [...] new e723460e4 44: onsuccess: 1: Successful build after gcc/linux: 35 commits new 7f5592dfb 45: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] new 25764e9eb 46: onsuccess: 1: Successful build after binutils/gdb: 2 commits new da2c68021 47: onsuccess: 1: Successful build after linux: 10 commits new 86d9e5168 48: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] new f4d2e8656 49: onsuccess: 1: Successful build after gcc/glibc: 5 commits new c8821244a 50: onsuccess: 1: Successful build after binutils/gcc/glibc/g [...] new 0b0d70f55 51: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] new 83a613a51 52: onsuccess: 1: Successful build after binutils/gcc/gdb: 7 commits new 0e83ab15a 53: onsuccess: 1: Successful build after binutils/gcc/gdb: 8 commits new ce9b4718a 54: onsuccess: 1: Successful build after binutils/gcc/gdb: 8 commits new 9a62bab26 55: onsuccess: 1: Successful build after gcc/linux/glibc/qemu [...] new 959c43c89 56: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] new 347b194c8 57: onsuccess: 1: Successful build after binutils/gcc/glibc/g [...] new 42f6ce637 58: onsuccess: 1: Successful build after binutils: gdb: new ' [...] new 8e2f2585e 59: onsuccess: 1: Successful build after binutils: 2 commits new e1d286867 60: onsuccess: 1: Successful build after glibc: 2 commits new 596dd2a7e 61: onsuccess: 1: Successful build after binutils/gcc/gdb/qem [...] new bae3323f6 62: onsuccess: 1: Successful build after binutils/gcc/gdb: 22 [...] new 5179d39af 63: onsuccess: 1: Successful build after binutils/gcc/gdb: 8 commits new 4652e35ea 64: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] new 53175e86c 65: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] new 551263e72 66: onsuccess: 1: Successful build after gcc/glibc: 10 commits new 2fbb99858 67: onsuccess: 1: Successful build after binutils/gcc/gdb: 10 [...] new 6d1e99615 68: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] new c728e7c5e 69: onsuccess: 1: Successful build after binutils/gcc/gdb: 5 commits new d701d4a18 70: onsuccess: 1: Successful build after binutils/gcc/gdb: 4 commits new 6aa41048b 71: onsuccess: 1: Successful build after gcc/glibc: 3 commits new c045b7a8e 72: onsuccess: 1: Successful build after linux: 12 commits new 82361a49b 73: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] new bf48ba747 74: onsuccess: 1: Successful build after binutils/gdb: 2 commits new fc90201da 75: onsuccess: 1: Successful build after linux: 44 commits new 781f7269e 76: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] new b8f48848d 77: onsuccess: 1: Successful build after gcc/linux/glibc: 22 commits new 40f129f5b 78: onsuccess: 1: Successful build after binutils/gcc/gdb: 4 commits new b0fe20925 79: onsuccess: 1: Successful build after binutils/gcc/glibc/g [...] new 72f41bdee 80: onsuccess: 1: Successful build after binutils/gcc/glibc/g [...] new a312a0987 81: onsuccess: 1: Successful build after binutils/gcc/gdb: 6 commits new c4bbf4874 82: onsuccess: 1: Successful build after binutils/gcc/gdb: 11 [...] new 50f8cf840 83: onsuccess: 1: Success after binutils/gcc/glibc/gdb: 17 commits new 6713a59d8 84: onsuccess: 1: Success after binutils/gcc/linux/gdb: 68 commits new 1c487eb4f 85: onsuccess: 1: Success after binutils/gcc/glibc/gdb/qemu: [...] new 86119f79b 86: onsuccess: 1: Success after binutils/gcc/gdb: 7 commits new e77964fae 87: onsuccess: 1: Success after binutils/gcc/gdb: 14 commits new d1dcb0740 88: onsuccess: 1: Success after gcc/linux/qemu: 149 commits new 648eb915d 89: onsuccess: 1: Success after binutils/gcc/gdb: 5 commits new d6f2117ca 90: onsuccess: 1: Success after binutils/gcc/gdb: 19 commits new 9559b1cf0 91: onsuccess: 1: Success after binutils/gcc/gdb: 8 commits new b0cb2e278 92: onsuccess: 1: Success after binutils/gcc/linux/gdb/qemu: [...] new a04fef81f 93: onsuccess: 1: Success after binutils/gcc/linux/gdb: 88 commits new 4020df513 94: onsuccess: 1: Success after gcc: openmp: Partial OpenMP 5 [...] new 37e1d28b3 95: onsuccess: #2070: 1: Success after basepoints/gcc-13-2389 [...] new dbdd26f3e 96: onsuccess: #2071: 1: Success after gcc/linux: 56 commits new 78125c3d1 97: onsuccess: #2072: 1: Success after binutils/gcc/gdb: 3 commits new 7f4de6307 98: onsuccess: #2073: 1: Success after gcc/linux: 11 commits new b4f39559a 99: onsuccess: #2074: 1: Success after baseline build: no new [...] new ed4b5fccf 100: onsuccess: #2077: 1: Success after binutils/gcc/linux/gd [...] new 517b2d781 101: onsuccess: #2130: 1: Success after binutils: 81 commits new 78da4d6b0 102: onsuccess: #2133: 1: Success after gdb-12-branchpoint-19 [...] new 285a83be0 103: onsuccess: #2135: 1: Success after gcc/linux/glibc/gdb/q [...] new a654c32e9 104: onsuccess: #2136: 1: Success after binutils/gcc/gdb: 3 commits new 4192f5f9f 105: onsuccess: #2137: 1: Success after basepoints/gcc-13-271 [...] new e8dbed1ec 106: onsuccess: #2138: 1: Success after binutils/gcc/glibc/gd [...] new f23372e04 107: onsuccess: #2139: 1: Success after binutils/gcc/gdb: 3 commits new 0fe87f833 108: onsuccess: #2140: 1: Success after binutils/gcc/gdb: 5 commits new 37ade7365 109: onsuccess: #2141: 1: Success after gcc/glibc: 6 commits new 06122c28c 110: onsuccess: #2142: 1: Success after binutils/gcc/glibc/gd [...] new 7ac9be801 111: onsuccess: #2143: 1: Success after binutils/gcc/linux/gl [...] new 5e7d695ab 112: onsuccess: #2144: 1: Success after binutils/gcc/glibc/gd [...] new d594bee45 113: onsuccess: #2145: 1: Success after binutils/gcc/glibc/gd [...] new 59f87618a 114: onsuccess: #2146: 1: Success after binutils/gcc/glibc/gd [...] new d22bc5204 115: onsuccess: #2147: 1: Success after binutils/linux/glibc/ [...] new 443a83b1b 116: onsuccess: #2148: 1: Success after binutils/gcc/gdb: 7 commits new c91e06f7a 117: onsuccess: #2150: 1: Success after binutils/gcc/glibc/gd [...] new 66ffcccc4 118: onsuccess: #2151: 1: Success after binutils/gcc/linux/gl [...]

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 (bd46f7434) \ 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 1644 -> 1704 bytes 02-prepare_abe/console.log.xz | Bin 2748 -> 2736 bytes 03-build_abe-binutils/console.log.xz | Bin 30148 -> 31080 bytes 04-build_abe-stage1/console.log.xz | Bin 72172 -> 72600 bytes 05-clean_sysroot/console.log.xz | Bin 328 -> 328 bytes 06-build_abe-linux/console.log.xz | Bin 8592 -> 9260 bytes 07-build_abe-glibc/console.log.xz | Bin 239496 -> 239916 bytes 08-build_abe-stage2/console.log.xz | Bin 202780 -> 202904 bytes 09-build_abe-gdb/console.log.xz | Bin 37476 -> 38292 bytes 10-build_abe-qemu/console.log.xz | Bin 31752 -> 31408 bytes 11-build_abe-dejagnu/console.log.xz | Bin 3880 -> 3876 bytes 12-build_abe-check_gcc/console.log.xz | Bin 2548 -> 2704 bytes 13-check_regression/console.log.xz | Bin 10896 -> 6520 bytes 13-check_regression/extra-bisect-params | 2 +- 13-check_regression/fails.sum | 586 +--- 13-check_regression/mail-body.txt | 186 +- 13-check_regression/results.compare | 610 +--- 13-check_regression/results.compare2 | 812 +---- 13-check_regression/results.regressions | 120 +- 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 +- git/linux_rev | 2 +- git/qemu_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 188 +- mail/mail-subject.txt | 2 +- manifest.sh | 44 +- results | 120 +- sumfiles/g++.log.xz | Bin 3397660 -> 3421900 bytes sumfiles/g++.sum | 338 +- sumfiles/gcc.log.xz | Bin 3016212 -> 3012288 bytes sumfiles/gcc.sum | 5085 ++++++++++++++++--------------- sumfiles/gfortran.log.xz | Bin 1025040 -> 1030344 bytes sumfiles/gfortran.sum | 57 +- sumfiles/libatomic.log.xz | Bin 2284 -> 2288 bytes sumfiles/libatomic.sum | 4 +- sumfiles/libgomp.log.xz | Bin 201764 -> 201992 bytes sumfiles/libgomp.sum | 16 +- sumfiles/libitm.log.xz | Bin 2668 -> 2652 bytes sumfiles/libitm.sum | 6 +- sumfiles/libstdc++.log.xz | Bin 423416 -> 422228 bytes sumfiles/libstdc++.sum | 17 +- 46 files changed, 3199 insertions(+), 5076 deletions(-)