Skip to content

test(cre): run execution metadata tests under mixed-env (CI signal only) - #24245

Draft
prashantkumar1982 wants to merge 1 commit into
developfrom
test/enable-execution-metadata-mixed-env
Draft

prashantkumar1982 wants to merge 1 commit into
developfrom
test/enable-execution-metadata-mixed-env

Conversation

@prashantkumar1982

Copy link
Copy Markdown
Contributor

Draft, for CI signal only; not intended to merge as is.

Removes the two SkipIfMixedEnv calls added in #24193 (CRE-5839) so the workflow execution metadata scenario runs under mixed-env (2 PR nodes + 2 baseline nodes per DON).

Context: after upgrading one prod zone-a workflow node to 2.74.1, confidential workflows fail with enclave quorum timeout: received 1 of 7 required signatures. ExecutionMetadata is now part of the ExecuteRequest embedded in the confidential-workflows capability input, which the enclave host hashes to batch requests across nodes, so a node with the field cannot batch with nodes without it.

Note: mixed-env uses the image of the branch this PR merges into as the baseline. Against develop that baseline already contains #24193, so this PR alone is not expected to reproduce the divergence; a manual run of cre-mixed-env-tests.yaml with a pre-#24193 mixed_env_baseline_image is needed for that.

Remove the SkipIfMixedEnv calls added with CRE-5839 (#24193) so the
execution metadata scenario and Test_CRE_V2_WorkflowExecutionMetadata run
in mixed-env, to see what the 2-2 mixed topology reports.

Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
@github-actions

Copy link
Copy Markdown
Contributor

✅ No conflicts with other open PRs targeting develop

This branch was successfully deployed

1 active deployment
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.

1 participant