[DO NOT MERGE] test: verify Codecov after --cov=sagemaker CR deploy by jam-jee · Pull Request #6066 · aws/sagemaker-python-sdk

jam-jee · 2026-07-20T20:12:33Z

⚠️ DO NOT MERGE — verification PR

Re-verification after the CI buildspec CR (--cov=. → --cov=sagemaker) was deployed to prod. No-op comment in all 4 submodule __init__.py files so every unit-test job runs and uploads coverage.

Goal

Confirm the deployed CR produces product-only coverage (~71%, test files excluded via the merged codecov.ymlignore:) instead of the old test-inflated ~90%.

Known caveats (may still block a clean PR result)

after_n_builds: 4 is still on master (fixfix: remove codecov after_n_builds so single-submodule PRs report coverage #6056 not yet merged). Uses 4 submodules to try to satisfy the count.
CodeBuild uploader previously sent branch= empty, pr=false, and no per-submodule -F flag, which caused the earlier 4-module run ([DO NOT MERGE] test: verify Codecov across all 4 submodules #6057) to collapse to sessions=1, 3 files, 37% and post no PR status. If the deploy did not also fix the uploader, coverage may still not attach to this PR — in that case check the commit report on codecov.io directly.

Will be closed without merging once we read the result.

No-op comment in all 4 submodule __init__.py files so every unit-test job runs and uploads coverage. Purpose: confirm whether the just-deployed buildspec CR (--cov=. -> --cov=sagemaker) now produces product-only coverage (~71%, test files excluded) instead of the old test-inflated ~90%. Same-repo branch, cut from current master. Verification only.

… NOT MERGE) The prior build on this branch ran before the buildspec CR (--cov=. -> --cov=sagemaker) deployed. Empty commit to force a fresh build so coverage.xml reflects product-only code. Verification only.

github-actions · 2026-07-22T21:05:04Z

Claude finished @jam-jee's task in 51s —— View job

Review: verification PR #6066

Read the diff (4 no-op comment lines)
Check CI / Codecov status
Post review

Code review

The diff is exactly what the description claims — one identical trailing comment appended to each of the four submodule __init__.py files:

# No-op line to trigger CI for a Codecov verification (DO NOT MERGE).

Correctness: Clean. No functional change, no imports, no __all__ edits, no API surface touched. Each line is a valid Python comment at module top-level and cannot affect import behavior or coverage of product code. sagemaker-train/__init__.py places the comment after the __getattr__ body — harmless, since it's outside the function.

Best practices / tests / security / performance: N/A — nothing to test, no runtime behavior, no inputs or credentials involved. This is CI plumbing, correctly labeled DO NOT MERGE.

CI / Codecov status (as of this run)

Check	Status
CodeQL	✅ success
Fortress Security Scan	✅ success
Sagemaker PR Checks (Master)	⏳ in progress
AI Code Review	⏳ in progress (this job)

The Sagemaker PR Checks workflow — the one that runs unit tests and uploads coverage — is still running, so the Codecov result can't be read yet. Once it completes, verify the goal against the two caveats in the description:

Product-only coverage (~71%, not ~90%) — confirms the codecov.ymlignore: for test files plus --cov=sagemaker took effect.
after_n_builds: 4 + uploader flags — if the PR still shows no Codecov status or a collapsed sessions=1 report (as in [DO NOT MERGE] test: verify Codecov across all 4 submodules #6057), the deployed CR didn't fix the uploader (empty branch=, pr=false, missing per-submodule -F). In that case read the commit report directly on codecov.io rather than the PR status.

Nothing to change in the code — re-run me once the PR Checks workflow finishes and I can help read the coverage outcome.

jam-jee · 2026-07-20T20:12:33Z

⚠️ DO NOT MERGE — verification PR

Re-verification after the CI buildspec CR (--cov=. → --cov=sagemaker) was deployed to prod. No-op comment in all 4 submodule __init__.py files so every unit-test job runs and uploads coverage.

Goal

Confirm the deployed CR produces product-only coverage (~71%, test files excluded via the merged codecov.ymlignore:) instead of the old test-inflated ~90%.

Known caveats (may still block a clean PR result)

after_n_builds: 4 is still on master (fixfix: remove codecov after_n_builds so single-submodule PRs report coverage #6056 not yet merged). Uses 4 submodules to try to satisfy the count.
CodeBuild uploader previously sent branch= empty, pr=false, and no per-submodule -F flag, which caused the earlier 4-module run ([DO NOT MERGE] test: verify Codecov across all 4 submodules #6057) to collapse to sessions=1, 3 files, 37% and post no PR status. If the deploy did not also fix the uploader, coverage may still not attach to this PR — in that case check the commit report on codecov.io directly.

Will be closed without merging once we read the result.

No-op comment in all 4 submodule __init__.py files so every unit-test job runs and uploads coverage. Purpose: confirm whether the just-deployed buildspec CR (--cov=. -> --cov=sagemaker) now produces product-only coverage (~71%, test files excluded) instead of the old test-inflated ~90%. Same-repo branch, cut from current master. Verification only.

… NOT MERGE) The prior build on this branch ran before the buildspec CR (--cov=. -> --cov=sagemaker) deployed. Empty commit to force a fresh build so coverage.xml reflects product-only code. Verification only.

github-actions · 2026-07-22T21:05:04Z

Claude finished @jam-jee's task in 51s —— View job

Review: verification PR #6066

Read the diff (4 no-op comment lines)
Check CI / Codecov status
Post review

Code review

The diff is exactly what the description claims — one identical trailing comment appended to each of the four submodule __init__.py files:

# No-op line to trigger CI for a Codecov verification (DO NOT MERGE).

Correctness: Clean. No functional change, no imports, no __all__ edits, no API surface touched. Each line is a valid Python comment at module top-level and cannot affect import behavior or coverage of product code. sagemaker-train/__init__.py places the comment after the __getattr__ body — harmless, since it's outside the function.

Best practices / tests / security / performance: N/A — nothing to test, no runtime behavior, no inputs or credentials involved. This is CI plumbing, correctly labeled DO NOT MERGE.

CI / Codecov status (as of this run)

Check	Status
CodeQL	✅ success
Fortress Security Scan	✅ success
Sagemaker PR Checks (Master)	⏳ in progress
AI Code Review	⏳ in progress (this job)

The Sagemaker PR Checks workflow — the one that runs unit tests and uploads coverage — is still running, so the Codecov result can't be read yet. Once it completes, verify the goal against the two caveats in the description:

Product-only coverage (~71%, not ~90%) — confirms the codecov.ymlignore: for test files plus --cov=sagemaker took effect.
after_n_builds: 4 + uploader flags — if the PR still shows no Codecov status or a collapsed sessions=1 report (as in [DO NOT MERGE] test: verify Codecov across all 4 submodules #6057), the deployed CR didn't fix the uploader (empty branch=, pr=false, missing per-submodule -F). In that case read the commit report directly on codecov.io rather than the PR status.

Nothing to change in the code — re-run me once the PR Checks workflow finishes and I can help read the coverage outcome.

jam-jee · 2026-07-20T20:12:33Z

⚠️ DO NOT MERGE — verification PR

Re-verification after the CI buildspec CR (--cov=. → --cov=sagemaker) was deployed to prod. No-op comment in all 4 submodule __init__.py files so every unit-test job runs and uploads coverage.

Goal

Confirm the deployed CR produces product-only coverage (~71%, test files excluded via the merged codecov.ymlignore:) instead of the old test-inflated ~90%.

Known caveats (may still block a clean PR result)

after_n_builds: 4 is still on master (fixfix: remove codecov after_n_builds so single-submodule PRs report coverage #6056 not yet merged). Uses 4 submodules to try to satisfy the count.
CodeBuild uploader previously sent branch= empty, pr=false, and no per-submodule -F flag, which caused the earlier 4-module run ([DO NOT MERGE] test: verify Codecov across all 4 submodules #6057) to collapse to sessions=1, 3 files, 37% and post no PR status. If the deploy did not also fix the uploader, coverage may still not attach to this PR — in that case check the commit report on codecov.io directly.

Will be closed without merging once we read the result.

No-op comment in all 4 submodule __init__.py files so every unit-test job runs and uploads coverage. Purpose: confirm whether the just-deployed buildspec CR (--cov=. -> --cov=sagemaker) now produces product-only coverage (~71%, test files excluded) instead of the old test-inflated ~90%. Same-repo branch, cut from current master. Verification only.

… NOT MERGE) The prior build on this branch ran before the buildspec CR (--cov=. -> --cov=sagemaker) deployed. Empty commit to force a fresh build so coverage.xml reflects product-only code. Verification only.

github-actions · 2026-07-22T21:05:04Z

Claude finished @jam-jee's task in 51s —— View job

Review: verification PR #6066

Read the diff (4 no-op comment lines)
Check CI / Codecov status
Post review

Code review

The diff is exactly what the description claims — one identical trailing comment appended to each of the four submodule __init__.py files:

# No-op line to trigger CI for a Codecov verification (DO NOT MERGE).

Correctness: Clean. No functional change, no imports, no __all__ edits, no API surface touched. Each line is a valid Python comment at module top-level and cannot affect import behavior or coverage of product code. sagemaker-train/__init__.py places the comment after the __getattr__ body — harmless, since it's outside the function.

Best practices / tests / security / performance: N/A — nothing to test, no runtime behavior, no inputs or credentials involved. This is CI plumbing, correctly labeled DO NOT MERGE.

CI / Codecov status (as of this run)

Check	Status
CodeQL	✅ success
Fortress Security Scan	✅ success
Sagemaker PR Checks (Master)	⏳ in progress
AI Code Review	⏳ in progress (this job)

The Sagemaker PR Checks workflow — the one that runs unit tests and uploads coverage — is still running, so the Codecov result can't be read yet. Once it completes, verify the goal against the two caveats in the description:

Product-only coverage (~71%, not ~90%) — confirms the codecov.ymlignore: for test files plus --cov=sagemaker took effect.
after_n_builds: 4 + uploader flags — if the PR still shows no Codecov status or a collapsed sessions=1 report (as in [DO NOT MERGE] test: verify Codecov across all 4 submodules #6057), the deployed CR didn't fix the uploader (empty branch=, pr=false, missing per-submodule -F). In that case read the commit report directly on codecov.io rather than the PR status.

Nothing to change in the code — re-run me once the PR Checks workflow finishes and I can help read the coverage outcome.

jam-jee · 2026-07-20T20:12:33Z

⚠️ DO NOT MERGE — verification PR

Re-verification after the CI buildspec CR (--cov=. → --cov=sagemaker) was deployed to prod. No-op comment in all 4 submodule __init__.py files so every unit-test job runs and uploads coverage.

Goal

Confirm the deployed CR produces product-only coverage (~71%, test files excluded via the merged codecov.ymlignore:) instead of the old test-inflated ~90%.

Known caveats (may still block a clean PR result)

after_n_builds: 4 is still on master (fixfix: remove codecov after_n_builds so single-submodule PRs report coverage #6056 not yet merged). Uses 4 submodules to try to satisfy the count.
CodeBuild uploader previously sent branch= empty, pr=false, and no per-submodule -F flag, which caused the earlier 4-module run ([DO NOT MERGE] test: verify Codecov across all 4 submodules #6057) to collapse to sessions=1, 3 files, 37% and post no PR status. If the deploy did not also fix the uploader, coverage may still not attach to this PR — in that case check the commit report on codecov.io directly.

Will be closed without merging once we read the result.

No-op comment in all 4 submodule __init__.py files so every unit-test job runs and uploads coverage. Purpose: confirm whether the just-deployed buildspec CR (--cov=. -> --cov=sagemaker) now produces product-only coverage (~71%, test files excluded) instead of the old test-inflated ~90%. Same-repo branch, cut from current master. Verification only.

… NOT MERGE) The prior build on this branch ran before the buildspec CR (--cov=. -> --cov=sagemaker) deployed. Empty commit to force a fresh build so coverage.xml reflects product-only code. Verification only.

github-actions · 2026-07-22T21:05:04Z

Claude finished @jam-jee's task in 51s —— View job

Review: verification PR #6066

Read the diff (4 no-op comment lines)
Check CI / Codecov status
Post review

Code review

The diff is exactly what the description claims — one identical trailing comment appended to each of the four submodule __init__.py files:

# No-op line to trigger CI for a Codecov verification (DO NOT MERGE).

Correctness: Clean. No functional change, no imports, no __all__ edits, no API surface touched. Each line is a valid Python comment at module top-level and cannot affect import behavior or coverage of product code. sagemaker-train/__init__.py places the comment after the __getattr__ body — harmless, since it's outside the function.

Best practices / tests / security / performance: N/A — nothing to test, no runtime behavior, no inputs or credentials involved. This is CI plumbing, correctly labeled DO NOT MERGE.

CI / Codecov status (as of this run)

Check	Status
CodeQL	✅ success
Fortress Security Scan	✅ success
Sagemaker PR Checks (Master)	⏳ in progress
AI Code Review	⏳ in progress (this job)

The Sagemaker PR Checks workflow — the one that runs unit tests and uploads coverage — is still running, so the Codecov result can't be read yet. Once it completes, verify the goal against the two caveats in the description:

Product-only coverage (~71%, not ~90%) — confirms the codecov.ymlignore: for test files plus --cov=sagemaker took effect.
after_n_builds: 4 + uploader flags — if the PR still shows no Codecov status or a collapsed sessions=1 report (as in [DO NOT MERGE] test: verify Codecov across all 4 submodules #6057), the deployed CR didn't fix the uploader (empty branch=, pr=false, missing per-submodule -F). In that case read the commit report directly on codecov.io rather than the PR status.

Nothing to change in the code — re-run me once the PR Checks workflow finishes and I can help read the coverage outcome.

jam-jee · 2026-07-20T20:12:33Z

⚠️ DO NOT MERGE — verification PR

Re-verification after the CI buildspec CR (--cov=. → --cov=sagemaker) was deployed to prod. No-op comment in all 4 submodule __init__.py files so every unit-test job runs and uploads coverage.

Goal

Confirm the deployed CR produces product-only coverage (~71%, test files excluded via the merged codecov.ymlignore:) instead of the old test-inflated ~90%.

Known caveats (may still block a clean PR result)

after_n_builds: 4 is still on master (fixfix: remove codecov after_n_builds so single-submodule PRs report coverage #6056 not yet merged). Uses 4 submodules to try to satisfy the count.
CodeBuild uploader previously sent branch= empty, pr=false, and no per-submodule -F flag, which caused the earlier 4-module run ([DO NOT MERGE] test: verify Codecov across all 4 submodules #6057) to collapse to sessions=1, 3 files, 37% and post no PR status. If the deploy did not also fix the uploader, coverage may still not attach to this PR — in that case check the commit report on codecov.io directly.

Will be closed without merging once we read the result.

No-op comment in all 4 submodule __init__.py files so every unit-test job runs and uploads coverage. Purpose: confirm whether the just-deployed buildspec CR (--cov=. -> --cov=sagemaker) now produces product-only coverage (~71%, test files excluded) instead of the old test-inflated ~90%. Same-repo branch, cut from current master. Verification only.

… NOT MERGE) The prior build on this branch ran before the buildspec CR (--cov=. -> --cov=sagemaker) deployed. Empty commit to force a fresh build so coverage.xml reflects product-only code. Verification only.

github-actions · 2026-07-22T21:05:04Z

Claude finished @jam-jee's task in 51s —— View job

Review: verification PR #6066

Read the diff (4 no-op comment lines)
Check CI / Codecov status
Post review

Code review

The diff is exactly what the description claims — one identical trailing comment appended to each of the four submodule __init__.py files:

# No-op line to trigger CI for a Codecov verification (DO NOT MERGE).

Correctness: Clean. No functional change, no imports, no __all__ edits, no API surface touched. Each line is a valid Python comment at module top-level and cannot affect import behavior or coverage of product code. sagemaker-train/__init__.py places the comment after the __getattr__ body — harmless, since it's outside the function.

Best practices / tests / security / performance: N/A — nothing to test, no runtime behavior, no inputs or credentials involved. This is CI plumbing, correctly labeled DO NOT MERGE.

CI / Codecov status (as of this run)

Check	Status
CodeQL	✅ success
Fortress Security Scan	✅ success
Sagemaker PR Checks (Master)	⏳ in progress
AI Code Review	⏳ in progress (this job)

The Sagemaker PR Checks workflow — the one that runs unit tests and uploads coverage — is still running, so the Codecov result can't be read yet. Once it completes, verify the goal against the two caveats in the description:

Product-only coverage (~71%, not ~90%) — confirms the codecov.ymlignore: for test files plus --cov=sagemaker took effect.
after_n_builds: 4 + uploader flags — if the PR still shows no Codecov status or a collapsed sessions=1 report (as in [DO NOT MERGE] test: verify Codecov across all 4 submodules #6057), the deployed CR didn't fix the uploader (empty branch=, pr=false, missing per-submodule -F). In that case read the commit report directly on codecov.io rather than the PR status.

Nothing to change in the code — re-run me once the PR Checks workflow finishes and I can help read the coverage outcome.

jam-jee · 2026-07-20T20:12:33Z

⚠️ DO NOT MERGE — verification PR

Re-verification after the CI buildspec CR (--cov=. → --cov=sagemaker) was deployed to prod. No-op comment in all 4 submodule __init__.py files so every unit-test job runs and uploads coverage.

Goal

Confirm the deployed CR produces product-only coverage (~71%, test files excluded via the merged codecov.ymlignore:) instead of the old test-inflated ~90%.

Known caveats (may still block a clean PR result)

after_n_builds: 4 is still on master (fixfix: remove codecov after_n_builds so single-submodule PRs report coverage #6056 not yet merged). Uses 4 submodules to try to satisfy the count.
CodeBuild uploader previously sent branch= empty, pr=false, and no per-submodule -F flag, which caused the earlier 4-module run ([DO NOT MERGE] test: verify Codecov across all 4 submodules #6057) to collapse to sessions=1, 3 files, 37% and post no PR status. If the deploy did not also fix the uploader, coverage may still not attach to this PR — in that case check the commit report on codecov.io directly.

Will be closed without merging once we read the result.

No-op comment in all 4 submodule __init__.py files so every unit-test job runs and uploads coverage. Purpose: confirm whether the just-deployed buildspec CR (--cov=. -> --cov=sagemaker) now produces product-only coverage (~71%, test files excluded) instead of the old test-inflated ~90%. Same-repo branch, cut from current master. Verification only.

… NOT MERGE) The prior build on this branch ran before the buildspec CR (--cov=. -> --cov=sagemaker) deployed. Empty commit to force a fresh build so coverage.xml reflects product-only code. Verification only.

github-actions · 2026-07-22T21:05:04Z

Claude finished @jam-jee's task in 51s —— View job

Review: verification PR #6066

Read the diff (4 no-op comment lines)
Check CI / Codecov status
Post review

Code review

The diff is exactly what the description claims — one identical trailing comment appended to each of the four submodule __init__.py files:

# No-op line to trigger CI for a Codecov verification (DO NOT MERGE).

Correctness: Clean. No functional change, no imports, no __all__ edits, no API surface touched. Each line is a valid Python comment at module top-level and cannot affect import behavior or coverage of product code. sagemaker-train/__init__.py places the comment after the __getattr__ body — harmless, since it's outside the function.

Best practices / tests / security / performance: N/A — nothing to test, no runtime behavior, no inputs or credentials involved. This is CI plumbing, correctly labeled DO NOT MERGE.

CI / Codecov status (as of this run)

Check	Status
CodeQL	✅ success
Fortress Security Scan	✅ success
Sagemaker PR Checks (Master)	⏳ in progress
AI Code Review	⏳ in progress (this job)

The Sagemaker PR Checks workflow — the one that runs unit tests and uploads coverage — is still running, so the Codecov result can't be read yet. Once it completes, verify the goal against the two caveats in the description:

Product-only coverage (~71%, not ~90%) — confirms the codecov.ymlignore: for test files plus --cov=sagemaker took effect.
after_n_builds: 4 + uploader flags — if the PR still shows no Codecov status or a collapsed sessions=1 report (as in [DO NOT MERGE] test: verify Codecov across all 4 submodules #6057), the deployed CR didn't fix the uploader (empty branch=, pr=false, missing per-submodule -F). In that case read the commit report directly on codecov.io rather than the PR status.

Nothing to change in the code — re-run me once the PR Checks workflow finishes and I can help read the coverage outcome.

jam-jee · 2026-07-20T20:12:33Z

⚠️ DO NOT MERGE — verification PR

Re-verification after the CI buildspec CR (--cov=. → --cov=sagemaker) was deployed to prod. No-op comment in all 4 submodule __init__.py files so every unit-test job runs and uploads coverage.

Goal

Confirm the deployed CR produces product-only coverage (~71%, test files excluded via the merged codecov.ymlignore:) instead of the old test-inflated ~90%.

Known caveats (may still block a clean PR result)

after_n_builds: 4 is still on master (fixfix: remove codecov after_n_builds so single-submodule PRs report coverage #6056 not yet merged). Uses 4 submodules to try to satisfy the count.
CodeBuild uploader previously sent branch= empty, pr=false, and no per-submodule -F flag, which caused the earlier 4-module run ([DO NOT MERGE] test: verify Codecov across all 4 submodules #6057) to collapse to sessions=1, 3 files, 37% and post no PR status. If the deploy did not also fix the uploader, coverage may still not attach to this PR — in that case check the commit report on codecov.io directly.

Will be closed without merging once we read the result.

No-op comment in all 4 submodule __init__.py files so every unit-test job runs and uploads coverage. Purpose: confirm whether the just-deployed buildspec CR (--cov=. -> --cov=sagemaker) now produces product-only coverage (~71%, test files excluded) instead of the old test-inflated ~90%. Same-repo branch, cut from current master. Verification only.

… NOT MERGE) The prior build on this branch ran before the buildspec CR (--cov=. -> --cov=sagemaker) deployed. Empty commit to force a fresh build so coverage.xml reflects product-only code. Verification only.

github-actions · 2026-07-22T21:05:04Z

Claude finished @jam-jee's task in 51s —— View job

Review: verification PR #6066

Read the diff (4 no-op comment lines)
Check CI / Codecov status
Post review

Code review

The diff is exactly what the description claims — one identical trailing comment appended to each of the four submodule __init__.py files:

# No-op line to trigger CI for a Codecov verification (DO NOT MERGE).

Correctness: Clean. No functional change, no imports, no __all__ edits, no API surface touched. Each line is a valid Python comment at module top-level and cannot affect import behavior or coverage of product code. sagemaker-train/__init__.py places the comment after the __getattr__ body — harmless, since it's outside the function.

Best practices / tests / security / performance: N/A — nothing to test, no runtime behavior, no inputs or credentials involved. This is CI plumbing, correctly labeled DO NOT MERGE.

CI / Codecov status (as of this run)

Check	Status
CodeQL	✅ success
Fortress Security Scan	✅ success
Sagemaker PR Checks (Master)	⏳ in progress
AI Code Review	⏳ in progress (this job)

The Sagemaker PR Checks workflow — the one that runs unit tests and uploads coverage — is still running, so the Codecov result can't be read yet. Once it completes, verify the goal against the two caveats in the description:

Product-only coverage (~71%, not ~90%) — confirms the codecov.ymlignore: for test files plus --cov=sagemaker took effect.
after_n_builds: 4 + uploader flags — if the PR still shows no Codecov status or a collapsed sessions=1 report (as in [DO NOT MERGE] test: verify Codecov across all 4 submodules #6057), the deployed CR didn't fix the uploader (empty branch=, pr=false, missing per-submodule -F). In that case read the commit report directly on codecov.io rather than the PR status.

Nothing to change in the code — re-run me once the PR Checks workflow finishes and I can help read the coverage outcome.

jam-jee · 2026-07-20T20:12:33Z

⚠️ DO NOT MERGE — verification PR

Re-verification after the CI buildspec CR (--cov=. → --cov=sagemaker) was deployed to prod. No-op comment in all 4 submodule __init__.py files so every unit-test job runs and uploads coverage.

Goal

Confirm the deployed CR produces product-only coverage (~71%, test files excluded via the merged codecov.ymlignore:) instead of the old test-inflated ~90%.

Known caveats (may still block a clean PR result)

after_n_builds: 4 is still on master (fixfix: remove codecov after_n_builds so single-submodule PRs report coverage #6056 not yet merged). Uses 4 submodules to try to satisfy the count.
CodeBuild uploader previously sent branch= empty, pr=false, and no per-submodule -F flag, which caused the earlier 4-module run ([DO NOT MERGE] test: verify Codecov across all 4 submodules #6057) to collapse to sessions=1, 3 files, 37% and post no PR status. If the deploy did not also fix the uploader, coverage may still not attach to this PR — in that case check the commit report on codecov.io directly.

Will be closed without merging once we read the result.

No-op comment in all 4 submodule __init__.py files so every unit-test job runs and uploads coverage. Purpose: confirm whether the just-deployed buildspec CR (--cov=. -> --cov=sagemaker) now produces product-only coverage (~71%, test files excluded) instead of the old test-inflated ~90%. Same-repo branch, cut from current master. Verification only.

… NOT MERGE) The prior build on this branch ran before the buildspec CR (--cov=. -> --cov=sagemaker) deployed. Empty commit to force a fresh build so coverage.xml reflects product-only code. Verification only.

github-actions · 2026-07-22T21:05:04Z

Claude finished @jam-jee's task in 51s —— View job

Review: verification PR #6066

Read the diff (4 no-op comment lines)
Check CI / Codecov status
Post review

Code review

The diff is exactly what the description claims — one identical trailing comment appended to each of the four submodule __init__.py files:

# No-op line to trigger CI for a Codecov verification (DO NOT MERGE).

Correctness: Clean. No functional change, no imports, no __all__ edits, no API surface touched. Each line is a valid Python comment at module top-level and cannot affect import behavior or coverage of product code. sagemaker-train/__init__.py places the comment after the __getattr__ body — harmless, since it's outside the function.

Best practices / tests / security / performance: N/A — nothing to test, no runtime behavior, no inputs or credentials involved. This is CI plumbing, correctly labeled DO NOT MERGE.

CI / Codecov status (as of this run)

Check	Status
CodeQL	✅ success
Fortress Security Scan	✅ success
Sagemaker PR Checks (Master)	⏳ in progress
AI Code Review	⏳ in progress (this job)

The Sagemaker PR Checks workflow — the one that runs unit tests and uploads coverage — is still running, so the Codecov result can't be read yet. Once it completes, verify the goal against the two caveats in the description:

Product-only coverage (~71%, not ~90%) — confirms the codecov.ymlignore: for test files plus --cov=sagemaker took effect.
after_n_builds: 4 + uploader flags — if the PR still shows no Codecov status or a collapsed sessions=1 report (as in [DO NOT MERGE] test: verify Codecov across all 4 submodules #6057), the deployed CR didn't fix the uploader (empty branch=, pr=false, missing per-submodule -F). In that case read the commit report directly on codecov.io rather than the PR status.

Nothing to change in the code — re-run me once the PR Checks workflow finishes and I can help read the coverage outcome.

jam-jee temporarily deployed to auto-approve July 20, 2026 20:20 — with GitHub Actions Inactive

test: re-trigger CI to pick up deployed --cov=sagemaker buildspec (DO…
6b41b3f
… NOT MERGE) The prior build on this branch ran before the buildspec CR (--cov=. -> --cov=sagemaker) deployed. Empty commit to force a fresh build so coverage.xml reflects product-only code. Verification only.

jam-jee temporarily deployed to auto-approve July 22, 2026 20:41 — with GitHub Actions Inactive

jam-jee temporarily deployed to auto-approve July 22, 2026 20:42 — with GitHub Actions Inactive

jam-jee temporarily deployed to auto-approve July 22, 2026 21:04 — with GitHub Actions Inactive

jam-jee closed this Jul 27, 2026

jam-jee temporarily deployed to auto-approve July 20, 2026 20:20 — with GitHub Actions Inactive

test: re-trigger CI to pick up deployed --cov=sagemaker buildspec (DO…
6b41b3f
… NOT MERGE) The prior build on this branch ran before the buildspec CR (--cov=. -> --cov=sagemaker) deployed. Empty commit to force a fresh build so coverage.xml reflects product-only code. Verification only.

jam-jee temporarily deployed to auto-approve July 22, 2026 20:41 — with GitHub Actions Inactive

jam-jee temporarily deployed to auto-approve July 22, 2026 20:42 — with GitHub Actions Inactive

jam-jee temporarily deployed to auto-approve July 22, 2026 21:04 — with GitHub Actions Inactive

jam-jee closed this Jul 27, 2026

jam-jee temporarily deployed to auto-approve July 20, 2026 20:20 — with GitHub Actions Inactive

test: re-trigger CI to pick up deployed --cov=sagemaker buildspec (DO…
6b41b3f
… NOT MERGE) The prior build on this branch ran before the buildspec CR (--cov=. -> --cov=sagemaker) deployed. Empty commit to force a fresh build so coverage.xml reflects product-only code. Verification only.

jam-jee temporarily deployed to auto-approve July 22, 2026 20:41 — with GitHub Actions Inactive

jam-jee temporarily deployed to auto-approve July 22, 2026 20:42 — with GitHub Actions Inactive

jam-jee temporarily deployed to auto-approve July 22, 2026 21:04 — with GitHub Actions Inactive

jam-jee closed this Jul 27, 2026

jam-jee temporarily deployed to auto-approve July 20, 2026 20:20 — with GitHub Actions Inactive

test: re-trigger CI to pick up deployed --cov=sagemaker buildspec (DO…
6b41b3f
… NOT MERGE) The prior build on this branch ran before the buildspec CR (--cov=. -> --cov=sagemaker) deployed. Empty commit to force a fresh build so coverage.xml reflects product-only code. Verification only.

jam-jee temporarily deployed to auto-approve July 22, 2026 20:41 — with GitHub Actions Inactive

jam-jee temporarily deployed to auto-approve July 22, 2026 20:42 — with GitHub Actions Inactive

jam-jee temporarily deployed to auto-approve July 22, 2026 21:04 — with GitHub Actions Inactive

jam-jee closed this Jul 27, 2026

jam-jee temporarily deployed to auto-approve July 20, 2026 20:20 — with GitHub Actions Inactive

test: re-trigger CI to pick up deployed --cov=sagemaker buildspec (DO…
6b41b3f
… NOT MERGE) The prior build on this branch ran before the buildspec CR (--cov=. -> --cov=sagemaker) deployed. Empty commit to force a fresh build so coverage.xml reflects product-only code. Verification only.

jam-jee temporarily deployed to auto-approve July 22, 2026 20:41 — with GitHub Actions Inactive

jam-jee temporarily deployed to auto-approve July 22, 2026 20:42 — with GitHub Actions Inactive

jam-jee temporarily deployed to auto-approve July 22, 2026 21:04 — with GitHub Actions Inactive

jam-jee closed this Jul 27, 2026

jam-jee temporarily deployed to auto-approve July 20, 2026 20:20 — with GitHub Actions Inactive

test: re-trigger CI to pick up deployed --cov=sagemaker buildspec (DO…
6b41b3f
… NOT MERGE) The prior build on this branch ran before the buildspec CR (--cov=. -> --cov=sagemaker) deployed. Empty commit to force a fresh build so coverage.xml reflects product-only code. Verification only.

jam-jee temporarily deployed to auto-approve July 22, 2026 20:41 — with GitHub Actions Inactive

jam-jee temporarily deployed to auto-approve July 22, 2026 20:42 — with GitHub Actions Inactive

jam-jee temporarily deployed to auto-approve July 22, 2026 21:04 — with GitHub Actions Inactive

jam-jee closed this Jul 27, 2026

jam-jee temporarily deployed to auto-approve July 20, 2026 20:20 — with GitHub Actions Inactive

test: re-trigger CI to pick up deployed --cov=sagemaker buildspec (DO…
6b41b3f
… NOT MERGE) The prior build on this branch ran before the buildspec CR (--cov=. -> --cov=sagemaker) deployed. Empty commit to force a fresh build so coverage.xml reflects product-only code. Verification only.

jam-jee temporarily deployed to auto-approve July 22, 2026 20:41 — with GitHub Actions Inactive

jam-jee temporarily deployed to auto-approve July 22, 2026 20:42 — with GitHub Actions Inactive

jam-jee temporarily deployed to auto-approve July 22, 2026 21:04 — with GitHub Actions Inactive

jam-jee closed this Jul 27, 2026

jam-jee temporarily deployed to auto-approve July 20, 2026 20:20 — with GitHub Actions Inactive

test: re-trigger CI to pick up deployed --cov=sagemaker buildspec (DO…
6b41b3f
… NOT MERGE) The prior build on this branch ran before the buildspec CR (--cov=. -> --cov=sagemaker) deployed. Empty commit to force a fresh build so coverage.xml reflects product-only code. Verification only.

jam-jee temporarily deployed to auto-approve July 22, 2026 20:41 — with GitHub Actions Inactive

jam-jee temporarily deployed to auto-approve July 22, 2026 20:42 — with GitHub Actions Inactive

jam-jee temporarily deployed to auto-approve July 22, 2026 21:04 — with GitHub Actions Inactive

jam-jee closed this Jul 27, 2026

Uh oh!

Conversation

jam-jee commented Jul 20, 2026

⚠️ DO NOT MERGE — verification PR

Goal

Known caveats (may still block a clean PR result)

Uh oh!

github-actionsBot commented Jul 22, 2026• edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Review: verification PR #6066

Code review

CI / Codecov status (as of this run)

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

1 participant

Uh oh!

Conversation

jam-jee commented Jul 20, 2026

⚠️ DO NOT MERGE — verification PR

Goal

Known caveats (may still block a clean PR result)

Uh oh!

github-actionsBot commented Jul 22, 2026• edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Review: verification PR #6066

Code review

CI / Codecov status (as of this run)

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

1 participant

Uh oh!

Conversation

jam-jee commented Jul 20, 2026

⚠️ DO NOT MERGE — verification PR

Goal

Known caveats (may still block a clean PR result)

Uh oh!

github-actionsBot commented Jul 22, 2026• edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Review: verification PR #6066

Code review

CI / Codecov status (as of this run)

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

1 participant

Uh oh!

Conversation

jam-jee commented Jul 20, 2026

⚠️ DO NOT MERGE — verification PR

Goal

Known caveats (may still block a clean PR result)

Uh oh!

github-actionsBot commented Jul 22, 2026• edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Review: verification PR #6066

Code review

CI / Codecov status (as of this run)

Uh oh!

Reviewers

Assignees

Labels

Projects

github-actionsBot commented Jul 22, 2026•
edited
Loading

github-actionsBot commented Jul 22, 2026•
edited
Loading

github-actionsBot commented Jul 22, 2026•
edited
Loading

github-actionsBot commented Jul 22, 2026•
edited
Loading

github-actionsBot commented Jul 22, 2026•
edited
Loading

github-actionsBot commented Jul 22, 2026•
edited
Loading