Tcwg-commits November 2022

tcwg-commits@lists.linaro.org

5 participants
4683 discussions

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_gcc_check/master-aarch64 updated (a948d8b0f9 -> 772b216737)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. tcwg-buildslave pushed a change to branch linaro-local/ci/tcwg_gcc_check/master-aarch64 in repository toolchain/ci/base-artifacts. discards a948d8b0f9 345: onsuccess: #2301: 1: Success after binutils/gcc: 5 commits discards 77d5d7cd90 344: onsuccess: #2300: 1: Success after binutils/gcc: 10 commits discards 55f8365a87 343: onsuccess: #2299: 1: Success after binutils/gcc: 18 commits discards ffafb2fc31 342: onsuccess: #2298: 1: Success after binutils/gcc: 17 commits discards 38b38ce4bd 341: onsuccess: #2297: 1: Success after binutils/gcc: 7 commits discards f2426833cc 340: onsuccess: #2296: 1: Success after gcc: 3 commits discards d88ca43e39 339: onsuccess: #2295: 1: Success after binutils/gcc: 18 commits discards d584d91502 338: onsuccess: #2294: 1: Success after binutils/gcc: 13 commits discards 7c92a21927 337: onsuccess: #2293: 1: Success after gcc: 21 commits discards 28ef99dd04 336: onsuccess: #2292: 1: Success after binutils/gcc: 3 commits discards faa45fa0ee 335: onsuccess: #2291: 1: Success after binutils/gcc: 3 commits discards 5686243bdc 334: onsuccess: #2290: 1: Success after binutils/gcc: 5 commits discards 23a13e8bac 333: onsuccess: #2289: 1: Success after basepoints/gcc-13-41 [...] discards 96cf88b807 332: onsuccess: #2288: 1: Success after gcc: 2 commits discards 8d51c6f9c0 331: onsuccess: #2287: 1: Success after gdb-12-branchpoint-2 [...] discards 484777bcba 330: onsuccess: #2286: 1: Success after binutils/gcc: 8 commits discards 485d1716d7 329: onsuccess: #2285: 1: Success after gcc: 8 commits discards d9c71cf1e1 328: onsuccess: #2283: 1: Success after gdb-12-branchpoint-2 [...] discards 1c2a6f31f1 327: onsuccess: #2281: 1: Success after binutils/gcc: 14 commits discards 83a96b6ce5 326: onsuccess: #2280: 1: Success after binutils/gcc: 10 commits discards dfb046107c 325: onsuccess: #2279: 1: Success after binutils/gcc: 13 commits discards 090df96ea2 324: onsuccess: #2278: 1: Success after binutils/gcc: 4 commits discards c47da8f449 323: onsuccess: #2277: 1: Success after binutils/gcc: 5 commits discards 5f72823052 322: onsuccess: #2276: 1: Success after binutils/gcc: 15 commits discards 070a9f8b1f 321: onsuccess: #2275: 1: Success after binutils/gcc: 12 commits discards b936a812b7 320: onsuccess: #2274: 1: Success after gcc: 5 commits discards 794b7924c1 319: onsuccess: #2273: 1: Success after binutils/gcc: 15 commits discards a3d3955628 318: onsuccess: #2272: 1: Success after binutils/gcc: 22 commits discards 50b810c7f0 317: onsuccess: #2271: 1: Success after binutils/gcc: 8 commits discards d80632ae65 316: onsuccess: #2270: 1: Success after gcc: 2 commits discards c671cc7567 315: onsuccess: #2269: 1: Success after binutils/gcc: 17 commits discards f07e947d7d 314: onsuccess: #2268: 1: Success after binutils/gcc: 101 commits discards 980d76cd87 313: onsuccess: #2267: 1: Success after binutils/gcc: 90 commits discards 982c1f03dd 312: onsuccess: #2265: 1: Success after binutils: 2 commits discards 160124c8b4 311: onsuccess: #2262: 1: Success after gdb-12-branchpoint-2 [...] discards e6fbc29926 310: onsuccess: #2259: 1: Success after binutils: 2 commits discards ba55fc8960 309: onsuccess: #2255: 1: Success after gdb-12-branchpoint-2 [...] discards 0a544d270d 308: onsuccess: #2252: 1: Success after gdb-12-branchpoint-2 [...] discards aa6fe2d94b 307: onsuccess: #2249: 1: Success after gdb-12-branchpoint-2 [...] discards c10482a37b 306: onsuccess: #2246: 1: Success after gdb-12-branchpoint-2 [...] discards 6977832290 305: onsuccess: #2244: 1: Success after binutils/gcc: 8 commits discards ff4c7f0446 304: onsuccess: #2243: 1: Success after binutils/gcc: 23 commits discards 45acbbcde4 303: onsuccess: #2242: 1: Success after binutils/gcc: 17 commits discards ab9e8ea1be 302: onsuccess: #2241: 1: Success after binutils/gcc: 10 commits discards 6d8c09f302 301: onsuccess: #2240: 1: Success after binutils/gcc: 10 commits discards 59b3039d56 300: onsuccess: #2239: 1: Success after binutils/gcc: 20 commits discards 68fb9b6b8f 299: onsuccess: #2238: 1: Success after binutils/gcc: 12 commits discards 1da8fb6771 298: onsuccess: #2237: 1: Success after binutils/gcc: 9 commits discards 031cb20b3e 297: onsuccess: #2236: 1: Success after binutils/gcc: 9 commits discards 1e2fda520a 296: onsuccess: #2235: 1: Success after binutils/gcc: 14 commits discards 85bdb7d6f5 295: onsuccess: #2234: 1: Success after binutils/gcc: 33 commits discards 5bb47d23fb 294: onsuccess: #2233: 1: Success after binutils/gcc: 4 commits discards 4dbe9a59d1 293: onsuccess: #2232: 1: Success after binutils/gcc: 5 commits discards c8cda269ff 292: onsuccess: #2231: 1: Success after binutils/gcc: 19 commits discards 97f0297c96 291: onsuccess: #2230: 1: Success after binutils/gcc: 31 commits discards 4b46ba6fa3 290: onsuccess: #2229: 1: Success after binutils/gcc: 12 commits discards 35ca5a1402 289: onsuccess: #2228: 1: Success after binutils/gcc: 11 commits discards 36afb53a4e 288: onsuccess: #2227: 1: Success after binutils/gcc: 16 commits discards 174f61fac7 287: onsuccess: #2226: 1: Success after binutils/gcc: 38 commits discards b270b1796b 286: onsuccess: #2225: 1: Success after binutils/gcc: 7 commits discards 24bf655bda 285: onsuccess: #2224: 1: Success after binutils/gcc: 2 commits discards b5f87b10dd 284: onsuccess: #2223: 1: Success after binutils/gcc: 5 commits discards 5058bbd028 283: onsuccess: #2222: 1: Success after gcc: 4 commits discards 6e17e912d7 282: onsuccess: #2221: 1: Success after gcc: 2 commits discards da83fff9e8 281: onsuccess: #2220: 1: Success after binutils/gcc: 4 commits discards 83bbea7cc4 280: onsuccess: #2219: 1: Success after binutils/gcc: 10 commits discards 2c0c8f9b90 279: onsuccess: #2218: 1: Success after basepoints/gcc-13-36 [...] discards 4f28e3fb31 278: onsuccess: #2217: 1: Success after binutils: 7 commits discards 360eef972c 277: onsuccess: #2216: 1: Success after binutils: 2 commits discards f0ed860f30 276: onsuccess: #2215: 1: Success after binutils/gcc: 44 commits discards c1277f67f6 275: onsuccess: #2214: 1: Success after binutils/gcc: 14 commits discards 522be8dac0 274: onsuccess: #2213: 1: Success after binutils/gcc: 12 commits discards dff63618d8 273: onsuccess: #2212: 1: Success after binutils/gcc: 13 commits discards 06f5cf58cf 272: onsuccess: #2211: 1: Success after binutils/gcc: 19 commits discards b4fa053351 271: onsuccess: #2210: 1: Success after binutils/gcc: 8 commits discards 57ba8bc336 270: onsuccess: #2209: 1: Success after gcc: 2 commits discards 8b47aac761 269: onsuccess: #2208: 1: Success after binutils/gcc: 8 commits discards 18e5431810 268: onsuccess: #2207: 1: Success after binutils/gcc: 12 commits discards e37029dabc 267: onsuccess: #2206: 1: Success after binutils/gcc: 5 commits discards bc335d900d 266: onsuccess: #2205: 1: Success after binutils/gcc: 8 commits discards 8c83d3ea89 265: onsuccess: #2204: 1: Success after binutils/gcc: 5 commits discards bfc5680532 264: onsuccess: #2203: 1: Success after gcc: 9 commits discards 43f5114e17 263: onsuccess: #2202: 1: Success after binutils/gcc: 5 commits discards e39db19367 262: onsuccess: #2201: 1: Success after gcc: 6 commits discards 49b80f8796 261: onsuccess: #2200: 1: Success after binutils/gcc: 8 commits discards 8a8f7ae962 260: onsuccess: #2199: 1: Success after binutils/gcc: 18 commits discards e372ec5800 259: onsuccess: #2198: 1: Success after binutils/gcc: 8 commits discards f255fded99 258: onsuccess: #2197: 1: Success after binutils/gcc: 5 commits discards beab8989c8 257: onsuccess: #2196: 1: Success after binutils/gcc: 2 commits discards 0dabe30118 256: onsuccess: #2195: 1: Success after gdb-12-branchpoint-2 [...] discards 36ab4d381f 255: onsuccess: #2194: 1: Success after basepoints/gcc-13-35 [...] discards fce8da0c6b 254: onsuccess: #2193: 1: Success after gdb-12-branchpoint-2 [...] discards 1295e47eef 253: onsuccess: #2192: 1: Success after gdb-12-branchpoint-2 [...] discards de9c5fe315 252: onsuccess: #2191: 1: Success after binutils/gcc: 29 commits discards b5a70adbc8 251: onsuccess: #2188: 1: Success after binutils/gcc: 11 commits discards 281c8eb037 250: onsuccess: #2187: 1: Success after binutils/gcc: 10 commits discards 0ac4454b25 249: onsuccess: #2186: 1: Success after binutils/gcc: 7 commits discards 1c6e23a9b4 248: onsuccess: #2185: 1: Success after binutils/gcc: 7 commits discards dab80d4ac3 247: onsuccess: #2184: 1: Success after binutils/gcc: 7 commits discards cbe2a3cca9 246: onsuccess: #2183: 1: Success after binutils/gcc: 8 commits discards 174a5a30d9 245: onsuccess: #2182: 1: Success after binutils/gcc: 6 commits new deb7c19b87 245: onsuccess: #2182: 1: Success after binutils/gcc: 6 commits new 14cd5fc953 246: onsuccess: #2183: 1: Success after binutils/gcc: 8 commits new af2fc4384d 247: onsuccess: #2184: 1: Success after binutils/gcc: 7 commits new 5053c1c2ca 248: onsuccess: #2185: 1: Success after binutils/gcc: 7 commits new b3fe32fd15 249: onsuccess: #2186: 1: Success after binutils/gcc: 7 commits new 68580e7927 250: onsuccess: #2187: 1: Success after binutils/gcc: 10 commits new 2bf374dc5c 251: onsuccess: #2188: 1: Success after binutils/gcc: 11 commits new cf8dc4573b 252: onsuccess: #2191: 1: Success after binutils/gcc: 29 commits new 1f799c5efd 253: onsuccess: #2192: 1: Success after gdb-12-branchpoint-2 [...] new e098b00b8c 254: onsuccess: #2193: 1: Success after gdb-12-branchpoint-2 [...] new c4ad8a9f50 255: onsuccess: #2194: 1: Success after basepoints/gcc-13-35 [...] new 01220df4e4 256: onsuccess: #2195: 1: Success after gdb-12-branchpoint-2 [...] new c8507987a3 257: onsuccess: #2196: 1: Success after binutils/gcc: 2 commits new c027a74c33 258: onsuccess: #2197: 1: Success after binutils/gcc: 5 commits new 149fdf27ee 259: onsuccess: #2198: 1: Success after binutils/gcc: 8 commits new fdc1f5a124 260: onsuccess: #2199: 1: Success after binutils/gcc: 18 commits new e4bebc0e65 261: onsuccess: #2200: 1: Success after binutils/gcc: 8 commits new 4bdfeb4aad 262: onsuccess: #2201: 1: Success after gcc: 6 commits new a6ffb5992d 263: onsuccess: #2202: 1: Success after binutils/gcc: 5 commits new 7d8de25532 264: onsuccess: #2203: 1: Success after gcc: 9 commits new f77b7d508d 265: onsuccess: #2204: 1: Success after binutils/gcc: 5 commits new 265b8af9a8 266: onsuccess: #2205: 1: Success after binutils/gcc: 8 commits new 6e76aa4d19 267: onsuccess: #2206: 1: Success after binutils/gcc: 5 commits new 56f8da63a3 268: onsuccess: #2207: 1: Success after binutils/gcc: 12 commits new 0afd46e6d0 269: onsuccess: #2208: 1: Success after binutils/gcc: 8 commits new ccecd83d6c 270: onsuccess: #2209: 1: Success after gcc: 2 commits new 0e992759e4 271: onsuccess: #2210: 1: Success after binutils/gcc: 8 commits new 5fb2130ff0 272: onsuccess: #2211: 1: Success after binutils/gcc: 19 commits new 6650744e08 273: onsuccess: #2212: 1: Success after binutils/gcc: 13 commits new bbd01beba3 274: onsuccess: #2213: 1: Success after binutils/gcc: 12 commits new 2acd7021ab 275: onsuccess: #2214: 1: Success after binutils/gcc: 14 commits new 5459f5fa61 276: onsuccess: #2215: 1: Success after binutils/gcc: 44 commits new dc9b9a9f31 277: onsuccess: #2216: 1: Success after binutils: 2 commits new 3d89e2c7a2 278: onsuccess: #2217: 1: Success after binutils: 7 commits new 6e78f26080 279: onsuccess: #2218: 1: Success after basepoints/gcc-13-36 [...] new 9bfe6f2943 280: onsuccess: #2219: 1: Success after binutils/gcc: 10 commits new 28fa014c0a 281: onsuccess: #2220: 1: Success after binutils/gcc: 4 commits new af10fd43c8 282: onsuccess: #2221: 1: Success after gcc: 2 commits new 04b20c15e7 283: onsuccess: #2222: 1: Success after gcc: 4 commits new 647f944fb7 284: onsuccess: #2223: 1: Success after binutils/gcc: 5 commits new 2fa1b6e02d 285: onsuccess: #2224: 1: Success after binutils/gcc: 2 commits new 79683ac2d0 286: onsuccess: #2225: 1: Success after binutils/gcc: 7 commits new b3398f0d9d 287: onsuccess: #2226: 1: Success after binutils/gcc: 38 commits new 40f22abd34 288: onsuccess: #2227: 1: Success after binutils/gcc: 16 commits new d181e4b396 289: onsuccess: #2228: 1: Success after binutils/gcc: 11 commits new 1cf64e9f03 290: onsuccess: #2229: 1: Success after binutils/gcc: 12 commits new cc653d0d7e 291: onsuccess: #2230: 1: Success after binutils/gcc: 31 commits new 66c9a5d39f 292: onsuccess: #2231: 1: Success after binutils/gcc: 19 commits new df0e46f82c 293: onsuccess: #2232: 1: Success after binutils/gcc: 5 commits new 74a755eaa7 294: onsuccess: #2233: 1: Success after binutils/gcc: 4 commits new 68f7b39ef1 295: onsuccess: #2234: 1: Success after binutils/gcc: 33 commits new dde2a13fdd 296: onsuccess: #2235: 1: Success after binutils/gcc: 14 commits new 9b73040cd0 297: onsuccess: #2236: 1: Success after binutils/gcc: 9 commits new 3e9adb575a 298: onsuccess: #2237: 1: Success after binutils/gcc: 9 commits new 1f3fb5e5dd 299: onsuccess: #2238: 1: Success after binutils/gcc: 12 commits new 017315fdab 300: onsuccess: #2239: 1: Success after binutils/gcc: 20 commits new b01191da48 301: onsuccess: #2240: 1: Success after binutils/gcc: 10 commits new d18c72db41 302: onsuccess: #2241: 1: Success after binutils/gcc: 10 commits new e9fde0da21 303: onsuccess: #2242: 1: Success after binutils/gcc: 17 commits new 2819cc065c 304: onsuccess: #2243: 1: Success after binutils/gcc: 23 commits new 3bc82fecc1 305: onsuccess: #2244: 1: Success after binutils/gcc: 8 commits new 5918ce4d43 306: onsuccess: #2246: 1: Success after gdb-12-branchpoint-2 [...] new 4efb6026bb 307: onsuccess: #2249: 1: Success after gdb-12-branchpoint-2 [...] new 4e449ff91d 308: onsuccess: #2252: 1: Success after gdb-12-branchpoint-2 [...] new a3c661ea2b 309: onsuccess: #2255: 1: Success after gdb-12-branchpoint-2 [...] new d96c2662f2 310: onsuccess: #2259: 1: Success after binutils: 2 commits new 33c2a9d301 311: onsuccess: #2262: 1: Success after gdb-12-branchpoint-2 [...] new ec1f52d93e 312: onsuccess: #2265: 1: Success after binutils: 2 commits new 468df97a5d 313: onsuccess: #2267: 1: Success after binutils/gcc: 90 commits new 7583827805 314: onsuccess: #2268: 1: Success after binutils/gcc: 101 commits new b8d9b0e312 315: onsuccess: #2269: 1: Success after binutils/gcc: 17 commits new e6c773fa96 316: onsuccess: #2270: 1: Success after gcc: 2 commits new 097977c190 317: onsuccess: #2271: 1: Success after binutils/gcc: 8 commits new febb04a3f0 318: onsuccess: #2272: 1: Success after binutils/gcc: 22 commits new 5402acbfb0 319: onsuccess: #2273: 1: Success after binutils/gcc: 15 commits new 4e8a4a102e 320: onsuccess: #2274: 1: Success after gcc: 5 commits new f390d3d2d5 321: onsuccess: #2275: 1: Success after binutils/gcc: 12 commits new 367d134a5d 322: onsuccess: #2276: 1: Success after binutils/gcc: 15 commits new 969f135d40 323: onsuccess: #2277: 1: Success after binutils/gcc: 5 commits new c0833e82d8 324: onsuccess: #2278: 1: Success after binutils/gcc: 4 commits new 2040f49a88 325: onsuccess: #2279: 1: Success after binutils/gcc: 13 commits new d93fc03110 326: onsuccess: #2280: 1: Success after binutils/gcc: 10 commits new efecaa1d56 327: onsuccess: #2281: 1: Success after binutils/gcc: 14 commits new f27e28365b 328: onsuccess: #2283: 1: Success after gdb-12-branchpoint-2 [...] new f507b11385 329: onsuccess: #2285: 1: Success after gcc: 8 commits new 10257d1297 330: onsuccess: #2286: 1: Success after binutils/gcc: 8 commits new e15696487d 331: onsuccess: #2287: 1: Success after gdb-12-branchpoint-2 [...] new 5ac63e0cea 332: onsuccess: #2288: 1: Success after gcc: 2 commits new 0eb6786aa0 333: onsuccess: #2289: 1: Success after basepoints/gcc-13-41 [...] new a92c83fb0c 334: onsuccess: #2290: 1: Success after binutils/gcc: 5 commits new 32df382898 335: onsuccess: #2291: 1: Success after binutils/gcc: 3 commits new aa915c7687 336: onsuccess: #2292: 1: Success after binutils/gcc: 3 commits new 0575a56d1f 337: onsuccess: #2293: 1: Success after gcc: 21 commits new 1b41127f1c 338: onsuccess: #2294: 1: Success after binutils/gcc: 13 commits new 32cebf0c48 339: onsuccess: #2295: 1: Success after binutils/gcc: 18 commits new 18cf154380 340: onsuccess: #2296: 1: Success after gcc: 3 commits new 4e33a3aed5 341: onsuccess: #2297: 1: Success after binutils/gcc: 7 commits new 8435b54633 342: onsuccess: #2298: 1: Success after binutils/gcc: 17 commits new 210704f1fd 343: onsuccess: #2299: 1: Success after binutils/gcc: 18 commits new 5a91df0eee 344: onsuccess: #2300: 1: Success after binutils/gcc: 10 commits new 10f119bdaf 345: onsuccess: #2301: 1: Success after binutils/gcc: 5 commits new 772b216737 346: onsuccess: #2302: 1: Success after binutils/gcc: 9 commits 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 (a948d8b0f9) \ N -- N -- N refs/heads/linaro-local/ci/tcwg_gcc_check/master-aarch64 [...] 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 1724 -> 1684 bytes 02-prepare_abe/console.log.xz | Bin 2736 -> 2728 bytes 03-build_abe-binutils/console.log.xz | Bin 39380 -> 39680 bytes 04-build_abe-gcc/console.log.xz | Bin 214788 -> 215168 bytes 05-build_abe-dejagnu/console.log.xz | Bin 3900 -> 3880 bytes 06-build_abe-check_gcc/console.log.xz | Bin 2712 -> 2672 bytes 07-check_regression/console.log.xz | Bin 5152 -> 5160 bytes 07-check_regression/extra-bisect-params | 2 +- 07-check_regression/fails.sum | 4 +- 07-check_regression/mail-body.txt | 48 +- 07-check_regression/results.compare | 34 +- 07-check_regression/results.compare2 | 23 +- 07-check_regression/results.regressions | 34 +- 08-update_baseline/console.log | 62 +- dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 50 +- mail/mail-subject.txt | 2 +- manifest.sh | 18 +- results | 34 +- sumfiles/g++.log.xz | Bin 3578372 -> 3623396 bytes sumfiles/g++.sum | 128 +- sumfiles/gcc.log.xz | Bin 3130800 -> 3130564 bytes sumfiles/gcc.sum | 4745 ++++++++++++++++--------------- sumfiles/gfortran.log.xz | Bin 1056920 -> 1049052 bytes sumfiles/gfortran.sum | 42 +- sumfiles/libatomic.log.xz | Bin 2188 -> 2188 bytes sumfiles/libatomic.sum | 4 +- sumfiles/libgomp.log.xz | Bin 218780 -> 219040 bytes sumfiles/libgomp.sum | 16 +- sumfiles/libitm.log.xz | Bin 2544 -> 2544 bytes sumfiles/libitm.sum | 6 +- sumfiles/libstdc++.log.xz | Bin 455264 -> 451836 bytes sumfiles/libstdc++.sum | 12 +- 36 files changed, 2637 insertions(+), 2635 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years

