Skip to content

test: move two tests in serve to gpu-integ-tests#6096

Merged
lucasjia-aws merged 1 commit into
aws:masterfrom
lucasjia-aws:fix/serve
Jul 23, 2026
Merged

test: move two tests in serve to gpu-integ-tests#6096
lucasjia-aws merged 1 commit into
aws:masterfrom
lucasjia-aws:fix/serve

Conversation

@lucasjia-aws

Copy link
Copy Markdown
Collaborator

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.

@github-actions

github-actions Bot commented Jul 23, 2026

Copy link
Copy Markdown

Claude finished @lucasjia-aws's task in 28s —— View job


PR Review

  • Read PR diff
  • Verify marker is registered and usage is consistent

Summary: This PR adds the @pytest.mark.gpu_intensive marker to two integration tests (test_recommendation_workflow_end_to_end and test_jumpstart_build_deploy_invoke_cleanup) so they run on scheduled CI rather than PR checks.

The change looks clean and correct:

  • The gpu_intensive marker is properly registered in sagemaker-serve/tox.ini:66 ("mark a test as GPU resource intensive (runs on scheduled CI, not PR checks)"), so there are no unknown-marker warnings.
  • The marker is applied consistently alongside the existing @pytest.mark.slow_test decorator on both tests, matching the intent of moving GPU-heavy tests off the PR path.
  • No functional/behavioral code is touched — this is a test-selection metadata change only.

No issues found. 👍

@lucasjia-aws
lucasjia-aws merged commit 158e7e1 into aws:master Jul 23, 2026
14 of 22 checks passed
@github-actions github-actions Bot mentioned this pull request Jul 24, 2026
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