Luis Padron

Do you have more information to provide? Maybe the logs during launch would help here, does this happen consistently for you?

Thanks for contributing! FWIW there's some commits in upstream adding support for this we'll likely take. Someone just needs to do the cherry-picks

This is the upstream commit i mean: https://github.com/bazelbuild/rules_swift/commit/26e26241bd118776af214c6f9ea66b918eac87f6 You can find several other Swift Testing related commits we need to cherry-pick over in: https://github.com/bazelbuild/rules_swift/commits/upstream I havent checked rules_apple yet but...

> Just to clarify, are you suggesting to just literally cherry-pick the commit your referenced (as well as any others that are needed) and then make my own PR with...

@brentleyjones Would you have some time to review this as well? Thank you!

I'm re-opening because it seems like Bazel will not be able to support this within Starlark (analysis time) but if we can move this work to the execution phase to...

Some things I can think of we should go over: - Removal of `swift.emit_symbol_graph` feature, we should point users to the new `swift_symbol_graph_extract` rule. - Changes to C/C++/Objective-C module name...

Filed a bug with Swift: https://github.com/swiftlang/swift/issues/79159

I tried the opening project in execution root work around but that didn't seem to work for this case. This seems to effect other error message tracing as well, like...

Some more testing here: --- In the first image (Vanilla Xcode) the failure has the context where as second image (Bazel) the information seems to be lost.