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 2b0f1d4a23 446: onsuccess: #7: 1: Success after binutils/gcc/gdb: 5 commits discards 8ee6bde3d4 445: onsuccess: #6: 1: Success after binutils/gcc/linux/gdb: [...] discards 82e8ed4fe5 444: onsuccess: #5: 1: Success after binutils/gcc/linux/glib [...] discards b8462276d9 443: onsuccess: #4: 1: Success after binutils/gcc/gdb/qemu: [...] discards 47cdc66504 442: onsuccess: #3: 1: Success after binutils/gcc/glibc/gdb/ [...] discards 82aae6af3b 441: onsuccess: #2266: 1: Success after binutils/gcc/linux/g [...] discards e98bb923b5 440: onsuccess: #2265: 1: Success after binutils/gcc/linux/g [...] discards 2257328d24 439: onsuccess: #2264: 1: Success after binutils/gcc/gdb: 13 [...] discards 299f7b8578 438: onsuccess: #2263: 1: Success after binutils/gcc/linux/g [...] discards 5f653d9421 437: onsuccess: #2261: 1: Success after binutils/gcc/glibc/g [...] discards 053588ec9b 436: onsuccess: #2260: 1: Success after gcc: 7 commits discards 929f657564 435: onsuccess: #2259: 1: Success after binutils/gcc/linux/g [...] discards 9c9ee6615d 434: onsuccess: #2258: 1: Success after binutils/gcc/linux/g [...] discards 982168b996 433: onsuccess: #2257: 1: Success after binutils/gcc/gdb/qem [...] discards ca74fab321 432: onsuccess: #2256: 1: Success after binutils/gdb: 10 commits discards 8dfe9b217b 431: onsuccess: #2255: 1: Success after binutils/gcc/linux/g [...] discards 119d620dcc 430: onsuccess: #2254: 1: Success after binutils/gcc/linux/g [...] discards c5d9dc2586 429: onsuccess: #2253: 1: Success after binutils/gcc/glibc/g [...] discards 44ca3a31d6 428: onsuccess: #2252: 1: Success after binutils/gdb: 2 commits discards a903b624cd 427: onsuccess: #2251: 1: Success after binutils/gcc/linux/g [...] discards 938446f50e 426: onsuccess: #2250: 1: Success after binutils/linux/gdb: [...] discards 59d6f1ba83 425: onsuccess: #2249: 1: Success after binutils/gcc/linux/g [...] discards 4aafe7275a 424: onsuccess: #2248: 1: Success after gcc: 6 commits discards 2d53d767b7 423: onsuccess: #2247: 1: Success after gcc/linux: 8 commits discards 76575b9089 422: onsuccess: #2246: 1: Success after binutils/gcc/linux/g [...] discards 5591e12998 421: onsuccess: #2245: 1: Success after binutils/gcc/glibc/g [...] discards 93c959ff8f 420: onsuccess: #2244: 1: Success after gcc/glibc: 5 commits discards 7bd8312a08 419: onsuccess: #2243: 1: Success after binutils/gcc/linux/g [...] discards 5eecbc02c8 418: onsuccess: #2239: 1: Success after binutils/gcc/gdb: 5 commits discards de87dbfed3 417: onsuccess: #2238: 1: Success after binutils/gcc/linux/g [...] discards 18022bc7a0 416: onsuccess: #2237: 1: Success after binutils/gcc/glibc/g [...] discards ae71b3b220 415: onsuccess: #2236: 1: Success after binutils/gcc/gdb: 14 [...] discards dd85d03e51 414: onsuccess: #2235: 1: Success after binutils/gcc/gdb: 13 [...] discards f65fd67e92 413: onsuccess: #2234: 1: Success after binutils/gcc/linux/g [...] discards a4a714d33a 412: onsuccess: #2233: 1: Success after binutils/gcc/glibc/g [...] discards 11152f89a6 411: onsuccess: #2232: 1: Success after gcc: 3 commits discards 5a69d444d5 410: onsuccess: #2231: 1: Success after binutils/gcc/linux/g [...] discards ce35863055 409: onsuccess: #2230: 1: Success after binutils/gcc/glibc/g [...] discards 293ecac5df 408: onsuccess: #2229: 1: Success after binutils/gcc/gdb: 26 [...] discards 2677554357 407: onsuccess: #2228: 1: Success after binutils/gcc/linux/g [...] discards 808e7a7fa5 406: onsuccess: #2227: 1: Success after binutils/linux/glibc [...] discards d3b56d543f 405: onsuccess: #2226: 1: Success after gcc/glibc: 39 commits discards eb33def8cd 404: onsuccess: #2225: 1: Success after binutils/gcc/gdb: 10 [...] discards 2664c0d75b 403: onsuccess: #2224: 1: Success after binutils/gcc/linux/g [...] discards 6157264969 402: onsuccess: #2223: 1: Success after binutils/gcc/gdb: 10 [...] discards cfe8c94166 401: onsuccess: #2222: 1: Success after binutils/gcc/gdb: 10 [...] discards ebad69df73 400: onsuccess: #2221: 1: Success after binutils/gcc/linux/g [...] discards 7ed8b7bcbe 399: onsuccess: #2220: 1: Success after binutils/gcc/linux/g [...] discards f588a86b44 398: onsuccess: #2219: 1: Success after binutils/gcc/gdb/qem [...] discards 53db5619b0 397: onsuccess: #2218: 1: Success after binutils/gcc/linux/g [...] discards 927e311e00 396: onsuccess: #2217: 1: Success after binutils/gcc/linux/g [...] discards 8598b7400f 395: onsuccess: #2216: 1: Success after binutils/gcc/linux/g [...] discards b93921e24e 394: onsuccess: #2215: 1: Success after binutils/gcc/gdb: 8 commits discards 2375e38acc 393: onsuccess: #2214: 1: Success after binutils/gcc/gdb: 12 [...] discards e7bcf64411 392: onsuccess: #2213: 1: Success after binutils/gcc/glibc/g [...] discards 113fa0cd67 391: onsuccess: #2212: 1: Success after binutils/gcc/gdb/qem [...] discards bed3888c04 390: onsuccess: #2211: 1: Success after binutils/gcc/linux/g [...] discards 34c25c36c0 389: onsuccess: #2210: 1: Success after binutils/gcc/linux/g [...] discards 657f97b4d3 388: onsuccess: #2209: 1: Success after binutils/gcc/glibc/g [...] discards bf65b18abb 387: onsuccess: #2208: 1: Success after gcc: 2 commits discards 900606bf9b 386: onsuccess: #2207: 1: Success after binutils/gcc/linux/g [...] discards ea31de1762 385: onsuccess: #2206: 1: Success after binutils/gcc/glibc/g [...] discards 5e3a616f0d 384: onsuccess: #2205: 1: Success after gcc: 2 commits discards 8c6350018c 383: onsuccess: #2204: 1: Success after binutils/gcc/linux/g [...] discards ac29abce34 382: onsuccess: #2203: 1: Success after gcc/qemu: 42 commits discards 80061ea02d 381: onsuccess: #2202: 1: Success after glibc-2.37.9000-17-g [...] discards b267b83d48 380: onsuccess: #2201: 1: Success after binutils/gcc/linux/g [...] discards b8de4d421a 379: onsuccess: #2200: 1: Success after binutils/gcc/linux/g [...] discards 66c2788eb6 378: onsuccess: #2199: 1: Success after binutils/gdb: 4 commits discards 58645dfde4 377: onsuccess: #2198: 1: Success after binutils/gcc/gdb: 3 commits discards 509de468e9 376: onsuccess: #2197: 1: Success after binutils/gcc/linux/g [...] discards 74faad58ef 375: onsuccess: #2195: 1: Success after binutils/gcc/gdb/qem [...] discards 4d189abb2f 374: onsuccess: #2194: 1: Success after binutils/gcc/linux/g [...] discards ab1eaec31f 373: onsuccess: #2193: 1: Success after binutils/gcc/glibc/g [...] discards 1f67d4dfb1 372: onsuccess: #2192: 1: Success after binutils/gcc/linux/g [...] discards 0767b8ed1c 371: onsuccess: #2191: 1: Success after binutils/gcc/gdb: 10 [...] discards fd032fcf00 370: onsuccess: #2190: 1: Success after binutils/gcc/linux/g [...] discards f15b9d2a6d 369: onsuccess: #2189: 1: Success after binutils/gcc/linux/g [...] discards 6f8255714c 368: onsuccess: #2188: 1: Success after binutils/gcc/linux/g [...] discards f544661016 367: onsuccess: #2187: 1: Success after binutils/gcc/gdb: 14 [...] discards abf4d20fa0 366: onsuccess: #2186: 1: Success after binutils/gcc/linux/g [...] discards 33408c70db 365: onsuccess: #2185: 1: Success after binutils/gcc/linux/g [...] discards 458805039f 364: onsuccess: #2184: 1: Success after binutils/gcc/linux/g [...] discards cfbced5c64 363: onsuccess: #2183: 1: Success after binutils/gcc/linux/g [...] discards 8545d3fe74 362: onsuccess: #2182: 1: Success after binutils/gcc/linux/g [...] discards 7a1323cc61 361: onsuccess: #2181: 1: Success after binutils/gcc/linux/g [...] discards 575f560767 360: onsuccess: #2180: 1: Success after binutils/gcc/linux/g [...] discards 519bfcf2f2 359: onsuccess: #2179: 1: Success after binutils/gcc/glibc/g [...] discards 2694638eab 358: onsuccess: #2178: 1: Success after binutils/gcc/linux/g [...] discards a410e04cb9 357: onsuccess: #2177: 1: Success after binutils/gcc/linux/g [...] discards 117e398e58 356: onsuccess: #2176: 1: Success after binutils/gcc/linux/g [...] discards 893cefac7a 355: onsuccess: #2175: 1: Success after binutils/gcc/linux/g [...] discards 95cf71b389 354: onsuccess: #2174: 1: Success after binutils/gcc/linux/g [...] discards 9ba80d14ee 353: onsuccess: #2173: 1: Success after binutils/gcc/gdb: 27 [...] discards 05827aa2ef 352: onsuccess: #2172: 1: Success after binutils/gcc/linux/g [...] discards f849c1faad 351: onsuccess: #2171: 1: Success after gcc/linux: 15 commits discards e70a3cd49d 350: onsuccess: #2170: 1: Success after binutils/gcc/linux/g [...] discards 351a079a0f 349: onsuccess: #2169: 1: Success after binutils/gcc/linux/g [...] discards bf6b40d63e 348: onsuccess: #2168: 1: Success after binutils/gcc/gdb: 9 commits discards cccc9b47f0 347: onsuccess: #2167: 1: Success after basepoints/gcc-13-51 [...] discards ce92e1aafd 346: onsuccess: #2166: 1: Success after binutils/gcc/linux/g [...] new ce3570b12f 346: onsuccess: #2166: 1: Success after binutils/gcc/linux/g [...] new b12bf582ab 347: onsuccess: #2167: 1: Success after basepoints/gcc-13-51 [...] new 919c5aa18e 348: onsuccess: #2168: 1: Success after binutils/gcc/gdb: 9 commits new 9658622f56 349: onsuccess: #2169: 1: Success after binutils/gcc/linux/g [...] new 1b9130aed7 350: onsuccess: #2170: 1: Success after binutils/gcc/linux/g [...] new 71ef19d121 351: onsuccess: #2171: 1: Success after gcc/linux: 15 commits new 3d7e52e659 352: onsuccess: #2172: 1: Success after binutils/gcc/linux/g [...] new d546004bc2 353: onsuccess: #2173: 1: Success after binutils/gcc/gdb: 27 [...] new dd2cd3c961 354: onsuccess: #2174: 1: Success after binutils/gcc/linux/g [...] new 1027209506 355: onsuccess: #2175: 1: Success after binutils/gcc/linux/g [...] new 76a23c6f91 356: onsuccess: #2176: 1: Success after binutils/gcc/linux/g [...] new 575c2940f1 357: onsuccess: #2177: 1: Success after binutils/gcc/linux/g [...] new da798451e4 358: onsuccess: #2178: 1: Success after binutils/gcc/linux/g [...] new 0b7606d5c4 359: onsuccess: #2179: 1: Success after binutils/gcc/glibc/g [...] new b32e9c9c87 360: onsuccess: #2180: 1: Success after binutils/gcc/linux/g [...] new 6d53c58e7e 361: onsuccess: #2181: 1: Success after binutils/gcc/linux/g [...] new 9831156bdf 362: onsuccess: #2182: 1: Success after binutils/gcc/linux/g [...] new 2c01716e5e 363: onsuccess: #2183: 1: Success after binutils/gcc/linux/g [...] new 7d4f4fd77e 364: onsuccess: #2184: 1: Success after binutils/gcc/linux/g [...] new a3a8e9c052 365: onsuccess: #2185: 1: Success after binutils/gcc/linux/g [...] new 443856a9f0 366: onsuccess: #2186: 1: Success after binutils/gcc/linux/g [...] new fda8235400 367: onsuccess: #2187: 1: Success after binutils/gcc/gdb: 14 [...] new ff1a0b19b5 368: onsuccess: #2188: 1: Success after binutils/gcc/linux/g [...] new 42a4420cda 369: onsuccess: #2189: 1: Success after binutils/gcc/linux/g [...] new 1ee76399bf 370: onsuccess: #2190: 1: Success after binutils/gcc/linux/g [...] new 39d64ecfba 371: onsuccess: #2191: 1: Success after binutils/gcc/gdb: 10 [...] new 5a6591b882 372: onsuccess: #2192: 1: Success after binutils/gcc/linux/g [...] new 5ef0d3d076 373: onsuccess: #2193: 1: Success after binutils/gcc/glibc/g [...] new 583dafd672 374: onsuccess: #2194: 1: Success after binutils/gcc/linux/g [...] new c2dc59b20a 375: onsuccess: #2195: 1: Success after binutils/gcc/gdb/qem [...] new 1f27555ed7 376: onsuccess: #2197: 1: Success after binutils/gcc/linux/g [...] new f8aceef42c 377: onsuccess: #2198: 1: Success after binutils/gcc/gdb: 3 commits new 60a8b85a21 378: onsuccess: #2199: 1: Success after binutils/gdb: 4 commits new 4b7bcb94e5 379: onsuccess: #2200: 1: Success after binutils/gcc/linux/g [...] new 0052506390 380: onsuccess: #2201: 1: Success after binutils/gcc/linux/g [...] new 6d4f973077 381: onsuccess: #2202: 1: Success after glibc-2.37.9000-17-g [...] new fb7b517555 382: onsuccess: #2203: 1: Success after gcc/qemu: 42 commits new 96cb788fe9 383: onsuccess: #2204: 1: Success after binutils/gcc/linux/g [...] new ea5436ddeb 384: onsuccess: #2205: 1: Success after gcc: 2 commits new f7b4c9580a 385: onsuccess: #2206: 1: Success after binutils/gcc/glibc/g [...] new 5eafa2d90f 386: onsuccess: #2207: 1: Success after binutils/gcc/linux/g [...] new d110e67bbb 387: onsuccess: #2208: 1: Success after gcc: 2 commits new cb6476c724 388: onsuccess: #2209: 1: Success after binutils/gcc/glibc/g [...] new 62646f5156 389: onsuccess: #2210: 1: Success after binutils/gcc/linux/g [...] new f879e31d05 390: onsuccess: #2211: 1: Success after binutils/gcc/linux/g [...] new 26c51b1f53 391: onsuccess: #2212: 1: Success after binutils/gcc/gdb/qem [...] new 0aaa1cf779 392: onsuccess: #2213: 1: Success after binutils/gcc/glibc/g [...] new d422773094 393: onsuccess: #2214: 1: Success after binutils/gcc/gdb: 12 [...] new ec4ce8e7fc 394: onsuccess: #2215: 1: Success after binutils/gcc/gdb: 8 commits new 96b79189e0 395: onsuccess: #2216: 1: Success after binutils/gcc/linux/g [...] new 767c38f98c 396: onsuccess: #2217: 1: Success after binutils/gcc/linux/g [...] new 29b344de5e 397: onsuccess: #2218: 1: Success after binutils/gcc/linux/g [...] new 9130f579ab 398: onsuccess: #2219: 1: Success after binutils/gcc/gdb/qem [...] new 47e233cb46 399: onsuccess: #2220: 1: Success after binutils/gcc/linux/g [...] new c055bd9083 400: onsuccess: #2221: 1: Success after binutils/gcc/linux/g [...] new ab700410d2 401: onsuccess: #2222: 1: Success after binutils/gcc/gdb: 10 [...] new b60f809f12 402: onsuccess: #2223: 1: Success after binutils/gcc/gdb: 10 [...] new 897b2e4323 403: onsuccess: #2224: 1: Success after binutils/gcc/linux/g [...] new 11ed2447fc 404: onsuccess: #2225: 1: Success after binutils/gcc/gdb: 10 [...] new b6c6d821e9 405: onsuccess: #2226: 1: Success after gcc/glibc: 39 commits new 2e15827fcb 406: onsuccess: #2227: 1: Success after binutils/linux/glibc [...] new 7c89168556 407: onsuccess: #2228: 1: Success after binutils/gcc/linux/g [...] new 3f6b07fedd 408: onsuccess: #2229: 1: Success after binutils/gcc/gdb: 26 [...] new 2e5e6d8b32 409: onsuccess: #2230: 1: Success after binutils/gcc/glibc/g [...] new 67f37b9176 410: onsuccess: #2231: 1: Success after binutils/gcc/linux/g [...] new 947cfc4ead 411: onsuccess: #2232: 1: Success after gcc: 3 commits new ed5582f6dc 412: onsuccess: #2233: 1: Success after binutils/gcc/glibc/g [...] new c2fc8af697 413: onsuccess: #2234: 1: Success after binutils/gcc/linux/g [...] new d85457391b 414: onsuccess: #2235: 1: Success after binutils/gcc/gdb: 13 [...] new 37dd5c981f 415: onsuccess: #2236: 1: Success after binutils/gcc/gdb: 14 [...] new 1b4d2d8915 416: onsuccess: #2237: 1: Success after binutils/gcc/glibc/g [...] new d2e9d83532 417: onsuccess: #2238: 1: Success after binutils/gcc/linux/g [...] new 1369b40798 418: onsuccess: #2239: 1: Success after binutils/gcc/gdb: 5 commits new fb4316cd08 419: onsuccess: #2243: 1: Success after binutils/gcc/linux/g [...] new c0dfe218aa 420: onsuccess: #2244: 1: Success after gcc/glibc: 5 commits new 02c8596127 421: onsuccess: #2245: 1: Success after binutils/gcc/glibc/g [...] new ec86b4c1bb 422: onsuccess: #2246: 1: Success after binutils/gcc/linux/g [...] new b48e395a04 423: onsuccess: #2247: 1: Success after gcc/linux: 8 commits new 866dfcff68 424: onsuccess: #2248: 1: Success after gcc: 6 commits new d672b90ec5 425: onsuccess: #2249: 1: Success after binutils/gcc/linux/g [...] new b275d030bc 426: onsuccess: #2250: 1: Success after binutils/linux/gdb: [...] new 00e8128bce 427: onsuccess: #2251: 1: Success after binutils/gcc/linux/g [...] new 2109352b46 428: onsuccess: #2252: 1: Success after binutils/gdb: 2 commits new 0f900bd85b 429: onsuccess: #2253: 1: Success after binutils/gcc/glibc/g [...] new a8bb421173 430: onsuccess: #2254: 1: Success after binutils/gcc/linux/g [...] new de0a80c9ce 431: onsuccess: #2255: 1: Success after binutils/gcc/linux/g [...] new 87edefb503 432: onsuccess: #2256: 1: Success after binutils/gdb: 10 commits new 17439d6b91 433: onsuccess: #2257: 1: Success after binutils/gcc/gdb/qem [...] new 6e65d1e97a 434: onsuccess: #2258: 1: Success after binutils/gcc/linux/g [...] new cd1ca5a134 435: onsuccess: #2259: 1: Success after binutils/gcc/linux/g [...] new 8d6a184134 436: onsuccess: #2260: 1: Success after gcc: 7 commits new 97f5d92158 437: onsuccess: #2261: 1: Success after binutils/gcc/glibc/g [...] new 8cf8057cc5 438: onsuccess: #2263: 1: Success after binutils/gcc/linux/g [...] new f1ab7e2521 439: onsuccess: #2264: 1: Success after binutils/gcc/gdb: 13 [...] new 35cf41dcd5 440: onsuccess: #2265: 1: Success after binutils/gcc/linux/g [...] new 8182f08791 441: onsuccess: #2266: 1: Success after binutils/gcc/linux/g [...] new 947f713654 442: onsuccess: #3: 1: Success after binutils/gcc/glibc/gdb/ [...] new 8eb4d7efb5 443: onsuccess: #4: 1: Success after binutils/gcc/gdb/qemu: [...] new f1791fe97f 444: onsuccess: #5: 1: Success after binutils/gcc/linux/glib [...] new 0903f9169a 445: onsuccess: #6: 1: Success after binutils/gcc/linux/gdb: [...] new dcfad8c588 446: onsuccess: #7: 1: Success after binutils/gcc/gdb: 5 commits new 8d3711801a 447: onsuccess: #8: 1: Success after binutils/gcc/linux/glib [...]
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 (2b0f1d4a23) \ 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 1768 -> 1804 bytes 02-prepare_abe/console.log.xz | Bin 2772 -> 2780 bytes 03-build_abe-binutils/console.log.xz | Bin 30716 -> 30572 bytes 04-build_abe-stage1/console.log.xz | Bin 89960 -> 89392 bytes 06-build_abe-linux/console.log.xz | Bin 8532 -> 8812 bytes 07-build_abe-glibc/console.log.xz | Bin 235764 -> 235600 bytes 08-build_abe-stage2/console.log.xz | Bin 226128 -> 226308 bytes 09-build_abe-gdb/console.log.xz | Bin 38584 -> 38584 bytes 10-build_abe-qemu/console.log.xz | Bin 31828 -> 32052 bytes 11-build_abe-dejagnu/console.log.xz | Bin 3808 -> 3820 bytes 12-build_abe-check_gcc/console.log.xz | Bin 3280 -> 2604 bytes 13-check_regression/console.log.xz | Bin 5748 -> 50028 bytes 13-check_regression/mail-body.txt | 26 - 13-check_regression/results.compare | 30 +- 13-check_regression/results.compare2 | 5777 ++++++++++++++++++++++++++++++++- 14-update_baseline/console.log | 70 +- dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- git/gdb_rev | 2 +- git/glibc_rev | 2 +- git/linux_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 28 +- mail/mail-subject.txt | 2 +- manifest.sh | 44 +- sumfiles/g++.log.xz | Bin 2681356 -> 2646524 bytes sumfiles/g++.sum | 4284 ++++++++++++------------ sumfiles/gcc.log.xz | Bin 2214272 -> 2228808 bytes sumfiles/gcc.sum | 1438 ++++---- sumfiles/gfortran.log.xz | Bin 900348 -> 891408 bytes sumfiles/gfortran.sum | 8 +- sumfiles/libatomic.log.xz | Bin 2284 -> 2284 bytes sumfiles/libatomic.sum | 2 +- sumfiles/libgomp.log.xz | Bin 216832 -> 216916 bytes sumfiles/libgomp.sum | 2 +- sumfiles/libitm.log.xz | Bin 2688 -> 2688 bytes sumfiles/libitm.sum | 2 +- sumfiles/libstdc++.log.xz | Bin 446652 -> 439080 bytes 39 files changed, 8697 insertions(+), 3030 deletions(-)