<div dir="ltr"><div>Thanks Alexander! I do have Python 3.5 installed via Anaconda on my Mac. Merging in the upstream cmark changes as in pull #1 for swift-cmark seems to have solved my issue.</div><div><a href="https://github.com/apple/swift-cmark/pull/1">https://github.com/apple/swift-cmark/pull/1</a><br></div><div><a href="https://github.com/jgm/cmark">https://github.com/jgm/cmark</a><br></div><div><br></div><div>All tests pass, and I get the final two lines:</div><div>-- check-swift-macosx-x86_64 finished --<br>--- Finished tests for swift ---<br></div><div><br></div><div>However, I still can't find check-swift in my build directory. Running `find . -name '*check-swift*'` returns no results. Is there some flag needed on the build-script to create these files?</div></div><div class="gmail_extra"><br><div class="gmail_quote">On Sat, Dec 12, 2015 at 10:51 AM, Alexander Alemayhu <span dir="ltr"><<a href="mailto:alexander@alemayhu.com" target="_blank">alexander@alemayhu.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><span class=""><br>
> On 11 Dec 2015, at 20:12, Dylan Brown via swift-users <<a href="mailto:swift-users@swift.org">swift-users@swift.org</a>> wrote:<br>
><br>
> Hello! When running `utils/build-script --clean -t`, I'm able to complete the build but it regularly fails the same 4/6 tests. Also, check-swift and check-swift-validation are not found in the build directory alongside Ninja-DebugAssert.<br>
> I've been working at this for a while, and I'm not sure where to look next. Any ideas what could be going wrong?<br>
<br>
</span>I was also experiencing the same issue. Have you looked at pull request #1 for<br>
swift-cmark[0]? Pulling in the upstream cmark changes resolved the failures<br>
for me.<br>
<br>
[0]: <a href="https://github.com/apple/swift-cmark/pull/1" rel="noreferrer" target="_blank">https://github.com/apple/swift-cmark/pull/1</a><br>
<br>
</blockquote></div><br></div>