Add runner input for `unused-dep.yml`

Open
#43 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
35/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Stale
Tech stack
github-actions, rust
Domain
ci-cd

Research direction

Start by reading unused-deps.yml and tracing how its runner is selected by consuming repositories. Then inspect Neptune's workflow configuration for the gbench dependency and its default opencl feature. Done means the workflow accepts a runner input and Neptune is configured to use an appropriate GPU-equipped runner or disable the default feature; validate the resulting workflow configuration.

Written by the indexing model from the issue text.

Description

Neptune's gbench subcrate has a default opencl feature, so it needs a GPU-equipped runner unless default features are disabled. Otherwise, it will error and open an issue such as https://github.com/lurk-lab/neptune/issues/271.

We should add a runner input to unused-deps.yml and then configure Neptune accordingly.

Dominant language
No language data
Stars
0
Forks
3
Avg merge
59m
Merged PRs (30d)
2

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from argumentcomputer/ci-workflows

All issues in argumentcomputer/ci-workflows

Similar issues

More DevOps issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.