Repository navigation
Use supported micromamba run options - #15
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
1 participant
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.
Runtime evidence from native run 37233126785 confirms the cache blocker is removed and exposes exec: --: invalid option. Upstream micromamba 1.5.8 does not implement Conda --no-capture-output; its prefix-command parser treats it as the command. Remove only this unsupported runner argument; micromamba already attaches all streams by default. Preserve explicit prefix, bounded evidence capture, isolated writable cache, read-only rootfs, network none and every scientific gate. Focused 159 PASS; full 8397 PASS / 13 SKIP / 0 FAIL; Ruff/actionlint/diff PASS. No frozen factory or Dockerfile changes, no publication.