-
Notifications
You must be signed in to change notification settings - Fork 3
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Improve gpu-ci
workflow
#18
Conversation
.github/workflows/gpu-ci.yml
Outdated
# Nextest profile specified in `.config/nextest.toml` | ||
nextest-profile: | ||
required: false | ||
default: "default" | ||
type: string | ||
# Cargo profile specified in `Cargo.toml` | ||
cargo-profile: | ||
required: false | ||
default: "release" | ||
type: string |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'm not against this in principle, but I think we've kept it uniformly to one choice across our repos. Did you notice otherwise?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We don't have either for neptune
and no cargo-profile
for grumpkin-msm
, but I agree I'd rather enforce these patterns for our repos than make them inputs. Will remove
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
For the record, I'm ok with either way of managing this. But:
This should work with
lurk-rs
,arecibo
,neptune
, andgrumpkin-msm
. The last may need some tweaks once GPU CI lands in argumentcomputer/grumpkin-msm#9 or similar.