t/nqp/19-file-ops.t failure in pre-2016.01

[coke]

This test was failing on OS X for me just prior to the 2016.01 release.

Since we cannot fudge here, commented out the test.

Since this is a new test, should be OK that the behavior isn't conforming to a new test yet.

  ### This test was added between 2015.12 and 2016.01, but was failing.
  # since it's something new, commenting out for 2016.01 release.
  #ok(nqp::lstat_time($symlink, $flag) != nqp::lstat_time($file, $flag), 'lstat_time doesn\'t follow symlink');

[usev6]

Does that test still fail on OS X? It works for me on linux and freebsd for both, MoarVM and JVM.

[tisonkun]

@coke How is it going? Can we safely close this issue?

[coke]

The test is still commented out since I opened this ticket, so I'm not sure people have been testing it on any platform.

I uncommented it and updated the test count, it's passing for me here on OS X. Someone else can re-open this ticket if needed.

[coke]

This test was refudged before the release.

Re-opening ticket.

[coke]

See 9a43e6c444

[tisonkun]

Yes, I just meet it several hours ago..

[coke]

I unskipped it again, let's see if it stays unskipped for the next release.

[jdv]

Skipped again. What I'm seeing is the nqp test run post nqp build on the release tarball fail on the first run but work subsequent runs... Looks like so:

t/nqp/019-file-ops.t ................... Failed 1/112 subtests
(less 1 skipped subtest: 110 okay)