Repository navigation
Conversation
Remove resolved texture-readiness and cloth-motion xfails and exercise the production GPU-transform path against the release candidate.
Route trusted fork dispatches through the dedicated runner and install the digest-pinned private RC while verifying its bytes and provenance.
1 task
Keep the supporting package job aligned with the historical OVRTX validation lane while retaining the fresh branch's manual-dispatch isolation.
Supply a create-time command so data-only images without CMD can be mounted and copied without attempting to execute their contents.
Use the 0.4.1 synchronous texture mode to improve cross-run rendering determinism while validating the release candidate.
Expose only GPU 0 during trusted fork dispatches so the known OVPhysX and OVRTX multi-GPU device-selection issue does not mask RC validation.
Select a specific device through NVIDIA_VISIBLE_DEVICES on CDI-based Horde runners while preserving the existing all-GPU path elsewhere.
Select the first concrete GPU or MIG identifier exposed by NVIDIA CDI instead of assuming an unavailable numeric alias on Horde runners.
Use the intended awk regular expression so UUID-qualified Horde GPU devices can be selected from the toolkit inventory.
Capture OVRTX motion after its additional history frame and refresh only the deterministic texture outputs produced by synchronous streaming.
Capture the documented 0.4.1 history frame for deterministic motion outputs and retain one narrowly observed full-MDL nondeterminism xfail.
Bring the validation branch onto the latest develop while preserving the fork-only workflow and current OVRTX test coverage.
github-actions
Bot
added
documentation
Advance the fork-only VTC lane to the pull-back-verified release candidate while preserving immutable digest pinning.
Remove the final release-candidate xfail and cap OVRTX pixel differences at 3 percent without changing other renderer tolerances.
nvsekkin
changed the title
Bless the visually reviewed table texture while applying the 3 percent OVRTX cap only to non-scale-sensitive AOVs.
Include the final develop updates before running the 0.4.1.364340 validation sweep.
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.
Summary
0.4.1.364340release candidate from a private, digest-pinned NGC wheelhouse.release@7f330117provenance before package and rendering tests.developinto the validation branch before testing.Artifact provenance
597e09f34819f31a71fb919c9b0024c3b652588bdfa4d1858b2222f219d0ec09sha256:9bae67cca7b01ff7c01e80a30734537012eabb1821b07e987c0ff845cb6d92bcrelease@7f330117Local validation
pip checkplus import/provenance assertions.12 passed).uv run --frozen isaaclab -f.CI validation plan
Scope notes
Important
This PR contains temporary fork-only validation infrastructure and must not be merged upstream.