[GH-ISSUE #2290] `cargo doc -p hickory-recursor` fails #956

New issue

Closed

opened 2026-03-16 01:05:19 +03:00 by kerem · 1 comment

kerem commented

2026-03-16 01:05:19 +03:00

Owner

Originally created by @japaric on GitHub (Jul 8, 2024).
Original GitHub issue: https://github.com/hickory-dns/hickory-dns/issues/2290

Describe the bug
what the title says

To Reproduce

$ cargo doc -p hickory-recursor
error[E0433]: failed to resolve: could not find `test` in `tokio`
   --> crates/recursor/src/recursor.rs:360:10
    |
360 | #[tokio::test]
    |          ^^^^ could not find `test` in `tokio`

For more information about this error, try `rustc --explain E0433`.
error: could not document `hickory-recursor`

Expected behavior
The command should succeed

System:

OS: Ubuntu
Architecture: x86_64
Version 22.04
rustc version: 1.79

Version:
Crate: hickory-recursor
Version: 35e2092760

Additional context
Fix incoming.

You may want to consider running something like cargo ws exec cargo doc in CI to catch issues like this in the future.

Originally created by @japaric on GitHub (Jul 8, 2024). Original GitHub issue: https://github.com/hickory-dns/hickory-dns/issues/2290 **Describe the bug** what the title says **To Reproduce** ``` console $ cargo doc -p hickory-recursor error[E0433]: failed to resolve: could not find `test` in `tokio` --> crates/recursor/src/recursor.rs:360:10 | 360 | #[tokio::test] | ^^^^ could not find `test` in `tokio` For more information about this error, try `rustc --explain E0433`. error: could not document `hickory-recursor` ``` **Expected behavior** The command should succeed **System:** - OS: Ubuntu - Architecture: x86_64 - Version 22.04 - rustc version: 1.79 **Version:** Crate: hickory-recursor Version: 35e2092760b9639a544fcb813754cab59cffe3d5 **Additional context** Fix incoming. You may want to consider running something like `cargo ws exec cargo doc` in CI to catch issues like this in the future.

kerem closed this issue

2026-03-16 01:05:24 +03:00

kerem commented

2026-03-16 01:05:30 +03:00

Author

Owner

@djc commented on GitHub (Jul 8, 2024):

You may want to consider running something like cargo ws exec cargo doc in CI to catch issues like this in the future.

Would be great to have.

@djc commented on GitHub (Jul 8, 2024): > You may want to consider running something like `cargo ws exec cargo doc` in CI to catch issues like this in the future. Would be great to have.

kerem referenced this issue

2026-03-16 02:27:15 +03:00

[PR #956] [MERGED] Bump log from 0.4.8 to 0.4.10 #1820