chore: refresh pixi.lock (benchmarks/cuda_core) - #2856
Open
github-actions[bot] wants to merge 1 commit into
Open
github-actions[bot] wants to merge 1 commit into
github-actions[bot] wants to merge 1 commit into
Conversation
Scheduled pixi update --no-install for this workspace only. Signed-off-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
github-actions
Bot
added
CI/CD
Contributor
jpascucci-nv
approved these changes
Sep 14, 2026
Contributor
|
/ok to test 5d12a4b |
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.
Automated lockfile refresh for
benchmarks/cuda_coreusing pixiv0.73.0(pixi update --no-install, followed by byte-stablepixi lock --checkcanonicalization).This PR is workspace-scoped so other packages are not forced to review
unrelated solver churn. See #2298.
Important
This PR was opened with
GITHUB_TOKEN. A maintainer with write access must:assignedeventcreates the required PR has assignee, labels, and milestone check
and gives the PR a clear owner.
If the diff looks wrong, close this PR and leave the branch deleted; the
next scheduled run opens a fresh one if an update is still needed.