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 cc24250702 173: onsuccess: #2208: 1: Success after gcc: 10 commits discards 91b9b5d755 172: onsuccess: #2207: 1: Success after binutils/gcc/linux/g [...] discards 6101f71f11 171: onsuccess: #2206: 1: Success after binutils/gcc/linux/g [...] discards f567a86abc 170: onsuccess: #2205: 1: Success after binutils/gcc/glibc/g [...] discards e0ba0b8d36 169: onsuccess: #2204: 1: Success after binutils/gcc/glibc/g [...] discards 587352b11e 168: onsuccess: #2203: 1: Success after binutils/gcc/glibc/g [...] discards 5adaddb04b 167: onsuccess: #2202: 1: Success after gcc/linux/glibc/qemu [...] discards e6a044dcae 166: onsuccess: #2201: 1: Success after gcc/glibc/qemu: 40 commits discards 421a73cec5 165: onsuccess: #2200: 1: Success after binutils/gdb: 8 commits discards 96ec80b707 164: onsuccess: #2199: 1: Success after binutils/gcc/linux/g [...] discards a0175ec57c 163: onsuccess: #2198: 1: Success after binutils/gcc/linux/g [...] discards 9a34728241 162: onsuccess: #2197: 1: Success after binutils/gcc/glibc/g [...] discards 11cff3ec6a 161: onsuccess: #2196: 1: Success after binutils/gcc/linux/g [...] discards f59e8abb6e 160: onsuccess: #2195: 1: Success after binutils/gcc/linux/g [...] discards 1242600672 159: onsuccess: #2194: 1: Success after gcc/linux/glibc: 197 [...] discards b80640d74d 158: onsuccess: #2193: 1: Success after binutils/gcc/glibc/g [...] discards 34ae868845 157: onsuccess: #2192: 1: Success after binutils/gcc/gdb: 8 commits discards 47d141f31f 156: onsuccess: #2191: 1: Success after binutils/gcc/linux/g [...] discards d06332cc14 155: onsuccess: #2190: 1: Success after binutils/gcc/linux/g [...] discards e68b3f5e00 154: onsuccess: #2189: 1: Success after binutils/gcc/gdb: 18 [...] discards 529243955d 153: onsuccess: #2188: 1: Success after binutils/gcc/gdb: 3 commits discards f3c485e08a 152: onsuccess: #2187: 1: Success after gcc/linux/glibc: 22 commits discards a74b02ece5 151: onsuccess: #2186: 1: Success after gcc: 2 commits discards a32d78c5c2 150: onsuccess: #2185: 1: Success after gcc: 3 commits discards 02a5e1089a 149: onsuccess: #2184: 1: Success after binutils/gcc/linux/g [...] discards 8f72b79cdc 148: onsuccess: #2183: 1: Success after gcc/linux/glibc: 64 commits discards 62b551268c 147: onsuccess: #2182: 1: Success after binutils/gcc/gdb: 18 [...] discards d3cf3e1656 146: onsuccess: #2181: 1: Success after binutils/glibc/gdb: [...] discards 7f15d026d0 145: onsuccess: #2180: 1: Success after binutils/gcc/linux/g [...] discards 244ff35392 144: onsuccess: #2179: 1: Success after binutils/gcc/linux/g [...] discards 5787e649da 143: onsuccess: #2178: 1: Success after binutils/gcc/gdb/qem [...] discards f879a83e33 142: onsuccess: #2177: 1: Success after gcc/glibc: 4 commits discards 8e1ae83e10 141: onsuccess: #2176: 1: Success after binutils/gcc/gdb: 6 commits discards ccf5ac62f5 140: onsuccess: #2175: 1: Success after binutils/gcc/linux/g [...] discards 69dc2b1058 139: onsuccess: #2174: 1: Success after binutils/gcc/gdb: 13 [...] discards ff08ff1b33 138: onsuccess: #2173: 1: Success after binutils/gcc/gdb: 5 commits discards 3af7b0d4cb 137: onsuccess: #2172: 1: Success after binutils/gcc/linux/g [...] discards 42d1c26025 136: onsuccess: #2171: 1: Success after binutils/gcc/gdb/qem [...] discards fa28546006 135: onsuccess: #2170: 1: Success after gcc/linux/qemu: 63 commits discards caf164a142 134: onsuccess: #2169: 1: Success after binutils/gcc/gdb: 13 [...] discards d7479bb62d 133: onsuccess: #2168: 1: Success after binutils/gcc/linux/g [...] discards 524388caad 132: onsuccess: #2167: 1: Success after binutils/gcc/glibc/g [...] discards d6142ec651 131: onsuccess: #2166: 1: Success after binutils/gcc/gdb: 12 [...] discards 4bf9f76a3c 130: onsuccess: #2165: 1: Success after binutils/gcc/gdb: 32 [...] discards d41d5f758d 129: onsuccess: #2164: 1: Success after binutils/gcc/linux/g [...] discards e0383d4e87 128: onsuccess: #2163: 1: Success after linux: 23 commits discards b99f1f0707 127: onsuccess: #2162: 1: Success after gcc: 9 commits discards 9a55638a84 126: onsuccess: #2161: 1: Success after basepoints/gcc-13-28 [...] discards 1a99f7a490 125: onsuccess: #2160: 1: Success after binutils/gcc/linux/g [...] discards e4836737bc 124: onsuccess: #2159: 1: Success after linux: 23 commits discards 4cebc00e1b 123: onsuccess: #2158: 1: Success after basepoints/gcc-13-28 [...] discards 29e316ef66 122: onsuccess: #2157: 1: Success after binutils/gcc/gdb: 6 commits discards 3f9fceac23 121: onsuccess: #2156: 1: Success after binutils/gcc/linux/g [...] discards cfc00d30ea 120: onsuccess: #2155: 1: Success after binutils/gcc/linux/g [...] discards 192ef765b9 119: onsuccess: #2154: 1: Success after binutils/gcc/linux/g [...] discards 123927428a 118: onsuccess: #2151: 1: Success after binutils/gcc/linux/g [...] discards de7bdbd2fa 117: onsuccess: #2150: 1: Success after binutils/gcc/glibc/g [...] discards e1f1cb4b77 116: onsuccess: #2148: 1: Success after binutils/gcc/gdb: 7 commits discards ce31e7f1a1 115: onsuccess: #2147: 1: Success after binutils/linux/glibc [...] discards 7516e02375 114: onsuccess: #2146: 1: Success after binutils/gcc/glibc/g [...] discards bde8b46aec 113: onsuccess: #2145: 1: Success after binutils/gcc/glibc/g [...] discards c3b7af0d56 112: onsuccess: #2144: 1: Success after binutils/gcc/glibc/g [...] discards ba62061c45 111: onsuccess: #2143: 1: Success after binutils/gcc/linux/g [...] discards a4d92b094d 110: onsuccess: #2142: 1: Success after binutils/gcc/glibc/g [...] discards 1515391aee 109: onsuccess: #2141: 1: Success after gcc/glibc: 6 commits discards 6256c99e07 108: onsuccess: #2140: 1: Success after binutils/gcc/gdb: 5 commits discards a08c416795 107: onsuccess: #2139: 1: Success after binutils/gcc/gdb: 3 commits discards c2980c5e49 106: onsuccess: #2138: 1: Success after binutils/gcc/glibc/g [...] discards 70cd4ec787 105: onsuccess: #2137: 1: Success after basepoints/gcc-13-27 [...] discards 7b396e8e46 104: onsuccess: #2136: 1: Success after binutils/gcc/gdb: 3 commits discards 1346b87b72 103: onsuccess: #2135: 1: Success after gcc/linux/glibc/gdb/ [...] discards 98a7303248 102: onsuccess: #2133: 1: Success after gdb-12-branchpoint-1 [...] discards c45143afa6 101: onsuccess: #2130: 1: Success after binutils: 81 commits discards 8eef5232dd 100: onsuccess: #2077: 1: Success after binutils/gcc/linux/g [...] discards 4f0a27063a 99: onsuccess: #2074: 1: Success after baseline build: no ne [...] discards a2730484f2 98: onsuccess: #2073: 1: Success after gcc/linux: 11 commits discards de9a00061a 97: onsuccess: #2072: 1: Success after binutils/gcc/gdb: 3 commits discards 5bee44af9c 96: onsuccess: #2071: 1: Success after gcc/linux: 56 commits discards 617c6065db 95: onsuccess: #2070: 1: Success after basepoints/gcc-13-238 [...] discards 63c2749af8 94: onsuccess: 1: Success after gcc: openmp: Partial OpenMP [...] discards c8c20ace81 93: onsuccess: 1: Success after binutils/gcc/linux/gdb: 88 commits discards 35c1e1a8bd 92: onsuccess: 1: Success after binutils/gcc/linux/gdb/qemu: [...] discards 92d525fcc6 91: onsuccess: 1: Success after binutils/gcc/gdb: 8 commits discards 5bf82d213b 90: onsuccess: 1: Success after binutils/gcc/gdb: 19 commits discards 4210319c66 89: onsuccess: 1: Success after binutils/gcc/gdb: 5 commits discards a4bbe2e067 88: onsuccess: 1: Success after gcc/linux/qemu: 149 commits discards 5560cb9040 87: onsuccess: 1: Success after binutils/gcc/gdb: 14 commits discards a886ae7253 86: onsuccess: 1: Success after binutils/gcc/gdb: 7 commits discards 313ddc93a2 85: onsuccess: 1: Success after binutils/gcc/glibc/gdb/qemu: [...] discards a3d1490844 84: onsuccess: 1: Success after binutils/gcc/linux/gdb: 68 commits discards d8ddc0d807 83: onsuccess: 1: Success after binutils/gcc/glibc/gdb: 17 commits discards 65ccf2849f 82: onsuccess: 1: Successful build after binutils/gcc/gdb: 1 [...] discards 83c8caad2b 81: onsuccess: 1: Successful build after binutils/gcc/gdb: 6 [...] discards f4514d3ba3 80: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] discards b9f55dad9b 79: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] discards 44ab18af47 78: onsuccess: 1: Successful build after binutils/gcc/gdb: 4 [...] discards 914264eb72 77: onsuccess: 1: Successful build after gcc/linux/glibc: 22 [...] discards 15cf081b7a 76: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 7e747326cd 75: onsuccess: 1: Successful build after linux: 44 commits discards 04e39af6e4 74: onsuccess: 1: Successful build after binutils/gdb: 2 commits discards 30ca9227b0 73: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 6bc1ecc76b 73: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new d3e24839cc 74: onsuccess: 1: Successful build after binutils/gdb: 2 commits new 674fdda3db 75: onsuccess: 1: Successful build after linux: 44 commits new ea4bb8a8f3 76: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 86b03495c8 77: onsuccess: 1: Successful build after gcc/linux/glibc: 22 [...] new 19391b784b 78: onsuccess: 1: Successful build after binutils/gcc/gdb: 4 [...] new 4cc2f9f668 79: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] new 0d63cc2558 80: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] new ad6ca45892 81: onsuccess: 1: Successful build after binutils/gcc/gdb: 6 [...] new 5a4f32ca80 82: onsuccess: 1: Successful build after binutils/gcc/gdb: 1 [...] new 0efbd1d39f 83: onsuccess: 1: Success after binutils/gcc/glibc/gdb: 17 commits new 2e22d52564 84: onsuccess: 1: Success after binutils/gcc/linux/gdb: 68 commits new 7bb4f58a9c 85: onsuccess: 1: Success after binutils/gcc/glibc/gdb/qemu: [...] new c16e3b6c93 86: onsuccess: 1: Success after binutils/gcc/gdb: 7 commits new e182c9fbcb 87: onsuccess: 1: Success after binutils/gcc/gdb: 14 commits new e299543fd6 88: onsuccess: 1: Success after gcc/linux/qemu: 149 commits new 3624f4297c 89: onsuccess: 1: Success after binutils/gcc/gdb: 5 commits new 816061eaef 90: onsuccess: 1: Success after binutils/gcc/gdb: 19 commits new f996522458 91: onsuccess: 1: Success after binutils/gcc/gdb: 8 commits new 937b8930a9 92: onsuccess: 1: Success after binutils/gcc/linux/gdb/qemu: [...] new 8e6d0c3dd9 93: onsuccess: 1: Success after binutils/gcc/linux/gdb: 88 commits new 8b00491bfb 94: onsuccess: 1: Success after gcc: openmp: Partial OpenMP [...] new 59654fdb5d 95: onsuccess: #2070: 1: Success after basepoints/gcc-13-238 [...] new 71340d7dc3 96: onsuccess: #2071: 1: Success after gcc/linux: 56 commits new e589ea9925 97: onsuccess: #2072: 1: Success after binutils/gcc/gdb: 3 commits new a7fc358a11 98: onsuccess: #2073: 1: Success after gcc/linux: 11 commits new 2c5253ed28 99: onsuccess: #2074: 1: Success after baseline build: no ne [...] new 3c85b54658 100: onsuccess: #2077: 1: Success after binutils/gcc/linux/g [...] new e515e22028 101: onsuccess: #2130: 1: Success after binutils: 81 commits new f69ada673a 102: onsuccess: #2133: 1: Success after gdb-12-branchpoint-1 [...] new a06fa0640d 103: onsuccess: #2135: 1: Success after gcc/linux/glibc/gdb/ [...] new 9da27b1cbe 104: onsuccess: #2136: 1: Success after binutils/gcc/gdb: 3 commits new e5496291fb 105: onsuccess: #2137: 1: Success after basepoints/gcc-13-27 [...] new 8d3dc2016f 106: onsuccess: #2138: 1: Success after binutils/gcc/glibc/g [...] new ff4d5e6367 107: onsuccess: #2139: 1: Success after binutils/gcc/gdb: 3 commits new 28f3f5474a 108: onsuccess: #2140: 1: Success after binutils/gcc/gdb: 5 commits new 96a5743070 109: onsuccess: #2141: 1: Success after gcc/glibc: 6 commits new a8abb96ff5 110: onsuccess: #2142: 1: Success after binutils/gcc/glibc/g [...] new b67d409503 111: onsuccess: #2143: 1: Success after binutils/gcc/linux/g [...] new 71e523689d 112: onsuccess: #2144: 1: Success after binutils/gcc/glibc/g [...] new dccf2640c8 113: onsuccess: #2145: 1: Success after binutils/gcc/glibc/g [...] new e2df7c7eea 114: onsuccess: #2146: 1: Success after binutils/gcc/glibc/g [...] new 2ffbd2ec17 115: onsuccess: #2147: 1: Success after binutils/linux/glibc [...] new 6228f838ea 116: onsuccess: #2148: 1: Success after binutils/gcc/gdb: 7 commits new ca6135b3e2 117: onsuccess: #2150: 1: Success after binutils/gcc/glibc/g [...] new 16d342ea6c 118: onsuccess: #2151: 1: Success after binutils/gcc/linux/g [...] new f9530b9fd9 119: onsuccess: #2154: 1: Success after binutils/gcc/linux/g [...] new d81f0cc4f5 120: onsuccess: #2155: 1: Success after binutils/gcc/linux/g [...] new c4128122aa 121: onsuccess: #2156: 1: Success after binutils/gcc/linux/g [...] new 541f94c51d 122: onsuccess: #2157: 1: Success after binutils/gcc/gdb: 6 commits new cdbb20032c 123: onsuccess: #2158: 1: Success after basepoints/gcc-13-28 [...] new 946f99e4dc 124: onsuccess: #2159: 1: Success after linux: 23 commits new f4d20f098e 125: onsuccess: #2160: 1: Success after binutils/gcc/linux/g [...] new 13cee88add 126: onsuccess: #2161: 1: Success after basepoints/gcc-13-28 [...] new f20d52c6a6 127: onsuccess: #2162: 1: Success after gcc: 9 commits new af80c0b7de 128: onsuccess: #2163: 1: Success after linux: 23 commits new 2df62cb282 129: onsuccess: #2164: 1: Success after binutils/gcc/linux/g [...] new 24ff573328 130: onsuccess: #2165: 1: Success after binutils/gcc/gdb: 32 [...] new c5001d5fe1 131: onsuccess: #2166: 1: Success after binutils/gcc/gdb: 12 [...] new ed3e3a9ebc 132: onsuccess: #2167: 1: Success after binutils/gcc/glibc/g [...] new ee151a7678 133: onsuccess: #2168: 1: Success after binutils/gcc/linux/g [...] new 41c37beba5 134: onsuccess: #2169: 1: Success after binutils/gcc/gdb: 13 [...] new 1151c9949e 135: onsuccess: #2170: 1: Success after gcc/linux/qemu: 63 commits new 6cf236d49b 136: onsuccess: #2171: 1: Success after binutils/gcc/gdb/qem [...] new d7632e7e42 137: onsuccess: #2172: 1: Success after binutils/gcc/linux/g [...] new 3acd6dd0b0 138: onsuccess: #2173: 1: Success after binutils/gcc/gdb: 5 commits new 93838834c4 139: onsuccess: #2174: 1: Success after binutils/gcc/gdb: 13 [...] new 7f525f8fcf 140: onsuccess: #2175: 1: Success after binutils/gcc/linux/g [...] new 11aa620ac4 141: onsuccess: #2176: 1: Success after binutils/gcc/gdb: 6 commits new a54bcf9261 142: onsuccess: #2177: 1: Success after gcc/glibc: 4 commits new a026f2fa04 143: onsuccess: #2178: 1: Success after binutils/gcc/gdb/qem [...] new 5a3ab38d41 144: onsuccess: #2179: 1: Success after binutils/gcc/linux/g [...] new cd02d9439a 145: onsuccess: #2180: 1: Success after binutils/gcc/linux/g [...] new 1f7b9cf084 146: onsuccess: #2181: 1: Success after binutils/glibc/gdb: [...] new 79a531f3a5 147: onsuccess: #2182: 1: Success after binutils/gcc/gdb: 18 [...] new c4aef2bdf0 148: onsuccess: #2183: 1: Success after gcc/linux/glibc: 64 commits new 7b0196ff3d 149: onsuccess: #2184: 1: Success after binutils/gcc/linux/g [...] new d9d2530e4e 150: onsuccess: #2185: 1: Success after gcc: 3 commits new 57386aae77 151: onsuccess: #2186: 1: Success after gcc: 2 commits new de313c06ed 152: onsuccess: #2187: 1: Success after gcc/linux/glibc: 22 commits new 601f9a476d 153: onsuccess: #2188: 1: Success after binutils/gcc/gdb: 3 commits new d15571a75d 154: onsuccess: #2189: 1: Success after binutils/gcc/gdb: 18 [...] new 6d2a20be0b 155: onsuccess: #2190: 1: Success after binutils/gcc/linux/g [...] new 507111de3b 156: onsuccess: #2191: 1: Success after binutils/gcc/linux/g [...] new 9521055c49 157: onsuccess: #2192: 1: Success after binutils/gcc/gdb: 8 commits new ff0fdef838 158: onsuccess: #2193: 1: Success after binutils/gcc/glibc/g [...] new a7441b5949 159: onsuccess: #2194: 1: Success after gcc/linux/glibc: 197 [...] new 7e528af537 160: onsuccess: #2195: 1: Success after binutils/gcc/linux/g [...] new 3031237db2 161: onsuccess: #2196: 1: Success after binutils/gcc/linux/g [...] new a35dba06ad 162: onsuccess: #2197: 1: Success after binutils/gcc/glibc/g [...] new 7a264ef9b8 163: onsuccess: #2198: 1: Success after binutils/gcc/linux/g [...] new a9f43ced30 164: onsuccess: #2199: 1: Success after binutils/gcc/linux/g [...] new 71631952fd 165: onsuccess: #2200: 1: Success after binutils/gdb: 8 commits new d48794c956 166: onsuccess: #2201: 1: Success after gcc/glibc/qemu: 40 commits new 048652fe51 167: onsuccess: #2202: 1: Success after gcc/linux/glibc/qemu [...] new 56efac3fd2 168: onsuccess: #2203: 1: Success after binutils/gcc/glibc/g [...] new 662941d090 169: onsuccess: #2204: 1: Success after binutils/gcc/glibc/g [...] new 5de4fe9da6 170: onsuccess: #2205: 1: Success after binutils/gcc/glibc/g [...] new fa5f7c74d1 171: onsuccess: #2206: 1: Success after binutils/gcc/linux/g [...] new 7faf8340ad 172: onsuccess: #2207: 1: Success after binutils/gcc/linux/g [...] new f5cf5ce2cd 173: onsuccess: #2208: 1: Success after gcc: 10 commits new b82887e406 174: onsuccess: #2209: 1: Success after binutils/gcc/gdb: 20 [...]

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 (cc24250702) \ 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 1708 -> 1736 bytes 02-prepare_abe/console.log.xz | Bin 2736 -> 2744 bytes 03-build_abe-binutils/console.log.xz | Bin 30776 -> 30460 bytes 04-build_abe-stage1/console.log.xz | Bin 72536 -> 72628 bytes 05-clean_sysroot/console.log.xz | Bin 328 -> 328 bytes 06-build_abe-linux/console.log.xz | Bin 8584 -> 8568 bytes 07-build_abe-glibc/console.log.xz | Bin 240412 -> 240232 bytes 08-build_abe-stage2/console.log.xz | Bin 203620 -> 203380 bytes 09-build_abe-gdb/console.log.xz | Bin 37936 -> 37660 bytes 10-build_abe-qemu/console.log.xz | Bin 31760 -> 31696 bytes 11-build_abe-dejagnu/console.log.xz | Bin 3920 -> 3880 bytes 12-build_abe-check_gcc/console.log.xz | Bin 2712 -> 2752 bytes 13-check_regression/console.log.xz | Bin 8840 -> 9036 bytes 13-check_regression/extra-bisect-params | 2 +- 13-check_regression/fails.sum | 97 +- 13-check_regression/mail-body.txt | 195 +- 13-check_regression/results.compare | 82 +- 13-check_regression/results.compare2 | 532 ++- 13-check_regression/results.regressions | 62 +- 14-update_baseline/console.log | 48 +- 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 | 197 +- mail/mail-subject.txt | 2 +- manifest.sh | 34 +- results | 62 +- sumfiles/g++.log.xz | Bin 3427456 -> 3416616 bytes sumfiles/g++.sum | 202 +- sumfiles/gcc.log.xz | Bin 3026824 -> 3031072 bytes sumfiles/gcc.sum | 5427 +++++++++++++++---------------- sumfiles/gfortran.log.xz | Bin 1033216 -> 1026220 bytes sumfiles/gfortran.sum | 44 +- sumfiles/libatomic.log.xz | Bin 2288 -> 2292 bytes sumfiles/libatomic.sum | 4 +- sumfiles/libgomp.log.xz | Bin 202244 -> 202684 bytes sumfiles/libgomp.sum | 16 +- sumfiles/libitm.log.xz | Bin 2692 -> 2692 bytes sumfiles/libitm.sum | 6 +- sumfiles/libstdc++.log.xz | Bin 430360 -> 420764 bytes sumfiles/libstdc++.sum | 16 +- 43 files changed, 3425 insertions(+), 3613 deletions(-)