Fix integration test#476
Merged
Merged
Conversation
…Test The `Try` wrapping obscures the exception stack when there's an unexpected exception, so you'd have to use a debugger to inspect the wrapped exception and its cause(s). This wrapping is unnecessary since we can just let the exception propagate and be caught as a test failure with the full exception stack intact.
Test Results2 297 tests 2 289 ✅ 1m 0s ⏱️ For more details on these parsing errors, see this check. Results for commit b2b1b18. |
fdennis
approved these changes
May 18, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
The integration test workflow is currently failing. This turns out to be because the
integrationTesttask configuration does not recursively create missing parent directories.