Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This is the command I tried to use to generate test coverage report:
Without any changes, this is the error that I was getting:
Bazel command output
The error seems to have been coming from the
//test/platform/swift/bridging:rust_bridge
dependency of the used bazel BUILD target so I tried to limit the number of run tests and their dependencies next.After I changed a bazel BUILD target to run tests from
ConfigurationTests.swift
file only I started getting following error:Bazel command output
The above error makes sense since our custom Rust build doesn't include profiling-related symbols. After moving to standard Rust build this is the error I am getting:
Bazel command output
In the above bazel command output you can see that bazel appears to be stuck after it's done running all tests from the specified target. I tried to update bazel to 7.3.1 to see whether that would get rid of the "stuck" error but it didn't help.