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 498abcd238 425: onsuccess: #2249: 1: Success after binutils/gcc/linux/g [...] discards df21c4916f 424: onsuccess: #2248: 1: Success after gcc: 6 commits discards 19d14ee57d 423: onsuccess: #2247: 1: Success after gcc/linux: 8 commits discards a32d5f743f 422: onsuccess: #2246: 1: Success after binutils/gcc/linux/g [...] discards 4f93ab6abf 421: onsuccess: #2245: 1: Success after binutils/gcc/glibc/g [...] discards 6ba2f4e001 420: onsuccess: #2244: 1: Success after gcc/glibc: 5 commits discards 17ddf2c63d 419: onsuccess: #2243: 1: Success after binutils/gcc/linux/g [...] discards e322f2742c 418: onsuccess: #2239: 1: Success after binutils/gcc/gdb: 5 commits discards 55ee382c18 417: onsuccess: #2238: 1: Success after binutils/gcc/linux/g [...] discards 069784ad82 416: onsuccess: #2237: 1: Success after binutils/gcc/glibc/g [...] discards 9642dd9520 415: onsuccess: #2236: 1: Success after binutils/gcc/gdb: 14 [...] discards 0c8d0d86b4 414: onsuccess: #2235: 1: Success after binutils/gcc/gdb: 13 [...] discards 4de89bdc9e 413: onsuccess: #2234: 1: Success after binutils/gcc/linux/g [...] discards 27896a413c 412: onsuccess: #2233: 1: Success after binutils/gcc/glibc/g [...] discards 7503bcd606 411: onsuccess: #2232: 1: Success after gcc: 3 commits discards a8b449034a 410: onsuccess: #2231: 1: Success after binutils/gcc/linux/g [...] discards 7e946c71dd 409: onsuccess: #2230: 1: Success after binutils/gcc/glibc/g [...] discards 5339ab7539 408: onsuccess: #2229: 1: Success after binutils/gcc/gdb: 26 [...] discards 77271fc5c0 407: onsuccess: #2228: 1: Success after binutils/gcc/linux/g [...] discards 570a2f665c 406: onsuccess: #2227: 1: Success after binutils/linux/glibc [...] discards c252f8f7dd 405: onsuccess: #2226: 1: Success after gcc/glibc: 39 commits discards be0f01383c 404: onsuccess: #2225: 1: Success after binutils/gcc/gdb: 10 [...] discards d4490ae95c 403: onsuccess: #2224: 1: Success after binutils/gcc/linux/g [...] discards d21fae5786 402: onsuccess: #2223: 1: Success after binutils/gcc/gdb: 10 [...] discards 993111307d 401: onsuccess: #2222: 1: Success after binutils/gcc/gdb: 10 [...] discards 3c96c92111 400: onsuccess: #2221: 1: Success after binutils/gcc/linux/g [...] discards 46a156821e 399: onsuccess: #2220: 1: Success after binutils/gcc/linux/g [...] discards 39154b3504 398: onsuccess: #2219: 1: Success after binutils/gcc/gdb/qem [...] discards 6b284b419a 397: onsuccess: #2218: 1: Success after binutils/gcc/linux/g [...] discards c8f7b5db08 396: onsuccess: #2217: 1: Success after binutils/gcc/linux/g [...] discards a5e3e25192 395: onsuccess: #2216: 1: Success after binutils/gcc/linux/g [...] discards 61f109605c 394: onsuccess: #2215: 1: Success after binutils/gcc/gdb: 8 commits discards c99b99bc94 393: onsuccess: #2214: 1: Success after binutils/gcc/gdb: 12 [...] discards 2446b7a53d 392: onsuccess: #2213: 1: Success after binutils/gcc/glibc/g [...] discards cd54e493e8 391: onsuccess: #2212: 1: Success after binutils/gcc/gdb/qem [...] discards 69f308d278 390: onsuccess: #2211: 1: Success after binutils/gcc/linux/g [...] discards bacbd186b6 389: onsuccess: #2210: 1: Success after binutils/gcc/linux/g [...] discards 48fcc72872 388: onsuccess: #2209: 1: Success after binutils/gcc/glibc/g [...] discards 5a3dd44ae9 387: onsuccess: #2208: 1: Success after gcc: 2 commits discards be3a48d99d 386: onsuccess: #2207: 1: Success after binutils/gcc/linux/g [...] discards 630c81e67e 385: onsuccess: #2206: 1: Success after binutils/gcc/glibc/g [...] discards adfdfcbd46 384: onsuccess: #2205: 1: Success after gcc: 2 commits discards b1e7c90da7 383: onsuccess: #2204: 1: Success after binutils/gcc/linux/g [...] discards 73e375a412 382: onsuccess: #2203: 1: Success after gcc/qemu: 42 commits discards 7f54bf90f0 381: onsuccess: #2202: 1: Success after glibc-2.37.9000-17-g [...] discards 39efca1325 380: onsuccess: #2201: 1: Success after binutils/gcc/linux/g [...] discards 683e38d9f8 379: onsuccess: #2200: 1: Success after binutils/gcc/linux/g [...] discards b53031cf96 378: onsuccess: #2199: 1: Success after binutils/gdb: 4 commits discards 0c26bde641 377: onsuccess: #2198: 1: Success after binutils/gcc/gdb: 3 commits discards 0ad2fd616e 376: onsuccess: #2197: 1: Success after binutils/gcc/linux/g [...] discards eefadb2173 375: onsuccess: #2195: 1: Success after binutils/gcc/gdb/qem [...] discards c40d86f154 374: onsuccess: #2194: 1: Success after binutils/gcc/linux/g [...] discards f7c055430b 373: onsuccess: #2193: 1: Success after binutils/gcc/glibc/g [...] discards a88a6fd40d 372: onsuccess: #2192: 1: Success after binutils/gcc/linux/g [...] discards e0d03ccfd9 371: onsuccess: #2191: 1: Success after binutils/gcc/gdb: 10 [...] discards d1862c8974 370: onsuccess: #2190: 1: Success after binutils/gcc/linux/g [...] discards a83aa9336b 369: onsuccess: #2189: 1: Success after binutils/gcc/linux/g [...] discards a871af802c 368: onsuccess: #2188: 1: Success after binutils/gcc/linux/g [...] discards 1c87320531 367: onsuccess: #2187: 1: Success after binutils/gcc/gdb: 14 [...] discards d6ef5a6b1a 366: onsuccess: #2186: 1: Success after binutils/gcc/linux/g [...] discards 5295aeccaa 365: onsuccess: #2185: 1: Success after binutils/gcc/linux/g [...] discards a10f49a861 364: onsuccess: #2184: 1: Success after binutils/gcc/linux/g [...] discards 4a9be095eb 363: onsuccess: #2183: 1: Success after binutils/gcc/linux/g [...] discards 6d02ecb872 362: onsuccess: #2182: 1: Success after binutils/gcc/linux/g [...] discards e2a3d28c8e 361: onsuccess: #2181: 1: Success after binutils/gcc/linux/g [...] discards 3d780c2b1d 360: onsuccess: #2180: 1: Success after binutils/gcc/linux/g [...] discards 32e5fd3d44 359: onsuccess: #2179: 1: Success after binutils/gcc/glibc/g [...] discards d01126b73f 358: onsuccess: #2178: 1: Success after binutils/gcc/linux/g [...] discards b965e12feb 357: onsuccess: #2177: 1: Success after binutils/gcc/linux/g [...] discards c5dffd3d23 356: onsuccess: #2176: 1: Success after binutils/gcc/linux/g [...] discards 691c6733df 355: onsuccess: #2175: 1: Success after binutils/gcc/linux/g [...] discards 9e1f366146 354: onsuccess: #2174: 1: Success after binutils/gcc/linux/g [...] discards 61905d4220 353: onsuccess: #2173: 1: Success after binutils/gcc/gdb: 27 [...] discards ecab5a5788 352: onsuccess: #2172: 1: Success after binutils/gcc/linux/g [...] discards 20f8ccedf7 351: onsuccess: #2171: 1: Success after gcc/linux: 15 commits discards bd598b7252 350: onsuccess: #2170: 1: Success after binutils/gcc/linux/g [...] discards 8f5e8f720c 349: onsuccess: #2169: 1: Success after binutils/gcc/linux/g [...] discards 92f5d8cab9 348: onsuccess: #2168: 1: Success after binutils/gcc/gdb: 9 commits discards fe096895a7 347: onsuccess: #2167: 1: Success after basepoints/gcc-13-51 [...] discards 856d3cb619 346: onsuccess: #2166: 1: Success after binutils/gcc/linux/g [...] discards 9c42213f88 345: onsuccess: #2165: 1: Success after binutils/gcc/glibc/g [...] discards e132f294e5 344: onsuccess: #2164: 1: Success after gcc/linux/glibc: 37 commits discards 57322d592c 343: onsuccess: #2163: 1: Success after binutils/gcc/gdb: 7 commits discards 863c5d88a0 342: onsuccess: #2162: 1: Success after binutils/gcc/linux/g [...] discards 8b1a6bceeb 341: onsuccess: #2161: 1: Success after binutils/gcc/gdb: 11 [...] discards d3600eac0a 340: onsuccess: #2160: 1: Success after binutils/gcc/gdb: 15 [...] discards 77707dccef 339: onsuccess: #2159: 1: Success after binutils/gcc/gdb: 4 commits discards 2b962ac3ea 338: onsuccess: #2158: 1: Success after binutils/gcc/linux/g [...] discards 360890a1eb 337: onsuccess: #2157: 1: Success after binutils/gcc/glibc/g [...] discards 9ce8ca30e7 336: onsuccess: #2156: 1: Success after binutils/gcc/linux/g [...] discards d84db3e742 335: onsuccess: #2155: 1: Success after binutils/gdb: 146 commits discards 575ce00f65 334: onsuccess: #2154: 1: Success after binutils/gcc/linux/g [...] discards 33962f4f13 333: onsuccess: #2153: 1: Success after binutils/gcc/gdb/qem [...] discards 4ad0a500aa 332: onsuccess: #2152: 1: Success after binutils/gcc/gdb/qem [...] discards e09d0104e4 331: onsuccess: #2151: 1: Success after binutils/gcc/linux/g [...] discards 41bc57f601 330: onsuccess: #2150: 1: Success after linux/qemu: 36 commits discards 0d766fc813 329: onsuccess: #2149: 1: Success after binutils/gcc/gdb/qem [...] discards 6e5ba423a5 328: onsuccess: #2148: 1: Success after gcc/linux/qemu: 78 commits discards c6e06e088f 327: onsuccess: #2147: 1: Success after basepoints/gcc-13-50 [...] discards 83ffbeef5d 326: onsuccess: #2146: 1: Success after binutils/gcc/linux/g [...] discards c58d873b41 325: onsuccess: #2145: 1: Success after binutils/gcc/glibc/g [...] new 7d1fe0e81f 325: onsuccess: #2145: 1: Success after binutils/gcc/glibc/g [...] new 2c7c1916ae 326: onsuccess: #2146: 1: Success after binutils/gcc/linux/g [...] new 82bcc05dfd 327: onsuccess: #2147: 1: Success after basepoints/gcc-13-50 [...] new 1220891fab 328: onsuccess: #2148: 1: Success after gcc/linux/qemu: 78 commits new 5e64353637 329: onsuccess: #2149: 1: Success after binutils/gcc/gdb/qem [...] new f841ce8c1a 330: onsuccess: #2150: 1: Success after linux/qemu: 36 commits new 3be3db99f9 331: onsuccess: #2151: 1: Success after binutils/gcc/linux/g [...] new a17cd100d7 332: onsuccess: #2152: 1: Success after binutils/gcc/gdb/qem [...] new 661f57f352 333: onsuccess: #2153: 1: Success after binutils/gcc/gdb/qem [...] new a8d434b994 334: onsuccess: #2154: 1: Success after binutils/gcc/linux/g [...] new f3a38152b2 335: onsuccess: #2155: 1: Success after binutils/gdb: 146 commits new 4761796cf0 336: onsuccess: #2156: 1: Success after binutils/gcc/linux/g [...] new 8815287ec8 337: onsuccess: #2157: 1: Success after binutils/gcc/glibc/g [...] new 47aa5f9976 338: onsuccess: #2158: 1: Success after binutils/gcc/linux/g [...] new 3f2cf4a583 339: onsuccess: #2159: 1: Success after binutils/gcc/gdb: 4 commits new e27bd0074f 340: onsuccess: #2160: 1: Success after binutils/gcc/gdb: 15 [...] new 3106f70169 341: onsuccess: #2161: 1: Success after binutils/gcc/gdb: 11 [...] new f69c770382 342: onsuccess: #2162: 1: Success after binutils/gcc/linux/g [...] new dc7d54f7c2 343: onsuccess: #2163: 1: Success after binutils/gcc/gdb: 7 commits new bde0293683 344: onsuccess: #2164: 1: Success after gcc/linux/glibc: 37 commits new 38da302376 345: onsuccess: #2165: 1: Success after binutils/gcc/glibc/g [...] new aeddd858d8 346: onsuccess: #2166: 1: Success after binutils/gcc/linux/g [...] new 15c98beec4 347: onsuccess: #2167: 1: Success after basepoints/gcc-13-51 [...] new e986a7e4fe 348: onsuccess: #2168: 1: Success after binutils/gcc/gdb: 9 commits new 27284c465a 349: onsuccess: #2169: 1: Success after binutils/gcc/linux/g [...] new 667bfc232e 350: onsuccess: #2170: 1: Success after binutils/gcc/linux/g [...] new 9bb222045e 351: onsuccess: #2171: 1: Success after gcc/linux: 15 commits new 5c87ecbf91 352: onsuccess: #2172: 1: Success after binutils/gcc/linux/g [...] new 2c8f6a1183 353: onsuccess: #2173: 1: Success after binutils/gcc/gdb: 27 [...] new 310da26839 354: onsuccess: #2174: 1: Success after binutils/gcc/linux/g [...] new bd0700029d 355: onsuccess: #2175: 1: Success after binutils/gcc/linux/g [...] new eddcf7c93a 356: onsuccess: #2176: 1: Success after binutils/gcc/linux/g [...] new a6905bc5df 357: onsuccess: #2177: 1: Success after binutils/gcc/linux/g [...] new 1d5aba030d 358: onsuccess: #2178: 1: Success after binutils/gcc/linux/g [...] new 3a785f69ed 359: onsuccess: #2179: 1: Success after binutils/gcc/glibc/g [...] new ca0c275bfd 360: onsuccess: #2180: 1: Success after binutils/gcc/linux/g [...] new 138ab19bec 361: onsuccess: #2181: 1: Success after binutils/gcc/linux/g [...] new 0b43daf649 362: onsuccess: #2182: 1: Success after binutils/gcc/linux/g [...] new 51031aee17 363: onsuccess: #2183: 1: Success after binutils/gcc/linux/g [...] new f6d95ef2e7 364: onsuccess: #2184: 1: Success after binutils/gcc/linux/g [...] new 9ca2435bd9 365: onsuccess: #2185: 1: Success after binutils/gcc/linux/g [...] new bc6d28bd44 366: onsuccess: #2186: 1: Success after binutils/gcc/linux/g [...] new 72b5b74d1d 367: onsuccess: #2187: 1: Success after binutils/gcc/gdb: 14 [...] new 4e163cadbd 368: onsuccess: #2188: 1: Success after binutils/gcc/linux/g [...] new 7e5a1d967a 369: onsuccess: #2189: 1: Success after binutils/gcc/linux/g [...] new 2e98de4482 370: onsuccess: #2190: 1: Success after binutils/gcc/linux/g [...] new a92af0babd 371: onsuccess: #2191: 1: Success after binutils/gcc/gdb: 10 [...] new 8bdbf921c4 372: onsuccess: #2192: 1: Success after binutils/gcc/linux/g [...] new e527db9310 373: onsuccess: #2193: 1: Success after binutils/gcc/glibc/g [...] new cc28fb9cca 374: onsuccess: #2194: 1: Success after binutils/gcc/linux/g [...] new f7a0de936b 375: onsuccess: #2195: 1: Success after binutils/gcc/gdb/qem [...] new c5e6a27034 376: onsuccess: #2197: 1: Success after binutils/gcc/linux/g [...] new 890ef6d285 377: onsuccess: #2198: 1: Success after binutils/gcc/gdb: 3 commits new e1898d87fd 378: onsuccess: #2199: 1: Success after binutils/gdb: 4 commits new c7c94ee6af 379: onsuccess: #2200: 1: Success after binutils/gcc/linux/g [...] new 7d7cb4a3d2 380: onsuccess: #2201: 1: Success after binutils/gcc/linux/g [...] new 729bf50095 381: onsuccess: #2202: 1: Success after glibc-2.37.9000-17-g [...] new 9016e4b5d0 382: onsuccess: #2203: 1: Success after gcc/qemu: 42 commits new 4b82511133 383: onsuccess: #2204: 1: Success after binutils/gcc/linux/g [...] new d2766f8c65 384: onsuccess: #2205: 1: Success after gcc: 2 commits new 7438614779 385: onsuccess: #2206: 1: Success after binutils/gcc/glibc/g [...] new 9301d8df77 386: onsuccess: #2207: 1: Success after binutils/gcc/linux/g [...] new 7e7f7a515b 387: onsuccess: #2208: 1: Success after gcc: 2 commits new 6d023a0fd7 388: onsuccess: #2209: 1: Success after binutils/gcc/glibc/g [...] new de0da5fa36 389: onsuccess: #2210: 1: Success after binutils/gcc/linux/g [...] new 06c0b3c5d0 390: onsuccess: #2211: 1: Success after binutils/gcc/linux/g [...] new 597bf10627 391: onsuccess: #2212: 1: Success after binutils/gcc/gdb/qem [...] new ec5e9b96dd 392: onsuccess: #2213: 1: Success after binutils/gcc/glibc/g [...] new cccfee0ff3 393: onsuccess: #2214: 1: Success after binutils/gcc/gdb: 12 [...] new acfe8a619f 394: onsuccess: #2215: 1: Success after binutils/gcc/gdb: 8 commits new 71d27f7475 395: onsuccess: #2216: 1: Success after binutils/gcc/linux/g [...] new 6f882fb951 396: onsuccess: #2217: 1: Success after binutils/gcc/linux/g [...] new 2de79bc300 397: onsuccess: #2218: 1: Success after binutils/gcc/linux/g [...] new 4d82dce842 398: onsuccess: #2219: 1: Success after binutils/gcc/gdb/qem [...] new e4a551a457 399: onsuccess: #2220: 1: Success after binutils/gcc/linux/g [...] new f782fc078a 400: onsuccess: #2221: 1: Success after binutils/gcc/linux/g [...] new 4cafef3cfa 401: onsuccess: #2222: 1: Success after binutils/gcc/gdb: 10 [...] new be67cf8d8c 402: onsuccess: #2223: 1: Success after binutils/gcc/gdb: 10 [...] new 1cd923df48 403: onsuccess: #2224: 1: Success after binutils/gcc/linux/g [...] new fe2ef245ac 404: onsuccess: #2225: 1: Success after binutils/gcc/gdb: 10 [...] new 096be92b48 405: onsuccess: #2226: 1: Success after gcc/glibc: 39 commits new 9295205bb1 406: onsuccess: #2227: 1: Success after binutils/linux/glibc [...] new 89edd7e665 407: onsuccess: #2228: 1: Success after binutils/gcc/linux/g [...] new 8870eb1100 408: onsuccess: #2229: 1: Success after binutils/gcc/gdb: 26 [...] new af1087cc0b 409: onsuccess: #2230: 1: Success after binutils/gcc/glibc/g [...] new a80c0f303f 410: onsuccess: #2231: 1: Success after binutils/gcc/linux/g [...] new 906c534f92 411: onsuccess: #2232: 1: Success after gcc: 3 commits new 4aeeaf9d5d 412: onsuccess: #2233: 1: Success after binutils/gcc/glibc/g [...] new f39c3238b8 413: onsuccess: #2234: 1: Success after binutils/gcc/linux/g [...] new 1e665acee8 414: onsuccess: #2235: 1: Success after binutils/gcc/gdb: 13 [...] new 1e24b699eb 415: onsuccess: #2236: 1: Success after binutils/gcc/gdb: 14 [...] new 710c94f519 416: onsuccess: #2237: 1: Success after binutils/gcc/glibc/g [...] new d055369ee8 417: onsuccess: #2238: 1: Success after binutils/gcc/linux/g [...] new 8e833cc976 418: onsuccess: #2239: 1: Success after binutils/gcc/gdb: 5 commits new 4b4a29f708 419: onsuccess: #2243: 1: Success after binutils/gcc/linux/g [...] new 199859fc21 420: onsuccess: #2244: 1: Success after gcc/glibc: 5 commits new f225445b6f 421: onsuccess: #2245: 1: Success after binutils/gcc/glibc/g [...] new 3192377497 422: onsuccess: #2246: 1: Success after binutils/gcc/linux/g [...] new 4084a4b8b5 423: onsuccess: #2247: 1: Success after gcc/linux: 8 commits new 81ce79c054 424: onsuccess: #2248: 1: Success after gcc: 6 commits new 3858b0ab63 425: onsuccess: #2249: 1: Success after binutils/gcc/linux/g [...] new ca36886d84 426: onsuccess: #2250: 1: Success after binutils/linux/gdb: [...]
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 (498abcd238) \ 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 1792 -> 1752 bytes 02-prepare_abe/console.log.xz | Bin 2768 -> 2756 bytes 03-build_abe-binutils/console.log.xz | Bin 30716 -> 30696 bytes 04-build_abe-stage1/console.log.xz | Bin 88836 -> 88484 bytes 06-build_abe-linux/console.log.xz | Bin 8636 -> 8676 bytes 07-build_abe-glibc/console.log.xz | Bin 235596 -> 235496 bytes 08-build_abe-stage2/console.log.xz | Bin 226892 -> 225368 bytes 09-build_abe-gdb/console.log.xz | Bin 38444 -> 38424 bytes 10-build_abe-qemu/console.log.xz | Bin 31552 -> 31380 bytes 11-build_abe-dejagnu/console.log.xz | Bin 3820 -> 3848 bytes 12-build_abe-check_gcc/console.log.xz | Bin 2600 -> 2592 bytes 13-check_regression/console.log.xz | Bin 6100 -> 5716 bytes 13-check_regression/results.compare | 16 ++++----- 13-check_regression/results.compare2 | 33 +++++------------ 14-update_baseline/console.log | 66 +++++++++++++++++----------------- dashboard/dashboard-generate.sh | 2 +- git/binutils_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 | 30 ++++++++-------- sumfiles/g++.log.xz | Bin 2653516 -> 2673144 bytes sumfiles/gcc.log.xz | Bin 2182416 -> 2197560 bytes sumfiles/gfortran.log.xz | Bin 896596 -> 892940 bytes sumfiles/libatomic.log.xz | Bin 2260 -> 2260 bytes sumfiles/libatomic.sum | 2 +- sumfiles/libgomp.log.xz | Bin 217076 -> 216920 bytes sumfiles/libgomp.sum | 2 +- sumfiles/libitm.log.xz | Bin 2664 -> 2668 bytes sumfiles/libitm.sum | 2 +- sumfiles/libstdc++.log.xz | Bin 438072 -> 440472 bytes sumfiles/libstdc++.sum | 22 +++++------- 34 files changed, 83 insertions(+), 104 deletions(-)