Open phated opened 6 years ago
If it consistently passes on all platforms + versions we can remove it
Alternatively we can scope the flakeyness to the appropriate version / platform rather than blanket flake. I can dig into doing this soon
I believe it's due to one of our tests needing certain file permissions. Ping me if you need to discuss anything.
CI: https://ci.nodejs.org/job/citgm-smoker-nobuild/257
I am only seeing it failing on WIN, rerun also failed.
Suggest marking it flaky on WIN until this get fixed.
I am seeing a lot of failures across various platforms:
10:22:02 error: | 223 passing (25s)
10:22:02 error: | 18 pending
10:22:02 error: | 1 failing
10:22:02 error: |
10:22:02 error: | 1) .dest() with custom owner calls fchown when the uid and/or gid are provided on the vinyl stat:
10:22:02 error: |
10:22:02 error: | Uncaught Error: Expected 0 to equal 1
10:22:02 error: | + expected - actual
10:22:02 error: |
10:22:02 error: | -0
10:22:02 error: | +1
10:22:02 error: |
10:22:02 error: | at assert (node_modules/expect/lib/assert.js:29:9)
10:22:02 error: | at Expectation.toEqual (node_modules/expect/lib/Expectation.js:81:30)
10:22:02 error: | at assert (test/dest-owner.js:49:38)
10:22:02 error: | at ConcatStream.<anonymous> (node_modules/concat-stream/index.js:36:43)
10:22:02 error: | at finishMaybe (node_modules/readable-stream/lib/_stream_writable.js:620:14)
10:22:02 error: | at endWritable (node_modules/readable-stream/lib/_stream_writable.js:628:3)
10:22:02 error: | at ConcatStream.Writable.end (node_modules/readable-stream/lib/_stream_writable.js:584:41)
10:22:02 error: | at Pumpify.onend (node_modules/readable-stream/lib/_stream_readable.js:577:10)
10:22:02 error: | at endReadableNT (node_modules/readable-stream/lib/_stream_readable.js:1000:12)
10:22:02 error: | at _combinedTickCallback (internal/process/next_tick.js:80:11)
10:22:02 error: | at process._tickCallback (internal/process/next_tick.js:104:9)
10:22:02 error: |
10:22:02 error: |
10:22:02 error: |
10:22:02 error: |
10:22:02 error: | npm ERR! Test failed. See above for more details.
10:22:02 error: done | The smoke test has failed.
NOTE: WIN failures https://github.com/nodejs/citgm/issues/537#issuecomment-368887232 is a different error
Vinyl-fs interacts with the filesystem so you need to provide proper interactions with the fs (fchown in your log).
The windows error looks like an install error. Maybe rebuilding native modules with chokidar (uses pre-gyp, I believe).
Can we get this fixed? I just noticed that our test suite is broken on node 10 due to some breaking changes with file modes that wasn't in node 9. Ref https://github.com/gulpjs/vinyl-fs/issues/300
@phated getting this fixed would involved getting the test suite to pass and consistently pass. While there are still failures on Node.js 10 we won't be able to do that.
Do you have a timeline to getting the suite working? Do you need support on that?
The reported failures in https://github.com/gulpjs/vinyl-fs/issues/300 look like https://github.com/nodejs/node/issues/20498.
@richardlau that's definitely the issue.
Looks like https://github.com/nodejs/node/pull/20588 will hopefully fix this issue
Looks like the fixes landed in 10.5 - hopefully we can get this unmarked flakey now.
Ping. I just verified that our tests work on node 10 - had to make a change to our file descriptor tests.
I believe vinyl-fs has been flagged as flakey but we've encountered some issues that probably would have been caught by citgm. Can we work to get off the flakey list?