Search
Items tagged with: nextest
One of the ways I disagree with many of my esteemed fellow Rust people is that I think #async #RustLang is great. Switching #nextest over to #asynchronous Rust has yielded incredible dividends, including but not limited to what I described in https://sunshowers.io/posts/nextest-and-tokio/.
The ability to write cross-platform heterogenous selects provides an extraordinary amount of power.
BTW, now that I'm at @oxidecomputer, I've been trying out nextest on #illumos and it works with zero (0) code changes!
The ability to write cross-platform heterogenous selects provides an extraordinary amount of power.
BTW, now that I'm at @oxidecomputer, I've been trying out nextest on #illumos and it works with zero (0) code changes!
How (and why) nextest uses tokio :: sunshowers
How my open source test runner uses async Rust.How (and why) nextest uses tokio
cargo-nextest 0.9.44 is out! A call for testing:
This version of my next-gen #RustLang #TestRunner supports pausing and resuming test runs on Unix (#NextestCtrlZ).
To make this work reliably, #nextest needs to use a "double-spawn" approach. This is currently off by default but can be turned on with an env var, `NEXTEST_EXPERIMENTAL_DOUBLE_SPAWN=1`.
Call for testing: If you're on Unix, please help test this! Update to 0.9.44, then set this environment variable. Thanks!
https://nexte.st/CHANGELOG.html#0944---2022-11-23
This version of my next-gen #RustLang #TestRunner supports pausing and resuming test runs on Unix (#NextestCtrlZ).
To make this work reliably, #nextest needs to use a "double-spawn" approach. This is currently off by default but can be turned on with an env var, `NEXTEST_EXPERIMENTAL_DOUBLE_SPAWN=1`.
Call for testing: If you're on Unix, please help test this! Update to 0.9.44, then set this environment variable. Thanks!
https://nexte.st/CHANGELOG.html#0944---2022-11-23
