stacks-network/stacks-core

Use nextest config for fine-tuning tests

Open

#5,486 opened on Nov 20, 2024

View on GitHub
 (3 comments) (0 reactions) (0 assignees)Rust (758 forks)auto 404
choregood first issueicebox

Repository metrics

Stars
 (3,063 stars)
PR merge metrics
 (PR metrics pending)

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

Research direction
Examine the nextest documentation for per test overrides and test groups, then consider applying the 'threads required' option to specific flaky tests in the stacks core test suite.
Tech stack
rust
Domain
testing
Issue type
Chore
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
2
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-3 hours
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
Rustnextest
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
60