Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Support Stacktrace when test crashes #35

Open
bigbangvn opened this issue Oct 4, 2021 · 1 comment
Open

Support Stacktrace when test crashes #35

bigbangvn opened this issue Oct 4, 2021 · 1 comment

Comments

@bigbangvn
Copy link

Currently, when tests crashes, seems there is no stack trace. That would help a lot to investigate issue, especially for me when I migrate a project to bazel and some unit test crash.

How to reproduce:
Just put fatalError("") in unit tests or in testing swift code.

A similar issue is opened in Bazel but it seems belong the this xctestrunner: bazelbuild/bazel#8050
@albertdai
Copy link
Contributor

Bang, could you find the crash reports in the xcresult generated under $TEST_UNDECLARED_OUTPUTS_DIR?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@bigbangvn @albertdai