Repository navigation
test: update expected error message for nonexistent durable execution - #9365
Merged
Merged
Conversation
The durable execution emulator now returns 'Durable Execution does not exist' instead of 'Execution <id> not found' for missing executions.
![aws-sam-tooling-bot[bot]](https://avatars.githubusercontent.com/b/1290?s=60&v=4){kind=small}
The durable execution emulator no longer emits RetryDetails on StepSucceeded events for first-attempt successes.
reedham-aws
approved these changes
Oct 22, 2026
roger-zhangg
approved these changes
Oct 22, 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
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.
Why is this change necessary?
Nightly integration tests (run 39759452844) fail in
tier1-windows-otherandlocal-invokebecause the durable execution emulator (:latest) changed its 404 message for missing executions:Execution 00000000-0000-0000-0000-000000000000 not foundDurable Execution does not existActual stderr captured in the failing run:
How does it address the issue?
Updates the expected message in
TestLocalExecution._do_execution_nonexistent_testto the new emulator text (coversget,history,stop, andtest_tier1_execution).Notes
The
tier1-finchandlocal-start-lambdafailures in the same run are infra:public.ecr.awstimeouts (Client.Timeout exceeded,i/o timeout) while pulling the Lambda and emulator images. They should pass on rerun and are not addressed here.By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.