Skip to content

test: fix hardcoded HyperPod cluster name in Nova integ tests#6005

Open
lucasjia-aws wants to merge 1 commit into
aws:masterfrom
lucasjia-aws:test/fix-gpu-us-east-1
Open

test: fix hardcoded HyperPod cluster name in Nova integ tests#6005
lucasjia-aws wants to merge 1 commit into
aws:masterfrom
lucasjia-aws:test/fix-gpu-us-east-1

Conversation

@lucasjia-aws

Copy link
Copy Markdown
Collaborator

The GPU integ tests in us-east-1 fail with ResourceNotFound because the CPT/SFT HyperPod tests hardcode the cluster name "riv-rig" (introduced in the Nova release), which does not exist in the test account. The actual provisioned cluster is "pysdk-hp-integ-tests".

Read the cluster name from the PYSDK_HYPERPOD_CLUSTER_NAME env var with a default of "pysdk-hp-integ-tests" so a future cluster rename no longer requires a code change. Applied to test_cpt_hyperpod.py, test_cpt_data_mixing_hyperpod.py, and test_sft_data_mixing_hyperpod.py.

Issue #, if available:

Description of changes:

By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

The GPU integ tests in us-east-1 fail with ResourceNotFound because the
CPT/SFT HyperPod tests hardcode the cluster name "riv-rig" (introduced in
the Nova release), which does not exist in the test account. The actual
provisioned cluster is "pysdk-hp-integ-tests".

Read the cluster name from the PYSDK_HYPERPOD_CLUSTER_NAME env var with a
default of "pysdk-hp-integ-tests" so a future cluster rename no longer
requires a code change. Applied to test_cpt_hyperpod.py,
test_cpt_data_mixing_hyperpod.py, and test_sft_data_mixing_hyperpod.py.
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