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 a68d06b3aa 132: onsuccess: #2167: 1: Success after binutils/gcc/glibc/g [...] discards 93a1bb7bcd 131: onsuccess: #2166: 1: Success after binutils/gcc/gdb: 12 [...] discards 1a28ee7673 130: onsuccess: #2165: 1: Success after binutils/gcc/gdb: 32 [...] discards dd4decf4cc 129: onsuccess: #2164: 1: Success after binutils/gcc/linux/g [...] discards 5ffedbc1f6 128: onsuccess: #2163: 1: Success after linux: 23 commits discards 31f407bd1f 127: onsuccess: #2162: 1: Success after gcc: 9 commits discards 47ab23d631 126: onsuccess: #2161: 1: Success after basepoints/gcc-13-28 [...] discards 125a8a30bc 125: onsuccess: #2160: 1: Success after binutils/gcc/linux/g [...] discards d084124194 124: onsuccess: #2159: 1: Success after linux: 23 commits discards 6a7ebca127 123: onsuccess: #2158: 1: Success after basepoints/gcc-13-28 [...] discards f75436aebf 122: onsuccess: #2157: 1: Success after binutils/gcc/gdb: 6 commits discards df5d4132c8 121: onsuccess: #2156: 1: Success after binutils/gcc/linux/g [...] discards 5a1de9abb3 120: onsuccess: #2155: 1: Success after binutils/gcc/linux/g [...] discards 2e75f075d8 119: onsuccess: #2154: 1: Success after binutils/gcc/linux/g [...] discards 28b5d78d03 118: onsuccess: #2151: 1: Success after binutils/gcc/linux/g [...] discards 22d15946ca 117: onsuccess: #2150: 1: Success after binutils/gcc/glibc/g [...] discards 30d3fd7263 116: onsuccess: #2148: 1: Success after binutils/gcc/gdb: 7 commits discards f7e26974a0 115: onsuccess: #2147: 1: Success after binutils/linux/glibc [...] discards bbf3a6589a 114: onsuccess: #2146: 1: Success after binutils/gcc/glibc/g [...] discards 92e1fe62a6 113: onsuccess: #2145: 1: Success after binutils/gcc/glibc/g [...] discards 27fe67a3b8 112: onsuccess: #2144: 1: Success after binutils/gcc/glibc/g [...] discards 982a7d724e 111: onsuccess: #2143: 1: Success after binutils/gcc/linux/g [...] discards 534552f4f8 110: onsuccess: #2142: 1: Success after binutils/gcc/glibc/g [...] discards 44eeb49be2 109: onsuccess: #2141: 1: Success after gcc/glibc: 6 commits discards fae69b4f72 108: onsuccess: #2140: 1: Success after binutils/gcc/gdb: 5 commits discards 7bacef81c1 107: onsuccess: #2139: 1: Success after binutils/gcc/gdb: 3 commits discards 8ef0bd5a90 106: onsuccess: #2138: 1: Success after binutils/gcc/glibc/g [...] discards 0a7e315bb7 105: onsuccess: #2137: 1: Success after basepoints/gcc-13-27 [...] discards c6f4eef030 104: onsuccess: #2136: 1: Success after binutils/gcc/gdb: 3 commits discards 0aac9cab77 103: onsuccess: #2135: 1: Success after gcc/linux/glibc/gdb/ [...] discards be5901ef06 102: onsuccess: #2133: 1: Success after gdb-12-branchpoint-1 [...] discards 62da89aa7f 101: onsuccess: #2130: 1: Success after binutils: 81 commits discards 246ed10e68 100: onsuccess: #2077: 1: Success after binutils/gcc/linux/g [...] discards b128a5d19e 99: onsuccess: #2074: 1: Success after baseline build: no ne [...] discards 3dd6a632e1 98: onsuccess: #2073: 1: Success after gcc/linux: 11 commits discards 95f34f2050 97: onsuccess: #2072: 1: Success after binutils/gcc/gdb: 3 commits discards 054ea8fc9b 96: onsuccess: #2071: 1: Success after gcc/linux: 56 commits discards 44ce4ae5ec 95: onsuccess: #2070: 1: Success after basepoints/gcc-13-238 [...] discards 2a2e04f9bb 94: onsuccess: 1: Success after gcc: openmp: Partial OpenMP [...] discards 6fb36d610f 93: onsuccess: 1: Success after binutils/gcc/linux/gdb: 88 commits discards 23b6b99c57 92: onsuccess: 1: Success after binutils/gcc/linux/gdb/qemu: [...] discards 511ac95b5b 91: onsuccess: 1: Success after binutils/gcc/gdb: 8 commits discards 387e2581ac 90: onsuccess: 1: Success after binutils/gcc/gdb: 19 commits discards b30e5799bb 89: onsuccess: 1: Success after binutils/gcc/gdb: 5 commits discards a492291dc0 88: onsuccess: 1: Success after gcc/linux/qemu: 149 commits discards 66ffe13bf4 87: onsuccess: 1: Success after binutils/gcc/gdb: 14 commits discards dea669266e 86: onsuccess: 1: Success after binutils/gcc/gdb: 7 commits discards 41cdeecb7e 85: onsuccess: 1: Success after binutils/gcc/glibc/gdb/qemu: [...] discards 02b4b5b2bc 84: onsuccess: 1: Success after binutils/gcc/linux/gdb: 68 commits discards 86a120e59a 83: onsuccess: 1: Success after binutils/gcc/glibc/gdb: 17 commits discards 348988ae9b 82: onsuccess: 1: Successful build after binutils/gcc/gdb: 1 [...] discards cc789dba3e 81: onsuccess: 1: Successful build after binutils/gcc/gdb: 6 [...] discards f9f1b9606b 80: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] discards 164b024806 79: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] discards 63521fb157 78: onsuccess: 1: Successful build after binutils/gcc/gdb: 4 [...] discards e6c7dee319 77: onsuccess: 1: Successful build after gcc/linux/glibc: 22 [...] discards 1f230f3011 76: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards ffe4c0c987 75: onsuccess: 1: Successful build after linux: 44 commits discards 8b1a4d8cef 74: onsuccess: 1: Successful build after binutils/gdb: 2 commits discards 5fdd0e59a7 73: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 1cb566e6e5 72: onsuccess: 1: Successful build after linux: 12 commits discards d6e48727fc 71: onsuccess: 1: Successful build after gcc/glibc: 3 commits discards c08cefc173 70: onsuccess: 1: Successful build after binutils/gcc/gdb: 4 [...] discards f22c4460f3 69: onsuccess: 1: Successful build after binutils/gcc/gdb: 5 [...] discards 0399b0f387 68: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 14b36b34d5 67: onsuccess: 1: Successful build after binutils/gcc/gdb: 1 [...] discards 69068b0a4a 66: onsuccess: 1: Successful build after gcc/glibc: 10 commits discards e354adbd4d 65: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 5341a70a02 64: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards c44ac29db1 63: onsuccess: 1: Successful build after binutils/gcc/gdb: 8 [...] discards 6a3a50e8d5 62: onsuccess: 1: Successful build after binutils/gcc/gdb: 2 [...] discards 87189513f0 61: onsuccess: 1: Successful build after binutils/gcc/gdb/qe [...] discards b2633f29cf 60: onsuccess: 1: Successful build after glibc: 2 commits discards d524014b1f 59: onsuccess: 1: Successful build after binutils: 2 commits discards ac75f88528 58: onsuccess: 1: Successful build after binutils: gdb: new [...] discards 09e22b9854 57: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] discards 432b667cf2 56: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards c54f98e06a 55: onsuccess: 1: Successful build after gcc/linux/glibc/qem [...] discards dcdc948aae 54: onsuccess: 1: Successful build after binutils/gcc/gdb: 8 [...] discards 97cf6a1fb6 53: onsuccess: 1: Successful build after binutils/gcc/gdb: 8 [...] discards 80eb211ade 52: onsuccess: 1: Successful build after binutils/gcc/gdb: 7 [...] discards 178c53fa7c 51: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 6ef61b5bd7 50: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] discards de8a8405e9 49: onsuccess: 1: Successful build after gcc/glibc: 5 commits discards 61141ffd79 48: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 980bc2f336 47: onsuccess: 1: Successful build after linux: 10 commits discards 300988487d 46: onsuccess: 1: Successful build after binutils/gdb: 2 commits discards 7b614c9bda 45: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 07b7dc147a 44: onsuccess: 1: Successful build after gcc/linux: 35 commits discards b19f2d3d45 43: onsuccess: 1: Successful build after gcc: LoongArch: Add [...] discards 7c86ec9125 42: onsuccess: 1: Successful build after gcc: libcpp: Implem [...] discards 298405d727 41: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards feeb840a26 40: onsuccess: 1: Successful build after linux/qemu: 147 commits discards 2a0da1f3d8 39: onsuccess: 1: Successful build after binutils/gcc/gdb/qe [...] discards 46a5122b9d 38: onsuccess: 1: Successful build after gcc/linux: 95 commits discards 825770ea47 37: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] discards ecf4ff7ede 36: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards fb25a8fa7d 35: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] discards b759b7deb7 34: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] discards ba5973f1f5 33: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 2636bc4a4c 32: onsuccess: 1: Successful build after gcc: 7 commits new 4f89fc0779 32: onsuccess: 1: Successful build after gcc: 7 commits new f5facb71af 33: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new ec2d5f9983 34: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] new 2a55f305b1 35: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] new a6c77e15a2 36: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 01f375448e 37: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] new 6ebcd83a3e 38: onsuccess: 1: Successful build after gcc/linux: 95 commits new 2e7521241a 39: onsuccess: 1: Successful build after binutils/gcc/gdb/qe [...] new dc19d5e7dd 40: onsuccess: 1: Successful build after linux/qemu: 147 commits new 60ac70bc2f 41: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 9b97c1c982 42: onsuccess: 1: Successful build after gcc: libcpp: Implem [...] new 4bc8ad629d 43: onsuccess: 1: Successful build after gcc: LoongArch: Add [...] new 86a221063b 44: onsuccess: 1: Successful build after gcc/linux: 35 commits new 0d4a76da22 45: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 77cf7c91b4 46: onsuccess: 1: Successful build after binutils/gdb: 2 commits new 2097b51b38 47: onsuccess: 1: Successful build after linux: 10 commits new 6c378e1bfe 48: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new bf50fc526b 49: onsuccess: 1: Successful build after gcc/glibc: 5 commits new 2fa39a4e3c 50: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] new d41e778c4f 51: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 2d4eaf4a58 52: onsuccess: 1: Successful build after binutils/gcc/gdb: 7 [...] new d9a42a9b0c 53: onsuccess: 1: Successful build after binutils/gcc/gdb: 8 [...] new a0466e14fa 54: onsuccess: 1: Successful build after binutils/gcc/gdb: 8 [...] new af99d60026 55: onsuccess: 1: Successful build after gcc/linux/glibc/qem [...] new 7616c66a04 56: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 13fab07880 57: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] new e1c23f0660 58: onsuccess: 1: Successful build after binutils: gdb: new [...] new 0275a67de8 59: onsuccess: 1: Successful build after binutils: 2 commits new 9e9e1b5a89 60: onsuccess: 1: Successful build after glibc: 2 commits new 2c93cfd1e2 61: onsuccess: 1: Successful build after binutils/gcc/gdb/qe [...] new 4e972cc7b2 62: onsuccess: 1: Successful build after binutils/gcc/gdb: 2 [...] new 5c89bd6b01 63: onsuccess: 1: Successful build after binutils/gcc/gdb: 8 [...] new 9ee4c14333 64: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new a4998a8e89 65: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 5a696017a4 66: onsuccess: 1: Successful build after gcc/glibc: 10 commits new 4e01b5d18d 67: onsuccess: 1: Successful build after binutils/gcc/gdb: 1 [...] new 25aa81d421 68: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new affdb1fc66 69: onsuccess: 1: Successful build after binutils/gcc/gdb: 5 [...] new 691f579b32 70: onsuccess: 1: Successful build after binutils/gcc/gdb: 4 [...] new 2042d64d2d 71: onsuccess: 1: Successful build after gcc/glibc: 3 commits new ac73a29917 72: onsuccess: 1: Successful build after linux: 12 commits new 1e9dcbec2a 73: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new cbd4d3ea82 74: onsuccess: 1: Successful build after binutils/gdb: 2 commits new 3d919e0c15 75: onsuccess: 1: Successful build after linux: 44 commits new 42a5610454 76: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 7f78ed4513 77: onsuccess: 1: Successful build after gcc/linux/glibc: 22 [...] new 7ca0251a7f 78: onsuccess: 1: Successful build after binutils/gcc/gdb: 4 [...] new e6e49e9bda 79: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] new 2fa4877662 80: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] new 90a10c1b83 81: onsuccess: 1: Successful build after binutils/gcc/gdb: 6 [...] new 03bdf6026a 82: onsuccess: 1: Successful build after binutils/gcc/gdb: 1 [...] new 13eb157509 83: onsuccess: 1: Success after binutils/gcc/glibc/gdb: 17 commits new 8ba5c35487 84: onsuccess: 1: Success after binutils/gcc/linux/gdb: 68 commits new 2159099173 85: onsuccess: 1: Success after binutils/gcc/glibc/gdb/qemu: [...] new f07220f727 86: onsuccess: 1: Success after binutils/gcc/gdb: 7 commits new a56ab637a1 87: onsuccess: 1: Success after binutils/gcc/gdb: 14 commits new ecd931ac05 88: onsuccess: 1: Success after gcc/linux/qemu: 149 commits new 4be74f59f7 89: onsuccess: 1: Success after binutils/gcc/gdb: 5 commits new 4ae5542639 90: onsuccess: 1: Success after binutils/gcc/gdb: 19 commits new 13ede4ae7b 91: onsuccess: 1: Success after binutils/gcc/gdb: 8 commits new db77d7532e 92: onsuccess: 1: Success after binutils/gcc/linux/gdb/qemu: [...] new 998240cfec 93: onsuccess: 1: Success after binutils/gcc/linux/gdb: 88 commits new 8bc5374335 94: onsuccess: 1: Success after gcc: openmp: Partial OpenMP [...] new 8d99ceeb48 95: onsuccess: #2070: 1: Success after basepoints/gcc-13-238 [...] new 12dcce9a9e 96: onsuccess: #2071: 1: Success after gcc/linux: 56 commits new 017f7fc98e 97: onsuccess: #2072: 1: Success after binutils/gcc/gdb: 3 commits new 08eab8fea5 98: onsuccess: #2073: 1: Success after gcc/linux: 11 commits new 7a4c4b96f8 99: onsuccess: #2074: 1: Success after baseline build: no ne [...] new f548717b14 100: onsuccess: #2077: 1: Success after binutils/gcc/linux/g [...] new b44ed66182 101: onsuccess: #2130: 1: Success after binutils: 81 commits new 3ae42609ca 102: onsuccess: #2133: 1: Success after gdb-12-branchpoint-1 [...] new 6c59fe2d9a 103: onsuccess: #2135: 1: Success after gcc/linux/glibc/gdb/ [...] new bdd2fc6b69 104: onsuccess: #2136: 1: Success after binutils/gcc/gdb: 3 commits new 816014f239 105: onsuccess: #2137: 1: Success after basepoints/gcc-13-27 [...] new b648a4feeb 106: onsuccess: #2138: 1: Success after binutils/gcc/glibc/g [...] new 59ab2bf2d3 107: onsuccess: #2139: 1: Success after binutils/gcc/gdb: 3 commits new 1b12028218 108: onsuccess: #2140: 1: Success after binutils/gcc/gdb: 5 commits new d9e5c78f28 109: onsuccess: #2141: 1: Success after gcc/glibc: 6 commits new 812c73254f 110: onsuccess: #2142: 1: Success after binutils/gcc/glibc/g [...] new 6eb45c43d5 111: onsuccess: #2143: 1: Success after binutils/gcc/linux/g [...] new f78fdd8705 112: onsuccess: #2144: 1: Success after binutils/gcc/glibc/g [...] new 7a4e195e7b 113: onsuccess: #2145: 1: Success after binutils/gcc/glibc/g [...] new 3c075114e2 114: onsuccess: #2146: 1: Success after binutils/gcc/glibc/g [...] new 3121157775 115: onsuccess: #2147: 1: Success after binutils/linux/glibc [...] new 8ea386a8b3 116: onsuccess: #2148: 1: Success after binutils/gcc/gdb: 7 commits new 8cfa5cf598 117: onsuccess: #2150: 1: Success after binutils/gcc/glibc/g [...] new c716b734a3 118: onsuccess: #2151: 1: Success after binutils/gcc/linux/g [...] new fa4ae317c5 119: onsuccess: #2154: 1: Success after binutils/gcc/linux/g [...] new 0e0643a22f 120: onsuccess: #2155: 1: Success after binutils/gcc/linux/g [...] new b584d7c053 121: onsuccess: #2156: 1: Success after binutils/gcc/linux/g [...] new 6b8403c53a 122: onsuccess: #2157: 1: Success after binutils/gcc/gdb: 6 commits new d009d8031a 123: onsuccess: #2158: 1: Success after basepoints/gcc-13-28 [...] new 609ba57d87 124: onsuccess: #2159: 1: Success after linux: 23 commits new 4f0bef0d83 125: onsuccess: #2160: 1: Success after binutils/gcc/linux/g [...] new 30311bb512 126: onsuccess: #2161: 1: Success after basepoints/gcc-13-28 [...] new 9998ad0509 127: onsuccess: #2162: 1: Success after gcc: 9 commits new 6a6aa2c031 128: onsuccess: #2163: 1: Success after linux: 23 commits new 07e7aba994 129: onsuccess: #2164: 1: Success after binutils/gcc/linux/g [...] new b4daae58f9 130: onsuccess: #2165: 1: Success after binutils/gcc/gdb: 32 [...] new ffebaee388 131: onsuccess: #2166: 1: Success after binutils/gcc/gdb: 12 [...] new 3771a18e08 132: onsuccess: #2167: 1: Success after binutils/gcc/glibc/g [...] new ce9b73e98c 133: onsuccess: #2168: 1: Success after binutils/gcc/linux/g [...]
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 (a68d06b3aa) \ 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 1720 -> 1752 bytes 02-prepare_abe/console.log.xz | Bin 2748 -> 2736 bytes 03-build_abe-binutils/console.log.xz | Bin 30708 -> 30960 bytes 04-build_abe-stage1/console.log.xz | Bin 72628 -> 72892 bytes 06-build_abe-linux/console.log.xz | Bin 8316 -> 8756 bytes 07-build_abe-glibc/console.log.xz | Bin 239716 -> 239876 bytes 08-build_abe-stage2/console.log.xz | Bin 203036 -> 204656 bytes 09-build_abe-gdb/console.log.xz | Bin 37856 -> 38024 bytes 10-build_abe-qemu/console.log.xz | Bin 32684 -> 33136 bytes 11-build_abe-dejagnu/console.log.xz | Bin 3900 -> 3904 bytes 12-build_abe-check_gcc/console.log.xz | Bin 2540 -> 2464 bytes 13-check_regression/console.log.xz | Bin 188948 -> 184900 bytes 13-check_regression/extra-bisect-params | 2 +- 13-check_regression/fails.sum | 12 +- 13-check_regression/mail-body.txt | 141 +- 13-check_regression/results.compare | 135 +- 13-check_regression/results.compare2 | 3002 +- 13-check_regression/results.regressions | 85 +- 14-update_baseline/console.log | 68 +- 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 | 143 +- mail/mail-subject.txt | 2 +- manifest.sh | 38 +- results | 85 +- sumfiles/g++.log.xz | Bin 3430312 -> 3412428 bytes sumfiles/g++.sum | 101 +- sumfiles/gcc.log.xz | Bin 3152532 -> 3032440 bytes sumfiles/gcc.sum | 45317 ++---------------------------- sumfiles/gfortran.log.xz | Bin 1028452 -> 1030084 bytes sumfiles/gfortran.sum | 10 +- sumfiles/libatomic.log.xz | Bin 2296 -> 2292 bytes sumfiles/libatomic.sum | 2 +- sumfiles/libgomp.log.xz | Bin 202420 -> 202052 bytes sumfiles/libgomp.sum | 2 +- sumfiles/libitm.log.xz | Bin 2660 -> 2656 bytes sumfiles/libitm.sum | 2 +- sumfiles/libstdc++.log.xz | Bin 417972 -> 422748 bytes sumfiles/libstdc++.sum | 6 +- 43 files changed, 3305 insertions(+), 45860 deletions(-)