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 068e421f86 156: onsuccess: #2191: 1: Success after binutils/gcc/linux/g [...] discards 01fc05a6e0 155: onsuccess: #2190: 1: Success after binutils/gcc/linux/g [...] discards a82a0c79f4 154: onsuccess: #2189: 1: Success after binutils/gcc/gdb: 18 [...] discards 160de55447 153: onsuccess: #2188: 1: Success after binutils/gcc/gdb: 3 commits discards cd65df7f83 152: onsuccess: #2187: 1: Success after gcc/linux/glibc: 22 commits discards 26b5195b47 151: onsuccess: #2186: 1: Success after gcc: 2 commits discards 848f26f1ca 150: onsuccess: #2185: 1: Success after gcc: 3 commits discards b583b3e130 149: onsuccess: #2184: 1: Success after binutils/gcc/linux/g [...] discards 49de3f8e9c 148: onsuccess: #2183: 1: Success after gcc/linux/glibc: 64 commits discards 8eb6bc0599 147: onsuccess: #2182: 1: Success after binutils/gcc/gdb: 18 [...] discards 9e4f4174f3 146: onsuccess: #2181: 1: Success after binutils/glibc/gdb: [...] discards 563cb87b5a 145: onsuccess: #2180: 1: Success after binutils/gcc/linux/g [...] discards b084eed31a 144: onsuccess: #2179: 1: Success after binutils/gcc/linux/g [...] discards 4b6a42f6ea 143: onsuccess: #2178: 1: Success after binutils/gcc/gdb/qem [...] discards bc70d1cf0c 142: onsuccess: #2177: 1: Success after gcc/glibc: 4 commits discards 28d10fffde 141: onsuccess: #2176: 1: Success after binutils/gcc/gdb: 6 commits discards 274ea7ab1a 140: onsuccess: #2175: 1: Success after binutils/gcc/linux/g [...] discards e83b49d640 139: onsuccess: #2174: 1: Success after binutils/gcc/gdb: 13 [...] discards 419600e248 138: onsuccess: #2173: 1: Success after binutils/gcc/gdb: 5 commits discards c4a6b1ec5e 137: onsuccess: #2172: 1: Success after binutils/gcc/linux/g [...] discards e183ab7241 136: onsuccess: #2171: 1: Success after binutils/gcc/gdb/qem [...] discards 0f44721c69 135: onsuccess: #2170: 1: Success after gcc/linux/qemu: 63 commits discards 0f0d5e2c54 134: onsuccess: #2169: 1: Success after binutils/gcc/gdb: 13 [...] discards ba42e673a9 133: onsuccess: #2168: 1: Success after binutils/gcc/linux/g [...] discards 0b9b399ff9 132: onsuccess: #2167: 1: Success after binutils/gcc/glibc/g [...] discards da022fa3ec 131: onsuccess: #2166: 1: Success after binutils/gcc/gdb: 12 [...] discards 87824472f2 130: onsuccess: #2165: 1: Success after binutils/gcc/gdb: 32 [...] discards f9d96f8030 129: onsuccess: #2164: 1: Success after binutils/gcc/linux/g [...] discards c9fa4b4feb 128: onsuccess: #2163: 1: Success after linux: 23 commits discards 4021a0cc2e 127: onsuccess: #2162: 1: Success after gcc: 9 commits discards 83e91162bf 126: onsuccess: #2161: 1: Success after basepoints/gcc-13-28 [...] discards 2a4f7d9d66 125: onsuccess: #2160: 1: Success after binutils/gcc/linux/g [...] discards cdfd41346c 124: onsuccess: #2159: 1: Success after linux: 23 commits discards a1383f684c 123: onsuccess: #2158: 1: Success after basepoints/gcc-13-28 [...] discards e55547bd7f 122: onsuccess: #2157: 1: Success after binutils/gcc/gdb: 6 commits discards 4fd81086d0 121: onsuccess: #2156: 1: Success after binutils/gcc/linux/g [...] discards b86257f97a 120: onsuccess: #2155: 1: Success after binutils/gcc/linux/g [...] discards 4429de90df 119: onsuccess: #2154: 1: Success after binutils/gcc/linux/g [...] discards d5b194c71e 118: onsuccess: #2151: 1: Success after binutils/gcc/linux/g [...] discards f53de9ff16 117: onsuccess: #2150: 1: Success after binutils/gcc/glibc/g [...] discards aa5de271bd 116: onsuccess: #2148: 1: Success after binutils/gcc/gdb: 7 commits discards 05e681558d 115: onsuccess: #2147: 1: Success after binutils/linux/glibc [...] discards ca424385e8 114: onsuccess: #2146: 1: Success after binutils/gcc/glibc/g [...] discards de5f591f6b 113: onsuccess: #2145: 1: Success after binutils/gcc/glibc/g [...] discards 11c3043304 112: onsuccess: #2144: 1: Success after binutils/gcc/glibc/g [...] discards dd3f88e809 111: onsuccess: #2143: 1: Success after binutils/gcc/linux/g [...] discards e39c873921 110: onsuccess: #2142: 1: Success after binutils/gcc/glibc/g [...] discards 36233c6494 109: onsuccess: #2141: 1: Success after gcc/glibc: 6 commits discards bddd2aa1cb 108: onsuccess: #2140: 1: Success after binutils/gcc/gdb: 5 commits discards 1390536b91 107: onsuccess: #2139: 1: Success after binutils/gcc/gdb: 3 commits discards 7487b7463a 106: onsuccess: #2138: 1: Success after binutils/gcc/glibc/g [...] discards 091a9c0570 105: onsuccess: #2137: 1: Success after basepoints/gcc-13-27 [...] discards 14b1242b04 104: onsuccess: #2136: 1: Success after binutils/gcc/gdb: 3 commits discards eec9ff7b4a 103: onsuccess: #2135: 1: Success after gcc/linux/glibc/gdb/ [...] discards 51124edaa5 102: onsuccess: #2133: 1: Success after gdb-12-branchpoint-1 [...] discards de1e25c2a8 101: onsuccess: #2130: 1: Success after binutils: 81 commits discards ff4d305d35 100: onsuccess: #2077: 1: Success after binutils/gcc/linux/g [...] discards 936a8d905f 99: onsuccess: #2074: 1: Success after baseline build: no ne [...] discards 1ff02ff4ae 98: onsuccess: #2073: 1: Success after gcc/linux: 11 commits discards 4eb248c844 97: onsuccess: #2072: 1: Success after binutils/gcc/gdb: 3 commits discards fda124138b 96: onsuccess: #2071: 1: Success after gcc/linux: 56 commits discards 37ea60cce9 95: onsuccess: #2070: 1: Success after basepoints/gcc-13-238 [...] discards 90e3674ae5 94: onsuccess: 1: Success after gcc: openmp: Partial OpenMP [...] discards 0821d1e404 93: onsuccess: 1: Success after binutils/gcc/linux/gdb: 88 commits discards 3f8fe43fea 92: onsuccess: 1: Success after binutils/gcc/linux/gdb/qemu: [...] discards 1909a930af 91: onsuccess: 1: Success after binutils/gcc/gdb: 8 commits discards 893172ad2d 90: onsuccess: 1: Success after binutils/gcc/gdb: 19 commits discards 16e3725d79 89: onsuccess: 1: Success after binutils/gcc/gdb: 5 commits discards 3b75bb8b83 88: onsuccess: 1: Success after gcc/linux/qemu: 149 commits discards 4109ce9398 87: onsuccess: 1: Success after binutils/gcc/gdb: 14 commits discards a21ab63670 86: onsuccess: 1: Success after binutils/gcc/gdb: 7 commits discards 4703574521 85: onsuccess: 1: Success after binutils/gcc/glibc/gdb/qemu: [...] discards d3962ad708 84: onsuccess: 1: Success after binutils/gcc/linux/gdb: 68 commits discards fe62cb5d21 83: onsuccess: 1: Success after binutils/gcc/glibc/gdb: 17 commits discards 74365579cf 82: onsuccess: 1: Successful build after binutils/gcc/gdb: 1 [...] discards a6a9e5534e 81: onsuccess: 1: Successful build after binutils/gcc/gdb: 6 [...] discards 531759ca59 80: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] discards e784f0173d 79: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] discards e87545e12a 78: onsuccess: 1: Successful build after binutils/gcc/gdb: 4 [...] discards e35b3786f3 77: onsuccess: 1: Successful build after gcc/linux/glibc: 22 [...] discards 3687b0307a 76: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 91ebf9353d 75: onsuccess: 1: Successful build after linux: 44 commits discards d7eca240ef 74: onsuccess: 1: Successful build after binutils/gdb: 2 commits discards a70a667c2c 73: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 2cd28e09ff 72: onsuccess: 1: Successful build after linux: 12 commits discards d467ec9847 71: onsuccess: 1: Successful build after gcc/glibc: 3 commits discards eec562af1d 70: onsuccess: 1: Successful build after binutils/gcc/gdb: 4 [...] discards 6fc9b72e77 69: onsuccess: 1: Successful build after binutils/gcc/gdb: 5 [...] discards 84fa7d72aa 68: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 63cd8bc3a6 67: onsuccess: 1: Successful build after binutils/gcc/gdb: 1 [...] discards 247b31a4d6 66: onsuccess: 1: Successful build after gcc/glibc: 10 commits discards 0790c6b1bb 65: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 0dac5fc1ac 64: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 6867a62829 63: onsuccess: 1: Successful build after binutils/gcc/gdb: 8 [...] discards 28a6af862b 62: onsuccess: 1: Successful build after binutils/gcc/gdb: 2 [...] discards a3bd176a1e 61: onsuccess: 1: Successful build after binutils/gcc/gdb/qe [...] discards 1daffc42f1 60: onsuccess: 1: Successful build after glibc: 2 commits discards 0616675025 59: onsuccess: 1: Successful build after binutils: 2 commits discards 0f13b1f63a 58: onsuccess: 1: Successful build after binutils: gdb: new [...] discards 826db87721 57: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] discards 1758f18e34 56: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new e3a5dee840 56: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new b215787d77 57: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] new e22e3b06ac 58: onsuccess: 1: Successful build after binutils: gdb: new [...] new 38afd41ce6 59: onsuccess: 1: Successful build after binutils: 2 commits new 67aed3f8e6 60: onsuccess: 1: Successful build after glibc: 2 commits new cfac6c4c4b 61: onsuccess: 1: Successful build after binutils/gcc/gdb/qe [...] new 6896343c4b 62: onsuccess: 1: Successful build after binutils/gcc/gdb: 2 [...] new af936b6a30 63: onsuccess: 1: Successful build after binutils/gcc/gdb: 8 [...] new daa0a9ea72 64: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new c99eef1102 65: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new d217d796bb 66: onsuccess: 1: Successful build after gcc/glibc: 10 commits new f6ec6051bb 67: onsuccess: 1: Successful build after binutils/gcc/gdb: 1 [...] new 4353660b0c 68: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 3b90ec1437 69: onsuccess: 1: Successful build after binutils/gcc/gdb: 5 [...] new 69a9e95dcb 70: onsuccess: 1: Successful build after binutils/gcc/gdb: 4 [...] new db94db49e4 71: onsuccess: 1: Successful build after gcc/glibc: 3 commits new a73ce032b2 72: onsuccess: 1: Successful build after linux: 12 commits new 035cc42d97 73: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 9b9a2188b5 74: onsuccess: 1: Successful build after binutils/gdb: 2 commits new 19e855aa20 75: onsuccess: 1: Successful build after linux: 44 commits new ab54080669 76: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 0a9e06a5ec 77: onsuccess: 1: Successful build after gcc/linux/glibc: 22 [...] new d28b8248fb 78: onsuccess: 1: Successful build after binutils/gcc/gdb: 4 [...] new 6baaa2c2bb 79: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] new fd1e3f2303 80: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] new 1985fee0de 81: onsuccess: 1: Successful build after binutils/gcc/gdb: 6 [...] new ec2a676b9c 82: onsuccess: 1: Successful build after binutils/gcc/gdb: 1 [...] new 4a63e188c2 83: onsuccess: 1: Success after binutils/gcc/glibc/gdb: 17 commits new 91eee9321c 84: onsuccess: 1: Success after binutils/gcc/linux/gdb: 68 commits new afbcdc1e47 85: onsuccess: 1: Success after binutils/gcc/glibc/gdb/qemu: [...] new 6fde556902 86: onsuccess: 1: Success after binutils/gcc/gdb: 7 commits new 07e1e4b8a3 87: onsuccess: 1: Success after binutils/gcc/gdb: 14 commits new 20a97b86f8 88: onsuccess: 1: Success after gcc/linux/qemu: 149 commits new b23883226d 89: onsuccess: 1: Success after binutils/gcc/gdb: 5 commits new 78d03360df 90: onsuccess: 1: Success after binutils/gcc/gdb: 19 commits new 96d062a69c 91: onsuccess: 1: Success after binutils/gcc/gdb: 8 commits new 046ddbd95d 92: onsuccess: 1: Success after binutils/gcc/linux/gdb/qemu: [...] new d45a595d05 93: onsuccess: 1: Success after binutils/gcc/linux/gdb: 88 commits new cf1133abdd 94: onsuccess: 1: Success after gcc: openmp: Partial OpenMP [...] new 4404f4de81 95: onsuccess: #2070: 1: Success after basepoints/gcc-13-238 [...] new 15eefe67df 96: onsuccess: #2071: 1: Success after gcc/linux: 56 commits new 5261cd439b 97: onsuccess: #2072: 1: Success after binutils/gcc/gdb: 3 commits new e527246415 98: onsuccess: #2073: 1: Success after gcc/linux: 11 commits new 61f546aeec 99: onsuccess: #2074: 1: Success after baseline build: no ne [...] new ae6b79e362 100: onsuccess: #2077: 1: Success after binutils/gcc/linux/g [...] new a9cd644924 101: onsuccess: #2130: 1: Success after binutils: 81 commits new e18983a345 102: onsuccess: #2133: 1: Success after gdb-12-branchpoint-1 [...] new 8602eb7df0 103: onsuccess: #2135: 1: Success after gcc/linux/glibc/gdb/ [...] new ef7784f6a5 104: onsuccess: #2136: 1: Success after binutils/gcc/gdb: 3 commits new baed0756b9 105: onsuccess: #2137: 1: Success after basepoints/gcc-13-27 [...] new 96fd1ae7ee 106: onsuccess: #2138: 1: Success after binutils/gcc/glibc/g [...] new 363ba30318 107: onsuccess: #2139: 1: Success after binutils/gcc/gdb: 3 commits new 7a75d8fc1c 108: onsuccess: #2140: 1: Success after binutils/gcc/gdb: 5 commits new 38dead2eb8 109: onsuccess: #2141: 1: Success after gcc/glibc: 6 commits new 983ee7e6c8 110: onsuccess: #2142: 1: Success after binutils/gcc/glibc/g [...] new 36faf4da03 111: onsuccess: #2143: 1: Success after binutils/gcc/linux/g [...] new 0f57d3a769 112: onsuccess: #2144: 1: Success after binutils/gcc/glibc/g [...] new 7423c7f638 113: onsuccess: #2145: 1: Success after binutils/gcc/glibc/g [...] new 1f76398cab 114: onsuccess: #2146: 1: Success after binutils/gcc/glibc/g [...] new 602c538d60 115: onsuccess: #2147: 1: Success after binutils/linux/glibc [...] new aa01867ca9 116: onsuccess: #2148: 1: Success after binutils/gcc/gdb: 7 commits new e1e996992f 117: onsuccess: #2150: 1: Success after binutils/gcc/glibc/g [...] new 42664ac6a2 118: onsuccess: #2151: 1: Success after binutils/gcc/linux/g [...] new 625546d305 119: onsuccess: #2154: 1: Success after binutils/gcc/linux/g [...] new f2171341b9 120: onsuccess: #2155: 1: Success after binutils/gcc/linux/g [...] new 6bbc636a40 121: onsuccess: #2156: 1: Success after binutils/gcc/linux/g [...] new 713d0a78d8 122: onsuccess: #2157: 1: Success after binutils/gcc/gdb: 6 commits new 0859b95d96 123: onsuccess: #2158: 1: Success after basepoints/gcc-13-28 [...] new a0126ed71f 124: onsuccess: #2159: 1: Success after linux: 23 commits new 873cd7937f 125: onsuccess: #2160: 1: Success after binutils/gcc/linux/g [...] new 5968918e1b 126: onsuccess: #2161: 1: Success after basepoints/gcc-13-28 [...] new 704ec862f4 127: onsuccess: #2162: 1: Success after gcc: 9 commits new 2e31b3a5de 128: onsuccess: #2163: 1: Success after linux: 23 commits new 334927ee5e 129: onsuccess: #2164: 1: Success after binutils/gcc/linux/g [...] new 656e61d493 130: onsuccess: #2165: 1: Success after binutils/gcc/gdb: 32 [...] new 1755ab453b 131: onsuccess: #2166: 1: Success after binutils/gcc/gdb: 12 [...] new 6b005e6f90 132: onsuccess: #2167: 1: Success after binutils/gcc/glibc/g [...] new a1b5b6970f 133: onsuccess: #2168: 1: Success after binutils/gcc/linux/g [...] new f204d97362 134: onsuccess: #2169: 1: Success after binutils/gcc/gdb: 13 [...] new 784d2196a4 135: onsuccess: #2170: 1: Success after gcc/linux/qemu: 63 commits new 164a593580 136: onsuccess: #2171: 1: Success after binutils/gcc/gdb/qem [...] new f669c09e2f 137: onsuccess: #2172: 1: Success after binutils/gcc/linux/g [...] new 72b724315c 138: onsuccess: #2173: 1: Success after binutils/gcc/gdb: 5 commits new b6bf550c15 139: onsuccess: #2174: 1: Success after binutils/gcc/gdb: 13 [...] new 59d966fef5 140: onsuccess: #2175: 1: Success after binutils/gcc/linux/g [...] new 1a382759a7 141: onsuccess: #2176: 1: Success after binutils/gcc/gdb: 6 commits new 5c437441eb 142: onsuccess: #2177: 1: Success after gcc/glibc: 4 commits new 1ea3dcfb33 143: onsuccess: #2178: 1: Success after binutils/gcc/gdb/qem [...] new c37396202d 144: onsuccess: #2179: 1: Success after binutils/gcc/linux/g [...] new 37b8037a7a 145: onsuccess: #2180: 1: Success after binutils/gcc/linux/g [...] new e3a2c90c9c 146: onsuccess: #2181: 1: Success after binutils/glibc/gdb: [...] new eea98d80a6 147: onsuccess: #2182: 1: Success after binutils/gcc/gdb: 18 [...] new 76a6be61d0 148: onsuccess: #2183: 1: Success after gcc/linux/glibc: 64 commits new f88483dd79 149: onsuccess: #2184: 1: Success after binutils/gcc/linux/g [...] new c0eb4d2512 150: onsuccess: #2185: 1: Success after gcc: 3 commits new 4c5d0c6d1e 151: onsuccess: #2186: 1: Success after gcc: 2 commits new a84bd4fd9a 152: onsuccess: #2187: 1: Success after gcc/linux/glibc: 22 commits new 1aca0ae517 153: onsuccess: #2188: 1: Success after binutils/gcc/gdb: 3 commits new be6c3e297e 154: onsuccess: #2189: 1: Success after binutils/gcc/gdb: 18 [...] new efb9c5d4e3 155: onsuccess: #2190: 1: Success after binutils/gcc/linux/g [...] new 46805b8f4b 156: onsuccess: #2191: 1: Success after binutils/gcc/linux/g [...] new 25eb8ef8dc 157: onsuccess: #2192: 1: Success after binutils/gcc/gdb: 8 commits
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 (068e421f86) \ 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 1748 -> 1744 bytes 02-prepare_abe/console.log.xz | Bin 2736 -> 2752 bytes 03-build_abe-binutils/console.log.xz | Bin 30136 -> 30720 bytes 04-build_abe-stage1/console.log.xz | Bin 72460 -> 72340 bytes 06-build_abe-linux/console.log.xz | Bin 8320 -> 8328 bytes 07-build_abe-glibc/console.log.xz | Bin 239796 -> 240108 bytes 08-build_abe-stage2/console.log.xz | Bin 203216 -> 203088 bytes 09-build_abe-gdb/console.log.xz | Bin 37548 -> 37928 bytes 10-build_abe-qemu/console.log.xz | Bin 31928 -> 31776 bytes 11-build_abe-dejagnu/console.log.xz | Bin 3880 -> 3896 bytes 12-build_abe-check_gcc/console.log.xz | Bin 2440 -> 2600 bytes 13-check_regression/console.log.xz | Bin 6008 -> 5856 bytes 13-check_regression/extra-bisect-params | 1 - 13-check_regression/fails.sum | 8 - 13-check_regression/mail-body.txt | 42 +- 13-check_regression/results.compare | 32 +- 13-check_regression/results.compare2 | 38 +- 13-check_regression/results.regressions | 28 - 14-update_baseline/console.log | 60 +- 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 | 44 +- mail/mail-subject.txt | 2 +- manifest.sh | 36 +- results | 28 - sumfiles/g++.log.xz | Bin 3408516 -> 3437232 bytes sumfiles/g++.sum | 56 +- sumfiles/gcc.log.xz | Bin 3023416 -> 3008240 bytes sumfiles/gcc.sum | 4356 +++++++++++++++---------------- sumfiles/gfortran.log.xz | Bin 1033820 -> 1034132 bytes sumfiles/gfortran.sum | 18 +- sumfiles/libatomic.log.xz | Bin 2292 -> 2296 bytes sumfiles/libatomic.sum | 2 +- sumfiles/libgomp.log.xz | Bin 202416 -> 202196 bytes sumfiles/libgomp.sum | 2 +- sumfiles/libitm.log.xz | Bin 2664 -> 2652 bytes sumfiles/libitm.sum | 2 +- sumfiles/libstdc++.log.xz | Bin 423608 -> 423804 bytes sumfiles/libstdc++.sum | 8 +- 42 files changed, 2356 insertions(+), 2417 deletions(-) delete mode 100644 13-check_regression/extra-bisect-params delete mode 100644 13-check_regression/fails.sum delete mode 100644 13-check_regression/results.regressions