Skip to content

ci: use latest conformance suite (git main) in conformance CI - #586

Merged
wangyb-A merged 3 commits into
mainfrom
ci-conformance-runner-git-main
Jul 27, 2026
Merged

ci: use latest conformance suite (git main) in conformance CI#586
wangyb-A merged 3 commits into
mainfrom
ci-conformance-runner-git-main

Conversation

@wangyb-A

Copy link
Copy Markdown
Contributor

Switches the conformance-tests workflow to install the runner from git main (subdirectory packages/aws-durable-execution-conformance-tests) instead of the pinned ==0.1.0 PyPI release, so new upstream suites/requirements are exercised automatically. Draft until reviewed.

Alex Wang added 2 commits July 27, 2026 21:22
Installs the conformance runner from the git main branch
(subdirectory packages/aws-durable-execution-conformance-tests)
instead of the pinned ==0.1.0 PyPI release, so new upstream
suites and requirements are exercised automatically.
Upstream requirements 1-17, 1-18, 3-11 and 3-17 now specify that
the input is logged through the step or child context logger
rather than printed to raw stdout, and the runner correlates
CloudWatch records to an execution with a JSON filter on the
executionArn field that the context logger attaches.

Replaces print() with the context logger in those four handlers
and sets the JSON log format on the step and child templates,
since Lambda's default text format drops the extra fields the
filter matches on. This also unblocks 1-7, which already used
the step context logger but emitted unstructured records.
@wangyb-A
wangyb-A force-pushed the ci-conformance-runner-git-main branch from 0d8b257 to 2d8f477 Compare July 27, 2026 21:24
Requirements 3-11 and 3-17 specify replay logging so a child body
re-execution stays observable, but the context logger suppresses
records while the context is replaying. Rebinds the replay source
with with_is_replaying so both handlers log unconditionally while
keeping the executionArn the runner correlates on.

3-11 asserts two records: the ReplayChildren re-execution emits no
history events, so the log is the only evidence it ran. 3-17 asserts
one, and needs replay logging for that count to be meaningful -- with
de-duplication an incorrect second execution is hidden.

Verified locally: the child body runs twice with is_replaying False
then True, yielding two records for 3-11 and one for 3-17.
@wangyb-A
wangyb-A marked this pull request as ready for review July 27, 2026 22:03
@wangyb-A
wangyb-A merged commit 8984294 into main Jul 27, 2026
22 of 23 checks passed
@wangyb-A
wangyb-A deleted the ci-conformance-runner-git-main branch July 27, 2026 22:11
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants