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-arm in repository toolchain/ci/base-artifacts.
discards 4ce9722951 424: onsuccess: #2248: 1: Success after gcc: 6 commits discards f361da03b7 423: onsuccess: #2247: 1: Success after gcc/linux: 8 commits discards 0d9606d111 422: onsuccess: #2246: 1: Success after binutils/gcc/linux/g [...] discards bd027a4df4 421: onsuccess: #2245: 1: Success after binutils/gcc/glibc/g [...] discards 688f55b878 420: onsuccess: #2244: 1: Success after gcc/glibc: 5 commits discards 77631c4723 419: onsuccess: #2243: 1: Success after binutils/gcc/linux/g [...] discards 79a9337f30 418: onsuccess: #2239: 1: Success after binutils/gcc/gdb: 5 commits discards ddeb7e9d32 417: onsuccess: #2238: 1: Success after binutils/gcc/linux/g [...] discards b5db90b142 416: onsuccess: #2237: 1: Success after binutils/gcc/glibc/g [...] discards 943ba40e7a 415: onsuccess: #2236: 1: Success after binutils/gcc/gdb: 14 [...] discards 3fe298acc6 414: onsuccess: #2235: 1: Success after binutils/gcc/gdb: 13 [...] discards 7a3753ba43 413: onsuccess: #2234: 1: Success after binutils/gcc/linux/g [...] discards 13cd2eb188 412: onsuccess: #2233: 1: Success after binutils/gcc/glibc/g [...] discards f6adf29adc 411: onsuccess: #2232: 1: Success after gcc: 3 commits discards 8bb8d1acb6 410: onsuccess: #2231: 1: Success after binutils/gcc/linux/g [...] discards 76c14c0819 409: onsuccess: #2230: 1: Success after binutils/gcc/glibc/g [...] discards f2f6366d8a 408: onsuccess: #2229: 1: Success after binutils/gcc/gdb: 26 [...] discards c2517c0fce 407: onsuccess: #2228: 1: Success after binutils/gcc/linux/g [...] discards ab9b423ce6 406: onsuccess: #2227: 1: Success after binutils/linux/glibc [...] discards 47f1776e5b 405: onsuccess: #2226: 1: Success after gcc/glibc: 39 commits discards 7dc487011c 404: onsuccess: #2225: 1: Success after binutils/gcc/gdb: 10 [...] discards 2c9881b7cd 403: onsuccess: #2224: 1: Success after binutils/gcc/linux/g [...] discards df15115940 402: onsuccess: #2223: 1: Success after binutils/gcc/gdb: 10 [...] discards 74f1ed7ae8 401: onsuccess: #2222: 1: Success after binutils/gcc/gdb: 10 [...] discards e7189193ae 400: onsuccess: #2221: 1: Success after binutils/gcc/linux/g [...] discards a322d9bb94 399: onsuccess: #2220: 1: Success after binutils/gcc/linux/g [...] discards ee5448abf8 398: onsuccess: #2219: 1: Success after binutils/gcc/gdb/qem [...] discards e91ecb298e 397: onsuccess: #2218: 1: Success after binutils/gcc/linux/g [...] discards 8dee548d60 396: onsuccess: #2217: 1: Success after binutils/gcc/linux/g [...] discards e5fe39b22e 395: onsuccess: #2216: 1: Success after binutils/gcc/linux/g [...] discards 9e1e71a28f 394: onsuccess: #2215: 1: Success after binutils/gcc/gdb: 8 commits discards 0ac880b344 393: onsuccess: #2214: 1: Success after binutils/gcc/gdb: 12 [...] discards cb0a4f9bc1 392: onsuccess: #2213: 1: Success after binutils/gcc/glibc/g [...] discards 418ea6cb6c 391: onsuccess: #2212: 1: Success after binutils/gcc/gdb/qem [...] discards e6aeb4b611 390: onsuccess: #2211: 1: Success after binutils/gcc/linux/g [...] discards 02d8ad7c38 389: onsuccess: #2210: 1: Success after binutils/gcc/linux/g [...] discards bc60716d34 388: onsuccess: #2209: 1: Success after binutils/gcc/glibc/g [...] discards b30ddba791 387: onsuccess: #2208: 1: Success after gcc: 2 commits discards 98e7e46caf 386: onsuccess: #2207: 1: Success after binutils/gcc/linux/g [...] discards cea935a0a8 385: onsuccess: #2206: 1: Success after binutils/gcc/glibc/g [...] discards 1d32976ac8 384: onsuccess: #2205: 1: Success after gcc: 2 commits discards 39899d527a 383: onsuccess: #2204: 1: Success after binutils/gcc/linux/g [...] discards a820b0f42f 382: onsuccess: #2203: 1: Success after gcc/qemu: 42 commits discards ce74eff733 381: onsuccess: #2202: 1: Success after glibc-2.37.9000-17-g [...] discards 8507156890 380: onsuccess: #2201: 1: Success after binutils/gcc/linux/g [...] discards 9c9cd030b6 379: onsuccess: #2200: 1: Success after binutils/gcc/linux/g [...] discards 8ee0c0ef47 378: onsuccess: #2199: 1: Success after binutils/gdb: 4 commits discards a4a356a39c 377: onsuccess: #2198: 1: Success after binutils/gcc/gdb: 3 commits discards 5e10f0ffa2 376: onsuccess: #2197: 1: Success after binutils/gcc/linux/g [...] discards 40f4d100be 375: onsuccess: #2195: 1: Success after binutils/gcc/gdb/qem [...] discards 46e609cc74 374: onsuccess: #2194: 1: Success after binutils/gcc/linux/g [...] discards 6cde27a9b4 373: onsuccess: #2193: 1: Success after binutils/gcc/glibc/g [...] discards 323ddb73a4 372: onsuccess: #2192: 1: Success after binutils/gcc/linux/g [...] discards d4e80de6cd 371: onsuccess: #2191: 1: Success after binutils/gcc/gdb: 10 [...] discards 3d1000a218 370: onsuccess: #2190: 1: Success after binutils/gcc/linux/g [...] discards 2bedb599f4 369: onsuccess: #2189: 1: Success after binutils/gcc/linux/g [...] discards fb2947dda8 368: onsuccess: #2188: 1: Success after binutils/gcc/linux/g [...] discards b8ae3d6b30 367: onsuccess: #2187: 1: Success after binutils/gcc/gdb: 14 [...] discards f056f80b6d 366: onsuccess: #2186: 1: Success after binutils/gcc/linux/g [...] discards 819b8d9ed8 365: onsuccess: #2185: 1: Success after binutils/gcc/linux/g [...] discards a1ffa8b1db 364: onsuccess: #2184: 1: Success after binutils/gcc/linux/g [...] discards 3d5c2a70c4 363: onsuccess: #2183: 1: Success after binutils/gcc/linux/g [...] discards 3eb667295d 362: onsuccess: #2182: 1: Success after binutils/gcc/linux/g [...] discards 596c59f14a 361: onsuccess: #2181: 1: Success after binutils/gcc/linux/g [...] discards f2c1e2321e 360: onsuccess: #2180: 1: Success after binutils/gcc/linux/g [...] discards b6a12b423e 359: onsuccess: #2179: 1: Success after binutils/gcc/glibc/g [...] discards 9763145da0 358: onsuccess: #2178: 1: Success after binutils/gcc/linux/g [...] discards a4091c92b5 357: onsuccess: #2177: 1: Success after binutils/gcc/linux/g [...] discards a4dc00e2ed 356: onsuccess: #2176: 1: Success after binutils/gcc/linux/g [...] discards 903b26a5d0 355: onsuccess: #2175: 1: Success after binutils/gcc/linux/g [...] discards 5af6fe8a11 354: onsuccess: #2174: 1: Success after binutils/gcc/linux/g [...] discards b36d28e420 353: onsuccess: #2173: 1: Success after binutils/gcc/gdb: 27 [...] discards 2ac05b8bdb 352: onsuccess: #2172: 1: Success after binutils/gcc/linux/g [...] discards a212173448 351: onsuccess: #2171: 1: Success after gcc/linux: 15 commits discards 0bba164d0c 350: onsuccess: #2170: 1: Success after binutils/gcc/linux/g [...] discards 4de10e42e9 349: onsuccess: #2169: 1: Success after binutils/gcc/linux/g [...] discards ff2fa29e2a 348: onsuccess: #2168: 1: Success after binutils/gcc/gdb: 9 commits discards 641f1c2f66 347: onsuccess: #2167: 1: Success after basepoints/gcc-13-51 [...] discards 078b56b01d 346: onsuccess: #2166: 1: Success after binutils/gcc/linux/g [...] discards f3e821edd1 345: onsuccess: #2165: 1: Success after binutils/gcc/glibc/g [...] discards 00a10096c0 344: onsuccess: #2164: 1: Success after gcc/linux/glibc: 37 commits discards c1c57cd32c 343: onsuccess: #2163: 1: Success after binutils/gcc/gdb: 7 commits discards 764ca283e9 342: onsuccess: #2162: 1: Success after binutils/gcc/linux/g [...] discards f4b46e6b77 341: onsuccess: #2161: 1: Success after binutils/gcc/gdb: 11 [...] discards 984c6b2bb0 340: onsuccess: #2160: 1: Success after binutils/gcc/gdb: 15 [...] discards 89af15edb8 339: onsuccess: #2159: 1: Success after binutils/gcc/gdb: 4 commits discards f7359fc310 338: onsuccess: #2158: 1: Success after binutils/gcc/linux/g [...] discards a3c9f909e5 337: onsuccess: #2157: 1: Success after binutils/gcc/glibc/g [...] discards 382ee61bf5 336: onsuccess: #2156: 1: Success after binutils/gcc/linux/g [...] discards 4e2ca812da 335: onsuccess: #2155: 1: Success after binutils/gdb: 146 commits discards da69099a6e 334: onsuccess: #2154: 1: Success after binutils/gcc/linux/g [...] discards 9eb0be03fb 333: onsuccess: #2153: 1: Success after binutils/gcc/gdb/qem [...] discards 7ca406c7da 332: onsuccess: #2152: 1: Success after binutils/gcc/gdb/qem [...] discards b9f140ae30 331: onsuccess: #2151: 1: Success after binutils/gcc/linux/g [...] discards af51cce7fe 330: onsuccess: #2150: 1: Success after linux/qemu: 36 commits discards b5e9312f62 329: onsuccess: #2149: 1: Success after binutils/gcc/gdb/qem [...] discards 0c0495cb3c 328: onsuccess: #2148: 1: Success after gcc/linux/qemu: 78 commits discards 7e895c7292 327: onsuccess: #2147: 1: Success after basepoints/gcc-13-50 [...] discards 060b9a8770 326: onsuccess: #2146: 1: Success after binutils/gcc/linux/g [...] discards c1ed945d38 325: onsuccess: #2145: 1: Success after binutils/gcc/glibc/g [...] discards 64e1a40072 324: onsuccess: #2144: 1: Success after binutils/gcc/gdb/qem [...] new 5eb1d5c997 324: onsuccess: #2144: 1: Success after binutils/gcc/gdb/qem [...] new c58d873b41 325: onsuccess: #2145: 1: Success after binutils/gcc/glibc/g [...] new 83ffbeef5d 326: onsuccess: #2146: 1: Success after binutils/gcc/linux/g [...] new c6e06e088f 327: onsuccess: #2147: 1: Success after basepoints/gcc-13-50 [...] new 6e5ba423a5 328: onsuccess: #2148: 1: Success after gcc/linux/qemu: 78 commits new 0d766fc813 329: onsuccess: #2149: 1: Success after binutils/gcc/gdb/qem [...] new 41bc57f601 330: onsuccess: #2150: 1: Success after linux/qemu: 36 commits new e09d0104e4 331: onsuccess: #2151: 1: Success after binutils/gcc/linux/g [...] new 4ad0a500aa 332: onsuccess: #2152: 1: Success after binutils/gcc/gdb/qem [...] new 33962f4f13 333: onsuccess: #2153: 1: Success after binutils/gcc/gdb/qem [...] new 575ce00f65 334: onsuccess: #2154: 1: Success after binutils/gcc/linux/g [...] new d84db3e742 335: onsuccess: #2155: 1: Success after binutils/gdb: 146 commits new 9ce8ca30e7 336: onsuccess: #2156: 1: Success after binutils/gcc/linux/g [...] new 360890a1eb 337: onsuccess: #2157: 1: Success after binutils/gcc/glibc/g [...] new 2b962ac3ea 338: onsuccess: #2158: 1: Success after binutils/gcc/linux/g [...] new 77707dccef 339: onsuccess: #2159: 1: Success after binutils/gcc/gdb: 4 commits new d3600eac0a 340: onsuccess: #2160: 1: Success after binutils/gcc/gdb: 15 [...] new 8b1a6bceeb 341: onsuccess: #2161: 1: Success after binutils/gcc/gdb: 11 [...] new 863c5d88a0 342: onsuccess: #2162: 1: Success after binutils/gcc/linux/g [...] new 57322d592c 343: onsuccess: #2163: 1: Success after binutils/gcc/gdb: 7 commits new e132f294e5 344: onsuccess: #2164: 1: Success after gcc/linux/glibc: 37 commits new 9c42213f88 345: onsuccess: #2165: 1: Success after binutils/gcc/glibc/g [...] new 856d3cb619 346: onsuccess: #2166: 1: Success after binutils/gcc/linux/g [...] new fe096895a7 347: onsuccess: #2167: 1: Success after basepoints/gcc-13-51 [...] new 92f5d8cab9 348: onsuccess: #2168: 1: Success after binutils/gcc/gdb: 9 commits new 8f5e8f720c 349: onsuccess: #2169: 1: Success after binutils/gcc/linux/g [...] new bd598b7252 350: onsuccess: #2170: 1: Success after binutils/gcc/linux/g [...] new 20f8ccedf7 351: onsuccess: #2171: 1: Success after gcc/linux: 15 commits new ecab5a5788 352: onsuccess: #2172: 1: Success after binutils/gcc/linux/g [...] new 61905d4220 353: onsuccess: #2173: 1: Success after binutils/gcc/gdb: 27 [...] new 9e1f366146 354: onsuccess: #2174: 1: Success after binutils/gcc/linux/g [...] new 691c6733df 355: onsuccess: #2175: 1: Success after binutils/gcc/linux/g [...] new c5dffd3d23 356: onsuccess: #2176: 1: Success after binutils/gcc/linux/g [...] new b965e12feb 357: onsuccess: #2177: 1: Success after binutils/gcc/linux/g [...] new d01126b73f 358: onsuccess: #2178: 1: Success after binutils/gcc/linux/g [...] new 32e5fd3d44 359: onsuccess: #2179: 1: Success after binutils/gcc/glibc/g [...] new 3d780c2b1d 360: onsuccess: #2180: 1: Success after binutils/gcc/linux/g [...] new e2a3d28c8e 361: onsuccess: #2181: 1: Success after binutils/gcc/linux/g [...] new 6d02ecb872 362: onsuccess: #2182: 1: Success after binutils/gcc/linux/g [...] new 4a9be095eb 363: onsuccess: #2183: 1: Success after binutils/gcc/linux/g [...] new a10f49a861 364: onsuccess: #2184: 1: Success after binutils/gcc/linux/g [...] new 5295aeccaa 365: onsuccess: #2185: 1: Success after binutils/gcc/linux/g [...] new d6ef5a6b1a 366: onsuccess: #2186: 1: Success after binutils/gcc/linux/g [...] new 1c87320531 367: onsuccess: #2187: 1: Success after binutils/gcc/gdb: 14 [...] new a871af802c 368: onsuccess: #2188: 1: Success after binutils/gcc/linux/g [...] new a83aa9336b 369: onsuccess: #2189: 1: Success after binutils/gcc/linux/g [...] new d1862c8974 370: onsuccess: #2190: 1: Success after binutils/gcc/linux/g [...] new e0d03ccfd9 371: onsuccess: #2191: 1: Success after binutils/gcc/gdb: 10 [...] new a88a6fd40d 372: onsuccess: #2192: 1: Success after binutils/gcc/linux/g [...] new f7c055430b 373: onsuccess: #2193: 1: Success after binutils/gcc/glibc/g [...] new c40d86f154 374: onsuccess: #2194: 1: Success after binutils/gcc/linux/g [...] new eefadb2173 375: onsuccess: #2195: 1: Success after binutils/gcc/gdb/qem [...] new 0ad2fd616e 376: onsuccess: #2197: 1: Success after binutils/gcc/linux/g [...] new 0c26bde641 377: onsuccess: #2198: 1: Success after binutils/gcc/gdb: 3 commits new b53031cf96 378: onsuccess: #2199: 1: Success after binutils/gdb: 4 commits new 683e38d9f8 379: onsuccess: #2200: 1: Success after binutils/gcc/linux/g [...] new 39efca1325 380: onsuccess: #2201: 1: Success after binutils/gcc/linux/g [...] new 7f54bf90f0 381: onsuccess: #2202: 1: Success after glibc-2.37.9000-17-g [...] new 73e375a412 382: onsuccess: #2203: 1: Success after gcc/qemu: 42 commits new b1e7c90da7 383: onsuccess: #2204: 1: Success after binutils/gcc/linux/g [...] new adfdfcbd46 384: onsuccess: #2205: 1: Success after gcc: 2 commits new 630c81e67e 385: onsuccess: #2206: 1: Success after binutils/gcc/glibc/g [...] new be3a48d99d 386: onsuccess: #2207: 1: Success after binutils/gcc/linux/g [...] new 5a3dd44ae9 387: onsuccess: #2208: 1: Success after gcc: 2 commits new 48fcc72872 388: onsuccess: #2209: 1: Success after binutils/gcc/glibc/g [...] new bacbd186b6 389: onsuccess: #2210: 1: Success after binutils/gcc/linux/g [...] new 69f308d278 390: onsuccess: #2211: 1: Success after binutils/gcc/linux/g [...] new cd54e493e8 391: onsuccess: #2212: 1: Success after binutils/gcc/gdb/qem [...] new 2446b7a53d 392: onsuccess: #2213: 1: Success after binutils/gcc/glibc/g [...] new c99b99bc94 393: onsuccess: #2214: 1: Success after binutils/gcc/gdb: 12 [...] new 61f109605c 394: onsuccess: #2215: 1: Success after binutils/gcc/gdb: 8 commits new a5e3e25192 395: onsuccess: #2216: 1: Success after binutils/gcc/linux/g [...] new c8f7b5db08 396: onsuccess: #2217: 1: Success after binutils/gcc/linux/g [...] new 6b284b419a 397: onsuccess: #2218: 1: Success after binutils/gcc/linux/g [...] new 39154b3504 398: onsuccess: #2219: 1: Success after binutils/gcc/gdb/qem [...] new 46a156821e 399: onsuccess: #2220: 1: Success after binutils/gcc/linux/g [...] new 3c96c92111 400: onsuccess: #2221: 1: Success after binutils/gcc/linux/g [...] new 993111307d 401: onsuccess: #2222: 1: Success after binutils/gcc/gdb: 10 [...] new d21fae5786 402: onsuccess: #2223: 1: Success after binutils/gcc/gdb: 10 [...] new d4490ae95c 403: onsuccess: #2224: 1: Success after binutils/gcc/linux/g [...] new be0f01383c 404: onsuccess: #2225: 1: Success after binutils/gcc/gdb: 10 [...] new c252f8f7dd 405: onsuccess: #2226: 1: Success after gcc/glibc: 39 commits new 570a2f665c 406: onsuccess: #2227: 1: Success after binutils/linux/glibc [...] new 77271fc5c0 407: onsuccess: #2228: 1: Success after binutils/gcc/linux/g [...] new 5339ab7539 408: onsuccess: #2229: 1: Success after binutils/gcc/gdb: 26 [...] new 7e946c71dd 409: onsuccess: #2230: 1: Success after binutils/gcc/glibc/g [...] new a8b449034a 410: onsuccess: #2231: 1: Success after binutils/gcc/linux/g [...] new 7503bcd606 411: onsuccess: #2232: 1: Success after gcc: 3 commits new 27896a413c 412: onsuccess: #2233: 1: Success after binutils/gcc/glibc/g [...] new 4de89bdc9e 413: onsuccess: #2234: 1: Success after binutils/gcc/linux/g [...] new 0c8d0d86b4 414: onsuccess: #2235: 1: Success after binutils/gcc/gdb: 13 [...] new 9642dd9520 415: onsuccess: #2236: 1: Success after binutils/gcc/gdb: 14 [...] new 069784ad82 416: onsuccess: #2237: 1: Success after binutils/gcc/glibc/g [...] new 55ee382c18 417: onsuccess: #2238: 1: Success after binutils/gcc/linux/g [...] new e322f2742c 418: onsuccess: #2239: 1: Success after binutils/gcc/gdb: 5 commits new 17ddf2c63d 419: onsuccess: #2243: 1: Success after binutils/gcc/linux/g [...] new 6ba2f4e001 420: onsuccess: #2244: 1: Success after gcc/glibc: 5 commits new 4f93ab6abf 421: onsuccess: #2245: 1: Success after binutils/gcc/glibc/g [...] new a32d5f743f 422: onsuccess: #2246: 1: Success after binutils/gcc/linux/g [...] new 19d14ee57d 423: onsuccess: #2247: 1: Success after gcc/linux: 8 commits new df21c4916f 424: onsuccess: #2248: 1: Success after gcc: 6 commits new 498abcd238 425: onsuccess: #2249: 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 (4ce9722951) \ 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 1744 -> 1792 bytes 02-prepare_abe/console.log.xz | Bin 2764 -> 2768 bytes 03-build_abe-binutils/console.log.xz | Bin 30812 -> 30716 bytes 04-build_abe-stage1/console.log.xz | Bin 88664 -> 88836 bytes 06-build_abe-linux/console.log.xz | Bin 8688 -> 8636 bytes 07-build_abe-glibc/console.log.xz | Bin 235608 -> 235596 bytes 08-build_abe-stage2/console.log.xz | Bin 225568 -> 226892 bytes 09-build_abe-gdb/console.log.xz | Bin 38564 -> 38444 bytes 10-build_abe-qemu/console.log.xz | Bin 31064 -> 31552 bytes 11-build_abe-dejagnu/console.log.xz | Bin 3804 -> 3820 bytes 12-build_abe-check_gcc/console.log.xz | Bin 3000 -> 2600 bytes 13-check_regression/console.log.xz | Bin 5436 -> 6100 bytes 13-check_regression/results.compare | 16 ++++----- 13-check_regression/results.compare2 | 43 ++++++++++++----------- 14-update_baseline/console.log | 62 +++++++++++++++++----------------- 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 | 2 +- mail/mail-subject.txt | 2 +- manifest.sh | 38 ++++++++++----------- sumfiles/g++.log.xz | Bin 2635752 -> 2653516 bytes sumfiles/g++.sum | 10 ++++-- sumfiles/gcc.log.xz | Bin 2219068 -> 2182416 bytes sumfiles/gcc.sum | 2 +- sumfiles/gfortran.log.xz | Bin 893748 -> 896596 bytes sumfiles/gfortran.sum | 2 +- sumfiles/libatomic.log.xz | Bin 2268 -> 2260 bytes sumfiles/libatomic.sum | 2 +- sumfiles/libgomp.log.xz | Bin 217028 -> 217076 bytes sumfiles/libgomp.sum | 2 +- sumfiles/libitm.log.xz | Bin 2664 -> 2664 bytes sumfiles/libitm.sum | 2 +- sumfiles/libstdc++.log.xz | Bin 435540 -> 438072 bytes sumfiles/libstdc++.sum | 26 ++++++++------ 38 files changed, 116 insertions(+), 105 deletions(-)