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
How to reproduce: Manually deleting the JUnit XML report from the build/test-results/opa directory, then run ./gradlew testRego.
build/test-results/opa
./gradlew testRego
Doing a clean testRego fixes the problem so it's likely just due to some assertion of the directory/file state before the test is run being erroneous.
clean testRego
The text was updated successfully, but these errors were encountered:
GH-14 Failed to read input stream
ec32094
Fix bug in directory creation logic and split the nested try-catch statements into separate ones for more granular error messages. Fixes #14
be7c28e
4c8bd02
Merge pull request #17 from Bisnode/GH-14-Failed-to-read-input-stream
2df1203
Successfully merging a pull request may close this issue.
How to reproduce: Manually deleting the JUnit XML report from the
build/test-results/opa
directory, then run./gradlew testRego
.Doing a
clean testRego
fixes the problem so it's likely just due to some assertion of the directory/file state before the test is run being erroneous.The text was updated successfully, but these errors were encountered: