-
-
Notifications
You must be signed in to change notification settings - Fork 759
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
1.18.1: Bazel based test runs fail in the KtTestCompiler
#4140
Comments
Shouldn't we look into processing the resources as a JAR to address the Bazel scenario as well rather than excluding it?
Discussed offline: This fix/patch will end up in Detekt |
The proposed patch fixes a real world issue. Maybe the resources based testing in Bazel can be fixed when it is a real world issue :) |
It does not fix test cases that use resource files from the project, but it's a start at least.
It does not fix test cases that use resource files from the project, but it's a start at least.
When using Bazel as a test runner for Detekt extensions, the tests fail with
The difference between Gradle and Bazel in this case is that Gradle provides the test classes as file paths, whereas Bazel provides them in a JAR.
Since we're not using resource based tests in our consuming project, it's easy enough to fix this by deferring the
root
path calculation.The question is, if we fix this, when might this be available in an upstream release?
The text was updated successfully, but these errors were encountered: