Skip to content

Integration test stabilization improvements - #7591

Draft
hgreebe wants to merge 8 commits into
aws:release-3.16from
hgreebe:release-3.16
Draft

Integration test stabilization improvements#7591
hgreebe wants to merge 8 commits into
aws:release-3.16from
hgreebe:release-3.16

Conversation

@hgreebe

@hgreebe hgreebe commented Sep 1, 2026

Copy link
Copy Markdown
Contributor

Description of changes

  • Cherry-pick test stabilization improvements from develop

Tests

  • Tested in develop, running integ tests on this branch

Please review the guidelines for contributing and Pull Request Instructions.

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

…el modules on every head node to prevent false alarms.

(cherry picked from commit 7a20fe4)
…es via COMMON_HEAD_NODE_LAZY_MODULES to avoid code duplication.

(cherry picked from commit b3bc527)
…ed by dpkg user prompts.

Such reconfiguration may occur when efs-utils get upgraded as part of the patching.

(cherry picked from commit cf4407a)
… from cluster config, which is not required for this test.

(cherry picked from commit 781dad2)
…ut by decoupling ProxyVerificationWaitCondition from the Proxy instance.

Also reduced the risk of proxy infra deployment failure by increasing the timeout of the proxy instance to not fail on slow user data.

(cherry picked from commit 1fa1447)
…all the instances required by the test and let the cluster use the specific subnet where they have been reserved.

(cherry picked from commit 9e4db01)
…d EFS in test_multiple_efs.

IAM policy evaluation can transiently delay the mount on head node reboot, causing flaky failures. Retry the mount check only for IAM-authorized EFS.

(cherry picked from commit a57a04f)
…E requeue deterministically

The TERMINATE branch snapshotted the transient CONFIGURING state via a single-shot
assert_job_state after a fixed sleep(10). When replacement nodes boot quickly the whole
node swap finishes inside the update-cluster --wait window, so the job is already RUNNING
again by the time the test samples it, causing false failures.

Assert the deterministic outcome instead: the job was requeued (wait_job_requeued) and is
running again, and the original instance it ran on was terminated
(wait_instance_replaced_or_terminating). Add SlurmCommands.get_job_instance_id to resolve
the job's instance via Slurm, and wait_job_requeued helper.

(cherry picked from commit 31f162a)
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