-
-
Notifications
You must be signed in to change notification settings - Fork 588
bazel coverage failed due to "No source for code" #1217
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
Comments
Just an FYI, that there is a newer issue on the main bazel repo: bazelbuild/bazel#18362. |
This issue has been automatically marked as stale because it has not had any activity for 180 days. It will be closed if no further activity occurs in 30 days. |
This issue was automatically closed because it went 30 days without a reply since it was labeled "Can Close?" |
Facing the same issue, any solutions? |
🐞 bug report
Affected Rule
The issue is caused by the rule:bazel coverage
Is this a regression?
Not sureDescription
bazel test
passed andbazel coverage
failed.We use pytest
tmpdir
to create temporary directory for one of the test cases during execution and it is assumed to be removed after the test cases finished automatically. It seems bazel coverage is trying to find the source file for the files in temporary directory which it shouldn't. It will throw "no source file found" error and this prevents generating coverage report.Also, Is there a workaround to ignore "no source for code" error?
Logs:
🔬 Minimal Reproduction
🔥 Exception or Error
🌍 Your Environment
Operating System:
Output of
bazel version
:Rules_python version:
Anything else relevant?
The text was updated successfully, but these errors were encountered: