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 38f10b3a6 120: onsuccess: #2155: 1: Success after binutils/gcc/linux/gl [...] discards 163229b72 119: onsuccess: #2154: 1: Success after binutils/gcc/linux/gl [...] discards 521c1e7e0 118: onsuccess: #2151: 1: Success after binutils/gcc/linux/gl [...] discards 13906b15c 117: onsuccess: #2150: 1: Success after binutils/gcc/glibc/gd [...] discards 9368e41ea 116: onsuccess: #2148: 1: Success after binutils/gcc/gdb: 7 commits discards 136660726 115: onsuccess: #2147: 1: Success after binutils/linux/glibc/ [...] discards c6f33b686 114: onsuccess: #2146: 1: Success after binutils/gcc/glibc/gd [...] discards 6e7246755 113: onsuccess: #2145: 1: Success after binutils/gcc/glibc/gd [...] discards 81669825d 112: onsuccess: #2144: 1: Success after binutils/gcc/glibc/gd [...] discards 0a99a8d4c 111: onsuccess: #2143: 1: Success after binutils/gcc/linux/gl [...] discards 580d1ae5c 110: onsuccess: #2142: 1: Success after binutils/gcc/glibc/gd [...] discards 5187eac84 109: onsuccess: #2141: 1: Success after gcc/glibc: 6 commits discards 0c44aa1ca 108: onsuccess: #2140: 1: Success after binutils/gcc/gdb: 5 commits discards 945f5c1a1 107: onsuccess: #2139: 1: Success after binutils/gcc/gdb: 3 commits discards bfd285896 106: onsuccess: #2138: 1: Success after binutils/gcc/glibc/gd [...] discards 9c97f9ec8 105: onsuccess: #2137: 1: Success after basepoints/gcc-13-271 [...] discards 4f74390e6 104: onsuccess: #2136: 1: Success after binutils/gcc/gdb: 3 commits discards effc18660 103: onsuccess: #2135: 1: Success after gcc/linux/glibc/gdb/q [...] discards cce612590 102: onsuccess: #2133: 1: Success after gdb-12-branchpoint-19 [...] discards ddfea0794 101: onsuccess: #2130: 1: Success after binutils: 81 commits discards 6615d9c4a 100: onsuccess: #2077: 1: Success after binutils/gcc/linux/gd [...] discards 9e0f1c5de 99: onsuccess: #2074: 1: Success after baseline build: no new [...] discards 6655e32fc 98: onsuccess: #2073: 1: Success after gcc/linux: 11 commits discards a218b75d6 97: onsuccess: #2072: 1: Success after binutils/gcc/gdb: 3 commits discards e46f77fa3 96: onsuccess: #2071: 1: Success after gcc/linux: 56 commits discards e9de26935 95: onsuccess: #2070: 1: Success after basepoints/gcc-13-2389 [...] discards 59dac4f2a 94: onsuccess: 1: Success after gcc: openmp: Partial OpenMP 5 [...] discards 54ae7c293 93: onsuccess: 1: Success after binutils/gcc/linux/gdb: 88 commits discards f7c191b0a 92: onsuccess: 1: Success after binutils/gcc/linux/gdb/qemu: [...] discards 1f746638c 91: onsuccess: 1: Success after binutils/gcc/gdb: 8 commits discards 2ce35d23c 90: onsuccess: 1: Success after binutils/gcc/gdb: 19 commits discards 1432e8b2b 89: onsuccess: 1: Success after binutils/gcc/gdb: 5 commits discards 74b235900 88: onsuccess: 1: Success after gcc/linux/qemu: 149 commits discards c98804d85 87: onsuccess: 1: Success after binutils/gcc/gdb: 14 commits discards 8b9d8da0e 86: onsuccess: 1: Success after binutils/gcc/gdb: 7 commits discards 59970c53e 85: onsuccess: 1: Success after binutils/gcc/glibc/gdb/qemu: [...] discards 048350a43 84: onsuccess: 1: Success after binutils/gcc/linux/gdb: 68 commits discards 19f9a0bc9 83: onsuccess: 1: Success after binutils/gcc/glibc/gdb: 17 commits discards be086fce4 82: onsuccess: 1: Successful build after binutils/gcc/gdb: 11 [...] discards 568025c00 81: onsuccess: 1: Successful build after binutils/gcc/gdb: 6 commits discards 432074574 80: onsuccess: 1: Successful build after binutils/gcc/glibc/g [...] discards 88e0ed563 79: onsuccess: 1: Successful build after binutils/gcc/glibc/g [...] discards feca64825 78: onsuccess: 1: Successful build after binutils/gcc/gdb: 4 commits discards 8ff18d5ea 77: onsuccess: 1: Successful build after gcc/linux/glibc: 22 commits discards c91389cbe 76: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] discards 9fa681541 75: onsuccess: 1: Successful build after linux: 44 commits discards d6e0c41c5 74: onsuccess: 1: Successful build after binutils/gdb: 2 commits discards 516bd77bf 73: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] discards 95b334832 72: onsuccess: 1: Successful build after linux: 12 commits discards 5926895b5 71: onsuccess: 1: Successful build after gcc/glibc: 3 commits discards 1a5d323f8 70: onsuccess: 1: Successful build after binutils/gcc/gdb: 4 commits discards 283934a86 69: onsuccess: 1: Successful build after binutils/gcc/gdb: 5 commits discards 627d82f67 68: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] discards d1ba3f404 67: onsuccess: 1: Successful build after binutils/gcc/gdb: 10 [...] discards 0d7222374 66: onsuccess: 1: Successful build after gcc/glibc: 10 commits discards a030e77a7 65: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] discards 33c337886 64: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] discards 832d4872a 63: onsuccess: 1: Successful build after binutils/gcc/gdb: 8 commits discards 57a04b6ba 62: onsuccess: 1: Successful build after binutils/gcc/gdb: 22 [...] discards a21f4fcb6 61: onsuccess: 1: Successful build after binutils/gcc/gdb/qem [...] discards a6ecdfba8 60: onsuccess: 1: Successful build after glibc: 2 commits discards 2bfa9085a 59: onsuccess: 1: Successful build after binutils: 2 commits discards 6ab2eb878 58: onsuccess: 1: Successful build after binutils: gdb: new ' [...] discards 90d3a6e6a 57: onsuccess: 1: Successful build after binutils/gcc/glibc/g [...] discards a9ddc365a 56: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] discards 573238b8a 55: onsuccess: 1: Successful build after gcc/linux/glibc/qemu [...] discards 38c718b58 54: onsuccess: 1: Successful build after binutils/gcc/gdb: 8 commits discards 1b8f6edf4 53: onsuccess: 1: Successful build after binutils/gcc/gdb: 8 commits discards 61a4f600a 52: onsuccess: 1: Successful build after binutils/gcc/gdb: 7 commits discards b451d50dc 51: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] discards 7282c2b58 50: onsuccess: 1: Successful build after binutils/gcc/glibc/g [...] discards aa59c533f 49: onsuccess: 1: Successful build after gcc/glibc: 5 commits discards c829b75bd 48: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] discards f619b9b42 47: onsuccess: 1: Successful build after linux: 10 commits discards af0e5c115 46: onsuccess: 1: Successful build after binutils/gdb: 2 commits discards 52f2a967f 45: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] discards e29824ee6 44: onsuccess: 1: Successful build after gcc/linux: 35 commits discards 63d1d164a 43: onsuccess: 1: Successful build after gcc: LoongArch: Add [...] discards beff84277 42: onsuccess: 1: Successful build after gcc: libcpp: Impleme [...] discards bf69953e2 41: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] discards 26684ffe4 40: onsuccess: 1: Successful build after linux/qemu: 147 commits discards 6e42420c2 39: onsuccess: 1: Successful build after binutils/gcc/gdb/qem [...] discards 5194930c0 38: onsuccess: 1: Successful build after gcc/linux: 95 commits discards ea6b0ce0c 37: onsuccess: 1: Successful build after binutils/gcc/glibc/g [...] discards 52ec6e1dc 36: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] discards 0349f9ca5 35: onsuccess: 1: Successful build after binutils/gcc/glibc/g [...] discards 84ba73008 34: onsuccess: 1: Successful build after binutils/gcc/glibc/g [...] discards c41c4d473 33: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] discards 318e15c78 32: onsuccess: 1: Successful build after gcc: 7 commits discards 5030c525b 31: onsuccess: 1: Successful build after binutils/gcc/glibc/g [...] discards d462e3be0 30: onsuccess: 1: Successful build after binutils/gcc/gdb/qem [...] discards 646b5b344 29: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] discards 3f31c1a6b 28: onsuccess: 1: Successful build after binutils/gcc/glibc/g [...] discards 91bd00f09 27: onsuccess: 1: Successful build after binutils/gcc/gdb: 25 [...] discards b3ab3d133 26: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards d39fda76e 25: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards ac915af2c 24: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards e875be745 23: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards 81922fe9c 22: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards ffb0d444a 21: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards 5cfbdce86 20: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new a54e1fd83 20: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new 741d00536 21: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new 2bd813101 22: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new 7be08e90a 23: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new e0fa32c28 24: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new c13750e1f 25: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new 42ff3ab2b 26: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new 2c83096f2 27: onsuccess: 1: Successful build after binutils/gcc/gdb: 25 [...] new 94a0d8893 28: onsuccess: 1: Successful build after binutils/gcc/glibc/g [...] new 88222fa27 29: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] new 79c6d9e41 30: onsuccess: 1: Successful build after binutils/gcc/gdb/qem [...] new 6b3de43fd 31: onsuccess: 1: Successful build after binutils/gcc/glibc/g [...] new 5aa2fce1f 32: onsuccess: 1: Successful build after gcc: 7 commits new 8f591c56f 33: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] new 5dc3b772f 34: onsuccess: 1: Successful build after binutils/gcc/glibc/g [...] new 49c217575 35: onsuccess: 1: Successful build after binutils/gcc/glibc/g [...] new cfb18c676 36: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] new 2422c73d6 37: onsuccess: 1: Successful build after binutils/gcc/glibc/g [...] new ed09cb8c0 38: onsuccess: 1: Successful build after gcc/linux: 95 commits new c55bc547f 39: onsuccess: 1: Successful build after binutils/gcc/gdb/qem [...] new 2b6c95fa1 40: onsuccess: 1: Successful build after linux/qemu: 147 commits new 7660b79e0 41: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] new 691f41253 42: onsuccess: 1: Successful build after gcc: libcpp: Impleme [...] new 686cd2a69 43: onsuccess: 1: Successful build after gcc: LoongArch: Add [...] new 20b65fe4a 44: onsuccess: 1: Successful build after gcc/linux: 35 commits new 3c34e5e11 45: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] new 73b7d379b 46: onsuccess: 1: Successful build after binutils/gdb: 2 commits new e4206687d 47: onsuccess: 1: Successful build after linux: 10 commits new c588a28d6 48: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] new b01cc4779 49: onsuccess: 1: Successful build after gcc/glibc: 5 commits new 020bb6489 50: onsuccess: 1: Successful build after binutils/gcc/glibc/g [...] new 42d7d88cb 51: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] new d2e8149b0 52: onsuccess: 1: Successful build after binutils/gcc/gdb: 7 commits new c0a8dd4ac 53: onsuccess: 1: Successful build after binutils/gcc/gdb: 8 commits new 0598beba3 54: onsuccess: 1: Successful build after binutils/gcc/gdb: 8 commits new 0fdc9d1dd 55: onsuccess: 1: Successful build after gcc/linux/glibc/qemu [...] new f2e44cdae 56: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] new 9cddc7233 57: onsuccess: 1: Successful build after binutils/gcc/glibc/g [...] new ecf6e70cb 58: onsuccess: 1: Successful build after binutils: gdb: new ' [...] new 8353c0944 59: onsuccess: 1: Successful build after binutils: 2 commits new e37c6e409 60: onsuccess: 1: Successful build after glibc: 2 commits new 40d89c7dd 61: onsuccess: 1: Successful build after binutils/gcc/gdb/qem [...] new 2f682f693 62: onsuccess: 1: Successful build after binutils/gcc/gdb: 22 [...] new db42fa227 63: onsuccess: 1: Successful build after binutils/gcc/gdb: 8 commits new 764996929 64: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] new a1452c6a9 65: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] new c3eedd3a6 66: onsuccess: 1: Successful build after gcc/glibc: 10 commits new 9385215b6 67: onsuccess: 1: Successful build after binutils/gcc/gdb: 10 [...] new c1cc3dd5d 68: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] new e50c6d4c9 69: onsuccess: 1: Successful build after binutils/gcc/gdb: 5 commits new add2fa323 70: onsuccess: 1: Successful build after binutils/gcc/gdb: 4 commits new c9674fda8 71: onsuccess: 1: Successful build after gcc/glibc: 3 commits new a8e95f6ed 72: onsuccess: 1: Successful build after linux: 12 commits new af1f40acf 73: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] new 21dead7c5 74: onsuccess: 1: Successful build after binutils/gdb: 2 commits new 414633c88 75: onsuccess: 1: Successful build after linux: 44 commits new 7b647c8dc 76: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] new 3b3316afa 77: onsuccess: 1: Successful build after gcc/linux/glibc: 22 commits new b26fce328 78: onsuccess: 1: Successful build after binutils/gcc/gdb: 4 commits new e80579d10 79: onsuccess: 1: Successful build after binutils/gcc/glibc/g [...] new 283457d96 80: onsuccess: 1: Successful build after binutils/gcc/glibc/g [...] new 087c7eec7 81: onsuccess: 1: Successful build after binutils/gcc/gdb: 6 commits new 7f38d2f67 82: onsuccess: 1: Successful build after binutils/gcc/gdb: 11 [...] new e85a12d4c 83: onsuccess: 1: Success after binutils/gcc/glibc/gdb: 17 commits new 2a1cb4c4b 84: onsuccess: 1: Success after binutils/gcc/linux/gdb: 68 commits new de85709f9 85: onsuccess: 1: Success after binutils/gcc/glibc/gdb/qemu: [...] new 51f4ddb93 86: onsuccess: 1: Success after binutils/gcc/gdb: 7 commits new 93f5b4c20 87: onsuccess: 1: Success after binutils/gcc/gdb: 14 commits new c0f33b38b 88: onsuccess: 1: Success after gcc/linux/qemu: 149 commits new d966e59ff 89: onsuccess: 1: Success after binutils/gcc/gdb: 5 commits new 3b783d693 90: onsuccess: 1: Success after binutils/gcc/gdb: 19 commits new 236c722e7 91: onsuccess: 1: Success after binutils/gcc/gdb: 8 commits new ab25cc895 92: onsuccess: 1: Success after binutils/gcc/linux/gdb/qemu: [...] new 9a9743974 93: onsuccess: 1: Success after binutils/gcc/linux/gdb: 88 commits new 5a103a414 94: onsuccess: 1: Success after gcc: openmp: Partial OpenMP 5 [...] new 80f25fd60 95: onsuccess: #2070: 1: Success after basepoints/gcc-13-2389 [...] new 14b972605 96: onsuccess: #2071: 1: Success after gcc/linux: 56 commits new ca9d1d763 97: onsuccess: #2072: 1: Success after binutils/gcc/gdb: 3 commits new 4751ef482 98: onsuccess: #2073: 1: Success after gcc/linux: 11 commits new f9ca15fda 99: onsuccess: #2074: 1: Success after baseline build: no new [...] new 099d0c3aa 100: onsuccess: #2077: 1: Success after binutils/gcc/linux/gd [...] new b9b8d6199 101: onsuccess: #2130: 1: Success after binutils: 81 commits new c82962e77 102: onsuccess: #2133: 1: Success after gdb-12-branchpoint-19 [...] new d4e450c97 103: onsuccess: #2135: 1: Success after gcc/linux/glibc/gdb/q [...] new 56da04e30 104: onsuccess: #2136: 1: Success after binutils/gcc/gdb: 3 commits new 6ca751b27 105: onsuccess: #2137: 1: Success after basepoints/gcc-13-271 [...] new ce5c22ba5 106: onsuccess: #2138: 1: Success after binutils/gcc/glibc/gd [...] new ea9d6efa8 107: onsuccess: #2139: 1: Success after binutils/gcc/gdb: 3 commits new efc986358 108: onsuccess: #2140: 1: Success after binutils/gcc/gdb: 5 commits new d9c9eb17e 109: onsuccess: #2141: 1: Success after gcc/glibc: 6 commits new 16bf50f5d 110: onsuccess: #2142: 1: Success after binutils/gcc/glibc/gd [...] new 53f4612f9 111: onsuccess: #2143: 1: Success after binutils/gcc/linux/gl [...] new 8191665fb 112: onsuccess: #2144: 1: Success after binutils/gcc/glibc/gd [...] new 395b8e572 113: onsuccess: #2145: 1: Success after binutils/gcc/glibc/gd [...] new 2238dfbe7 114: onsuccess: #2146: 1: Success after binutils/gcc/glibc/gd [...] new 02a0373fa 115: onsuccess: #2147: 1: Success after binutils/linux/glibc/ [...] new 9b996ef22 116: onsuccess: #2148: 1: Success after binutils/gcc/gdb: 7 commits new a42c02ed3 117: onsuccess: #2150: 1: Success after binutils/gcc/glibc/gd [...] new 26a44b332 118: onsuccess: #2151: 1: Success after binutils/gcc/linux/gl [...] new 2cea14d8f 119: onsuccess: #2154: 1: Success after binutils/gcc/linux/gl [...] new c41bcd5a4 120: onsuccess: #2155: 1: Success after binutils/gcc/linux/gl [...] new 94a8dfb35 121: onsuccess: #2156: 1: Success after binutils/gcc/linux/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 (38f10b3a6) \ 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 -> 1704 bytes 02-prepare_abe/console.log.xz | Bin 2744 -> 2732 bytes 03-build_abe-binutils/console.log.xz | Bin 30320 -> 31048 bytes 04-build_abe-stage1/console.log.xz | Bin 72224 -> 72216 bytes 05-clean_sysroot/console.log.xz | Bin 328 -> 328 bytes 06-build_abe-linux/console.log.xz | Bin 8908 -> 8840 bytes 07-build_abe-glibc/console.log.xz | Bin 239788 -> 239936 bytes 08-build_abe-stage2/console.log.xz | Bin 203228 -> 203024 bytes 09-build_abe-gdb/console.log.xz | Bin 37512 -> 38328 bytes 10-build_abe-qemu/console.log.xz | Bin 32012 -> 31268 bytes 11-build_abe-dejagnu/console.log.xz | Bin 3872 -> 3872 bytes 12-build_abe-check_gcc/console.log.xz | Bin 2776 -> 2444 bytes 13-check_regression/console.log.xz | Bin 6292 -> 7280 bytes 13-check_regression/results.compare | 24 +- 13-check_regression/results.compare2 | 735 ++++- 14-update_baseline/console.log | 64 +- dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- git/gdb_rev | 2 +- git/linux_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 2 +- mail/mail-subject.txt | 2 +- manifest.sh | 38 +- sumfiles/g++.log.xz | Bin 3410492 -> 3405888 bytes sumfiles/g++.sum | 159 +- sumfiles/gcc.log.xz | Bin 3016028 -> 3032792 bytes sumfiles/gcc.sum | 5576 +++++++++++++++++++-------------- sumfiles/gfortran.log.xz | Bin 1027592 -> 1029764 bytes sumfiles/gfortran.sum | 44 +- sumfiles/libatomic.log.xz | Bin 2292 -> 2292 bytes sumfiles/libatomic.sum | 4 +- sumfiles/libgomp.log.xz | Bin 201928 -> 201860 bytes sumfiles/libgomp.sum | 16 +- sumfiles/libitm.log.xz | Bin 2656 -> 2660 bytes sumfiles/libitm.sum | 6 +- sumfiles/libstdc++.log.xz | Bin 427916 -> 422808 bytes sumfiles/libstdc++.sum | 19 +- 39 files changed, 4036 insertions(+), 2665 deletions(-)