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 25eb8ef8dc 157: onsuccess: #2192: 1: Success after binutils/gcc/gdb: 8 commits discards 46805b8f4b 156: onsuccess: #2191: 1: Success after binutils/gcc/linux/g [...] discards efb9c5d4e3 155: onsuccess: #2190: 1: Success after binutils/gcc/linux/g [...] discards be6c3e297e 154: onsuccess: #2189: 1: Success after binutils/gcc/gdb: 18 [...] discards 1aca0ae517 153: onsuccess: #2188: 1: Success after binutils/gcc/gdb: 3 commits discards a84bd4fd9a 152: onsuccess: #2187: 1: Success after gcc/linux/glibc: 22 commits discards 4c5d0c6d1e 151: onsuccess: #2186: 1: Success after gcc: 2 commits discards c0eb4d2512 150: onsuccess: #2185: 1: Success after gcc: 3 commits discards f88483dd79 149: onsuccess: #2184: 1: Success after binutils/gcc/linux/g [...] discards 76a6be61d0 148: onsuccess: #2183: 1: Success after gcc/linux/glibc: 64 commits discards eea98d80a6 147: onsuccess: #2182: 1: Success after binutils/gcc/gdb: 18 [...] discards e3a2c90c9c 146: onsuccess: #2181: 1: Success after binutils/glibc/gdb: [...] discards 37b8037a7a 145: onsuccess: #2180: 1: Success after binutils/gcc/linux/g [...] discards c37396202d 144: onsuccess: #2179: 1: Success after binutils/gcc/linux/g [...] discards 1ea3dcfb33 143: onsuccess: #2178: 1: Success after binutils/gcc/gdb/qem [...] discards 5c437441eb 142: onsuccess: #2177: 1: Success after gcc/glibc: 4 commits discards 1a382759a7 141: onsuccess: #2176: 1: Success after binutils/gcc/gdb: 6 commits discards 59d966fef5 140: onsuccess: #2175: 1: Success after binutils/gcc/linux/g [...] discards b6bf550c15 139: onsuccess: #2174: 1: Success after binutils/gcc/gdb: 13 [...] discards 72b724315c 138: onsuccess: #2173: 1: Success after binutils/gcc/gdb: 5 commits discards f669c09e2f 137: onsuccess: #2172: 1: Success after binutils/gcc/linux/g [...] discards 164a593580 136: onsuccess: #2171: 1: Success after binutils/gcc/gdb/qem [...] discards 784d2196a4 135: onsuccess: #2170: 1: Success after gcc/linux/qemu: 63 commits discards f204d97362 134: onsuccess: #2169: 1: Success after binutils/gcc/gdb: 13 [...] discards a1b5b6970f 133: onsuccess: #2168: 1: Success after binutils/gcc/linux/g [...] discards 6b005e6f90 132: onsuccess: #2167: 1: Success after binutils/gcc/glibc/g [...] discards 1755ab453b 131: onsuccess: #2166: 1: Success after binutils/gcc/gdb: 12 [...] discards 656e61d493 130: onsuccess: #2165: 1: Success after binutils/gcc/gdb: 32 [...] discards 334927ee5e 129: onsuccess: #2164: 1: Success after binutils/gcc/linux/g [...] discards 2e31b3a5de 128: onsuccess: #2163: 1: Success after linux: 23 commits discards 704ec862f4 127: onsuccess: #2162: 1: Success after gcc: 9 commits discards 5968918e1b 126: onsuccess: #2161: 1: Success after basepoints/gcc-13-28 [...] discards 873cd7937f 125: onsuccess: #2160: 1: Success after binutils/gcc/linux/g [...] discards a0126ed71f 124: onsuccess: #2159: 1: Success after linux: 23 commits discards 0859b95d96 123: onsuccess: #2158: 1: Success after basepoints/gcc-13-28 [...] discards 713d0a78d8 122: onsuccess: #2157: 1: Success after binutils/gcc/gdb: 6 commits discards 6bbc636a40 121: onsuccess: #2156: 1: Success after binutils/gcc/linux/g [...] discards f2171341b9 120: onsuccess: #2155: 1: Success after binutils/gcc/linux/g [...] discards 625546d305 119: onsuccess: #2154: 1: Success after binutils/gcc/linux/g [...] discards 42664ac6a2 118: onsuccess: #2151: 1: Success after binutils/gcc/linux/g [...] discards e1e996992f 117: onsuccess: #2150: 1: Success after binutils/gcc/glibc/g [...] discards aa01867ca9 116: onsuccess: #2148: 1: Success after binutils/gcc/gdb: 7 commits discards 602c538d60 115: onsuccess: #2147: 1: Success after binutils/linux/glibc [...] discards 1f76398cab 114: onsuccess: #2146: 1: Success after binutils/gcc/glibc/g [...] discards 7423c7f638 113: onsuccess: #2145: 1: Success after binutils/gcc/glibc/g [...] discards 0f57d3a769 112: onsuccess: #2144: 1: Success after binutils/gcc/glibc/g [...] discards 36faf4da03 111: onsuccess: #2143: 1: Success after binutils/gcc/linux/g [...] discards 983ee7e6c8 110: onsuccess: #2142: 1: Success after binutils/gcc/glibc/g [...] discards 38dead2eb8 109: onsuccess: #2141: 1: Success after gcc/glibc: 6 commits discards 7a75d8fc1c 108: onsuccess: #2140: 1: Success after binutils/gcc/gdb: 5 commits discards 363ba30318 107: onsuccess: #2139: 1: Success after binutils/gcc/gdb: 3 commits discards 96fd1ae7ee 106: onsuccess: #2138: 1: Success after binutils/gcc/glibc/g [...] discards baed0756b9 105: onsuccess: #2137: 1: Success after basepoints/gcc-13-27 [...] discards ef7784f6a5 104: onsuccess: #2136: 1: Success after binutils/gcc/gdb: 3 commits discards 8602eb7df0 103: onsuccess: #2135: 1: Success after gcc/linux/glibc/gdb/ [...] discards e18983a345 102: onsuccess: #2133: 1: Success after gdb-12-branchpoint-1 [...] discards a9cd644924 101: onsuccess: #2130: 1: Success after binutils: 81 commits discards ae6b79e362 100: onsuccess: #2077: 1: Success after binutils/gcc/linux/g [...] discards 61f546aeec 99: onsuccess: #2074: 1: Success after baseline build: no ne [...] discards e527246415 98: onsuccess: #2073: 1: Success after gcc/linux: 11 commits discards 5261cd439b 97: onsuccess: #2072: 1: Success after binutils/gcc/gdb: 3 commits discards 15eefe67df 96: onsuccess: #2071: 1: Success after gcc/linux: 56 commits discards 4404f4de81 95: onsuccess: #2070: 1: Success after basepoints/gcc-13-238 [...] discards cf1133abdd 94: onsuccess: 1: Success after gcc: openmp: Partial OpenMP [...] discards d45a595d05 93: onsuccess: 1: Success after binutils/gcc/linux/gdb: 88 commits discards 046ddbd95d 92: onsuccess: 1: Success after binutils/gcc/linux/gdb/qemu: [...] discards 96d062a69c 91: onsuccess: 1: Success after binutils/gcc/gdb: 8 commits discards 78d03360df 90: onsuccess: 1: Success after binutils/gcc/gdb: 19 commits discards b23883226d 89: onsuccess: 1: Success after binutils/gcc/gdb: 5 commits discards 20a97b86f8 88: onsuccess: 1: Success after gcc/linux/qemu: 149 commits discards 07e1e4b8a3 87: onsuccess: 1: Success after binutils/gcc/gdb: 14 commits discards 6fde556902 86: onsuccess: 1: Success after binutils/gcc/gdb: 7 commits discards afbcdc1e47 85: onsuccess: 1: Success after binutils/gcc/glibc/gdb/qemu: [...] discards 91eee9321c 84: onsuccess: 1: Success after binutils/gcc/linux/gdb: 68 commits discards 4a63e188c2 83: onsuccess: 1: Success after binutils/gcc/glibc/gdb: 17 commits discards ec2a676b9c 82: onsuccess: 1: Successful build after binutils/gcc/gdb: 1 [...] discards 1985fee0de 81: onsuccess: 1: Successful build after binutils/gcc/gdb: 6 [...] discards fd1e3f2303 80: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] discards 6baaa2c2bb 79: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] discards d28b8248fb 78: onsuccess: 1: Successful build after binutils/gcc/gdb: 4 [...] discards 0a9e06a5ec 77: onsuccess: 1: Successful build after gcc/linux/glibc: 22 [...] discards ab54080669 76: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 19e855aa20 75: onsuccess: 1: Successful build after linux: 44 commits discards 9b9a2188b5 74: onsuccess: 1: Successful build after binutils/gdb: 2 commits discards 035cc42d97 73: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards a73ce032b2 72: onsuccess: 1: Successful build after linux: 12 commits discards db94db49e4 71: onsuccess: 1: Successful build after gcc/glibc: 3 commits discards 69a9e95dcb 70: onsuccess: 1: Successful build after binutils/gcc/gdb: 4 [...] discards 3b90ec1437 69: onsuccess: 1: Successful build after binutils/gcc/gdb: 5 [...] discards 4353660b0c 68: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards f6ec6051bb 67: onsuccess: 1: Successful build after binutils/gcc/gdb: 1 [...] discards d217d796bb 66: onsuccess: 1: Successful build after gcc/glibc: 10 commits discards c99eef1102 65: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards daa0a9ea72 64: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards af936b6a30 63: onsuccess: 1: Successful build after binutils/gcc/gdb: 8 [...] discards 6896343c4b 62: onsuccess: 1: Successful build after binutils/gcc/gdb: 2 [...] discards cfac6c4c4b 61: onsuccess: 1: Successful build after binutils/gcc/gdb/qe [...] discards 67aed3f8e6 60: onsuccess: 1: Successful build after glibc: 2 commits discards 38afd41ce6 59: onsuccess: 1: Successful build after binutils: 2 commits discards e22e3b06ac 58: onsuccess: 1: Successful build after binutils: gdb: new [...] discards b215787d77 57: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] new 8e47c5fca5 57: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] new dc8c273257 58: onsuccess: 1: Successful build after binutils: gdb: new [...] new 43be9af63a 59: onsuccess: 1: Successful build after binutils: 2 commits new 922dbe485d 60: onsuccess: 1: Successful build after glibc: 2 commits new f806dddc6e 61: onsuccess: 1: Successful build after binutils/gcc/gdb/qe [...] new 6f8f9aef33 62: onsuccess: 1: Successful build after binutils/gcc/gdb: 2 [...] new 8137990564 63: onsuccess: 1: Successful build after binutils/gcc/gdb: 8 [...] new 545557c993 64: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new d1c7888800 65: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 59a70e06c7 66: onsuccess: 1: Successful build after gcc/glibc: 10 commits new 6c6e21565b 67: onsuccess: 1: Successful build after binutils/gcc/gdb: 1 [...] new 704cd78419 68: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 72908ea2aa 69: onsuccess: 1: Successful build after binutils/gcc/gdb: 5 [...] new 37c611caf0 70: onsuccess: 1: Successful build after binutils/gcc/gdb: 4 [...] new 82a178929b 71: onsuccess: 1: Successful build after gcc/glibc: 3 commits new cfca240c9b 72: onsuccess: 1: Successful build after linux: 12 commits new 3b1528e8c3 73: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new b6e87396eb 74: onsuccess: 1: Successful build after binutils/gdb: 2 commits new 0f18d76ba2 75: onsuccess: 1: Successful build after linux: 44 commits new 81eb8ac777 76: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new fbbb8771b2 77: onsuccess: 1: Successful build after gcc/linux/glibc: 22 [...] new 35cb604304 78: onsuccess: 1: Successful build after binutils/gcc/gdb: 4 [...] new cddb4f5876 79: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] new 7b472821be 80: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] new dd19879f03 81: onsuccess: 1: Successful build after binutils/gcc/gdb: 6 [...] new 0de6207565 82: onsuccess: 1: Successful build after binutils/gcc/gdb: 1 [...] new b846efe34b 83: onsuccess: 1: Success after binutils/gcc/glibc/gdb: 17 commits new d591cdb604 84: onsuccess: 1: Success after binutils/gcc/linux/gdb: 68 commits new acd34a2ae1 85: onsuccess: 1: Success after binutils/gcc/glibc/gdb/qemu: [...] new 2bdb65dffd 86: onsuccess: 1: Success after binutils/gcc/gdb: 7 commits new 583a4a8ba9 87: onsuccess: 1: Success after binutils/gcc/gdb: 14 commits new 91c2a1a308 88: onsuccess: 1: Success after gcc/linux/qemu: 149 commits new 8bfe1b8ac1 89: onsuccess: 1: Success after binutils/gcc/gdb: 5 commits new 43a9b3abaa 90: onsuccess: 1: Success after binutils/gcc/gdb: 19 commits new da5150d578 91: onsuccess: 1: Success after binutils/gcc/gdb: 8 commits new f417380eda 92: onsuccess: 1: Success after binutils/gcc/linux/gdb/qemu: [...] new 8570f008c7 93: onsuccess: 1: Success after binutils/gcc/linux/gdb: 88 commits new bed7a44ad1 94: onsuccess: 1: Success after gcc: openmp: Partial OpenMP [...] new 190ad4c543 95: onsuccess: #2070: 1: Success after basepoints/gcc-13-238 [...] new b71b1f9b31 96: onsuccess: #2071: 1: Success after gcc/linux: 56 commits new da40980d29 97: onsuccess: #2072: 1: Success after binutils/gcc/gdb: 3 commits new d89fc07ff5 98: onsuccess: #2073: 1: Success after gcc/linux: 11 commits new 8655a1d182 99: onsuccess: #2074: 1: Success after baseline build: no ne [...] new 45b4b65d96 100: onsuccess: #2077: 1: Success after binutils/gcc/linux/g [...] new 0bb5dcfff0 101: onsuccess: #2130: 1: Success after binutils: 81 commits new 22040e0ad3 102: onsuccess: #2133: 1: Success after gdb-12-branchpoint-1 [...] new b22c0a1748 103: onsuccess: #2135: 1: Success after gcc/linux/glibc/gdb/ [...] new 82893b4990 104: onsuccess: #2136: 1: Success after binutils/gcc/gdb: 3 commits new 9f40db46d9 105: onsuccess: #2137: 1: Success after basepoints/gcc-13-27 [...] new d667f7eda2 106: onsuccess: #2138: 1: Success after binutils/gcc/glibc/g [...] new 0b5a6156e1 107: onsuccess: #2139: 1: Success after binutils/gcc/gdb: 3 commits new d56c8679ad 108: onsuccess: #2140: 1: Success after binutils/gcc/gdb: 5 commits new 3d4672b077 109: onsuccess: #2141: 1: Success after gcc/glibc: 6 commits new 23f84bd53a 110: onsuccess: #2142: 1: Success after binutils/gcc/glibc/g [...] new 056c4fe799 111: onsuccess: #2143: 1: Success after binutils/gcc/linux/g [...] new 570baeab4d 112: onsuccess: #2144: 1: Success after binutils/gcc/glibc/g [...] new 697476793a 113: onsuccess: #2145: 1: Success after binutils/gcc/glibc/g [...] new b1e17dd95b 114: onsuccess: #2146: 1: Success after binutils/gcc/glibc/g [...] new 56cede9be1 115: onsuccess: #2147: 1: Success after binutils/linux/glibc [...] new cdb41c6d3b 116: onsuccess: #2148: 1: Success after binutils/gcc/gdb: 7 commits new e2379cea2d 117: onsuccess: #2150: 1: Success after binutils/gcc/glibc/g [...] new 3369064c9e 118: onsuccess: #2151: 1: Success after binutils/gcc/linux/g [...] new af580faf98 119: onsuccess: #2154: 1: Success after binutils/gcc/linux/g [...] new 33421cca3a 120: onsuccess: #2155: 1: Success after binutils/gcc/linux/g [...] new 88939709f2 121: onsuccess: #2156: 1: Success after binutils/gcc/linux/g [...] new 2a7b457b66 122: onsuccess: #2157: 1: Success after binutils/gcc/gdb: 6 commits new 5c73c5412b 123: onsuccess: #2158: 1: Success after basepoints/gcc-13-28 [...] new 2fad372832 124: onsuccess: #2159: 1: Success after linux: 23 commits new 8028a4ec73 125: onsuccess: #2160: 1: Success after binutils/gcc/linux/g [...] new d052c5097b 126: onsuccess: #2161: 1: Success after basepoints/gcc-13-28 [...] new 2d6d4dca7b 127: onsuccess: #2162: 1: Success after gcc: 9 commits new b340d7a5dc 128: onsuccess: #2163: 1: Success after linux: 23 commits new 33167e90e2 129: onsuccess: #2164: 1: Success after binutils/gcc/linux/g [...] new 5a1c9f8811 130: onsuccess: #2165: 1: Success after binutils/gcc/gdb: 32 [...] new 2bf9043a39 131: onsuccess: #2166: 1: Success after binutils/gcc/gdb: 12 [...] new e5772d0ed5 132: onsuccess: #2167: 1: Success after binutils/gcc/glibc/g [...] new 120522f05d 133: onsuccess: #2168: 1: Success after binutils/gcc/linux/g [...] new 24cbfe85f0 134: onsuccess: #2169: 1: Success after binutils/gcc/gdb: 13 [...] new 597d64a8eb 135: onsuccess: #2170: 1: Success after gcc/linux/qemu: 63 commits new dd381f1625 136: onsuccess: #2171: 1: Success after binutils/gcc/gdb/qem [...] new 5a8a3325c9 137: onsuccess: #2172: 1: Success after binutils/gcc/linux/g [...] new 93e775593f 138: onsuccess: #2173: 1: Success after binutils/gcc/gdb: 5 commits new 73d7fb7f9a 139: onsuccess: #2174: 1: Success after binutils/gcc/gdb: 13 [...] new 78e91f8967 140: onsuccess: #2175: 1: Success after binutils/gcc/linux/g [...] new 1a3ebc79e6 141: onsuccess: #2176: 1: Success after binutils/gcc/gdb: 6 commits new ec414bfc39 142: onsuccess: #2177: 1: Success after gcc/glibc: 4 commits new 152c212981 143: onsuccess: #2178: 1: Success after binutils/gcc/gdb/qem [...] new a2c40ac4d9 144: onsuccess: #2179: 1: Success after binutils/gcc/linux/g [...] new b78cf4a738 145: onsuccess: #2180: 1: Success after binutils/gcc/linux/g [...] new 2adccd1078 146: onsuccess: #2181: 1: Success after binutils/glibc/gdb: [...] new 9726f9a014 147: onsuccess: #2182: 1: Success after binutils/gcc/gdb: 18 [...] new 7f900610b0 148: onsuccess: #2183: 1: Success after gcc/linux/glibc: 64 commits new aff16be23b 149: onsuccess: #2184: 1: Success after binutils/gcc/linux/g [...] new a5b14d371d 150: onsuccess: #2185: 1: Success after gcc: 3 commits new 4530614ec2 151: onsuccess: #2186: 1: Success after gcc: 2 commits new 031839291b 152: onsuccess: #2187: 1: Success after gcc/linux/glibc: 22 commits new 7759dcb0c9 153: onsuccess: #2188: 1: Success after binutils/gcc/gdb: 3 commits new 78703d9740 154: onsuccess: #2189: 1: Success after binutils/gcc/gdb: 18 [...] new 8ab71a261b 155: onsuccess: #2190: 1: Success after binutils/gcc/linux/g [...] new e8311a3ec0 156: onsuccess: #2191: 1: Success after binutils/gcc/linux/g [...] new c7538d910b 157: onsuccess: #2192: 1: Success after binutils/gcc/gdb: 8 commits new c35cc15b20 158: onsuccess: #2193: 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 (25eb8ef8dc) \ 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 1744 -> 1704 bytes 02-prepare_abe/console.log.xz | Bin 2752 -> 2748 bytes 03-build_abe-binutils/console.log.xz | Bin 30720 -> 30812 bytes 04-build_abe-stage1/console.log.xz | Bin 72340 -> 74324 bytes 06-build_abe-linux/console.log.xz | Bin 8328 -> 8304 bytes 07-build_abe-glibc/console.log.xz | Bin 240108 -> 239864 bytes 08-build_abe-stage2/console.log.xz | Bin 203088 -> 204752 bytes 09-build_abe-gdb/console.log.xz | Bin 37928 -> 37812 bytes 10-build_abe-qemu/console.log.xz | Bin 31776 -> 32016 bytes 11-build_abe-dejagnu/console.log.xz | Bin 3896 -> 3948 bytes 12-build_abe-check_gcc/console.log.xz | Bin 2600 -> 4808 bytes 13-check_regression/console.log.xz | Bin 5856 -> 9908 bytes 13-check_regression/extra-bisect-params | 1 + 13-check_regression/fails.sum | 51 + 13-check_regression/mail-body.txt | 113 +- 13-check_regression/results.compare | 85 +- 13-check_regression/results.compare2 | 599 +++- 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/glibc_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 115 +- mail/mail-subject.txt | 2 +- manifest.sh | 36 +- results | 85 + sumfiles/g++.log.xz | Bin 3437232 -> 3410948 bytes sumfiles/g++.sum | 38 +- sumfiles/gcc.log.xz | Bin 3008240 -> 3030496 bytes sumfiles/gcc.sum | 4978 ++++++++++++++++--------------- sumfiles/gfortran.log.xz | Bin 1034132 -> 1032208 bytes sumfiles/gfortran.sum | 8 +- sumfiles/libatomic.log.xz | Bin 2296 -> 2292 bytes sumfiles/libatomic.sum | 2 +- sumfiles/libgomp.log.xz | Bin 202196 -> 202264 bytes sumfiles/libgomp.sum | 2 +- sumfiles/libitm.log.xz | Bin 2652 -> 2656 bytes sumfiles/libitm.sum | 2 +- sumfiles/libstdc++.log.xz | Bin 423804 -> 421400 bytes sumfiles/libstdc++.sum | 180 +- 43 files changed, 3736 insertions(+), 2726 deletions(-) create mode 100644 13-check_regression/extra-bisect-params create mode 100644 13-check_regression/fails.sum create mode 100644 13-check_regression/results.regressions