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 8d3711801a 447: onsuccess: #8: 1: Success after binutils/gcc/linux/glib [...] discards dcfad8c588 446: onsuccess: #7: 1: Success after binutils/gcc/gdb: 5 commits discards 0903f9169a 445: onsuccess: #6: 1: Success after binutils/gcc/linux/gdb: [...] discards f1791fe97f 444: onsuccess: #5: 1: Success after binutils/gcc/linux/glib [...] discards 8eb4d7efb5 443: onsuccess: #4: 1: Success after binutils/gcc/gdb/qemu: [...] discards 947f713654 442: onsuccess: #3: 1: Success after binutils/gcc/glibc/gdb/ [...] discards 8182f08791 441: onsuccess: #2266: 1: Success after binutils/gcc/linux/g [...] discards 35cf41dcd5 440: onsuccess: #2265: 1: Success after binutils/gcc/linux/g [...] discards f1ab7e2521 439: onsuccess: #2264: 1: Success after binutils/gcc/gdb: 13 [...] discards 8cf8057cc5 438: onsuccess: #2263: 1: Success after binutils/gcc/linux/g [...] discards 97f5d92158 437: onsuccess: #2261: 1: Success after binutils/gcc/glibc/g [...] discards 8d6a184134 436: onsuccess: #2260: 1: Success after gcc: 7 commits discards cd1ca5a134 435: onsuccess: #2259: 1: Success after binutils/gcc/linux/g [...] discards 6e65d1e97a 434: onsuccess: #2258: 1: Success after binutils/gcc/linux/g [...] discards 17439d6b91 433: onsuccess: #2257: 1: Success after binutils/gcc/gdb/qem [...] discards 87edefb503 432: onsuccess: #2256: 1: Success after binutils/gdb: 10 commits discards de0a80c9ce 431: onsuccess: #2255: 1: Success after binutils/gcc/linux/g [...] discards a8bb421173 430: onsuccess: #2254: 1: Success after binutils/gcc/linux/g [...] discards 0f900bd85b 429: onsuccess: #2253: 1: Success after binutils/gcc/glibc/g [...] discards 2109352b46 428: onsuccess: #2252: 1: Success after binutils/gdb: 2 commits discards 00e8128bce 427: onsuccess: #2251: 1: Success after binutils/gcc/linux/g [...] discards b275d030bc 426: onsuccess: #2250: 1: Success after binutils/linux/gdb: [...] discards d672b90ec5 425: onsuccess: #2249: 1: Success after binutils/gcc/linux/g [...] discards 866dfcff68 424: onsuccess: #2248: 1: Success after gcc: 6 commits discards b48e395a04 423: onsuccess: #2247: 1: Success after gcc/linux: 8 commits discards ec86b4c1bb 422: onsuccess: #2246: 1: Success after binutils/gcc/linux/g [...] discards 02c8596127 421: onsuccess: #2245: 1: Success after binutils/gcc/glibc/g [...] discards c0dfe218aa 420: onsuccess: #2244: 1: Success after gcc/glibc: 5 commits discards fb4316cd08 419: onsuccess: #2243: 1: Success after binutils/gcc/linux/g [...] discards 1369b40798 418: onsuccess: #2239: 1: Success after binutils/gcc/gdb: 5 commits discards d2e9d83532 417: onsuccess: #2238: 1: Success after binutils/gcc/linux/g [...] discards 1b4d2d8915 416: onsuccess: #2237: 1: Success after binutils/gcc/glibc/g [...] discards 37dd5c981f 415: onsuccess: #2236: 1: Success after binutils/gcc/gdb: 14 [...] discards d85457391b 414: onsuccess: #2235: 1: Success after binutils/gcc/gdb: 13 [...] discards c2fc8af697 413: onsuccess: #2234: 1: Success after binutils/gcc/linux/g [...] discards ed5582f6dc 412: onsuccess: #2233: 1: Success after binutils/gcc/glibc/g [...] discards 947cfc4ead 411: onsuccess: #2232: 1: Success after gcc: 3 commits discards 67f37b9176 410: onsuccess: #2231: 1: Success after binutils/gcc/linux/g [...] discards 2e5e6d8b32 409: onsuccess: #2230: 1: Success after binutils/gcc/glibc/g [...] discards 3f6b07fedd 408: onsuccess: #2229: 1: Success after binutils/gcc/gdb: 26 [...] discards 7c89168556 407: onsuccess: #2228: 1: Success after binutils/gcc/linux/g [...] discards 2e15827fcb 406: onsuccess: #2227: 1: Success after binutils/linux/glibc [...] discards b6c6d821e9 405: onsuccess: #2226: 1: Success after gcc/glibc: 39 commits discards 11ed2447fc 404: onsuccess: #2225: 1: Success after binutils/gcc/gdb: 10 [...] discards 897b2e4323 403: onsuccess: #2224: 1: Success after binutils/gcc/linux/g [...] discards b60f809f12 402: onsuccess: #2223: 1: Success after binutils/gcc/gdb: 10 [...] discards ab700410d2 401: onsuccess: #2222: 1: Success after binutils/gcc/gdb: 10 [...] discards c055bd9083 400: onsuccess: #2221: 1: Success after binutils/gcc/linux/g [...] discards 47e233cb46 399: onsuccess: #2220: 1: Success after binutils/gcc/linux/g [...] discards 9130f579ab 398: onsuccess: #2219: 1: Success after binutils/gcc/gdb/qem [...] discards 29b344de5e 397: onsuccess: #2218: 1: Success after binutils/gcc/linux/g [...] discards 767c38f98c 396: onsuccess: #2217: 1: Success after binutils/gcc/linux/g [...] discards 96b79189e0 395: onsuccess: #2216: 1: Success after binutils/gcc/linux/g [...] discards ec4ce8e7fc 394: onsuccess: #2215: 1: Success after binutils/gcc/gdb: 8 commits discards d422773094 393: onsuccess: #2214: 1: Success after binutils/gcc/gdb: 12 [...] discards 0aaa1cf779 392: onsuccess: #2213: 1: Success after binutils/gcc/glibc/g [...] discards 26c51b1f53 391: onsuccess: #2212: 1: Success after binutils/gcc/gdb/qem [...] discards f879e31d05 390: onsuccess: #2211: 1: Success after binutils/gcc/linux/g [...] discards 62646f5156 389: onsuccess: #2210: 1: Success after binutils/gcc/linux/g [...] discards cb6476c724 388: onsuccess: #2209: 1: Success after binutils/gcc/glibc/g [...] discards d110e67bbb 387: onsuccess: #2208: 1: Success after gcc: 2 commits discards 5eafa2d90f 386: onsuccess: #2207: 1: Success after binutils/gcc/linux/g [...] discards f7b4c9580a 385: onsuccess: #2206: 1: Success after binutils/gcc/glibc/g [...] discards ea5436ddeb 384: onsuccess: #2205: 1: Success after gcc: 2 commits discards 96cb788fe9 383: onsuccess: #2204: 1: Success after binutils/gcc/linux/g [...] discards fb7b517555 382: onsuccess: #2203: 1: Success after gcc/qemu: 42 commits discards 6d4f973077 381: onsuccess: #2202: 1: Success after glibc-2.37.9000-17-g [...] discards 0052506390 380: onsuccess: #2201: 1: Success after binutils/gcc/linux/g [...] discards 4b7bcb94e5 379: onsuccess: #2200: 1: Success after binutils/gcc/linux/g [...] discards 60a8b85a21 378: onsuccess: #2199: 1: Success after binutils/gdb: 4 commits discards f8aceef42c 377: onsuccess: #2198: 1: Success after binutils/gcc/gdb: 3 commits discards 1f27555ed7 376: onsuccess: #2197: 1: Success after binutils/gcc/linux/g [...] discards c2dc59b20a 375: onsuccess: #2195: 1: Success after binutils/gcc/gdb/qem [...] discards 583dafd672 374: onsuccess: #2194: 1: Success after binutils/gcc/linux/g [...] discards 5ef0d3d076 373: onsuccess: #2193: 1: Success after binutils/gcc/glibc/g [...] discards 5a6591b882 372: onsuccess: #2192: 1: Success after binutils/gcc/linux/g [...] discards 39d64ecfba 371: onsuccess: #2191: 1: Success after binutils/gcc/gdb: 10 [...] discards 1ee76399bf 370: onsuccess: #2190: 1: Success after binutils/gcc/linux/g [...] discards 42a4420cda 369: onsuccess: #2189: 1: Success after binutils/gcc/linux/g [...] discards ff1a0b19b5 368: onsuccess: #2188: 1: Success after binutils/gcc/linux/g [...] discards fda8235400 367: onsuccess: #2187: 1: Success after binutils/gcc/gdb: 14 [...] discards 443856a9f0 366: onsuccess: #2186: 1: Success after binutils/gcc/linux/g [...] discards a3a8e9c052 365: onsuccess: #2185: 1: Success after binutils/gcc/linux/g [...] discards 7d4f4fd77e 364: onsuccess: #2184: 1: Success after binutils/gcc/linux/g [...] discards 2c01716e5e 363: onsuccess: #2183: 1: Success after binutils/gcc/linux/g [...] discards 9831156bdf 362: onsuccess: #2182: 1: Success after binutils/gcc/linux/g [...] discards 6d53c58e7e 361: onsuccess: #2181: 1: Success after binutils/gcc/linux/g [...] discards b32e9c9c87 360: onsuccess: #2180: 1: Success after binutils/gcc/linux/g [...] discards 0b7606d5c4 359: onsuccess: #2179: 1: Success after binutils/gcc/glibc/g [...] discards da798451e4 358: onsuccess: #2178: 1: Success after binutils/gcc/linux/g [...] discards 575c2940f1 357: onsuccess: #2177: 1: Success after binutils/gcc/linux/g [...] discards 76a23c6f91 356: onsuccess: #2176: 1: Success after binutils/gcc/linux/g [...] discards 1027209506 355: onsuccess: #2175: 1: Success after binutils/gcc/linux/g [...] discards dd2cd3c961 354: onsuccess: #2174: 1: Success after binutils/gcc/linux/g [...] discards d546004bc2 353: onsuccess: #2173: 1: Success after binutils/gcc/gdb: 27 [...] discards 3d7e52e659 352: onsuccess: #2172: 1: Success after binutils/gcc/linux/g [...] discards 71ef19d121 351: onsuccess: #2171: 1: Success after gcc/linux: 15 commits discards 1b9130aed7 350: onsuccess: #2170: 1: Success after binutils/gcc/linux/g [...] discards 9658622f56 349: onsuccess: #2169: 1: Success after binutils/gcc/linux/g [...] discards 919c5aa18e 348: onsuccess: #2168: 1: Success after binutils/gcc/gdb: 9 commits discards b12bf582ab 347: onsuccess: #2167: 1: Success after basepoints/gcc-13-51 [...] new 1e92681d5a 347: onsuccess: #2167: 1: Success after basepoints/gcc-13-51 [...] new b954a3d346 348: onsuccess: #2168: 1: Success after binutils/gcc/gdb: 9 commits new 21fac27b70 349: onsuccess: #2169: 1: Success after binutils/gcc/linux/g [...] new 36d1ca43d4 350: onsuccess: #2170: 1: Success after binutils/gcc/linux/g [...] new ee42407039 351: onsuccess: #2171: 1: Success after gcc/linux: 15 commits new 3682b14275 352: onsuccess: #2172: 1: Success after binutils/gcc/linux/g [...] new 2c15cbc582 353: onsuccess: #2173: 1: Success after binutils/gcc/gdb: 27 [...] new d473ffe654 354: onsuccess: #2174: 1: Success after binutils/gcc/linux/g [...] new 3020a5cb37 355: onsuccess: #2175: 1: Success after binutils/gcc/linux/g [...] new 36b3f024c8 356: onsuccess: #2176: 1: Success after binutils/gcc/linux/g [...] new 2b1326ee36 357: onsuccess: #2177: 1: Success after binutils/gcc/linux/g [...] new dab80bb47e 358: onsuccess: #2178: 1: Success after binutils/gcc/linux/g [...] new 1f05bd8554 359: onsuccess: #2179: 1: Success after binutils/gcc/glibc/g [...] new cd10a36fb7 360: onsuccess: #2180: 1: Success after binutils/gcc/linux/g [...] new 92c20b88bc 361: onsuccess: #2181: 1: Success after binutils/gcc/linux/g [...] new c0a27b3150 362: onsuccess: #2182: 1: Success after binutils/gcc/linux/g [...] new 9b003a4be1 363: onsuccess: #2183: 1: Success after binutils/gcc/linux/g [...] new 38664a1a40 364: onsuccess: #2184: 1: Success after binutils/gcc/linux/g [...] new b9c4d0e3d1 365: onsuccess: #2185: 1: Success after binutils/gcc/linux/g [...] new c765b6ce8c 366: onsuccess: #2186: 1: Success after binutils/gcc/linux/g [...] new 0cdc015edb 367: onsuccess: #2187: 1: Success after binutils/gcc/gdb: 14 [...] new 25aeafb67e 368: onsuccess: #2188: 1: Success after binutils/gcc/linux/g [...] new 4b2e8168dd 369: onsuccess: #2189: 1: Success after binutils/gcc/linux/g [...] new f470ba9e54 370: onsuccess: #2190: 1: Success after binutils/gcc/linux/g [...] new ed9d52780a 371: onsuccess: #2191: 1: Success after binutils/gcc/gdb: 10 [...] new 8b31c243ce 372: onsuccess: #2192: 1: Success after binutils/gcc/linux/g [...] new 4db2d14171 373: onsuccess: #2193: 1: Success after binutils/gcc/glibc/g [...] new 4596f53424 374: onsuccess: #2194: 1: Success after binutils/gcc/linux/g [...] new afc799b8a2 375: onsuccess: #2195: 1: Success after binutils/gcc/gdb/qem [...] new cf2296d12f 376: onsuccess: #2197: 1: Success after binutils/gcc/linux/g [...] new 9cf257b1ed 377: onsuccess: #2198: 1: Success after binutils/gcc/gdb: 3 commits new b462d08a30 378: onsuccess: #2199: 1: Success after binutils/gdb: 4 commits new f506d6f09c 379: onsuccess: #2200: 1: Success after binutils/gcc/linux/g [...] new 1fea9251b5 380: onsuccess: #2201: 1: Success after binutils/gcc/linux/g [...] new bdc19c405b 381: onsuccess: #2202: 1: Success after glibc-2.37.9000-17-g [...] new 74e35ff265 382: onsuccess: #2203: 1: Success after gcc/qemu: 42 commits new 1a89445186 383: onsuccess: #2204: 1: Success after binutils/gcc/linux/g [...] new 4e4c94051e 384: onsuccess: #2205: 1: Success after gcc: 2 commits new 7afb7a052b 385: onsuccess: #2206: 1: Success after binutils/gcc/glibc/g [...] new 09004a953d 386: onsuccess: #2207: 1: Success after binutils/gcc/linux/g [...] new 5f56c59c5f 387: onsuccess: #2208: 1: Success after gcc: 2 commits new 02b5eee781 388: onsuccess: #2209: 1: Success after binutils/gcc/glibc/g [...] new 65256a1686 389: onsuccess: #2210: 1: Success after binutils/gcc/linux/g [...] new e7ac6ff32d 390: onsuccess: #2211: 1: Success after binutils/gcc/linux/g [...] new 03c4a85235 391: onsuccess: #2212: 1: Success after binutils/gcc/gdb/qem [...] new 7e14a3f8ac 392: onsuccess: #2213: 1: Success after binutils/gcc/glibc/g [...] new 064c4f229c 393: onsuccess: #2214: 1: Success after binutils/gcc/gdb: 12 [...] new 90047851be 394: onsuccess: #2215: 1: Success after binutils/gcc/gdb: 8 commits new d13683d76d 395: onsuccess: #2216: 1: Success after binutils/gcc/linux/g [...] new f3f170a561 396: onsuccess: #2217: 1: Success after binutils/gcc/linux/g [...] new 77f0cd92f2 397: onsuccess: #2218: 1: Success after binutils/gcc/linux/g [...] new f3778e65d6 398: onsuccess: #2219: 1: Success after binutils/gcc/gdb/qem [...] new f3fd1faef6 399: onsuccess: #2220: 1: Success after binutils/gcc/linux/g [...] new d5463f68cf 400: onsuccess: #2221: 1: Success after binutils/gcc/linux/g [...] new ac7be1ca78 401: onsuccess: #2222: 1: Success after binutils/gcc/gdb: 10 [...] new 664b6ec677 402: onsuccess: #2223: 1: Success after binutils/gcc/gdb: 10 [...] new bd95fdf48c 403: onsuccess: #2224: 1: Success after binutils/gcc/linux/g [...] new b0d87a9fa2 404: onsuccess: #2225: 1: Success after binutils/gcc/gdb: 10 [...] new 0925ff0161 405: onsuccess: #2226: 1: Success after gcc/glibc: 39 commits new 35044b25a2 406: onsuccess: #2227: 1: Success after binutils/linux/glibc [...] new 750e709d3f 407: onsuccess: #2228: 1: Success after binutils/gcc/linux/g [...] new 947aa8c61a 408: onsuccess: #2229: 1: Success after binutils/gcc/gdb: 26 [...] new c7166b98fe 409: onsuccess: #2230: 1: Success after binutils/gcc/glibc/g [...] new e9de695505 410: onsuccess: #2231: 1: Success after binutils/gcc/linux/g [...] new 8a7aa8086c 411: onsuccess: #2232: 1: Success after gcc: 3 commits new 5d8271700f 412: onsuccess: #2233: 1: Success after binutils/gcc/glibc/g [...] new 3d3d9ecbe8 413: onsuccess: #2234: 1: Success after binutils/gcc/linux/g [...] new 8469f5da11 414: onsuccess: #2235: 1: Success after binutils/gcc/gdb: 13 [...] new 2aa7462e1f 415: onsuccess: #2236: 1: Success after binutils/gcc/gdb: 14 [...] new ccff250412 416: onsuccess: #2237: 1: Success after binutils/gcc/glibc/g [...] new 39f0a041da 417: onsuccess: #2238: 1: Success after binutils/gcc/linux/g [...] new 97393c61c4 418: onsuccess: #2239: 1: Success after binutils/gcc/gdb: 5 commits new e9f8a141aa 419: onsuccess: #2243: 1: Success after binutils/gcc/linux/g [...] new 5b595b40be 420: onsuccess: #2244: 1: Success after gcc/glibc: 5 commits new 5cd80859d9 421: onsuccess: #2245: 1: Success after binutils/gcc/glibc/g [...] new 0e8497d13a 422: onsuccess: #2246: 1: Success after binutils/gcc/linux/g [...] new dfa41ea6c9 423: onsuccess: #2247: 1: Success after gcc/linux: 8 commits new 47e6814bac 424: onsuccess: #2248: 1: Success after gcc: 6 commits new 0fffc0c751 425: onsuccess: #2249: 1: Success after binutils/gcc/linux/g [...] new c84c754079 426: onsuccess: #2250: 1: Success after binutils/linux/gdb: [...] new 0fdd349699 427: onsuccess: #2251: 1: Success after binutils/gcc/linux/g [...] new 68cbbc3b72 428: onsuccess: #2252: 1: Success after binutils/gdb: 2 commits new c4151ad1fc 429: onsuccess: #2253: 1: Success after binutils/gcc/glibc/g [...] new 777e743ff8 430: onsuccess: #2254: 1: Success after binutils/gcc/linux/g [...] new 2210744274 431: onsuccess: #2255: 1: Success after binutils/gcc/linux/g [...] new ff98fb8a63 432: onsuccess: #2256: 1: Success after binutils/gdb: 10 commits new ae8c0f0c59 433: onsuccess: #2257: 1: Success after binutils/gcc/gdb/qem [...] new 305ab48f93 434: onsuccess: #2258: 1: Success after binutils/gcc/linux/g [...] new 4ceab0b29c 435: onsuccess: #2259: 1: Success after binutils/gcc/linux/g [...] new b03dfbf17c 436: onsuccess: #2260: 1: Success after gcc: 7 commits new fc08bbc3df 437: onsuccess: #2261: 1: Success after binutils/gcc/glibc/g [...] new 70f8356171 438: onsuccess: #2263: 1: Success after binutils/gcc/linux/g [...] new ef51cad9cc 439: onsuccess: #2264: 1: Success after binutils/gcc/gdb: 13 [...] new fa139b8e73 440: onsuccess: #2265: 1: Success after binutils/gcc/linux/g [...] new 99849c57ca 441: onsuccess: #2266: 1: Success after binutils/gcc/linux/g [...] new 8cab5091bd 442: onsuccess: #3: 1: Success after binutils/gcc/glibc/gdb/ [...] new e841d7ad5c 443: onsuccess: #4: 1: Success after binutils/gcc/gdb/qemu: [...] new 0d30489dba 444: onsuccess: #5: 1: Success after binutils/gcc/linux/glib [...] new fadcbd1a37 445: onsuccess: #6: 1: Success after binutils/gcc/linux/gdb: [...] new 873e989676 446: onsuccess: #7: 1: Success after binutils/gcc/gdb: 5 commits new 8ed4b56a7f 447: onsuccess: #8: 1: Success after binutils/gcc/linux/glib [...] new 3e5e49fb48 448: onsuccess: #9: 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 (8d3711801a) \ 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 1804 -> 1760 bytes 02-prepare_abe/console.log.xz | Bin 2780 -> 2760 bytes 03-build_abe-binutils/console.log.xz | Bin 30572 -> 30576 bytes 04-build_abe-stage1/console.log.xz | Bin 89392 -> 89364 bytes 06-build_abe-linux/console.log.xz | Bin 8812 -> 9444 bytes 07-build_abe-glibc/console.log.xz | Bin 235600 -> 236040 bytes 08-build_abe-stage2/console.log.xz | Bin 226308 -> 225760 bytes 09-build_abe-gdb/console.log.xz | Bin 38584 -> 38536 bytes 10-build_abe-qemu/console.log.xz | Bin 32052 -> 31684 bytes 11-build_abe-dejagnu/console.log.xz | Bin 3820 -> 3812 bytes 12-build_abe-check_gcc/console.log.xz | Bin 2604 -> 3012 bytes 13-check_regression/console.log.xz | Bin 50028 -> 5832 bytes 13-check_regression/results.compare | 16 +- 13-check_regression/results.compare2 | 5763 +-------------------------------- 14-update_baseline/console.log | 66 +- 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 | 40 +- sumfiles/g++.log.xz | Bin 2646524 -> 2670368 bytes sumfiles/g++.sum | 2 +- sumfiles/gcc.log.xz | Bin 2228808 -> 2205452 bytes sumfiles/gcc.sum | 2 +- sumfiles/gfortran.log.xz | Bin 891408 -> 893788 bytes sumfiles/gfortran.sum | 2 +- sumfiles/libatomic.log.xz | Bin 2284 -> 2280 bytes sumfiles/libatomic.sum | 2 +- sumfiles/libgomp.log.xz | Bin 216916 -> 216992 bytes sumfiles/libgomp.sum | 2 +- sumfiles/libitm.log.xz | Bin 2688 -> 2692 bytes sumfiles/libitm.sum | 2 +- sumfiles/libstdc++.log.xz | Bin 439080 -> 441292 bytes 37 files changed, 78 insertions(+), 5835 deletions(-)