<deleted> - #2459
Closed
rparolin wants to merge 1 commit into
Closed
Conversation
`ci-pixi-source-test.yml` used `setup-pixi` with `run-install: false` and plain `pixi run` everywhere, so nothing pinned CI to the committed lock files. If a `pixi.toml` changes without a matching `pixi lock`, pixi's default behaviour is to silently re-solve and rewrite `pixi.lock` in place -- CI then builds and tests an environment that is *not* the one committed to the repo, goes green, and the stale lock only surfaces for the next developer. Set `PIXI_LOCKED: "true"` at the workflow level so pixi aborts with "lock file not up-to-date with the workspace" instead. Why an env var rather than `--locked` on each command: the root test and docs tasks dispatch into the sub-package manifests via nested `pixi run --manifest-path ...`. A flag on the outer command does not reach those child processes; the environment variable does. Why `--locked` and not `pixi lock --check`: `--locked` compares the lock against the manifest only and does not re-solve against the channels, so it stays green when a floating dependency gets a new upstream release. `pixi lock --check` re-solves, and would go red spontaneously whenever conda-forge publishes -- `benchmarks/cuda_core` fails it today for exactly that reason (cuda-pathfinder 1.5.6 -> 1.6.0), with no change to its manifest. Verified locally: - `PIXI_LOCKED=true pixi run -e cu13 test-pathfinder` passes today (1095 passed, 4 skipped), including the nested manifest dispatch. - With a dependency added to `cuda_pathfinder/pixi.toml` and no re-lock, the same command fails fast with "lock file not up-to-date with the workspace"; without the variable, pixi re-solves and rewrites the lock. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
|
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.
No description provided.