Bug report for `trillium-http`: Tests fail when not specifying any features
divergentdave opened this issue · comments
Describe the bug
The library-level doctest in trillium-http creates a TCP server using async-net, and connects to it using trillium_testing::ClientConfig. This works when any of the features trillium-testing/tokio, trillium-testing/smol, or trillium-testing/async-std are enabled, but fails when none of these features are enabled, because it uses the in-memory RuntimelessClientConfig, which does not touch the network. The CI runs tests with each of these features enabled, but not with default features.
To Reproduce
Steps to reproduce the behavior:
- Run
cargo test