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 a6c9296282 162: onsuccess: #2197: 1: Success after binutils/gcc/glibc/g [...] discards 621a2452eb 161: onsuccess: #2196: 1: Success after binutils/gcc/linux/g [...] discards 7c5aca15f0 160: onsuccess: #2195: 1: Success after binutils/gcc/linux/g [...] discards 71b860bdf2 159: onsuccess: #2194: 1: Success after gcc/linux/glibc: 197 [...] discards d50bcfacee 158: onsuccess: #2193: 1: Success after binutils/gcc/glibc/g [...] discards 8963064629 157: onsuccess: #2192: 1: Success after binutils/gcc/gdb: 8 commits discards a0f5868d83 156: onsuccess: #2191: 1: Success after binutils/gcc/linux/g [...] discards d016f47839 155: onsuccess: #2190: 1: Success after binutils/gcc/linux/g [...] discards fcf10b984c 154: onsuccess: #2189: 1: Success after binutils/gcc/gdb: 18 [...] discards 77d3a8c9ae 153: onsuccess: #2188: 1: Success after binutils/gcc/gdb: 3 commits discards 191cea079d 152: onsuccess: #2187: 1: Success after gcc/linux/glibc: 22 commits discards 0048261030 151: onsuccess: #2186: 1: Success after gcc: 2 commits discards a78b18ba76 150: onsuccess: #2185: 1: Success after gcc: 3 commits discards 3ed285fd18 149: onsuccess: #2184: 1: Success after binutils/gcc/linux/g [...] discards 34b0cb1abd 148: onsuccess: #2183: 1: Success after gcc/linux/glibc: 64 commits discards 5a59f0914f 147: onsuccess: #2182: 1: Success after binutils/gcc/gdb: 18 [...] discards afdd380d0e 146: onsuccess: #2181: 1: Success after binutils/glibc/gdb: [...] discards 452ece8007 145: onsuccess: #2180: 1: Success after binutils/gcc/linux/g [...] discards 0273822d48 144: onsuccess: #2179: 1: Success after binutils/gcc/linux/g [...] discards 2dc81b6626 143: onsuccess: #2178: 1: Success after binutils/gcc/gdb/qem [...] discards f81b2d68aa 142: onsuccess: #2177: 1: Success after gcc/glibc: 4 commits discards ed7f3ff16c 141: onsuccess: #2176: 1: Success after binutils/gcc/gdb: 6 commits discards 77a0952fd7 140: onsuccess: #2175: 1: Success after binutils/gcc/linux/g [...] discards 9a784d11cc 139: onsuccess: #2174: 1: Success after binutils/gcc/gdb: 13 [...] discards faa8d994e1 138: onsuccess: #2173: 1: Success after binutils/gcc/gdb: 5 commits discards 897008f1e6 137: onsuccess: #2172: 1: Success after binutils/gcc/linux/g [...] discards 265d1c05e2 136: onsuccess: #2171: 1: Success after binutils/gcc/gdb/qem [...] discards 787012bc19 135: onsuccess: #2170: 1: Success after gcc/linux/qemu: 63 commits discards f42268936e 134: onsuccess: #2169: 1: Success after binutils/gcc/gdb: 13 [...] discards 0514bab253 133: onsuccess: #2168: 1: Success after binutils/gcc/linux/g [...] discards 4801292882 132: onsuccess: #2167: 1: Success after binutils/gcc/glibc/g [...] discards 1c4850af1f 131: onsuccess: #2166: 1: Success after binutils/gcc/gdb: 12 [...] discards d762e9595d 130: onsuccess: #2165: 1: Success after binutils/gcc/gdb: 32 [...] discards ea1b7f5432 129: onsuccess: #2164: 1: Success after binutils/gcc/linux/g [...] discards 1f01297726 128: onsuccess: #2163: 1: Success after linux: 23 commits discards 05461d31f3 127: onsuccess: #2162: 1: Success after gcc: 9 commits discards 29ae108f36 126: onsuccess: #2161: 1: Success after basepoints/gcc-13-28 [...] discards 12d05888ac 125: onsuccess: #2160: 1: Success after binutils/gcc/linux/g [...] discards b5b938b0cc 124: onsuccess: #2159: 1: Success after linux: 23 commits discards 4c798f71f0 123: onsuccess: #2158: 1: Success after basepoints/gcc-13-28 [...] discards 9ec7d537f4 122: onsuccess: #2157: 1: Success after binutils/gcc/gdb: 6 commits discards f8ea90f269 121: onsuccess: #2156: 1: Success after binutils/gcc/linux/g [...] discards dfc64be600 120: onsuccess: #2155: 1: Success after binutils/gcc/linux/g [...] discards 8f0c10d96e 119: onsuccess: #2154: 1: Success after binutils/gcc/linux/g [...] discards 02bd408d81 118: onsuccess: #2151: 1: Success after binutils/gcc/linux/g [...] discards 7eb8a3f99c 117: onsuccess: #2150: 1: Success after binutils/gcc/glibc/g [...] discards b4e129f0f6 116: onsuccess: #2148: 1: Success after binutils/gcc/gdb: 7 commits discards 4bd8d63331 115: onsuccess: #2147: 1: Success after binutils/linux/glibc [...] discards ad96eb2366 114: onsuccess: #2146: 1: Success after binutils/gcc/glibc/g [...] discards 418518d092 113: onsuccess: #2145: 1: Success after binutils/gcc/glibc/g [...] discards aea3ed83f3 112: onsuccess: #2144: 1: Success after binutils/gcc/glibc/g [...] discards 9c0a521241 111: onsuccess: #2143: 1: Success after binutils/gcc/linux/g [...] discards d55267530a 110: onsuccess: #2142: 1: Success after binutils/gcc/glibc/g [...] discards 5ad31d859b 109: onsuccess: #2141: 1: Success after gcc/glibc: 6 commits discards e43322fc9e 108: onsuccess: #2140: 1: Success after binutils/gcc/gdb: 5 commits discards 1101692d58 107: onsuccess: #2139: 1: Success after binutils/gcc/gdb: 3 commits discards c848972de4 106: onsuccess: #2138: 1: Success after binutils/gcc/glibc/g [...] discards b3e981321c 105: onsuccess: #2137: 1: Success after basepoints/gcc-13-27 [...] discards 8e28af31b8 104: onsuccess: #2136: 1: Success after binutils/gcc/gdb: 3 commits discards f63431ce89 103: onsuccess: #2135: 1: Success after gcc/linux/glibc/gdb/ [...] discards ad89073ba2 102: onsuccess: #2133: 1: Success after gdb-12-branchpoint-1 [...] discards 5b0c70bcd8 101: onsuccess: #2130: 1: Success after binutils: 81 commits discards d81bcac289 100: onsuccess: #2077: 1: Success after binutils/gcc/linux/g [...] discards a0e6970b29 99: onsuccess: #2074: 1: Success after baseline build: no ne [...] discards 8f4a7f8269 98: onsuccess: #2073: 1: Success after gcc/linux: 11 commits discards 4ced6a8bab 97: onsuccess: #2072: 1: Success after binutils/gcc/gdb: 3 commits discards 3638d91da1 96: onsuccess: #2071: 1: Success after gcc/linux: 56 commits discards 4dccfb0f4b 95: onsuccess: #2070: 1: Success after basepoints/gcc-13-238 [...] discards be809e6c30 94: onsuccess: 1: Success after gcc: openmp: Partial OpenMP [...] discards 04b98cde14 93: onsuccess: 1: Success after binutils/gcc/linux/gdb: 88 commits discards 844d57fb1f 92: onsuccess: 1: Success after binutils/gcc/linux/gdb/qemu: [...] discards 5a1cc01b10 91: onsuccess: 1: Success after binutils/gcc/gdb: 8 commits discards 5843253e29 90: onsuccess: 1: Success after binutils/gcc/gdb: 19 commits discards 4ca6bef5e5 89: onsuccess: 1: Success after binutils/gcc/gdb: 5 commits discards ccdf9a4209 88: onsuccess: 1: Success after gcc/linux/qemu: 149 commits discards efe9bf5859 87: onsuccess: 1: Success after binutils/gcc/gdb: 14 commits discards dcf486d920 86: onsuccess: 1: Success after binutils/gcc/gdb: 7 commits discards 46175e8dc7 85: onsuccess: 1: Success after binutils/gcc/glibc/gdb/qemu: [...] discards 62a9966761 84: onsuccess: 1: Success after binutils/gcc/linux/gdb: 68 commits discards 91d9cd5c07 83: onsuccess: 1: Success after binutils/gcc/glibc/gdb: 17 commits discards 9bc184e674 82: onsuccess: 1: Successful build after binutils/gcc/gdb: 1 [...] discards e9a102ecd5 81: onsuccess: 1: Successful build after binutils/gcc/gdb: 6 [...] discards d2be4dd2d8 80: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] discards afa5c5f0bf 79: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] discards 26e1b456d1 78: onsuccess: 1: Successful build after binutils/gcc/gdb: 4 [...] discards 3e8f4d62d6 77: onsuccess: 1: Successful build after gcc/linux/glibc: 22 [...] discards 7073310843 76: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards b2a1ed533d 75: onsuccess: 1: Successful build after linux: 44 commits discards e4981204d7 74: onsuccess: 1: Successful build after binutils/gdb: 2 commits discards 048481ad69 73: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards fe35cf32ea 72: onsuccess: 1: Successful build after linux: 12 commits discards 073664df36 71: onsuccess: 1: Successful build after gcc/glibc: 3 commits discards 18e5b63c96 70: onsuccess: 1: Successful build after binutils/gcc/gdb: 4 [...] discards 0b09980422 69: onsuccess: 1: Successful build after binutils/gcc/gdb: 5 [...] discards 3634dd1762 68: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards dbfa27cb66 67: onsuccess: 1: Successful build after binutils/gcc/gdb: 1 [...] discards 95e61a4363 66: onsuccess: 1: Successful build after gcc/glibc: 10 commits discards b2f384cabd 65: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 08fbe77942 64: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 6a7486e6f9 63: onsuccess: 1: Successful build after binutils/gcc/gdb: 8 [...] discards cc9207c2d8 62: onsuccess: 1: Successful build after binutils/gcc/gdb: 2 [...] new 9ea9275824 62: onsuccess: 1: Successful build after binutils/gcc/gdb: 2 [...] new c4e45c3363 63: onsuccess: 1: Successful build after binutils/gcc/gdb: 8 [...] new 680ef0f8e0 64: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 43a997eaff 65: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 1b78243f6c 66: onsuccess: 1: Successful build after gcc/glibc: 10 commits new cc92477e5f 67: onsuccess: 1: Successful build after binutils/gcc/gdb: 1 [...] new 3f5553b331 68: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new a9af5d13fa 69: onsuccess: 1: Successful build after binutils/gcc/gdb: 5 [...] new 71bd7cc23a 70: onsuccess: 1: Successful build after binutils/gcc/gdb: 4 [...] new f7c4fb4513 71: onsuccess: 1: Successful build after gcc/glibc: 3 commits new 862dd7b854 72: onsuccess: 1: Successful build after linux: 12 commits new 5ce669517a 73: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 1423b610d2 74: onsuccess: 1: Successful build after binutils/gdb: 2 commits new 3686f85362 75: onsuccess: 1: Successful build after linux: 44 commits new 8e6df726c2 76: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 0ecd661ed0 77: onsuccess: 1: Successful build after gcc/linux/glibc: 22 [...] new 59e3ebf603 78: onsuccess: 1: Successful build after binutils/gcc/gdb: 4 [...] new f9ae68073c 79: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] new f4de20e4a1 80: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] new fd76ee9754 81: onsuccess: 1: Successful build after binutils/gcc/gdb: 6 [...] new 023f3d651a 82: onsuccess: 1: Successful build after binutils/gcc/gdb: 1 [...] new 3fe5a125f3 83: onsuccess: 1: Success after binutils/gcc/glibc/gdb: 17 commits new 10d7f17a7e 84: onsuccess: 1: Success after binutils/gcc/linux/gdb: 68 commits new d4a0502061 85: onsuccess: 1: Success after binutils/gcc/glibc/gdb/qemu: [...] new 5d52399e4a 86: onsuccess: 1: Success after binutils/gcc/gdb: 7 commits new 45b9d5ec21 87: onsuccess: 1: Success after binutils/gcc/gdb: 14 commits new 6ba49b0dc9 88: onsuccess: 1: Success after gcc/linux/qemu: 149 commits new 2e8f05ac70 89: onsuccess: 1: Success after binutils/gcc/gdb: 5 commits new ddf04ddd36 90: onsuccess: 1: Success after binutils/gcc/gdb: 19 commits new bd4d99a118 91: onsuccess: 1: Success after binutils/gcc/gdb: 8 commits new 133c7ed7a3 92: onsuccess: 1: Success after binutils/gcc/linux/gdb/qemu: [...] new 1e85082482 93: onsuccess: 1: Success after binutils/gcc/linux/gdb: 88 commits new 8d901f9ad9 94: onsuccess: 1: Success after gcc: openmp: Partial OpenMP [...] new 7fcae6ef64 95: onsuccess: #2070: 1: Success after basepoints/gcc-13-238 [...] new 285f8dafd7 96: onsuccess: #2071: 1: Success after gcc/linux: 56 commits new 343715294a 97: onsuccess: #2072: 1: Success after binutils/gcc/gdb: 3 commits new a74cf65df9 98: onsuccess: #2073: 1: Success after gcc/linux: 11 commits new 49d31e37ce 99: onsuccess: #2074: 1: Success after baseline build: no ne [...] new 939f639a30 100: onsuccess: #2077: 1: Success after binutils/gcc/linux/g [...] new 6a3cacabd5 101: onsuccess: #2130: 1: Success after binutils: 81 commits new 9655c014f8 102: onsuccess: #2133: 1: Success after gdb-12-branchpoint-1 [...] new 32b1cece37 103: onsuccess: #2135: 1: Success after gcc/linux/glibc/gdb/ [...] new 6b955cede0 104: onsuccess: #2136: 1: Success after binutils/gcc/gdb: 3 commits new 540ec2dd7b 105: onsuccess: #2137: 1: Success after basepoints/gcc-13-27 [...] new 4dbc3e9432 106: onsuccess: #2138: 1: Success after binutils/gcc/glibc/g [...] new 74315f9f2f 107: onsuccess: #2139: 1: Success after binutils/gcc/gdb: 3 commits new eb6906a700 108: onsuccess: #2140: 1: Success after binutils/gcc/gdb: 5 commits new b5b3b26de4 109: onsuccess: #2141: 1: Success after gcc/glibc: 6 commits new 496210e9c9 110: onsuccess: #2142: 1: Success after binutils/gcc/glibc/g [...] new f265362656 111: onsuccess: #2143: 1: Success after binutils/gcc/linux/g [...] new 595fd93a1e 112: onsuccess: #2144: 1: Success after binutils/gcc/glibc/g [...] new ff1870ade9 113: onsuccess: #2145: 1: Success after binutils/gcc/glibc/g [...] new 3bc571a524 114: onsuccess: #2146: 1: Success after binutils/gcc/glibc/g [...] new 6ad938029d 115: onsuccess: #2147: 1: Success after binutils/linux/glibc [...] new 9ce230b00b 116: onsuccess: #2148: 1: Success after binutils/gcc/gdb: 7 commits new a2b1b3f533 117: onsuccess: #2150: 1: Success after binutils/gcc/glibc/g [...] new cb4e7f55c8 118: onsuccess: #2151: 1: Success after binutils/gcc/linux/g [...] new c36f2f1ef5 119: onsuccess: #2154: 1: Success after binutils/gcc/linux/g [...] new cbdd4eb228 120: onsuccess: #2155: 1: Success after binutils/gcc/linux/g [...] new 473a98bd03 121: onsuccess: #2156: 1: Success after binutils/gcc/linux/g [...] new bc228b1791 122: onsuccess: #2157: 1: Success after binutils/gcc/gdb: 6 commits new 915eb868c4 123: onsuccess: #2158: 1: Success after basepoints/gcc-13-28 [...] new 69bcb103b5 124: onsuccess: #2159: 1: Success after linux: 23 commits new 3a2b8eda98 125: onsuccess: #2160: 1: Success after binutils/gcc/linux/g [...] new ab8363f96f 126: onsuccess: #2161: 1: Success after basepoints/gcc-13-28 [...] new fb9baddfe3 127: onsuccess: #2162: 1: Success after gcc: 9 commits new 19815f9deb 128: onsuccess: #2163: 1: Success after linux: 23 commits new d20ce12d7b 129: onsuccess: #2164: 1: Success after binutils/gcc/linux/g [...] new ff16f030d5 130: onsuccess: #2165: 1: Success after binutils/gcc/gdb: 32 [...] new 39d2b62bf1 131: onsuccess: #2166: 1: Success after binutils/gcc/gdb: 12 [...] new 736dc4731d 132: onsuccess: #2167: 1: Success after binutils/gcc/glibc/g [...] new af4e564c6f 133: onsuccess: #2168: 1: Success after binutils/gcc/linux/g [...] new 6db38ddd71 134: onsuccess: #2169: 1: Success after binutils/gcc/gdb: 13 [...] new 47515ca50d 135: onsuccess: #2170: 1: Success after gcc/linux/qemu: 63 commits new 81df9e8886 136: onsuccess: #2171: 1: Success after binutils/gcc/gdb/qem [...] new da1408a126 137: onsuccess: #2172: 1: Success after binutils/gcc/linux/g [...] new 85e261d078 138: onsuccess: #2173: 1: Success after binutils/gcc/gdb: 5 commits new a7c13e99d5 139: onsuccess: #2174: 1: Success after binutils/gcc/gdb: 13 [...] new 5b68ebba44 140: onsuccess: #2175: 1: Success after binutils/gcc/linux/g [...] new a042e6407f 141: onsuccess: #2176: 1: Success after binutils/gcc/gdb: 6 commits new ca74f8a334 142: onsuccess: #2177: 1: Success after gcc/glibc: 4 commits new 103b9d674f 143: onsuccess: #2178: 1: Success after binutils/gcc/gdb/qem [...] new b80c09847a 144: onsuccess: #2179: 1: Success after binutils/gcc/linux/g [...] new eb929bf144 145: onsuccess: #2180: 1: Success after binutils/gcc/linux/g [...] new a527e113e2 146: onsuccess: #2181: 1: Success after binutils/glibc/gdb: [...] new ddc2f14692 147: onsuccess: #2182: 1: Success after binutils/gcc/gdb: 18 [...] new 4b061431bb 148: onsuccess: #2183: 1: Success after gcc/linux/glibc: 64 commits new 41f269b4d0 149: onsuccess: #2184: 1: Success after binutils/gcc/linux/g [...] new 7a7a860794 150: onsuccess: #2185: 1: Success after gcc: 3 commits new 200232ce66 151: onsuccess: #2186: 1: Success after gcc: 2 commits new 9919d34fe3 152: onsuccess: #2187: 1: Success after gcc/linux/glibc: 22 commits new ff45a23679 153: onsuccess: #2188: 1: Success after binutils/gcc/gdb: 3 commits new 465d50759d 154: onsuccess: #2189: 1: Success after binutils/gcc/gdb: 18 [...] new e824c4fda7 155: onsuccess: #2190: 1: Success after binutils/gcc/linux/g [...] new 562b609382 156: onsuccess: #2191: 1: Success after binutils/gcc/linux/g [...] new 9263ed146f 157: onsuccess: #2192: 1: Success after binutils/gcc/gdb: 8 commits new cfb52d97eb 158: onsuccess: #2193: 1: Success after binutils/gcc/glibc/g [...] new 27cb513f63 159: onsuccess: #2194: 1: Success after gcc/linux/glibc: 197 [...] new 9cdbdcbb7c 160: onsuccess: #2195: 1: Success after binutils/gcc/linux/g [...] new 8121b54132 161: onsuccess: #2196: 1: Success after binutils/gcc/linux/g [...] new b2e1c21d04 162: onsuccess: #2197: 1: Success after binutils/gcc/glibc/g [...] new df24a7fcb0 163: onsuccess: #2198: 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 (a6c9296282) \ 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 -> 1712 bytes 02-prepare_abe/console.log.xz | Bin 2736 -> 2748 bytes 03-build_abe-binutils/console.log.xz | Bin 30680 -> 30708 bytes 04-build_abe-stage1/console.log.xz | Bin 72208 -> 72784 bytes 06-build_abe-linux/console.log.xz | Bin 9188 -> 8512 bytes 07-build_abe-glibc/console.log.xz | Bin 239956 -> 239908 bytes 08-build_abe-stage2/console.log.xz | Bin 203236 -> 202916 bytes 09-build_abe-gdb/console.log.xz | Bin 37760 -> 37424 bytes 10-build_abe-qemu/console.log.xz | Bin 31908 -> 32048 bytes 11-build_abe-dejagnu/console.log.xz | Bin 3924 -> 3880 bytes 12-build_abe-check_gcc/console.log.xz | Bin 2608 -> 2656 bytes 13-check_regression/console.log.xz | Bin 6140 -> 6204 bytes 13-check_regression/results.compare | 16 +- 13-check_regression/results.compare2 | 31 +- 14-update_baseline/console.log | 36 +- 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 | 2 +- mail/mail-subject.txt | 2 +- manifest.sh | 38 +- sumfiles/g++.log.xz | Bin 3411544 -> 3403752 bytes sumfiles/g++.sum | 44 +- sumfiles/gcc.log.xz | Bin 3031412 -> 3029292 bytes sumfiles/gcc.sum | 4483 +++++++++++++++++---------------- sumfiles/gfortran.log.xz | Bin 1031376 -> 1035288 bytes sumfiles/gfortran.sum | 12 +- sumfiles/libatomic.log.xz | Bin 2292 -> 2296 bytes sumfiles/libatomic.sum | 2 +- sumfiles/libgomp.log.xz | Bin 202248 -> 202344 bytes sumfiles/libgomp.sum | 2 +- sumfiles/libitm.log.xz | Bin 2660 -> 2660 bytes sumfiles/libitm.sum | 2 +- sumfiles/libstdc++.log.xz | Bin 430132 -> 426720 bytes sumfiles/libstdc++.sum | 2 +- 38 files changed, 2349 insertions(+), 2335 deletions(-)