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 71f554bdb1 154: onsuccess: #2189: 1: Success after binutils/gcc/gdb: 18 [...] discards 25cc411511 153: onsuccess: #2188: 1: Success after binutils/gcc/gdb: 3 commits discards f6c92d1503 152: onsuccess: #2187: 1: Success after gcc/linux/glibc: 22 commits discards 864296c798 151: onsuccess: #2186: 1: Success after gcc: 2 commits discards 2edc7eea38 150: onsuccess: #2185: 1: Success after gcc: 3 commits discards a2a347de9f 149: onsuccess: #2184: 1: Success after binutils/gcc/linux/g [...] discards bbbf11ee45 148: onsuccess: #2183: 1: Success after gcc/linux/glibc: 64 commits discards 84dc5a2b68 147: onsuccess: #2182: 1: Success after binutils/gcc/gdb: 18 [...] discards b3db7cc387 146: onsuccess: #2181: 1: Success after binutils/glibc/gdb: [...] discards a813b5b6a1 145: onsuccess: #2180: 1: Success after binutils/gcc/linux/g [...] discards 650dcc5464 144: onsuccess: #2179: 1: Success after binutils/gcc/linux/g [...] discards a07bcdb306 143: onsuccess: #2178: 1: Success after binutils/gcc/gdb/qem [...] discards 68f3ff84c8 142: onsuccess: #2177: 1: Success after gcc/glibc: 4 commits discards 516568f786 141: onsuccess: #2176: 1: Success after binutils/gcc/gdb: 6 commits discards 3cb57b59bb 140: onsuccess: #2175: 1: Success after binutils/gcc/linux/g [...] discards 6b19e634cf 139: onsuccess: #2174: 1: Success after binutils/gcc/gdb: 13 [...] discards 2bfe33c0af 138: onsuccess: #2173: 1: Success after binutils/gcc/gdb: 5 commits discards 30e5ede381 137: onsuccess: #2172: 1: Success after binutils/gcc/linux/g [...] discards df2d235808 136: onsuccess: #2171: 1: Success after binutils/gcc/gdb/qem [...] discards 539572a8d3 135: onsuccess: #2170: 1: Success after gcc/linux/qemu: 63 commits discards fa84d0d547 134: onsuccess: #2169: 1: Success after binutils/gcc/gdb: 13 [...] discards fefeaae2cc 133: onsuccess: #2168: 1: Success after binutils/gcc/linux/g [...] discards 9a56e7436f 132: onsuccess: #2167: 1: Success after binutils/gcc/glibc/g [...] discards abf11365a2 131: onsuccess: #2166: 1: Success after binutils/gcc/gdb: 12 [...] discards a2cbf0188f 130: onsuccess: #2165: 1: Success after binutils/gcc/gdb: 32 [...] discards cc9b35b3b1 129: onsuccess: #2164: 1: Success after binutils/gcc/linux/g [...] discards 09b1c5ba75 128: onsuccess: #2163: 1: Success after linux: 23 commits discards a4a18fe655 127: onsuccess: #2162: 1: Success after gcc: 9 commits discards 13d18aac66 126: onsuccess: #2161: 1: Success after basepoints/gcc-13-28 [...] discards 18e91df37e 125: onsuccess: #2160: 1: Success after binutils/gcc/linux/g [...] discards 6ce8802fd0 124: onsuccess: #2159: 1: Success after linux: 23 commits discards 4cde71f5fe 123: onsuccess: #2158: 1: Success after basepoints/gcc-13-28 [...] discards 796dd6cfbc 122: onsuccess: #2157: 1: Success after binutils/gcc/gdb: 6 commits discards 87870cea6c 121: onsuccess: #2156: 1: Success after binutils/gcc/linux/g [...] discards 87eb4bce48 120: onsuccess: #2155: 1: Success after binutils/gcc/linux/g [...] discards b9e067cf8a 119: onsuccess: #2154: 1: Success after binutils/gcc/linux/g [...] discards 5dc4416720 118: onsuccess: #2151: 1: Success after binutils/gcc/linux/g [...] discards b85803a92f 117: onsuccess: #2150: 1: Success after binutils/gcc/glibc/g [...] discards 93e8cfecbd 116: onsuccess: #2148: 1: Success after binutils/gcc/gdb: 7 commits discards 213acea74c 115: onsuccess: #2147: 1: Success after binutils/linux/glibc [...] discards fd488ab35c 114: onsuccess: #2146: 1: Success after binutils/gcc/glibc/g [...] discards fbc1b40a3d 113: onsuccess: #2145: 1: Success after binutils/gcc/glibc/g [...] discards 08e4d4814f 112: onsuccess: #2144: 1: Success after binutils/gcc/glibc/g [...] discards 0fc7da07e8 111: onsuccess: #2143: 1: Success after binutils/gcc/linux/g [...] discards 12fae94892 110: onsuccess: #2142: 1: Success after binutils/gcc/glibc/g [...] discards 25fb2ace23 109: onsuccess: #2141: 1: Success after gcc/glibc: 6 commits discards 487fe1ff7a 108: onsuccess: #2140: 1: Success after binutils/gcc/gdb: 5 commits discards fc1155c886 107: onsuccess: #2139: 1: Success after binutils/gcc/gdb: 3 commits discards ab6208f50d 106: onsuccess: #2138: 1: Success after binutils/gcc/glibc/g [...] discards 7e8e336a57 105: onsuccess: #2137: 1: Success after basepoints/gcc-13-27 [...] discards b7dc133863 104: onsuccess: #2136: 1: Success after binutils/gcc/gdb: 3 commits discards 6d89c82827 103: onsuccess: #2135: 1: Success after gcc/linux/glibc/gdb/ [...] discards 24e54cb662 102: onsuccess: #2133: 1: Success after gdb-12-branchpoint-1 [...] discards 628325fa6a 101: onsuccess: #2130: 1: Success after binutils: 81 commits discards 350d4713e0 100: onsuccess: #2077: 1: Success after binutils/gcc/linux/g [...] discards 4c69320477 99: onsuccess: #2074: 1: Success after baseline build: no ne [...] discards 6ebd5dadf6 98: onsuccess: #2073: 1: Success after gcc/linux: 11 commits discards 3c0c6d495e 97: onsuccess: #2072: 1: Success after binutils/gcc/gdb: 3 commits discards a82cf3602c 96: onsuccess: #2071: 1: Success after gcc/linux: 56 commits discards d1b2427d67 95: onsuccess: #2070: 1: Success after basepoints/gcc-13-238 [...] discards 8a365cf2a5 94: onsuccess: 1: Success after gcc: openmp: Partial OpenMP [...] discards 728856177d 93: onsuccess: 1: Success after binutils/gcc/linux/gdb: 88 commits discards 4778ac950e 92: onsuccess: 1: Success after binutils/gcc/linux/gdb/qemu: [...] discards 702d6b42a3 91: onsuccess: 1: Success after binutils/gcc/gdb: 8 commits discards 7d8fd5fc42 90: onsuccess: 1: Success after binutils/gcc/gdb: 19 commits discards 7030de2c24 89: onsuccess: 1: Success after binutils/gcc/gdb: 5 commits discards 4d82e1c116 88: onsuccess: 1: Success after gcc/linux/qemu: 149 commits discards dbfc541e4b 87: onsuccess: 1: Success after binutils/gcc/gdb: 14 commits discards 27090cdfab 86: onsuccess: 1: Success after binutils/gcc/gdb: 7 commits discards e5f153c843 85: onsuccess: 1: Success after binutils/gcc/glibc/gdb/qemu: [...] discards 79b23630d5 84: onsuccess: 1: Success after binutils/gcc/linux/gdb: 68 commits discards eca1677e17 83: onsuccess: 1: Success after binutils/gcc/glibc/gdb: 17 commits discards 5b62c17768 82: onsuccess: 1: Successful build after binutils/gcc/gdb: 1 [...] discards 8d364e5b6d 81: onsuccess: 1: Successful build after binutils/gcc/gdb: 6 [...] discards 390e1e966e 80: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] discards 3239c67024 79: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] discards 5f9cb89224 78: onsuccess: 1: Successful build after binutils/gcc/gdb: 4 [...] discards 8f5c8cd4ff 77: onsuccess: 1: Successful build after gcc/linux/glibc: 22 [...] discards 5c8ff8f4d5 76: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 74734d50ee 75: onsuccess: 1: Successful build after linux: 44 commits discards 8a32fc4488 74: onsuccess: 1: Successful build after binutils/gdb: 2 commits discards cbc8a6ee89 73: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards ce233d5e6b 72: onsuccess: 1: Successful build after linux: 12 commits discards fb88d81a54 71: onsuccess: 1: Successful build after gcc/glibc: 3 commits discards feb063d296 70: onsuccess: 1: Successful build after binutils/gcc/gdb: 4 [...] discards c04746aba0 69: onsuccess: 1: Successful build after binutils/gcc/gdb: 5 [...] discards e064d825eb 68: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 7e83936eb8 67: onsuccess: 1: Successful build after binutils/gcc/gdb: 1 [...] discards 48b5bd8c40 66: onsuccess: 1: Successful build after gcc/glibc: 10 commits discards 8d217635b6 65: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards fc01bf115c 64: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 00c5a29a07 63: onsuccess: 1: Successful build after binutils/gcc/gdb: 8 [...] discards 0791c14d58 62: onsuccess: 1: Successful build after binutils/gcc/gdb: 2 [...] discards 556572c05d 61: onsuccess: 1: Successful build after binutils/gcc/gdb/qe [...] discards 8890bfccff 60: onsuccess: 1: Successful build after glibc: 2 commits discards 8ad950b6f9 59: onsuccess: 1: Successful build after binutils: 2 commits discards 61447effca 58: onsuccess: 1: Successful build after binutils: gdb: new [...] discards 48a6a6ebaa 57: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] discards 4d23312c09 56: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 2b11c3cbe1 55: onsuccess: 1: Successful build after gcc/linux/glibc/qem [...] discards 34ca317eef 54: onsuccess: 1: Successful build after binutils/gcc/gdb: 8 [...] new e52a06d913 54: onsuccess: 1: Successful build after binutils/gcc/gdb: 8 [...] new 9eaeee48ff 55: onsuccess: 1: Successful build after gcc/linux/glibc/qem [...] new c4f0e6dd5d 56: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 3b408c19f9 57: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] new bacb609864 58: onsuccess: 1: Successful build after binutils: gdb: new [...] new e68efca98b 59: onsuccess: 1: Successful build after binutils: 2 commits new 00dd264d68 60: onsuccess: 1: Successful build after glibc: 2 commits new 09be2e9eac 61: onsuccess: 1: Successful build after binutils/gcc/gdb/qe [...] new 22cbfb5caf 62: onsuccess: 1: Successful build after binutils/gcc/gdb: 2 [...] new 6d8e2b15bb 63: onsuccess: 1: Successful build after binutils/gcc/gdb: 8 [...] new ea50043cbe 64: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 79647b2547 65: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new aa822a57fa 66: onsuccess: 1: Successful build after gcc/glibc: 10 commits new a53f559573 67: onsuccess: 1: Successful build after binutils/gcc/gdb: 1 [...] new 4690a12c23 68: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new f736cba4f8 69: onsuccess: 1: Successful build after binutils/gcc/gdb: 5 [...] new 5a294ee92c 70: onsuccess: 1: Successful build after binutils/gcc/gdb: 4 [...] new 460075457c 71: onsuccess: 1: Successful build after gcc/glibc: 3 commits new 3b5ae4e322 72: onsuccess: 1: Successful build after linux: 12 commits new 5f678f5d26 73: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 664c4cd968 74: onsuccess: 1: Successful build after binutils/gdb: 2 commits new 25d3a5649d 75: onsuccess: 1: Successful build after linux: 44 commits new 487a7f6b54 76: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 5bb657995f 77: onsuccess: 1: Successful build after gcc/linux/glibc: 22 [...] new 1f80d0fa7f 78: onsuccess: 1: Successful build after binutils/gcc/gdb: 4 [...] new 0b24af59dc 79: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] new 41156ccd7e 80: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] new a79cc899b5 81: onsuccess: 1: Successful build after binutils/gcc/gdb: 6 [...] new 5e70677787 82: onsuccess: 1: Successful build after binutils/gcc/gdb: 1 [...] new c9aa8f0a90 83: onsuccess: 1: Success after binutils/gcc/glibc/gdb: 17 commits new 5ef3e5fbae 84: onsuccess: 1: Success after binutils/gcc/linux/gdb: 68 commits new 3c4f0899d8 85: onsuccess: 1: Success after binutils/gcc/glibc/gdb/qemu: [...] new 5c48491f6a 86: onsuccess: 1: Success after binutils/gcc/gdb: 7 commits new f363095c40 87: onsuccess: 1: Success after binutils/gcc/gdb: 14 commits new 5089cbd7ee 88: onsuccess: 1: Success after gcc/linux/qemu: 149 commits new a4a93b4afb 89: onsuccess: 1: Success after binutils/gcc/gdb: 5 commits new 1291957ee0 90: onsuccess: 1: Success after binutils/gcc/gdb: 19 commits new 7b0e265e72 91: onsuccess: 1: Success after binutils/gcc/gdb: 8 commits new 924afcb9b9 92: onsuccess: 1: Success after binutils/gcc/linux/gdb/qemu: [...] new e5d165a355 93: onsuccess: 1: Success after binutils/gcc/linux/gdb: 88 commits new e2401bddc3 94: onsuccess: 1: Success after gcc: openmp: Partial OpenMP [...] new aed6ddb410 95: onsuccess: #2070: 1: Success after basepoints/gcc-13-238 [...] new 0414a21784 96: onsuccess: #2071: 1: Success after gcc/linux: 56 commits new a2f03f66dc 97: onsuccess: #2072: 1: Success after binutils/gcc/gdb: 3 commits new de89e74e24 98: onsuccess: #2073: 1: Success after gcc/linux: 11 commits new 42ba2f78bc 99: onsuccess: #2074: 1: Success after baseline build: no ne [...] new db9ccc04d3 100: onsuccess: #2077: 1: Success after binutils/gcc/linux/g [...] new b76df77aa2 101: onsuccess: #2130: 1: Success after binutils: 81 commits new 170c80e02c 102: onsuccess: #2133: 1: Success after gdb-12-branchpoint-1 [...] new 443e408ba7 103: onsuccess: #2135: 1: Success after gcc/linux/glibc/gdb/ [...] new 73339f110f 104: onsuccess: #2136: 1: Success after binutils/gcc/gdb: 3 commits new c1dc9ad219 105: onsuccess: #2137: 1: Success after basepoints/gcc-13-27 [...] new ff6b10e572 106: onsuccess: #2138: 1: Success after binutils/gcc/glibc/g [...] new edaf4db5b1 107: onsuccess: #2139: 1: Success after binutils/gcc/gdb: 3 commits new cfe50d1ad3 108: onsuccess: #2140: 1: Success after binutils/gcc/gdb: 5 commits new 448ec07cc0 109: onsuccess: #2141: 1: Success after gcc/glibc: 6 commits new 962e9dfcd8 110: onsuccess: #2142: 1: Success after binutils/gcc/glibc/g [...] new 7fac7042d2 111: onsuccess: #2143: 1: Success after binutils/gcc/linux/g [...] new d4088026f5 112: onsuccess: #2144: 1: Success after binutils/gcc/glibc/g [...] new e91028af33 113: onsuccess: #2145: 1: Success after binutils/gcc/glibc/g [...] new d2b25fff9d 114: onsuccess: #2146: 1: Success after binutils/gcc/glibc/g [...] new 3ed3ee32c6 115: onsuccess: #2147: 1: Success after binutils/linux/glibc [...] new 9f5555d2ed 116: onsuccess: #2148: 1: Success after binutils/gcc/gdb: 7 commits new 7ab72da4ab 117: onsuccess: #2150: 1: Success after binutils/gcc/glibc/g [...] new ba59b8491d 118: onsuccess: #2151: 1: Success after binutils/gcc/linux/g [...] new 4dfe7484bd 119: onsuccess: #2154: 1: Success after binutils/gcc/linux/g [...] new 0f72394213 120: onsuccess: #2155: 1: Success after binutils/gcc/linux/g [...] new 5cad7ce7e3 121: onsuccess: #2156: 1: Success after binutils/gcc/linux/g [...] new 5be70e4c79 122: onsuccess: #2157: 1: Success after binutils/gcc/gdb: 6 commits new 7328d5ac95 123: onsuccess: #2158: 1: Success after basepoints/gcc-13-28 [...] new 65a38d1193 124: onsuccess: #2159: 1: Success after linux: 23 commits new b0ee3aa118 125: onsuccess: #2160: 1: Success after binutils/gcc/linux/g [...] new 92b89630bc 126: onsuccess: #2161: 1: Success after basepoints/gcc-13-28 [...] new 4e22b93178 127: onsuccess: #2162: 1: Success after gcc: 9 commits new e387e9eee9 128: onsuccess: #2163: 1: Success after linux: 23 commits new aa7cde98da 129: onsuccess: #2164: 1: Success after binutils/gcc/linux/g [...] new 20cbc9c86e 130: onsuccess: #2165: 1: Success after binutils/gcc/gdb: 32 [...] new d25e54e99e 131: onsuccess: #2166: 1: Success after binutils/gcc/gdb: 12 [...] new 7bc723f080 132: onsuccess: #2167: 1: Success after binutils/gcc/glibc/g [...] new 9d958f4607 133: onsuccess: #2168: 1: Success after binutils/gcc/linux/g [...] new 24a6e24ed0 134: onsuccess: #2169: 1: Success after binutils/gcc/gdb: 13 [...] new af68149978 135: onsuccess: #2170: 1: Success after gcc/linux/qemu: 63 commits new d8d46cdbea 136: onsuccess: #2171: 1: Success after binutils/gcc/gdb/qem [...] new 63bd572742 137: onsuccess: #2172: 1: Success after binutils/gcc/linux/g [...] new 29d0d6f2bb 138: onsuccess: #2173: 1: Success after binutils/gcc/gdb: 5 commits new ceb0933f6e 139: onsuccess: #2174: 1: Success after binutils/gcc/gdb: 13 [...] new de036dfc3a 140: onsuccess: #2175: 1: Success after binutils/gcc/linux/g [...] new 09660b14e4 141: onsuccess: #2176: 1: Success after binutils/gcc/gdb: 6 commits new 6d62db8971 142: onsuccess: #2177: 1: Success after gcc/glibc: 4 commits new 18c95ca237 143: onsuccess: #2178: 1: Success after binutils/gcc/gdb/qem [...] new e9527f858b 144: onsuccess: #2179: 1: Success after binutils/gcc/linux/g [...] new 0e7b02a0fd 145: onsuccess: #2180: 1: Success after binutils/gcc/linux/g [...] new 47c2fd9eed 146: onsuccess: #2181: 1: Success after binutils/glibc/gdb: [...] new 43bf08fb6b 147: onsuccess: #2182: 1: Success after binutils/gcc/gdb: 18 [...] new 37a536a95c 148: onsuccess: #2183: 1: Success after gcc/linux/glibc: 64 commits new 7ae279969a 149: onsuccess: #2184: 1: Success after binutils/gcc/linux/g [...] new 2a81a2affa 150: onsuccess: #2185: 1: Success after gcc: 3 commits new 8d8dd18c8e 151: onsuccess: #2186: 1: Success after gcc: 2 commits new 7094769710 152: onsuccess: #2187: 1: Success after gcc/linux/glibc: 22 commits new 319001da96 153: onsuccess: #2188: 1: Success after binutils/gcc/gdb: 3 commits new 330b64206e 154: onsuccess: #2189: 1: Success after binutils/gcc/gdb: 18 [...] new 94826eac49 155: onsuccess: #2190: 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 (71f554bdb1) \ 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 1704 -> 1700 bytes 02-prepare_abe/console.log.xz | Bin 2744 -> 2728 bytes 03-build_abe-binutils/console.log.xz | Bin 30832 -> 30368 bytes 04-build_abe-stage1/console.log.xz | Bin 72680 -> 72316 bytes 05-clean_sysroot/console.log.xz | Bin 328 -> 328 bytes 06-build_abe-linux/console.log.xz | Bin 8928 -> 8548 bytes 07-build_abe-glibc/console.log.xz | Bin 240008 -> 239844 bytes 08-build_abe-stage2/console.log.xz | Bin 203648 -> 203196 bytes 09-build_abe-gdb/console.log.xz | Bin 38152 -> 37712 bytes 10-build_abe-qemu/console.log.xz | Bin 31844 -> 31936 bytes 11-build_abe-dejagnu/console.log.xz | Bin 3880 -> 3900 bytes 12-build_abe-check_gcc/console.log.xz | Bin 2880 -> 2568 bytes 13-check_regression/console.log.xz | Bin 18844 -> 9528 bytes 13-check_regression/extra-bisect-params | 1 - 13-check_regression/fails.sum | 11 - 13-check_regression/mail-body.txt | 143 +- 13-check_regression/results.compare | 345 +- 13-check_regression/results.compare2 | 3316 +++---------------- 13-check_regression/results.regressions | 101 - 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 | 145 +- mail/mail-subject.txt | 2 +- manifest.sh | 36 +- results | 101 - sumfiles/g++.log.xz | Bin 3415412 -> 3411884 bytes sumfiles/g++.sum | 148 +- sumfiles/gcc.log.xz | Bin 3030792 -> 3031720 bytes sumfiles/gcc.sum | 5311 +++++++++++++++---------------- sumfiles/gfortran.log.xz | Bin 1029700 -> 1034672 bytes sumfiles/gfortran.sum | 44 +- sumfiles/libatomic.log.xz | Bin 2288 -> 2288 bytes sumfiles/libatomic.sum | 4 +- sumfiles/libgomp.log.xz | Bin 202448 -> 202288 bytes sumfiles/libgomp.sum | 16 +- sumfiles/libitm.log.xz | Bin 2656 -> 2656 bytes sumfiles/libitm.sum | 6 +- sumfiles/libstdc++.log.xz | Bin 423268 -> 427432 bytes sumfiles/libstdc++.sum | 16 +- 44 files changed, 3368 insertions(+), 6458 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