-
Notifications
You must be signed in to change notification settings - Fork 45
tests all fail #7
Comments
On node 6.9.1, nodereport commit 7cd3f76, ubuntu linux x64, g++ (Ubuntu 5.4.0-6ubuntu1~16.04.2) 5.4.0 20160609 |
Can you try running the tests using: |
Above is your problem, the tests assumed that The tests don't instantly fail now (EDIT: "now" meaning after #11), but they don't complete, they print this to screen (EDIT: and then hang):
With a test log of https://gist.github.com/d4cef9d4f5691c44eb06ad97c000a380 Btw, its probably worth getting this building and running in CI, either the nodefoundation's if possible, or Travis. |
@sam-github prototype fix for the hang you are seeing in the tests: |
It's easier for me to git clone things you PR (you can PR before something is known to work, its OK). I'll go find add you as a git source and fetch your code. |
that's OS X, the original test was on Linux, I'll try Linux when I get home |
I merged #11 and doing so closed this issue. I'm assuming we need to keep this open as the tests are still failing, re-opening. |
^--- linux run On node 7, the tests never complete. My suspicion would be the use of Can you not reproduce what I see, @rnchamberlain ? I assume the tests pass for you, but on what platforms? |
@sam-github I reproduced the test suite hang on Linux x86, node 7. It gets stuck on test 3. #16 fixes it for me, the test suite completes now, all tests pass. The autorun.js was supposed to cope with a hang in one of the individual tests, but I expect the restructure that @richardlau is doing will improve that aspect. I'll look at the node 7 deprecation warnings, |
The node v7 deprecation warnings were from fs.unlink() in autorun.js. They are fixed in #15 (the NodeReport files produced by the tests are no longer deleted). |
@sam-github fyi the re-write of the tests using tap has landed now, could you re-test when convenient, thanks. |
|
The text was updated successfully, but these errors were encountered: