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 b82887e406 174: onsuccess: #2209: 1: Success after binutils/gcc/gdb: 20 [...] discards f5cf5ce2cd 173: onsuccess: #2208: 1: Success after gcc: 10 commits discards 7faf8340ad 172: onsuccess: #2207: 1: Success after binutils/gcc/linux/g [...] discards fa5f7c74d1 171: onsuccess: #2206: 1: Success after binutils/gcc/linux/g [...] discards 5de4fe9da6 170: onsuccess: #2205: 1: Success after binutils/gcc/glibc/g [...] discards 662941d090 169: onsuccess: #2204: 1: Success after binutils/gcc/glibc/g [...] discards 56efac3fd2 168: onsuccess: #2203: 1: Success after binutils/gcc/glibc/g [...] discards 048652fe51 167: onsuccess: #2202: 1: Success after gcc/linux/glibc/qemu [...] discards d48794c956 166: onsuccess: #2201: 1: Success after gcc/glibc/qemu: 40 commits discards 71631952fd 165: onsuccess: #2200: 1: Success after binutils/gdb: 8 commits discards a9f43ced30 164: onsuccess: #2199: 1: Success after binutils/gcc/linux/g [...] discards 7a264ef9b8 163: onsuccess: #2198: 1: Success after binutils/gcc/linux/g [...] discards a35dba06ad 162: onsuccess: #2197: 1: Success after binutils/gcc/glibc/g [...] discards 3031237db2 161: onsuccess: #2196: 1: Success after binutils/gcc/linux/g [...] discards 7e528af537 160: onsuccess: #2195: 1: Success after binutils/gcc/linux/g [...] discards a7441b5949 159: onsuccess: #2194: 1: Success after gcc/linux/glibc: 197 [...] discards ff0fdef838 158: onsuccess: #2193: 1: Success after binutils/gcc/glibc/g [...] discards 9521055c49 157: onsuccess: #2192: 1: Success after binutils/gcc/gdb: 8 commits discards 507111de3b 156: onsuccess: #2191: 1: Success after binutils/gcc/linux/g [...] discards 6d2a20be0b 155: onsuccess: #2190: 1: Success after binutils/gcc/linux/g [...] discards d15571a75d 154: onsuccess: #2189: 1: Success after binutils/gcc/gdb: 18 [...] discards 601f9a476d 153: onsuccess: #2188: 1: Success after binutils/gcc/gdb: 3 commits discards de313c06ed 152: onsuccess: #2187: 1: Success after gcc/linux/glibc: 22 commits discards 57386aae77 151: onsuccess: #2186: 1: Success after gcc: 2 commits discards d9d2530e4e 150: onsuccess: #2185: 1: Success after gcc: 3 commits discards 7b0196ff3d 149: onsuccess: #2184: 1: Success after binutils/gcc/linux/g [...] discards c4aef2bdf0 148: onsuccess: #2183: 1: Success after gcc/linux/glibc: 64 commits discards 79a531f3a5 147: onsuccess: #2182: 1: Success after binutils/gcc/gdb: 18 [...] discards 1f7b9cf084 146: onsuccess: #2181: 1: Success after binutils/glibc/gdb: [...] discards cd02d9439a 145: onsuccess: #2180: 1: Success after binutils/gcc/linux/g [...] discards 5a3ab38d41 144: onsuccess: #2179: 1: Success after binutils/gcc/linux/g [...] discards a026f2fa04 143: onsuccess: #2178: 1: Success after binutils/gcc/gdb/qem [...] discards a54bcf9261 142: onsuccess: #2177: 1: Success after gcc/glibc: 4 commits discards 11aa620ac4 141: onsuccess: #2176: 1: Success after binutils/gcc/gdb: 6 commits discards 7f525f8fcf 140: onsuccess: #2175: 1: Success after binutils/gcc/linux/g [...] discards 93838834c4 139: onsuccess: #2174: 1: Success after binutils/gcc/gdb: 13 [...] discards 3acd6dd0b0 138: onsuccess: #2173: 1: Success after binutils/gcc/gdb: 5 commits discards d7632e7e42 137: onsuccess: #2172: 1: Success after binutils/gcc/linux/g [...] discards 6cf236d49b 136: onsuccess: #2171: 1: Success after binutils/gcc/gdb/qem [...] discards 1151c9949e 135: onsuccess: #2170: 1: Success after gcc/linux/qemu: 63 commits discards 41c37beba5 134: onsuccess: #2169: 1: Success after binutils/gcc/gdb: 13 [...] discards ee151a7678 133: onsuccess: #2168: 1: Success after binutils/gcc/linux/g [...] discards ed3e3a9ebc 132: onsuccess: #2167: 1: Success after binutils/gcc/glibc/g [...] discards c5001d5fe1 131: onsuccess: #2166: 1: Success after binutils/gcc/gdb: 12 [...] discards 24ff573328 130: onsuccess: #2165: 1: Success after binutils/gcc/gdb: 32 [...] discards 2df62cb282 129: onsuccess: #2164: 1: Success after binutils/gcc/linux/g [...] discards af80c0b7de 128: onsuccess: #2163: 1: Success after linux: 23 commits discards f20d52c6a6 127: onsuccess: #2162: 1: Success after gcc: 9 commits discards 13cee88add 126: onsuccess: #2161: 1: Success after basepoints/gcc-13-28 [...] discards f4d20f098e 125: onsuccess: #2160: 1: Success after binutils/gcc/linux/g [...] discards 946f99e4dc 124: onsuccess: #2159: 1: Success after linux: 23 commits discards cdbb20032c 123: onsuccess: #2158: 1: Success after basepoints/gcc-13-28 [...] discards 541f94c51d 122: onsuccess: #2157: 1: Success after binutils/gcc/gdb: 6 commits discards c4128122aa 121: onsuccess: #2156: 1: Success after binutils/gcc/linux/g [...] discards d81f0cc4f5 120: onsuccess: #2155: 1: Success after binutils/gcc/linux/g [...] discards f9530b9fd9 119: onsuccess: #2154: 1: Success after binutils/gcc/linux/g [...] discards 16d342ea6c 118: onsuccess: #2151: 1: Success after binutils/gcc/linux/g [...] discards ca6135b3e2 117: onsuccess: #2150: 1: Success after binutils/gcc/glibc/g [...] discards 6228f838ea 116: onsuccess: #2148: 1: Success after binutils/gcc/gdb: 7 commits discards 2ffbd2ec17 115: onsuccess: #2147: 1: Success after binutils/linux/glibc [...] discards e2df7c7eea 114: onsuccess: #2146: 1: Success after binutils/gcc/glibc/g [...] discards dccf2640c8 113: onsuccess: #2145: 1: Success after binutils/gcc/glibc/g [...] discards 71e523689d 112: onsuccess: #2144: 1: Success after binutils/gcc/glibc/g [...] discards b67d409503 111: onsuccess: #2143: 1: Success after binutils/gcc/linux/g [...] discards a8abb96ff5 110: onsuccess: #2142: 1: Success after binutils/gcc/glibc/g [...] discards 96a5743070 109: onsuccess: #2141: 1: Success after gcc/glibc: 6 commits discards 28f3f5474a 108: onsuccess: #2140: 1: Success after binutils/gcc/gdb: 5 commits discards ff4d5e6367 107: onsuccess: #2139: 1: Success after binutils/gcc/gdb: 3 commits discards 8d3dc2016f 106: onsuccess: #2138: 1: Success after binutils/gcc/glibc/g [...] discards e5496291fb 105: onsuccess: #2137: 1: Success after basepoints/gcc-13-27 [...] discards 9da27b1cbe 104: onsuccess: #2136: 1: Success after binutils/gcc/gdb: 3 commits discards a06fa0640d 103: onsuccess: #2135: 1: Success after gcc/linux/glibc/gdb/ [...] discards f69ada673a 102: onsuccess: #2133: 1: Success after gdb-12-branchpoint-1 [...] discards e515e22028 101: onsuccess: #2130: 1: Success after binutils: 81 commits discards 3c85b54658 100: onsuccess: #2077: 1: Success after binutils/gcc/linux/g [...] discards 2c5253ed28 99: onsuccess: #2074: 1: Success after baseline build: no ne [...] discards a7fc358a11 98: onsuccess: #2073: 1: Success after gcc/linux: 11 commits discards e589ea9925 97: onsuccess: #2072: 1: Success after binutils/gcc/gdb: 3 commits discards 71340d7dc3 96: onsuccess: #2071: 1: Success after gcc/linux: 56 commits discards 59654fdb5d 95: onsuccess: #2070: 1: Success after basepoints/gcc-13-238 [...] discards 8b00491bfb 94: onsuccess: 1: Success after gcc: openmp: Partial OpenMP [...] discards 8e6d0c3dd9 93: onsuccess: 1: Success after binutils/gcc/linux/gdb: 88 commits discards 937b8930a9 92: onsuccess: 1: Success after binutils/gcc/linux/gdb/qemu: [...] discards f996522458 91: onsuccess: 1: Success after binutils/gcc/gdb: 8 commits discards 816061eaef 90: onsuccess: 1: Success after binutils/gcc/gdb: 19 commits discards 3624f4297c 89: onsuccess: 1: Success after binutils/gcc/gdb: 5 commits discards e299543fd6 88: onsuccess: 1: Success after gcc/linux/qemu: 149 commits discards e182c9fbcb 87: onsuccess: 1: Success after binutils/gcc/gdb: 14 commits discards c16e3b6c93 86: onsuccess: 1: Success after binutils/gcc/gdb: 7 commits discards 7bb4f58a9c 85: onsuccess: 1: Success after binutils/gcc/glibc/gdb/qemu: [...] discards 2e22d52564 84: onsuccess: 1: Success after binutils/gcc/linux/gdb: 68 commits discards 0efbd1d39f 83: onsuccess: 1: Success after binutils/gcc/glibc/gdb: 17 commits discards 5a4f32ca80 82: onsuccess: 1: Successful build after binutils/gcc/gdb: 1 [...] discards ad6ca45892 81: onsuccess: 1: Successful build after binutils/gcc/gdb: 6 [...] discards 0d63cc2558 80: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] discards 4cc2f9f668 79: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] discards 19391b784b 78: onsuccess: 1: Successful build after binutils/gcc/gdb: 4 [...] discards 86b03495c8 77: onsuccess: 1: Successful build after gcc/linux/glibc: 22 [...] discards ea4bb8a8f3 76: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 674fdda3db 75: onsuccess: 1: Successful build after linux: 44 commits discards d3e24839cc 74: onsuccess: 1: Successful build after binutils/gdb: 2 commits new 8a34204bc5 74: onsuccess: 1: Successful build after binutils/gdb: 2 commits new b7817d2281 75: onsuccess: 1: Successful build after linux: 44 commits new 14ebae6124 76: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new e7aad8cde0 77: onsuccess: 1: Successful build after gcc/linux/glibc: 22 [...] new 0f86a44d7e 78: onsuccess: 1: Successful build after binutils/gcc/gdb: 4 [...] new c54713a387 79: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] new 82b3ef6b0c 80: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] new 1974b37c48 81: onsuccess: 1: Successful build after binutils/gcc/gdb: 6 [...] new b9d234f5d2 82: onsuccess: 1: Successful build after binutils/gcc/gdb: 1 [...] new 9cbea1feac 83: onsuccess: 1: Success after binutils/gcc/glibc/gdb: 17 commits new cac180946a 84: onsuccess: 1: Success after binutils/gcc/linux/gdb: 68 commits new 440f5d6a9d 85: onsuccess: 1: Success after binutils/gcc/glibc/gdb/qemu: [...] new f993a7ea13 86: onsuccess: 1: Success after binutils/gcc/gdb: 7 commits new 54b90716f6 87: onsuccess: 1: Success after binutils/gcc/gdb: 14 commits new afdbfed702 88: onsuccess: 1: Success after gcc/linux/qemu: 149 commits new 66f889d8d6 89: onsuccess: 1: Success after binutils/gcc/gdb: 5 commits new 1963748462 90: onsuccess: 1: Success after binutils/gcc/gdb: 19 commits new 296a083542 91: onsuccess: 1: Success after binutils/gcc/gdb: 8 commits new 729e8972cf 92: onsuccess: 1: Success after binutils/gcc/linux/gdb/qemu: [...] new c96db3ac93 93: onsuccess: 1: Success after binutils/gcc/linux/gdb: 88 commits new 82502ce77f 94: onsuccess: 1: Success after gcc: openmp: Partial OpenMP [...] new 66e2f26cfa 95: onsuccess: #2070: 1: Success after basepoints/gcc-13-238 [...] new 8af1d2a75d 96: onsuccess: #2071: 1: Success after gcc/linux: 56 commits new f7d521dad0 97: onsuccess: #2072: 1: Success after binutils/gcc/gdb: 3 commits new 1cd7c94584 98: onsuccess: #2073: 1: Success after gcc/linux: 11 commits new 70b4ce501e 99: onsuccess: #2074: 1: Success after baseline build: no ne [...] new 797160124d 100: onsuccess: #2077: 1: Success after binutils/gcc/linux/g [...] new af2e9c8189 101: onsuccess: #2130: 1: Success after binutils: 81 commits new 571cbe89a6 102: onsuccess: #2133: 1: Success after gdb-12-branchpoint-1 [...] new 461ec7ec4d 103: onsuccess: #2135: 1: Success after gcc/linux/glibc/gdb/ [...] new 68adcff119 104: onsuccess: #2136: 1: Success after binutils/gcc/gdb: 3 commits new b22ee34f35 105: onsuccess: #2137: 1: Success after basepoints/gcc-13-27 [...] new 3f84fe5581 106: onsuccess: #2138: 1: Success after binutils/gcc/glibc/g [...] new 49c59bb051 107: onsuccess: #2139: 1: Success after binutils/gcc/gdb: 3 commits new 1812a33fcf 108: onsuccess: #2140: 1: Success after binutils/gcc/gdb: 5 commits new ff8a993810 109: onsuccess: #2141: 1: Success after gcc/glibc: 6 commits new bb67332941 110: onsuccess: #2142: 1: Success after binutils/gcc/glibc/g [...] new 372db16cdc 111: onsuccess: #2143: 1: Success after binutils/gcc/linux/g [...] new 45ae2bcfe3 112: onsuccess: #2144: 1: Success after binutils/gcc/glibc/g [...] new 47faa46263 113: onsuccess: #2145: 1: Success after binutils/gcc/glibc/g [...] new 0e2c3a9afb 114: onsuccess: #2146: 1: Success after binutils/gcc/glibc/g [...] new 27be44135c 115: onsuccess: #2147: 1: Success after binutils/linux/glibc [...] new aaeff03dc0 116: onsuccess: #2148: 1: Success after binutils/gcc/gdb: 7 commits new 021c0ade0d 117: onsuccess: #2150: 1: Success after binutils/gcc/glibc/g [...] new 20d9fcad59 118: onsuccess: #2151: 1: Success after binutils/gcc/linux/g [...] new ff4334a77e 119: onsuccess: #2154: 1: Success after binutils/gcc/linux/g [...] new aa71205943 120: onsuccess: #2155: 1: Success after binutils/gcc/linux/g [...] new 5d9cd90925 121: onsuccess: #2156: 1: Success after binutils/gcc/linux/g [...] new 8cd676c6b2 122: onsuccess: #2157: 1: Success after binutils/gcc/gdb: 6 commits new 99a5d856cf 123: onsuccess: #2158: 1: Success after basepoints/gcc-13-28 [...] new f5a80ed131 124: onsuccess: #2159: 1: Success after linux: 23 commits new d7ce916451 125: onsuccess: #2160: 1: Success after binutils/gcc/linux/g [...] new 9518cfd335 126: onsuccess: #2161: 1: Success after basepoints/gcc-13-28 [...] new 3ade4b4389 127: onsuccess: #2162: 1: Success after gcc: 9 commits new 1ab7f09e7f 128: onsuccess: #2163: 1: Success after linux: 23 commits new d6d19326dc 129: onsuccess: #2164: 1: Success after binutils/gcc/linux/g [...] new 7054f484cc 130: onsuccess: #2165: 1: Success after binutils/gcc/gdb: 32 [...] new 1425c473e6 131: onsuccess: #2166: 1: Success after binutils/gcc/gdb: 12 [...] new 4930e4b9ca 132: onsuccess: #2167: 1: Success after binutils/gcc/glibc/g [...] new 169ab687ac 133: onsuccess: #2168: 1: Success after binutils/gcc/linux/g [...] new fdc4b6915b 134: onsuccess: #2169: 1: Success after binutils/gcc/gdb: 13 [...] new a2359ac45d 135: onsuccess: #2170: 1: Success after gcc/linux/qemu: 63 commits new 6711fb1ab8 136: onsuccess: #2171: 1: Success after binutils/gcc/gdb/qem [...] new d52a26adde 137: onsuccess: #2172: 1: Success after binutils/gcc/linux/g [...] new 90a6ee30c2 138: onsuccess: #2173: 1: Success after binutils/gcc/gdb: 5 commits new c80fb0f69a 139: onsuccess: #2174: 1: Success after binutils/gcc/gdb: 13 [...] new 33bdc20b85 140: onsuccess: #2175: 1: Success after binutils/gcc/linux/g [...] new 7bdebcd9b7 141: onsuccess: #2176: 1: Success after binutils/gcc/gdb: 6 commits new ada1d33818 142: onsuccess: #2177: 1: Success after gcc/glibc: 4 commits new f4e9e36a0f 143: onsuccess: #2178: 1: Success after binutils/gcc/gdb/qem [...] new e1a35b1e96 144: onsuccess: #2179: 1: Success after binutils/gcc/linux/g [...] new 49178c341c 145: onsuccess: #2180: 1: Success after binutils/gcc/linux/g [...] new 33f2b9d88e 146: onsuccess: #2181: 1: Success after binutils/glibc/gdb: [...] new 733a78e715 147: onsuccess: #2182: 1: Success after binutils/gcc/gdb: 18 [...] new 2cd85c60f8 148: onsuccess: #2183: 1: Success after gcc/linux/glibc: 64 commits new acb5b8ae99 149: onsuccess: #2184: 1: Success after binutils/gcc/linux/g [...] new e48dc0c737 150: onsuccess: #2185: 1: Success after gcc: 3 commits new 9b3e63538b 151: onsuccess: #2186: 1: Success after gcc: 2 commits new 4b82292c5d 152: onsuccess: #2187: 1: Success after gcc/linux/glibc: 22 commits new fb6143b13e 153: onsuccess: #2188: 1: Success after binutils/gcc/gdb: 3 commits new a799cebbe9 154: onsuccess: #2189: 1: Success after binutils/gcc/gdb: 18 [...] new 155889dd55 155: onsuccess: #2190: 1: Success after binutils/gcc/linux/g [...] new 60107ff445 156: onsuccess: #2191: 1: Success after binutils/gcc/linux/g [...] new 481221605b 157: onsuccess: #2192: 1: Success after binutils/gcc/gdb: 8 commits new 68b1a9798a 158: onsuccess: #2193: 1: Success after binutils/gcc/glibc/g [...] new c4e3da3956 159: onsuccess: #2194: 1: Success after gcc/linux/glibc: 197 [...] new d5d55f946c 160: onsuccess: #2195: 1: Success after binutils/gcc/linux/g [...] new 7f242e2c11 161: onsuccess: #2196: 1: Success after binutils/gcc/linux/g [...] new f935ccc50a 162: onsuccess: #2197: 1: Success after binutils/gcc/glibc/g [...] new 28a5bdc30d 163: onsuccess: #2198: 1: Success after binutils/gcc/linux/g [...] new ad5b516905 164: onsuccess: #2199: 1: Success after binutils/gcc/linux/g [...] new 220bbfa96f 165: onsuccess: #2200: 1: Success after binutils/gdb: 8 commits new dc67714697 166: onsuccess: #2201: 1: Success after gcc/glibc/qemu: 40 commits new fa7606c082 167: onsuccess: #2202: 1: Success after gcc/linux/glibc/qemu [...] new 6eac475fe6 168: onsuccess: #2203: 1: Success after binutils/gcc/glibc/g [...] new 70e268c690 169: onsuccess: #2204: 1: Success after binutils/gcc/glibc/g [...] new 05d64ea5bf 170: onsuccess: #2205: 1: Success after binutils/gcc/glibc/g [...] new c506410fa9 171: onsuccess: #2206: 1: Success after binutils/gcc/linux/g [...] new 2104342eb8 172: onsuccess: #2207: 1: Success after binutils/gcc/linux/g [...] new 2591ac7a9b 173: onsuccess: #2208: 1: Success after gcc: 10 commits new 4d8774fa85 174: onsuccess: #2209: 1: Success after binutils/gcc/gdb: 20 [...] new 1f7afb67f3 175: onsuccess: #2210: 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 (b82887e406) \ 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 1736 -> 1712 bytes 02-prepare_abe/console.log.xz | Bin 2744 -> 2744 bytes 03-build_abe-binutils/console.log.xz | Bin 30460 -> 31320 bytes 04-build_abe-stage1/console.log.xz | Bin 72628 -> 73284 bytes 05-clean_sysroot/console.log.xz | Bin 328 -> 328 bytes 06-build_abe-linux/console.log.xz | Bin 8568 -> 9048 bytes 07-build_abe-glibc/console.log.xz | Bin 240232 -> 240704 bytes 08-build_abe-stage2/console.log.xz | Bin 203380 -> 205472 bytes 09-build_abe-gdb/console.log.xz | Bin 37660 -> 38200 bytes 10-build_abe-qemu/console.log.xz | Bin 31696 -> 32048 bytes 11-build_abe-dejagnu/console.log.xz | Bin 3880 -> 3908 bytes 12-build_abe-check_gcc/console.log.xz | Bin 2752 -> 2940 bytes 13-check_regression/console.log.xz | Bin 9036 -> 7000 bytes 13-check_regression/extra-bisect-params | 2 +- 13-check_regression/fails.sum | 10 +- 13-check_regression/mail-body.txt | 159 +- 13-check_regression/results.compare | 125 +- 13-check_regression/results.compare2 | 585 +--- 13-check_regression/results.regressions | 97 +- 14-update_baseline/console.log | 64 +- dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- git/gdb_rev | 2 +- git/glibc_rev | 2 +- git/linux_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 161 +- mail/mail-subject.txt | 2 +- manifest.sh | 42 +- results | 97 +- sumfiles/g++.log.xz | Bin 3416616 -> 3424824 bytes sumfiles/g++.sum | 244 +- sumfiles/gcc.log.xz | Bin 3031072 -> 3034024 bytes sumfiles/gcc.sum | 5594 ++++++++++++++++--------------- sumfiles/gfortran.log.xz | Bin 1026220 -> 1037348 bytes sumfiles/gfortran.sum | 42 +- sumfiles/libatomic.log.xz | Bin 2292 -> 2296 bytes sumfiles/libatomic.sum | 4 +- sumfiles/libgomp.log.xz | Bin 202684 -> 202248 bytes sumfiles/libgomp.sum | 16 +- sumfiles/libitm.log.xz | Bin 2692 -> 2692 bytes sumfiles/libitm.sum | 6 +- sumfiles/libstdc++.log.xz | Bin 420764 -> 427756 bytes sumfiles/libstdc++.sum | 18 +- 45 files changed, 3243 insertions(+), 4039 deletions(-)