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 de39bd93de 498: onsuccess: #65: 1: [TCWG CI] https://ci.linaro.org/job/ [...] discards 42e839797d 497: onsuccess: #64: 1: [TCWG CI] https://ci.linaro.org/job/ [...] discards 755c755a9b 496: onsuccess: #60: 1: [TCWG CI] https://ci.linaro.org/job/ [...] discards 74cd8329bc 495: onsuccess: #59: 1: [TCWG CI] https://ci.linaro.org/job/ [...] discards 8834c65959 494: onsuccess: #58: 1: [TCWG CI] https://ci.linaro.org/job/ [...] discards f76e574e29 493: onsuccess: #56: 1: [TCWG CI] https://ci.linaro.org/job/ [...] discards 9489475017 492: onsuccess: #55: 1: [TCWG CI] https://ci.linaro.org/job/ [...] discards ff1e364814 491: onsuccess: #54: 1: [TCWG CI] https://ci.linaro.org/job/ [...] discards 2f8384e4dd 490: onsuccess: #53: 1: [TCWG CI] https://ci.linaro.org/job/ [...] discards 5d06855dcf 489: onsuccess: #52: 1: [TCWG CI] Success after binutils/gcc [...] discards 25f39afd2d 488: onsuccess: #51: 1: [TCWG CI] Success after binutils/gcc [...] discards 146f8a73d7 487: onsuccess: #50: 1: [TCWG CI] Success after binutils/gcc [...] discards 9098be04bc 486: onsuccess: #49: 1: [TCWG CI] Success after binutils/gcc [...] discards f71041132d 485: onsuccess: #47: 1: [TCWG CI] Success after binutils/gcc [...] discards 5ca1d16812 484: onsuccess: #46: 1: [TCWG CI] Success after binutils/gcc [...] discards 3d364bf0d3 483: onsuccess: #45: 1: [TCWG CI] Success after binutils/gcc [...] discards 38438a4212 482: onsuccess: #44: 1: [TCWG CI] Success after binutils/gcc [...] discards 1464547519 481: onsuccess: #43: 1: [TCWG CI] Success after binutils/gcc [...] discards a91230e00f 480: onsuccess: #42: 1: [TCWG CI] Success after binutils/gcc [...] discards 92cf93c020 479: onsuccess: #41: 1: [TCWG CI] Success after binutils/gcc [...] discards 700463ff4e 478: onsuccess: #40: 1: [TCWG CI] Success after binutils/gcc [...] discards 1f9c36f2b4 477: onsuccess: #39: 1: [TCWG CI] Success after binutils/gcc [...] discards d60511f2ab 476: onsuccess: #37: 1: Success after binutils/gcc/linux/gli [...] discards 721cc33381 475: onsuccess: #36: 1: Success after binutils/gcc/linux/gdb [...] discards dae5eea150 474: onsuccess: #35: 1: Success after binutils/gcc/linux/gdb [...] discards 9d92f25b2a 473: onsuccess: #34: 1: Success after binutils/gcc/linux/gdb [...] discards c969a05c56 472: onsuccess: #33: 1: Success after binutils/gcc/linux/gdb [...] discards 79e59d3eb5 471: onsuccess: #32: 1: Success after binutils/gcc/linux/gli [...] discards 93a12b3979 470: onsuccess: #31: 1: Success after binutils/gcc/linux/gdb [...] discards 65aadc6711 469: onsuccess: #30: 1: Success after binutils/gcc/linux/gdb [...] discards bdf342edaf 468: onsuccess: #29: 1: Success after binutils/gcc/linux/gdb [...] discards 04dead8d83 467: onsuccess: #28: 1: Success after binutils/gcc/linux/gdb [...] discards 2f023e267e 466: onsuccess: #27: 1: Success after binutils/gcc/linux/gdb [...] discards be85c443c2 465: onsuccess: #26: 1: Success after binutils/gcc/linux/gdb [...] discards cd8a127265 464: onsuccess: #25: 1: Success after binutils/gcc/linux/gli [...] discards 8b6fa0ee64 463: onsuccess: #24: 1: Success after binutils/gcc/linux/gli [...] discards 3440e94942 462: onsuccess: #23: 1: Success after binutils/gcc/linux/gli [...] discards b18370063d 461: onsuccess: #22: 1: Success after binutils/gcc/linux/gdb [...] discards 5de488c970 460: onsuccess: #21: 1: Success after binutils/gcc/linux/gli [...] discards d9d8f6d640 459: onsuccess: #20: 1: Success after binutils/gcc/linux/gdb [...] discards dcaf58e686 458: onsuccess: #19: 1: Success after binutils/gcc/linux/gli [...] discards 7967e603d8 457: onsuccess: #18: 1: Success after binutils/gcc/linux/gli [...] discards 4070426b46 456: onsuccess: #17: 1: Success after binutils/gcc/linux/gli [...] discards 75618a6a0b 455: onsuccess: #16: 1: Success after binutils/gcc/linux/gdb [...] discards e4fa68b7be 454: onsuccess: #15: 1: Success after binutils/gcc/linux/gdb [...] discards c1644dedd4 453: onsuccess: #14: 1: Success after binutils/gcc/linux/gdb [...] discards b2acf8731f 452: onsuccess: #13: 1: Success after binutils/gcc/linux/gli [...] discards 8e5f986763 451: onsuccess: #12: 1: Success after binutils/gcc/linux/gli [...] discards 8847e684bf 450: onsuccess: #11: 1: Success after binutils/gcc/linux/gli [...] discards b8271af460 449: onsuccess: #10: 1: Success after binutils/gcc/linux/gli [...] discards 7d925d7c97 448: onsuccess: #9: 1: Success after binutils/gcc/linux/gdb: [...] discards ce838d1ea7 447: onsuccess: #8: 1: Success after binutils/gcc/linux/glib [...] discards 203b7dc2f0 446: onsuccess: #7: 1: Success after binutils/gcc/gdb: 5 commits discards 2c627bfde9 445: onsuccess: #6: 1: Success after binutils/gcc/linux/gdb: [...] discards af742983bc 444: onsuccess: #5: 1: Success after binutils/gcc/linux/glib [...] discards 1eaaf402c6 443: onsuccess: #4: 1: Success after binutils/gcc/gdb/qemu: [...] discards f70e725e73 442: onsuccess: #3: 1: Success after binutils/gcc/glibc/gdb/ [...] discards 60559c0bec 441: onsuccess: #2266: 1: Success after binutils/gcc/linux/g [...] discards cdd47b37d8 440: onsuccess: #2265: 1: Success after binutils/gcc/linux/g [...] discards 52d9e32c3f 439: onsuccess: #2264: 1: Success after binutils/gcc/gdb: 13 [...] discards da7a5785c9 438: onsuccess: #2263: 1: Success after binutils/gcc/linux/g [...] discards 4e5b3c1e66 437: onsuccess: #2261: 1: Success after binutils/gcc/glibc/g [...] discards 33715d12ac 436: onsuccess: #2260: 1: Success after gcc: 7 commits discards f6fe29584c 435: onsuccess: #2259: 1: Success after binutils/gcc/linux/g [...] discards 18b68c240c 434: onsuccess: #2258: 1: Success after binutils/gcc/linux/g [...] discards 6aaf8a36e9 433: onsuccess: #2257: 1: Success after binutils/gcc/gdb/qem [...] discards ef7b717074 432: onsuccess: #2256: 1: Success after binutils/gdb: 10 commits discards 3b5a979cbb 431: onsuccess: #2255: 1: Success after binutils/gcc/linux/g [...] discards 96fe53e816 430: onsuccess: #2254: 1: Success after binutils/gcc/linux/g [...] discards 63e631e734 429: onsuccess: #2253: 1: Success after binutils/gcc/glibc/g [...] discards 5608a70dd3 428: onsuccess: #2252: 1: Success after binutils/gdb: 2 commits discards 928ce204f3 427: onsuccess: #2251: 1: Success after binutils/gcc/linux/g [...] discards 21f072351b 426: onsuccess: #2250: 1: Success after binutils/linux/gdb: [...] discards 0e991220c8 425: onsuccess: #2249: 1: Success after binutils/gcc/linux/g [...] discards ba7558884f 424: onsuccess: #2248: 1: Success after gcc: 6 commits discards 0b94ef9455 423: onsuccess: #2247: 1: Success after gcc/linux: 8 commits discards 77da97c665 422: onsuccess: #2246: 1: Success after binutils/gcc/linux/g [...] discards 3480080bc2 421: onsuccess: #2245: 1: Success after binutils/gcc/glibc/g [...] discards 1a12df2956 420: onsuccess: #2244: 1: Success after gcc/glibc: 5 commits discards cf2c7f5807 419: onsuccess: #2243: 1: Success after binutils/gcc/linux/g [...] discards 55f2ee293b 418: onsuccess: #2239: 1: Success after binutils/gcc/gdb: 5 commits discards 9783969f27 417: onsuccess: #2238: 1: Success after binutils/gcc/linux/g [...] discards 4d18e4b759 416: onsuccess: #2237: 1: Success after binutils/gcc/glibc/g [...] discards 265647b085 415: onsuccess: #2236: 1: Success after binutils/gcc/gdb: 14 [...] discards 1b495513ef 414: onsuccess: #2235: 1: Success after binutils/gcc/gdb: 13 [...] discards ef0120b96b 413: onsuccess: #2234: 1: Success after binutils/gcc/linux/g [...] discards f97e66ea97 412: onsuccess: #2233: 1: Success after binutils/gcc/glibc/g [...] discards c17b5d424c 411: onsuccess: #2232: 1: Success after gcc: 3 commits discards a0b49680a7 410: onsuccess: #2231: 1: Success after binutils/gcc/linux/g [...] discards e48ce81cff 409: onsuccess: #2230: 1: Success after binutils/gcc/glibc/g [...] discards 120eff3419 408: onsuccess: #2229: 1: Success after binutils/gcc/gdb: 26 [...] discards b4e73e50d6 407: onsuccess: #2228: 1: Success after binutils/gcc/linux/g [...] discards f84640a9f0 406: onsuccess: #2227: 1: Success after binutils/linux/glibc [...] discards a630aa5e19 405: onsuccess: #2226: 1: Success after gcc/glibc: 39 commits discards c79de3ea6d 404: onsuccess: #2225: 1: Success after binutils/gcc/gdb: 10 [...] discards 3b2a374403 403: onsuccess: #2224: 1: Success after binutils/gcc/linux/g [...] discards 6b548f335c 402: onsuccess: #2223: 1: Success after binutils/gcc/gdb: 10 [...] discards 8b806a708f 401: onsuccess: #2222: 1: Success after binutils/gcc/gdb: 10 [...] discards ee2258cee2 400: onsuccess: #2221: 1: Success after binutils/gcc/linux/g [...] discards 9a396dffff 399: onsuccess: #2220: 1: Success after binutils/gcc/linux/g [...] discards 1e1fbd9dbd 398: onsuccess: #2219: 1: Success after binutils/gcc/gdb/qem [...] new 576477a888 398: onsuccess: #2219: 1: Success after binutils/gcc/gdb/qem [...] new 0e99f47ed8 399: onsuccess: #2220: 1: Success after binutils/gcc/linux/g [...] new fca4153eb4 400: onsuccess: #2221: 1: Success after binutils/gcc/linux/g [...] new 3107eb26bb 401: onsuccess: #2222: 1: Success after binutils/gcc/gdb: 10 [...] new 4a27cd39c9 402: onsuccess: #2223: 1: Success after binutils/gcc/gdb: 10 [...] new 0dda22a3e8 403: onsuccess: #2224: 1: Success after binutils/gcc/linux/g [...] new ff4ceae874 404: onsuccess: #2225: 1: Success after binutils/gcc/gdb: 10 [...] new cd6afca0e8 405: onsuccess: #2226: 1: Success after gcc/glibc: 39 commits new 77d3ca933c 406: onsuccess: #2227: 1: Success after binutils/linux/glibc [...] new 5af2a11186 407: onsuccess: #2228: 1: Success after binutils/gcc/linux/g [...] new 9592a65416 408: onsuccess: #2229: 1: Success after binutils/gcc/gdb: 26 [...] new 0fe146819e 409: onsuccess: #2230: 1: Success after binutils/gcc/glibc/g [...] new 92f7101508 410: onsuccess: #2231: 1: Success after binutils/gcc/linux/g [...] new 2645eb604c 411: onsuccess: #2232: 1: Success after gcc: 3 commits new bd812f38a6 412: onsuccess: #2233: 1: Success after binutils/gcc/glibc/g [...] new 2938aef12f 413: onsuccess: #2234: 1: Success after binutils/gcc/linux/g [...] new bcff6a6f22 414: onsuccess: #2235: 1: Success after binutils/gcc/gdb: 13 [...] new 0aec68e149 415: onsuccess: #2236: 1: Success after binutils/gcc/gdb: 14 [...] new 49b03674d8 416: onsuccess: #2237: 1: Success after binutils/gcc/glibc/g [...] new 6c0cfc4857 417: onsuccess: #2238: 1: Success after binutils/gcc/linux/g [...] new 4d13b75ef6 418: onsuccess: #2239: 1: Success after binutils/gcc/gdb: 5 commits new 401bbb2f28 419: onsuccess: #2243: 1: Success after binutils/gcc/linux/g [...] new 62cfd7d4e9 420: onsuccess: #2244: 1: Success after gcc/glibc: 5 commits new 1e38807d3b 421: onsuccess: #2245: 1: Success after binutils/gcc/glibc/g [...] new 8c11a498db 422: onsuccess: #2246: 1: Success after binutils/gcc/linux/g [...] new dae6045e7d 423: onsuccess: #2247: 1: Success after gcc/linux: 8 commits new f79026a168 424: onsuccess: #2248: 1: Success after gcc: 6 commits new f29dc80f76 425: onsuccess: #2249: 1: Success after binutils/gcc/linux/g [...] new 5a917521c6 426: onsuccess: #2250: 1: Success after binutils/linux/gdb: [...] new 71f34f1d4d 427: onsuccess: #2251: 1: Success after binutils/gcc/linux/g [...] new dffe44d45e 428: onsuccess: #2252: 1: Success after binutils/gdb: 2 commits new 84ebd488fe 429: onsuccess: #2253: 1: Success after binutils/gcc/glibc/g [...] new b34fe1c078 430: onsuccess: #2254: 1: Success after binutils/gcc/linux/g [...] new e686b354a1 431: onsuccess: #2255: 1: Success after binutils/gcc/linux/g [...] new 20d4ba64cd 432: onsuccess: #2256: 1: Success after binutils/gdb: 10 commits new 80c82b7dc4 433: onsuccess: #2257: 1: Success after binutils/gcc/gdb/qem [...] new 110c317325 434: onsuccess: #2258: 1: Success after binutils/gcc/linux/g [...] new b7ebe7d68b 435: onsuccess: #2259: 1: Success after binutils/gcc/linux/g [...] new f369096ca8 436: onsuccess: #2260: 1: Success after gcc: 7 commits new e12a6fdf3e 437: onsuccess: #2261: 1: Success after binutils/gcc/glibc/g [...] new 6c717e40cf 438: onsuccess: #2263: 1: Success after binutils/gcc/linux/g [...] new 2d2819254a 439: onsuccess: #2264: 1: Success after binutils/gcc/gdb: 13 [...] new 71d17f6929 440: onsuccess: #2265: 1: Success after binutils/gcc/linux/g [...] new be0170419d 441: onsuccess: #2266: 1: Success after binutils/gcc/linux/g [...] new 7dceefd1c3 442: onsuccess: #3: 1: Success after binutils/gcc/glibc/gdb/ [...] new 563926cb04 443: onsuccess: #4: 1: Success after binutils/gcc/gdb/qemu: [...] new fd5c52e48c 444: onsuccess: #5: 1: Success after binutils/gcc/linux/glib [...] new 7ae66dcece 445: onsuccess: #6: 1: Success after binutils/gcc/linux/gdb: [...] new 3a0e7aa412 446: onsuccess: #7: 1: Success after binutils/gcc/gdb: 5 commits new 17dd21d746 447: onsuccess: #8: 1: Success after binutils/gcc/linux/glib [...] new 8b40e4033e 448: onsuccess: #9: 1: Success after binutils/gcc/linux/gdb: [...] new 91dcc209a5 449: onsuccess: #10: 1: Success after binutils/gcc/linux/gli [...] new 3392d9876b 450: onsuccess: #11: 1: Success after binutils/gcc/linux/gli [...] new 077f735576 451: onsuccess: #12: 1: Success after binutils/gcc/linux/gli [...] new 017fa0ca03 452: onsuccess: #13: 1: Success after binutils/gcc/linux/gli [...] new ab5c633bdb 453: onsuccess: #14: 1: Success after binutils/gcc/linux/gdb [...] new fddd710d87 454: onsuccess: #15: 1: Success after binutils/gcc/linux/gdb [...] new 7b52feb0dc 455: onsuccess: #16: 1: Success after binutils/gcc/linux/gdb [...] new d5f75f5d33 456: onsuccess: #17: 1: Success after binutils/gcc/linux/gli [...] new 833641e26a 457: onsuccess: #18: 1: Success after binutils/gcc/linux/gli [...] new 45d92df135 458: onsuccess: #19: 1: Success after binutils/gcc/linux/gli [...] new 581381f3c3 459: onsuccess: #20: 1: Success after binutils/gcc/linux/gdb [...] new 5a25010b87 460: onsuccess: #21: 1: Success after binutils/gcc/linux/gli [...] new 558fa4f776 461: onsuccess: #22: 1: Success after binutils/gcc/linux/gdb [...] new ac637ae7a0 462: onsuccess: #23: 1: Success after binutils/gcc/linux/gli [...] new ca4dbdc01d 463: onsuccess: #24: 1: Success after binutils/gcc/linux/gli [...] new 51db651e89 464: onsuccess: #25: 1: Success after binutils/gcc/linux/gli [...] new d0a19419b4 465: onsuccess: #26: 1: Success after binutils/gcc/linux/gdb [...] new 9bc92da3a0 466: onsuccess: #27: 1: Success after binutils/gcc/linux/gdb [...] new e8119555f6 467: onsuccess: #28: 1: Success after binutils/gcc/linux/gdb [...] new 02439847b8 468: onsuccess: #29: 1: Success after binutils/gcc/linux/gdb [...] new a2fdbbdfbf 469: onsuccess: #30: 1: Success after binutils/gcc/linux/gdb [...] new 3d196196c4 470: onsuccess: #31: 1: Success after binutils/gcc/linux/gdb [...] new 1eb191f526 471: onsuccess: #32: 1: Success after binutils/gcc/linux/gli [...] new 2a17d6c58d 472: onsuccess: #33: 1: Success after binutils/gcc/linux/gdb [...] new 65f6b64120 473: onsuccess: #34: 1: Success after binutils/gcc/linux/gdb [...] new 03a6845b86 474: onsuccess: #35: 1: Success after binutils/gcc/linux/gdb [...] new ada0640ee2 475: onsuccess: #36: 1: Success after binutils/gcc/linux/gdb [...] new 14ac77e362 476: onsuccess: #37: 1: Success after binutils/gcc/linux/gli [...] new 3106c1b121 477: onsuccess: #39: 1: [TCWG CI] Success after binutils/gcc [...] new a2db9966cf 478: onsuccess: #40: 1: [TCWG CI] Success after binutils/gcc [...] new 8f6f5feafe 479: onsuccess: #41: 1: [TCWG CI] Success after binutils/gcc [...] new b4028ef715 480: onsuccess: #42: 1: [TCWG CI] Success after binutils/gcc [...] new c3e5a0e97e 481: onsuccess: #43: 1: [TCWG CI] Success after binutils/gcc [...] new fbd17b662d 482: onsuccess: #44: 1: [TCWG CI] Success after binutils/gcc [...] new 130dff27b7 483: onsuccess: #45: 1: [TCWG CI] Success after binutils/gcc [...] new 754d6c443d 484: onsuccess: #46: 1: [TCWG CI] Success after binutils/gcc [...] new 6ebc9b2468 485: onsuccess: #47: 1: [TCWG CI] Success after binutils/gcc [...] new 0ee12a7cb1 486: onsuccess: #49: 1: [TCWG CI] Success after binutils/gcc [...] new 5abf03cf34 487: onsuccess: #50: 1: [TCWG CI] Success after binutils/gcc [...] new 6cd6a2d0bf 488: onsuccess: #51: 1: [TCWG CI] Success after binutils/gcc [...] new fcec70cd75 489: onsuccess: #52: 1: [TCWG CI] Success after binutils/gcc [...] new 87700aba83 490: onsuccess: #53: 1: [TCWG CI] https://ci.linaro.org/job/ [...] new 3e224f42b0 491: onsuccess: #54: 1: [TCWG CI] https://ci.linaro.org/job/ [...] new b5ff1c94cc 492: onsuccess: #55: 1: [TCWG CI] https://ci.linaro.org/job/ [...] new 0865d9ed96 493: onsuccess: #56: 1: [TCWG CI] https://ci.linaro.org/job/ [...] new 06977de817 494: onsuccess: #58: 1: [TCWG CI] https://ci.linaro.org/job/ [...] new 0b486c5405 495: onsuccess: #59: 1: [TCWG CI] https://ci.linaro.org/job/ [...] new 651369964c 496: onsuccess: #60: 1: [TCWG CI] https://ci.linaro.org/job/ [...] new 66dea88955 497: onsuccess: #64: 1: [TCWG CI] https://ci.linaro.org/job/ [...] new 32cd966df8 498: onsuccess: #65: 1: [TCWG CI] https://ci.linaro.org/job/ [...] new 9f8c93d7c3 499: force: #67: 1: [TCWG CI] https://ci.linaro.org/job/tcwg [...]

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 (de39bd93de) \ 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: 00-sumfiles/g++.log.0.xz | Bin 0 -> 2713668 bytes 00-sumfiles/g++.log.xz | Bin 2686492 -> 0 bytes sumfiles/g++.sum => 00-sumfiles/g++.sum.0 | 2 +- 00-sumfiles/gcc.log.0.xz | Bin 0 -> 2230540 bytes 00-sumfiles/gcc.log.1.xz | Bin 0 -> 38308 bytes 00-sumfiles/gcc.log.xz | Bin 2210512 -> 0 bytes sumfiles/gcc.sum => 00-sumfiles/gcc.sum.0 | 4 +- 00-sumfiles/gcc.sum.1 | 1668 ++++++++++++++++++++ 00-sumfiles/gfortran.log.0.xz | Bin 0 -> 908516 bytes 00-sumfiles/gfortran.log.xz | Bin 904528 -> 0 bytes .../gfortran.sum => 00-sumfiles/gfortran.sum.0 | 2 +- 00-sumfiles/libatomic.log.0.xz | Bin 0 -> 2284 bytes 00-sumfiles/libatomic.log.xz | Bin 2284 -> 0 bytes .../libatomic.sum => 00-sumfiles/libatomic.sum.0 | 2 +- 00-sumfiles/libgomp.log.0.xz | Bin 0 -> 217616 bytes 00-sumfiles/libgomp.log.xz | Bin 217524 -> 0 bytes sumfiles/libgomp.sum => 00-sumfiles/libgomp.sum.0 | 2 +- 00-sumfiles/libitm.log.0.xz | Bin 0 -> 2688 bytes 00-sumfiles/libitm.log.xz | Bin 2692 -> 0 bytes sumfiles/libitm.sum => 00-sumfiles/libitm.sum.0 | 2 +- 00-sumfiles/libstdc++.log.0.xz | Bin 0 -> 454452 bytes 00-sumfiles/libstdc++.log.xz | Bin 450988 -> 0 bytes .../libstdc++.sum => 00-sumfiles/libstdc++.sum.0 | 0 01-reset_artifacts/console.log.xz | Bin 2200 -> 2240 bytes 02-prepare_abe/console.log.xz | Bin 2452 -> 2448 bytes 03-build_abe-binutils/console.log.xz | Bin 27000 -> 27148 bytes 04-build_abe-stage1/console.log.xz | Bin 89528 -> 89080 bytes 05-clean_sysroot/console.log.xz | Bin 332 -> 332 bytes 06-build_abe-linux/console.log.xz | Bin 8668 -> 8684 bytes 07-build_abe-glibc/console.log.xz | Bin 233544 -> 231228 bytes 08-build_abe-stage2/console.log.xz | Bin 225172 -> 224640 bytes 09-build_abe-gdb/console.log.xz | Bin 34336 -> 34332 bytes 10-build_abe-qemu/console.log.xz | Bin 29284 -> 29628 bytes 11-build_abe-dejagnu/console.log.xz | Bin 3856 -> 3860 bytes 12-build_abe-check_gcc/console.log.xz | Bin 7428 -> 7720 bytes 12-build_abe-check_gcc/flaky.xfail | 2 +- 13-check_regression/console.log.xz | Bin 1284 -> 2028 bytes 13-check_regression/extra-bisect-params | 1 + 13-check_regression/fails.sum | 6 + 13-check_regression/results.compare | 43 +- 13-check_regression/results.compare2 | 6 +- 13-check_regression/results.regressions | 32 + 14-update_baseline/console.log | 74 +- jenkins/notify.sh | 2 +- mail/check-regression-status.txt | 2 +- mail/results.compare | 43 +- mail/results.regressions | 32 + manifest.sh | 19 +- results | 32 + sumfiles/g++.sum | 6 +- sumfiles/gcc.sum | 8 +- sumfiles/gfortran.sum | 6 +- sumfiles/libatomic.sum | 6 +- sumfiles/libgomp.sum | 6 +- sumfiles/libitm.sum | 6 +- sumfiles/libstdc++.sum | 4 + 56 files changed, 1929 insertions(+), 89 deletions(-) create mode 100644 00-sumfiles/g++.log.0.xz delete mode 100644 00-sumfiles/g++.log.xz copy sumfiles/g++.sum => 00-sumfiles/g++.sum.0 (99%) create mode 100644 00-sumfiles/gcc.log.0.xz create mode 100644 00-sumfiles/gcc.log.1.xz delete mode 100644 00-sumfiles/gcc.log.xz copy sumfiles/gcc.sum => 00-sumfiles/gcc.sum.0 (99%) create mode 100644 00-sumfiles/gcc.sum.1 create mode 100644 00-sumfiles/gfortran.log.0.xz delete mode 100644 00-sumfiles/gfortran.log.xz copy sumfiles/gfortran.sum => 00-sumfiles/gfortran.sum.0 (99%) create mode 100644 00-sumfiles/libatomic.log.0.xz delete mode 100644 00-sumfiles/libatomic.log.xz copy sumfiles/libatomic.sum => 00-sumfiles/libatomic.sum.0 (98%) create mode 100644 00-sumfiles/libgomp.log.0.xz delete mode 100644 00-sumfiles/libgomp.log.xz copy sumfiles/libgomp.sum => 00-sumfiles/libgomp.sum.0 (99%) create mode 100644 00-sumfiles/libitm.log.0.xz delete mode 100644 00-sumfiles/libitm.log.xz copy sumfiles/libitm.sum => 00-sumfiles/libitm.sum.0 (97%) create mode 100644 00-sumfiles/libstdc++.log.0.xz delete mode 100644 00-sumfiles/libstdc++.log.xz copy sumfiles/libstdc++.sum => 00-sumfiles/libstdc++.sum.0 (100%) create mode 100644 13-check_regression/extra-bisect-params create mode 100644 13-check_regression/fails.sum create mode 100644 13-check_regression/results.regressions create mode 100644 mail/results.regressions