[INFO] cloning repository https://github.com/u2/ckb-time-oracle [INFO] running `Command { std: "git" "-c" "credential.helper=" "-c" "credential.helper=/workspace/cargo-home/bin/git-credential-null" "clone" "--bare" "https://github.com/u2/ckb-time-oracle" "/workspace/cache/git-repos/https%3A%2F%2Fgithub.com%2Fu2%2Fckb-time-oracle", kill_on_drop: false }` [INFO] [stderr] Cloning into bare repository '/workspace/cache/git-repos/https%3A%2F%2Fgithub.com%2Fu2%2Fckb-time-oracle'... [INFO] running `Command { std: "git" "rev-parse" "HEAD", kill_on_drop: false }` [INFO] [stdout] 70c77fef22681cdd9acf8420868d9cfc439cf187 [INFO] checking u2/ckb-time-oracle against master#9c3064e131f4939cc95a29bb11413c49bbda1491 for pr-144098 [INFO] running `Command { std: "git" "clone" "/workspace/cache/git-repos/https%3A%2F%2Fgithub.com%2Fu2%2Fckb-time-oracle" "/workspace/builds/worker-4-tc2/source", kill_on_drop: false }` [INFO] [stderr] Cloning into '/workspace/builds/worker-4-tc2/source'... [INFO] [stderr] done. [INFO] started tweaking git repo https://github.com/u2/ckb-time-oracle [INFO] finished tweaking git repo https://github.com/u2/ckb-time-oracle [INFO] tweaked toml for git repo https://github.com/u2/ckb-time-oracle written to /workspace/builds/worker-4-tc2/source/Cargo.toml [INFO] validating manifest of git repo https://github.com/u2/ckb-time-oracle on toolchain 9c3064e131f4939cc95a29bb11413c49bbda1491 [INFO] running `Command { std: CARGO_HOME="/workspace/cargo-home" RUSTUP_HOME="/workspace/rustup-home" "/workspace/cargo-home/bin/cargo" "+9c3064e131f4939cc95a29bb11413c49bbda1491" "metadata" "--manifest-path" "Cargo.toml" "--no-deps", kill_on_drop: false }` [INFO] crate git repo https://github.com/u2/ckb-time-oracle already has a lockfile, it will not be regenerated [INFO] running `Command { std: CARGO_HOME="/workspace/cargo-home" RUSTUP_HOME="/workspace/rustup-home" "/workspace/cargo-home/bin/cargo" "+9c3064e131f4939cc95a29bb11413c49bbda1491" "fetch" "--manifest-path" "Cargo.toml", kill_on_drop: false }` [INFO] [stderr] Blocking waiting for file lock on package cache [INFO] [stderr] Blocking waiting for file lock on package cache [INFO] [stderr] Downloading crates ... [INFO] [stderr] Downloaded ckb-hash v0.121.0 [INFO] [stderr] Downloaded ckb-hash v0.119.0 [INFO] [stderr] Downloaded ckb-std v0.16.4 [INFO] [stderr] Downloaded ckb-gen-types v0.119.0 [INFO] running `Command { std: "docker" "create" "-v" "/var/lib/crater-agent-workspace/builds/worker-4-tc2/target:/opt/rustwide/target:rw,Z" "-v" "/var/lib/crater-agent-workspace/builds/worker-4-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:cf8efcab8866f2cf4285301c7418e2f4f2a9b088c91ba69c40d5b659f81557f7" "/opt/rustwide/cargo-home/bin/cargo" "+9c3064e131f4939cc95a29bb11413c49bbda1491" "metadata" "--no-deps" "--format-version=1", kill_on_drop: false }` [INFO] [stdout] 1dc70af49a4e2e21df323a194fa09834a5ca3618ee71ef2e4ac2c68f6fb26e15 [INFO] running `Command { std: "docker" "start" "-a" "1dc70af49a4e2e21df323a194fa09834a5ca3618ee71ef2e4ac2c68f6fb26e15", kill_on_drop: false }` [INFO] running `Command { std: "docker" "inspect" "1dc70af49a4e2e21df323a194fa09834a5ca3618ee71ef2e4ac2c68f6fb26e15", kill_on_drop: false }` [INFO] running `Command { std: "docker" "rm" "-f" "1dc70af49a4e2e21df323a194fa09834a5ca3618ee71ef2e4ac2c68f6fb26e15", kill_on_drop: false }` [INFO] [stdout] 1dc70af49a4e2e21df323a194fa09834a5ca3618ee71ef2e4ac2c68f6fb26e15 [INFO] running `Command { std: "docker" "create" "-v" "/var/lib/crater-agent-workspace/builds/worker-4-tc2/target:/opt/rustwide/target:rw,Z" "-v" "/var/lib/crater-agent-workspace/builds/worker-4-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:cf8efcab8866f2cf4285301c7418e2f4f2a9b088c91ba69c40d5b659f81557f7" "/opt/rustwide/cargo-home/bin/cargo" "+9c3064e131f4939cc95a29bb11413c49bbda1491" "check" "--frozen" "--all" "--all-targets" "--message-format=json", kill_on_drop: false }` [INFO] [stdout] 3d4e0c289ced6b47fc9d7e2b620310ef376aef86e50c88309ab788141d864f37 [INFO] running `Command { std: "docker" "start" "-a" "3d4e0c289ced6b47fc9d7e2b620310ef376aef86e50c88309ab788141d864f37", kill_on_drop: false }` [INFO] [stderr] Checking blake2b-ref v0.3.1 [INFO] [stderr] Compiling shlex v1.3.0 [INFO] [stderr] Checking cfg-if v1.0.1 [INFO] [stderr] Checking bytes v1.10.1 [INFO] [stderr] Checking buddy-alloc v0.6.0 [INFO] [stderr] Checking gcd v2.3.0 [INFO] [stderr] Compiling cc v1.2.27 [INFO] [stderr] Checking molecule v0.8.0 [INFO] [stderr] Checking ckb-hash v0.119.0 [INFO] [stderr] Checking ckb-hash v0.121.0 [INFO] [stderr] Checking ckb-gen-types v0.119.0 [INFO] [stderr] Compiling ckb-std v0.16.4 [INFO] [stderr] Checking time v0.1.0 (/opt/rustwide/workdir/contracts/time) [INFO] [stdout] warning: unexpected `cfg` condition value: `native-simulator` [INFO] [stdout] --> contracts/time/src/main.rs:68:5 [INFO] [stdout] | [INFO] [stdout] 68 | ckb_std::debug!("This is a time script contract!"); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: no expected values for `feature` [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `ckb_std::debug` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `ckb_std::debug` may come from an old version of the `ckb_std` crate, try updating your dependency with `cargo update -p ckb_std` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: `#[warn(unexpected_cfgs)]` on by default [INFO] [stdout] = note: this warning originates in the macro `ckb_std::debug` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `native-simulator` [INFO] [stdout] --> contracts/time/src/main.rs:68:5 [INFO] [stdout] | [INFO] [stdout] 68 | ckb_std::debug!("This is a time script contract!"); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: no expected values for `feature` [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `ckb_std::debug` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `ckb_std::debug` may come from an old version of the `ckb_std` crate, try updating your dependency with `cargo update -p ckb_std` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `ckb_std::debug` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `native-simulator` [INFO] [stdout] --> contracts/time/src/main.rs:68:5 [INFO] [stdout] | [INFO] [stdout] 68 | ckb_std::debug!("This is a time script contract!"); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: no expected values for `feature` [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `ckb_std::debug` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `ckb_std::debug` may come from an old version of the `ckb_std` crate, try updating your dependency with `cargo update -p ckb_std` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: `#[warn(unexpected_cfgs)]` on by default [INFO] [stdout] = note: this warning originates in the macro `ckb_std::debug` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `native-simulator` [INFO] [stdout] --> contracts/time/src/main.rs:98:13 [INFO] [stdout] | [INFO] [stdout] 98 | debug!("load cell err: {:?}", e); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: no expected values for `feature` [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `debug` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `debug` may come from an old version of the `ckb_std` crate, try updating your dependency with `cargo update -p ckb_std` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `debug` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `native-simulator` [INFO] [stdout] --> contracts/time/src/main.rs:98:13 [INFO] [stdout] | [INFO] [stdout] 98 | debug!("load cell err: {:?}", e); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: no expected values for `feature` [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `debug` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `debug` may come from an old version of the `ckb_std` crate, try updating your dependency with `cargo update -p ckb_std` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `debug` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `native-simulator` [INFO] [stdout] --> contracts/time/src/main.rs:68:5 [INFO] [stdout] | [INFO] [stdout] 68 | ckb_std::debug!("This is a time script contract!"); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: no expected values for `feature` [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `ckb_std::debug` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `ckb_std::debug` may come from an old version of the `ckb_std` crate, try updating your dependency with `cargo update -p ckb_std` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `ckb_std::debug` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `native-simulator` [INFO] [stdout] --> contracts/time/src/main.rs:124:9 [INFO] [stdout] | [INFO] [stdout] 124 | debug!("There can only be at most one input time cell!"); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: no expected values for `feature` [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `debug` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `debug` may come from an old version of the `ckb_std` crate, try updating your dependency with `cargo update -p ckb_std` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `debug` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `native-simulator` [INFO] [stdout] --> contracts/time/src/main.rs:124:9 [INFO] [stdout] | [INFO] [stdout] 124 | debug!("There can only be at most one input time cell!"); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: no expected values for `feature` [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `debug` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `debug` may come from an old version of the `ckb_std` crate, try updating your dependency with `cargo update -p ckb_std` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `debug` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `native-simulator` [INFO] [stdout] --> contracts/time/src/main.rs:98:13 [INFO] [stdout] | [INFO] [stdout] 98 | debug!("load cell err: {:?}", e); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: no expected values for `feature` [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `debug` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `debug` may come from an old version of the `ckb_std` crate, try updating your dependency with `cargo update -p ckb_std` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `debug` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `native-simulator` [INFO] [stdout] --> contracts/time/src/main.rs:98:13 [INFO] [stdout] | [INFO] [stdout] 98 | debug!("load cell err: {:?}", e); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: no expected values for `feature` [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `debug` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `debug` may come from an old version of the `ckb_std` crate, try updating your dependency with `cargo update -p ckb_std` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `debug` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `native-simulator` [INFO] [stdout] --> contracts/time/src/main.rs:129:9 [INFO] [stdout] | [INFO] [stdout] 129 | debug!("There can only one output time cell!"); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: no expected values for `feature` [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `debug` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `debug` may come from an old version of the `ckb_std` crate, try updating your dependency with `cargo update -p ckb_std` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `debug` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `native-simulator` [INFO] [stdout] --> contracts/time/src/main.rs:124:9 [INFO] [stdout] | [INFO] [stdout] 124 | debug!("There can only be at most one input time cell!"); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: no expected values for `feature` [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `debug` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `debug` may come from an old version of the `ckb_std` crate, try updating your dependency with `cargo update -p ckb_std` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `debug` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `native-simulator` [INFO] [stdout] --> contracts/time/src/main.rs:129:9 [INFO] [stdout] | [INFO] [stdout] 129 | debug!("There can only one output time cell!"); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: no expected values for `feature` [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `debug` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `debug` may come from an old version of the `ckb_std` crate, try updating your dependency with `cargo update -p ckb_std` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `debug` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `native-simulator` [INFO] [stdout] --> contracts/time/src/main.rs:124:9 [INFO] [stdout] | [INFO] [stdout] 124 | debug!("There can only be at most one input time cell!"); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: no expected values for `feature` [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `debug` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `debug` may come from an old version of the `ckb_std` crate, try updating your dependency with `cargo update -p ckb_std` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `debug` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `native-simulator` [INFO] [stdout] --> contracts/time/src/main.rs:147:9 [INFO] [stdout] | [INFO] [stdout] 147 | ckb_std::debug!("ret: {:?}, type_id: {:?}", ret, type_id); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: no expected values for `feature` [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `ckb_std::debug` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `ckb_std::debug` may come from an old version of the `ckb_std` crate, try updating your dependency with `cargo update -p ckb_std` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `ckb_std::debug` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `native-simulator` [INFO] [stdout] --> contracts/time/src/main.rs:147:9 [INFO] [stdout] | [INFO] [stdout] 147 | ckb_std::debug!("ret: {:?}, type_id: {:?}", ret, type_id); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: no expected values for `feature` [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `ckb_std::debug` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `ckb_std::debug` may come from an old version of the `ckb_std` crate, try updating your dependency with `cargo update -p ckb_std` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `ckb_std::debug` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `native-simulator` [INFO] [stdout] --> contracts/time/src/main.rs:129:9 [INFO] [stdout] | [INFO] [stdout] 129 | debug!("There can only one output time cell!"); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: no expected values for `feature` [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `debug` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `debug` may come from an old version of the `ckb_std` crate, try updating your dependency with `cargo update -p ckb_std` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `debug` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `native-simulator` [INFO] [stdout] --> contracts/time/src/main.rs:150:13 [INFO] [stdout] | [INFO] [stdout] 150 | debug!("Invalid type ID!"); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: no expected values for `feature` [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `debug` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `debug` may come from an old version of the `ckb_std` crate, try updating your dependency with `cargo update -p ckb_std` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `debug` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `native-simulator` [INFO] [stdout] --> contracts/time/src/main.rs:150:13 [INFO] [stdout] | [INFO] [stdout] 150 | debug!("Invalid type ID!"); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: no expected values for `feature` [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `debug` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `debug` may come from an old version of the `ckb_std` crate, try updating your dependency with `cargo update -p ckb_std` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `debug` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `native-simulator` [INFO] [stdout] --> contracts/time/src/main.rs:129:9 [INFO] [stdout] | [INFO] [stdout] 129 | debug!("There can only one output time cell!"); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: no expected values for `feature` [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `debug` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `debug` may come from an old version of the `ckb_std` crate, try updating your dependency with `cargo update -p ckb_std` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `debug` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `native-simulator` [INFO] [stdout] --> contracts/time/src/main.rs:163:9 [INFO] [stdout] | [INFO] [stdout] 163 | debug!("Length of type id is incorrect!"); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: no expected values for `feature` [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `debug` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `debug` may come from an old version of the `ckb_std` crate, try updating your dependency with `cargo update -p ckb_std` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `debug` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `native-simulator` [INFO] [stdout] --> contracts/time/src/main.rs:147:9 [INFO] [stdout] | [INFO] [stdout] 147 | ckb_std::debug!("ret: {:?}, type_id: {:?}", ret, type_id); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: no expected values for `feature` [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `ckb_std::debug` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `ckb_std::debug` may come from an old version of the `ckb_std` crate, try updating your dependency with `cargo update -p ckb_std` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `ckb_std::debug` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `native-simulator` [INFO] [stdout] --> contracts/time/src/main.rs:163:9 [INFO] [stdout] | [INFO] [stdout] 163 | debug!("Length of type id is incorrect!"); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: no expected values for `feature` [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `debug` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `debug` may come from an old version of the `ckb_std` crate, try updating your dependency with `cargo update -p ckb_std` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `debug` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `native-simulator` [INFO] [stdout] --> contracts/time/src/main.rs:147:9 [INFO] [stdout] | [INFO] [stdout] 147 | ckb_std::debug!("ret: {:?}, type_id: {:?}", ret, type_id); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: no expected values for `feature` [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `ckb_std::debug` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `ckb_std::debug` may come from an old version of the `ckb_std` crate, try updating your dependency with `cargo update -p ckb_std` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `ckb_std::debug` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `native-simulator` [INFO] [stdout] --> contracts/time/src/main.rs:177:9 [INFO] [stdout] | [INFO] [stdout] 177 | / debug!( [INFO] [stdout] 178 | | "Length of always success is incorrect! args len is {}", [INFO] [stdout] 179 | | args.raw_data().len() [INFO] [stdout] 180 | | ); [INFO] [stdout] | |_________^ [INFO] [stdout] | [INFO] [stdout] = note: no expected values for `feature` [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `debug` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `debug` may come from an old version of the `ckb_std` crate, try updating your dependency with `cargo update -p ckb_std` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `debug` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `native-simulator` [INFO] [stdout] --> contracts/time/src/main.rs:150:13 [INFO] [stdout] | [INFO] [stdout] 150 | debug!("Invalid type ID!"); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: no expected values for `feature` [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `debug` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `debug` may come from an old version of the `ckb_std` crate, try updating your dependency with `cargo update -p ckb_std` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `debug` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `native-simulator` [INFO] [stdout] --> contracts/time/src/main.rs:150:13 [INFO] [stdout] | [INFO] [stdout] 150 | debug!("Invalid type ID!"); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: no expected values for `feature` [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `debug` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `debug` may come from an old version of the `ckb_std` crate, try updating your dependency with `cargo update -p ckb_std` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `debug` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `native-simulator` [INFO] [stdout] --> contracts/time/src/main.rs:177:9 [INFO] [stdout] | [INFO] [stdout] 177 | / debug!( [INFO] [stdout] 178 | | "Length of always success is incorrect! args len is {}", [INFO] [stdout] 179 | | args.raw_data().len() [INFO] [stdout] 180 | | ); [INFO] [stdout] | |_________^ [INFO] [stdout] | [INFO] [stdout] = note: no expected values for `feature` [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `debug` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `debug` may come from an old version of the `ckb_std` crate, try updating your dependency with `cargo update -p ckb_std` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `debug` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] error: `#[panic_handler]` function required, but not found [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] error: unwinding panics are not supported without std [INFO] [stdout] | [INFO] [stdout] = help: using nightly cargo, use -Zbuild-std with panic="abort" to avoid unwinding [INFO] [stdout] = note: since the core library is usually precompiled with panic="unwind", rebuilding your crate with panic="abort" may not be enough to fix the problem [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `native-simulator` [INFO] [stdout] --> contracts/time/src/main.rs:163:9 [INFO] [stdout] | [INFO] [stdout] 163 | debug!("Length of type id is incorrect!"); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: no expected values for `feature` [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `debug` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `debug` may come from an old version of the `ckb_std` crate, try updating your dependency with `cargo update -p ckb_std` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `debug` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `native-simulator` [INFO] [stdout] --> contracts/time/src/main.rs:163:9 [INFO] [stdout] | [INFO] [stdout] 163 | debug!("Length of type id is incorrect!"); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: no expected values for `feature` [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `debug` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `debug` may come from an old version of the `ckb_std` crate, try updating your dependency with `cargo update -p ckb_std` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `debug` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `native-simulator` [INFO] [stdout] --> contracts/time/src/main.rs:177:9 [INFO] [stdout] | [INFO] [stdout] 177 | / debug!( [INFO] [stdout] 178 | | "Length of always success is incorrect! args len is {}", [INFO] [stdout] 179 | | args.raw_data().len() [INFO] [stdout] 180 | | ); [INFO] [stdout] | |_________^ [INFO] [stdout] | [INFO] [stdout] = note: no expected values for `feature` [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `debug` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `debug` may come from an old version of the `ckb_std` crate, try updating your dependency with `cargo update -p ckb_std` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `debug` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `native-simulator` [INFO] [stdout] --> contracts/time/src/main.rs:177:9 [INFO] [stdout] | [INFO] [stdout] 177 | / debug!( [INFO] [stdout] 178 | | "Length of always success is incorrect! args len is {}", [INFO] [stdout] 179 | | args.raw_data().len() [INFO] [stdout] 180 | | ); [INFO] [stdout] | |_________^ [INFO] [stdout] | [INFO] [stdout] = note: no expected values for `feature` [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `debug` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `debug` may come from an old version of the `ckb_std` crate, try updating your dependency with `cargo update -p ckb_std` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `debug` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stderr] error: could not compile `time` (bin "time") due to 2 previous errors; 16 warnings emitted [INFO] running `Command { std: "docker" "inspect" "3d4e0c289ced6b47fc9d7e2b620310ef376aef86e50c88309ab788141d864f37", kill_on_drop: false }` [INFO] running `Command { std: "docker" "rm" "-f" "3d4e0c289ced6b47fc9d7e2b620310ef376aef86e50c88309ab788141d864f37", kill_on_drop: false }` [INFO] [stdout] 3d4e0c289ced6b47fc9d7e2b620310ef376aef86e50c88309ab788141d864f37