stacks-network / stacks-network/stacks-core
Use nextest config for fine-tuning tests
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 3.1k
- Forks
- 762
- Avg merge
- 4d 6h
- Merged PRs (30d)
- 76
Description
we ran into an issue resolved by this commit: https://github.com/stacks-network/stacks-core/pull/5296/commits/82c36d7e544b384f5a7942a12b8a750660622206
what was happening was that the test in the commit above was timing out on a remote runner, but passing locally.
likely due to this issue in their docs: https://nexte.st/docs/configuration/threads-required/?h=threads
for the above test, i was able to confirm that using that threads-required flag for this specific test allowed it to pass.
i think we should be able to utilize this config to more finely-tune how we run tests locally and on remote blackboxes to reduce transient failures.
https://nexte.st/docs/configuration/per-test-overrides/
https://nexte.st/docs/configuration/test-groups/
Contributor guide
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.
Research direction
Start with the test and configuration changes shown in commit 82c36d7e544b384f5a7942a12b8a750660622206, then review the referenced nextest documentation for per-test overrides, test groups, and threads-required. Done means the affected test uses appropriate nextest configuration and no longer times out on remote runners while continuing to pass locally.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- testing
- Issue type
- Refactor
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100