Test: make Error constructor more robust to broken objects #42850
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.
We sometimes make incompletely defined objects for testing, such as declaring simply
struct AnInt <: Signed; end
, but not defining the methods required by their API. If we have an error involving them, that then sometimes breaks the error reporting code, obscuring the real point of failure. This tries to be more robust against that case, so we still get information on what expression caused the failure to occur and it doesn't kill the rest of the testset.