Repository navigation
Include GPU validation tests in Iris bundles - #111
Merged
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Include the materialized validation tests and fixtures explicitly in the GPU job's Iris bundle. Iris excludes directories named
testsby default, includingvalidation-source/tests, so the H100 release check reached pytest with its required source files missing. The failed mainline release stopped before the serving smoke and correctly published no wheel.A CPU round trip through the current Iris bundler reproduces the omission and verifies that the explicit glob restores all six required suite files and all 2,143 test and fixture files in a 10.9 MB ZIP. All 31 release-metadata tests and scoped lint pass. GPU qualification has not been rerun.
The required tests and publication gates remain unchanged. A manual GPU build on main is required after merge because release-workflow changes do not trigger automatic builds.