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 d400e3f167 131: onsuccess: #2166: 1: Success after binutils/gcc/gdb: 12 [...] discards b0bddfa744 130: onsuccess: #2165: 1: Success after binutils/gcc/gdb: 32 [...] discards daa0f61377 129: onsuccess: #2164: 1: Success after binutils/gcc/linux/g [...] discards ec1112a2c3 128: onsuccess: #2163: 1: Success after linux: 23 commits discards 0cb108d935 127: onsuccess: #2162: 1: Success after gcc: 9 commits discards cf45da1c60 126: onsuccess: #2161: 1: Success after basepoints/gcc-13-28 [...] discards 9139d21527 125: onsuccess: #2160: 1: Success after binutils/gcc/linux/g [...] discards 485903251b 124: onsuccess: #2159: 1: Success after linux: 23 commits discards 1952055986 123: onsuccess: #2158: 1: Success after basepoints/gcc-13-28 [...] discards 8f075382e7 122: onsuccess: #2157: 1: Success after binutils/gcc/gdb: 6 commits discards a3cdeb16c9 121: onsuccess: #2156: 1: Success after binutils/gcc/linux/g [...] discards 4650523382 120: onsuccess: #2155: 1: Success after binutils/gcc/linux/g [...] discards 54135f5b51 119: onsuccess: #2154: 1: Success after binutils/gcc/linux/g [...] discards 6d02b44539 118: onsuccess: #2151: 1: Success after binutils/gcc/linux/g [...] discards 1b6f2c37fe 117: onsuccess: #2150: 1: Success after binutils/gcc/glibc/g [...] discards ab6b74e8f5 116: onsuccess: #2148: 1: Success after binutils/gcc/gdb: 7 commits discards dcf6020874 115: onsuccess: #2147: 1: Success after binutils/linux/glibc [...] discards 668c42337e 114: onsuccess: #2146: 1: Success after binutils/gcc/glibc/g [...] discards 78d7df70f9 113: onsuccess: #2145: 1: Success after binutils/gcc/glibc/g [...] discards 8a3d685dca 112: onsuccess: #2144: 1: Success after binutils/gcc/glibc/g [...] discards 8263d34c7b 111: onsuccess: #2143: 1: Success after binutils/gcc/linux/g [...] discards 1ba7365101 110: onsuccess: #2142: 1: Success after binutils/gcc/glibc/g [...] discards d5f1197585 109: onsuccess: #2141: 1: Success after gcc/glibc: 6 commits discards 7c7fba77af 108: onsuccess: #2140: 1: Success after binutils/gcc/gdb: 5 commits discards 357a2e93ef 107: onsuccess: #2139: 1: Success after binutils/gcc/gdb: 3 commits discards c72dfcc6de 106: onsuccess: #2138: 1: Success after binutils/gcc/glibc/g [...] discards 86d30cd892 105: onsuccess: #2137: 1: Success after basepoints/gcc-13-27 [...] discards 3456b26e41 104: onsuccess: #2136: 1: Success after binutils/gcc/gdb: 3 commits discards 25482e7117 103: onsuccess: #2135: 1: Success after gcc/linux/glibc/gdb/ [...] discards d3d878f4bd 102: onsuccess: #2133: 1: Success after gdb-12-branchpoint-1 [...] discards 30dc8b218a 101: onsuccess: #2130: 1: Success after binutils: 81 commits discards f8e90c185b 100: onsuccess: #2077: 1: Success after binutils/gcc/linux/g [...] discards 0b9d0d5aa1 99: onsuccess: #2074: 1: Success after baseline build: no ne [...] discards 17a874f902 98: onsuccess: #2073: 1: Success after gcc/linux: 11 commits discards cbfe0a5f1a 97: onsuccess: #2072: 1: Success after binutils/gcc/gdb: 3 commits discards f8e966ca15 96: onsuccess: #2071: 1: Success after gcc/linux: 56 commits discards 8615725fd8 95: onsuccess: #2070: 1: Success after basepoints/gcc-13-238 [...] discards eb24c7feac 94: onsuccess: 1: Success after gcc: openmp: Partial OpenMP [...] discards 03aea9493e 93: onsuccess: 1: Success after binutils/gcc/linux/gdb: 88 commits discards f56a770633 92: onsuccess: 1: Success after binutils/gcc/linux/gdb/qemu: [...] discards 82b28d1c67 91: onsuccess: 1: Success after binutils/gcc/gdb: 8 commits discards 43902df0b9 90: onsuccess: 1: Success after binutils/gcc/gdb: 19 commits discards 9cf174d8c1 89: onsuccess: 1: Success after binutils/gcc/gdb: 5 commits discards c51292e9c2 88: onsuccess: 1: Success after gcc/linux/qemu: 149 commits discards ee14630f07 87: onsuccess: 1: Success after binutils/gcc/gdb: 14 commits discards 1421a0edad 86: onsuccess: 1: Success after binutils/gcc/gdb: 7 commits discards 0e1f60f504 85: onsuccess: 1: Success after binutils/gcc/glibc/gdb/qemu: [...] discards a0b436a73d 84: onsuccess: 1: Success after binutils/gcc/linux/gdb: 68 commits discards 8070e3e33d 83: onsuccess: 1: Success after binutils/gcc/glibc/gdb: 17 commits discards 7e40b5fba7 82: onsuccess: 1: Successful build after binutils/gcc/gdb: 1 [...] discards fbb50e2288 81: onsuccess: 1: Successful build after binutils/gcc/gdb: 6 [...] discards 97a30b31a9 80: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] discards bd9912ace6 79: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] discards 4379bcb34b 78: onsuccess: 1: Successful build after binutils/gcc/gdb: 4 [...] discards ff83d9e933 77: onsuccess: 1: Successful build after gcc/linux/glibc: 22 [...] discards fa623ba090 76: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 3a12161b6b 75: onsuccess: 1: Successful build after linux: 44 commits discards e3522c38da 74: onsuccess: 1: Successful build after binutils/gdb: 2 commits discards 26557bde51 73: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 87c53e50ae 72: onsuccess: 1: Successful build after linux: 12 commits discards 5603ae8e8f 71: onsuccess: 1: Successful build after gcc/glibc: 3 commits discards c8235d29ea 70: onsuccess: 1: Successful build after binutils/gcc/gdb: 4 [...] discards 393d89d1a9 69: onsuccess: 1: Successful build after binutils/gcc/gdb: 5 [...] discards 6778068f57 68: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards b1ea57ff58 67: onsuccess: 1: Successful build after binutils/gcc/gdb: 1 [...] discards 9aeef1c0b3 66: onsuccess: 1: Successful build after gcc/glibc: 10 commits discards fb0dc5718b 65: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards db5aa3c086 64: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards d2668ea03e 63: onsuccess: 1: Successful build after binutils/gcc/gdb: 8 [...] discards c7ae312c7e 62: onsuccess: 1: Successful build after binutils/gcc/gdb: 2 [...] discards ada84a0dde 61: onsuccess: 1: Successful build after binutils/gcc/gdb/qe [...] discards 67caab9ff6 60: onsuccess: 1: Successful build after glibc: 2 commits discards 85051b45e5 59: onsuccess: 1: Successful build after binutils: 2 commits discards 9aeccda6b6 58: onsuccess: 1: Successful build after binutils: gdb: new [...] discards ababf461b6 57: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] discards e62c4352bd 56: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards eeddb6a6c0 55: onsuccess: 1: Successful build after gcc/linux/glibc/qem [...] discards 0e491c0edb 54: onsuccess: 1: Successful build after binutils/gcc/gdb: 8 [...] discards b6190abdcd 53: onsuccess: 1: Successful build after binutils/gcc/gdb: 8 [...] discards 685496457f 52: onsuccess: 1: Successful build after binutils/gcc/gdb: 7 [...] discards 6364668d54 51: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 194716b49a 50: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] discards f7a426858c 49: onsuccess: 1: Successful build after gcc/glibc: 5 commits discards 44073e6918 48: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 267ce2de79 47: onsuccess: 1: Successful build after linux: 10 commits discards 8252a4cacf 46: onsuccess: 1: Successful build after binutils/gdb: 2 commits discards bddda05728 45: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 646bd1ccbe 44: onsuccess: 1: Successful build after gcc/linux: 35 commits discards 986a0ee028 43: onsuccess: 1: Successful build after gcc: LoongArch: Add [...] discards 7de583bde2 42: onsuccess: 1: Successful build after gcc: libcpp: Implem [...] discards 6b490230d2 41: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 82cc0185cf 40: onsuccess: 1: Successful build after linux/qemu: 147 commits discards 0d1ad80f52 39: onsuccess: 1: Successful build after binutils/gcc/gdb/qe [...] discards 1e516d7491 38: onsuccess: 1: Successful build after gcc/linux: 95 commits discards 03c77aa94f 37: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] discards 1f9878a702 36: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 8b2f8373ba 35: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] discards 01edc8ac8e 34: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] discards ede6946f7f 33: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 0b5610e1e8 32: onsuccess: 1: Successful build after gcc: 7 commits discards 85bb5b0261 31: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] new 2a5381fdca 31: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] new 2636bc4a4c 32: onsuccess: 1: Successful build after gcc: 7 commits new ba5973f1f5 33: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new b759b7deb7 34: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] new fb25a8fa7d 35: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] new ecf4ff7ede 36: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 825770ea47 37: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] new 46a5122b9d 38: onsuccess: 1: Successful build after gcc/linux: 95 commits new 2a0da1f3d8 39: onsuccess: 1: Successful build after binutils/gcc/gdb/qe [...] new feeb840a26 40: onsuccess: 1: Successful build after linux/qemu: 147 commits new 298405d727 41: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 7c86ec9125 42: onsuccess: 1: Successful build after gcc: libcpp: Implem [...] new b19f2d3d45 43: onsuccess: 1: Successful build after gcc: LoongArch: Add [...] new 07b7dc147a 44: onsuccess: 1: Successful build after gcc/linux: 35 commits new 7b614c9bda 45: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 300988487d 46: onsuccess: 1: Successful build after binutils/gdb: 2 commits new 980bc2f336 47: onsuccess: 1: Successful build after linux: 10 commits new 61141ffd79 48: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new de8a8405e9 49: onsuccess: 1: Successful build after gcc/glibc: 5 commits new 6ef61b5bd7 50: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] new 178c53fa7c 51: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 80eb211ade 52: onsuccess: 1: Successful build after binutils/gcc/gdb: 7 [...] new 97cf6a1fb6 53: onsuccess: 1: Successful build after binutils/gcc/gdb: 8 [...] new dcdc948aae 54: onsuccess: 1: Successful build after binutils/gcc/gdb: 8 [...] new c54f98e06a 55: onsuccess: 1: Successful build after gcc/linux/glibc/qem [...] new 432b667cf2 56: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 09e22b9854 57: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] new ac75f88528 58: onsuccess: 1: Successful build after binutils: gdb: new [...] new d524014b1f 59: onsuccess: 1: Successful build after binutils: 2 commits new b2633f29cf 60: onsuccess: 1: Successful build after glibc: 2 commits new 87189513f0 61: onsuccess: 1: Successful build after binutils/gcc/gdb/qe [...] new 6a3a50e8d5 62: onsuccess: 1: Successful build after binutils/gcc/gdb: 2 [...] new c44ac29db1 63: onsuccess: 1: Successful build after binutils/gcc/gdb: 8 [...] new 5341a70a02 64: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new e354adbd4d 65: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 69068b0a4a 66: onsuccess: 1: Successful build after gcc/glibc: 10 commits new 14b36b34d5 67: onsuccess: 1: Successful build after binutils/gcc/gdb: 1 [...] new 0399b0f387 68: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new f22c4460f3 69: onsuccess: 1: Successful build after binutils/gcc/gdb: 5 [...] new c08cefc173 70: onsuccess: 1: Successful build after binutils/gcc/gdb: 4 [...] new d6e48727fc 71: onsuccess: 1: Successful build after gcc/glibc: 3 commits new 1cb566e6e5 72: onsuccess: 1: Successful build after linux: 12 commits new 5fdd0e59a7 73: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 8b1a4d8cef 74: onsuccess: 1: Successful build after binutils/gdb: 2 commits new ffe4c0c987 75: onsuccess: 1: Successful build after linux: 44 commits new 1f230f3011 76: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new e6c7dee319 77: onsuccess: 1: Successful build after gcc/linux/glibc: 22 [...] new 63521fb157 78: onsuccess: 1: Successful build after binutils/gcc/gdb: 4 [...] new 164b024806 79: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] new f9f1b9606b 80: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] new cc789dba3e 81: onsuccess: 1: Successful build after binutils/gcc/gdb: 6 [...] new 348988ae9b 82: onsuccess: 1: Successful build after binutils/gcc/gdb: 1 [...] new 86a120e59a 83: onsuccess: 1: Success after binutils/gcc/glibc/gdb: 17 commits new 02b4b5b2bc 84: onsuccess: 1: Success after binutils/gcc/linux/gdb: 68 commits new 41cdeecb7e 85: onsuccess: 1: Success after binutils/gcc/glibc/gdb/qemu: [...] new dea669266e 86: onsuccess: 1: Success after binutils/gcc/gdb: 7 commits new 66ffe13bf4 87: onsuccess: 1: Success after binutils/gcc/gdb: 14 commits new a492291dc0 88: onsuccess: 1: Success after gcc/linux/qemu: 149 commits new b30e5799bb 89: onsuccess: 1: Success after binutils/gcc/gdb: 5 commits new 387e2581ac 90: onsuccess: 1: Success after binutils/gcc/gdb: 19 commits new 511ac95b5b 91: onsuccess: 1: Success after binutils/gcc/gdb: 8 commits new 23b6b99c57 92: onsuccess: 1: Success after binutils/gcc/linux/gdb/qemu: [...] new 6fb36d610f 93: onsuccess: 1: Success after binutils/gcc/linux/gdb: 88 commits new 2a2e04f9bb 94: onsuccess: 1: Success after gcc: openmp: Partial OpenMP [...] new 44ce4ae5ec 95: onsuccess: #2070: 1: Success after basepoints/gcc-13-238 [...] new 054ea8fc9b 96: onsuccess: #2071: 1: Success after gcc/linux: 56 commits new 95f34f2050 97: onsuccess: #2072: 1: Success after binutils/gcc/gdb: 3 commits new 3dd6a632e1 98: onsuccess: #2073: 1: Success after gcc/linux: 11 commits new b128a5d19e 99: onsuccess: #2074: 1: Success after baseline build: no ne [...] new 246ed10e68 100: onsuccess: #2077: 1: Success after binutils/gcc/linux/g [...] new 62da89aa7f 101: onsuccess: #2130: 1: Success after binutils: 81 commits new be5901ef06 102: onsuccess: #2133: 1: Success after gdb-12-branchpoint-1 [...] new 0aac9cab77 103: onsuccess: #2135: 1: Success after gcc/linux/glibc/gdb/ [...] new c6f4eef030 104: onsuccess: #2136: 1: Success after binutils/gcc/gdb: 3 commits new 0a7e315bb7 105: onsuccess: #2137: 1: Success after basepoints/gcc-13-27 [...] new 8ef0bd5a90 106: onsuccess: #2138: 1: Success after binutils/gcc/glibc/g [...] new 7bacef81c1 107: onsuccess: #2139: 1: Success after binutils/gcc/gdb: 3 commits new fae69b4f72 108: onsuccess: #2140: 1: Success after binutils/gcc/gdb: 5 commits new 44eeb49be2 109: onsuccess: #2141: 1: Success after gcc/glibc: 6 commits new 534552f4f8 110: onsuccess: #2142: 1: Success after binutils/gcc/glibc/g [...] new 982a7d724e 111: onsuccess: #2143: 1: Success after binutils/gcc/linux/g [...] new 27fe67a3b8 112: onsuccess: #2144: 1: Success after binutils/gcc/glibc/g [...] new 92e1fe62a6 113: onsuccess: #2145: 1: Success after binutils/gcc/glibc/g [...] new bbf3a6589a 114: onsuccess: #2146: 1: Success after binutils/gcc/glibc/g [...] new f7e26974a0 115: onsuccess: #2147: 1: Success after binutils/linux/glibc [...] new 30d3fd7263 116: onsuccess: #2148: 1: Success after binutils/gcc/gdb: 7 commits new 22d15946ca 117: onsuccess: #2150: 1: Success after binutils/gcc/glibc/g [...] new 28b5d78d03 118: onsuccess: #2151: 1: Success after binutils/gcc/linux/g [...] new 2e75f075d8 119: onsuccess: #2154: 1: Success after binutils/gcc/linux/g [...] new 5a1de9abb3 120: onsuccess: #2155: 1: Success after binutils/gcc/linux/g [...] new df5d4132c8 121: onsuccess: #2156: 1: Success after binutils/gcc/linux/g [...] new f75436aebf 122: onsuccess: #2157: 1: Success after binutils/gcc/gdb: 6 commits new 6a7ebca127 123: onsuccess: #2158: 1: Success after basepoints/gcc-13-28 [...] new d084124194 124: onsuccess: #2159: 1: Success after linux: 23 commits new 125a8a30bc 125: onsuccess: #2160: 1: Success after binutils/gcc/linux/g [...] new 47ab23d631 126: onsuccess: #2161: 1: Success after basepoints/gcc-13-28 [...] new 31f407bd1f 127: onsuccess: #2162: 1: Success after gcc: 9 commits new 5ffedbc1f6 128: onsuccess: #2163: 1: Success after linux: 23 commits new dd4decf4cc 129: onsuccess: #2164: 1: Success after binutils/gcc/linux/g [...] new 1a28ee7673 130: onsuccess: #2165: 1: Success after binutils/gcc/gdb: 32 [...] new 93a1bb7bcd 131: onsuccess: #2166: 1: Success after binutils/gcc/gdb: 12 [...] new a68d06b3aa 132: onsuccess: #2167: 1: Success after binutils/gcc/glibc/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 (d400e3f167) \ 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 1688 -> 1720 bytes 02-prepare_abe/console.log.xz | Bin 2736 -> 2748 bytes 03-build_abe-binutils/console.log.xz | Bin 30388 -> 30708 bytes 04-build_abe-stage1/console.log.xz | Bin 72592 -> 72628 bytes 05-clean_sysroot/console.log.xz | Bin 328 -> 328 bytes 06-build_abe-linux/console.log.xz | Bin 8296 -> 8316 bytes 07-build_abe-glibc/console.log.xz | Bin 239696 -> 239716 bytes 08-build_abe-stage2/console.log.xz | Bin 203040 -> 203036 bytes 09-build_abe-gdb/console.log.xz | Bin 37516 -> 37856 bytes 10-build_abe-qemu/console.log.xz | Bin 31664 -> 32684 bytes 11-build_abe-dejagnu/console.log.xz | Bin 3876 -> 3900 bytes 12-build_abe-check_gcc/console.log.xz | Bin 2984 -> 2540 bytes 13-check_regression/console.log.xz | Bin 25756 -> 188948 bytes 13-check_regression/extra-bisect-params | 2 +- 13-check_regression/fails.sum | 123 +- 13-check_regression/mail-body.txt | 202 +- 13-check_regression/results.compare | 81 +- 13-check_regression/results.compare2 | 48077 +++++++++++++++++++++++++++--- 13-check_regression/results.regressions | 56 +- 14-update_baseline/console.log | 70 +- dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- git/gdb_rev | 2 +- git/glibc_rev | 2 +- git/qemu_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 204 +- mail/mail-subject.txt | 2 +- manifest.sh | 42 +- results | 56 +- sumfiles/g++.log.xz | Bin 3410228 -> 3430312 bytes sumfiles/g++.sum | 270 +- sumfiles/gcc.log.xz | Bin 3028004 -> 3152532 bytes sumfiles/gcc.sum | 45761 ++++++++++++++++++++++++++-- sumfiles/gfortran.log.xz | Bin 1031244 -> 1028452 bytes sumfiles/gfortran.sum | 42 +- sumfiles/libatomic.log.xz | Bin 2292 -> 2296 bytes sumfiles/libatomic.sum | 4 +- sumfiles/libgomp.log.xz | Bin 202020 -> 202420 bytes sumfiles/libgomp.sum | 16 +- sumfiles/libitm.log.xz | Bin 2668 -> 2660 bytes sumfiles/libitm.sum | 6 +- sumfiles/libstdc++.log.xz | Bin 417352 -> 417972 bytes sumfiles/libstdc++.sum | 14 +- 45 files changed, 87681 insertions(+), 7361 deletions(-)