Build #1751501 2025-02-14T08:50:36.453458+00:00
# rustc version
rustc 1.86.0-nightly (a567209da 2025-02-13)# docs.rs version
docsrs 0.6.0 (35977596 2025-02-09)# build log
[INFO] running `Command { std: "docker" "create" "-v" "/home/cratesfyi/workspace/builds/rendy-graph-0.5.1/target:/opt/rustwide/target:rw,Z" "-v" "/home/cratesfyi/workspace/builds/rendy-graph-0.5.1/source:/opt/rustwide/workdir:ro,Z" "-v" "/home/cratesfyi/workspace/cargo-home:/opt/rustwide/cargo-home:ro,Z" "-v" "/home/cratesfyi/workspace/rustup-home:/opt/rustwide/rustup-home:ro,Z" "-e" "SOURCE_DIR=/opt/rustwide/workdir" "-e" "CARGO_TARGET_DIR=/opt/rustwide/target" "-e" "DOCS_RS=1" "-e" "CARGO_HOME=/opt/rustwide/cargo-home" "-e" "RUSTUP_HOME=/opt/rustwide/rustup-home" "-w" "/opt/rustwide/workdir" "-m" "6442450944" "--cpus" "6" "--user" "1001:1001" "--network" "none" "ghcr.io/rust-lang/crates-build-env/linux@sha256:3959728d45483eb673ba100a951a6b9f5012970368db2a9e08e0ac9b67c8a5ad" "/opt/rustwide/cargo-home/bin/cargo" "+nightly" "rustdoc" "--lib" "-Zrustdoc-map" "--config" "build.rustdocflags=[\"--cfg\", \"docsrs\", \"-Z\", \"unstable-options\", \"--emit=invocation-specific\", \"--resource-suffix\", \"-20250213-1.86.0-nightly-a567209da\", \"--static-root-path\", \"/-/rustdoc.static/\", \"--cap-lints\", \"warn\", \"--extern-html-root-takes-precedence\"]" "--offline" "-Zunstable-options" "--config=doc.extern-map.registries.crates-io=\"https://docs.rs/{pkg_name}/{version}/x86_64-unknown-linux-gnu\"" "-Zrustdoc-scrape-examples" "-j6" "--target" "x86_64-unknown-linux-gnu", kill_on_drop: false }`
[INFO] [stderr] WARNING: Your kernel does not support swap limit capabilities or the cgroup is not mounted. Memory limited without swap.
[INFO] [stdout] 8b74d87ea4d0c01e467f6c35715f3dac4b5304c7b98dcda6449ad69403732900
[INFO] running `Command { std: "docker" "start" "-a" "8b74d87ea4d0c01e467f6c35715f3dac4b5304c7b98dcda6449ad69403732900", kill_on_drop: false }`
[INFO] [stderr] warning: target filter specified, but no targets matched; this is a no-op
[INFO] [stderr] Documenting rendy-graph v0.5.1 (/opt/rustwide/workdir)
[INFO] [stderr] warning: unexpected `cfg` condition value: `thread_profiler`
[INFO] [stderr] --> src/graph/mod.rs:78:9
[INFO] [stderr] |
[INFO] [stderr] 78 | profile_scope!("alloc");
[INFO] [stderr] | ^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stderr] |
[INFO] [stderr] = note: expected values for `feature` are: `dx12`, `empty`, `gl`, `metal`, `no-slow-safety-checks`, `profiler`, `serde`, and `vulkan`
[INFO] [stderr] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stderr] = help: try referring to `profile_scope` crate for guidance on how handle this unexpected cfg
[INFO] [stderr] = help: the macro `profile_scope` may come from an old version of the `thread_profiler` crate, try updating your dependency with `cargo update -p thread_profiler`
[INFO] [stderr] = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stderr] = note: `#[warn(unexpected_cfgs)]` on by default
[INFO] [stderr] = note: this warning originates in the macro `profile_scope` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stderr]
[INFO] [stderr] warning: unexpected `cfg` condition value: `thread_profiler`
[INFO] [stderr] --> src/graph/mod.rs:168:9
[INFO] [stderr] |
[INFO] [stderr] 168 | profile_scope!("run");
[INFO] [stderr] | ^^^^^^^^^^^^^^^^^^^^^
[INFO] [stderr] |
[INFO] [stderr] = note: expected values for `feature` are: `dx12`, `empty`, `gl`, `metal`, `no-slow-safety-checks`, `profiler`, `serde`, and `vulkan`
[INFO] [stderr] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stderr] = help: try referring to `profile_scope` crate for guidance on how handle this unexpected cfg
[INFO] [stderr] = help: the macro `profile_scope` may come from an old version of the `thread_profiler` crate, try updating your dependency with `cargo update -p thread_profiler`
[INFO] [stderr] = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stderr] = note: this warning originates in the macro `profile_scope` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stderr]
[INFO] [stderr] warning: unexpected `cfg` condition value: `thread_profiler`
[INFO] [stderr] --> src/graph/mod.rs:267:9
[INFO] [stderr] |
[INFO] [stderr] 267 | profile_scope!("dispose");
[INFO] [stderr] | ^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stderr] |
[INFO] [stderr] = note: expected values for `feature` are: `dx12`, `empty`, `gl`, `metal`, `no-slow-safety-checks`, `profiler`, `serde`, and `vulkan`
[INFO] [stderr] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stderr] = help: try referring to `profile_scope` crate for guidance on how handle this unexpected cfg
[INFO] [stderr] = help: the macro `profile_scope` may come from an old version of the `thread_profiler` crate, try updating your dependency with `cargo update -p thread_profiler`
[INFO] [stderr] = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stderr] = note: this warning originates in the macro `profile_scope` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stderr]
[INFO] [stderr] warning: unexpected `cfg` condition value: `thread_profiler`
[INFO] [stderr] --> src/graph/mod.rs:347:9
[INFO] [stderr] |
[INFO] [stderr] 347 | profile_scope!("create_buffer");
[INFO] [stderr] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stderr] |
[INFO] [stderr] = note: expected values for `feature` are: `dx12`, `empty`, `gl`, `metal`, `no-slow-safety-checks`, `profiler`, `serde`, and `vulkan`
[INFO] [stderr] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stderr] = help: try referring to `profile_scope` crate for guidance on how handle this unexpected cfg
[INFO] [stderr] = help: the macro `profile_scope` may come from an old version of the `thread_profiler` crate, try updating your dependency with `cargo update -p thread_profiler`
[INFO] [stderr] = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stderr] = note: this warning originates in the macro `profile_scope` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stderr]
[INFO] [stderr] warning: unexpected `cfg` condition value: `thread_profiler`
[INFO] [stderr] --> src/graph/mod.rs:364:9
[INFO] [stderr] |
[INFO] [stderr] 364 | profile_scope!("create_image");
[INFO] [stderr] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stderr] |
[INFO] [stderr] = note: expected values for `feature` are: `dx12`, `empty`, `gl`, `metal`, `no-slow-safety-checks`, `profiler`, `serde`, and `vulkan`
[INFO] [stderr] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stderr] = help: try referring to `profile_scope` crate for guidance on how handle this unexpected cfg
[INFO] [stderr] = help: the macro `profile_scope` may come from an old version of the `thread_profiler` crate, try updating your dependency with `cargo update -p thread_profiler`
[INFO] [stderr] = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stderr] = note: this warning originates in the macro `profile_scope` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stderr]
[INFO] [stderr] warning: unexpected `cfg` condition value: `thread_profiler`
[INFO] [stderr] --> src/graph/mod.rs:414:9
[INFO] [stderr] |
[INFO] [stderr] 414 | profile_scope!("build");
[INFO] [stderr] | ^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stderr] |
[INFO] [stderr] = note: expected values for `feature` are: `dx12`, `empty`, `gl`, `metal`, `no-slow-safety-checks`, `profiler`, `serde`, and `vulkan`
[INFO] [stderr] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stderr] = help: try referring to `profile_scope` crate for guidance on how handle this unexpected cfg
[INFO] [stderr] = help: the macro `profile_scope` may come from an old version of the `thread_profiler` crate, try updating your dependency with `cargo update -p thread_profiler`
[INFO] [stderr] = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stderr] = note: this warning originates in the macro `profile_scope` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stderr]
[INFO] [stderr] warning: unexpected `cfg` condition value: `thread_profiler`
[INFO] [stderr] --> src/graph/mod.rs:418:13
[INFO] [stderr] |
[INFO] [stderr] 418 | profile_scope!("schedule_nodes");
[INFO] [stderr] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stderr] |
[INFO] [stderr] = note: expected values for `feature` are: `dx12`, `empty`, `gl`, `metal`, `no-slow-safety-checks`, `profiler`, `serde`, and `vulkan`
[INFO] [stderr] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stderr] = help: try referring to `profile_scope` crate for guidance on how handle this unexpected cfg
[INFO] [stderr] = help: the macro `profile_scope` may come from an old version of the `thread_profiler` crate, try updating your dependency with `cargo update -p thread_profiler`
[INFO] [stderr] = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stderr] = note: this warning originates in the macro `profile_scope` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stderr]
[INFO] [stderr] warning: unexpected `cfg` condition value: `thread_profiler`
[INFO] [stderr] --> src/graph/mod.rs:454:13
[INFO] [stderr] |
[INFO] [stderr] 454 | profile_scope!("build_nodes");
[INFO] [stderr] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stderr] |
[INFO] [stderr] = note: expected values for `feature` are: `dx12`, `empty`, `gl`, `metal`, `no-slow-safety-checks`, `profiler`, `serde`, and `vulkan`
[INFO] [stderr] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stderr] = help: try referring to `profile_scope` crate for guidance on how handle this unexpected cfg
[INFO] [stderr] = help: the macro `profile_scope` may come from an old version of the `thread_profiler` crate, try updating your dependency with `cargo update -p thread_profiler`
[INFO] [stderr] = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stderr] = note: this warning originates in the macro `profile_scope` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stderr]
[INFO] [stderr] warning: `rendy-graph` (lib doc) generated 8 warnings
[INFO] [stderr] Finished `dev` profile [unoptimized + debuginfo] target(s) in 0.63s
[INFO] [stderr] Generated /opt/rustwide/target/x86_64-unknown-linux-gnu/doc/rendy_graph/index.html
[INFO] running `Command { std: "docker" "inspect" "8b74d87ea4d0c01e467f6c35715f3dac4b5304c7b98dcda6449ad69403732900", kill_on_drop: false }`
[INFO] running `Command { std: "docker" "rm" "-f" "8b74d87ea4d0c01e467f6c35715f3dac4b5304c7b98dcda6449ad69403732900", kill_on_drop: false }`
[INFO] [stdout] 8b74d87ea4d0c01e467f6c35715f3dac4b5304c7b98dcda6449ad69403732900