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. https://github.com/apple/swift-cmark/pull/1 https://github.com/jgm/cmark
All tests pass, and I get the final two lines: -- check-swift-macosx-x86_64 finished -- --- Finished tests for swift --- 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? On Sat, Dec 12, 2015 at 10:51 AM, Alexander Alemayhu <alexan...@alemayhu.com > wrote: > > > On 11 Dec 2015, at 20:12, Dylan Brown via swift-users < > swift-users@swift.org> wrote: > > > > 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. > > 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? > > I was also experiencing the same issue. Have you looked at pull request > #1 for > swift-cmark[0]? Pulling in the upstream cmark changes resolved the > failures > for me. > > [0]: https://github.com/apple/swift-cmark/pull/1 > >
_______________________________________________ swift-users mailing list swift-users@swift.org https://lists.swift.org/mailman/listinfo/swift-users
