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 c3a83d104f 186: onsuccess: #2291: 1: Success after binutils/gcc/linux/g [...] discards 17eaf0c340 185: onsuccess: #2290: 1: Success after binutils/gcc/linux/g [...] discards af8e7dc7f2 184: onsuccess: #2288: 1: Success after binutils/gcc/linux/g [...] discards 2aa1b4f0a6 183: onsuccess: #2270: 1: Success after binutils/gcc/linux/g [...] discards d2dd5094ba 182: onsuccess: #2247: 1: Success after binutils/gcc/linux/g [...] discards 631b754a51 181: onsuccess: #2239: 1: Success after binutils/gcc/linux/g [...] discards d9afbbdb32 180: onsuccess: #2232: 1: Success after binutils/gcc/glibc/g [...] discards 2d8745a556 179: onsuccess: #2230: 1: Success after binutils/gcc/linux/g [...] discards d4150e471b 178: onsuccess: #2217: 1: Success after binutils/gcc/linux/g [...] discards 0cb3c872df 177: onsuccess: #2212: 1: Success after binutils/gdb: 2 commits discards 7262e9a152 176: onsuccess: #2211: 1: Success after binutils/gcc/linux/g [...] discards ca543cf7f4 175: onsuccess: #2210: 1: Success after binutils/gcc/linux/g [...] discards cdd91a26c6 174: onsuccess: #2209: 1: Success after binutils/gcc/gdb: 20 [...] discards 2f0432970d 173: onsuccess: #2208: 1: Success after gcc: 10 commits discards 713c9401ea 172: onsuccess: #2207: 1: Success after binutils/gcc/linux/g [...] discards 5e793e914a 171: onsuccess: #2206: 1: Success after binutils/gcc/linux/g [...] discards 06848091f9 170: onsuccess: #2205: 1: Success after binutils/gcc/glibc/g [...] discards ce5f078594 169: onsuccess: #2204: 1: Success after binutils/gcc/glibc/g [...] discards 890233a870 168: onsuccess: #2203: 1: Success after binutils/gcc/glibc/g [...] discards f75064a27b 167: onsuccess: #2202: 1: Success after gcc/linux/glibc/qemu [...] discards e252c7cbfd 166: onsuccess: #2201: 1: Success after gcc/glibc/qemu: 40 commits discards 3fe7b7b1ca 165: onsuccess: #2200: 1: Success after binutils/gdb: 8 commits discards 61a3b3c8cb 164: onsuccess: #2199: 1: Success after binutils/gcc/linux/g [...] discards 103a95ab94 163: onsuccess: #2198: 1: Success after binutils/gcc/linux/g [...] discards fb9a1bf81c 162: onsuccess: #2197: 1: Success after binutils/gcc/glibc/g [...] discards 2b70740254 161: onsuccess: #2196: 1: Success after binutils/gcc/linux/g [...] discards c02a85c816 160: onsuccess: #2195: 1: Success after binutils/gcc/linux/g [...] discards db561daf2a 159: onsuccess: #2194: 1: Success after gcc/linux/glibc: 197 [...] discards 6061d11d99 158: onsuccess: #2193: 1: Success after binutils/gcc/glibc/g [...] discards 857e7a13ca 157: onsuccess: #2192: 1: Success after binutils/gcc/gdb: 8 commits discards 651791535e 156: onsuccess: #2191: 1: Success after binutils/gcc/linux/g [...] discards f76fc06258 155: onsuccess: #2190: 1: Success after binutils/gcc/linux/g [...] discards afbf4e62c8 154: onsuccess: #2189: 1: Success after binutils/gcc/gdb: 18 [...] discards 74bba532b3 153: onsuccess: #2188: 1: Success after binutils/gcc/gdb: 3 commits discards 8729fc4965 152: onsuccess: #2187: 1: Success after gcc/linux/glibc: 22 commits discards 6b8b0a4044 151: onsuccess: #2186: 1: Success after gcc: 2 commits discards 961edbd3a4 150: onsuccess: #2185: 1: Success after gcc: 3 commits discards e82a74bf25 149: onsuccess: #2184: 1: Success after binutils/gcc/linux/g [...] discards c75c1ce155 148: onsuccess: #2183: 1: Success after gcc/linux/glibc: 64 commits discards 92f5fbe0dc 147: onsuccess: #2182: 1: Success after binutils/gcc/gdb: 18 [...] discards 7cd55020b5 146: onsuccess: #2181: 1: Success after binutils/glibc/gdb: [...] discards 3c35c2985b 145: onsuccess: #2180: 1: Success after binutils/gcc/linux/g [...] discards e29ad8c667 144: onsuccess: #2179: 1: Success after binutils/gcc/linux/g [...] discards 2b0b40b8a1 143: onsuccess: #2178: 1: Success after binutils/gcc/gdb/qem [...] discards d9bd9c3515 142: onsuccess: #2177: 1: Success after gcc/glibc: 4 commits discards 933769ad60 141: onsuccess: #2176: 1: Success after binutils/gcc/gdb: 6 commits discards 332d582e06 140: onsuccess: #2175: 1: Success after binutils/gcc/linux/g [...] discards e6a3922e08 139: onsuccess: #2174: 1: Success after binutils/gcc/gdb: 13 [...] discards d20f641880 138: onsuccess: #2173: 1: Success after binutils/gcc/gdb: 5 commits discards b194dfcd1b 137: onsuccess: #2172: 1: Success after binutils/gcc/linux/g [...] discards 0f136db770 136: onsuccess: #2171: 1: Success after binutils/gcc/gdb/qem [...] discards a5cb041c8d 135: onsuccess: #2170: 1: Success after gcc/linux/qemu: 63 commits discards 12ac6ee2a7 134: onsuccess: #2169: 1: Success after binutils/gcc/gdb: 13 [...] discards 983fac4ad8 133: onsuccess: #2168: 1: Success after binutils/gcc/linux/g [...] discards ee15e4fd64 132: onsuccess: #2167: 1: Success after binutils/gcc/glibc/g [...] discards 540f965339 131: onsuccess: #2166: 1: Success after binutils/gcc/gdb: 12 [...] discards 1885d4a52d 130: onsuccess: #2165: 1: Success after binutils/gcc/gdb: 32 [...] discards 5e5e45d764 129: onsuccess: #2164: 1: Success after binutils/gcc/linux/g [...] discards 2e3aa2aadc 128: onsuccess: #2163: 1: Success after linux: 23 commits discards 17d3fc17b5 127: onsuccess: #2162: 1: Success after gcc: 9 commits discards 3e32781ec0 126: onsuccess: #2161: 1: Success after basepoints/gcc-13-28 [...] discards a031725507 125: onsuccess: #2160: 1: Success after binutils/gcc/linux/g [...] discards a8933ca906 124: onsuccess: #2159: 1: Success after linux: 23 commits discards f5d8517376 123: onsuccess: #2158: 1: Success after basepoints/gcc-13-28 [...] discards 2d5d10ebda 122: onsuccess: #2157: 1: Success after binutils/gcc/gdb: 6 commits discards 3b30063588 121: onsuccess: #2156: 1: Success after binutils/gcc/linux/g [...] discards de3e7e3446 120: onsuccess: #2155: 1: Success after binutils/gcc/linux/g [...] discards 72ff8df929 119: onsuccess: #2154: 1: Success after binutils/gcc/linux/g [...] discards 97a9b10f69 118: onsuccess: #2151: 1: Success after binutils/gcc/linux/g [...] discards 35d66e2357 117: onsuccess: #2150: 1: Success after binutils/gcc/glibc/g [...] discards c27f380623 116: onsuccess: #2148: 1: Success after binutils/gcc/gdb: 7 commits discards bc1316964f 115: onsuccess: #2147: 1: Success after binutils/linux/glibc [...] discards 07990ab4e9 114: onsuccess: #2146: 1: Success after binutils/gcc/glibc/g [...] discards f3ab1d1f31 113: onsuccess: #2145: 1: Success after binutils/gcc/glibc/g [...] discards 17020e22ff 112: onsuccess: #2144: 1: Success after binutils/gcc/glibc/g [...] discards 329f3cd17c 111: onsuccess: #2143: 1: Success after binutils/gcc/linux/g [...] discards 3669588843 110: onsuccess: #2142: 1: Success after binutils/gcc/glibc/g [...] discards b9ed71420c 109: onsuccess: #2141: 1: Success after gcc/glibc: 6 commits discards b638a369da 108: onsuccess: #2140: 1: Success after binutils/gcc/gdb: 5 commits discards ec9be47718 107: onsuccess: #2139: 1: Success after binutils/gcc/gdb: 3 commits discards b90f121b98 106: onsuccess: #2138: 1: Success after binutils/gcc/glibc/g [...] discards 11ab54e4bb 105: onsuccess: #2137: 1: Success after basepoints/gcc-13-27 [...] discards f9a5c69406 104: onsuccess: #2136: 1: Success after binutils/gcc/gdb: 3 commits discards 5f0b9d1568 103: onsuccess: #2135: 1: Success after gcc/linux/glibc/gdb/ [...] discards e72f80b24b 102: onsuccess: #2133: 1: Success after gdb-12-branchpoint-1 [...] discards b4e175811f 101: onsuccess: #2130: 1: Success after binutils: 81 commits discards f21a82d2ef 100: onsuccess: #2077: 1: Success after binutils/gcc/linux/g [...] discards 43b15ab548 99: onsuccess: #2074: 1: Success after baseline build: no ne [...] discards 5b5c3154c8 98: onsuccess: #2073: 1: Success after gcc/linux: 11 commits discards d200d32120 97: onsuccess: #2072: 1: Success after binutils/gcc/gdb: 3 commits discards bce0613ee9 96: onsuccess: #2071: 1: Success after gcc/linux: 56 commits discards 45f8d80da1 95: onsuccess: #2070: 1: Success after basepoints/gcc-13-238 [...] discards f373bbe963 94: onsuccess: 1: Success after gcc: openmp: Partial OpenMP [...] discards c0bb46fb0e 93: onsuccess: 1: Success after binutils/gcc/linux/gdb: 88 commits discards 2bf23f2bd0 92: onsuccess: 1: Success after binutils/gcc/linux/gdb/qemu: [...] discards 837389dd17 91: onsuccess: 1: Success after binutils/gcc/gdb: 8 commits discards 16d7d0b746 90: onsuccess: 1: Success after binutils/gcc/gdb: 19 commits discards 6bd3ba0d01 89: onsuccess: 1: Success after binutils/gcc/gdb: 5 commits discards f6f3a4eac1 88: onsuccess: 1: Success after gcc/linux/qemu: 149 commits discards 31bf5abe97 87: onsuccess: 1: Success after binutils/gcc/gdb: 14 commits discards d82eee8311 86: onsuccess: 1: Success after binutils/gcc/gdb: 7 commits new c3a0b6cc65 86: onsuccess: 1: Success after binutils/gcc/gdb: 7 commits new 3be5503806 87: onsuccess: 1: Success after binutils/gcc/gdb: 14 commits new 22ae164e72 88: onsuccess: 1: Success after gcc/linux/qemu: 149 commits new 5cfb5402f6 89: onsuccess: 1: Success after binutils/gcc/gdb: 5 commits new 589b0353d3 90: onsuccess: 1: Success after binutils/gcc/gdb: 19 commits new 7a7b0b160c 91: onsuccess: 1: Success after binutils/gcc/gdb: 8 commits new f6475821c4 92: onsuccess: 1: Success after binutils/gcc/linux/gdb/qemu: [...] new 8d0996472b 93: onsuccess: 1: Success after binutils/gcc/linux/gdb: 88 commits new 8290eaf867 94: onsuccess: 1: Success after gcc: openmp: Partial OpenMP [...] new 0910f188be 95: onsuccess: #2070: 1: Success after basepoints/gcc-13-238 [...] new 6d55fb98b8 96: onsuccess: #2071: 1: Success after gcc/linux: 56 commits new 27c72eeb66 97: onsuccess: #2072: 1: Success after binutils/gcc/gdb: 3 commits new e85b272653 98: onsuccess: #2073: 1: Success after gcc/linux: 11 commits new d623ba2b73 99: onsuccess: #2074: 1: Success after baseline build: no ne [...] new 93b0ecd72c 100: onsuccess: #2077: 1: Success after binutils/gcc/linux/g [...] new c54156b09e 101: onsuccess: #2130: 1: Success after binutils: 81 commits new 9f3fc7e20d 102: onsuccess: #2133: 1: Success after gdb-12-branchpoint-1 [...] new 721a83f2e8 103: onsuccess: #2135: 1: Success after gcc/linux/glibc/gdb/ [...] new 149fc48cb9 104: onsuccess: #2136: 1: Success after binutils/gcc/gdb: 3 commits new 7409f44c57 105: onsuccess: #2137: 1: Success after basepoints/gcc-13-27 [...] new 0a35b6d10b 106: onsuccess: #2138: 1: Success after binutils/gcc/glibc/g [...] new aee98e55e5 107: onsuccess: #2139: 1: Success after binutils/gcc/gdb: 3 commits new 267da01159 108: onsuccess: #2140: 1: Success after binutils/gcc/gdb: 5 commits new 307b67d50c 109: onsuccess: #2141: 1: Success after gcc/glibc: 6 commits new 32f43c33b3 110: onsuccess: #2142: 1: Success after binutils/gcc/glibc/g [...] new 4ab6ea9944 111: onsuccess: #2143: 1: Success after binutils/gcc/linux/g [...] new 4d2e3d758c 112: onsuccess: #2144: 1: Success after binutils/gcc/glibc/g [...] new 0fe23b1b39 113: onsuccess: #2145: 1: Success after binutils/gcc/glibc/g [...] new 53df894ae2 114: onsuccess: #2146: 1: Success after binutils/gcc/glibc/g [...] new 31e896974e 115: onsuccess: #2147: 1: Success after binutils/linux/glibc [...] new c6b501fabe 116: onsuccess: #2148: 1: Success after binutils/gcc/gdb: 7 commits new 5685c1492f 117: onsuccess: #2150: 1: Success after binutils/gcc/glibc/g [...] new b7705b1510 118: onsuccess: #2151: 1: Success after binutils/gcc/linux/g [...] new eb43b23930 119: onsuccess: #2154: 1: Success after binutils/gcc/linux/g [...] new 9f8f01641a 120: onsuccess: #2155: 1: Success after binutils/gcc/linux/g [...] new 93a947eb75 121: onsuccess: #2156: 1: Success after binutils/gcc/linux/g [...] new 8445c130dd 122: onsuccess: #2157: 1: Success after binutils/gcc/gdb: 6 commits new c31f6a1ff4 123: onsuccess: #2158: 1: Success after basepoints/gcc-13-28 [...] new dda92f6697 124: onsuccess: #2159: 1: Success after linux: 23 commits new ddb3685d38 125: onsuccess: #2160: 1: Success after binutils/gcc/linux/g [...] new f389ac1361 126: onsuccess: #2161: 1: Success after basepoints/gcc-13-28 [...] new 7d671c0947 127: onsuccess: #2162: 1: Success after gcc: 9 commits new e82f4db46c 128: onsuccess: #2163: 1: Success after linux: 23 commits new 3cf2f6da6b 129: onsuccess: #2164: 1: Success after binutils/gcc/linux/g [...] new 7a1da9a634 130: onsuccess: #2165: 1: Success after binutils/gcc/gdb: 32 [...] new 17bd841f78 131: onsuccess: #2166: 1: Success after binutils/gcc/gdb: 12 [...] new 31202e599b 132: onsuccess: #2167: 1: Success after binutils/gcc/glibc/g [...] new 41aa75348e 133: onsuccess: #2168: 1: Success after binutils/gcc/linux/g [...] new 238e7d8c4b 134: onsuccess: #2169: 1: Success after binutils/gcc/gdb: 13 [...] new 4113e22446 135: onsuccess: #2170: 1: Success after gcc/linux/qemu: 63 commits new bb49c41f99 136: onsuccess: #2171: 1: Success after binutils/gcc/gdb/qem [...] new ae29c5f494 137: onsuccess: #2172: 1: Success after binutils/gcc/linux/g [...] new 785bc18b3d 138: onsuccess: #2173: 1: Success after binutils/gcc/gdb: 5 commits new 26566e1bac 139: onsuccess: #2174: 1: Success after binutils/gcc/gdb: 13 [...] new a3703dc44d 140: onsuccess: #2175: 1: Success after binutils/gcc/linux/g [...] new 1f50c17d06 141: onsuccess: #2176: 1: Success after binutils/gcc/gdb: 6 commits new d66e0fcc64 142: onsuccess: #2177: 1: Success after gcc/glibc: 4 commits new 4a8f338dfc 143: onsuccess: #2178: 1: Success after binutils/gcc/gdb/qem [...] new 562bfd3cce 144: onsuccess: #2179: 1: Success after binutils/gcc/linux/g [...] new d602af3a39 145: onsuccess: #2180: 1: Success after binutils/gcc/linux/g [...] new 9d94873fa4 146: onsuccess: #2181: 1: Success after binutils/glibc/gdb: [...] new 43d55337b6 147: onsuccess: #2182: 1: Success after binutils/gcc/gdb: 18 [...] new 06d0cb3684 148: onsuccess: #2183: 1: Success after gcc/linux/glibc: 64 commits new e5617d20b7 149: onsuccess: #2184: 1: Success after binutils/gcc/linux/g [...] new 335c5dafc3 150: onsuccess: #2185: 1: Success after gcc: 3 commits new 00cbd4ec1e 151: onsuccess: #2186: 1: Success after gcc: 2 commits new b539441849 152: onsuccess: #2187: 1: Success after gcc/linux/glibc: 22 commits new 7a6ffdfd86 153: onsuccess: #2188: 1: Success after binutils/gcc/gdb: 3 commits new e0bfba34d1 154: onsuccess: #2189: 1: Success after binutils/gcc/gdb: 18 [...] new 6ab1bc3d6a 155: onsuccess: #2190: 1: Success after binutils/gcc/linux/g [...] new f45cdf9f98 156: onsuccess: #2191: 1: Success after binutils/gcc/linux/g [...] new ace504107d 157: onsuccess: #2192: 1: Success after binutils/gcc/gdb: 8 commits new 9d18d9bcb4 158: onsuccess: #2193: 1: Success after binutils/gcc/glibc/g [...] new 8ff7300f42 159: onsuccess: #2194: 1: Success after gcc/linux/glibc: 197 [...] new 95af1c395c 160: onsuccess: #2195: 1: Success after binutils/gcc/linux/g [...] new 6281a094fd 161: onsuccess: #2196: 1: Success after binutils/gcc/linux/g [...] new f02975beeb 162: onsuccess: #2197: 1: Success after binutils/gcc/glibc/g [...] new f1404d18c7 163: onsuccess: #2198: 1: Success after binutils/gcc/linux/g [...] new a5290bef62 164: onsuccess: #2199: 1: Success after binutils/gcc/linux/g [...] new ddc8555900 165: onsuccess: #2200: 1: Success after binutils/gdb: 8 commits new 02b773e80c 166: onsuccess: #2201: 1: Success after gcc/glibc/qemu: 40 commits new a87e0fcf6e 167: onsuccess: #2202: 1: Success after gcc/linux/glibc/qemu [...] new f5a6e808e4 168: onsuccess: #2203: 1: Success after binutils/gcc/glibc/g [...] new fec488f64d 169: onsuccess: #2204: 1: Success after binutils/gcc/glibc/g [...] new 5e65c48b74 170: onsuccess: #2205: 1: Success after binutils/gcc/glibc/g [...] new ad784a1230 171: onsuccess: #2206: 1: Success after binutils/gcc/linux/g [...] new 8e2d41972b 172: onsuccess: #2207: 1: Success after binutils/gcc/linux/g [...] new cd285d403e 173: onsuccess: #2208: 1: Success after gcc: 10 commits new 7ed50c9006 174: onsuccess: #2209: 1: Success after binutils/gcc/gdb: 20 [...] new 0a64cabfdb 175: onsuccess: #2210: 1: Success after binutils/gcc/linux/g [...] new a2bf92389c 176: onsuccess: #2211: 1: Success after binutils/gcc/linux/g [...] new d32fd54c9d 177: onsuccess: #2212: 1: Success after binutils/gdb: 2 commits new 2e275f2cca 178: onsuccess: #2217: 1: Success after binutils/gcc/linux/g [...] new 3caca465f3 179: onsuccess: #2230: 1: Success after binutils/gcc/linux/g [...] new b83cb20183 180: onsuccess: #2232: 1: Success after binutils/gcc/glibc/g [...] new 42ebcbc87f 181: onsuccess: #2239: 1: Success after binutils/gcc/linux/g [...] new 639400777d 182: onsuccess: #2247: 1: Success after binutils/gcc/linux/g [...] new e432d438fa 183: onsuccess: #2270: 1: Success after binutils/gcc/linux/g [...] new 5484edc2fb 184: onsuccess: #2288: 1: Success after binutils/gcc/linux/g [...] new 18097a9d3e 185: onsuccess: #2290: 1: Success after binutils/gcc/linux/g [...] new 05a11a33bd 186: onsuccess: #2291: 1: Success after binutils/gcc/linux/g [...] new c63d7147cc 187: onsuccess: #2294: 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 (c3a83d104f) \ 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 1720 -> 1768 bytes 02-prepare_abe/console.log.xz | Bin 2744 -> 2752 bytes 03-build_abe-binutils/console.log.xz | Bin 30188 -> 31028 bytes 04-build_abe-stage1/console.log.xz | Bin 72632 -> 72624 bytes 05-clean_sysroot/console.log.xz | Bin 328 -> 328 bytes 06-build_abe-linux/console.log.xz | Bin 8696 -> 9104 bytes 07-build_abe-glibc/console.log.xz | Bin 239700 -> 239772 bytes 08-build_abe-stage2/console.log.xz | Bin 202784 -> 203672 bytes 09-build_abe-gdb/console.log.xz | Bin 37528 -> 37588 bytes 10-build_abe-qemu/console.log.xz | Bin 31728 -> 31888 bytes 11-build_abe-dejagnu/console.log.xz | Bin 3888 -> 3904 bytes 12-build_abe-check_gcc/console.log.xz | Bin 2600 -> 2800 bytes 13-check_regression/console.log.xz | Bin 11736 -> 13700 bytes 13-check_regression/extra-bisect-params | 2 +- 13-check_regression/fails.sum | 112 +- 13-check_regression/mail-body.txt | 198 +- 13-check_regression/results.compare | 134 +- 13-check_regression/results.compare2 | 884 +++-- 13-check_regression/results.regressions | 146 +- 14-update_baseline/console.log | 44 +- 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 | 200 +- mail/mail-subject.txt | 2 +- manifest.sh | 36 +- results | 146 +- sumfiles/g++.log.xz | Bin 3449744 -> 3432872 bytes sumfiles/g++.sum | 189 +- sumfiles/gcc.log.xz | Bin 3024396 -> 3047764 bytes sumfiles/gcc.sum | 6006 ++++++++++++++++--------------- sumfiles/gfortran.log.xz | Bin 1033272 -> 1040688 bytes sumfiles/gfortran.sum | 40 +- sumfiles/libatomic.log.xz | Bin 2292 -> 2288 bytes sumfiles/libatomic.sum | 4 +- sumfiles/libgomp.log.xz | Bin 204188 -> 204060 bytes sumfiles/libgomp.sum | 16 +- sumfiles/libitm.log.xz | Bin 2696 -> 2700 bytes sumfiles/libitm.sum | 6 +- sumfiles/libstdc++.log.xz | Bin 427452 -> 428104 bytes sumfiles/libstdc++.sum | 16 +- 44 files changed, 4426 insertions(+), 3767 deletions(-)