The module-level doc comment in matter/bridge.rs had a 4-space-indented ASCII tree diagram. Rustdoc parses any 4-space-indented block in a doc comment as a Rust code block (markdown indented-code-block syntax) and runs it as a doctest. The tree text isn't valid Rust → doctest fails. This broke the Rust Workspace Tests workflow on PR #778: test crates/.../src/matter/bridge.rs - matter::bridge (line 6) ... FAILED test result: FAILED. 0 passed; 1 failed error: doctest failed, to rerun pass `-p ... --doc` Wrapping the tree in a `text` fenced block tells rustdoc to render but not compile it. Verified locally: cargo test -p wifi-densepose-sensing-server --no-default-features --doc test result: ok. 0 passed; 0 failed; 1 ignored Refs PR #778, issue #776. Co-Authored-By: claude-flow <ruv@ruv.net> |
||
|---|---|---|
| .. | ||
| .cargo | ||
| .claude-flow | ||
| crates | ||
| data | ||
| docs | ||
| examples | ||
| patches/ruvector-crv | ||
| Cargo.lock | ||
| Cargo.toml | ||
| rust-toolchain.toml | ||