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 b3895bfbfe 129: onsuccess: #2164: 1: Success after binutils/gcc/linux/g [...] discards 4c1883752e 128: onsuccess: #2163: 1: Success after linux: 23 commits discards 31aedf9763 127: onsuccess: #2162: 1: Success after gcc: 9 commits discards 8999b2c82e 126: onsuccess: #2161: 1: Success after basepoints/gcc-13-28 [...] discards d93b7bc536 125: onsuccess: #2160: 1: Success after binutils/gcc/linux/g [...] discards d92e8f18a4 124: onsuccess: #2159: 1: Success after linux: 23 commits discards 6b403760b9 123: onsuccess: #2158: 1: Success after basepoints/gcc-13-28 [...] discards aebd9dd99b 122: onsuccess: #2157: 1: Success after binutils/gcc/gdb: 6 commits discards 6e2221887f 121: onsuccess: #2156: 1: Success after binutils/gcc/linux/g [...] discards 388750ab06 120: onsuccess: #2155: 1: Success after binutils/gcc/linux/g [...] discards c4c62aabb4 119: onsuccess: #2154: 1: Success after binutils/gcc/linux/g [...] discards c85b7195a8 118: onsuccess: #2151: 1: Success after binutils/gcc/linux/g [...] discards 0151ecbd90 117: onsuccess: #2150: 1: Success after binutils/gcc/glibc/g [...] discards 84b8157891 116: onsuccess: #2148: 1: Success after binutils/gcc/gdb: 7 commits discards 4f3004a95e 115: onsuccess: #2147: 1: Success after binutils/linux/glibc [...] discards 39d97639e1 114: onsuccess: #2146: 1: Success after binutils/gcc/glibc/g [...] discards 6fce869d76 113: onsuccess: #2145: 1: Success after binutils/gcc/glibc/g [...] discards e208a193c1 112: onsuccess: #2144: 1: Success after binutils/gcc/glibc/g [...] discards 22e062b974 111: onsuccess: #2143: 1: Success after binutils/gcc/linux/g [...] discards 51fc658f1d 110: onsuccess: #2142: 1: Success after binutils/gcc/glibc/g [...] discards f652280c1d 109: onsuccess: #2141: 1: Success after gcc/glibc: 6 commits discards 735f0f8f79 108: onsuccess: #2140: 1: Success after binutils/gcc/gdb: 5 commits discards 0107e3c9db 107: onsuccess: #2139: 1: Success after binutils/gcc/gdb: 3 commits discards 766d8b213e 106: onsuccess: #2138: 1: Success after binutils/gcc/glibc/g [...] discards e20f9431b9 105: onsuccess: #2137: 1: Success after basepoints/gcc-13-27 [...] discards d4bd4cfed2 104: onsuccess: #2136: 1: Success after binutils/gcc/gdb: 3 commits discards 96c2f8c734 103: onsuccess: #2135: 1: Success after gcc/linux/glibc/gdb/ [...] discards 85265bdb68 102: onsuccess: #2133: 1: Success after gdb-12-branchpoint-1 [...] discards 24659dbcd4 101: onsuccess: #2130: 1: Success after binutils: 81 commits discards 493ff0494a 100: onsuccess: #2077: 1: Success after binutils/gcc/linux/g [...] discards e4b7762593 99: onsuccess: #2074: 1: Success after baseline build: no ne [...] discards 20838ce18d 98: onsuccess: #2073: 1: Success after gcc/linux: 11 commits discards e0a26c64ab 97: onsuccess: #2072: 1: Success after binutils/gcc/gdb: 3 commits discards 1e99357a7b 96: onsuccess: #2071: 1: Success after gcc/linux: 56 commits discards e12dc33f12 95: onsuccess: #2070: 1: Success after basepoints/gcc-13-238 [...] discards 014446a5c0 94: onsuccess: 1: Success after gcc: openmp: Partial OpenMP [...] discards e1dd9ff483 93: onsuccess: 1: Success after binutils/gcc/linux/gdb: 88 commits discards 84a980b152 92: onsuccess: 1: Success after binutils/gcc/linux/gdb/qemu: [...] discards ef675a99b3 91: onsuccess: 1: Success after binutils/gcc/gdb: 8 commits discards bb29915c49 90: onsuccess: 1: Success after binutils/gcc/gdb: 19 commits discards a196fea2bc 89: onsuccess: 1: Success after binutils/gcc/gdb: 5 commits discards 509df9a2af 88: onsuccess: 1: Success after gcc/linux/qemu: 149 commits discards edc7f9ddef 87: onsuccess: 1: Success after binutils/gcc/gdb: 14 commits discards 1b223f75d5 86: onsuccess: 1: Success after binutils/gcc/gdb: 7 commits discards 71f21d0dd8 85: onsuccess: 1: Success after binutils/gcc/glibc/gdb/qemu: [...] discards ef6054c60d 84: onsuccess: 1: Success after binutils/gcc/linux/gdb: 68 commits discards 75037182eb 83: onsuccess: 1: Success after binutils/gcc/glibc/gdb: 17 commits discards 2af0a0ef6f 82: onsuccess: 1: Successful build after binutils/gcc/gdb: 1 [...] discards f1b5d648e0 81: onsuccess: 1: Successful build after binutils/gcc/gdb: 6 [...] discards 79e47ffc44 80: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] discards c3e52a629b 79: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] discards 8dcf6fa31e 78: onsuccess: 1: Successful build after binutils/gcc/gdb: 4 [...] discards 145e875646 77: onsuccess: 1: Successful build after gcc/linux/glibc: 22 [...] discards 5d2ba8f285 76: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 5332fb9952 75: onsuccess: 1: Successful build after linux: 44 commits discards 5b35a6b2e9 74: onsuccess: 1: Successful build after binutils/gdb: 2 commits discards fb3441f03b 73: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards e0ff045086 72: onsuccess: 1: Successful build after linux: 12 commits discards a519450d59 71: onsuccess: 1: Successful build after gcc/glibc: 3 commits discards f2302f3897 70: onsuccess: 1: Successful build after binutils/gcc/gdb: 4 [...] discards a65b46af3e 69: onsuccess: 1: Successful build after binutils/gcc/gdb: 5 [...] discards 2d598076d4 68: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 41a77c6662 67: onsuccess: 1: Successful build after binutils/gcc/gdb: 1 [...] discards af26dfdac2 66: onsuccess: 1: Successful build after gcc/glibc: 10 commits discards 0eb244d8de 65: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 9a31f25b2f 64: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards a8fb7cbb53 63: onsuccess: 1: Successful build after binutils/gcc/gdb: 8 [...] discards 51c146b948 62: onsuccess: 1: Successful build after binutils/gcc/gdb: 2 [...] discards 7122f926d4 61: onsuccess: 1: Successful build after binutils/gcc/gdb/qe [...] discards b25c757db3 60: onsuccess: 1: Successful build after glibc: 2 commits discards 3d1ffdfc40 59: onsuccess: 1: Successful build after binutils: 2 commits discards fb943af2f2 58: onsuccess: 1: Successful build after binutils: gdb: new [...] discards fdf5525ae0 57: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] discards 4df6af0255 56: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 203cc585b1 55: onsuccess: 1: Successful build after gcc/linux/glibc/qem [...] discards 116ad91480 54: onsuccess: 1: Successful build after binutils/gcc/gdb: 8 [...] discards 3f87c1b1ee 53: onsuccess: 1: Successful build after binutils/gcc/gdb: 8 [...] discards d012575e0a 52: onsuccess: 1: Successful build after binutils/gcc/gdb: 7 [...] discards 3a7339bfea 51: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 8c1d7bd363 50: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] discards de3e00a549 49: onsuccess: 1: Successful build after gcc/glibc: 5 commits discards 70d764c4ea 48: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 48532a8209 47: onsuccess: 1: Successful build after linux: 10 commits discards 1d6bc55e8b 46: onsuccess: 1: Successful build after binutils/gdb: 2 commits discards c65a3b9fdd 45: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 924a3974ca 44: onsuccess: 1: Successful build after gcc/linux: 35 commits discards c7ca264bb0 43: onsuccess: 1: Successful build after gcc: LoongArch: Add [...] discards ef67d63aae 42: onsuccess: 1: Successful build after gcc: libcpp: Implem [...] discards bac03f810b 41: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 4ecad2fced 40: onsuccess: 1: Successful build after linux/qemu: 147 commits discards 329b2571b9 39: onsuccess: 1: Successful build after binutils/gcc/gdb/qe [...] discards 5225daa464 38: onsuccess: 1: Successful build after gcc/linux: 95 commits discards c4204fd2bc 37: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] discards 08ef82439a 36: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 4e912f5059 35: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] discards 726c55a035 34: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] discards af68fcf74d 33: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards d0edb8f86d 32: onsuccess: 1: Successful build after gcc: 7 commits discards 7fb7ec1b06 31: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] discards aabc31e570 30: onsuccess: 1: Successful build after binutils/gcc/gdb/qe [...] discards 68cc5a46f8 29: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 478d661d64 29: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 58e7476d1b 30: onsuccess: 1: Successful build after binutils/gcc/gdb/qe [...] new 0477980931 31: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] new da034ce476 32: onsuccess: 1: Successful build after gcc: 7 commits new 814ae9e9e8 33: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new f7f7d8b83f 34: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] new 9f66daf177 35: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] new d5f585ff2e 36: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 4d2f5403f6 37: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] new 9daa4d2ec6 38: onsuccess: 1: Successful build after gcc/linux: 95 commits new a963877e0d 39: onsuccess: 1: Successful build after binutils/gcc/gdb/qe [...] new 2e75fa2bb3 40: onsuccess: 1: Successful build after linux/qemu: 147 commits new 43bf5046b2 41: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 778a53fe8d 42: onsuccess: 1: Successful build after gcc: libcpp: Implem [...] new bb5f3f42d2 43: onsuccess: 1: Successful build after gcc: LoongArch: Add [...] new a5e0bb16d9 44: onsuccess: 1: Successful build after gcc/linux: 35 commits new 51cedcbd70 45: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new aa15b88abe 46: onsuccess: 1: Successful build after binutils/gdb: 2 commits new 48fc91e26c 47: onsuccess: 1: Successful build after linux: 10 commits new 1d197f386d 48: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 848c111abf 49: onsuccess: 1: Successful build after gcc/glibc: 5 commits new f5ba01caa2 50: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] new 6aa2d20d93 51: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new d9eed3c8f4 52: onsuccess: 1: Successful build after binutils/gcc/gdb: 7 [...] new c479540018 53: onsuccess: 1: Successful build after binutils/gcc/gdb: 8 [...] new 67d62b0109 54: onsuccess: 1: Successful build after binutils/gcc/gdb: 8 [...] new d3561cbdcf 55: onsuccess: 1: Successful build after gcc/linux/glibc/qem [...] new a98ce0ef14 56: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 6703fce69f 57: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] new 4a166dce63 58: onsuccess: 1: Successful build after binutils: gdb: new [...] new 98e119f44c 59: onsuccess: 1: Successful build after binutils: 2 commits new 4400c4470c 60: onsuccess: 1: Successful build after glibc: 2 commits new 3337621c35 61: onsuccess: 1: Successful build after binutils/gcc/gdb/qe [...] new 92b9790975 62: onsuccess: 1: Successful build after binutils/gcc/gdb: 2 [...] new b6896b0d5c 63: onsuccess: 1: Successful build after binutils/gcc/gdb: 8 [...] new 1dd0f2b99a 64: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 2713b1c573 65: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new dc94f588ec 66: onsuccess: 1: Successful build after gcc/glibc: 10 commits new 7a5f689955 67: onsuccess: 1: Successful build after binutils/gcc/gdb: 1 [...] new 5ff4e543b2 68: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 3dfd99fb85 69: onsuccess: 1: Successful build after binutils/gcc/gdb: 5 [...] new 887b0b69bd 70: onsuccess: 1: Successful build after binutils/gcc/gdb: 4 [...] new 2b8ce459ce 71: onsuccess: 1: Successful build after gcc/glibc: 3 commits new eadee2bcea 72: onsuccess: 1: Successful build after linux: 12 commits new 0b26cbe884 73: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 128ec114b1 74: onsuccess: 1: Successful build after binutils/gdb: 2 commits new f6691c488e 75: onsuccess: 1: Successful build after linux: 44 commits new 642f80ac8a 76: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 8a0314a337 77: onsuccess: 1: Successful build after gcc/linux/glibc: 22 [...] new afd5587938 78: onsuccess: 1: Successful build after binutils/gcc/gdb: 4 [...] new 050e7f78bd 79: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] new 400f05d917 80: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] new ace02afe87 81: onsuccess: 1: Successful build after binutils/gcc/gdb: 6 [...] new 642bcced08 82: onsuccess: 1: Successful build after binutils/gcc/gdb: 1 [...] new e52793178c 83: onsuccess: 1: Success after binutils/gcc/glibc/gdb: 17 commits new 44106b4033 84: onsuccess: 1: Success after binutils/gcc/linux/gdb: 68 commits new c331a9aa4f 85: onsuccess: 1: Success after binutils/gcc/glibc/gdb/qemu: [...] new 792005944c 86: onsuccess: 1: Success after binutils/gcc/gdb: 7 commits new 6a5254c3bf 87: onsuccess: 1: Success after binutils/gcc/gdb: 14 commits new 284b06e45f 88: onsuccess: 1: Success after gcc/linux/qemu: 149 commits new 2fd0ef1cc3 89: onsuccess: 1: Success after binutils/gcc/gdb: 5 commits new 7205c04231 90: onsuccess: 1: Success after binutils/gcc/gdb: 19 commits new d3f9f7a6b7 91: onsuccess: 1: Success after binutils/gcc/gdb: 8 commits new bca78918cd 92: onsuccess: 1: Success after binutils/gcc/linux/gdb/qemu: [...] new cceff4763d 93: onsuccess: 1: Success after binutils/gcc/linux/gdb: 88 commits new 8690c634a7 94: onsuccess: 1: Success after gcc: openmp: Partial OpenMP [...] new af9bd204de 95: onsuccess: #2070: 1: Success after basepoints/gcc-13-238 [...] new c2e7ef2f89 96: onsuccess: #2071: 1: Success after gcc/linux: 56 commits new f5930959fa 97: onsuccess: #2072: 1: Success after binutils/gcc/gdb: 3 commits new 2c597eb659 98: onsuccess: #2073: 1: Success after gcc/linux: 11 commits new f49de48489 99: onsuccess: #2074: 1: Success after baseline build: no ne [...] new 260685ce3d 100: onsuccess: #2077: 1: Success after binutils/gcc/linux/g [...] new a9b2c46f48 101: onsuccess: #2130: 1: Success after binutils: 81 commits new b0e9422564 102: onsuccess: #2133: 1: Success after gdb-12-branchpoint-1 [...] new a04685cfdb 103: onsuccess: #2135: 1: Success after gcc/linux/glibc/gdb/ [...] new a7c59fa3ed 104: onsuccess: #2136: 1: Success after binutils/gcc/gdb: 3 commits new dcdba7b2a5 105: onsuccess: #2137: 1: Success after basepoints/gcc-13-27 [...] new 66eb2c4ffc 106: onsuccess: #2138: 1: Success after binutils/gcc/glibc/g [...] new 01cc351fed 107: onsuccess: #2139: 1: Success after binutils/gcc/gdb: 3 commits new 84932780ac 108: onsuccess: #2140: 1: Success after binutils/gcc/gdb: 5 commits new 0b52c480ed 109: onsuccess: #2141: 1: Success after gcc/glibc: 6 commits new da1e8643ad 110: onsuccess: #2142: 1: Success after binutils/gcc/glibc/g [...] new adf899c912 111: onsuccess: #2143: 1: Success after binutils/gcc/linux/g [...] new 3079569b26 112: onsuccess: #2144: 1: Success after binutils/gcc/glibc/g [...] new e878f6be54 113: onsuccess: #2145: 1: Success after binutils/gcc/glibc/g [...] new cab9c626af 114: onsuccess: #2146: 1: Success after binutils/gcc/glibc/g [...] new f0103b24a5 115: onsuccess: #2147: 1: Success after binutils/linux/glibc [...] new 8e468ced41 116: onsuccess: #2148: 1: Success after binutils/gcc/gdb: 7 commits new 7dc790f09c 117: onsuccess: #2150: 1: Success after binutils/gcc/glibc/g [...] new 93796b9662 118: onsuccess: #2151: 1: Success after binutils/gcc/linux/g [...] new 7df144ead9 119: onsuccess: #2154: 1: Success after binutils/gcc/linux/g [...] new b538731fb4 120: onsuccess: #2155: 1: Success after binutils/gcc/linux/g [...] new 077d992bb6 121: onsuccess: #2156: 1: Success after binutils/gcc/linux/g [...] new d74d548cfa 122: onsuccess: #2157: 1: Success after binutils/gcc/gdb: 6 commits new 3a48694b90 123: onsuccess: #2158: 1: Success after basepoints/gcc-13-28 [...] new db82ac3f2f 124: onsuccess: #2159: 1: Success after linux: 23 commits new 5a3336ec4b 125: onsuccess: #2160: 1: Success after binutils/gcc/linux/g [...] new eeb5f8195f 126: onsuccess: #2161: 1: Success after basepoints/gcc-13-28 [...] new 01e803cbf4 127: onsuccess: #2162: 1: Success after gcc: 9 commits new 2fcb681838 128: onsuccess: #2163: 1: Success after linux: 23 commits new 5270175d9f 129: onsuccess: #2164: 1: Success after binutils/gcc/linux/g [...] new 7b8c593ad2 130: onsuccess: #2165: 1: Success after binutils/gcc/gdb: 32 [...]
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 (b3895bfbfe) \ 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 1740 -> 1708 bytes 02-prepare_abe/console.log.xz | Bin 2732 -> 2748 bytes 03-build_abe-binutils/console.log.xz | Bin 30236 -> 30380 bytes 04-build_abe-stage1/console.log.xz | Bin 72272 -> 72244 bytes 05-clean_sysroot/console.log.xz | Bin 328 -> 328 bytes 06-build_abe-linux/console.log.xz | Bin 8312 -> 8360 bytes 07-build_abe-glibc/console.log.xz | Bin 240760 -> 240392 bytes 08-build_abe-stage2/console.log.xz | Bin 205820 -> 204472 bytes 09-build_abe-gdb/console.log.xz | Bin 38268 -> 37596 bytes 10-build_abe-qemu/console.log.xz | Bin 31644 -> 31444 bytes 11-build_abe-dejagnu/console.log.xz | Bin 3888 -> 3884 bytes 12-build_abe-check_gcc/console.log.xz | Bin 2464 -> 2812 bytes 13-check_regression/console.log.xz | Bin 13360 -> 27300 bytes 13-check_regression/extra-bisect-params | 2 +- 13-check_regression/fails.sum | 63 +- 13-check_regression/mail-body.txt | 201 +- 13-check_regression/results.compare | 85 +- 13-check_regression/results.compare2 | 5802 ++++++++++++++++++++++++------- 13-check_regression/results.regressions | 86 +- 14-update_baseline/console.log | 70 +- 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 | 203 +- mail/mail-subject.txt | 2 +- manifest.sh | 34 +- results | 86 +- sumfiles/g++.log.xz | Bin 3422004 -> 3408936 bytes sumfiles/g++.sum | 5407 +++++++++++----------------- sumfiles/gcc.log.xz | Bin 3028000 -> 3031700 bytes sumfiles/gcc.sum | 4860 +++++++++++++------------- sumfiles/gfortran.log.xz | Bin 1029312 -> 1036392 bytes sumfiles/gfortran.sum | 40 +- sumfiles/libatomic.log.xz | Bin 2292 -> 2292 bytes sumfiles/libatomic.sum | 4 +- sumfiles/libgomp.log.xz | Bin 202060 -> 202136 bytes sumfiles/libgomp.sum | 16 +- sumfiles/libitm.log.xz | Bin 2660 -> 2656 bytes sumfiles/libitm.sum | 6 +- sumfiles/libstdc++.log.xz | Bin 427872 -> 426256 bytes sumfiles/libstdc++.sum | 14 +- 43 files changed, 9478 insertions(+), 7513 deletions(-)