-
Notifications
You must be signed in to change notification settings - Fork 1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Test failure in compact.js #669
Comments
See #673 - related? |
Could be. I can't figure out how we're not getting logs from the tests that are reported as passing in the same run. @wohali What do you think about adding a few commands to the script just before starting the javascript test suite to check on host health? I'm thinking of checking things like df, free, netstat, and maybe something like |
I did some of that in the jenkins-pipeline branch: Lines 92 to 103 in 32eb49a
It's a good idea. Even crazier could have a mini benchmark - try to write to disk, read back, run a few cpu speed tests, memory usage etc. And maybe decide test environment is just crappy and give up. Cause it certainly seems crappy a lot of the times. |
@davisp we lose it because In short |
* Use double backticks in src/api/server/authn.rst * Review update: Add double backticks for config/code only
Seems like a new one and a bit of an oddity.
Travis log:
And the dev/logs/node1.log from the uploaded report
I don't understand how the previous tests aren't showing up in that log.
The text was updated successfully, but these errors were encountered: