Closed
Description
openedon Apr 4, 2019
After a simple git clone, I tried to generate the crate documentation. I really don't know why I get this error.
The problem seems to be here but what's wrong? ^^'
// file: src/nom.rs
/// Recognizes big endian unsigned 3 byte integer
#[inline]
pub fn be_u24(i: &[u8]) -> IResult<&[u8], u32> {
if i.len() < 3 {
need_more(i, Needed::Size(3))
} else {
let res = ((i[0] as u32) << 16) + ((i[1] as u32) << 8) + (i[2] as u32);
Ok((&i[3..], res))
}
}The source is on glitch: https://glitch.com/edit/#!/nom-fork?path=nom/README.md:1:0
Meta
$ cargo doc
Updating registry `https://github.com/rust-lang/crates.io-index`
Downloading memchr v2.2.0
Downloading libc v0.2.51
Downloading version_check v0.1.5
Compiling libc v0.2.51
Compiling memchr v2.2.0
Compiling version_check v0.1.5
Documenting libc v0.2.51
Compiling nom v4.2.2 (file:///app/nom)
Documenting memchr v2.2.0
Documenting nom v4.2.2 (file:///app/nom)
thread '<unnamed>' panicked at 'failed to generate documentation: Error { file: "/app/nom/target/doc/nom/fn.be_u24.html", error: Os { code: 28, kind: Other, message: "No space left on device" } }', libcore/result.rs:945:5
note: Run with `RUST_BACKTRACE=1` for a backtrace.
error: internal compiler error: unexpected panic
note: the compiler unexpectedly panicked. this is a bug.
note: we would appreciate a bug report: https://github.com/rust-lang/rust/blob/master/CONTRIBUTING.md#bug-reports
note: rustc 1.28.0 (9634041f0 2018-07-30) running on x86_64-unknown-linux-gnu
error: Could not document `nom`.
Caused by:
process didn't exit successfully: `rustdoc --crate-name nom src/lib.rs -o /app/nom/target/doc --cfg feature="alloc" --cfg feature="default" --cfg feature="memchr" --cfg feature="std" -L dependency=/app/nom/target/debug/deps --extern memchr=/app/nom/target/debug/deps/libmemchr-b2cd595b80edfc3d.rmeta --cfg stable_i128` (exit code: 101)
Feel free to ping me if you need to ask me more!
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
