Address failing test: test_runtime_backend_errors_handled#492
Merged
sundarshankar89 merged 4 commits intomainfrom Mar 13, 2026
Merged
Address failing test: test_runtime_backend_errors_handled#492sundarshankar89 merged 4 commits intomainfrom
test_runtime_backend_errors_handled#492sundarshankar89 merged 4 commits intomainfrom
Conversation
test_runtime_backend_errors_handled
|
✅ 37/37 passed, 4 skipped, 4m27s total Running from acceptance #562 |
The prior way assumed we didn't have certain permissions, but CI/CD does have them.
Contributor
Author
These tests fail on |
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
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.
This PR addresses a failing test:
test_runtime_backend_errors_handledThis test checks error-handling, but one of the scenarios started failing under CI/CD because the test assumed it couldn't do something. Environment permissions have been updated, which means that it could and the error wasn't triggered. This PR modifies the scenario so that it will always produce an error.
Resolves #489.
Incidental changes: