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 748a2235c4 453: onsuccess: #14: 1: Success after binutils/gcc/linux/gdb [...] discards afd7a4a5e3 452: onsuccess: #13: 1: Success after binutils/gcc/linux/gli [...] discards 61f733a095 451: onsuccess: #12: 1: Success after binutils/gcc/linux/gli [...] discards b077ff71ed 450: onsuccess: #11: 1: Success after binutils/gcc/linux/gli [...] discards 0e72e90d64 449: onsuccess: #10: 1: Success after binutils/gcc/linux/gli [...] discards ef50081c72 448: onsuccess: #9: 1: Success after binutils/gcc/linux/gdb: [...] discards dfe2477465 447: onsuccess: #8: 1: Success after binutils/gcc/linux/glib [...] discards 0c9e50c264 446: onsuccess: #7: 1: Success after binutils/gcc/gdb: 5 commits discards 1cab6968bf 445: onsuccess: #6: 1: Success after binutils/gcc/linux/gdb: [...] discards 14f13a5b3c 444: onsuccess: #5: 1: Success after binutils/gcc/linux/glib [...] discards 7548fdc32a 443: onsuccess: #4: 1: Success after binutils/gcc/gdb/qemu: [...] discards 95afc72d36 442: onsuccess: #3: 1: Success after binutils/gcc/glibc/gdb/ [...] discards 9e9bfedfcb 441: onsuccess: #2266: 1: Success after binutils/gcc/linux/g [...] discards 28387d5cb8 440: onsuccess: #2265: 1: Success after binutils/gcc/linux/g [...] discards 1d712af7e3 439: onsuccess: #2264: 1: Success after binutils/gcc/gdb: 13 [...] discards 51b3ca4abe 438: onsuccess: #2263: 1: Success after binutils/gcc/linux/g [...] discards 50bcc7f751 437: onsuccess: #2261: 1: Success after binutils/gcc/glibc/g [...] discards 62afb95218 436: onsuccess: #2260: 1: Success after gcc: 7 commits discards 8730fff177 435: onsuccess: #2259: 1: Success after binutils/gcc/linux/g [...] discards 4cf306af03 434: onsuccess: #2258: 1: Success after binutils/gcc/linux/g [...] discards 7955342643 433: onsuccess: #2257: 1: Success after binutils/gcc/gdb/qem [...] discards adb09d9019 432: onsuccess: #2256: 1: Success after binutils/gdb: 10 commits discards f67d2a788c 431: onsuccess: #2255: 1: Success after binutils/gcc/linux/g [...] discards 2462fdc869 430: onsuccess: #2254: 1: Success after binutils/gcc/linux/g [...] discards c6518244d9 429: onsuccess: #2253: 1: Success after binutils/gcc/glibc/g [...] discards 83575c63da 428: onsuccess: #2252: 1: Success after binutils/gdb: 2 commits discards 0153505aae 427: onsuccess: #2251: 1: Success after binutils/gcc/linux/g [...] discards 306c4abb08 426: onsuccess: #2250: 1: Success after binutils/linux/gdb: [...] discards 656452efec 425: onsuccess: #2249: 1: Success after binutils/gcc/linux/g [...] discards f7a69f552e 424: onsuccess: #2248: 1: Success after gcc: 6 commits discards 0ce51c0963 423: onsuccess: #2247: 1: Success after gcc/linux: 8 commits discards fa9dc8e6d8 422: onsuccess: #2246: 1: Success after binutils/gcc/linux/g [...] discards e142674787 421: onsuccess: #2245: 1: Success after binutils/gcc/glibc/g [...] discards b4e001df3c 420: onsuccess: #2244: 1: Success after gcc/glibc: 5 commits discards 2b33df36f9 419: onsuccess: #2243: 1: Success after binutils/gcc/linux/g [...] discards fa9c3f6231 418: onsuccess: #2239: 1: Success after binutils/gcc/gdb: 5 commits discards ccff24a549 417: onsuccess: #2238: 1: Success after binutils/gcc/linux/g [...] discards 2abd003878 416: onsuccess: #2237: 1: Success after binutils/gcc/glibc/g [...] discards d8e9199393 415: onsuccess: #2236: 1: Success after binutils/gcc/gdb: 14 [...] discards d4ed78702d 414: onsuccess: #2235: 1: Success after binutils/gcc/gdb: 13 [...] discards a23c297e8d 413: onsuccess: #2234: 1: Success after binutils/gcc/linux/g [...] discards fe0740fc6b 412: onsuccess: #2233: 1: Success after binutils/gcc/glibc/g [...] discards fcb0f319de 411: onsuccess: #2232: 1: Success after gcc: 3 commits discards d1014d9f2d 410: onsuccess: #2231: 1: Success after binutils/gcc/linux/g [...] discards 38f235a69e 409: onsuccess: #2230: 1: Success after binutils/gcc/glibc/g [...] discards 7058df2a8a 408: onsuccess: #2229: 1: Success after binutils/gcc/gdb: 26 [...] discards 9dcfbfff36 407: onsuccess: #2228: 1: Success after binutils/gcc/linux/g [...] discards 0e7a05af5d 406: onsuccess: #2227: 1: Success after binutils/linux/glibc [...] discards 3437be9b7e 405: onsuccess: #2226: 1: Success after gcc/glibc: 39 commits discards 21f0226da9 404: onsuccess: #2225: 1: Success after binutils/gcc/gdb: 10 [...] discards 9697f14779 403: onsuccess: #2224: 1: Success after binutils/gcc/linux/g [...] discards 7189f9a264 402: onsuccess: #2223: 1: Success after binutils/gcc/gdb: 10 [...] discards c6ed99626f 401: onsuccess: #2222: 1: Success after binutils/gcc/gdb: 10 [...] discards 5e67c92efc 400: onsuccess: #2221: 1: Success after binutils/gcc/linux/g [...] discards 6771c0a811 399: onsuccess: #2220: 1: Success after binutils/gcc/linux/g [...] discards a939dca0f8 398: onsuccess: #2219: 1: Success after binutils/gcc/gdb/qem [...] discards 92b39d6cda 397: onsuccess: #2218: 1: Success after binutils/gcc/linux/g [...] discards a2be6ec40a 396: onsuccess: #2217: 1: Success after binutils/gcc/linux/g [...] discards 0834e961cb 395: onsuccess: #2216: 1: Success after binutils/gcc/linux/g [...] discards 1cc18353dc 394: onsuccess: #2215: 1: Success after binutils/gcc/gdb: 8 commits discards 5d6d045568 393: onsuccess: #2214: 1: Success after binutils/gcc/gdb: 12 [...] discards 2aa9768b3b 392: onsuccess: #2213: 1: Success after binutils/gcc/glibc/g [...] discards cad991d4df 391: onsuccess: #2212: 1: Success after binutils/gcc/gdb/qem [...] discards d55c170084 390: onsuccess: #2211: 1: Success after binutils/gcc/linux/g [...] discards a9a334b698 389: onsuccess: #2210: 1: Success after binutils/gcc/linux/g [...] discards 4b33868bf4 388: onsuccess: #2209: 1: Success after binutils/gcc/glibc/g [...] discards 7eb9b1f435 387: onsuccess: #2208: 1: Success after gcc: 2 commits discards d1818a8880 386: onsuccess: #2207: 1: Success after binutils/gcc/linux/g [...] discards 0e8998137a 385: onsuccess: #2206: 1: Success after binutils/gcc/glibc/g [...] discards f7c18ac657 384: onsuccess: #2205: 1: Success after gcc: 2 commits discards 080d66a69e 383: onsuccess: #2204: 1: Success after binutils/gcc/linux/g [...] discards 8ae7305c14 382: onsuccess: #2203: 1: Success after gcc/qemu: 42 commits discards 93565cfdef 381: onsuccess: #2202: 1: Success after glibc-2.37.9000-17-g [...] discards eb8405a3ab 380: onsuccess: #2201: 1: Success after binutils/gcc/linux/g [...] discards a3d4b35093 379: onsuccess: #2200: 1: Success after binutils/gcc/linux/g [...] discards 527e0fec84 378: onsuccess: #2199: 1: Success after binutils/gdb: 4 commits discards fc04cb0e9d 377: onsuccess: #2198: 1: Success after binutils/gcc/gdb: 3 commits discards f65c0c2d16 376: onsuccess: #2197: 1: Success after binutils/gcc/linux/g [...] discards 9bb85dad82 375: onsuccess: #2195: 1: Success after binutils/gcc/gdb/qem [...] discards 0bb5bc3b81 374: onsuccess: #2194: 1: Success after binutils/gcc/linux/g [...] discards 2d934731f7 373: onsuccess: #2193: 1: Success after binutils/gcc/glibc/g [...] discards 5ec4e7dabd 372: onsuccess: #2192: 1: Success after binutils/gcc/linux/g [...] discards 9295cf3c96 371: onsuccess: #2191: 1: Success after binutils/gcc/gdb: 10 [...] discards 011e8a68cb 370: onsuccess: #2190: 1: Success after binutils/gcc/linux/g [...] discards 1fc3bfa39f 369: onsuccess: #2189: 1: Success after binutils/gcc/linux/g [...] discards 5e81ce3915 368: onsuccess: #2188: 1: Success after binutils/gcc/linux/g [...] discards bfc02e1b04 367: onsuccess: #2187: 1: Success after binutils/gcc/gdb: 14 [...] discards 6932506bb3 366: onsuccess: #2186: 1: Success after binutils/gcc/linux/g [...] discards d07f31c525 365: onsuccess: #2185: 1: Success after binutils/gcc/linux/g [...] discards ad5bed1ed8 364: onsuccess: #2184: 1: Success after binutils/gcc/linux/g [...] discards 6179bc18f6 363: onsuccess: #2183: 1: Success after binutils/gcc/linux/g [...] discards fccafd40d4 362: onsuccess: #2182: 1: Success after binutils/gcc/linux/g [...] discards 296268604e 361: onsuccess: #2181: 1: Success after binutils/gcc/linux/g [...] discards db04905c38 360: onsuccess: #2180: 1: Success after binutils/gcc/linux/g [...] discards 7fe0b87e5e 359: onsuccess: #2179: 1: Success after binutils/gcc/glibc/g [...] discards 8462281a8e 358: onsuccess: #2178: 1: Success after binutils/gcc/linux/g [...] discards d1f2278a46 357: onsuccess: #2177: 1: Success after binutils/gcc/linux/g [...] discards 010cff6ced 356: onsuccess: #2176: 1: Success after binutils/gcc/linux/g [...] discards ccec1214f6 355: onsuccess: #2175: 1: Success after binutils/gcc/linux/g [...] discards 435d5fa230 354: onsuccess: #2174: 1: Success after binutils/gcc/linux/g [...] discards 938acc8f2f 353: onsuccess: #2173: 1: Success after binutils/gcc/gdb: 27 [...] new 794777dd74 353: onsuccess: #2173: 1: Success after binutils/gcc/gdb: 27 [...] new 6f25a62bcc 354: onsuccess: #2174: 1: Success after binutils/gcc/linux/g [...] new f8497c754d 355: onsuccess: #2175: 1: Success after binutils/gcc/linux/g [...] new c4af39374d 356: onsuccess: #2176: 1: Success after binutils/gcc/linux/g [...] new 5b3c36a174 357: onsuccess: #2177: 1: Success after binutils/gcc/linux/g [...] new 8be6aa1cf2 358: onsuccess: #2178: 1: Success after binutils/gcc/linux/g [...] new ae231fd542 359: onsuccess: #2179: 1: Success after binutils/gcc/glibc/g [...] new 448696617d 360: onsuccess: #2180: 1: Success after binutils/gcc/linux/g [...] new 2eaae15d3f 361: onsuccess: #2181: 1: Success after binutils/gcc/linux/g [...] new 7242dcfcde 362: onsuccess: #2182: 1: Success after binutils/gcc/linux/g [...] new 548e5f2fcc 363: onsuccess: #2183: 1: Success after binutils/gcc/linux/g [...] new 9cd09504a4 364: onsuccess: #2184: 1: Success after binutils/gcc/linux/g [...] new 5f5b8b3a80 365: onsuccess: #2185: 1: Success after binutils/gcc/linux/g [...] new 198516bcf9 366: onsuccess: #2186: 1: Success after binutils/gcc/linux/g [...] new 182cc70931 367: onsuccess: #2187: 1: Success after binutils/gcc/gdb: 14 [...] new 3121cd9021 368: onsuccess: #2188: 1: Success after binutils/gcc/linux/g [...] new 237f81c70a 369: onsuccess: #2189: 1: Success after binutils/gcc/linux/g [...] new 5653a604d4 370: onsuccess: #2190: 1: Success after binutils/gcc/linux/g [...] new d8db32cc4e 371: onsuccess: #2191: 1: Success after binutils/gcc/gdb: 10 [...] new bcc60fc975 372: onsuccess: #2192: 1: Success after binutils/gcc/linux/g [...] new 47f04d3d91 373: onsuccess: #2193: 1: Success after binutils/gcc/glibc/g [...] new b7eee48f9d 374: onsuccess: #2194: 1: Success after binutils/gcc/linux/g [...] new e74ae0bfa3 375: onsuccess: #2195: 1: Success after binutils/gcc/gdb/qem [...] new 02bee69528 376: onsuccess: #2197: 1: Success after binutils/gcc/linux/g [...] new 6c65066d61 377: onsuccess: #2198: 1: Success after binutils/gcc/gdb: 3 commits new 735391bf6b 378: onsuccess: #2199: 1: Success after binutils/gdb: 4 commits new 734264c966 379: onsuccess: #2200: 1: Success after binutils/gcc/linux/g [...] new dc23d2b71d 380: onsuccess: #2201: 1: Success after binutils/gcc/linux/g [...] new 9485337e62 381: onsuccess: #2202: 1: Success after glibc-2.37.9000-17-g [...] new 14db2a11d4 382: onsuccess: #2203: 1: Success after gcc/qemu: 42 commits new 9912d470cf 383: onsuccess: #2204: 1: Success after binutils/gcc/linux/g [...] new 7ee74609f1 384: onsuccess: #2205: 1: Success after gcc: 2 commits new 43c7bc9320 385: onsuccess: #2206: 1: Success after binutils/gcc/glibc/g [...] new 7f109d8e14 386: onsuccess: #2207: 1: Success after binutils/gcc/linux/g [...] new 5fb1704d69 387: onsuccess: #2208: 1: Success after gcc: 2 commits new 69f6b08712 388: onsuccess: #2209: 1: Success after binutils/gcc/glibc/g [...] new afbdb6ec0e 389: onsuccess: #2210: 1: Success after binutils/gcc/linux/g [...] new 629bb80b88 390: onsuccess: #2211: 1: Success after binutils/gcc/linux/g [...] new d38b58a85d 391: onsuccess: #2212: 1: Success after binutils/gcc/gdb/qem [...] new bbf24a558b 392: onsuccess: #2213: 1: Success after binutils/gcc/glibc/g [...] new 2d8c363583 393: onsuccess: #2214: 1: Success after binutils/gcc/gdb: 12 [...] new 449b9b7e6e 394: onsuccess: #2215: 1: Success after binutils/gcc/gdb: 8 commits new 84587ec7e2 395: onsuccess: #2216: 1: Success after binutils/gcc/linux/g [...] new 13b22c2658 396: onsuccess: #2217: 1: Success after binutils/gcc/linux/g [...] new be7914e106 397: onsuccess: #2218: 1: Success after binutils/gcc/linux/g [...] new e715ac45ec 398: onsuccess: #2219: 1: Success after binutils/gcc/gdb/qem [...] new 527e68561c 399: onsuccess: #2220: 1: Success after binutils/gcc/linux/g [...] new ed1576be85 400: onsuccess: #2221: 1: Success after binutils/gcc/linux/g [...] new 71846a94a5 401: onsuccess: #2222: 1: Success after binutils/gcc/gdb: 10 [...] new 435edd69b4 402: onsuccess: #2223: 1: Success after binutils/gcc/gdb: 10 [...] new e72f22a01d 403: onsuccess: #2224: 1: Success after binutils/gcc/linux/g [...] new ee32df3180 404: onsuccess: #2225: 1: Success after binutils/gcc/gdb: 10 [...] new 1e39cfcf6f 405: onsuccess: #2226: 1: Success after gcc/glibc: 39 commits new 4765e11cee 406: onsuccess: #2227: 1: Success after binutils/linux/glibc [...] new dad26cae85 407: onsuccess: #2228: 1: Success after binutils/gcc/linux/g [...] new a40bc9e971 408: onsuccess: #2229: 1: Success after binutils/gcc/gdb: 26 [...] new 512bd9bef0 409: onsuccess: #2230: 1: Success after binutils/gcc/glibc/g [...] new 72ded951a4 410: onsuccess: #2231: 1: Success after binutils/gcc/linux/g [...] new 9994dc84c9 411: onsuccess: #2232: 1: Success after gcc: 3 commits new af36ac72de 412: onsuccess: #2233: 1: Success after binutils/gcc/glibc/g [...] new d35892493c 413: onsuccess: #2234: 1: Success after binutils/gcc/linux/g [...] new b21c11ac2c 414: onsuccess: #2235: 1: Success after binutils/gcc/gdb: 13 [...] new 4ea1168eae 415: onsuccess: #2236: 1: Success after binutils/gcc/gdb: 14 [...] new 0d3685c6ea 416: onsuccess: #2237: 1: Success after binutils/gcc/glibc/g [...] new 8529dd7e5d 417: onsuccess: #2238: 1: Success after binutils/gcc/linux/g [...] new b9a90c922a 418: onsuccess: #2239: 1: Success after binutils/gcc/gdb: 5 commits new 5f16606b37 419: onsuccess: #2243: 1: Success after binutils/gcc/linux/g [...] new a608a74801 420: onsuccess: #2244: 1: Success after gcc/glibc: 5 commits new d96d7b3f8e 421: onsuccess: #2245: 1: Success after binutils/gcc/glibc/g [...] new efc51568fb 422: onsuccess: #2246: 1: Success after binutils/gcc/linux/g [...] new 0e81812be4 423: onsuccess: #2247: 1: Success after gcc/linux: 8 commits new 51b33a54ba 424: onsuccess: #2248: 1: Success after gcc: 6 commits new 52ccaebe17 425: onsuccess: #2249: 1: Success after binutils/gcc/linux/g [...] new db9ddc167d 426: onsuccess: #2250: 1: Success after binutils/linux/gdb: [...] new dd3736aac0 427: onsuccess: #2251: 1: Success after binutils/gcc/linux/g [...] new 3c71ddb267 428: onsuccess: #2252: 1: Success after binutils/gdb: 2 commits new 292f90be8d 429: onsuccess: #2253: 1: Success after binutils/gcc/glibc/g [...] new a4ca3c20ba 430: onsuccess: #2254: 1: Success after binutils/gcc/linux/g [...] new 51a9a53c5d 431: onsuccess: #2255: 1: Success after binutils/gcc/linux/g [...] new 102deaf9ba 432: onsuccess: #2256: 1: Success after binutils/gdb: 10 commits new 41a9c803fd 433: onsuccess: #2257: 1: Success after binutils/gcc/gdb/qem [...] new c8de22a258 434: onsuccess: #2258: 1: Success after binutils/gcc/linux/g [...] new 46870f7e6b 435: onsuccess: #2259: 1: Success after binutils/gcc/linux/g [...] new 3457aec04e 436: onsuccess: #2260: 1: Success after gcc: 7 commits new a4f14b0c27 437: onsuccess: #2261: 1: Success after binutils/gcc/glibc/g [...] new f2d7c90990 438: onsuccess: #2263: 1: Success after binutils/gcc/linux/g [...] new 1b3d5a6c0e 439: onsuccess: #2264: 1: Success after binutils/gcc/gdb: 13 [...] new b463e7ae33 440: onsuccess: #2265: 1: Success after binutils/gcc/linux/g [...] new c7af27787e 441: onsuccess: #2266: 1: Success after binutils/gcc/linux/g [...] new 3b2ccbd662 442: onsuccess: #3: 1: Success after binutils/gcc/glibc/gdb/ [...] new 1c58980412 443: onsuccess: #4: 1: Success after binutils/gcc/gdb/qemu: [...] new 944073b812 444: onsuccess: #5: 1: Success after binutils/gcc/linux/glib [...] new e23a229b74 445: onsuccess: #6: 1: Success after binutils/gcc/linux/gdb: [...] new 06e93b31e5 446: onsuccess: #7: 1: Success after binutils/gcc/gdb: 5 commits new dad639e5f2 447: onsuccess: #8: 1: Success after binutils/gcc/linux/glib [...] new d45d15a075 448: onsuccess: #9: 1: Success after binutils/gcc/linux/gdb: [...] new 24917979dd 449: onsuccess: #10: 1: Success after binutils/gcc/linux/gli [...] new 2d49eacaaa 450: onsuccess: #11: 1: Success after binutils/gcc/linux/gli [...] new b3690059a1 451: onsuccess: #12: 1: Success after binutils/gcc/linux/gli [...] new adc84a9a91 452: onsuccess: #13: 1: Success after binutils/gcc/linux/gli [...] new 545d599573 453: onsuccess: #14: 1: Success after binutils/gcc/linux/gdb [...] new 992da3040b 454: onsuccess: #15: 1: Success after binutils/gcc/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 (748a2235c4) \ 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 1756 -> 1768 bytes 02-prepare_abe/console.log.xz | Bin 2792 -> 2768 bytes 03-build_abe-binutils/console.log.xz | Bin 30836 -> 30900 bytes 04-build_abe-stage1/console.log.xz | Bin 89544 -> 89544 bytes 05-clean_sysroot/console.log.xz | Bin 332 -> 332 bytes 06-build_abe-linux/console.log.xz | Bin 8604 -> 8520 bytes 07-build_abe-glibc/console.log.xz | Bin 236688 -> 236640 bytes 08-build_abe-stage2/console.log.xz | Bin 225708 -> 225772 bytes 09-build_abe-gdb/console.log.xz | Bin 37940 -> 38596 bytes 10-build_abe-qemu/console.log.xz | Bin 32020 -> 30824 bytes 11-build_abe-dejagnu/console.log.xz | Bin 3796 -> 3792 bytes 12-build_abe-check_gcc/console.log.xz | Bin 2988 -> 2580 bytes 13-check_regression/console.log.xz | Bin 14172 -> 6712 bytes 13-check_regression/results.compare | 948 +------------------------ 13-check_regression/results.compare2 | 1219 +++------------------------------ 14-update_baseline/console.log | 64 +- dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- git/gdb_rev | 2 +- git/linux_rev | 2 +- git/qemu_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 2 +- mail/mail-subject.txt | 2 +- manifest.sh | 42 +- sumfiles/g++.log.xz | Bin 2659808 -> 2677708 bytes sumfiles/g++.sum | 176 +++-- sumfiles/gcc.log.xz | Bin 2232928 -> 2207000 bytes sumfiles/gcc.sum | 368 +++++----- sumfiles/gfortran.log.xz | Bin 893808 -> 899736 bytes sumfiles/gfortran.sum | 38 +- sumfiles/libatomic.log.xz | Bin 2276 -> 2284 bytes sumfiles/libatomic.sum | 4 +- sumfiles/libgomp.log.xz | Bin 217052 -> 217060 bytes sumfiles/libgomp.sum | 16 +- sumfiles/libitm.log.xz | Bin 2692 -> 2696 bytes sumfiles/libitm.sum | 6 +- sumfiles/libstdc++.log.xz | Bin 445516 -> 447032 bytes sumfiles/libstdc++.sum | 8 +- 40 files changed, 529 insertions(+), 2378 deletions(-)