On Tue, Dec 26, 2017 at 08:06:36PM +0000, Zefram wrote: > James E Keenan via RT wrote: > >However, I see that we have a FAIL in this test file being reported on > >a Cygwin smoke rig. > > That's annoying. The test allows for a platform to veto having an > unlinked cwd, and I'd expect Windows to exercise that veto, but apparently > it's not, so I don't know what arrangement Cygwin actually ends up with. > Apparently it's getting the wrong result from the XS getcwd(), and then > terminating when running the XS abs_path(). I don't see how that could > terminate when getcwd() didn't. > > I'd like to see more detail of the test output and the mode of > termination. So IIUC, in this ticket, the infinite loop problem has been fixed on all platforms except Cygwin. CXan we do anything about that (e.g. skip the test), and if so can this ticket then be removed from the 5.28 blockers? -- "I used to be with it, but then they changed what ‘it’ was, and now what I’m with isn’t it. And what’s ‘it’ seems weird and scary to me." -- Grandpa Simpson (It will happen to you too.)Thread Previous | Thread Next