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 9a7763a29e 194: onsuccess: #2340: 1: Success after binutils/gcc/linux/g [...] discards 9a9aeea97c 193: onsuccess: #2339: 1: Success after binutils/gcc/glibc/g [...] discards 2d97b4bb4b 192: onsuccess: #2338: 1: Success after binutils/gcc/linux/g [...] discards c0eb63fe52 191: onsuccess: #2331: 1: Success after gcc/qemu: 90 commits discards 9bcf8a5ce2 190: onsuccess: #2330: 1: Success after binutils/gcc/linux/g [...] discards 8cbb817d5e 189: onsuccess: #2299: 1: Success after binutils/gcc/linux/g [...] discards fab2deb637 188: onsuccess: #2295: 1: Success after binutils/gcc/linux/g [...] discards dfa7e38206 187: onsuccess: #2294: 1: Success after binutils/gcc/linux/g [...] discards 1f85b82d2f 186: onsuccess: #2291: 1: Success after binutils/gcc/linux/g [...] discards fd18ec8514 185: onsuccess: #2290: 1: Success after binutils/gcc/linux/g [...] discards fe3a739cf0 184: onsuccess: #2288: 1: Success after binutils/gcc/linux/g [...] discards 64f7fcf5ef 183: onsuccess: #2270: 1: Success after binutils/gcc/linux/g [...] discards 2d4566aa9d 182: onsuccess: #2247: 1: Success after binutils/gcc/linux/g [...] discards a22d419e87 181: onsuccess: #2239: 1: Success after binutils/gcc/linux/g [...] discards abcf083357 180: onsuccess: #2232: 1: Success after binutils/gcc/glibc/g [...] discards d567df4bc3 179: onsuccess: #2230: 1: Success after binutils/gcc/linux/g [...] discards e52ab5bb2b 178: onsuccess: #2217: 1: Success after binutils/gcc/linux/g [...] discards 1064417e44 177: onsuccess: #2212: 1: Success after binutils/gdb: 2 commits discards b07190171c 176: onsuccess: #2211: 1: Success after binutils/gcc/linux/g [...] discards 7be9ac3a57 175: onsuccess: #2210: 1: Success after binutils/gcc/linux/g [...] discards e0f839c067 174: onsuccess: #2209: 1: Success after binutils/gcc/gdb: 20 [...] discards c26be0a397 173: onsuccess: #2208: 1: Success after gcc: 10 commits discards bed2e36ecd 172: onsuccess: #2207: 1: Success after binutils/gcc/linux/g [...] discards e3848bf51c 171: onsuccess: #2206: 1: Success after binutils/gcc/linux/g [...] discards 178020aaa9 170: onsuccess: #2205: 1: Success after binutils/gcc/glibc/g [...] discards 7519e4e286 169: onsuccess: #2204: 1: Success after binutils/gcc/glibc/g [...] discards e24373d23f 168: onsuccess: #2203: 1: Success after binutils/gcc/glibc/g [...] discards be72573c7f 167: onsuccess: #2202: 1: Success after gcc/linux/glibc/qemu [...] discards cd1e9220af 166: onsuccess: #2201: 1: Success after gcc/glibc/qemu: 40 commits discards dcda4d2145 165: onsuccess: #2200: 1: Success after binutils/gdb: 8 commits discards 868647e01b 164: onsuccess: #2199: 1: Success after binutils/gcc/linux/g [...] discards fd416ef4f7 163: onsuccess: #2198: 1: Success after binutils/gcc/linux/g [...] discards b3819a2c1b 162: onsuccess: #2197: 1: Success after binutils/gcc/glibc/g [...] discards a5fe1ce939 161: onsuccess: #2196: 1: Success after binutils/gcc/linux/g [...] discards 317d076e09 160: onsuccess: #2195: 1: Success after binutils/gcc/linux/g [...] discards 46c6374989 159: onsuccess: #2194: 1: Success after gcc/linux/glibc: 197 [...] discards bd49d6be24 158: onsuccess: #2193: 1: Success after binutils/gcc/glibc/g [...] discards ec8a8d8309 157: onsuccess: #2192: 1: Success after binutils/gcc/gdb: 8 commits discards 3c1df4d678 156: onsuccess: #2191: 1: Success after binutils/gcc/linux/g [...] discards 6f46652e93 155: onsuccess: #2190: 1: Success after binutils/gcc/linux/g [...] discards bc9c0ac962 154: onsuccess: #2189: 1: Success after binutils/gcc/gdb: 18 [...] discards 8e5a65d925 153: onsuccess: #2188: 1: Success after binutils/gcc/gdb: 3 commits discards 6d2c3b33c9 152: onsuccess: #2187: 1: Success after gcc/linux/glibc: 22 commits discards 55dd5d02ce 151: onsuccess: #2186: 1: Success after gcc: 2 commits discards ab4bbe8507 150: onsuccess: #2185: 1: Success after gcc: 3 commits discards c1af24965c 149: onsuccess: #2184: 1: Success after binutils/gcc/linux/g [...] discards 9ec63d90b0 148: onsuccess: #2183: 1: Success after gcc/linux/glibc: 64 commits discards 48205e36de 147: onsuccess: #2182: 1: Success after binutils/gcc/gdb: 18 [...] discards 9602db36e4 146: onsuccess: #2181: 1: Success after binutils/glibc/gdb: [...] discards 0104aa06bb 145: onsuccess: #2180: 1: Success after binutils/gcc/linux/g [...] discards da111a9328 144: onsuccess: #2179: 1: Success after binutils/gcc/linux/g [...] discards 47cfb2300a 143: onsuccess: #2178: 1: Success after binutils/gcc/gdb/qem [...] discards 8e4429a17d 142: onsuccess: #2177: 1: Success after gcc/glibc: 4 commits discards ae4f3817fd 141: onsuccess: #2176: 1: Success after binutils/gcc/gdb: 6 commits discards 376cfa452e 140: onsuccess: #2175: 1: Success after binutils/gcc/linux/g [...] discards 1abd351ce1 139: onsuccess: #2174: 1: Success after binutils/gcc/gdb: 13 [...] discards 6f96f3ce5c 138: onsuccess: #2173: 1: Success after binutils/gcc/gdb: 5 commits discards d47bdf4592 137: onsuccess: #2172: 1: Success after binutils/gcc/linux/g [...] discards 65a152a6d9 136: onsuccess: #2171: 1: Success after binutils/gcc/gdb/qem [...] discards 7651c2d19c 135: onsuccess: #2170: 1: Success after gcc/linux/qemu: 63 commits discards 5b25a70136 134: onsuccess: #2169: 1: Success after binutils/gcc/gdb: 13 [...] discards 8dc16d01b0 133: onsuccess: #2168: 1: Success after binutils/gcc/linux/g [...] discards ae6e229e46 132: onsuccess: #2167: 1: Success after binutils/gcc/glibc/g [...] discards 101dd70ad6 131: onsuccess: #2166: 1: Success after binutils/gcc/gdb: 12 [...] discards 5a82e32fbc 130: onsuccess: #2165: 1: Success after binutils/gcc/gdb: 32 [...] discards 50bf51f8e7 129: onsuccess: #2164: 1: Success after binutils/gcc/linux/g [...] discards 21b7685705 128: onsuccess: #2163: 1: Success after linux: 23 commits discards 11ffa78f87 127: onsuccess: #2162: 1: Success after gcc: 9 commits discards ccfa525b1a 126: onsuccess: #2161: 1: Success after basepoints/gcc-13-28 [...] discards 102b9127c1 125: onsuccess: #2160: 1: Success after binutils/gcc/linux/g [...] discards b5441d9dea 124: onsuccess: #2159: 1: Success after linux: 23 commits discards d3f0a6e077 123: onsuccess: #2158: 1: Success after basepoints/gcc-13-28 [...] discards b5109302ca 122: onsuccess: #2157: 1: Success after binutils/gcc/gdb: 6 commits discards dfa70e6b5b 121: onsuccess: #2156: 1: Success after binutils/gcc/linux/g [...] discards f590661cbe 120: onsuccess: #2155: 1: Success after binutils/gcc/linux/g [...] discards 8621eaf1b8 119: onsuccess: #2154: 1: Success after binutils/gcc/linux/g [...] discards 77a5d556da 118: onsuccess: #2151: 1: Success after binutils/gcc/linux/g [...] discards 15bb5877a7 117: onsuccess: #2150: 1: Success after binutils/gcc/glibc/g [...] discards 009e884d94 116: onsuccess: #2148: 1: Success after binutils/gcc/gdb: 7 commits discards 696e4d22b6 115: onsuccess: #2147: 1: Success after binutils/linux/glibc [...] discards 9b373419a5 114: onsuccess: #2146: 1: Success after binutils/gcc/glibc/g [...] discards e876a9e3e2 113: onsuccess: #2145: 1: Success after binutils/gcc/glibc/g [...] discards 5328992e80 112: onsuccess: #2144: 1: Success after binutils/gcc/glibc/g [...] discards 64fe88a5d6 111: onsuccess: #2143: 1: Success after binutils/gcc/linux/g [...] discards 6ba57d5494 110: onsuccess: #2142: 1: Success after binutils/gcc/glibc/g [...] discards b761726144 109: onsuccess: #2141: 1: Success after gcc/glibc: 6 commits discards 5ae8c27357 108: onsuccess: #2140: 1: Success after binutils/gcc/gdb: 5 commits discards 104643915b 107: onsuccess: #2139: 1: Success after binutils/gcc/gdb: 3 commits discards 20a912e214 106: onsuccess: #2138: 1: Success after binutils/gcc/glibc/g [...] discards 034c5627d5 105: onsuccess: #2137: 1: Success after basepoints/gcc-13-27 [...] discards b52378b229 104: onsuccess: #2136: 1: Success after binutils/gcc/gdb: 3 commits discards 0fc8e0b7d3 103: onsuccess: #2135: 1: Success after gcc/linux/glibc/gdb/ [...] discards e8ab902fa4 102: onsuccess: #2133: 1: Success after gdb-12-branchpoint-1 [...] discards e2a8f4e23b 101: onsuccess: #2130: 1: Success after binutils: 81 commits discards 1cb30b23d8 100: onsuccess: #2077: 1: Success after binutils/gcc/linux/g [...] discards ab30ef32b2 99: onsuccess: #2074: 1: Success after baseline build: no ne [...] discards be0d794740 98: onsuccess: #2073: 1: Success after gcc/linux: 11 commits discards 75eb3e4a1b 97: onsuccess: #2072: 1: Success after binutils/gcc/gdb: 3 commits discards 56b33d4718 96: onsuccess: #2071: 1: Success after gcc/linux: 56 commits discards 5b60c79a3f 95: onsuccess: #2070: 1: Success after basepoints/gcc-13-238 [...] discards f40ae1927d 94: onsuccess: 1: Success after gcc: openmp: Partial OpenMP [...] new f690d442ea 94: onsuccess: 1: Success after gcc: openmp: Partial OpenMP [...] new 9e8c62db13 95: onsuccess: #2070: 1: Success after basepoints/gcc-13-238 [...] new 9d26ee0fed 96: onsuccess: #2071: 1: Success after gcc/linux: 56 commits new 63c326f01c 97: onsuccess: #2072: 1: Success after binutils/gcc/gdb: 3 commits new 9754adffbe 98: onsuccess: #2073: 1: Success after gcc/linux: 11 commits new a5ea7f91e0 99: onsuccess: #2074: 1: Success after baseline build: no ne [...] new ecd697ad0f 100: onsuccess: #2077: 1: Success after binutils/gcc/linux/g [...] new ef5fb32526 101: onsuccess: #2130: 1: Success after binutils: 81 commits new f08f90154c 102: onsuccess: #2133: 1: Success after gdb-12-branchpoint-1 [...] new bbfaa50182 103: onsuccess: #2135: 1: Success after gcc/linux/glibc/gdb/ [...] new d509ad5f53 104: onsuccess: #2136: 1: Success after binutils/gcc/gdb: 3 commits new 374a6655e6 105: onsuccess: #2137: 1: Success after basepoints/gcc-13-27 [...] new eef7726585 106: onsuccess: #2138: 1: Success after binutils/gcc/glibc/g [...] new a8a077c7c2 107: onsuccess: #2139: 1: Success after binutils/gcc/gdb: 3 commits new 3a680f75d2 108: onsuccess: #2140: 1: Success after binutils/gcc/gdb: 5 commits new 00d9d29cdb 109: onsuccess: #2141: 1: Success after gcc/glibc: 6 commits new aef91621f9 110: onsuccess: #2142: 1: Success after binutils/gcc/glibc/g [...] new d9851baf47 111: onsuccess: #2143: 1: Success after binutils/gcc/linux/g [...] new 0914341f1c 112: onsuccess: #2144: 1: Success after binutils/gcc/glibc/g [...] new 8f21935884 113: onsuccess: #2145: 1: Success after binutils/gcc/glibc/g [...] new 6a2e42df33 114: onsuccess: #2146: 1: Success after binutils/gcc/glibc/g [...] new 327b1f867c 115: onsuccess: #2147: 1: Success after binutils/linux/glibc [...] new 9962f503ac 116: onsuccess: #2148: 1: Success after binutils/gcc/gdb: 7 commits new 51acf8a0e3 117: onsuccess: #2150: 1: Success after binutils/gcc/glibc/g [...] new 14aade8eb0 118: onsuccess: #2151: 1: Success after binutils/gcc/linux/g [...] new 0e4b1ff2a5 119: onsuccess: #2154: 1: Success after binutils/gcc/linux/g [...] new 9bf7c6dbe5 120: onsuccess: #2155: 1: Success after binutils/gcc/linux/g [...] new c06abd080f 121: onsuccess: #2156: 1: Success after binutils/gcc/linux/g [...] new df85d3a8fa 122: onsuccess: #2157: 1: Success after binutils/gcc/gdb: 6 commits new d5a63884d8 123: onsuccess: #2158: 1: Success after basepoints/gcc-13-28 [...] new c8c313b90a 124: onsuccess: #2159: 1: Success after linux: 23 commits new 03c9dce30a 125: onsuccess: #2160: 1: Success after binutils/gcc/linux/g [...] new 9193345d7b 126: onsuccess: #2161: 1: Success after basepoints/gcc-13-28 [...] new edfaebb6ea 127: onsuccess: #2162: 1: Success after gcc: 9 commits new 6df618e17b 128: onsuccess: #2163: 1: Success after linux: 23 commits new ca13c7f321 129: onsuccess: #2164: 1: Success after binutils/gcc/linux/g [...] new 097eb542d0 130: onsuccess: #2165: 1: Success after binutils/gcc/gdb: 32 [...] new 5c6cc54e58 131: onsuccess: #2166: 1: Success after binutils/gcc/gdb: 12 [...] new 88d9501fda 132: onsuccess: #2167: 1: Success after binutils/gcc/glibc/g [...] new 14363d8269 133: onsuccess: #2168: 1: Success after binutils/gcc/linux/g [...] new 8960c89f94 134: onsuccess: #2169: 1: Success after binutils/gcc/gdb: 13 [...] new fd9b6aa26d 135: onsuccess: #2170: 1: Success after gcc/linux/qemu: 63 commits new 17f35497cc 136: onsuccess: #2171: 1: Success after binutils/gcc/gdb/qem [...] new 917c486505 137: onsuccess: #2172: 1: Success after binutils/gcc/linux/g [...] new 5d86ea00a2 138: onsuccess: #2173: 1: Success after binutils/gcc/gdb: 5 commits new 7b9cb4e7db 139: onsuccess: #2174: 1: Success after binutils/gcc/gdb: 13 [...] new 5fd543ed00 140: onsuccess: #2175: 1: Success after binutils/gcc/linux/g [...] new e8680df484 141: onsuccess: #2176: 1: Success after binutils/gcc/gdb: 6 commits new 48284fbd6b 142: onsuccess: #2177: 1: Success after gcc/glibc: 4 commits new 5fd9080521 143: onsuccess: #2178: 1: Success after binutils/gcc/gdb/qem [...] new 1399663b25 144: onsuccess: #2179: 1: Success after binutils/gcc/linux/g [...] new af1d11b916 145: onsuccess: #2180: 1: Success after binutils/gcc/linux/g [...] new 0d0e5bec9e 146: onsuccess: #2181: 1: Success after binutils/glibc/gdb: [...] new 4dd399de1a 147: onsuccess: #2182: 1: Success after binutils/gcc/gdb: 18 [...] new cece0c6f3b 148: onsuccess: #2183: 1: Success after gcc/linux/glibc: 64 commits new 9fd3efcf0f 149: onsuccess: #2184: 1: Success after binutils/gcc/linux/g [...] new c46072d750 150: onsuccess: #2185: 1: Success after gcc: 3 commits new 00a15426f3 151: onsuccess: #2186: 1: Success after gcc: 2 commits new 8c9ee7f523 152: onsuccess: #2187: 1: Success after gcc/linux/glibc: 22 commits new 7bd570a11a 153: onsuccess: #2188: 1: Success after binutils/gcc/gdb: 3 commits new 64d69ddada 154: onsuccess: #2189: 1: Success after binutils/gcc/gdb: 18 [...] new 7cad52ec33 155: onsuccess: #2190: 1: Success after binutils/gcc/linux/g [...] new 01ffdcf033 156: onsuccess: #2191: 1: Success after binutils/gcc/linux/g [...] new 0e92fd7ce1 157: onsuccess: #2192: 1: Success after binutils/gcc/gdb: 8 commits new edfdacb7de 158: onsuccess: #2193: 1: Success after binutils/gcc/glibc/g [...] new 07ec8fa71b 159: onsuccess: #2194: 1: Success after gcc/linux/glibc: 197 [...] new 2f62562e74 160: onsuccess: #2195: 1: Success after binutils/gcc/linux/g [...] new 3d754f3f5f 161: onsuccess: #2196: 1: Success after binutils/gcc/linux/g [...] new c68740fd53 162: onsuccess: #2197: 1: Success after binutils/gcc/glibc/g [...] new 409898a247 163: onsuccess: #2198: 1: Success after binutils/gcc/linux/g [...] new 1d0cc11f92 164: onsuccess: #2199: 1: Success after binutils/gcc/linux/g [...] new eaadb00d2b 165: onsuccess: #2200: 1: Success after binutils/gdb: 8 commits new 50356d4c47 166: onsuccess: #2201: 1: Success after gcc/glibc/qemu: 40 commits new 9206980048 167: onsuccess: #2202: 1: Success after gcc/linux/glibc/qemu [...] new b829d22719 168: onsuccess: #2203: 1: Success after binutils/gcc/glibc/g [...] new 1753d30c26 169: onsuccess: #2204: 1: Success after binutils/gcc/glibc/g [...] new d908f480a9 170: onsuccess: #2205: 1: Success after binutils/gcc/glibc/g [...] new 6c62ff0ff4 171: onsuccess: #2206: 1: Success after binutils/gcc/linux/g [...] new bb37b4c8f9 172: onsuccess: #2207: 1: Success after binutils/gcc/linux/g [...] new f978795607 173: onsuccess: #2208: 1: Success after gcc: 10 commits new e71cfe9ce5 174: onsuccess: #2209: 1: Success after binutils/gcc/gdb: 20 [...] new c878692f2d 175: onsuccess: #2210: 1: Success after binutils/gcc/linux/g [...] new c644b98807 176: onsuccess: #2211: 1: Success after binutils/gcc/linux/g [...] new 9bfc56f449 177: onsuccess: #2212: 1: Success after binutils/gdb: 2 commits new 59ad96262a 178: onsuccess: #2217: 1: Success after binutils/gcc/linux/g [...] new faa347d16c 179: onsuccess: #2230: 1: Success after binutils/gcc/linux/g [...] new 96ba924266 180: onsuccess: #2232: 1: Success after binutils/gcc/glibc/g [...] new 0e1c9d4ad0 181: onsuccess: #2239: 1: Success after binutils/gcc/linux/g [...] new 4c8fe84a19 182: onsuccess: #2247: 1: Success after binutils/gcc/linux/g [...] new 71c00032e1 183: onsuccess: #2270: 1: Success after binutils/gcc/linux/g [...] new a5a2509bd0 184: onsuccess: #2288: 1: Success after binutils/gcc/linux/g [...] new 37740556da 185: onsuccess: #2290: 1: Success after binutils/gcc/linux/g [...] new 0e3abd2589 186: onsuccess: #2291: 1: Success after binutils/gcc/linux/g [...] new 5b3f609a8b 187: onsuccess: #2294: 1: Success after binutils/gcc/linux/g [...] new d6560c2512 188: onsuccess: #2295: 1: Success after binutils/gcc/linux/g [...] new 5087171931 189: onsuccess: #2299: 1: Success after binutils/gcc/linux/g [...] new c43c4e465a 190: onsuccess: #2330: 1: Success after binutils/gcc/linux/g [...] new 798796adea 191: onsuccess: #2331: 1: Success after gcc/qemu: 90 commits new 9a677a9e24 192: onsuccess: #2338: 1: Success after binutils/gcc/linux/g [...] new aed67338a3 193: onsuccess: #2339: 1: Success after binutils/gcc/glibc/g [...] new 49ec0a81f7 194: onsuccess: #2340: 1: Success after binutils/gcc/linux/g [...] new 2f2bec6cfe 195: onsuccess: #2341: 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 (9a7763a29e) \ 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 1752 -> 1700 bytes 02-prepare_abe/console.log.xz | Bin 2736 -> 2744 bytes 03-build_abe-binutils/console.log.xz | Bin 30440 -> 30484 bytes 04-build_abe-stage1/console.log.xz | Bin 72896 -> 71712 bytes 06-build_abe-linux/console.log.xz | Bin 8872 -> 9684 bytes 07-build_abe-glibc/console.log.xz | Bin 244344 -> 243868 bytes 08-build_abe-stage2/console.log.xz | Bin 204456 -> 202748 bytes 09-build_abe-gdb/console.log.xz | Bin 38896 -> 37892 bytes 10-build_abe-qemu/console.log.xz | Bin 31880 -> 31316 bytes 11-build_abe-dejagnu/console.log.xz | Bin 3928 -> 3884 bytes 12-build_abe-check_gcc/console.log.xz | Bin 4140 -> 3060 bytes 13-check_regression/console.log.xz | Bin 7404 -> 6512 bytes 13-check_regression/extra-bisect-params | 2 +- 13-check_regression/fails.sum | 7 +- 13-check_regression/mail-body.txt | 77 +- 13-check_regression/results.compare | 36 +- 13-check_regression/results.compare2 | 116 +- 13-check_regression/results.regressions | 36 +- 14-update_baseline/console.log | 64 +- 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 | 79 +- mail/mail-subject.txt | 2 +- manifest.sh | 38 +- results | 36 +- sumfiles/g++.log.xz | Bin 3421792 -> 3425084 bytes sumfiles/g++.sum | 55 +- sumfiles/gcc.log.xz | Bin 3049496 -> 3032464 bytes sumfiles/gcc.sum | 4150 +++++++++++++++---------------- sumfiles/gfortran.log.xz | Bin 1036444 -> 1032044 bytes sumfiles/gfortran.sum | 6 +- sumfiles/libatomic.log.xz | Bin 2292 -> 2288 bytes sumfiles/libatomic.sum | 2 +- sumfiles/libgomp.log.xz | Bin 213572 -> 213624 bytes sumfiles/libgomp.sum | 2 +- sumfiles/libitm.log.xz | Bin 2696 -> 2692 bytes sumfiles/libitm.sum | 2 +- sumfiles/libstdc++.log.xz | Bin 433504 -> 426532 bytes sumfiles/libstdc++.sum | 6 +- 43 files changed, 2382 insertions(+), 2346 deletions(-)