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 94826eac4 155: onsuccess: #2190: 1: Success after binutils/gcc/linux/gd [...] discards 330b64206 154: onsuccess: #2189: 1: Success after binutils/gcc/gdb: 18 commits discards 319001da9 153: onsuccess: #2188: 1: Success after binutils/gcc/gdb: 3 commits discards 709476971 152: onsuccess: #2187: 1: Success after gcc/linux/glibc: 22 commits discards 8d8dd18c8 151: onsuccess: #2186: 1: Success after gcc: 2 commits discards 2a81a2aff 150: onsuccess: #2185: 1: Success after gcc: 3 commits discards 7ae279969 149: onsuccess: #2184: 1: Success after binutils/gcc/linux/gd [...] discards 37a536a95 148: onsuccess: #2183: 1: Success after gcc/linux/glibc: 64 commits discards 43bf08fb6 147: onsuccess: #2182: 1: Success after binutils/gcc/gdb: 18 commits discards 47c2fd9ee 146: onsuccess: #2181: 1: Success after binutils/glibc/gdb: 2 [...] discards 0e7b02a0f 145: onsuccess: #2180: 1: Success after binutils/gcc/linux/gd [...] discards e9527f858 144: onsuccess: #2179: 1: Success after binutils/gcc/linux/gd [...] discards 18c95ca23 143: onsuccess: #2178: 1: Success after binutils/gcc/gdb/qemu [...] discards 6d62db897 142: onsuccess: #2177: 1: Success after gcc/glibc: 4 commits discards 09660b14e 141: onsuccess: #2176: 1: Success after binutils/gcc/gdb: 6 commits discards de036dfc3 140: onsuccess: #2175: 1: Success after binutils/gcc/linux/gl [...] discards ceb0933f6 139: onsuccess: #2174: 1: Success after binutils/gcc/gdb: 13 commits discards 29d0d6f2b 138: onsuccess: #2173: 1: Success after binutils/gcc/gdb: 5 commits discards 63bd57274 137: onsuccess: #2172: 1: Success after binutils/gcc/linux/gl [...] discards d8d46cdbe 136: onsuccess: #2171: 1: Success after binutils/gcc/gdb/qemu [...] discards af6814997 135: onsuccess: #2170: 1: Success after gcc/linux/qemu: 63 commits discards 24a6e24ed 134: onsuccess: #2169: 1: Success after binutils/gcc/gdb: 13 commits discards 9d958f460 133: onsuccess: #2168: 1: Success after binutils/gcc/linux/gd [...] discards 7bc723f08 132: onsuccess: #2167: 1: Success after binutils/gcc/glibc/gd [...] discards d25e54e99 131: onsuccess: #2166: 1: Success after binutils/gcc/gdb: 12 commits discards 20cbc9c86 130: onsuccess: #2165: 1: Success after binutils/gcc/gdb: 32 commits discards aa7cde98d 129: onsuccess: #2164: 1: Success after binutils/gcc/linux/gd [...] discards e387e9eee 128: onsuccess: #2163: 1: Success after linux: 23 commits discards 4e22b9317 127: onsuccess: #2162: 1: Success after gcc: 9 commits discards 92b89630b 126: onsuccess: #2161: 1: Success after basepoints/gcc-13-283 [...] discards b0ee3aa11 125: onsuccess: #2160: 1: Success after binutils/gcc/linux/gd [...] discards 65a38d119 124: onsuccess: #2159: 1: Success after linux: 23 commits discards 7328d5ac9 123: onsuccess: #2158: 1: Success after basepoints/gcc-13-283 [...] discards 5be70e4c7 122: onsuccess: #2157: 1: Success after binutils/gcc/gdb: 6 commits discards 5cad7ce7e 121: onsuccess: #2156: 1: Success after binutils/gcc/linux/gd [...] discards 0f7239421 120: onsuccess: #2155: 1: Success after binutils/gcc/linux/gl [...] discards 4dfe7484b 119: onsuccess: #2154: 1: Success after binutils/gcc/linux/gl [...] discards ba59b8491 118: onsuccess: #2151: 1: Success after binutils/gcc/linux/gl [...] discards 7ab72da4a 117: onsuccess: #2150: 1: Success after binutils/gcc/glibc/gd [...] discards 9f5555d2e 116: onsuccess: #2148: 1: Success after binutils/gcc/gdb: 7 commits discards 3ed3ee32c 115: onsuccess: #2147: 1: Success after binutils/linux/glibc/ [...] discards d2b25fff9 114: onsuccess: #2146: 1: Success after binutils/gcc/glibc/gd [...] discards e91028af3 113: onsuccess: #2145: 1: Success after binutils/gcc/glibc/gd [...] discards d4088026f 112: onsuccess: #2144: 1: Success after binutils/gcc/glibc/gd [...] discards 7fac7042d 111: onsuccess: #2143: 1: Success after binutils/gcc/linux/gl [...] discards 962e9dfcd 110: onsuccess: #2142: 1: Success after binutils/gcc/glibc/gd [...] discards 448ec07cc 109: onsuccess: #2141: 1: Success after gcc/glibc: 6 commits discards cfe50d1ad 108: onsuccess: #2140: 1: Success after binutils/gcc/gdb: 5 commits discards edaf4db5b 107: onsuccess: #2139: 1: Success after binutils/gcc/gdb: 3 commits discards ff6b10e57 106: onsuccess: #2138: 1: Success after binutils/gcc/glibc/gd [...] discards c1dc9ad21 105: onsuccess: #2137: 1: Success after basepoints/gcc-13-271 [...] discards 73339f110 104: onsuccess: #2136: 1: Success after binutils/gcc/gdb: 3 commits discards 443e408ba 103: onsuccess: #2135: 1: Success after gcc/linux/glibc/gdb/q [...] discards 170c80e02 102: onsuccess: #2133: 1: Success after gdb-12-branchpoint-19 [...] discards b76df77aa 101: onsuccess: #2130: 1: Success after binutils: 81 commits discards db9ccc04d 100: onsuccess: #2077: 1: Success after binutils/gcc/linux/gd [...] discards 42ba2f78b 99: onsuccess: #2074: 1: Success after baseline build: no new [...] discards de89e74e2 98: onsuccess: #2073: 1: Success after gcc/linux: 11 commits discards a2f03f66d 97: onsuccess: #2072: 1: Success after binutils/gcc/gdb: 3 commits discards 0414a2178 96: onsuccess: #2071: 1: Success after gcc/linux: 56 commits discards aed6ddb41 95: onsuccess: #2070: 1: Success after basepoints/gcc-13-2389 [...] discards e2401bddc 94: onsuccess: 1: Success after gcc: openmp: Partial OpenMP 5 [...] discards e5d165a35 93: onsuccess: 1: Success after binutils/gcc/linux/gdb: 88 commits discards 924afcb9b 92: onsuccess: 1: Success after binutils/gcc/linux/gdb/qemu: [...] discards 7b0e265e7 91: onsuccess: 1: Success after binutils/gcc/gdb: 8 commits discards 1291957ee 90: onsuccess: 1: Success after binutils/gcc/gdb: 19 commits discards a4a93b4af 89: onsuccess: 1: Success after binutils/gcc/gdb: 5 commits discards 5089cbd7e 88: onsuccess: 1: Success after gcc/linux/qemu: 149 commits discards f363095c4 87: onsuccess: 1: Success after binutils/gcc/gdb: 14 commits discards 5c48491f6 86: onsuccess: 1: Success after binutils/gcc/gdb: 7 commits discards 3c4f0899d 85: onsuccess: 1: Success after binutils/gcc/glibc/gdb/qemu: [...] discards 5ef3e5fba 84: onsuccess: 1: Success after binutils/gcc/linux/gdb: 68 commits discards c9aa8f0a9 83: onsuccess: 1: Success after binutils/gcc/glibc/gdb: 17 commits discards 5e7067778 82: onsuccess: 1: Successful build after binutils/gcc/gdb: 11 [...] discards a79cc899b 81: onsuccess: 1: Successful build after binutils/gcc/gdb: 6 commits discards 41156ccd7 80: onsuccess: 1: Successful build after binutils/gcc/glibc/g [...] discards 0b24af59d 79: onsuccess: 1: Successful build after binutils/gcc/glibc/g [...] discards 1f80d0fa7 78: onsuccess: 1: Successful build after binutils/gcc/gdb: 4 commits discards 5bb657995 77: onsuccess: 1: Successful build after gcc/linux/glibc: 22 commits discards 487a7f6b5 76: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] discards 25d3a5649 75: onsuccess: 1: Successful build after linux: 44 commits discards 664c4cd96 74: onsuccess: 1: Successful build after binutils/gdb: 2 commits discards 5f678f5d2 73: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] discards 3b5ae4e32 72: onsuccess: 1: Successful build after linux: 12 commits discards 460075457 71: onsuccess: 1: Successful build after gcc/glibc: 3 commits discards 5a294ee92 70: onsuccess: 1: Successful build after binutils/gcc/gdb: 4 commits discards f736cba4f 69: onsuccess: 1: Successful build after binutils/gcc/gdb: 5 commits discards 4690a12c2 68: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] discards a53f55957 67: onsuccess: 1: Successful build after binutils/gcc/gdb: 10 [...] discards aa822a57f 66: onsuccess: 1: Successful build after gcc/glibc: 10 commits discards 79647b254 65: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] discards ea50043cb 64: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] discards 6d8e2b15b 63: onsuccess: 1: Successful build after binutils/gcc/gdb: 8 commits discards 22cbfb5ca 62: onsuccess: 1: Successful build after binutils/gcc/gdb: 22 [...] discards 09be2e9ea 61: onsuccess: 1: Successful build after binutils/gcc/gdb/qem [...] discards 00dd264d6 60: onsuccess: 1: Successful build after glibc: 2 commits discards e68efca98 59: onsuccess: 1: Successful build after binutils: 2 commits discards bacb60986 58: onsuccess: 1: Successful build after binutils: gdb: new ' [...] discards 3b408c19f 57: onsuccess: 1: Successful build after binutils/gcc/glibc/g [...] discards c4f0e6dd5 56: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] discards 9eaeee48f 55: onsuccess: 1: Successful build after gcc/linux/glibc/qemu [...] new aa4f33392 55: onsuccess: 1: Successful build after gcc/linux/glibc/qemu [...] new 1758f18e3 56: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] new 826db8772 57: onsuccess: 1: Successful build after binutils/gcc/glibc/g [...] new 0f13b1f63 58: onsuccess: 1: Successful build after binutils: gdb: new ' [...] new 061667502 59: onsuccess: 1: Successful build after binutils: 2 commits new 1daffc42f 60: onsuccess: 1: Successful build after glibc: 2 commits new a3bd176a1 61: onsuccess: 1: Successful build after binutils/gcc/gdb/qem [...] new 28a6af862 62: onsuccess: 1: Successful build after binutils/gcc/gdb: 22 [...] new 6867a6282 63: onsuccess: 1: Successful build after binutils/gcc/gdb: 8 commits new 0dac5fc1a 64: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] new 0790c6b1b 65: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] new 247b31a4d 66: onsuccess: 1: Successful build after gcc/glibc: 10 commits new 63cd8bc3a 67: onsuccess: 1: Successful build after binutils/gcc/gdb: 10 [...] new 84fa7d72a 68: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] new 6fc9b72e7 69: onsuccess: 1: Successful build after binutils/gcc/gdb: 5 commits new eec562af1 70: onsuccess: 1: Successful build after binutils/gcc/gdb: 4 commits new d467ec984 71: onsuccess: 1: Successful build after gcc/glibc: 3 commits new 2cd28e09f 72: onsuccess: 1: Successful build after linux: 12 commits new a70a667c2 73: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] new d7eca240e 74: onsuccess: 1: Successful build after binutils/gdb: 2 commits new 91ebf9353 75: onsuccess: 1: Successful build after linux: 44 commits new 3687b0307 76: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] new e35b3786f 77: onsuccess: 1: Successful build after gcc/linux/glibc: 22 commits new e87545e12 78: onsuccess: 1: Successful build after binutils/gcc/gdb: 4 commits new e784f0173 79: onsuccess: 1: Successful build after binutils/gcc/glibc/g [...] new 531759ca5 80: onsuccess: 1: Successful build after binutils/gcc/glibc/g [...] new a6a9e5534 81: onsuccess: 1: Successful build after binutils/gcc/gdb: 6 commits new 74365579c 82: onsuccess: 1: Successful build after binutils/gcc/gdb: 11 [...] new fe62cb5d2 83: onsuccess: 1: Success after binutils/gcc/glibc/gdb: 17 commits new d3962ad70 84: onsuccess: 1: Success after binutils/gcc/linux/gdb: 68 commits new 470357452 85: onsuccess: 1: Success after binutils/gcc/glibc/gdb/qemu: [...] new a21ab6367 86: onsuccess: 1: Success after binutils/gcc/gdb: 7 commits new 4109ce939 87: onsuccess: 1: Success after binutils/gcc/gdb: 14 commits new 3b75bb8b8 88: onsuccess: 1: Success after gcc/linux/qemu: 149 commits new 16e3725d7 89: onsuccess: 1: Success after binutils/gcc/gdb: 5 commits new 893172ad2 90: onsuccess: 1: Success after binutils/gcc/gdb: 19 commits new 1909a930a 91: onsuccess: 1: Success after binutils/gcc/gdb: 8 commits new 3f8fe43fe 92: onsuccess: 1: Success after binutils/gcc/linux/gdb/qemu: [...] new 0821d1e40 93: onsuccess: 1: Success after binutils/gcc/linux/gdb: 88 commits new 90e3674ae 94: onsuccess: 1: Success after gcc: openmp: Partial OpenMP 5 [...] new 37ea60cce 95: onsuccess: #2070: 1: Success after basepoints/gcc-13-2389 [...] new fda124138 96: onsuccess: #2071: 1: Success after gcc/linux: 56 commits new 4eb248c84 97: onsuccess: #2072: 1: Success after binutils/gcc/gdb: 3 commits new 1ff02ff4a 98: onsuccess: #2073: 1: Success after gcc/linux: 11 commits new 936a8d905 99: onsuccess: #2074: 1: Success after baseline build: no new [...] new ff4d305d3 100: onsuccess: #2077: 1: Success after binutils/gcc/linux/gd [...] new de1e25c2a 101: onsuccess: #2130: 1: Success after binutils: 81 commits new 51124edaa 102: onsuccess: #2133: 1: Success after gdb-12-branchpoint-19 [...] new eec9ff7b4 103: onsuccess: #2135: 1: Success after gcc/linux/glibc/gdb/q [...] new 14b1242b0 104: onsuccess: #2136: 1: Success after binutils/gcc/gdb: 3 commits new 091a9c057 105: onsuccess: #2137: 1: Success after basepoints/gcc-13-271 [...] new 7487b7463 106: onsuccess: #2138: 1: Success after binutils/gcc/glibc/gd [...] new 1390536b9 107: onsuccess: #2139: 1: Success after binutils/gcc/gdb: 3 commits new bddd2aa1c 108: onsuccess: #2140: 1: Success after binutils/gcc/gdb: 5 commits new 36233c649 109: onsuccess: #2141: 1: Success after gcc/glibc: 6 commits new e39c87392 110: onsuccess: #2142: 1: Success after binutils/gcc/glibc/gd [...] new dd3f88e80 111: onsuccess: #2143: 1: Success after binutils/gcc/linux/gl [...] new 11c304330 112: onsuccess: #2144: 1: Success after binutils/gcc/glibc/gd [...] new de5f591f6 113: onsuccess: #2145: 1: Success after binutils/gcc/glibc/gd [...] new ca424385e 114: onsuccess: #2146: 1: Success after binutils/gcc/glibc/gd [...] new 05e681558 115: onsuccess: #2147: 1: Success after binutils/linux/glibc/ [...] new aa5de271b 116: onsuccess: #2148: 1: Success after binutils/gcc/gdb: 7 commits new f53de9ff1 117: onsuccess: #2150: 1: Success after binutils/gcc/glibc/gd [...] new d5b194c71 118: onsuccess: #2151: 1: Success after binutils/gcc/linux/gl [...] new 4429de90d 119: onsuccess: #2154: 1: Success after binutils/gcc/linux/gl [...] new b86257f97 120: onsuccess: #2155: 1: Success after binutils/gcc/linux/gl [...] new 4fd81086d 121: onsuccess: #2156: 1: Success after binutils/gcc/linux/gd [...] new e55547bd7 122: onsuccess: #2157: 1: Success after binutils/gcc/gdb: 6 commits new a1383f684 123: onsuccess: #2158: 1: Success after basepoints/gcc-13-283 [...] new cdfd41346 124: onsuccess: #2159: 1: Success after linux: 23 commits new 2a4f7d9d6 125: onsuccess: #2160: 1: Success after binutils/gcc/linux/gd [...] new 83e91162b 126: onsuccess: #2161: 1: Success after basepoints/gcc-13-283 [...] new 4021a0cc2 127: onsuccess: #2162: 1: Success after gcc: 9 commits new c9fa4b4fe 128: onsuccess: #2163: 1: Success after linux: 23 commits new f9d96f803 129: onsuccess: #2164: 1: Success after binutils/gcc/linux/gd [...] new 87824472f 130: onsuccess: #2165: 1: Success after binutils/gcc/gdb: 32 commits new da022fa3e 131: onsuccess: #2166: 1: Success after binutils/gcc/gdb: 12 commits new 0b9b399ff 132: onsuccess: #2167: 1: Success after binutils/gcc/glibc/gd [...] new ba42e673a 133: onsuccess: #2168: 1: Success after binutils/gcc/linux/gd [...] new 0f0d5e2c5 134: onsuccess: #2169: 1: Success after binutils/gcc/gdb: 13 commits new 0f44721c6 135: onsuccess: #2170: 1: Success after gcc/linux/qemu: 63 commits new e183ab724 136: onsuccess: #2171: 1: Success after binutils/gcc/gdb/qemu [...] new c4a6b1ec5 137: onsuccess: #2172: 1: Success after binutils/gcc/linux/gl [...] new 419600e24 138: onsuccess: #2173: 1: Success after binutils/gcc/gdb: 5 commits new e83b49d64 139: onsuccess: #2174: 1: Success after binutils/gcc/gdb: 13 commits new 274ea7ab1 140: onsuccess: #2175: 1: Success after binutils/gcc/linux/gl [...] new 28d10fffd 141: onsuccess: #2176: 1: Success after binutils/gcc/gdb: 6 commits new bc70d1cf0 142: onsuccess: #2177: 1: Success after gcc/glibc: 4 commits new 4b6a42f6e 143: onsuccess: #2178: 1: Success after binutils/gcc/gdb/qemu [...] new b084eed31 144: onsuccess: #2179: 1: Success after binutils/gcc/linux/gd [...] new 563cb87b5 145: onsuccess: #2180: 1: Success after binutils/gcc/linux/gd [...] new 9e4f4174f 146: onsuccess: #2181: 1: Success after binutils/glibc/gdb: 2 [...] new 8eb6bc059 147: onsuccess: #2182: 1: Success after binutils/gcc/gdb: 18 commits new 49de3f8e9 148: onsuccess: #2183: 1: Success after gcc/linux/glibc: 64 commits new b583b3e13 149: onsuccess: #2184: 1: Success after binutils/gcc/linux/gd [...] new 848f26f1c 150: onsuccess: #2185: 1: Success after gcc: 3 commits new 26b5195b4 151: onsuccess: #2186: 1: Success after gcc: 2 commits new cd65df7f8 152: onsuccess: #2187: 1: Success after gcc/linux/glibc: 22 commits new 160de5544 153: onsuccess: #2188: 1: Success after binutils/gcc/gdb: 3 commits new a82a0c79f 154: onsuccess: #2189: 1: Success after binutils/gcc/gdb: 18 commits new 01fc05a6e 155: onsuccess: #2190: 1: Success after binutils/gcc/linux/gd [...] new 068e421f8 156: onsuccess: #2191: 1: Success after binutils/gcc/linux/gd [...]

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 (94826eac4) \ 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 1700 -> 1748 bytes 02-prepare_abe/console.log.xz | Bin 2728 -> 2736 bytes 03-build_abe-binutils/console.log.xz | Bin 30368 -> 30136 bytes 04-build_abe-stage1/console.log.xz | Bin 72316 -> 72460 bytes 05-clean_sysroot/console.log.xz | Bin 328 -> 328 bytes 06-build_abe-linux/console.log.xz | Bin 8548 -> 8320 bytes 07-build_abe-glibc/console.log.xz | Bin 239844 -> 239796 bytes 08-build_abe-stage2/console.log.xz | Bin 203196 -> 203216 bytes 09-build_abe-gdb/console.log.xz | Bin 37712 -> 37548 bytes 10-build_abe-qemu/console.log.xz | Bin 31936 -> 31928 bytes 11-build_abe-dejagnu/console.log.xz | Bin 3900 -> 3880 bytes 12-build_abe-check_gcc/console.log.xz | Bin 2568 -> 2440 bytes 13-check_regression/console.log.xz | Bin 9528 -> 6008 bytes 13-check_regression/extra-bisect-params | 1 + 13-check_regression/fails.sum | 8 + 13-check_regression/mail-body.txt | 129 +- 13-check_regression/results.compare | 68 +- 13-check_regression/results.compare2 | 732 +---- 13-check_regression/results.regressions | 28 + 14-update_baseline/console.log | 46 +- 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 | 131 +- mail/mail-subject.txt | 2 +- manifest.sh | 36 +- results | 28 + sumfiles/g++.log.xz | Bin 3411884 -> 3408516 bytes sumfiles/g++.sum | 171 +- sumfiles/gcc.log.xz | Bin 3031720 -> 3023416 bytes sumfiles/gcc.sum | 4435 ++++++++++++++++--------------- sumfiles/gfortran.log.xz | Bin 1034672 -> 1033820 bytes sumfiles/gfortran.sum | 44 +- sumfiles/libatomic.log.xz | Bin 2288 -> 2292 bytes sumfiles/libatomic.sum | 4 +- sumfiles/libgomp.log.xz | Bin 202288 -> 202416 bytes sumfiles/libgomp.sum | 16 +- sumfiles/libitm.log.xz | Bin 2656 -> 2664 bytes sumfiles/libitm.sum | 6 +- sumfiles/libstdc++.log.xz | Bin 427432 -> 423608 bytes sumfiles/libstdc++.sum | 18 +- 44 files changed, 2557 insertions(+), 3358 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