We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
It runs, but fails early. For example, there's no /dev/urandom on Windows.
The text was updated successfully, but these errors were encountered:
for test failures, I pushed a commit to my repo where I enabled all tests again: https://ci.appveyor.com/project/JanSchulz/jq/build/1.0.41 https://ci.appveyor.com/project/JanSchulz/jq
Sorry, something went wrong.
Yeah, and this is the log from my build prior to disabling the failing tests: https://ci.appveyor.com/project/nicowilliams/jq/build/1.0.1/job/fsxq3h06tt8oq448
We'll also need to add regression tests for jq bugs on Windows.
The first problem in tests/shtest, of course, is that the warnings we're looking for have Windows line endings (\r\n).
tests/shtest
\r\n
No branches or pull requests
It runs, but fails early. For example, there's no /dev/urandom on Windows.
The text was updated successfully, but these errors were encountered: