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 c63d7147cc 187: onsuccess: #2294: 1: Success after binutils/gcc/linux/g [...] discards 05a11a33bd 186: onsuccess: #2291: 1: Success after binutils/gcc/linux/g [...] discards 18097a9d3e 185: onsuccess: #2290: 1: Success after binutils/gcc/linux/g [...] discards 5484edc2fb 184: onsuccess: #2288: 1: Success after binutils/gcc/linux/g [...] discards e432d438fa 183: onsuccess: #2270: 1: Success after binutils/gcc/linux/g [...] discards 639400777d 182: onsuccess: #2247: 1: Success after binutils/gcc/linux/g [...] discards 42ebcbc87f 181: onsuccess: #2239: 1: Success after binutils/gcc/linux/g [...] discards b83cb20183 180: onsuccess: #2232: 1: Success after binutils/gcc/glibc/g [...] discards 3caca465f3 179: onsuccess: #2230: 1: Success after binutils/gcc/linux/g [...] discards 2e275f2cca 178: onsuccess: #2217: 1: Success after binutils/gcc/linux/g [...] discards d32fd54c9d 177: onsuccess: #2212: 1: Success after binutils/gdb: 2 commits discards a2bf92389c 176: onsuccess: #2211: 1: Success after binutils/gcc/linux/g [...] discards 0a64cabfdb 175: onsuccess: #2210: 1: Success after binutils/gcc/linux/g [...] discards 7ed50c9006 174: onsuccess: #2209: 1: Success after binutils/gcc/gdb: 20 [...] discards cd285d403e 173: onsuccess: #2208: 1: Success after gcc: 10 commits discards 8e2d41972b 172: onsuccess: #2207: 1: Success after binutils/gcc/linux/g [...] discards ad784a1230 171: onsuccess: #2206: 1: Success after binutils/gcc/linux/g [...] discards 5e65c48b74 170: onsuccess: #2205: 1: Success after binutils/gcc/glibc/g [...] discards fec488f64d 169: onsuccess: #2204: 1: Success after binutils/gcc/glibc/g [...] discards f5a6e808e4 168: onsuccess: #2203: 1: Success after binutils/gcc/glibc/g [...] discards a87e0fcf6e 167: onsuccess: #2202: 1: Success after gcc/linux/glibc/qemu [...] discards 02b773e80c 166: onsuccess: #2201: 1: Success after gcc/glibc/qemu: 40 commits discards ddc8555900 165: onsuccess: #2200: 1: Success after binutils/gdb: 8 commits discards a5290bef62 164: onsuccess: #2199: 1: Success after binutils/gcc/linux/g [...] discards f1404d18c7 163: onsuccess: #2198: 1: Success after binutils/gcc/linux/g [...] discards f02975beeb 162: onsuccess: #2197: 1: Success after binutils/gcc/glibc/g [...] discards 6281a094fd 161: onsuccess: #2196: 1: Success after binutils/gcc/linux/g [...] discards 95af1c395c 160: onsuccess: #2195: 1: Success after binutils/gcc/linux/g [...] discards 8ff7300f42 159: onsuccess: #2194: 1: Success after gcc/linux/glibc: 197 [...] discards 9d18d9bcb4 158: onsuccess: #2193: 1: Success after binutils/gcc/glibc/g [...] discards ace504107d 157: onsuccess: #2192: 1: Success after binutils/gcc/gdb: 8 commits discards f45cdf9f98 156: onsuccess: #2191: 1: Success after binutils/gcc/linux/g [...] discards 6ab1bc3d6a 155: onsuccess: #2190: 1: Success after binutils/gcc/linux/g [...] discards e0bfba34d1 154: onsuccess: #2189: 1: Success after binutils/gcc/gdb: 18 [...] discards 7a6ffdfd86 153: onsuccess: #2188: 1: Success after binutils/gcc/gdb: 3 commits discards b539441849 152: onsuccess: #2187: 1: Success after gcc/linux/glibc: 22 commits discards 00cbd4ec1e 151: onsuccess: #2186: 1: Success after gcc: 2 commits discards 335c5dafc3 150: onsuccess: #2185: 1: Success after gcc: 3 commits discards e5617d20b7 149: onsuccess: #2184: 1: Success after binutils/gcc/linux/g [...] discards 06d0cb3684 148: onsuccess: #2183: 1: Success after gcc/linux/glibc: 64 commits discards 43d55337b6 147: onsuccess: #2182: 1: Success after binutils/gcc/gdb: 18 [...] discards 9d94873fa4 146: onsuccess: #2181: 1: Success after binutils/glibc/gdb: [...] discards d602af3a39 145: onsuccess: #2180: 1: Success after binutils/gcc/linux/g [...] discards 562bfd3cce 144: onsuccess: #2179: 1: Success after binutils/gcc/linux/g [...] discards 4a8f338dfc 143: onsuccess: #2178: 1: Success after binutils/gcc/gdb/qem [...] discards d66e0fcc64 142: onsuccess: #2177: 1: Success after gcc/glibc: 4 commits discards 1f50c17d06 141: onsuccess: #2176: 1: Success after binutils/gcc/gdb: 6 commits discards a3703dc44d 140: onsuccess: #2175: 1: Success after binutils/gcc/linux/g [...] discards 26566e1bac 139: onsuccess: #2174: 1: Success after binutils/gcc/gdb: 13 [...] discards 785bc18b3d 138: onsuccess: #2173: 1: Success after binutils/gcc/gdb: 5 commits discards ae29c5f494 137: onsuccess: #2172: 1: Success after binutils/gcc/linux/g [...] discards bb49c41f99 136: onsuccess: #2171: 1: Success after binutils/gcc/gdb/qem [...] discards 4113e22446 135: onsuccess: #2170: 1: Success after gcc/linux/qemu: 63 commits discards 238e7d8c4b 134: onsuccess: #2169: 1: Success after binutils/gcc/gdb: 13 [...] discards 41aa75348e 133: onsuccess: #2168: 1: Success after binutils/gcc/linux/g [...] discards 31202e599b 132: onsuccess: #2167: 1: Success after binutils/gcc/glibc/g [...] discards 17bd841f78 131: onsuccess: #2166: 1: Success after binutils/gcc/gdb: 12 [...] discards 7a1da9a634 130: onsuccess: #2165: 1: Success after binutils/gcc/gdb: 32 [...] discards 3cf2f6da6b 129: onsuccess: #2164: 1: Success after binutils/gcc/linux/g [...] discards e82f4db46c 128: onsuccess: #2163: 1: Success after linux: 23 commits discards 7d671c0947 127: onsuccess: #2162: 1: Success after gcc: 9 commits discards f389ac1361 126: onsuccess: #2161: 1: Success after basepoints/gcc-13-28 [...] discards ddb3685d38 125: onsuccess: #2160: 1: Success after binutils/gcc/linux/g [...] discards dda92f6697 124: onsuccess: #2159: 1: Success after linux: 23 commits discards c31f6a1ff4 123: onsuccess: #2158: 1: Success after basepoints/gcc-13-28 [...] discards 8445c130dd 122: onsuccess: #2157: 1: Success after binutils/gcc/gdb: 6 commits discards 93a947eb75 121: onsuccess: #2156: 1: Success after binutils/gcc/linux/g [...] discards 9f8f01641a 120: onsuccess: #2155: 1: Success after binutils/gcc/linux/g [...] discards eb43b23930 119: onsuccess: #2154: 1: Success after binutils/gcc/linux/g [...] discards b7705b1510 118: onsuccess: #2151: 1: Success after binutils/gcc/linux/g [...] discards 5685c1492f 117: onsuccess: #2150: 1: Success after binutils/gcc/glibc/g [...] discards c6b501fabe 116: onsuccess: #2148: 1: Success after binutils/gcc/gdb: 7 commits discards 31e896974e 115: onsuccess: #2147: 1: Success after binutils/linux/glibc [...] discards 53df894ae2 114: onsuccess: #2146: 1: Success after binutils/gcc/glibc/g [...] discards 0fe23b1b39 113: onsuccess: #2145: 1: Success after binutils/gcc/glibc/g [...] discards 4d2e3d758c 112: onsuccess: #2144: 1: Success after binutils/gcc/glibc/g [...] discards 4ab6ea9944 111: onsuccess: #2143: 1: Success after binutils/gcc/linux/g [...] discards 32f43c33b3 110: onsuccess: #2142: 1: Success after binutils/gcc/glibc/g [...] discards 307b67d50c 109: onsuccess: #2141: 1: Success after gcc/glibc: 6 commits discards 267da01159 108: onsuccess: #2140: 1: Success after binutils/gcc/gdb: 5 commits discards aee98e55e5 107: onsuccess: #2139: 1: Success after binutils/gcc/gdb: 3 commits discards 0a35b6d10b 106: onsuccess: #2138: 1: Success after binutils/gcc/glibc/g [...] discards 7409f44c57 105: onsuccess: #2137: 1: Success after basepoints/gcc-13-27 [...] discards 149fc48cb9 104: onsuccess: #2136: 1: Success after binutils/gcc/gdb: 3 commits discards 721a83f2e8 103: onsuccess: #2135: 1: Success after gcc/linux/glibc/gdb/ [...] discards 9f3fc7e20d 102: onsuccess: #2133: 1: Success after gdb-12-branchpoint-1 [...] discards c54156b09e 101: onsuccess: #2130: 1: Success after binutils: 81 commits discards 93b0ecd72c 100: onsuccess: #2077: 1: Success after binutils/gcc/linux/g [...] discards d623ba2b73 99: onsuccess: #2074: 1: Success after baseline build: no ne [...] discards e85b272653 98: onsuccess: #2073: 1: Success after gcc/linux: 11 commits discards 27c72eeb66 97: onsuccess: #2072: 1: Success after binutils/gcc/gdb: 3 commits discards 6d55fb98b8 96: onsuccess: #2071: 1: Success after gcc/linux: 56 commits discards 0910f188be 95: onsuccess: #2070: 1: Success after basepoints/gcc-13-238 [...] discards 8290eaf867 94: onsuccess: 1: Success after gcc: openmp: Partial OpenMP [...] discards 8d0996472b 93: onsuccess: 1: Success after binutils/gcc/linux/gdb: 88 commits discards f6475821c4 92: onsuccess: 1: Success after binutils/gcc/linux/gdb/qemu: [...] discards 7a7b0b160c 91: onsuccess: 1: Success after binutils/gcc/gdb: 8 commits discards 589b0353d3 90: onsuccess: 1: Success after binutils/gcc/gdb: 19 commits discards 5cfb5402f6 89: onsuccess: 1: Success after binutils/gcc/gdb: 5 commits discards 22ae164e72 88: onsuccess: 1: Success after gcc/linux/qemu: 149 commits discards 3be5503806 87: onsuccess: 1: Success after binutils/gcc/gdb: 14 commits new fdd210853e 87: onsuccess: 1: Success after binutils/gcc/gdb: 14 commits new dcf7c09a4f 88: onsuccess: 1: Success after gcc/linux/qemu: 149 commits new 40674810ef 89: onsuccess: 1: Success after binutils/gcc/gdb: 5 commits new bd6ab57f75 90: onsuccess: 1: Success after binutils/gcc/gdb: 19 commits new 8014188dae 91: onsuccess: 1: Success after binutils/gcc/gdb: 8 commits new 4401dd17fc 92: onsuccess: 1: Success after binutils/gcc/linux/gdb/qemu: [...] new 931c4d0927 93: onsuccess: 1: Success after binutils/gcc/linux/gdb: 88 commits new 5a8024e8a1 94: onsuccess: 1: Success after gcc: openmp: Partial OpenMP [...] new bd7b1b5b08 95: onsuccess: #2070: 1: Success after basepoints/gcc-13-238 [...] new 54c7c7437f 96: onsuccess: #2071: 1: Success after gcc/linux: 56 commits new f6c6919180 97: onsuccess: #2072: 1: Success after binutils/gcc/gdb: 3 commits new ce5931d2df 98: onsuccess: #2073: 1: Success after gcc/linux: 11 commits new 45fb72d5a7 99: onsuccess: #2074: 1: Success after baseline build: no ne [...] new 9320549849 100: onsuccess: #2077: 1: Success after binutils/gcc/linux/g [...] new b634a52bcc 101: onsuccess: #2130: 1: Success after binutils: 81 commits new b834fe6b9b 102: onsuccess: #2133: 1: Success after gdb-12-branchpoint-1 [...] new c7645fc14e 103: onsuccess: #2135: 1: Success after gcc/linux/glibc/gdb/ [...] new 82828845ce 104: onsuccess: #2136: 1: Success after binutils/gcc/gdb: 3 commits new f3c95aeb9a 105: onsuccess: #2137: 1: Success after basepoints/gcc-13-27 [...] new 94fa7f723f 106: onsuccess: #2138: 1: Success after binutils/gcc/glibc/g [...] new 619901dae0 107: onsuccess: #2139: 1: Success after binutils/gcc/gdb: 3 commits new 5e547608b4 108: onsuccess: #2140: 1: Success after binutils/gcc/gdb: 5 commits new a4d6450929 109: onsuccess: #2141: 1: Success after gcc/glibc: 6 commits new 6791459854 110: onsuccess: #2142: 1: Success after binutils/gcc/glibc/g [...] new 5afe049fae 111: onsuccess: #2143: 1: Success after binutils/gcc/linux/g [...] new 6ca08215bd 112: onsuccess: #2144: 1: Success after binutils/gcc/glibc/g [...] new d794a0c8b1 113: onsuccess: #2145: 1: Success after binutils/gcc/glibc/g [...] new 5b87be5a2d 114: onsuccess: #2146: 1: Success after binutils/gcc/glibc/g [...] new c4083d9e55 115: onsuccess: #2147: 1: Success after binutils/linux/glibc [...] new 297c308737 116: onsuccess: #2148: 1: Success after binutils/gcc/gdb: 7 commits new d657c3277e 117: onsuccess: #2150: 1: Success after binutils/gcc/glibc/g [...] new 0ab46fc68e 118: onsuccess: #2151: 1: Success after binutils/gcc/linux/g [...] new 656cf6aac9 119: onsuccess: #2154: 1: Success after binutils/gcc/linux/g [...] new 387caa047e 120: onsuccess: #2155: 1: Success after binutils/gcc/linux/g [...] new b7736b59dd 121: onsuccess: #2156: 1: Success after binutils/gcc/linux/g [...] new db1c3b0fe7 122: onsuccess: #2157: 1: Success after binutils/gcc/gdb: 6 commits new adefd0e32c 123: onsuccess: #2158: 1: Success after basepoints/gcc-13-28 [...] new 8ef0e63e54 124: onsuccess: #2159: 1: Success after linux: 23 commits new daa093a56c 125: onsuccess: #2160: 1: Success after binutils/gcc/linux/g [...] new cdbf2c797c 126: onsuccess: #2161: 1: Success after basepoints/gcc-13-28 [...] new aa9f22e49d 127: onsuccess: #2162: 1: Success after gcc: 9 commits new f1f7f2eef2 128: onsuccess: #2163: 1: Success after linux: 23 commits new 27d3cd03a6 129: onsuccess: #2164: 1: Success after binutils/gcc/linux/g [...] new e73db05c90 130: onsuccess: #2165: 1: Success after binutils/gcc/gdb: 32 [...] new f603c5cf55 131: onsuccess: #2166: 1: Success after binutils/gcc/gdb: 12 [...] new dce960a7b8 132: onsuccess: #2167: 1: Success after binutils/gcc/glibc/g [...] new 6277324b62 133: onsuccess: #2168: 1: Success after binutils/gcc/linux/g [...] new 951abb3207 134: onsuccess: #2169: 1: Success after binutils/gcc/gdb: 13 [...] new fcc312558c 135: onsuccess: #2170: 1: Success after gcc/linux/qemu: 63 commits new efb5184516 136: onsuccess: #2171: 1: Success after binutils/gcc/gdb/qem [...] new e7fde599e5 137: onsuccess: #2172: 1: Success after binutils/gcc/linux/g [...] new 81e7681bb5 138: onsuccess: #2173: 1: Success after binutils/gcc/gdb: 5 commits new 948360b1cc 139: onsuccess: #2174: 1: Success after binutils/gcc/gdb: 13 [...] new 411f3ea678 140: onsuccess: #2175: 1: Success after binutils/gcc/linux/g [...] new 8e851650f2 141: onsuccess: #2176: 1: Success after binutils/gcc/gdb: 6 commits new a33e6c2aa4 142: onsuccess: #2177: 1: Success after gcc/glibc: 4 commits new 3e44c92026 143: onsuccess: #2178: 1: Success after binutils/gcc/gdb/qem [...] new 6e406cbd6a 144: onsuccess: #2179: 1: Success after binutils/gcc/linux/g [...] new c60cca766f 145: onsuccess: #2180: 1: Success after binutils/gcc/linux/g [...] new 04b80b68c4 146: onsuccess: #2181: 1: Success after binutils/glibc/gdb: [...] new cc7d3a84ee 147: onsuccess: #2182: 1: Success after binutils/gcc/gdb: 18 [...] new e8b194720e 148: onsuccess: #2183: 1: Success after gcc/linux/glibc: 64 commits new 0d35214f62 149: onsuccess: #2184: 1: Success after binutils/gcc/linux/g [...] new a3c86a707c 150: onsuccess: #2185: 1: Success after gcc: 3 commits new 76c0d15f90 151: onsuccess: #2186: 1: Success after gcc: 2 commits new 31f5845dcc 152: onsuccess: #2187: 1: Success after gcc/linux/glibc: 22 commits new 25a47aec8a 153: onsuccess: #2188: 1: Success after binutils/gcc/gdb: 3 commits new dfee17e2fc 154: onsuccess: #2189: 1: Success after binutils/gcc/gdb: 18 [...] new c8a1c652a9 155: onsuccess: #2190: 1: Success after binutils/gcc/linux/g [...] new cabb299141 156: onsuccess: #2191: 1: Success after binutils/gcc/linux/g [...] new 01e326203a 157: onsuccess: #2192: 1: Success after binutils/gcc/gdb: 8 commits new 20b7356e31 158: onsuccess: #2193: 1: Success after binutils/gcc/glibc/g [...] new bc756aff7f 159: onsuccess: #2194: 1: Success after gcc/linux/glibc: 197 [...] new 30e2786d59 160: onsuccess: #2195: 1: Success after binutils/gcc/linux/g [...] new 816d307e57 161: onsuccess: #2196: 1: Success after binutils/gcc/linux/g [...] new f64b425e61 162: onsuccess: #2197: 1: Success after binutils/gcc/glibc/g [...] new efa488a797 163: onsuccess: #2198: 1: Success after binutils/gcc/linux/g [...] new e65c915b0f 164: onsuccess: #2199: 1: Success after binutils/gcc/linux/g [...] new 973eb4b4e5 165: onsuccess: #2200: 1: Success after binutils/gdb: 8 commits new f1369924ec 166: onsuccess: #2201: 1: Success after gcc/glibc/qemu: 40 commits new 07115c3a96 167: onsuccess: #2202: 1: Success after gcc/linux/glibc/qemu [...] new 0791069319 168: onsuccess: #2203: 1: Success after binutils/gcc/glibc/g [...] new 127a6e689d 169: onsuccess: #2204: 1: Success after binutils/gcc/glibc/g [...] new 6ea4c530a5 170: onsuccess: #2205: 1: Success after binutils/gcc/glibc/g [...] new 65b47e0ddd 171: onsuccess: #2206: 1: Success after binutils/gcc/linux/g [...] new 8baa08b689 172: onsuccess: #2207: 1: Success after binutils/gcc/linux/g [...] new 256310bc09 173: onsuccess: #2208: 1: Success after gcc: 10 commits new 2998116d3d 174: onsuccess: #2209: 1: Success after binutils/gcc/gdb: 20 [...] new 55f801c699 175: onsuccess: #2210: 1: Success after binutils/gcc/linux/g [...] new 503b314c1f 176: onsuccess: #2211: 1: Success after binutils/gcc/linux/g [...] new 70a0042b0a 177: onsuccess: #2212: 1: Success after binutils/gdb: 2 commits new 5dd68b9413 178: onsuccess: #2217: 1: Success after binutils/gcc/linux/g [...] new 135a731da5 179: onsuccess: #2230: 1: Success after binutils/gcc/linux/g [...] new cc67f59368 180: onsuccess: #2232: 1: Success after binutils/gcc/glibc/g [...] new dd9916858d 181: onsuccess: #2239: 1: Success after binutils/gcc/linux/g [...] new dbfc5a7512 182: onsuccess: #2247: 1: Success after binutils/gcc/linux/g [...] new 9fbf9ba8bb 183: onsuccess: #2270: 1: Success after binutils/gcc/linux/g [...] new 414f735c2c 184: onsuccess: #2288: 1: Success after binutils/gcc/linux/g [...] new 4e894c4d93 185: onsuccess: #2290: 1: Success after binutils/gcc/linux/g [...] new 47d340a534 186: onsuccess: #2291: 1: Success after binutils/gcc/linux/g [...] new da659b8de3 187: onsuccess: #2294: 1: Success after binutils/gcc/linux/g [...] new 38a662256b 188: onsuccess: #2295: 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 (c63d7147cc) \ 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 1768 -> 1696 bytes 02-prepare_abe/console.log.xz | Bin 2752 -> 2756 bytes 03-build_abe-binutils/console.log.xz | Bin 31028 -> 30144 bytes 04-build_abe-stage1/console.log.xz | Bin 72624 -> 72372 bytes 06-build_abe-linux/console.log.xz | Bin 9104 -> 8740 bytes 07-build_abe-glibc/console.log.xz | Bin 239772 -> 239996 bytes 08-build_abe-stage2/console.log.xz | Bin 203672 -> 202844 bytes 09-build_abe-gdb/console.log.xz | Bin 37588 -> 37540 bytes 10-build_abe-qemu/console.log.xz | Bin 31888 -> 32272 bytes 11-build_abe-dejagnu/console.log.xz | Bin 3904 -> 3888 bytes 12-build_abe-check_gcc/console.log.xz | Bin 2800 -> 2604 bytes 13-check_regression/console.log.xz | Bin 13700 -> 10740 bytes 13-check_regression/extra-bisect-params | 2 +- 13-check_regression/fails.sum | 69 +- 13-check_regression/mail-body.txt | 230 +- 13-check_regression/results.compare | 187 +- 13-check_regression/results.compare2 | 1761 +++++------ 13-check_regression/results.regressions | 112 +- 14-update_baseline/console.log | 70 +- 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 | 232 +- mail/mail-subject.txt | 2 +- manifest.sh | 38 +- results | 112 +- sumfiles/g++.log.xz | Bin 3432872 -> 3421660 bytes sumfiles/g++.sum | 67 +- sumfiles/gcc.log.xz | Bin 3047764 -> 3039956 bytes sumfiles/gcc.sum | 4919 ++++++++++++++----------------- sumfiles/gfortran.log.xz | Bin 1040688 -> 1031520 bytes sumfiles/gfortran.sum | 6 +- sumfiles/libatomic.log.xz | Bin 2288 -> 2296 bytes sumfiles/libatomic.sum | 2 +- sumfiles/libgomp.log.xz | Bin 204060 -> 204100 bytes sumfiles/libgomp.sum | 2 +- sumfiles/libitm.log.xz | Bin 2700 -> 2692 bytes sumfiles/libitm.sum | 2 +- sumfiles/libstdc++.log.xz | Bin 428104 -> 423392 bytes sumfiles/libstdc++.sum | 8 +- 43 files changed, 3506 insertions(+), 4327 deletions(-)