-
-
Notifications
You must be signed in to change notification settings - Fork 111
Open
Description
Nextest 0.9.100 appears to be hanging in some configurations:
- On the Arch Linux build server, as documented in the discussion
- In one illumos CI run so far.
Discussed in #2458
Originally posted by orhun July 11, 2025
Hey!
I'm maintaining cargo-nextest
for Arch Linux and we are currently running tests like this after building the package:
build() {
cd "$pkgname-$pkgver"
cargo build --release --frozen --package "$pkgname" --no-default-features --features default-no-update
}
check() {
cd "$pkgname-$pkgver"
cargo run --package cargo-nextest -- nextest run -- --skip test_version_info
}
I adopted this from the GitHub workflows from this repository a while ago.
However, with the last release (0.9.100
), running the tests take a long time and get stuck after a while, maybe due to the new global timeout feature?
More specifically, after this point:
SLOW [>1620.000s] nextest-runner::integration basic::test_retries::retry_overrides_ignored
SLOW [>1620.000s] nextest-runner::integration basic::test_retries::retry_overrides_obeyed
SLOW [>1620.000s] nextest-runner::integration basic::test_run
SLOW [>1620.000s] nextest-runner::integration basic::test_run_ignored
SLOW [>1620.000s] nextest-runner::integration basic::test_string_filters_without_filter_expr
SLOW [>1620.000s] nextest-runner::integration basic::test_termination
SLOW [>1620.000s] nextest-runner::integration target_runner::test_listing_with_target_runner
SLOW [>1620.000s] nextest-runner::integration target_runner::test_run_with_target_runn
So I have a couple of questions:
- What do you suggest we do as packagers to avoid long-running tests like this? Is there a filter command or something similar to skip these?
- Is my way of running tests correct & can it be improved?
Thank you :)
Metadata
Metadata
Assignees
Labels
No labels