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 3e5e49fb48 448: onsuccess: #9: 1: Success after binutils/gcc/linux/gdb: [...] discards 8ed4b56a7f 447: onsuccess: #8: 1: Success after binutils/gcc/linux/glib [...] discards 873e989676 446: onsuccess: #7: 1: Success after binutils/gcc/gdb: 5 commits discards fadcbd1a37 445: onsuccess: #6: 1: Success after binutils/gcc/linux/gdb: [...] discards 0d30489dba 444: onsuccess: #5: 1: Success after binutils/gcc/linux/glib [...] discards e841d7ad5c 443: onsuccess: #4: 1: Success after binutils/gcc/gdb/qemu: [...] discards 8cab5091bd 442: onsuccess: #3: 1: Success after binutils/gcc/glibc/gdb/ [...] discards 99849c57ca 441: onsuccess: #2266: 1: Success after binutils/gcc/linux/g [...] discards fa139b8e73 440: onsuccess: #2265: 1: Success after binutils/gcc/linux/g [...] discards ef51cad9cc 439: onsuccess: #2264: 1: Success after binutils/gcc/gdb: 13 [...] discards 70f8356171 438: onsuccess: #2263: 1: Success after binutils/gcc/linux/g [...] discards fc08bbc3df 437: onsuccess: #2261: 1: Success after binutils/gcc/glibc/g [...] discards b03dfbf17c 436: onsuccess: #2260: 1: Success after gcc: 7 commits discards 4ceab0b29c 435: onsuccess: #2259: 1: Success after binutils/gcc/linux/g [...] discards 305ab48f93 434: onsuccess: #2258: 1: Success after binutils/gcc/linux/g [...] discards ae8c0f0c59 433: onsuccess: #2257: 1: Success after binutils/gcc/gdb/qem [...] discards ff98fb8a63 432: onsuccess: #2256: 1: Success after binutils/gdb: 10 commits discards 2210744274 431: onsuccess: #2255: 1: Success after binutils/gcc/linux/g [...] discards 777e743ff8 430: onsuccess: #2254: 1: Success after binutils/gcc/linux/g [...] discards c4151ad1fc 429: onsuccess: #2253: 1: Success after binutils/gcc/glibc/g [...] discards 68cbbc3b72 428: onsuccess: #2252: 1: Success after binutils/gdb: 2 commits discards 0fdd349699 427: onsuccess: #2251: 1: Success after binutils/gcc/linux/g [...] discards c84c754079 426: onsuccess: #2250: 1: Success after binutils/linux/gdb: [...] discards 0fffc0c751 425: onsuccess: #2249: 1: Success after binutils/gcc/linux/g [...] discards 47e6814bac 424: onsuccess: #2248: 1: Success after gcc: 6 commits discards dfa41ea6c9 423: onsuccess: #2247: 1: Success after gcc/linux: 8 commits discards 0e8497d13a 422: onsuccess: #2246: 1: Success after binutils/gcc/linux/g [...] discards 5cd80859d9 421: onsuccess: #2245: 1: Success after binutils/gcc/glibc/g [...] discards 5b595b40be 420: onsuccess: #2244: 1: Success after gcc/glibc: 5 commits discards e9f8a141aa 419: onsuccess: #2243: 1: Success after binutils/gcc/linux/g [...] discards 97393c61c4 418: onsuccess: #2239: 1: Success after binutils/gcc/gdb: 5 commits discards 39f0a041da 417: onsuccess: #2238: 1: Success after binutils/gcc/linux/g [...] discards ccff250412 416: onsuccess: #2237: 1: Success after binutils/gcc/glibc/g [...] discards 2aa7462e1f 415: onsuccess: #2236: 1: Success after binutils/gcc/gdb: 14 [...] discards 8469f5da11 414: onsuccess: #2235: 1: Success after binutils/gcc/gdb: 13 [...] discards 3d3d9ecbe8 413: onsuccess: #2234: 1: Success after binutils/gcc/linux/g [...] discards 5d8271700f 412: onsuccess: #2233: 1: Success after binutils/gcc/glibc/g [...] discards 8a7aa8086c 411: onsuccess: #2232: 1: Success after gcc: 3 commits discards e9de695505 410: onsuccess: #2231: 1: Success after binutils/gcc/linux/g [...] discards c7166b98fe 409: onsuccess: #2230: 1: Success after binutils/gcc/glibc/g [...] discards 947aa8c61a 408: onsuccess: #2229: 1: Success after binutils/gcc/gdb: 26 [...] discards 750e709d3f 407: onsuccess: #2228: 1: Success after binutils/gcc/linux/g [...] discards 35044b25a2 406: onsuccess: #2227: 1: Success after binutils/linux/glibc [...] discards 0925ff0161 405: onsuccess: #2226: 1: Success after gcc/glibc: 39 commits discards b0d87a9fa2 404: onsuccess: #2225: 1: Success after binutils/gcc/gdb: 10 [...] discards bd95fdf48c 403: onsuccess: #2224: 1: Success after binutils/gcc/linux/g [...] discards 664b6ec677 402: onsuccess: #2223: 1: Success after binutils/gcc/gdb: 10 [...] discards ac7be1ca78 401: onsuccess: #2222: 1: Success after binutils/gcc/gdb: 10 [...] discards d5463f68cf 400: onsuccess: #2221: 1: Success after binutils/gcc/linux/g [...] discards f3fd1faef6 399: onsuccess: #2220: 1: Success after binutils/gcc/linux/g [...] discards f3778e65d6 398: onsuccess: #2219: 1: Success after binutils/gcc/gdb/qem [...] discards 77f0cd92f2 397: onsuccess: #2218: 1: Success after binutils/gcc/linux/g [...] discards f3f170a561 396: onsuccess: #2217: 1: Success after binutils/gcc/linux/g [...] discards d13683d76d 395: onsuccess: #2216: 1: Success after binutils/gcc/linux/g [...] discards 90047851be 394: onsuccess: #2215: 1: Success after binutils/gcc/gdb: 8 commits discards 064c4f229c 393: onsuccess: #2214: 1: Success after binutils/gcc/gdb: 12 [...] discards 7e14a3f8ac 392: onsuccess: #2213: 1: Success after binutils/gcc/glibc/g [...] discards 03c4a85235 391: onsuccess: #2212: 1: Success after binutils/gcc/gdb/qem [...] discards e7ac6ff32d 390: onsuccess: #2211: 1: Success after binutils/gcc/linux/g [...] discards 65256a1686 389: onsuccess: #2210: 1: Success after binutils/gcc/linux/g [...] discards 02b5eee781 388: onsuccess: #2209: 1: Success after binutils/gcc/glibc/g [...] discards 5f56c59c5f 387: onsuccess: #2208: 1: Success after gcc: 2 commits discards 09004a953d 386: onsuccess: #2207: 1: Success after binutils/gcc/linux/g [...] discards 7afb7a052b 385: onsuccess: #2206: 1: Success after binutils/gcc/glibc/g [...] discards 4e4c94051e 384: onsuccess: #2205: 1: Success after gcc: 2 commits discards 1a89445186 383: onsuccess: #2204: 1: Success after binutils/gcc/linux/g [...] discards 74e35ff265 382: onsuccess: #2203: 1: Success after gcc/qemu: 42 commits discards bdc19c405b 381: onsuccess: #2202: 1: Success after glibc-2.37.9000-17-g [...] discards 1fea9251b5 380: onsuccess: #2201: 1: Success after binutils/gcc/linux/g [...] discards f506d6f09c 379: onsuccess: #2200: 1: Success after binutils/gcc/linux/g [...] discards b462d08a30 378: onsuccess: #2199: 1: Success after binutils/gdb: 4 commits discards 9cf257b1ed 377: onsuccess: #2198: 1: Success after binutils/gcc/gdb: 3 commits discards cf2296d12f 376: onsuccess: #2197: 1: Success after binutils/gcc/linux/g [...] discards afc799b8a2 375: onsuccess: #2195: 1: Success after binutils/gcc/gdb/qem [...] discards 4596f53424 374: onsuccess: #2194: 1: Success after binutils/gcc/linux/g [...] discards 4db2d14171 373: onsuccess: #2193: 1: Success after binutils/gcc/glibc/g [...] discards 8b31c243ce 372: onsuccess: #2192: 1: Success after binutils/gcc/linux/g [...] discards ed9d52780a 371: onsuccess: #2191: 1: Success after binutils/gcc/gdb: 10 [...] discards f470ba9e54 370: onsuccess: #2190: 1: Success after binutils/gcc/linux/g [...] discards 4b2e8168dd 369: onsuccess: #2189: 1: Success after binutils/gcc/linux/g [...] discards 25aeafb67e 368: onsuccess: #2188: 1: Success after binutils/gcc/linux/g [...] discards 0cdc015edb 367: onsuccess: #2187: 1: Success after binutils/gcc/gdb: 14 [...] discards c765b6ce8c 366: onsuccess: #2186: 1: Success after binutils/gcc/linux/g [...] discards b9c4d0e3d1 365: onsuccess: #2185: 1: Success after binutils/gcc/linux/g [...] discards 38664a1a40 364: onsuccess: #2184: 1: Success after binutils/gcc/linux/g [...] discards 9b003a4be1 363: onsuccess: #2183: 1: Success after binutils/gcc/linux/g [...] discards c0a27b3150 362: onsuccess: #2182: 1: Success after binutils/gcc/linux/g [...] discards 92c20b88bc 361: onsuccess: #2181: 1: Success after binutils/gcc/linux/g [...] discards cd10a36fb7 360: onsuccess: #2180: 1: Success after binutils/gcc/linux/g [...] discards 1f05bd8554 359: onsuccess: #2179: 1: Success after binutils/gcc/glibc/g [...] discards dab80bb47e 358: onsuccess: #2178: 1: Success after binutils/gcc/linux/g [...] discards 2b1326ee36 357: onsuccess: #2177: 1: Success after binutils/gcc/linux/g [...] discards 36b3f024c8 356: onsuccess: #2176: 1: Success after binutils/gcc/linux/g [...] discards 3020a5cb37 355: onsuccess: #2175: 1: Success after binutils/gcc/linux/g [...] discards d473ffe654 354: onsuccess: #2174: 1: Success after binutils/gcc/linux/g [...] discards 2c15cbc582 353: onsuccess: #2173: 1: Success after binutils/gcc/gdb: 27 [...] discards 3682b14275 352: onsuccess: #2172: 1: Success after binutils/gcc/linux/g [...] discards ee42407039 351: onsuccess: #2171: 1: Success after gcc/linux: 15 commits discards 36d1ca43d4 350: onsuccess: #2170: 1: Success after binutils/gcc/linux/g [...] discards 21fac27b70 349: onsuccess: #2169: 1: Success after binutils/gcc/linux/g [...] discards b954a3d346 348: onsuccess: #2168: 1: Success after binutils/gcc/gdb: 9 commits new 7e2743ebc1 348: onsuccess: #2168: 1: Success after binutils/gcc/gdb: 9 commits new 01620b5dca 349: onsuccess: #2169: 1: Success after binutils/gcc/linux/g [...] new 7b77fdedeb 350: onsuccess: #2170: 1: Success after binutils/gcc/linux/g [...] new 4876837d26 351: onsuccess: #2171: 1: Success after gcc/linux: 15 commits new 5acb9474b3 352: onsuccess: #2172: 1: Success after binutils/gcc/linux/g [...] new 4fe619ff78 353: onsuccess: #2173: 1: Success after binutils/gcc/gdb: 27 [...] new 8127ad2c35 354: onsuccess: #2174: 1: Success after binutils/gcc/linux/g [...] new 94e618ed7d 355: onsuccess: #2175: 1: Success after binutils/gcc/linux/g [...] new fef598a657 356: onsuccess: #2176: 1: Success after binutils/gcc/linux/g [...] new a4087f5508 357: onsuccess: #2177: 1: Success after binutils/gcc/linux/g [...] new a8a1878130 358: onsuccess: #2178: 1: Success after binutils/gcc/linux/g [...] new c7c6690422 359: onsuccess: #2179: 1: Success after binutils/gcc/glibc/g [...] new 96a1d360b1 360: onsuccess: #2180: 1: Success after binutils/gcc/linux/g [...] new a9a71862c2 361: onsuccess: #2181: 1: Success after binutils/gcc/linux/g [...] new 8b58724150 362: onsuccess: #2182: 1: Success after binutils/gcc/linux/g [...] new b08bf6fc99 363: onsuccess: #2183: 1: Success after binutils/gcc/linux/g [...] new c4000d8744 364: onsuccess: #2184: 1: Success after binutils/gcc/linux/g [...] new 0d1bfc7274 365: onsuccess: #2185: 1: Success after binutils/gcc/linux/g [...] new ba8656b62e 366: onsuccess: #2186: 1: Success after binutils/gcc/linux/g [...] new a727d8b21a 367: onsuccess: #2187: 1: Success after binutils/gcc/gdb: 14 [...] new 0fa2f3ef24 368: onsuccess: #2188: 1: Success after binutils/gcc/linux/g [...] new a39c3a62d5 369: onsuccess: #2189: 1: Success after binutils/gcc/linux/g [...] new 3999f65c65 370: onsuccess: #2190: 1: Success after binutils/gcc/linux/g [...] new f86b39a727 371: onsuccess: #2191: 1: Success after binutils/gcc/gdb: 10 [...] new c1277208ad 372: onsuccess: #2192: 1: Success after binutils/gcc/linux/g [...] new 031a761183 373: onsuccess: #2193: 1: Success after binutils/gcc/glibc/g [...] new 1b4acff807 374: onsuccess: #2194: 1: Success after binutils/gcc/linux/g [...] new fb37be2af8 375: onsuccess: #2195: 1: Success after binutils/gcc/gdb/qem [...] new d26e05613a 376: onsuccess: #2197: 1: Success after binutils/gcc/linux/g [...] new 7a1f58d85d 377: onsuccess: #2198: 1: Success after binutils/gcc/gdb: 3 commits new a0084807b1 378: onsuccess: #2199: 1: Success after binutils/gdb: 4 commits new ee3357626c 379: onsuccess: #2200: 1: Success after binutils/gcc/linux/g [...] new 7766c86507 380: onsuccess: #2201: 1: Success after binutils/gcc/linux/g [...] new af2e25c483 381: onsuccess: #2202: 1: Success after glibc-2.37.9000-17-g [...] new 3aa94bfa92 382: onsuccess: #2203: 1: Success after gcc/qemu: 42 commits new 1a3256bc17 383: onsuccess: #2204: 1: Success after binutils/gcc/linux/g [...] new 1f0cbf055b 384: onsuccess: #2205: 1: Success after gcc: 2 commits new a6e52e8684 385: onsuccess: #2206: 1: Success after binutils/gcc/glibc/g [...] new 73ad2fdc6a 386: onsuccess: #2207: 1: Success after binutils/gcc/linux/g [...] new 3694c08654 387: onsuccess: #2208: 1: Success after gcc: 2 commits new 7b67efb002 388: onsuccess: #2209: 1: Success after binutils/gcc/glibc/g [...] new 3ca72c905c 389: onsuccess: #2210: 1: Success after binutils/gcc/linux/g [...] new fb40f3dc52 390: onsuccess: #2211: 1: Success after binutils/gcc/linux/g [...] new 52b451661e 391: onsuccess: #2212: 1: Success after binutils/gcc/gdb/qem [...] new befee5517e 392: onsuccess: #2213: 1: Success after binutils/gcc/glibc/g [...] new 313bf8185c 393: onsuccess: #2214: 1: Success after binutils/gcc/gdb: 12 [...] new ac358ececc 394: onsuccess: #2215: 1: Success after binutils/gcc/gdb: 8 commits new 5994fbbc6d 395: onsuccess: #2216: 1: Success after binutils/gcc/linux/g [...] new 4883529226 396: onsuccess: #2217: 1: Success after binutils/gcc/linux/g [...] new 47ca2f1f47 397: onsuccess: #2218: 1: Success after binutils/gcc/linux/g [...] new 8cb46c1b40 398: onsuccess: #2219: 1: Success after binutils/gcc/gdb/qem [...] new 6fcc4799fa 399: onsuccess: #2220: 1: Success after binutils/gcc/linux/g [...] new dc7271f0d2 400: onsuccess: #2221: 1: Success after binutils/gcc/linux/g [...] new ccd21b3684 401: onsuccess: #2222: 1: Success after binutils/gcc/gdb: 10 [...] new 52472bcd21 402: onsuccess: #2223: 1: Success after binutils/gcc/gdb: 10 [...] new fc8aed4707 403: onsuccess: #2224: 1: Success after binutils/gcc/linux/g [...] new 001740ef8d 404: onsuccess: #2225: 1: Success after binutils/gcc/gdb: 10 [...] new 94169f574c 405: onsuccess: #2226: 1: Success after gcc/glibc: 39 commits new 7135a621ba 406: onsuccess: #2227: 1: Success after binutils/linux/glibc [...] new 717e51540d 407: onsuccess: #2228: 1: Success after binutils/gcc/linux/g [...] new 0593a9d350 408: onsuccess: #2229: 1: Success after binutils/gcc/gdb: 26 [...] new 501a144c35 409: onsuccess: #2230: 1: Success after binutils/gcc/glibc/g [...] new 3b974e75d9 410: onsuccess: #2231: 1: Success after binutils/gcc/linux/g [...] new 10d94784d7 411: onsuccess: #2232: 1: Success after gcc: 3 commits new 2f1d83fe46 412: onsuccess: #2233: 1: Success after binutils/gcc/glibc/g [...] new 1fdcb11f68 413: onsuccess: #2234: 1: Success after binutils/gcc/linux/g [...] new 12ec18350b 414: onsuccess: #2235: 1: Success after binutils/gcc/gdb: 13 [...] new 8e2b6ef214 415: onsuccess: #2236: 1: Success after binutils/gcc/gdb: 14 [...] new 9dad8dc1b2 416: onsuccess: #2237: 1: Success after binutils/gcc/glibc/g [...] new 8757ea7836 417: onsuccess: #2238: 1: Success after binutils/gcc/linux/g [...] new 64b79f0523 418: onsuccess: #2239: 1: Success after binutils/gcc/gdb: 5 commits new c7baaaa773 419: onsuccess: #2243: 1: Success after binutils/gcc/linux/g [...] new 040cab1f72 420: onsuccess: #2244: 1: Success after gcc/glibc: 5 commits new 3a1bd2779b 421: onsuccess: #2245: 1: Success after binutils/gcc/glibc/g [...] new e0456c1186 422: onsuccess: #2246: 1: Success after binutils/gcc/linux/g [...] new 384d585977 423: onsuccess: #2247: 1: Success after gcc/linux: 8 commits new 32d24791ef 424: onsuccess: #2248: 1: Success after gcc: 6 commits new 240e7c8f9d 425: onsuccess: #2249: 1: Success after binutils/gcc/linux/g [...] new 6584cce26c 426: onsuccess: #2250: 1: Success after binutils/linux/gdb: [...] new 9dcdfa372c 427: onsuccess: #2251: 1: Success after binutils/gcc/linux/g [...] new 8745db8932 428: onsuccess: #2252: 1: Success after binutils/gdb: 2 commits new bf23c6b056 429: onsuccess: #2253: 1: Success after binutils/gcc/glibc/g [...] new c2938fb587 430: onsuccess: #2254: 1: Success after binutils/gcc/linux/g [...] new ceae32393f 431: onsuccess: #2255: 1: Success after binutils/gcc/linux/g [...] new 0fa0acda07 432: onsuccess: #2256: 1: Success after binutils/gdb: 10 commits new ce05eea523 433: onsuccess: #2257: 1: Success after binutils/gcc/gdb/qem [...] new 34e2724226 434: onsuccess: #2258: 1: Success after binutils/gcc/linux/g [...] new 576309a28b 435: onsuccess: #2259: 1: Success after binutils/gcc/linux/g [...] new bb765a31cf 436: onsuccess: #2260: 1: Success after gcc: 7 commits new 718e54093a 437: onsuccess: #2261: 1: Success after binutils/gcc/glibc/g [...] new b15472d3ea 438: onsuccess: #2263: 1: Success after binutils/gcc/linux/g [...] new 28a999db0d 439: onsuccess: #2264: 1: Success after binutils/gcc/gdb: 13 [...] new 667b1327d0 440: onsuccess: #2265: 1: Success after binutils/gcc/linux/g [...] new 18435bbcaf 441: onsuccess: #2266: 1: Success after binutils/gcc/linux/g [...] new 120aac8b69 442: onsuccess: #3: 1: Success after binutils/gcc/glibc/gdb/ [...] new a52142e461 443: onsuccess: #4: 1: Success after binutils/gcc/gdb/qemu: [...] new da7007cf6f 444: onsuccess: #5: 1: Success after binutils/gcc/linux/glib [...] new e062a7c504 445: onsuccess: #6: 1: Success after binutils/gcc/linux/gdb: [...] new 3e559104de 446: onsuccess: #7: 1: Success after binutils/gcc/gdb: 5 commits new c41828dda0 447: onsuccess: #8: 1: Success after binutils/gcc/linux/glib [...] new 4bed055a0e 448: onsuccess: #9: 1: Success after binutils/gcc/linux/gdb: [...] new b89e2f5489 449: onsuccess: #10: 1: Success after binutils/gcc/linux/gli [...]

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 (3e5e49fb48) \ 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 1760 -> 1804 bytes 02-prepare_abe/console.log.xz | Bin 2760 -> 2780 bytes 03-build_abe-binutils/console.log.xz | Bin 30576 -> 30960 bytes 04-build_abe-stage1/console.log.xz | Bin 89364 -> 89312 bytes 06-build_abe-linux/console.log.xz | Bin 9444 -> 8808 bytes 07-build_abe-glibc/console.log.xz | Bin 236040 -> 235452 bytes 08-build_abe-stage2/console.log.xz | Bin 225760 -> 225296 bytes 09-build_abe-gdb/console.log.xz | Bin 38536 -> 39176 bytes 10-build_abe-qemu/console.log.xz | Bin 31684 -> 32148 bytes 11-build_abe-dejagnu/console.log.xz | Bin 3812 -> 3804 bytes 12-build_abe-check_gcc/console.log.xz | Bin 3012 -> 2936 bytes 13-check_regression/console.log.xz | Bin 5832 -> 28624 bytes 13-check_regression/results.compare | 16 +- 13-check_regression/results.compare2 | 5781 ++++++++++++++++++++++++++++++++- 14-update_baseline/console.log | 38 +- 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 +- git/qemu_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 2 +- mail/mail-subject.txt | 2 +- manifest.sh | 48 +- sumfiles/g++.log.xz | Bin 2670368 -> 2649328 bytes sumfiles/g++.sum | 4284 ++++++++++++------------ sumfiles/gcc.log.xz | Bin 2205452 -> 2225412 bytes sumfiles/gcc.sum | 1440 ++++---- sumfiles/gfortran.log.xz | Bin 893788 -> 895052 bytes sumfiles/gfortran.sum | 22 +- sumfiles/libatomic.log.xz | Bin 2280 -> 2284 bytes sumfiles/libatomic.sum | 2 +- sumfiles/libgomp.log.xz | Bin 216992 -> 216808 bytes sumfiles/libgomp.sum | 2 +- sumfiles/libitm.log.xz | Bin 2692 -> 2688 bytes sumfiles/libitm.sum | 2 +- sumfiles/libstdc++.log.xz | Bin 441292 -> 439516 bytes 39 files changed, 8719 insertions(+), 2936 deletions(-)