[INFO] fetching crate eat-nom 0.1.5...
[INFO] checking eat-nom-0.1.5 against master#c2f2db79ca3024f68d22b45aa22b570775c2c4ad for pr-124157
[INFO] extracting crate eat-nom 0.1.5 into /workspace/builds/worker-2-tc1/source
[INFO] validating manifest of crates.io crate eat-nom 0.1.5 on toolchain c2f2db79ca3024f68d22b45aa22b570775c2c4ad
[INFO] running `Command { std: CARGO_HOME="/workspace/cargo-home" RUSTUP_HOME="/workspace/rustup-home" "/workspace/cargo-home/bin/cargo" "+c2f2db79ca3024f68d22b45aa22b570775c2c4ad" "metadata" "--manifest-path" "Cargo.toml" "--no-deps", kill_on_drop: false }`
[INFO] started tweaking crates.io crate eat-nom 0.1.5
[INFO] finished tweaking crates.io crate eat-nom 0.1.5
[INFO] tweaked toml for crates.io crate eat-nom 0.1.5 written to /workspace/builds/worker-2-tc1/source/Cargo.toml
[INFO] running `Command { std: CARGO_HOME="/workspace/cargo-home" RUSTUP_HOME="/workspace/rustup-home" "/workspace/cargo-home/bin/cargo" "+c2f2db79ca3024f68d22b45aa22b570775c2c4ad" "generate-lockfile" "--manifest-path" "Cargo.toml", kill_on_drop: false }`
[INFO] [stderr]     Updating crates.io index
[INFO] [stderr]      Locking 15 packages to latest compatible versions
[INFO] [stderr]       Adding arrayvec v0.5.2 (latest: v0.7.4)
[INFO] [stderr]       Adding bitflags v1.3.2 (latest: v2.5.0)
[INFO] [stderr]       Adding bitvec v0.19.6 (latest: v1.0.1)
[INFO] [stderr]       Adding funty v1.1.0 (latest: v2.0.0)
[INFO] [stderr]       Adding lexical-core v0.7.6 (latest: v0.8.5)
[INFO] [stderr]       Adding memchr v2.3.4 (latest: v2.7.2)
[INFO] [stderr]       Adding nom v6.2.2 (latest: v7.1.3)
[INFO] [stderr]       Adding radium v0.5.3 (latest: v1.1.0)
[INFO] [stderr]       Adding wyz v0.2.0 (latest: v0.6.1)
[INFO] running `Command { std: CARGO_HOME="/workspace/cargo-home" RUSTUP_HOME="/workspace/rustup-home" "/workspace/cargo-home/bin/cargo" "+c2f2db79ca3024f68d22b45aa22b570775c2c4ad" "fetch" "--manifest-path" "Cargo.toml", kill_on_drop: false }`
[INFO] running `Command { std: "docker" "create" "-v" "/var/lib/crater-agent-workspace/builds/worker-2-tc1/target:/opt/rustwide/target:rw,Z" "-v" "/var/lib/crater-agent-workspace/builds/worker-2-tc1/source:/opt/rustwide/workdir:ro,Z" "-v" "/var/lib/crater-agent-workspace/cargo-home:/opt/rustwide/cargo-home:ro,Z" "-v" "/var/lib/crater-agent-workspace/rustup-home:/opt/rustwide/rustup-home:ro,Z" "-e" "SOURCE_DIR=/opt/rustwide/workdir" "-e" "CARGO_TARGET_DIR=/opt/rustwide/target" "-e" "CARGO_HOME=/opt/rustwide/cargo-home" "-e" "RUSTUP_HOME=/opt/rustwide/rustup-home" "-w" "/opt/rustwide/workdir" "-m" "1610612736" "--user" "0:0" "--network" "none" "ghcr.io/rust-lang/crates-build-env/linux@sha256:99613afd962a8cfa530ec1899472a458bd015a1ab0af876cf7eb06f6006d81ea" "/opt/rustwide/cargo-home/bin/cargo" "+c2f2db79ca3024f68d22b45aa22b570775c2c4ad" "metadata" "--no-deps" "--format-version=1", kill_on_drop: false }`
[INFO] [stdout] 077fbc69a79f6e93dffa200fff7f5197c06942b5de2fc381876e9bc8a94c0b5a
[INFO] running `Command { std: "docker" "start" "-a" "077fbc69a79f6e93dffa200fff7f5197c06942b5de2fc381876e9bc8a94c0b5a", kill_on_drop: false }`
[INFO] running `Command { std: "docker" "inspect" "077fbc69a79f6e93dffa200fff7f5197c06942b5de2fc381876e9bc8a94c0b5a", kill_on_drop: false }`
[INFO] running `Command { std: "docker" "rm" "-f" "077fbc69a79f6e93dffa200fff7f5197c06942b5de2fc381876e9bc8a94c0b5a", kill_on_drop: false }`
[INFO] [stdout] 077fbc69a79f6e93dffa200fff7f5197c06942b5de2fc381876e9bc8a94c0b5a
[INFO] running `Command { std: "docker" "create" "-v" "/var/lib/crater-agent-workspace/builds/worker-2-tc1/target:/opt/rustwide/target:rw,Z" "-v" "/var/lib/crater-agent-workspace/builds/worker-2-tc1/source:/opt/rustwide/workdir:ro,Z" "-v" "/var/lib/crater-agent-workspace/cargo-home:/opt/rustwide/cargo-home:ro,Z" "-v" "/var/lib/crater-agent-workspace/rustup-home:/opt/rustwide/rustup-home:ro,Z" "-e" "SOURCE_DIR=/opt/rustwide/workdir" "-e" "CARGO_TARGET_DIR=/opt/rustwide/target" "-e" "CARGO_INCREMENTAL=0" "-e" "RUST_BACKTRACE=full" "-e" "RUSTFLAGS=--cap-lints=forbid" "-e" "RUSTDOCFLAGS=--cap-lints=forbid" "-e" "CARGO_HOME=/opt/rustwide/cargo-home" "-e" "RUSTUP_HOME=/opt/rustwide/rustup-home" "-w" "/opt/rustwide/workdir" "-m" "1610612736" "--user" "0:0" "--network" "none" "ghcr.io/rust-lang/crates-build-env/linux@sha256:99613afd962a8cfa530ec1899472a458bd015a1ab0af876cf7eb06f6006d81ea" "/opt/rustwide/cargo-home/bin/cargo" "+c2f2db79ca3024f68d22b45aa22b570775c2c4ad" "check" "--frozen" "--all" "--all-targets" "--message-format=json", kill_on_drop: false }`
[INFO] [stdout] 66f954ae8714606e678098fd2edadd9143faf6f2079666ba37b90028178451fe
[INFO] running `Command { std: "docker" "start" "-a" "66f954ae8714606e678098fd2edadd9143faf6f2079666ba37b90028178451fe", kill_on_drop: false }`
[INFO] [stderr]    Compiling radium v0.5.3
[INFO] [stderr]    Compiling memchr v2.3.4
[INFO] [stderr]    Compiling lexical-core v0.7.6
[INFO] [stderr]     Checking funty v1.1.0
[INFO] [stderr]     Checking wyz v0.2.0
[INFO] [stderr]     Checking arrayvec v0.5.2
[INFO] [stderr]     Checking tap v1.0.1
[INFO] [stderr]    Compiling nom v6.2.2
[INFO] [stderr]     Checking bitvec v0.19.6
[INFO] [stderr]     Checking eat-nom v0.1.5 (/opt/rustwide/workdir)
[INFO] [stdout] error[E0277]: `?` couldn't convert the error to `error::ErrorKind`
[INFO] [stdout]   --> src/ip.rs:26:29
[INFO] [stdout]    |
[INFO] [stdout] 25 | pub fn parse_ip(input: &str) -> EatResult<IpAddr> {
[INFO] [stdout]    |                                 ----------------- expected `error::ErrorKind` because of this
[INFO] [stdout] 26 |     let (_, out) = ip(input)?;
[INFO] [stdout]    |                    ---------^ the trait `From<nom::Err<nom::error::Error<&str>>>` is not implemented for `error::ErrorKind`, which is required by `Result<IpAddr, error::ErrorKind>: FromResidual<Result<Infallible, nom::Err<nom::error::Error<&str>>>>`
[INFO] [stdout]    |                    |
[INFO] [stdout]    |                    this can't be annotated with `?` because it has type `Result<_, nom::Err<nom::error::Error<&str>>>`
[INFO] [stdout]    |
[INFO] [stdout]    = note: the question mark operation (`?`) implicitly performs a conversion on the error value using the `From` trait
[INFO] [stdout]    = help: the following other types implement trait `From<T>`:
[INFO] [stdout]              <error::ErrorKind as From<AddrParseError>>
[INFO] [stdout]              <error::ErrorKind as From<ParseIntError>>
[INFO] [stdout]              <error::ErrorKind as From<nom::Err<(&str, nom::error::ErrorKind)>>>
[INFO] [stdout]    = note: required for `Result<IpAddr, error::ErrorKind>` to implement `FromResidual<Result<Infallible, nom::Err<nom::error::Error<&str>>>>`
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error[E0277]: `?` couldn't convert the error to `error::ErrorKind`
[INFO] [stdout]   --> src/ip.rs:45:67
[INFO] [stdout]    |
[INFO] [stdout] 44 | pub fn parse_ip_mask<'a>(input: &'a str, concat: &'a str) -> EatResult<(IpAddr, IpAddr)> {
[INFO] [stdout]    |                                                              --------------------------- expected `error::ErrorKind` because of this
[INFO] [stdout] 45 |     let (_, (ip, _, mask)) = tuple((ip, tag(concat), mask))(input)?;
[INFO] [stdout]    |                              -------------------------------------^ the trait `From<nom::Err<nom::error::Error<&str>>>` is not implemented for `error::ErrorKind`, which is required by `Result<(IpAddr, IpAddr), error::ErrorKind>: FromResidual<Result<Infallible, nom::Err<nom::error::Error<&str>>>>`
[INFO] [stdout]    |                              |
[INFO] [stdout]    |                              this can't be annotated with `?` because it has type `Result<_, nom::Err<nom::error::Error<&str>>>`
[INFO] [stdout]    |
[INFO] [stdout]    = note: the question mark operation (`?`) implicitly performs a conversion on the error value using the `From` trait
[INFO] [stdout]    = help: the following other types implement trait `From<T>`:
[INFO] [stdout]              <error::ErrorKind as From<AddrParseError>>
[INFO] [stdout]              <error::ErrorKind as From<ParseIntError>>
[INFO] [stdout]              <error::ErrorKind as From<nom::Err<(&str, nom::error::ErrorKind)>>>
[INFO] [stdout]    = note: required for `Result<(IpAddr, IpAddr), error::ErrorKind>` to implement `FromResidual<Result<Infallible, nom::Err<nom::error::Error<&str>>>>`
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error[E0277]: `?` couldn't convert the error to `error::ErrorKind`
[INFO] [stdout]   --> src/error.rs:85:50
[INFO] [stdout]    |
[INFO] [stdout] 80 |     fn test_until_eof_ok() -> EatResult<()> {
[INFO] [stdout]    |                               ------------- expected `error::ErrorKind` because of this
[INFO] [stdout] ...
[INFO] [stdout] 85 |         let (x, y) = until_eof("hello, worldeof")?;
[INFO] [stdout]    |                      ----------------------------^ the trait `From<nom::Err<nom::error::Error<&str>>>` is not implemented for `error::ErrorKind`, which is required by `Result<(), error::ErrorKind>: FromResidual<Result<Infallible, nom::Err<nom::error::Error<&str>>>>`
[INFO] [stdout]    |                      |
[INFO] [stdout]    |                      this can't be annotated with `?` because it has type `Result<_, nom::Err<nom::error::Error<&str>>>`
[INFO] [stdout]    |
[INFO] [stdout]    = note: the question mark operation (`?`) implicitly performs a conversion on the error value using the `From` trait
[INFO] [stdout]    = help: the following other types implement trait `From<T>`:
[INFO] [stdout]              <error::ErrorKind as From<AddrParseError>>
[INFO] [stdout]              <error::ErrorKind as From<ParseIntError>>
[INFO] [stdout]              <error::ErrorKind as From<nom::Err<(&str, nom::error::ErrorKind)>>>
[INFO] [stdout]    = note: required for `Result<(), error::ErrorKind>` to implement `FromResidual<Result<Infallible, nom::Err<nom::error::Error<&str>>>>`
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error[E0277]: `?` couldn't convert the error to `error::ErrorKind`
[INFO] [stdout]   --> src/ip.rs:53:81
[INFO] [stdout]    |
[INFO] [stdout] 51 | pub fn parse_ip_mask_opt(input: &str) -> EatResult<(IpAddr, IpAddr)> {
[INFO] [stdout]    |                                          --------------------------- expected `error::ErrorKind` because of this
[INFO] [stdout] 52 |     let (_, (ip, _, mask)) =
[INFO] [stdout] 53 |         tuple((ip, alt((tag("/"), tag("-"), tag(" "), tag("\\"))), mask))(input)?;
[INFO] [stdout]    |         ------------------------------------------------------------------------^ the trait `From<nom::Err<nom::error::Error<&str>>>` is not implemented for `error::ErrorKind`, which is required by `Result<(IpAddr, IpAddr), error::ErrorKind>: FromResidual<Result<Infallible, nom::Err<nom::error::Error<&str>>>>`
[INFO] [stdout]    |         |
[INFO] [stdout]    |         this can't be annotated with `?` because it has type `Result<_, nom::Err<nom::error::Error<&str>>>`
[INFO] [stdout]    |
[INFO] [stdout]    = note: the question mark operation (`?`) implicitly performs a conversion on the error value using the `From` trait
[INFO] [stdout]    = help: the following other types implement trait `From<T>`:
[INFO] [stdout]              <error::ErrorKind as From<AddrParseError>>
[INFO] [stdout]              <error::ErrorKind as From<ParseIntError>>
[INFO] [stdout]              <error::ErrorKind as From<nom::Err<(&str, nom::error::ErrorKind)>>>
[INFO] [stdout]    = note: required for `Result<(IpAddr, IpAddr), error::ErrorKind>` to implement `FromResidual<Result<Infallible, nom::Err<nom::error::Error<&str>>>>`
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error[E0277]: `?` couldn't convert the error to `error::ErrorKind`
[INFO] [stdout]   --> src/ip.rs:60:67
[INFO] [stdout]    |
[INFO] [stdout] 59 | pub fn parse_ip_range<'a>(input: &'a str, concat: &'a str) -> EatResult<Range<IpAddr>> {
[INFO] [stdout]    |                                                               ------------------------ expected `error::ErrorKind` because of this
[INFO] [stdout] 60 |     let (_, (start, _, end)) = tuple((ip, tag(concat), ip))(input)?;
[INFO] [stdout]    |                                -----------------------------------^ the trait `From<nom::Err<nom::error::Error<&str>>>` is not implemented for `error::ErrorKind`, which is required by `Result<std::ops::Range<IpAddr>, error::ErrorKind>: FromResidual<Result<Infallible, nom::Err<nom::error::Error<&str>>>>`
[INFO] [stdout]    |                                |
[INFO] [stdout]    |                                this can't be annotated with `?` because it has type `Result<_, nom::Err<nom::error::Error<&str>>>`
[INFO] [stdout]    |
[INFO] [stdout]    = note: the question mark operation (`?`) implicitly performs a conversion on the error value using the `From` trait
[INFO] [stdout]    = help: the following other types implement trait `From<T>`:
[INFO] [stdout]              <error::ErrorKind as From<AddrParseError>>
[INFO] [stdout]              <error::ErrorKind as From<ParseIntError>>
[INFO] [stdout]              <error::ErrorKind as From<nom::Err<(&str, nom::error::ErrorKind)>>>
[INFO] [stdout]    = note: required for `Result<std::ops::Range<IpAddr>, error::ErrorKind>` to implement `FromResidual<Result<Infallible, nom::Err<nom::error::Error<&str>>>>`
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error[E0277]: `?` couldn't convert the error to `error::ErrorKind`
[INFO] [stdout]   --> src/ip.rs:26:29
[INFO] [stdout]    |
[INFO] [stdout] 25 | pub fn parse_ip(input: &str) -> EatResult<IpAddr> {
[INFO] [stdout]    |                                 ----------------- expected `error::ErrorKind` because of this
[INFO] [stdout] 26 |     let (_, out) = ip(input)?;
[INFO] [stdout]    |                    ---------^ the trait `From<nom::Err<nom::error::Error<&str>>>` is not implemented for `error::ErrorKind`, which is required by `Result<IpAddr, error::ErrorKind>: FromResidual<Result<Infallible, nom::Err<nom::error::Error<&str>>>>`
[INFO] [stdout]    |                    |
[INFO] [stdout]    |                    this can't be annotated with `?` because it has type `Result<_, nom::Err<nom::error::Error<&str>>>`
[INFO] [stdout]    |
[INFO] [stdout]    = note: the question mark operation (`?`) implicitly performs a conversion on the error value using the `From` trait
[INFO] [stdout]    = help: the following other types implement trait `From<T>`:
[INFO] [stdout]              <error::ErrorKind as From<AddrParseError>>
[INFO] [stdout]              <error::ErrorKind as From<ParseIntError>>
[INFO] [stdout]              <error::ErrorKind as From<nom::Err<(&str, nom::error::ErrorKind)>>>
[INFO] [stdout]    = note: required for `Result<IpAddr, error::ErrorKind>` to implement `FromResidual<Result<Infallible, nom::Err<nom::error::Error<&str>>>>`
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error[E0277]: `?` couldn't convert the error to `error::ErrorKind`
[INFO] [stdout]   --> src/ip.rs:68:79
[INFO] [stdout]    |
[INFO] [stdout] 66 | pub fn parse_ip_range_opt(input: &str) -> EatResult<Range<IpAddr>> {
[INFO] [stdout]    |                                           ------------------------ expected `error::ErrorKind` because of this
[INFO] [stdout] 67 |     let (_, (start, _, end)) =
[INFO] [stdout] 68 |         tuple((ip, alt((tag("/"), tag("-"), tag(" "), tag("\\"))), ip))(input)?;
[INFO] [stdout]    |         ----------------------------------------------------------------------^ the trait `From<nom::Err<nom::error::Error<&str>>>` is not implemented for `error::ErrorKind`, which is required by `Result<std::ops::Range<IpAddr>, error::ErrorKind>: FromResidual<Result<Infallible, nom::Err<nom::error::Error<&str>>>>`
[INFO] [stdout]    |         |
[INFO] [stdout]    |         this can't be annotated with `?` because it has type `Result<_, nom::Err<nom::error::Error<&str>>>`
[INFO] [stdout]    |
[INFO] [stdout]    = note: the question mark operation (`?`) implicitly performs a conversion on the error value using the `From` trait
[INFO] [stdout]    = help: the following other types implement trait `From<T>`:
[INFO] [stdout]              <error::ErrorKind as From<AddrParseError>>
[INFO] [stdout]              <error::ErrorKind as From<ParseIntError>>
[INFO] [stdout]              <error::ErrorKind as From<nom::Err<(&str, nom::error::ErrorKind)>>>
[INFO] [stdout]    = note: required for `Result<std::ops::Range<IpAddr>, error::ErrorKind>` to implement `FromResidual<Result<Infallible, nom::Err<nom::error::Error<&str>>>>`
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error[E0277]: `?` couldn't convert the error to `error::ErrorKind`
[INFO] [stdout]   --> src/ip.rs:45:67
[INFO] [stdout]    |
[INFO] [stdout] 44 | pub fn parse_ip_mask<'a>(input: &'a str, concat: &'a str) -> EatResult<(IpAddr, IpAddr)> {
[INFO] [stdout]    |                                                              --------------------------- expected `error::ErrorKind` because of this
[INFO] [stdout] 45 |     let (_, (ip, _, mask)) = tuple((ip, tag(concat), mask))(input)?;
[INFO] [stdout]    |                              -------------------------------------^ the trait `From<nom::Err<nom::error::Error<&str>>>` is not implemented for `error::ErrorKind`, which is required by `Result<(IpAddr, IpAddr), error::ErrorKind>: FromResidual<Result<Infallible, nom::Err<nom::error::Error<&str>>>>`
[INFO] [stdout]    |                              |
[INFO] [stdout]    |                              this can't be annotated with `?` because it has type `Result<_, nom::Err<nom::error::Error<&str>>>`
[INFO] [stdout]    |
[INFO] [stdout]    = note: the question mark operation (`?`) implicitly performs a conversion on the error value using the `From` trait
[INFO] [stdout]    = help: the following other types implement trait `From<T>`:
[INFO] [stdout]              <error::ErrorKind as From<AddrParseError>>
[INFO] [stdout]              <error::ErrorKind as From<ParseIntError>>
[INFO] [stdout]              <error::ErrorKind as From<nom::Err<(&str, nom::error::ErrorKind)>>>
[INFO] [stdout]    = note: required for `Result<(IpAddr, IpAddr), error::ErrorKind>` to implement `FromResidual<Result<Infallible, nom::Err<nom::error::Error<&str>>>>`
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error[E0277]: `?` couldn't convert the error to `error::ErrorKind`
[INFO] [stdout]   --> src/ip.rs:75:69
[INFO] [stdout]    |
[INFO] [stdout] 74 | pub fn parse_ip_cidr<'a>(input: &'a str, concat: &'a str) -> EatResult<(IpAddr, usize)> {
[INFO] [stdout]    |                                                              -------------------------- expected `error::ErrorKind` because of this
[INFO] [stdout] 75 |     let (_, (ip, _, cidr)) = tuple((ip, tag(concat), digit1))(input)?;
[INFO] [stdout]    |                              ---------------------------------------^ the trait `From<nom::Err<nom::error::Error<&str>>>` is not implemented for `error::ErrorKind`, which is required by `Result<(IpAddr, usize), error::ErrorKind>: FromResidual<Result<Infallible, nom::Err<nom::error::Error<&str>>>>`
[INFO] [stdout]    |                              |
[INFO] [stdout]    |                              this can't be annotated with `?` because it has type `Result<_, nom::Err<nom::error::Error<&str>>>`
[INFO] [stdout]    |
[INFO] [stdout]    = note: the question mark operation (`?`) implicitly performs a conversion on the error value using the `From` trait
[INFO] [stdout]    = help: the following other types implement trait `From<T>`:
[INFO] [stdout]              <error::ErrorKind as From<AddrParseError>>
[INFO] [stdout]              <error::ErrorKind as From<ParseIntError>>
[INFO] [stdout]              <error::ErrorKind as From<nom::Err<(&str, nom::error::ErrorKind)>>>
[INFO] [stdout]    = note: required for `Result<(IpAddr, usize), error::ErrorKind>` to implement `FromResidual<Result<Infallible, nom::Err<nom::error::Error<&str>>>>`
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error[E0277]: `?` couldn't convert the error to `error::ErrorKind`
[INFO] [stdout]   --> src/ip.rs:53:81
[INFO] [stdout]    |
[INFO] [stdout] 51 | pub fn parse_ip_mask_opt(input: &str) -> EatResult<(IpAddr, IpAddr)> {
[INFO] [stdout]    |                                          --------------------------- expected `error::ErrorKind` because of this
[INFO] [stdout] 52 |     let (_, (ip, _, mask)) =
[INFO] [stdout] 53 |         tuple((ip, alt((tag("/"), tag("-"), tag(" "), tag("\\"))), mask))(input)?;
[INFO] [stdout]    |         ------------------------------------------------------------------------^ the trait `From<nom::Err<nom::error::Error<&str>>>` is not implemented for `error::ErrorKind`, which is required by `Result<(IpAddr, IpAddr), error::ErrorKind>: FromResidual<Result<Infallible, nom::Err<nom::error::Error<&str>>>>`
[INFO] [stdout]    |         |
[INFO] [stdout]    |         this can't be annotated with `?` because it has type `Result<_, nom::Err<nom::error::Error<&str>>>`
[INFO] [stdout]    |
[INFO] [stdout]    = note: the question mark operation (`?`) implicitly performs a conversion on the error value using the `From` trait
[INFO] [stdout]    = help: the following other types implement trait `From<T>`:
[INFO] [stdout]              <error::ErrorKind as From<AddrParseError>>
[INFO] [stdout]              <error::ErrorKind as From<ParseIntError>>
[INFO] [stdout]              <error::ErrorKind as From<nom::Err<(&str, nom::error::ErrorKind)>>>
[INFO] [stdout]    = note: required for `Result<(IpAddr, IpAddr), error::ErrorKind>` to implement `FromResidual<Result<Infallible, nom::Err<nom::error::Error<&str>>>>`
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error[E0277]: `?` couldn't convert the error to `error::ErrorKind`
[INFO] [stdout]   --> src/ip.rs:83:83
[INFO] [stdout]    |
[INFO] [stdout] 81 | pub fn parse_ip_cidr_opt(input: &str) -> EatResult<(IpAddr, usize)> {
[INFO] [stdout]    |                                          -------------------------- expected `error::ErrorKind` because of this
[INFO] [stdout] 82 |     let (_, (ip, _, cidr)) =
[INFO] [stdout] 83 |         tuple((ip, alt((tag("/"), tag("-"), tag(" "), tag("\\"))), digit1))(input)?;
[INFO] [stdout]    |         --------------------------------------------------------------------------^ the trait `From<nom::Err<nom::error::Error<&str>>>` is not implemented for `error::ErrorKind`, which is required by `Result<(IpAddr, usize), error::ErrorKind>: FromResidual<Result<Infallible, nom::Err<nom::error::Error<&str>>>>`
[INFO] [stdout]    |         |
[INFO] [stdout]    |         this can't be annotated with `?` because it has type `Result<_, nom::Err<nom::error::Error<&str>>>`
[INFO] [stdout]    |
[INFO] [stdout]    = note: the question mark operation (`?`) implicitly performs a conversion on the error value using the `From` trait
[INFO] [stdout]    = help: the following other types implement trait `From<T>`:
[INFO] [stdout]              <error::ErrorKind as From<AddrParseError>>
[INFO] [stdout]              <error::ErrorKind as From<ParseIntError>>
[INFO] [stdout]              <error::ErrorKind as From<nom::Err<(&str, nom::error::ErrorKind)>>>
[INFO] [stdout]    = note: required for `Result<(IpAddr, usize), error::ErrorKind>` to implement `FromResidual<Result<Infallible, nom::Err<nom::error::Error<&str>>>>`
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error[E0277]: `?` couldn't convert the error to `error::ErrorKind`
[INFO] [stdout]   --> src/ip.rs:60:67
[INFO] [stdout]    |
[INFO] [stdout] 59 | pub fn parse_ip_range<'a>(input: &'a str, concat: &'a str) -> EatResult<Range<IpAddr>> {
[INFO] [stdout]    |                                                               ------------------------ expected `error::ErrorKind` because of this
[INFO] [stdout] 60 |     let (_, (start, _, end)) = tuple((ip, tag(concat), ip))(input)?;
[INFO] [stdout]    |                                -----------------------------------^ the trait `From<nom::Err<nom::error::Error<&str>>>` is not implemented for `error::ErrorKind`, which is required by `Result<std::ops::Range<IpAddr>, error::ErrorKind>: FromResidual<Result<Infallible, nom::Err<nom::error::Error<&str>>>>`
[INFO] [stdout]    |                                |
[INFO] [stdout]    |                                this can't be annotated with `?` because it has type `Result<_, nom::Err<nom::error::Error<&str>>>`
[INFO] [stdout]    |
[INFO] [stdout]    = note: the question mark operation (`?`) implicitly performs a conversion on the error value using the `From` trait
[INFO] [stdout]    = help: the following other types implement trait `From<T>`:
[INFO] [stdout]              <error::ErrorKind as From<AddrParseError>>
[INFO] [stdout]              <error::ErrorKind as From<ParseIntError>>
[INFO] [stdout]              <error::ErrorKind as From<nom::Err<(&str, nom::error::ErrorKind)>>>
[INFO] [stdout]    = note: required for `Result<std::ops::Range<IpAddr>, error::ErrorKind>` to implement `FromResidual<Result<Infallible, nom::Err<nom::error::Error<&str>>>>`
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error[E0277]: `?` couldn't convert the error to `error::ErrorKind`
[INFO] [stdout]   --> src/ip.rs:68:79
[INFO] [stdout]    |
[INFO] [stdout] 66 | pub fn parse_ip_range_opt(input: &str) -> EatResult<Range<IpAddr>> {
[INFO] [stdout]    |                                           ------------------------ expected `error::ErrorKind` because of this
[INFO] [stdout] 67 |     let (_, (start, _, end)) =
[INFO] [stdout] 68 |         tuple((ip, alt((tag("/"), tag("-"), tag(" "), tag("\\"))), ip))(input)?;
[INFO] [stdout]    |         ----------------------------------------------------------------------^ the trait `From<nom::Err<nom::error::Error<&str>>>` is not implemented for `error::ErrorKind`, which is required by `Result<std::ops::Range<IpAddr>, error::ErrorKind>: FromResidual<Result<Infallible, nom::Err<nom::error::Error<&str>>>>`
[INFO] [stdout]    |         |
[INFO] [stdout]    |         this can't be annotated with `?` because it has type `Result<_, nom::Err<nom::error::Error<&str>>>`
[INFO] [stdout]    |
[INFO] [stdout]    = note: the question mark operation (`?`) implicitly performs a conversion on the error value using the `From` trait
[INFO] [stdout]    = help: the following other types implement trait `From<T>`:
[INFO] [stdout]              <error::ErrorKind as From<AddrParseError>>
[INFO] [stdout]              <error::ErrorKind as From<ParseIntError>>
[INFO] [stdout]              <error::ErrorKind as From<nom::Err<(&str, nom::error::ErrorKind)>>>
[INFO] [stdout]    = note: required for `Result<std::ops::Range<IpAddr>, error::ErrorKind>` to implement `FromResidual<Result<Infallible, nom::Err<nom::error::Error<&str>>>>`
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error[E0277]: `?` couldn't convert the error to `error::ErrorKind`
[INFO] [stdout]   --> src/ip.rs:75:69
[INFO] [stdout]    |
[INFO] [stdout] 74 | pub fn parse_ip_cidr<'a>(input: &'a str, concat: &'a str) -> EatResult<(IpAddr, usize)> {
[INFO] [stdout]    |                                                              -------------------------- expected `error::ErrorKind` because of this
[INFO] [stdout] 75 |     let (_, (ip, _, cidr)) = tuple((ip, tag(concat), digit1))(input)?;
[INFO] [stdout]    |                              ---------------------------------------^ the trait `From<nom::Err<nom::error::Error<&str>>>` is not implemented for `error::ErrorKind`, which is required by `Result<(IpAddr, usize), error::ErrorKind>: FromResidual<Result<Infallible, nom::Err<nom::error::Error<&str>>>>`
[INFO] [stdout]    |                              |
[INFO] [stdout]    |                              this can't be annotated with `?` because it has type `Result<_, nom::Err<nom::error::Error<&str>>>`
[INFO] [stdout]    |
[INFO] [stdout]    = note: the question mark operation (`?`) implicitly performs a conversion on the error value using the `From` trait
[INFO] [stdout]    = help: the following other types implement trait `From<T>`:
[INFO] [stdout]              <error::ErrorKind as From<AddrParseError>>
[INFO] [stdout]              <error::ErrorKind as From<ParseIntError>>
[INFO] [stdout]              <error::ErrorKind as From<nom::Err<(&str, nom::error::ErrorKind)>>>
[INFO] [stdout]    = note: required for `Result<(IpAddr, usize), error::ErrorKind>` to implement `FromResidual<Result<Infallible, nom::Err<nom::error::Error<&str>>>>`
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error[E0277]: `?` couldn't convert the error to `error::ErrorKind`
[INFO] [stdout]   --> src/ip.rs:83:83
[INFO] [stdout]    |
[INFO] [stdout] 81 | pub fn parse_ip_cidr_opt(input: &str) -> EatResult<(IpAddr, usize)> {
[INFO] [stdout]    |                                          -------------------------- expected `error::ErrorKind` because of this
[INFO] [stdout] 82 |     let (_, (ip, _, cidr)) =
[INFO] [stdout] 83 |         tuple((ip, alt((tag("/"), tag("-"), tag(" "), tag("\\"))), digit1))(input)?;
[INFO] [stdout]    |         --------------------------------------------------------------------------^ the trait `From<nom::Err<nom::error::Error<&str>>>` is not implemented for `error::ErrorKind`, which is required by `Result<(IpAddr, usize), error::ErrorKind>: FromResidual<Result<Infallible, nom::Err<nom::error::Error<&str>>>>`
[INFO] [stdout]    |         |
[INFO] [stdout]    |         this can't be annotated with `?` because it has type `Result<_, nom::Err<nom::error::Error<&str>>>`
[INFO] [stdout]    |
[INFO] [stdout]    = note: the question mark operation (`?`) implicitly performs a conversion on the error value using the `From` trait
[INFO] [stdout]    = help: the following other types implement trait `From<T>`:
[INFO] [stdout]              <error::ErrorKind as From<AddrParseError>>
[INFO] [stdout]              <error::ErrorKind as From<ParseIntError>>
[INFO] [stdout]              <error::ErrorKind as From<nom::Err<(&str, nom::error::ErrorKind)>>>
[INFO] [stdout]    = note: required for `Result<(IpAddr, usize), error::ErrorKind>` to implement `FromResidual<Result<Infallible, nom::Err<nom::error::Error<&str>>>>`
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error: aborting due to 7 previous errors
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] For more information about this error, try `rustc --explain E0277`.
[INFO] [stdout] 
[INFO] [stderr] error: could not compile `eat-nom` (lib) due to 8 previous errors
[INFO] [stderr] warning: build failed, waiting for other jobs to finish...
[INFO] [stdout] error: aborting due to 8 previous errors
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] For more information about this error, try `rustc --explain E0277`.
[INFO] [stdout] 
[INFO] [stderr] error: could not compile `eat-nom` (lib test) due to 9 previous errors
[INFO] running `Command { std: "docker" "inspect" "66f954ae8714606e678098fd2edadd9143faf6f2079666ba37b90028178451fe", kill_on_drop: false }`
[INFO] running `Command { std: "docker" "rm" "-f" "66f954ae8714606e678098fd2edadd9143faf6f2079666ba37b90028178451fe", kill_on_drop: false }`
[INFO] [stdout] 66f954ae8714606e678098fd2edadd9143faf6f2079666ba37b90028178451fe
[INFO] checking eat-nom-0.1.5 against try#9c7b5f5b6b8ec32bbbcf9f07fc0e5208da6c5f88 for pr-124157
[INFO] extracting crate eat-nom 0.1.5 into /workspace/builds/worker-2-tc2/source
[INFO] validating manifest of crates.io crate eat-nom 0.1.5 on toolchain 9c7b5f5b6b8ec32bbbcf9f07fc0e5208da6c5f88
[INFO] running `Command { std: CARGO_HOME="/workspace/cargo-home" RUSTUP_HOME="/workspace/rustup-home" "/workspace/cargo-home/bin/cargo" "+9c7b5f5b6b8ec32bbbcf9f07fc0e5208da6c5f88" "metadata" "--manifest-path" "Cargo.toml" "--no-deps", kill_on_drop: false }`
[INFO] started tweaking crates.io crate eat-nom 0.1.5
[INFO] finished tweaking crates.io crate eat-nom 0.1.5
[INFO] tweaked toml for crates.io crate eat-nom 0.1.5 written to /workspace/builds/worker-2-tc2/source/Cargo.toml
[INFO] running `Command { std: CARGO_HOME="/workspace/cargo-home" RUSTUP_HOME="/workspace/rustup-home" "/workspace/cargo-home/bin/cargo" "+9c7b5f5b6b8ec32bbbcf9f07fc0e5208da6c5f88" "generate-lockfile" "--manifest-path" "Cargo.toml", kill_on_drop: false }`
[INFO] [stderr]     Blocking waiting for file lock on package cache
[INFO] [stderr]     Updating crates.io index
[INFO] [stderr]     Blocking waiting for file lock on package cache
[INFO] [stderr]      Locking 15 packages to latest compatible versions
[INFO] [stderr]       Adding arrayvec v0.5.2 (latest: v0.7.4)
[INFO] [stderr]       Adding bitflags v1.3.2 (latest: v2.5.0)
[INFO] [stderr]       Adding bitvec v0.19.6 (latest: v1.0.1)
[INFO] [stderr]       Adding funty v1.1.0 (latest: v2.0.0)
[INFO] [stderr]       Adding lexical-core v0.7.6 (latest: v0.8.5)
[INFO] [stderr]       Adding memchr v2.3.4 (latest: v2.7.2)
[INFO] [stderr]       Adding nom v6.2.2 (latest: v7.1.3)
[INFO] [stderr]       Adding radium v0.5.3 (latest: v1.1.0)
[INFO] [stderr]       Adding wyz v0.2.0 (latest: v0.6.1)
[INFO] running `Command { std: CARGO_HOME="/workspace/cargo-home" RUSTUP_HOME="/workspace/rustup-home" "/workspace/cargo-home/bin/cargo" "+9c7b5f5b6b8ec32bbbcf9f07fc0e5208da6c5f88" "fetch" "--manifest-path" "Cargo.toml", kill_on_drop: false }`
[INFO] running `Command { std: "docker" "create" "-v" "/var/lib/crater-agent-workspace/builds/worker-2-tc2/target:/opt/rustwide/target:rw,Z" "-v" "/var/lib/crater-agent-workspace/builds/worker-2-tc2/source:/opt/rustwide/workdir:ro,Z" "-v" "/var/lib/crater-agent-workspace/cargo-home:/opt/rustwide/cargo-home:ro,Z" "-v" "/var/lib/crater-agent-workspace/rustup-home:/opt/rustwide/rustup-home:ro,Z" "-e" "SOURCE_DIR=/opt/rustwide/workdir" "-e" "CARGO_TARGET_DIR=/opt/rustwide/target" "-e" "CARGO_HOME=/opt/rustwide/cargo-home" "-e" "RUSTUP_HOME=/opt/rustwide/rustup-home" "-w" "/opt/rustwide/workdir" "-m" "1610612736" "--user" "0:0" "--network" "none" "ghcr.io/rust-lang/crates-build-env/linux@sha256:99613afd962a8cfa530ec1899472a458bd015a1ab0af876cf7eb06f6006d81ea" "/opt/rustwide/cargo-home/bin/cargo" "+9c7b5f5b6b8ec32bbbcf9f07fc0e5208da6c5f88" "metadata" "--no-deps" "--format-version=1", kill_on_drop: false }`
[INFO] [stdout] 0e0dfd21f44581e64f67f0992964164d291cf522cf986fd100848c01a1c13eff
[INFO] running `Command { std: "docker" "start" "-a" "0e0dfd21f44581e64f67f0992964164d291cf522cf986fd100848c01a1c13eff", kill_on_drop: false }`
[INFO] running `Command { std: "docker" "inspect" "0e0dfd21f44581e64f67f0992964164d291cf522cf986fd100848c01a1c13eff", kill_on_drop: false }`
[INFO] running `Command { std: "docker" "rm" "-f" "0e0dfd21f44581e64f67f0992964164d291cf522cf986fd100848c01a1c13eff", kill_on_drop: false }`
[INFO] [stdout] 0e0dfd21f44581e64f67f0992964164d291cf522cf986fd100848c01a1c13eff
[INFO] running `Command { std: "docker" "create" "-v" "/var/lib/crater-agent-workspace/builds/worker-2-tc2/target:/opt/rustwide/target:rw,Z" "-v" "/var/lib/crater-agent-workspace/builds/worker-2-tc2/source:/opt/rustwide/workdir:ro,Z" "-v" "/var/lib/crater-agent-workspace/cargo-home:/opt/rustwide/cargo-home:ro,Z" "-v" "/var/lib/crater-agent-workspace/rustup-home:/opt/rustwide/rustup-home:ro,Z" "-e" "SOURCE_DIR=/opt/rustwide/workdir" "-e" "CARGO_TARGET_DIR=/opt/rustwide/target" "-e" "CARGO_INCREMENTAL=0" "-e" "RUST_BACKTRACE=full" "-e" "RUSTFLAGS=--cap-lints=forbid" "-e" "RUSTDOCFLAGS=--cap-lints=forbid" "-e" "CARGO_HOME=/opt/rustwide/cargo-home" "-e" "RUSTUP_HOME=/opt/rustwide/rustup-home" "-w" "/opt/rustwide/workdir" "-m" "1610612736" "--user" "0:0" "--network" "none" "ghcr.io/rust-lang/crates-build-env/linux@sha256:99613afd962a8cfa530ec1899472a458bd015a1ab0af876cf7eb06f6006d81ea" "/opt/rustwide/cargo-home/bin/cargo" "+9c7b5f5b6b8ec32bbbcf9f07fc0e5208da6c5f88" "check" "--frozen" "--all" "--all-targets" "--message-format=json", kill_on_drop: false }`
[INFO] [stdout] c92f9caf7e43d67e8f1bcde800b408ffde576bacd23de1214890d847f138b336
[INFO] running `Command { std: "docker" "start" "-a" "c92f9caf7e43d67e8f1bcde800b408ffde576bacd23de1214890d847f138b336", kill_on_drop: false }`
[INFO] [stderr]    Compiling radium v0.5.3
[INFO] [stderr]    Compiling lexical-core v0.7.6
[INFO] [stderr]    Compiling memchr v2.3.4
[INFO] [stderr]     Checking wyz v0.2.0
[INFO] [stderr]     Checking tap v1.0.1
[INFO] [stderr]     Checking arrayvec v0.5.2
[INFO] [stderr]     Checking funty v1.1.0
[INFO] [stderr]    Compiling nom v6.2.2
[INFO] [stderr]     Checking bitvec v0.19.6
[INFO] [stderr]     Checking eat-nom v0.1.5 (/opt/rustwide/workdir)
[INFO] [stdout] error[E0277]: `?` couldn't convert the error to `error::ErrorKind`
[INFO] [stdout]   --> src/ip.rs:26:29
[INFO] [stdout]    |
[INFO] [stdout] 25 | pub fn parse_ip(input: &str) -> EatResult<IpAddr> {
[INFO] [stdout]    |                                 ----------------- expected `error::ErrorKind` because of this
[INFO] [stdout] 26 |     let (_, out) = ip(input)?;
[INFO] [stdout]    |                    ---------^ the trait `From<nom::Err<nom::error::Error<&str>>>` is not implemented for `error::ErrorKind`, which is required by `Result<IpAddr, error::ErrorKind>: FromResidual<Result<Infallible, nom::Err<nom::error::Error<&str>>>>`
[INFO] [stdout]    |                    |
[INFO] [stdout]    |                    this can't be annotated with `?` because it has type `Result<_, nom::Err<nom::error::Error<&str>>>`
[INFO] [stdout]    |
[INFO] [stdout]    = note: the question mark operation (`?`) implicitly performs a conversion on the error value using the `From` trait
[INFO] [stdout]    = help: the following other types implement trait `From<T>`:
[INFO] [stdout]              <error::ErrorKind as From<AddrParseError>>
[INFO] [stdout]              <error::ErrorKind as From<ParseIntError>>
[INFO] [stdout]              <error::ErrorKind as From<nom::Err<(&str, nom::error::ErrorKind)>>>
[INFO] [stdout]    = note: required for `Result<IpAddr, error::ErrorKind>` to implement `FromResidual<Result<Infallible, nom::Err<nom::error::Error<&str>>>>`
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error[E0277]: `?` couldn't convert the error to `error::ErrorKind`
[INFO] [stdout]   --> src/ip.rs:45:67
[INFO] [stdout]    |
[INFO] [stdout] 44 | pub fn parse_ip_mask<'a>(input: &'a str, concat: &'a str) -> EatResult<(IpAddr, IpAddr)> {
[INFO] [stdout]    |                                                              --------------------------- expected `error::ErrorKind` because of this
[INFO] [stdout] 45 |     let (_, (ip, _, mask)) = tuple((ip, tag(concat), mask))(input)?;
[INFO] [stdout]    |                              -------------------------------------^ the trait `From<nom::Err<nom::error::Error<&str>>>` is not implemented for `error::ErrorKind`, which is required by `Result<(IpAddr, IpAddr), error::ErrorKind>: FromResidual<Result<Infallible, nom::Err<nom::error::Error<&str>>>>`
[INFO] [stdout]    |                              |
[INFO] [stdout]    |                              this can't be annotated with `?` because it has type `Result<_, nom::Err<nom::error::Error<&str>>>`
[INFO] [stdout]    |
[INFO] [stdout]    = note: the question mark operation (`?`) implicitly performs a conversion on the error value using the `From` trait
[INFO] [stdout]    = help: the following other types implement trait `From<T>`:
[INFO] [stdout]              <error::ErrorKind as From<AddrParseError>>
[INFO] [stdout]              <error::ErrorKind as From<ParseIntError>>
[INFO] [stdout]              <error::ErrorKind as From<nom::Err<(&str, nom::error::ErrorKind)>>>
[INFO] [stdout]    = note: required for `Result<(IpAddr, IpAddr), error::ErrorKind>` to implement `FromResidual<Result<Infallible, nom::Err<nom::error::Error<&str>>>>`
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error[E0277]: `?` couldn't convert the error to `error::ErrorKind`
[INFO] [stdout]   --> src/ip.rs:53:81
[INFO] [stdout]    |
[INFO] [stdout] 51 | pub fn parse_ip_mask_opt(input: &str) -> EatResult<(IpAddr, IpAddr)> {
[INFO] [stdout]    |                                          --------------------------- expected `error::ErrorKind` because of this
[INFO] [stdout] 52 |     let (_, (ip, _, mask)) =
[INFO] [stdout] 53 |         tuple((ip, alt((tag("/"), tag("-"), tag(" "), tag("\\"))), mask))(input)?;
[INFO] [stdout]    |         ------------------------------------------------------------------------^ the trait `From<nom::Err<nom::error::Error<&str>>>` is not implemented for `error::ErrorKind`, which is required by `Result<(IpAddr, IpAddr), error::ErrorKind>: FromResidual<Result<Infallible, nom::Err<nom::error::Error<&str>>>>`
[INFO] [stdout]    |         |
[INFO] [stdout]    |         this can't be annotated with `?` because it has type `Result<_, nom::Err<nom::error::Error<&str>>>`
[INFO] [stdout]    |
[INFO] [stdout]    = note: the question mark operation (`?`) implicitly performs a conversion on the error value using the `From` trait
[INFO] [stdout]    = help: the following other types implement trait `From<T>`:
[INFO] [stdout]              <error::ErrorKind as From<AddrParseError>>
[INFO] [stdout]              <error::ErrorKind as From<ParseIntError>>
[INFO] [stdout]              <error::ErrorKind as From<nom::Err<(&str, nom::error::ErrorKind)>>>
[INFO] [stdout]    = note: required for `Result<(IpAddr, IpAddr), error::ErrorKind>` to implement `FromResidual<Result<Infallible, nom::Err<nom::error::Error<&str>>>>`
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error[E0277]: `?` couldn't convert the error to `error::ErrorKind`
[INFO] [stdout]   --> src/ip.rs:60:67
[INFO] [stdout]    |
[INFO] [stdout] 59 | pub fn parse_ip_range<'a>(input: &'a str, concat: &'a str) -> EatResult<Range<IpAddr>> {
[INFO] [stdout]    |                                                               ------------------------ expected `error::ErrorKind` because of this
[INFO] [stdout] 60 |     let (_, (start, _, end)) = tuple((ip, tag(concat), ip))(input)?;
[INFO] [stdout]    |                                -----------------------------------^ the trait `From<nom::Err<nom::error::Error<&str>>>` is not implemented for `error::ErrorKind`, which is required by `Result<std::ops::Range<IpAddr>, error::ErrorKind>: FromResidual<Result<Infallible, nom::Err<nom::error::Error<&str>>>>`
[INFO] [stdout]    |                                |
[INFO] [stdout]    |                                this can't be annotated with `?` because it has type `Result<_, nom::Err<nom::error::Error<&str>>>`
[INFO] [stdout]    |
[INFO] [stdout]    = note: the question mark operation (`?`) implicitly performs a conversion on the error value using the `From` trait
[INFO] [stdout]    = help: the following other types implement trait `From<T>`:
[INFO] [stdout]              <error::ErrorKind as From<AddrParseError>>
[INFO] [stdout]              <error::ErrorKind as From<ParseIntError>>
[INFO] [stdout]              <error::ErrorKind as From<nom::Err<(&str, nom::error::ErrorKind)>>>
[INFO] [stdout]    = note: required for `Result<std::ops::Range<IpAddr>, error::ErrorKind>` to implement `FromResidual<Result<Infallible, nom::Err<nom::error::Error<&str>>>>`
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error[E0277]: `?` couldn't convert the error to `error::ErrorKind`
[INFO] [stdout]   --> src/error.rs:85:50
[INFO] [stdout]    |
[INFO] [stdout] 80 |     fn test_until_eof_ok() -> EatResult<()> {
[INFO] [stdout]    |                               ------------- expected `error::ErrorKind` because of this
[INFO] [stdout] ...
[INFO] [stdout] 85 |         let (x, y) = until_eof("hello, worldeof")?;
[INFO] [stdout]    |                      ----------------------------^ the trait `From<nom::Err<nom::error::Error<&str>>>` is not implemented for `error::ErrorKind`, which is required by `Result<(), error::ErrorKind>: FromResidual<Result<Infallible, nom::Err<nom::error::Error<&str>>>>`
[INFO] [stdout]    |                      |
[INFO] [stdout]    |                      this can't be annotated with `?` because it has type `Result<_, nom::Err<nom::error::Error<&str>>>`
[INFO] [stdout]    |
[INFO] [stdout]    = note: the question mark operation (`?`) implicitly performs a conversion on the error value using the `From` trait
[INFO] [stdout]    = help: the following other types implement trait `From<T>`:
[INFO] [stdout]              <error::ErrorKind as From<AddrParseError>>
[INFO] [stdout]              <error::ErrorKind as From<ParseIntError>>
[INFO] [stdout]              <error::ErrorKind as From<nom::Err<(&str, nom::error::ErrorKind)>>>
[INFO] [stdout]    = note: required for `Result<(), error::ErrorKind>` to implement `FromResidual<Result<Infallible, nom::Err<nom::error::Error<&str>>>>`
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error[E0277]: `?` couldn't convert the error to `error::ErrorKind`
[INFO] [stdout]   --> src/ip.rs:68:79
[INFO] [stdout]    |
[INFO] [stdout] 66 | pub fn parse_ip_range_opt(input: &str) -> EatResult<Range<IpAddr>> {
[INFO] [stdout]    |                                           ------------------------ expected `error::ErrorKind` because of this
[INFO] [stdout] 67 |     let (_, (start, _, end)) =
[INFO] [stdout] 68 |         tuple((ip, alt((tag("/"), tag("-"), tag(" "), tag("\\"))), ip))(input)?;
[INFO] [stdout]    |         ----------------------------------------------------------------------^ the trait `From<nom::Err<nom::error::Error<&str>>>` is not implemented for `error::ErrorKind`, which is required by `Result<std::ops::Range<IpAddr>, error::ErrorKind>: FromResidual<Result<Infallible, nom::Err<nom::error::Error<&str>>>>`
[INFO] [stdout]    |         |
[INFO] [stdout]    |         this can't be annotated with `?` because it has type `Result<_, nom::Err<nom::error::Error<&str>>>`
[INFO] [stdout]    |
[INFO] [stdout]    = note: the question mark operation (`?`) implicitly performs a conversion on the error value using the `From` trait
[INFO] [stdout]    = help: the following other types implement trait `From<T>`:
[INFO] [stdout]              <error::ErrorKind as From<AddrParseError>>
[INFO] [stdout]              <error::ErrorKind as From<ParseIntError>>
[INFO] [stdout]              <error::ErrorKind as From<nom::Err<(&str, nom::error::ErrorKind)>>>
[INFO] [stdout]    = note: required for `Result<std::ops::Range<IpAddr>, error::ErrorKind>` to implement `FromResidual<Result<Infallible, nom::Err<nom::error::Error<&str>>>>`
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error[E0277]: `?` couldn't convert the error to `error::ErrorKind`
[INFO] [stdout]   --> src/ip.rs:75:69
[INFO] [stdout]    |
[INFO] [stdout] 74 | pub fn parse_ip_cidr<'a>(input: &'a str, concat: &'a str) -> EatResult<(IpAddr, usize)> {
[INFO] [stdout]    |                                                              -------------------------- expected `error::ErrorKind` because of this
[INFO] [stdout] 75 |     let (_, (ip, _, cidr)) = tuple((ip, tag(concat), digit1))(input)?;
[INFO] [stdout]    |                              ---------------------------------------^ the trait `From<nom::Err<nom::error::Error<&str>>>` is not implemented for `error::ErrorKind`, which is required by `Result<(IpAddr, usize), error::ErrorKind>: FromResidual<Result<Infallible, nom::Err<nom::error::Error<&str>>>>`
[INFO] [stdout]    |                              |
[INFO] [stdout]    |                              this can't be annotated with `?` because it has type `Result<_, nom::Err<nom::error::Error<&str>>>`
[INFO] [stdout]    |
[INFO] [stdout]    = note: the question mark operation (`?`) implicitly performs a conversion on the error value using the `From` trait
[INFO] [stdout]    = help: the following other types implement trait `From<T>`:
[INFO] [stdout]              <error::ErrorKind as From<AddrParseError>>
[INFO] [stdout]              <error::ErrorKind as From<ParseIntError>>
[INFO] [stdout]              <error::ErrorKind as From<nom::Err<(&str, nom::error::ErrorKind)>>>
[INFO] [stdout]    = note: required for `Result<(IpAddr, usize), error::ErrorKind>` to implement `FromResidual<Result<Infallible, nom::Err<nom::error::Error<&str>>>>`
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error[E0277]: `?` couldn't convert the error to `error::ErrorKind`
[INFO] [stdout]   --> src/ip.rs:26:29
[INFO] [stdout]    |
[INFO] [stdout] 25 | pub fn parse_ip(input: &str) -> EatResult<IpAddr> {
[INFO] [stdout]    |                                 ----------------- expected `error::ErrorKind` because of this
[INFO] [stdout] 26 |     let (_, out) = ip(input)?;
[INFO] [stdout]    |                    ---------^ the trait `From<nom::Err<nom::error::Error<&str>>>` is not implemented for `error::ErrorKind`, which is required by `Result<IpAddr, error::ErrorKind>: FromResidual<Result<Infallible, nom::Err<nom::error::Error<&str>>>>`
[INFO] [stdout]    |                    |
[INFO] [stdout]    |                    this can't be annotated with `?` because it has type `Result<_, nom::Err<nom::error::Error<&str>>>`
[INFO] [stdout]    |
[INFO] [stdout]    = note: the question mark operation (`?`) implicitly performs a conversion on the error value using the `From` trait
[INFO] [stdout]    = help: the following other types implement trait `From<T>`:
[INFO] [stdout]              <error::ErrorKind as From<AddrParseError>>
[INFO] [stdout]              <error::ErrorKind as From<ParseIntError>>
[INFO] [stdout]              <error::ErrorKind as From<nom::Err<(&str, nom::error::ErrorKind)>>>
[INFO] [stdout]    = note: required for `Result<IpAddr, error::ErrorKind>` to implement `FromResidual<Result<Infallible, nom::Err<nom::error::Error<&str>>>>`
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error[E0277]: `?` couldn't convert the error to `error::ErrorKind`
[INFO] [stdout]   --> src/ip.rs:83:83
[INFO] [stdout]    |
[INFO] [stdout] 81 | pub fn parse_ip_cidr_opt(input: &str) -> EatResult<(IpAddr, usize)> {
[INFO] [stdout]    |                                          -------------------------- expected `error::ErrorKind` because of this
[INFO] [stdout] 82 |     let (_, (ip, _, cidr)) =
[INFO] [stdout] 83 |         tuple((ip, alt((tag("/"), tag("-"), tag(" "), tag("\\"))), digit1))(input)?;
[INFO] [stdout]    |         --------------------------------------------------------------------------^ the trait `From<nom::Err<nom::error::Error<&str>>>` is not implemented for `error::ErrorKind`, which is required by `Result<(IpAddr, usize), error::ErrorKind>: FromResidual<Result<Infallible, nom::Err<nom::error::Error<&str>>>>`
[INFO] [stdout]    |         |
[INFO] [stdout]    |         this can't be annotated with `?` because it has type `Result<_, nom::Err<nom::error::Error<&str>>>`
[INFO] [stdout]    |
[INFO] [stdout]    = note: the question mark operation (`?`) implicitly performs a conversion on the error value using the `From` trait
[INFO] [stdout]    = help: the following other types implement trait `From<T>`:
[INFO] [stdout]              <error::ErrorKind as From<AddrParseError>>
[INFO] [stdout]              <error::ErrorKind as From<ParseIntError>>
[INFO] [stdout]              <error::ErrorKind as From<nom::Err<(&str, nom::error::ErrorKind)>>>
[INFO] [stdout]    = note: required for `Result<(IpAddr, usize), error::ErrorKind>` to implement `FromResidual<Result<Infallible, nom::Err<nom::error::Error<&str>>>>`
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error[E0277]: `?` couldn't convert the error to `error::ErrorKind`
[INFO] [stdout]   --> src/ip.rs:45:67
[INFO] [stdout]    |
[INFO] [stdout] 44 | pub fn parse_ip_mask<'a>(input: &'a str, concat: &'a str) -> EatResult<(IpAddr, IpAddr)> {
[INFO] [stdout]    |                                                              --------------------------- expected `error::ErrorKind` because of this
[INFO] [stdout] 45 |     let (_, (ip, _, mask)) = tuple((ip, tag(concat), mask))(input)?;
[INFO] [stdout]    |                              -------------------------------------^ the trait `From<nom::Err<nom::error::Error<&str>>>` is not implemented for `error::ErrorKind`, which is required by `Result<(IpAddr, IpAddr), error::ErrorKind>: FromResidual<Result<Infallible, nom::Err<nom::error::Error<&str>>>>`
[INFO] [stdout]    |                              |
[INFO] [stdout]    |                              this can't be annotated with `?` because it has type `Result<_, nom::Err<nom::error::Error<&str>>>`
[INFO] [stdout]    |
[INFO] [stdout]    = note: the question mark operation (`?`) implicitly performs a conversion on the error value using the `From` trait
[INFO] [stdout]    = help: the following other types implement trait `From<T>`:
[INFO] [stdout]              <error::ErrorKind as From<AddrParseError>>
[INFO] [stdout]              <error::ErrorKind as From<ParseIntError>>
[INFO] [stdout]              <error::ErrorKind as From<nom::Err<(&str, nom::error::ErrorKind)>>>
[INFO] [stdout]    = note: required for `Result<(IpAddr, IpAddr), error::ErrorKind>` to implement `FromResidual<Result<Infallible, nom::Err<nom::error::Error<&str>>>>`
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error[E0277]: `?` couldn't convert the error to `error::ErrorKind`
[INFO] [stdout]   --> src/ip.rs:53:81
[INFO] [stdout]    |
[INFO] [stdout] 51 | pub fn parse_ip_mask_opt(input: &str) -> EatResult<(IpAddr, IpAddr)> {
[INFO] [stdout]    |                                          --------------------------- expected `error::ErrorKind` because of this
[INFO] [stdout] 52 |     let (_, (ip, _, mask)) =
[INFO] [stdout] 53 |         tuple((ip, alt((tag("/"), tag("-"), tag(" "), tag("\\"))), mask))(input)?;
[INFO] [stdout]    |         ------------------------------------------------------------------------^ the trait `From<nom::Err<nom::error::Error<&str>>>` is not implemented for `error::ErrorKind`, which is required by `Result<(IpAddr, IpAddr), error::ErrorKind>: FromResidual<Result<Infallible, nom::Err<nom::error::Error<&str>>>>`
[INFO] [stdout]    |         |
[INFO] [stdout]    |         this can't be annotated with `?` because it has type `Result<_, nom::Err<nom::error::Error<&str>>>`
[INFO] [stdout]    |
[INFO] [stdout]    = note: the question mark operation (`?`) implicitly performs a conversion on the error value using the `From` trait
[INFO] [stdout]    = help: the following other types implement trait `From<T>`:
[INFO] [stdout]              <error::ErrorKind as From<AddrParseError>>
[INFO] [stdout]              <error::ErrorKind as From<ParseIntError>>
[INFO] [stdout]              <error::ErrorKind as From<nom::Err<(&str, nom::error::ErrorKind)>>>
[INFO] [stdout]    = note: required for `Result<(IpAddr, IpAddr), error::ErrorKind>` to implement `FromResidual<Result<Infallible, nom::Err<nom::error::Error<&str>>>>`
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error[E0277]: `?` couldn't convert the error to `error::ErrorKind`
[INFO] [stdout]   --> src/ip.rs:60:67
[INFO] [stdout]    |
[INFO] [stdout] 59 | pub fn parse_ip_range<'a>(input: &'a str, concat: &'a str) -> EatResult<Range<IpAddr>> {
[INFO] [stdout]    |                                                               ------------------------ expected `error::ErrorKind` because of this
[INFO] [stdout] 60 |     let (_, (start, _, end)) = tuple((ip, tag(concat), ip))(input)?;
[INFO] [stdout]    |                                -----------------------------------^ the trait `From<nom::Err<nom::error::Error<&str>>>` is not implemented for `error::ErrorKind`, which is required by `Result<std::ops::Range<IpAddr>, error::ErrorKind>: FromResidual<Result<Infallible, nom::Err<nom::error::Error<&str>>>>`
[INFO] [stdout]    |                                |
[INFO] [stdout]    |                                this can't be annotated with `?` because it has type `Result<_, nom::Err<nom::error::Error<&str>>>`
[INFO] [stdout]    |
[INFO] [stdout]    = note: the question mark operation (`?`) implicitly performs a conversion on the error value using the `From` trait
[INFO] [stdout]    = help: the following other types implement trait `From<T>`:
[INFO] [stdout]              <error::ErrorKind as From<AddrParseError>>
[INFO] [stdout]              <error::ErrorKind as From<ParseIntError>>
[INFO] [stdout]              <error::ErrorKind as From<nom::Err<(&str, nom::error::ErrorKind)>>>
[INFO] [stdout]    = note: required for `Result<std::ops::Range<IpAddr>, error::ErrorKind>` to implement `FromResidual<Result<Infallible, nom::Err<nom::error::Error<&str>>>>`
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error[E0277]: `?` couldn't convert the error to `error::ErrorKind`
[INFO] [stdout]   --> src/ip.rs:68:79
[INFO] [stdout]    |
[INFO] [stdout] 66 | pub fn parse_ip_range_opt(input: &str) -> EatResult<Range<IpAddr>> {
[INFO] [stdout]    |                                           ------------------------ expected `error::ErrorKind` because of this
[INFO] [stdout] 67 |     let (_, (start, _, end)) =
[INFO] [stdout] 68 |         tuple((ip, alt((tag("/"), tag("-"), tag(" "), tag("\\"))), ip))(input)?;
[INFO] [stdout]    |         ----------------------------------------------------------------------^ the trait `From<nom::Err<nom::error::Error<&str>>>` is not implemented for `error::ErrorKind`, which is required by `Result<std::ops::Range<IpAddr>, error::ErrorKind>: FromResidual<Result<Infallible, nom::Err<nom::error::Error<&str>>>>`
[INFO] [stdout]    |         |
[INFO] [stdout]    |         this can't be annotated with `?` because it has type `Result<_, nom::Err<nom::error::Error<&str>>>`
[INFO] [stdout]    |
[INFO] [stdout]    = note: the question mark operation (`?`) implicitly performs a conversion on the error value using the `From` trait
[INFO] [stdout]    = help: the following other types implement trait `From<T>`:
[INFO] [stdout]              <error::ErrorKind as From<AddrParseError>>
[INFO] [stdout]              <error::ErrorKind as From<ParseIntError>>
[INFO] [stdout]              <error::ErrorKind as From<nom::Err<(&str, nom::error::ErrorKind)>>>
[INFO] [stdout]    = note: required for `Result<std::ops::Range<IpAddr>, error::ErrorKind>` to implement `FromResidual<Result<Infallible, nom::Err<nom::error::Error<&str>>>>`
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error[E0277]: `?` couldn't convert the error to `error::ErrorKind`
[INFO] [stdout]   --> src/ip.rs:75:69
[INFO] [stdout]    |
[INFO] [stdout] 74 | pub fn parse_ip_cidr<'a>(input: &'a str, concat: &'a str) -> EatResult<(IpAddr, usize)> {
[INFO] [stdout]    |                                                              -------------------------- expected `error::ErrorKind` because of this
[INFO] [stdout] 75 |     let (_, (ip, _, cidr)) = tuple((ip, tag(concat), digit1))(input)?;
[INFO] [stdout]    |                              ---------------------------------------^ the trait `From<nom::Err<nom::error::Error<&str>>>` is not implemented for `error::ErrorKind`, which is required by `Result<(IpAddr, usize), error::ErrorKind>: FromResidual<Result<Infallible, nom::Err<nom::error::Error<&str>>>>`
[INFO] [stdout]    |                              |
[INFO] [stdout]    |                              this can't be annotated with `?` because it has type `Result<_, nom::Err<nom::error::Error<&str>>>`
[INFO] [stdout]    |
[INFO] [stdout]    = note: the question mark operation (`?`) implicitly performs a conversion on the error value using the `From` trait
[INFO] [stdout]    = help: the following other types implement trait `From<T>`:
[INFO] [stdout]              <error::ErrorKind as From<AddrParseError>>
[INFO] [stdout]              <error::ErrorKind as From<ParseIntError>>
[INFO] [stdout]              <error::ErrorKind as From<nom::Err<(&str, nom::error::ErrorKind)>>>
[INFO] [stdout]    = note: required for `Result<(IpAddr, usize), error::ErrorKind>` to implement `FromResidual<Result<Infallible, nom::Err<nom::error::Error<&str>>>>`
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error[E0277]: `?` couldn't convert the error to `error::ErrorKind`
[INFO] [stdout]   --> src/ip.rs:83:83
[INFO] [stdout]    |
[INFO] [stdout] 81 | pub fn parse_ip_cidr_opt(input: &str) -> EatResult<(IpAddr, usize)> {
[INFO] [stdout]    |                                          -------------------------- expected `error::ErrorKind` because of this
[INFO] [stdout] 82 |     let (_, (ip, _, cidr)) =
[INFO] [stdout] 83 |         tuple((ip, alt((tag("/"), tag("-"), tag(" "), tag("\\"))), digit1))(input)?;
[INFO] [stdout]    |         --------------------------------------------------------------------------^ the trait `From<nom::Err<nom::error::Error<&str>>>` is not implemented for `error::ErrorKind`, which is required by `Result<(IpAddr, usize), error::ErrorKind>: FromResidual<Result<Infallible, nom::Err<nom::error::Error<&str>>>>`
[INFO] [stdout]    |         |
[INFO] [stdout]    |         this can't be annotated with `?` because it has type `Result<_, nom::Err<nom::error::Error<&str>>>`
[INFO] [stdout]    |
[INFO] [stdout]    = note: the question mark operation (`?`) implicitly performs a conversion on the error value using the `From` trait
[INFO] [stdout]    = help: the following other types implement trait `From<T>`:
[INFO] [stdout]              <error::ErrorKind as From<AddrParseError>>
[INFO] [stdout]              <error::ErrorKind as From<ParseIntError>>
[INFO] [stdout]              <error::ErrorKind as From<nom::Err<(&str, nom::error::ErrorKind)>>>
[INFO] [stdout]    = note: required for `Result<(IpAddr, usize), error::ErrorKind>` to implement `FromResidual<Result<Infallible, nom::Err<nom::error::Error<&str>>>>`
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error: aborting due to 7 previous errors
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] For more information about this error, try `rustc --explain E0277`.
[INFO] [stdout] 
[INFO] [stderr] error: could not compile `eat-nom` (lib) due to 8 previous errors
[INFO] [stderr] warning: build failed, waiting for other jobs to finish...
[INFO] [stdout] error: aborting due to 8 previous errors
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] For more information about this error, try `rustc --explain E0277`.
[INFO] [stdout] 
[INFO] [stderr] error: could not compile `eat-nom` (lib test) due to 9 previous errors
[INFO] running `Command { std: "docker" "inspect" "c92f9caf7e43d67e8f1bcde800b408ffde576bacd23de1214890d847f138b336", kill_on_drop: false }`
[INFO] running `Command { std: "docker" "rm" "-f" "c92f9caf7e43d67e8f1bcde800b408ffde576bacd23de1214890d847f138b336", kill_on_drop: false }`
[INFO] [stdout] c92f9caf7e43d67e8f1bcde800b408ffde576bacd23de1214890d847f138b336
