Skip to content

Refine the Foundation error backtracing guard #813

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

Merged
merged 1 commit into from
Nov 8, 2024

Conversation

briancroom
Copy link
Contributor

Follow-on from #812:

  • Move the check slightly to ensure that it is applied in all scenarios.
  • Disable the behavior by default due to it causing problems for some tests which perform equality checks on NSError objects.

* Move the check slightly to ensure that it is applied in all scenarios.
* Disable the behavior by default due to it causing problems for some tests
  which perform equality checks on NSError objects.
@briancroom
Copy link
Contributor Author

@swift-ci please test

@briancroom briancroom merged commit 97d4c18 into main Nov 8, 2024
3 checks passed
@briancroom briancroom deleted the bcroom/adjust-foundation-error-backtracing branch November 8, 2024 20:37
@grynspan grynspan added bug 🪲 Something isn't working darwin 🍎 macOS, iOS, watchOS, tvOS, and visionOS support issue-handling Related to Issue handling within the testing library labels Dec 5, 2024
@grynspan grynspan modified the milestones: Swift 6.x, Swift 6.1 Dec 5, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug 🪲 Something isn't working darwin 🍎 macOS, iOS, watchOS, tvOS, and visionOS support issue-handling Related to Issue handling within the testing library
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants