Cheers for the clarification. I will spend some time working through some of the other failures, should help me get to grips with it all :)
James Sent from my iPhone > On 14 May 2016, at 15:02, Bouke Haarsma via swift-corelibs-dev > <swift-corelibs-dev@swift.org> wrote: > > On 2016-05-14 09:05:08 +0000, James Lee via swift-corelibs-dev said: > > > > Please excuse my ignorance, I have looked into the POSIX calls, but am I > right in assuming that the EBADF is due to the test calling to a file that > doesn't exist and that is just how OSX handles this case? > > > > The problem on OSX was that closing the same FD in the child process would > result in the EBADF. The change in the error handling posted before made the > error more visible. The actual fix for OSX was to make sure a single FD was > closed only once. See also PR #363 > https://github.com/apple/swift-corelibs-foundation/pull/362, especially > https://github.com/apple/swift-corelibs-foundation/pull/363/commits/3fd0df28107847b7121f6cb2f823fbad9e2ddcff. > > > > - Bouke > > _______________________________________________ > swift-corelibs-dev mailing list > swift-corelibs-dev@swift.org > https://lists.swift.org/mailman/listinfo/swift-corelibs-dev
_______________________________________________ swift-corelibs-dev mailing list swift-corelibs-dev@swift.org https://lists.swift.org/mailman/listinfo/swift-corelibs-dev