[linux] branch master updated (eb7081409f94 -> 4312098baf37)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. unknown user pushed a change to branch master in repository linux. from eb7081409f94 Linux 6.1-rc6 new 9f0933ac026f fscache: fix OOB Read in __fscache_acquire_volume new 11c10956515b 9p/fd: fix issue of list_del corruption in p9_fd_cancel() new 578b565b240a 9p/fd: Fix write overflow in p9_read_work new 6854fadbeee1 9p/fd: Use P9_HDRSZ for header size new 391c18cf776e 9p/xen: check logical size for buffer size new fd64898dfed5 Merge tag '9p-for-6.1-rc7' of https://github.com/martinetd/linux new 0d10e90cee9e spi: mediatek: Fix DEVAPC Violation at KO Remove new db2d2dc9a0b5 spi: spi-imx: Fix spi_bus_clk if requested clock is higher [...] new 804313b64e41 spi: dw-dma: decrease reference count in dw_spi_dma_init_mfld() new 2197aa6b0aa2 spi: tegra210-quad: Fix duplicate resource error new e85e9e0d8cb7 spi: spi-imx: spi_imx_transfer_one(): check for DMA transf [...] new 4312098baf37 Merge tag 'spi-fix-v6.1-rc6' of git://git.kernel.org/pub/s [...] The 12 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: drivers/spi/spi-dw-dma.c | 3 +++ drivers/spi/spi-imx.c | 13 ++++++++----- drivers/spi/spi-mt65xx.c | 8 +++++++- drivers/spi/spi-tegra210-quad.c | 3 ++- fs/fscache/volume.c | 7 +++++-- include/linux/fscache.h | 2 +- net/9p/trans_fd.c | 24 +++++++++++++----------- net/9p/trans_xen.c | 9 +++++++++ 8 files changed, 48 insertions(+), 21 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_kernel/llvm-master-aarch64-lts-allnoconfig updated (c34111f3ad -> 42bbc8e375)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. tcwg-buildslave pushed a change to branch linaro-local/ci/tcwg_kernel/llvm-master-aarch64-lts-allnoconfig in repository toolchain/ci/base-artifacts. from c34111f3ad 22: onsuccess: #475: boot: Success after binutils/llvm/linux [...] new 42bbc8e375 23: onsuccess: #476: boot: Success after binutils/llvm/qemu: [...] The 1 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 1696 -> 1896 bytes 02-prepare_abe/console.log.xz | Bin 2752 -> 2744 bytes 03-build_abe-binutils/console.log.xz | Bin 31736 -> 31828 bytes 04-build_kernel_llvm/console.log.xz | Bin 65368 -> 64776 bytes 05-build_abe-qemu/console.log.xz | Bin 31180 -> 31308 bytes 06-build_linux/console.log.xz | Bin 3364 -> 3368 bytes 07-boot_linux/console.log.xz | Bin 504 -> 504 bytes 08-check_regression/console.log.xz | Bin 4440 -> 3996 bytes dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/llvm_rev | 2 +- git/qemu_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 2 +- mail/mail-subject.txt | 2 +- manifest.sh | 28 ++++++++++++++-------------- 16 files changed, 21 insertions(+), 21 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_gnu_native_check_gdb/master-arm updated (4318ee56a4 -> 13feacb3c8)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. tcwg-buildslave pushed a change to branch linaro-local/ci/tcwg_gnu_native_check_gdb/master-arm in repository toolchain/ci/base-artifacts. discards 4318ee56a4 111: onsuccess: #598: 1: Success after binutils/gcc/gdb: 48 commits discards 2bde17d3e7 110: onsuccess: #597: 1: Success after binutils/gcc/linux/gl [...] discards 0f83d2abfb 109: onsuccess: #596: 1: Success after binutils/gcc/linux/gd [...] discards a814cb5c3f 108: onsuccess: #595: 1: Success after binutils/gcc/linux/gd [...] discards 33cf365081 107: onsuccess: #594: 1: Success after binutils/gcc/linux/gl [...] discards 28a359e06d 106: onsuccess: #593: 1: Success after binutils/gcc/linux/gd [...] discards 9a2414ea0e 105: onsuccess: #592: 1: Success after binutils/gcc/linux/gd [...] discards 33b252df16 104: onsuccess: #591: 1: Success after binutils/gcc/linux/gl [...] discards d86550e125 103: onsuccess: #589: 1: Success after binutils: 3 commits discards 821854263b 102: onsuccess: #586: 1: Success after binutils: 5 commits discards 97277fe67e 101: onsuccess: #584: 1: Success after binutils/gcc/linux/gd [...] discards db897f52b7 100: onsuccess: #583: 1: Success after binutils/gcc/linux/gl [...] discards e86092c79b 99: onsuccess: #582: 1: Success after binutils/gcc/linux/gli [...] discards 1ddfdd0a60 98: onsuccess: #581: 1: Success after binutils/gcc/linux/gli [...] discards 821b0c27a7 97: onsuccess: #580: 1: Success after binutils/gcc/linux/gli [...] discards 3d24384a18 96: onsuccess: #579: 1: Success after binutils/gcc/linux/gdb [...] discards efb2c7241a 95: onsuccess: #578: 1: Success after binutils/gcc/linux/gli [...] discards 84050247d2 94: onsuccess: #577: 1: Success after binutils/gcc/linux/gli [...] discards cae9ae27fb 93: onsuccess: #576: 1: Success after binutils/gcc/linux/gli [...] discards 9957efe169 92: onsuccess: #575: 1: Success after linux: 34 commits discards 53c9e35d18 91: onsuccess: #574: 1: Success after glibc: 3 commits discards ad9f1e7972 90: onsuccess: #572: 1: Success after binutils: 15 commits discards d90a79557f 89: onsuccess: #570: 1: Success after linux: 11 commits discards dd0d0255dd 88: onsuccess: #569: 1: Success after glibc: 10 commits discards 81ce858efa 87: onsuccess: #567: 1: Success after binutils: 8 commits discards d34e62fd19 86: onsuccess: #565: 1: Success after binutils/gcc/linux/gli [...] discards 6e39fa2fe0 85: onsuccess: #564: 1: Success after binutils/gcc/linux/gdb [...] discards e99fc2aa6b 84: onsuccess: #563: 1: Success after binutils/gcc/linux/gli [...] discards 91ff65778f 83: onsuccess: #562: 1: Success after binutils/gcc/linux/gli [...] discards 691775881e 82: onsuccess: #561: 1: Success after binutils/gcc/linux/gli [...] discards a0b57e2352 81: onsuccess: #560: 1: Success after binutils/gcc/linux/gli [...] discards 5bcde7f21d 80: onsuccess: #559: 1: Success after binutils/gcc/linux/gli [...] discards f597e76cd8 79: onsuccess: #558: 1: Success after binutils/gcc/linux/gli [...] discards 67bf73abbb 78: onsuccess: #557: 1: Success after binutils/gcc/linux/gdb [...] discards 02cee064a0 77: onsuccess: #556: 1: Success after binutils/gcc/linux/gdb [...] discards 4c6a4f3871 76: onsuccess: #555: 1: Success after binutils/gcc/linux/gli [...] discards 413643601f 75: onsuccess: #554: 1: Success after binutils/gcc/glibc/gdb [...] discards d51741dd79 74: onsuccess: #553: 1: Success after binutils/gcc/linux/gli [...] discards d30d3b9e36 73: onsuccess: #552: 1: Success after binutils/gcc/linux/gli [...] discards 97a2859a6a 72: onsuccess: #551: 1: Success after binutils/gcc/linux/gli [...] discards 60673d2cb9 71: onsuccess: #550: 1: Success after binutils/gcc/linux/gdb [...] discards 476128a20f 70: onsuccess: #549: 1: Success after binutils/gcc/linux/gli [...] discards a5e8bfc948 69: onsuccess: #548: 1: Success after binutils/gcc/linux/gli [...] discards 30afb9cc4c 68: onsuccess: #547: 1: Success after binutils/gcc/linux/gli [...] discards 5550ce6512 67: onsuccess: #546: 1: Success after binutils/gcc/linux/gli [...] discards db6ea9ab82 66: onsuccess: #545: 1: Success after binutils/gcc/linux/gli [...] discards 872bd0778f 65: onsuccess: #544: 1: Success after binutils/gcc/linux/gli [...] discards 53615dbaae 64: onsuccess: #543: 1: Success after binutils/gcc/linux/gli [...] discards 640aa964b9 63: onsuccess: #542: 1: Success after binutils/gcc/linux/gli [...] discards 6b41f6c184 62: onsuccess: #541: 1: Success after binutils/gcc/linux/gli [...] discards 0403ce3cba 61: onsuccess: #540: 1: Success after binutils/gcc/linux/gli [...] discards 39d0cab296 60: onsuccess: #539: 1: Success after binutils/gcc/linux/gli [...] discards fa40d61ef1 59: onsuccess: #538: 1: Success after binutils/gcc/linux/gli [...] discards d0cc0b7c30 58: onsuccess: #537: 1: Success after binutils/gcc/linux/gli [...] discards 97d3afbf1d 57: onsuccess: #536: 1: Success after binutils/gcc/linux/gli [...] discards 321e576257 56: onsuccess: #535: 1: Success after binutils/gcc/linux/gli [...] discards 9b768dc89f 55: onsuccess: #534: 1: Success after binutils/gcc/linux/gli [...] discards b5daebd29d 54: onsuccess: #533: 1: Success after binutils/gcc/linux/gli [...] discards 57bcf7c5fd 53: onsuccess: #531: 1: Success after binutils: 12 commits discards 7ce083405f 52: onsuccess: #528: 1: Success after binutils: 8 commits discards 1d3bf9895c 51: onsuccess: #525: 1: Success after binutils: 8 commits discards b65c7f0346 50: onsuccess: #523: 1: Success after binutils/gcc/linux/gdb [...] discards ce8e37978b 49: onsuccess: #522: 1: Success after binutils/gcc/linux/gli [...] discards e3c23090a8 48: onsuccess: #521: 1: Success after binutils/gcc/linux/gli [...] discards efa5377d07 47: onsuccess: #520: 1: Success after binutils/gcc/glibc/gdb [...] discards 18ba628880 46: onsuccess: #519: 1: Success after binutils/gcc/linux/gli [...] discards cb9e5c34d5 45: onsuccess: #518: 1: Success after binutils/gcc/glibc/gdb [...] discards 18fddc6ddf 44: onsuccess: #517: 1: Success after binutils/gcc/linux/gli [...] discards f128e8f3d3 43: onsuccess: #516: 1: Success after binutils/gcc/linux/gli [...] discards ccd15bbc61 42: onsuccess: #515: 1: Success after binutils/gcc/linux/gli [...] discards 576a1361d6 41: onsuccess: #514: 1: Success after linux: 64 commits discards cd9eff205c 40: onsuccess: #513: 1: Success after glibc-2.36.9000-121-g5 [...] discards 35a8fd313c 39: onsuccess: #511: 1: Success after binutils: 8 commits discards a126fd6df3 38: onsuccess: #508: 1: Success after binutils: 3 commits discards 433bceae99 37: onsuccess: #506: 1: Success after v6.0-rc5-25-g3245cb65f [...] discards 1c4253e83c 36: onsuccess: #505: 1: Success after glibc: 3 commits discards 40a9df4854 35: onsuccess: #503: 1: Success after binutils: 11 commits discards 137b3ac8e9 34: onsuccess: #501: 1: Success after binutils/gcc/linux/gli [...] discards 76e1ba1368 33: onsuccess: #500: 1: Success after binutils/gcc/linux/gdb [...] discards bc9e639171 32: onsuccess: #499: 1: Success after binutils/gcc/linux/gli [...] discards f2d88c9e2c 31: onsuccess: #498: 1: Success after binutils/gcc/linux/gdb [...] discards a71cd75b1f 30: onsuccess: #497: 1: Success after binutils/gcc/linux/gli [...] discards 6e1e8be296 29: onsuccess: #496: 1: Success after binutils/gcc/linux/gli [...] discards 979f092260 28: onsuccess: #495: 1: Success after binutils/gcc/linux/gdb [...] discards 7a9bb97761 27: onsuccess: #494: 1: Success after binutils/gcc/linux/gli [...] discards fe9b1c94b5 26: onsuccess: #493: 1: Success after binutils/gcc/linux/gli [...] discards 33310d0b45 25: onsuccess: #491: 1: Success after binutils/gcc/linux/gdb [...] discards 3ff06887d4 24: onsuccess: 1: Success after binutils/gcc/linux/gdb: 117 commits discards a22e96e43e 23: onsuccess: 1: Success after binutils/gcc/linux/glibc/gdb [...] discards f02345bfda 22: onsuccess: 1: Success after binutils/gcc/linux/glibc/gdb [...] discards 30fc9b39aa 21: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards f031d93e7f 20: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 3960f662d2 19: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards a590987791 18: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 78509f2bef 17: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards d519a19aea 16: onsuccess: 1: Successful build after binutils: 4 commits discards eb67c9817a 15: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 04d118b005 14: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 43df73ca6e 13: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 26e36244d7 12: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards c40bbecb30 11: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 5a8f9c0117 11: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 06840521ff 12: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 417bca2070 13: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new bb727c5c0d 14: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 0e4c4649cb 15: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 198184b02a 16: onsuccess: 1: Successful build after binutils: 4 commits new 4069185045 17: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new dd5a1a9eb7 18: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new cd5cf240d9 19: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new fe418183c1 20: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 796303b3ea 21: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 736b16a6cf 22: onsuccess: 1: Success after binutils/gcc/linux/glibc/gdb [...] new e2b2c40b56 23: onsuccess: 1: Success after binutils/gcc/linux/glibc/gdb [...] new be7f5bdd4b 24: onsuccess: 1: Success after binutils/gcc/linux/gdb: 117 commits new 9a945ad416 25: onsuccess: #491: 1: Success after binutils/gcc/linux/gdb [...] new 3b3d9994cd 26: onsuccess: #493: 1: Success after binutils/gcc/linux/gli [...] new 5d47ca2bf8 27: onsuccess: #494: 1: Success after binutils/gcc/linux/gli [...] new bc582dc3a3 28: onsuccess: #495: 1: Success after binutils/gcc/linux/gdb [...] new a35dd90d72 29: onsuccess: #496: 1: Success after binutils/gcc/linux/gli [...] new 6d5a5b9e09 30: onsuccess: #497: 1: Success after binutils/gcc/linux/gli [...] new 88adf7ae0e 31: onsuccess: #498: 1: Success after binutils/gcc/linux/gdb [...] new 318ed568c3 32: onsuccess: #499: 1: Success after binutils/gcc/linux/gli [...] new 32e2a524fb 33: onsuccess: #500: 1: Success after binutils/gcc/linux/gdb [...] new 7bcf5fda01 34: onsuccess: #501: 1: Success after binutils/gcc/linux/gli [...] new 257277f42f 35: onsuccess: #503: 1: Success after binutils: 11 commits new 7703277c07 36: onsuccess: #505: 1: Success after glibc: 3 commits new 31d10e038d 37: onsuccess: #506: 1: Success after v6.0-rc5-25-g3245cb65f [...] new 252d6d4cee 38: onsuccess: #508: 1: Success after binutils: 3 commits new e4efde7a9d 39: onsuccess: #511: 1: Success after binutils: 8 commits new 2f43f4d929 40: onsuccess: #513: 1: Success after glibc-2.36.9000-121-g5 [...] new dbd1e6ec60 41: onsuccess: #514: 1: Success after linux: 64 commits new 7268775d02 42: onsuccess: #515: 1: Success after binutils/gcc/linux/gli [...] new 56583c61a9 43: onsuccess: #516: 1: Success after binutils/gcc/linux/gli [...] new 8c1a159a7a 44: onsuccess: #517: 1: Success after binutils/gcc/linux/gli [...] new d20715cf27 45: onsuccess: #518: 1: Success after binutils/gcc/glibc/gdb [...] new 8df84a6499 46: onsuccess: #519: 1: Success after binutils/gcc/linux/gli [...] new 9c591286ab 47: onsuccess: #520: 1: Success after binutils/gcc/glibc/gdb [...] new 5f943db743 48: onsuccess: #521: 1: Success after binutils/gcc/linux/gli [...] new 4c3cfed0d8 49: onsuccess: #522: 1: Success after binutils/gcc/linux/gli [...] new 4df44f6d52 50: onsuccess: #523: 1: Success after binutils/gcc/linux/gdb [...] new a9a06523ca 51: onsuccess: #525: 1: Success after binutils: 8 commits new 00d55e1457 52: onsuccess: #528: 1: Success after binutils: 8 commits new acb79ddd2b 53: onsuccess: #531: 1: Success after binutils: 12 commits new ab57ee66ed 54: onsuccess: #533: 1: Success after binutils/gcc/linux/gli [...] new bfe8122561 55: onsuccess: #534: 1: Success after binutils/gcc/linux/gli [...] new 78970aeb97 56: onsuccess: #535: 1: Success after binutils/gcc/linux/gli [...] new cd95816f00 57: onsuccess: #536: 1: Success after binutils/gcc/linux/gli [...] new ac20560c93 58: onsuccess: #537: 1: Success after binutils/gcc/linux/gli [...] new d86595d132 59: onsuccess: #538: 1: Success after binutils/gcc/linux/gli [...] new 24a57c6eb4 60: onsuccess: #539: 1: Success after binutils/gcc/linux/gli [...] new a2d5ab94fb 61: onsuccess: #540: 1: Success after binutils/gcc/linux/gli [...] new ed423cd68f 62: onsuccess: #541: 1: Success after binutils/gcc/linux/gli [...] new 76cd1eb9a6 63: onsuccess: #542: 1: Success after binutils/gcc/linux/gli [...] new 4c52c12a94 64: onsuccess: #543: 1: Success after binutils/gcc/linux/gli [...] new 81e887f4fd 65: onsuccess: #544: 1: Success after binutils/gcc/linux/gli [...] new 39373e0c00 66: onsuccess: #545: 1: Success after binutils/gcc/linux/gli [...] new e3817d0cdc 67: onsuccess: #546: 1: Success after binutils/gcc/linux/gli [...] new 98daabbd21 68: onsuccess: #547: 1: Success after binutils/gcc/linux/gli [...] new a90080056b 69: onsuccess: #548: 1: Success after binutils/gcc/linux/gli [...] new 157a94751e 70: onsuccess: #549: 1: Success after binutils/gcc/linux/gli [...] new 28c858f50d 71: onsuccess: #550: 1: Success after binutils/gcc/linux/gdb [...] new 77b38a423d 72: onsuccess: #551: 1: Success after binutils/gcc/linux/gli [...] new b4b36c6d18 73: onsuccess: #552: 1: Success after binutils/gcc/linux/gli [...] new 48d42f087b 74: onsuccess: #553: 1: Success after binutils/gcc/linux/gli [...] new 2f5e13bdab 75: onsuccess: #554: 1: Success after binutils/gcc/glibc/gdb [...] new 3f88f8ff95 76: onsuccess: #555: 1: Success after binutils/gcc/linux/gli [...] new a631e234d8 77: onsuccess: #556: 1: Success after binutils/gcc/linux/gdb [...] new bb7676e737 78: onsuccess: #557: 1: Success after binutils/gcc/linux/gdb [...] new fa61a72d9c 79: onsuccess: #558: 1: Success after binutils/gcc/linux/gli [...] new 5430830ab5 80: onsuccess: #559: 1: Success after binutils/gcc/linux/gli [...] new af5ac270bd 81: onsuccess: #560: 1: Success after binutils/gcc/linux/gli [...] new 7b65859a54 82: onsuccess: #561: 1: Success after binutils/gcc/linux/gli [...] new d47b8f67e8 83: onsuccess: #562: 1: Success after binutils/gcc/linux/gli [...] new 7a52f62dc7 84: onsuccess: #563: 1: Success after binutils/gcc/linux/gli [...] new cdde8c4e3c 85: onsuccess: #564: 1: Success after binutils/gcc/linux/gdb [...] new 2d9a0ddf7b 86: onsuccess: #565: 1: Success after binutils/gcc/linux/gli [...] new be861f57e4 87: onsuccess: #567: 1: Success after binutils: 8 commits new 1fc1980622 88: onsuccess: #569: 1: Success after glibc: 10 commits new 17e28a33cf 89: onsuccess: #570: 1: Success after linux: 11 commits new 40eac092ae 90: onsuccess: #572: 1: Success after binutils: 15 commits new f40929d240 91: onsuccess: #574: 1: Success after glibc: 3 commits new 048ec7e01f 92: onsuccess: #575: 1: Success after linux: 34 commits new 0c05a56482 93: onsuccess: #576: 1: Success after binutils/gcc/linux/gli [...] new a678badfba 94: onsuccess: #577: 1: Success after binutils/gcc/linux/gli [...] new 932877a815 95: onsuccess: #578: 1: Success after binutils/gcc/linux/gli [...] new a45eabbf20 96: onsuccess: #579: 1: Success after binutils/gcc/linux/gdb [...] new d93df53363 97: onsuccess: #580: 1: Success after binutils/gcc/linux/gli [...] new a1045d4d30 98: onsuccess: #581: 1: Success after binutils/gcc/linux/gli [...] new d05ba7cff6 99: onsuccess: #582: 1: Success after binutils/gcc/linux/gli [...] new 57fd0f8f5a 100: onsuccess: #583: 1: Success after binutils/gcc/linux/gl [...] new 6160462ad6 101: onsuccess: #584: 1: Success after binutils/gcc/linux/gd [...] new 2911b55b0c 102: onsuccess: #586: 1: Success after binutils: 5 commits new 2d47028d76 103: onsuccess: #589: 1: Success after binutils: 3 commits new ec6c51e0bd 104: onsuccess: #591: 1: Success after binutils/gcc/linux/gl [...] new e0614f4de8 105: onsuccess: #592: 1: Success after binutils/gcc/linux/gd [...] new 25ff68ab4b 106: onsuccess: #593: 1: Success after binutils/gcc/linux/gd [...] new 9e50349633 107: onsuccess: #594: 1: Success after binutils/gcc/linux/gl [...] new ccff8378bb 108: onsuccess: #595: 1: Success after binutils/gcc/linux/gd [...] new 1d964898a5 109: onsuccess: #596: 1: Success after binutils/gcc/linux/gd [...] new e1195e7de9 110: onsuccess: #597: 1: Success after binutils/gcc/linux/gl [...] new a19862f1a5 111: onsuccess: #598: 1: Success after binutils/gcc/gdb: 48 commits new 13feacb3c8 112: onsuccess: #599: 1: Success after binutils/gcc/gdb: 68 commits 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 (4318ee56a4) \ N -- N -- N refs/heads/linaro-local/ci/tcwg_gnu_native_check_gdb/mas [...] 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 1740 -> 1672 bytes 02-prepare_abe/console.log.xz | Bin 2728 -> 2724 bytes 03-build_abe-binutils/console.log.xz | Bin 53092 -> 53476 bytes 04-build_abe-gcc/console.log.xz | Bin 236384 -> 236372 bytes 05-clean_sysroot/console.log.xz | Bin 316 -> 316 bytes 06-build_abe-linux/console.log.xz | Bin 8364 -> 8320 bytes 07-build_abe-glibc/console.log.xz | Bin 235632 -> 235400 bytes 08-build_abe-gdb/console.log.xz | Bin 51168 -> 52104 bytes 09-build_abe-dejagnu/console.log.xz | Bin 3816 -> 3828 bytes 10-build_abe-check_gdb/console.log.xz | Bin 2216 -> 2332 bytes 11-check_regression/console.log.xz | Bin 15048 -> 13148 bytes 11-check_regression/extra-bisect-params | 2 +- 11-check_regression/fails.sum | 62 +- 11-check_regression/mail-body.txt | 200 +- 11-check_regression/results.compare | 182 +- 11-check_regression/results.compare2 | 5260 +++++++++------------ 11-check_regression/results.regressions | 132 +- 12-update_baseline/console.log | 64 +- 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 | 202 +- mail/mail-subject.txt | 2 +- manifest.sh | 28 +- results | 132 +- sumfiles/gdb.log.xz | Bin 1718060 -> 1786760 bytes sumfiles/gdb.sum | 7880 ++++++++++--------------------- 29 files changed, 5314 insertions(+), 8842 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_gnu_native_check_gcc/master-aarch64 updated (1aa97e7877 -> dfcc568444)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. tcwg-buildslave pushed a change to branch linaro-local/ci/tcwg_gnu_native_check_gcc/master-aarch64 in repository toolchain/ci/base-artifacts. discards 1aa97e7877 103: onsuccess: #844: 1: Success after binutils/gcc/gdb: 52 commits discards f3b86bba50 102: onsuccess: #843: 1: Success after binutils/gcc/linux/gl [...] discards ae322eefb1 101: onsuccess: #842: 1: Success after binutils/gcc/linux/gd [...] discards 5bd70d0f45 100: onsuccess: #841: 1: Success after binutils/gcc/linux/gd [...] discards 48dedfb3b2 99: onsuccess: #840: 1: Success after binutils/gcc/linux/gdb [...] discards 09d3ad869b 98: onsuccess: #839: 1: Success after binutils/gcc/linux/gli [...] discards 8dcaeebb6d 97: onsuccess: #838: 1: Success after binutils/gcc/linux/gdb [...] discards 89390fc79e 96: onsuccess: #837: 1: Success after binutils/gcc/linux/gli [...] discards c5b3d84293 95: onsuccess: #835: 1: Success after binutils: 3 commits discards a1efc2d8c7 94: onsuccess: #832: 1: Success after binutils: 5 commits discards 081fa0f078 93: onsuccess: #830: 1: Success after binutils/gcc/linux/gdb [...] discards 32568b3ce4 92: onsuccess: #829: 1: Success after binutils/gcc/linux/gli [...] discards be84b88f36 91: onsuccess: #828: 1: Success after binutils/gcc/linux/gli [...] discards 7aafccf583 90: onsuccess: #827: 1: Success after binutils/gcc/linux/gli [...] discards 19eca28185 89: onsuccess: #826: 1: Success after binutils/gcc/linux/gli [...] discards c02e8263bb 88: onsuccess: #825: 1: Success after binutils/gcc/linux/gdb [...] discards 4eaf51b755 87: onsuccess: #824: 1: Success after binutils/gcc/linux/gli [...] discards 5ddc199adc 86: onsuccess: #823: 1: Success after binutils/gcc/linux/gli [...] discards 5ab54f4819 85: onsuccess: #822: 1: Success after binutils/gcc/linux/gli [...] discards f58ac3ef1c 84: onsuccess: #821: 1: Success after binutils/gcc/linux/gli [...] discards c0cf4d4bfd 83: onsuccess: #820: 1: Success after binutils/gcc/linux/gli [...] discards 37cb8ca0dc 82: onsuccess: #819: 1: Success after binutils/gcc/linux/gli [...] discards 34481c3b05 81: onsuccess: #818: 1: Success after binutils/gcc/linux/gdb [...] discards 55976fa96f 80: onsuccess: #817: 1: Success after binutils/gcc/linux/gli [...] discards 6e877311c3 79: onsuccess: #816: 1: Success after binutils/gcc/linux/gli [...] discards 82ca3839d1 78: onsuccess: #815: 1: Success after binutils/gcc/linux/gli [...] discards 56a0131452 77: onsuccess: #814: 1: Success after binutils/gcc/linux/gli [...] discards 394c4ef349 76: onsuccess: #813: 1: Success after binutils/gcc/linux/gli [...] discards 807d7eee5c 75: onsuccess: #812: 1: Success after binutils/gcc/linux/gli [...] discards c9f49e297e 74: onsuccess: #811: 1: Success after binutils/gcc/linux/gdb [...] discards 09b821d6b8 73: onsuccess: #810: 1: Success after binutils/gcc/linux/gdb [...] discards 7ebb5d6e0c 72: onsuccess: #809: 1: Success after binutils/gcc/linux/gli [...] discards f88324098e 71: onsuccess: #808: 1: Success after binutils/gcc/glibc/gdb [...] discards 7d687bb15e 70: onsuccess: #807: 1: Success after binutils/gcc/linux/gli [...] discards a1a9b991f7 69: onsuccess: #806: 1: Success after binutils/gcc/linux/gli [...] discards 00f64bbc77 68: onsuccess: #805: 1: Success after binutils/gcc/linux/gli [...] discards 451e23a9da 67: onsuccess: #804: 1: Success after binutils/gcc/linux/gdb [...] discards e21fdaacd6 66: onsuccess: #803: 1: Success after binutils/gcc/linux/gli [...] discards 6ad83501f0 65: onsuccess: #802: 1: Success after binutils/gcc/linux/gli [...] discards 5ad3a8e543 64: onsuccess: #801: 1: Success after binutils/gcc/linux/gli [...] discards 8a4123f6da 63: onsuccess: #800: 1: Success after binutils/gcc/linux/gli [...] discards d9330ad12d 62: onsuccess: #799: 1: Success after binutils/gcc/linux/gdb [...] discards c312cdd3bb 61: onsuccess: #798: 1: Success after binutils/gcc/linux/gli [...] discards 58e0cd5555 60: onsuccess: #797: 1: Success after binutils/gcc/glibc/gdb [...] discards a5bd5e330a 59: onsuccess: #796: 1: Success after binutils/gcc/linux/gli [...] discards 76230ebac7 58: onsuccess: #795: 1: Success after binutils/gcc/linux/gdb [...] discards e37a93db85 57: onsuccess: #794: 1: Success after binutils/gcc/linux/gli [...] discards 254bb676f5 56: onsuccess: #793: 1: Success after binutils/gcc/linux/gli [...] discards 6eb190649d 55: onsuccess: #792: 1: Success after binutils/gcc/linux/gli [...] discards 4ac8cbc969 54: onsuccess: #791: 1: Success after binutils/gcc/linux/gli [...] discards c909221efa 53: onsuccess: #790: 1: Success after binutils/gcc/linux/gli [...] discards 5f5b1c57b8 52: onsuccess: #789: 1: Success after binutils/gcc/linux/gli [...] discards 074a9a56f7 51: onsuccess: #788: 1: Success after binutils/gcc/linux/gli [...] discards 66eaec6df4 50: onsuccess: #787: 1: Success after binutils/gcc/linux/gli [...] discards 192ca53f30 49: onsuccess: #785: 1: Success after binutils: 12 commits discards 94b1480a6d 48: onsuccess: #782: 1: Success after binutils: 8 commits discards a0b219770b 47: onsuccess: #780: 1: Success after binutils/gcc/linux/gli [...] discards b49e1442d6 46: onsuccess: #779: 1: Success after binutils/gcc/linux/gdb [...] discards 2ff4ece4ce 45: onsuccess: #778: 1: Success after binutils/gcc/linux/gdb [...] discards 04f5ed61b5 44: onsuccess: #777: 1: Success after binutils/gcc/linux/gli [...] discards 6769485d2c 43: onsuccess: #776: 1: Success after binutils/gcc/glibc/gdb [...] discards 0742c1eabe 42: onsuccess: #775: 1: Success after binutils/gcc/linux/gli [...] discards 414ee26008 41: onsuccess: #774: 1: Success after binutils/gcc/linux/gli [...] discards 984bf64465 40: onsuccess: #773: 1: Success after binutils/gcc/linux/gli [...] discards 508fdd906e 39: onsuccess: #772: 1: Success after binutils/gcc/linux/gli [...] discards 5120ef8a5c 38: onsuccess: #771: 1: Success after binutils/gcc/linux/gli [...] discards b444605a3d 37: onsuccess: #770: 1: Success after binutils/gcc/linux/gli [...] discards 151aa0675c 36: onsuccess: #769: 1: Success after binutils/gcc/gdb: 22 commits discards 5f7ca5fbe6 35: onsuccess: #768: 1: Success after binutils/gcc/linux/gli [...] discards 02ad3523f0 34: onsuccess: #767: 1: Success after binutils/gcc/linux/gli [...] discards 97beab0550 33: onsuccess: #766: 1: Success after binutils/gcc/linux/gdb [...] discards 2d8b8de2dd 32: onsuccess: #765: 1: Success after binutils/gcc/glibc/gdb [...] discards 6cb1da5a7e 31: onsuccess: #764: 1: Success after binutils/gcc/linux/gdb [...] discards e9c11279fd 30: onsuccess: #763: 1: Success after binutils/gcc/linux/gli [...] discards 8c90c4f542 29: onsuccess: #762: 1: Success after binutils/gcc/linux/gli [...] discards dbac8a3727 28: onsuccess: #761: 1: Success after binutils/gcc/linux/gdb [...] discards 1e55c22a2f 27: onsuccess: #760: 1: Success after binutils/gcc/linux/gli [...] discards e15491788f 26: onsuccess: #759: 1: Success after binutils/gcc/linux/gli [...] discards 6f6f49cb08 25: onsuccess: #757: 1: Success after binutils/gcc/linux/gdb [...] discards 4a41bff458 24: onsuccess: 1: Success after binutils/gcc/linux/gdb: 117 commits discards 58e6585ba8 23: onsuccess: 1: Success after binutils/gcc/linux/glibc/gdb [...] discards 278aa2e01c 22: onsuccess: 1: Success after binutils/gcc/linux/glibc/gdb [...] discards bd377d7977 21: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards f9a9a7e1fa 20: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 23e7013aa6 19: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 9b6801d502 18: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards dd0e9e8694 17: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 46e770d61e 16: onsuccess: 1: Successful build after binutils: 4 commits discards eb3733acc5 15: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 4008500922 14: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards b961cf32d3 13: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards fc64b540b4 12: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards babdc3e24f 11: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards c52e383ff7 10: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards f9ac8a25b5 9: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] discards bb7c2a77f8 8: onsuccess: 1: Successful build after binutils/gcc/glibc/g [...] discards d055da0d61 7: onsuccess: binutils-gcc-linux-glibc-gdb: 1 discards 360f240957 6: onsuccess: binutils-gcc-linux-glibc-gdb: 1 discards 820c096d57 5: onsuccess: binutils-gcc-linux-glibc-gdb: 1 discards a744e2945b 4: onsuccess: binutils-gcc-linux-glibc-gdb: 1 discards 4e305383e9 3: onsuccess: binutils-gcc-linux-glibc-gdb: 1 new 0588d1f3c9 3: onsuccess: binutils-gcc-linux-glibc-gdb: 1 new c7c562708d 4: onsuccess: binutils-gcc-linux-glibc-gdb: 1 new 106b06d8f8 5: onsuccess: binutils-gcc-linux-glibc-gdb: 1 new cc236f1ed4 6: onsuccess: binutils-gcc-linux-glibc-gdb: 1 new bdfe06b46f 7: onsuccess: binutils-gcc-linux-glibc-gdb: 1 new 50d961633a 8: onsuccess: 1: Successful build after binutils/gcc/glibc/g [...] new 5b9ada933d 9: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] new 5088a0020a 10: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 9e223df0fc 11: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 90d2eb8197 12: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new d9fed8ca79 13: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 7911f8d7ff 14: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new ab4dc3b450 15: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 30159a27ca 16: onsuccess: 1: Successful build after binutils: 4 commits new 3917699e98 17: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new bfb255a95b 18: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 47e0c93c3c 19: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new ba977ac60e 20: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 0f0a039f41 21: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new c8dda7aac4 22: onsuccess: 1: Success after binutils/gcc/linux/glibc/gdb [...] new 674976f7f1 23: onsuccess: 1: Success after binutils/gcc/linux/glibc/gdb [...] new 44d6695f2c 24: onsuccess: 1: Success after binutils/gcc/linux/gdb: 117 commits new d765e5256a 25: onsuccess: #757: 1: Success after binutils/gcc/linux/gdb [...] new afd7660995 26: onsuccess: #759: 1: Success after binutils/gcc/linux/gli [...] new b55ddf6aee 27: onsuccess: #760: 1: Success after binutils/gcc/linux/gli [...] new 15d4fdc642 28: onsuccess: #761: 1: Success after binutils/gcc/linux/gdb [...] new d95692fb98 29: onsuccess: #762: 1: Success after binutils/gcc/linux/gli [...] new 6c1325a835 30: onsuccess: #763: 1: Success after binutils/gcc/linux/gli [...] new cc1be23e55 31: onsuccess: #764: 1: Success after binutils/gcc/linux/gdb [...] new 121327752c 32: onsuccess: #765: 1: Success after binutils/gcc/glibc/gdb [...] new 1602433c92 33: onsuccess: #766: 1: Success after binutils/gcc/linux/gdb [...] new 1e52a1166f 34: onsuccess: #767: 1: Success after binutils/gcc/linux/gli [...] new 329e6d60af 35: onsuccess: #768: 1: Success after binutils/gcc/linux/gli [...] new f85ff6d5c3 36: onsuccess: #769: 1: Success after binutils/gcc/gdb: 22 commits new c934537719 37: onsuccess: #770: 1: Success after binutils/gcc/linux/gli [...] new 619dc0ccd2 38: onsuccess: #771: 1: Success after binutils/gcc/linux/gli [...] new d793f4cbd2 39: onsuccess: #772: 1: Success after binutils/gcc/linux/gli [...] new efeabe0b7a 40: onsuccess: #773: 1: Success after binutils/gcc/linux/gli [...] new 705a546ed8 41: onsuccess: #774: 1: Success after binutils/gcc/linux/gli [...] new c2ad3752b7 42: onsuccess: #775: 1: Success after binutils/gcc/linux/gli [...] new 1c43adf199 43: onsuccess: #776: 1: Success after binutils/gcc/glibc/gdb [...] new fc7299f284 44: onsuccess: #777: 1: Success after binutils/gcc/linux/gli [...] new bbbedd312c 45: onsuccess: #778: 1: Success after binutils/gcc/linux/gdb [...] new 52d61035c1 46: onsuccess: #779: 1: Success after binutils/gcc/linux/gdb [...] new 5743f8ea4c 47: onsuccess: #780: 1: Success after binutils/gcc/linux/gli [...] new cca5ac1e9a 48: onsuccess: #782: 1: Success after binutils: 8 commits new 6ca38f2239 49: onsuccess: #785: 1: Success after binutils: 12 commits new 5d574117b4 50: onsuccess: #787: 1: Success after binutils/gcc/linux/gli [...] new b11588142a 51: onsuccess: #788: 1: Success after binutils/gcc/linux/gli [...] new 24bbb709ea 52: onsuccess: #789: 1: Success after binutils/gcc/linux/gli [...] new b61fdec91c 53: onsuccess: #790: 1: Success after binutils/gcc/linux/gli [...] new f4c81ef935 54: onsuccess: #791: 1: Success after binutils/gcc/linux/gli [...] new b966bb6a38 55: onsuccess: #792: 1: Success after binutils/gcc/linux/gli [...] new 1cae83f04d 56: onsuccess: #793: 1: Success after binutils/gcc/linux/gli [...] new 44cf982065 57: onsuccess: #794: 1: Success after binutils/gcc/linux/gli [...] new dd391485cd 58: onsuccess: #795: 1: Success after binutils/gcc/linux/gdb [...] new 94e4840e27 59: onsuccess: #796: 1: Success after binutils/gcc/linux/gli [...] new e6e3d88141 60: onsuccess: #797: 1: Success after binutils/gcc/glibc/gdb [...] new 59f35b49b6 61: onsuccess: #798: 1: Success after binutils/gcc/linux/gli [...] new 7ce567a870 62: onsuccess: #799: 1: Success after binutils/gcc/linux/gdb [...] new a2581afb2c 63: onsuccess: #800: 1: Success after binutils/gcc/linux/gli [...] new 31450ca6ea 64: onsuccess: #801: 1: Success after binutils/gcc/linux/gli [...] new 1affecb592 65: onsuccess: #802: 1: Success after binutils/gcc/linux/gli [...] new 3588979c8f 66: onsuccess: #803: 1: Success after binutils/gcc/linux/gli [...] new 81c7bbc5fa 67: onsuccess: #804: 1: Success after binutils/gcc/linux/gdb [...] new 1d363593ba 68: onsuccess: #805: 1: Success after binutils/gcc/linux/gli [...] new 9a2f3c0d8a 69: onsuccess: #806: 1: Success after binutils/gcc/linux/gli [...] new a17b43b282 70: onsuccess: #807: 1: Success after binutils/gcc/linux/gli [...] new 63f9ddaca4 71: onsuccess: #808: 1: Success after binutils/gcc/glibc/gdb [...] new 0074050889 72: onsuccess: #809: 1: Success after binutils/gcc/linux/gli [...] new dc39d3fd35 73: onsuccess: #810: 1: Success after binutils/gcc/linux/gdb [...] new 6efde22413 74: onsuccess: #811: 1: Success after binutils/gcc/linux/gdb [...] new c6b5aa4fe0 75: onsuccess: #812: 1: Success after binutils/gcc/linux/gli [...] new 038f8069ec 76: onsuccess: #813: 1: Success after binutils/gcc/linux/gli [...] new 2a1cecbd8e 77: onsuccess: #814: 1: Success after binutils/gcc/linux/gli [...] new 5f23f09dfa 78: onsuccess: #815: 1: Success after binutils/gcc/linux/gli [...] new 3e1c4b9873 79: onsuccess: #816: 1: Success after binutils/gcc/linux/gli [...] new eeb3518e95 80: onsuccess: #817: 1: Success after binutils/gcc/linux/gli [...] new cffb407054 81: onsuccess: #818: 1: Success after binutils/gcc/linux/gdb [...] new cb76925a1e 82: onsuccess: #819: 1: Success after binutils/gcc/linux/gli [...] new 4266ca1b8d 83: onsuccess: #820: 1: Success after binutils/gcc/linux/gli [...] new b1b13f96c9 84: onsuccess: #821: 1: Success after binutils/gcc/linux/gli [...] new a69a44d19d 85: onsuccess: #822: 1: Success after binutils/gcc/linux/gli [...] new 3deee609df 86: onsuccess: #823: 1: Success after binutils/gcc/linux/gli [...] new 2ce3521e3a 87: onsuccess: #824: 1: Success after binutils/gcc/linux/gli [...] new 4d44952747 88: onsuccess: #825: 1: Success after binutils/gcc/linux/gdb [...] new b3497cb3ff 89: onsuccess: #826: 1: Success after binutils/gcc/linux/gli [...] new 137e06e651 90: onsuccess: #827: 1: Success after binutils/gcc/linux/gli [...] new c8624a76ee 91: onsuccess: #828: 1: Success after binutils/gcc/linux/gli [...] new ddd4c93151 92: onsuccess: #829: 1: Success after binutils/gcc/linux/gli [...] new fc0c649648 93: onsuccess: #830: 1: Success after binutils/gcc/linux/gdb [...] new 7a170b6b46 94: onsuccess: #832: 1: Success after binutils: 5 commits new b486bbfa8f 95: onsuccess: #835: 1: Success after binutils: 3 commits new 81ac248d16 96: onsuccess: #837: 1: Success after binutils/gcc/linux/gli [...] new 8eeb465d64 97: onsuccess: #838: 1: Success after binutils/gcc/linux/gdb [...] new cbe2f6fbc1 98: onsuccess: #839: 1: Success after binutils/gcc/linux/gli [...] new 21afe2a28f 99: onsuccess: #840: 1: Success after binutils/gcc/linux/gdb [...] new eaa62f6192 100: onsuccess: #841: 1: Success after binutils/gcc/linux/gd [...] new 31e9ae6ea3 101: onsuccess: #842: 1: Success after binutils/gcc/linux/gd [...] new d24fe46efb 102: onsuccess: #843: 1: Success after binutils/gcc/linux/gl [...] new 327d133f38 103: onsuccess: #844: 1: Success after binutils/gcc/gdb: 52 commits new dfcc568444 104: onsuccess: #845: 1: Success after binutils/gcc/gdb: 64 commits 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 (1aa97e7877) \ N -- N -- N refs/heads/linaro-local/ci/tcwg_gnu_native_check_gcc/mas [...] 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 1700 -> 1700 bytes 02-prepare_abe/console.log.xz | Bin 2716 -> 2728 bytes 03-build_abe-binutils/console.log.xz | Bin 39184 -> 39400 bytes 04-build_abe-gcc/console.log.xz | Bin 214444 -> 214192 bytes 06-build_abe-linux/console.log.xz | Bin 8296 -> 8384 bytes 07-build_abe-glibc/console.log.xz | Bin 244028 -> 244608 bytes 08-build_abe-gdb/console.log.xz | Bin 39000 -> 39060 bytes 09-build_abe-dejagnu/console.log.xz | Bin 3832 -> 3836 bytes 10-build_abe-check_gcc/console.log.xz | Bin 2684 -> 2504 bytes 11-check_regression/console.log.xz | Bin 6680 -> 6476 bytes 11-check_regression/extra-bisect-params | 2 +- 11-check_regression/fails.sum | 4 +- 11-check_regression/mail-body.txt | 44 +- 11-check_regression/results.compare | 18 +- 11-check_regression/results.compare2 | 125 +- 11-check_regression/results.regressions | 18 +- 12-update_baseline/console.log | 36 +- 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 | 46 +- mail/mail-subject.txt | 2 +- manifest.sh | 28 +- results | 18 +- sumfiles/g++.log.xz | Bin 3768964 -> 3748656 bytes sumfiles/g++.sum | 16 +- sumfiles/gcc.log.xz | Bin 3295056 -> 3280156 bytes sumfiles/gcc.sum | 4296 ++++++++++++++++--------------- sumfiles/gfortran.log.xz | Bin 1080092 -> 1079992 bytes sumfiles/gfortran.sum | 6 +- sumfiles/libatomic.log.xz | Bin 2268 -> 2276 bytes sumfiles/libatomic.sum | 2 +- sumfiles/libgomp.log.xz | Bin 230512 -> 230704 bytes sumfiles/libgomp.sum | 2 +- sumfiles/libitm.log.xz | Bin 2664 -> 2668 bytes sumfiles/libitm.sum | 2 +- sumfiles/libstdc++.log.xz | Bin 446520 -> 453312 bytes sumfiles/libstdc++.sum | 5 +- 40 files changed, 2393 insertions(+), 2287 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_kernel/llvm-release-arm-lts-allnoconfig updated (88a2d70e49 -> e3dc8712b6)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. tcwg-buildslave pushed a change to branch linaro-local/ci/tcwg_kernel/llvm-release-arm-lts-allnoconfig in repository toolchain/ci/base-artifacts. from 88a2d70e49 23: onsuccess: #245: all: Success after binutils/llvm/linux/ [...] new e3dc8712b6 24: onsuccess: #246: all: Success after binutils/llvm/qemu: [...] The 1 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 1688 -> 1688 bytes 02-prepare_abe/console.log.xz | Bin 2740 -> 2732 bytes 03-build_abe-binutils/console.log.xz | Bin 30084 -> 30004 bytes 04-build_kernel_llvm/console.log.xz | Bin 65148 -> 63868 bytes 05-build_abe-qemu/console.log.xz | Bin 30944 -> 30348 bytes 06-build_linux/console.log.xz | Bin 3428 -> 3424 bytes 07-boot_linux/console.log.xz | Bin 496 -> 496 bytes 08-check_regression/console.log.xz | Bin 4248 -> 3556 bytes dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/llvm_rev | 2 +- git/qemu_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 2 +- mail/mail-subject.txt | 2 +- manifest.sh | 28 ++++++++++++++-------------- 16 files changed, 21 insertions(+), 21 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_gcc_bootstrap/release-arm-bootstrap_profiled_lto updated (1edf694670 -> 8c988541cb)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. tcwg-buildslave pushed a change to branch linaro-local/ci/tcwg_gcc_bootstrap/release-arm-bootstrap_profiled_lto in repository toolchain/ci/base-artifacts. from 1edf694670 29: onsuccess: #141: 2: Success after binutils/gcc: 8 commits new 8c988541cb 30: onsuccess: #142: 2: Success after binutils/gcc: 12 commits The 1 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 1692 -> 1864 bytes 02-prepare_abe/console.log.xz | Bin 2716 -> 2724 bytes 04-build_abe-binutils/console.log.xz | Bin 50980 -> 52216 bytes 05-build_abe-bootstrap_profiled_lto/console.log.xz | Bin 948360 -> 945612 bytes 06-check_regression/console.log.xz | Bin 2892 -> 2840 bytes 07-update_baseline/console.log | 9 --------- dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 2 +- mail/mail-subject.txt | 2 +- manifest.sh | 20 ++++++++++---------- 13 files changed, 16 insertions(+), 25 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_gnu_native_fast_check_gdb/master-aarch64 updated (3a6851bb94 -> 3dd527c9c5)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. tcwg-buildslave pushed a change to branch linaro-local/ci/tcwg_gnu_native_fast_check_gdb/master-aarch64 in repository toolchain/ci/base-artifacts. from 3a6851bb94 17: onsuccess: #22: 1: Success after binutils/gcc/gdb: 52 commits new 3dd527c9c5 18: onsuccess: #23: 1: Success after binutils/gcc/gdb: 64 commits The 1 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 1680 -> 1684 bytes 02-prepare_abe/console.log.xz | Bin 2716 -> 2724 bytes 03-build_abe-binutils/console.log.xz | Bin 39592 -> 39544 bytes 04-build_abe-gcc/console.log.xz | Bin 213688 -> 214868 bytes 05-clean_sysroot/console.log.xz | Bin 316 -> 312 bytes 06-build_abe-linux/console.log.xz | Bin 8444 -> 8408 bytes 07-build_abe-glibc/console.log.xz | Bin 245976 -> 245156 bytes 08-build_abe-gdb/console.log.xz | Bin 39964 -> 39424 bytes 09-build_abe-dejagnu/console.log.xz | Bin 3972 -> 3852 bytes 10-build_abe-check_gdb/console.log.xz | Bin 2648 -> 2688 bytes 11-check_regression/console.log.xz | Bin 5760 -> 5364 bytes 11-check_regression/results.compare | 4 ++-- 11-check_regression/results.compare2 | 6 +++--- 12-update_baseline/console.log | 2 +- 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 | 2 +- mail/mail-subject.txt | 2 +- manifest.sh | 28 ++++++++++++++-------------- sumfiles/gdb.log.xz | Bin 14484 -> 14492 bytes sumfiles/gdb.sum | 34 +++++++++++++++++----------------- 24 files changed, 44 insertions(+), 44 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_bmk_gnu_tk1/gnu-master-arm-spec2k6-O3 updated (6225804575 -> b3cba2c52c)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. tcwg-buildslave pushed a change to branch linaro-local/ci/tcwg_bmk_gnu_tk1/gnu-master-arm-spec2k6-O3 in repository toolchain/ci/base-artifacts. from 6225804575 30: onsuccess: #511: 1: [TCWG CI] No change after gcc: 86 commits new b3cba2c52c 31: onsuccess: #512: 1: [TCWG CI] No change after binutils: [...] The 1 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 1756 -> 1744 bytes 02-prepare_abe/console.log.xz | Bin 2736 -> 2736 bytes 03-build_abe-binutils/console.log.xz | Bin 31492 -> 32360 bytes 04-build_abe-stage1/console.log.xz | Bin 92152 -> 92284 bytes 06-build_abe-linux/console.log.xz | Bin 8776 -> 8752 bytes 07-build_abe-glibc/console.log.xz | Bin 235220 -> 235108 bytes 08-build_abe-stage2/console.log.xz | Bin 209728 -> 209576 bytes 09-benchmark/benchmark-build.log | 114 +- 09-benchmark/benchmark.log | 112 +- 09-benchmark/console.log.xz | Bin 3828 -> 3884 bytes 10-check_regression/console.log.xz | Bin 16136 -> 16148 bytes .../csv-results-vs-first-1/md5sum.csv | 2574 +- .../csv-results-vs-first-1/perf.csv | 3292 +- .../csv-results-vs-first-1/results.csv | 19689 +- .../csv-results-vs-first-1/size.csv | 533793 ++++++++--------- .../csv-results-vs-first-1/vect.csv | 444 +- .../csv-results-vs-prev-0/md5sum.csv | 2934 +- 10-check_regression/csv-results-vs-prev-0/perf.csv | 3387 +- .../csv-results-vs-prev-0/results.csv | 22321 +- 10-check_regression/csv-results-vs-prev-0/size.csv | 535066 +++++++++--------- 10-check_regression/csv-results-vs-prev-0/vect.csv | 348 +- .../csv-results-vs-prev-1/md5sum.csv | 2574 +- 10-check_regression/csv-results-vs-prev-1/perf.csv | 3292 +- .../csv-results-vs-prev-1/results.csv | 19689 +- 10-check_regression/csv-results-vs-prev-1/size.csv | 533793 ++++++++--------- 10-check_regression/csv-results-vs-prev-1/vect.csv | 444 +- 10-check_regression/results-vs-first-brief.csv | 66 +- 10-check_regression/results-vs-first-full.csv | 3174 +- 10-check_regression/results-vs-first-internal.csv | 246 +- 10-check_regression/results-vs-first.csv | 246 +- 10-check_regression/results-vs-first.log | 1068 +- 10-check_regression/results-vs-prev-brief.csv | 68 +- 10-check_regression/results-vs-prev-compare.csv | 6 +- 10-check_regression/results-vs-prev-full.csv | 3420 +- 10-check_regression/results-vs-prev-internal.csv | 252 +- 10-check_regression/results-vs-prev.csv | 252 +- 10-check_regression/results-vs-prev.log | 1334 +- 10-check_regression/skipped-symbols.txt | 2 +- dashboard/dashboard-generate.sh | 2 +- .../400.perlbench/results-metadata.json | 10 +- .../squad-vs-first/401.bzip2/results-metadata.json | 10 +- .../squad-vs-first/403.gcc/results-metadata.json | 10 +- .../squad-vs-first/403.gcc/results-metrics.json | 2 +- .../410.bwaves/results-metadata.json | 10 +- .../416.gamess/results-metadata.json | 10 +- .../squad-vs-first/429.mcf/results-metadata.json | 10 +- .../squad-vs-first/433.milc/results-metadata.json | 10 +- .../434.zeusmp/results-metadata.json | 10 +- .../435.gromacs/results-metadata.json | 10 +- .../436.cactusADM/results-metadata.json | 10 +- .../437.leslie3d/results-metadata.json | 10 +- .../437.leslie3d/results-metrics.json | 2 +- .../squad-vs-first/444.namd/results-metadata.json | 10 +- .../squad-vs-first/445.gobmk/results-metadata.json | 10 +- .../447.dealII/results-metadata.json | 10 +- .../squad-vs-first/447.dealII/results-metrics.json | 2 +- .../450.soplex/results-metadata.json | 10 +- .../453.povray/results-metadata.json | 10 +- .../squad-vs-first/453.povray/results-metrics.json | 2 +- .../454.calculix/results-metadata.json | 10 +- .../squad-vs-first/456.hmmer/results-metadata.json | 10 +- .../squad-vs-first/456.hmmer/results-metrics.json | 2 +- .../squad-vs-first/458.sjeng/results-metadata.json | 10 +- .../squad-vs-first/458.sjeng/results-metrics.json | 2 +- .../459.GemsFDTD/results-metadata.json | 10 +- .../462.libquantum/results-metadata.json | 10 +- .../464.h264ref/results-metadata.json | 10 +- .../464.h264ref/results-metrics.json | 2 +- .../squad-vs-first/465.tonto/results-metadata.json | 10 +- .../squad-vs-first/470.lbm/results-metadata.json | 10 +- .../471.omnetpp/results-metadata.json | 10 +- .../471.omnetpp/results-metrics.json | 2 +- .../squad-vs-first/473.astar/results-metadata.json | 10 +- .../squad-vs-first/481.wrf/results-metadata.json | 10 +- .../squad-vs-first/481.wrf/results-metrics.json | 2 +- .../482.sphinx3/results-metadata.json | 10 +- .../483.xalancbmk/results-metadata.json | 10 +- .../squad-vs-first/Mean/results-metadata.json | 10 +- dashboard/squad-vs-first/dashboard-push-squad.sh | 122 +- git/binutils_rev | 2 +- mail/jira-body.txt | 14 +- mail/mail-body.txt | 14 +- mail/mail-subject.txt | 2 +- manifest.sh | 16 +- results_id | 2 +- 85 files changed, 839106 insertions(+), 855386 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years

[gcc] branch master updated (8a0fce6a519 -> 2eaa0cc45e8)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. unknown user pushed a change to branch master in repository gcc. from 8a0fce6a519 c: Fix compile time hog in c_genericize [PR107127] new 2eaa0cc45e8 Fortran: error recovery on associate with bad selector [PR107577] The 1 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: gcc/fortran/resolve.cc | 3 ++- gcc/testsuite/gfortran.dg/pr107577.f90 | 13 +++++++++++++ 2 files changed, 15 insertions(+), 1 deletion(-) create mode 100644 gcc/testsuite/gfortran.dg/pr107577.f90 -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years

Jump to page:

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

Tcwg-commits November 2022