CI testing
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 62/100
Research direction
Start by reading the GitHub Actions workflow and the repository's test.py script to determine how built wheels can be tested. Confirm the expected wheel-testing command, then add a CI step or job that runs it against the built wheels. Done means the workflow tests the packaged wheels successfully.
Written by the indexing model from the issue text.
Description
I'd be nice to have the built wheels tested in CI as well.
If it's something simple like running the test.py script I'd be happy to provide a PR adding a test step/job to the GitHub Actions workflow, just need a confirmation about how to test it.
- Dominant language
- Python
- Stars
- 40
- Forks
- 19
- PR merge metrics
- No merged PRs in 30d
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from pyocd/libusb-package
-
Difficulty 2/5 1-3 hours Newbie friendliness 52/100
pyocd/libusb-package#9 ·
-
BSD support Open
Difficulty 4/5 3-5 days Newbie friendliness 35/100
pyocd/libusb-package#1 · 5 comments · 1 reaction ·
All issues in pyocd/libusb-package
Similar issues
-
area/auth bug comp/agent P3 platform/discord type/security
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
NousResearch/hermes-agent#117848 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
bancolombia/sentinel#23 ·
-
test md OpenCI
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
-
integration:quickjs org:external priority:backlog topic:code-interpreter topic:middleware type:feature
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
langchain-ai/deepagents#6450 ·
-
bug client
Difficulty 2/5 1-3 hours Newbie friendliness 88/100