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

Improve test failure backtrace #6

Open
iampatbrown opened this issue May 30, 2022 · 0 comments
Open

Improve test failure backtrace #6

iampatbrown opened this issue May 30, 2022 · 0 comments
Labels
enhancement New feature or request

Comments

@iampatbrown
Copy link
Collaborator

💬 Context

XCTIssue provides limited frame information with failures and is also not available in the corelibs version. Capturing the call stack at the time of failure might be a better option to provide a more useful backtrace.

📝 Notes

  • Darwin platforms could rely on Thread.callStackSymbols plus _stdlib_demangleName from Runtime.swift.gyb
  • Linux and Windows support might need some extra work similar to swift-backtrace
  • Would be good to benchmark the implementation as well
  • Should this be configurable? If someone isn't interested in backtraces, it adds a lot of unneeded data to their uploads
@iampatbrown iampatbrown added the enhancement New feature or request label May 30, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
enhancement New feature or request
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@iampatbrown