Build #1751494 2025-02-14T08:49:02.457847+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-factory-0.5.1/target:/opt/rustwide/target:rw,Z" "-v" "/home/cratesfyi/workspace/builds/rendy-factory-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] 0a19e9bec613655f1d929c3c25e819422a071c8ecb79d0f227383a23af74c59c
[INFO] running `Command { std: "docker" "start" "-a" "0a19e9bec613655f1d929c3c25e819422a071c8ecb79d0f227383a23af74c59c", kill_on_drop: false }`
[INFO] [stderr] warning: target filter specified, but no targets matched; this is a no-op
[INFO] [stderr] Documenting rendy-factory v0.5.1 (/opt/rustwide/workdir)
[INFO] [stderr] warning: unexpected `cfg` condition value: `thread_profiler`
[INFO] [stderr] --> src/factory.rs:231:9
[INFO] [stderr] |
[INFO] [stderr] 231 | profile_scope!("wait_idle");
[INFO] [stderr] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stderr] |
[INFO] [stderr] = note: expected values for `feature` are: `dx12`, `empty`, `gl`, `metal`, `no-slow-safety-checks`, `profiler`, `serde`, and `serde-1`
[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/factory.rs:250:9
[INFO] [stderr] |
[INFO] [stderr] 250 | profile_scope!("create_relevant_buffer");
[INFO] [stderr] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stderr] |
[INFO] [stderr] = note: expected values for `feature` are: `dx12`, `empty`, `gl`, `metal`, `no-slow-safety-checks`, `profiler`, `serde`, and `serde-1`
[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/factory.rs:294:9
[INFO] [stderr] |
[INFO] [stderr] 294 | profile_scope!("create_relevant_image");
[INFO] [stderr] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stderr] |
[INFO] [stderr] = note: expected values for `feature` are: `dx12`, `empty`, `gl`, `metal`, `no-slow-safety-checks`, `profiler`, `serde`, and `serde-1`
[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/factory.rs:680:9
[INFO] [stderr] |
[INFO] [stderr] 680 | profile_scope!("create_surface");
[INFO] [stderr] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stderr] |
[INFO] [stderr] = note: expected values for `feature` are: `dx12`, `empty`, `gl`, `metal`, `no-slow-safety-checks`, `profiler`, `serde`, and `serde-1`
[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/factory.rs:698:9
[INFO] [stderr] |
[INFO] [stderr] 698 | profile_scope!("create_surface");
[INFO] [stderr] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stderr] |
[INFO] [stderr] = note: expected values for `feature` are: `dx12`, `empty`, `gl`, `metal`, `no-slow-safety-checks`, `profiler`, `serde`, and `serde-1`
[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/factory.rs:716:9
[INFO] [stderr] |
[INFO] [stderr] 716 | profile_scope!("get_surface_compatibility");
[INFO] [stderr] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stderr] |
[INFO] [stderr] = note: expected values for `feature` are: `dx12`, `empty`, `gl`, `metal`, `no-slow-safety-checks`, `profiler`, `serde`, and `serde-1`
[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/factory.rs:735:9
[INFO] [stderr] |
[INFO] [stderr] 735 | profile_scope!("get_surface_compatibility");
[INFO] [stderr] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stderr] |
[INFO] [stderr] = note: expected values for `feature` are: `dx12`, `empty`, `gl`, `metal`, `no-slow-safety-checks`, `profiler`, `serde`, and `serde-1`
[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/factory.rs:751:9
[INFO] [stderr] |
[INFO] [stderr] 751 | profile_scope!("get_surface_format");
[INFO] [stderr] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stderr] |
[INFO] [stderr] = note: expected values for `feature` are: `dx12`, `empty`, `gl`, `metal`, `no-slow-safety-checks`, `profiler`, `serde`, and `serde-1`
[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/factory.rs:803:9
[INFO] [stderr] |
[INFO] [stderr] 803 | profile_scope!("create_target");
[INFO] [stderr] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stderr] |
[INFO] [stderr] = note: expected values for `feature` are: `dx12`, `empty`, `gl`, `metal`, `no-slow-safety-checks`, `profiler`, `serde`, and `serde-1`
[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/factory.rs:838:9
[INFO] [stderr] |
[INFO] [stderr] 838 | profile_scope!("create_semaphore");
[INFO] [stderr] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stderr] |
[INFO] [stderr] = note: expected values for `feature` are: `dx12`, `empty`, `gl`, `metal`, `no-slow-safety-checks`, `profiler`, `serde`, and `serde-1`
[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/factory.rs:893:9
[INFO] [stderr] |
[INFO] [stderr] 893 | profile_scope!("wait_for_fence");
[INFO] [stderr] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stderr] |
[INFO] [stderr] = note: expected values for `feature` are: `dx12`, `empty`, `gl`, `metal`, `no-slow-safety-checks`, `profiler`, `serde`, and `serde-1`
[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/factory.rs:917:9
[INFO] [stderr] |
[INFO] [stderr] 917 | profile_scope!("wait_for_fences");
[INFO] [stderr] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stderr] |
[INFO] [stderr] = note: expected values for `feature` are: `dx12`, `empty`, `gl`, `metal`, `no-slow-safety-checks`, `profiler`, `serde`, and `serde-1`
[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/factory.rs:1002:9
[INFO] [stderr] |
[INFO] [stderr] 1002 | profile_scope!("create_command_pool");
[INFO] [stderr] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stderr] |
[INFO] [stderr] = note: expected values for `feature` are: `dx12`, `empty`, `gl`, `metal`, `no-slow-safety-checks`, `profiler`, `serde`, and `serde-1`
[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/factory.rs:1041:9
[INFO] [stderr] |
[INFO] [stderr] 1041 | profile_scope!("cleanup");
[INFO] [stderr] | ^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stderr] |
[INFO] [stderr] = note: expected values for `feature` are: `dx12`, `empty`, `gl`, `metal`, `no-slow-safety-checks`, `profiler`, `serde`, and `serde-1`
[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/factory.rs:1128:9
[INFO] [stderr] |
[INFO] [stderr] 1128 | profile_scope!("create_descriptor_sets");
[INFO] [stderr] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stderr] |
[INFO] [stderr] = note: expected values for `feature` are: `dx12`, `empty`, `gl`, `metal`, `no-slow-safety-checks`, `profiler`, `serde`, and `serde-1`
[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: unresolved link to `flush_uploads`
[INFO] [stderr] --> src/factory.rs:484:21
[INFO] [stderr] |
[INFO] [stderr] 484 | /// upon next [`flush_uploads`] or [`maintain`] call to this `Factory`, and
[INFO] [stderr] | ^^^^^^^^^^^^^ no item named `flush_uploads` in scope
[INFO] [stderr] |
[INFO] [stderr] = help: to escape `[` and `]` characters, add '\' before them like `\[` or `\]`
[INFO] [stderr] = note: `#[warn(rustdoc::broken_intra_doc_links)]` on by default
[INFO] [stderr]
[INFO] [stderr] warning: unresolved link to `maintain`
[INFO] [stderr] --> src/factory.rs:484:42
[INFO] [stderr] |
[INFO] [stderr] 484 | /// upon next [`flush_uploads`] or [`maintain`] call to this `Factory`, and
[INFO] [stderr] | ^^^^^^^^ no item named `maintain` in scope
[INFO] [stderr] |
[INFO] [stderr] = help: to escape `[` and `]` characters, add '\' before them like `\[` or `\]`
[INFO] [stderr]
[INFO] [stderr] warning: unresolved link to `flush_uploads`
[INFO] [stderr] --> src/factory.rs:487:11
[INFO] [stderr] |
[INFO] [stderr] 487 | /// [`flush_uploads`] or [`maintain`] call
[INFO] [stderr] | ^^^^^^^^^^^^^ no item named `flush_uploads` in scope
[INFO] [stderr] |
[INFO] [stderr] = help: to escape `[` and `]` characters, add '\' before them like `\[` or `\]`
[INFO] [stderr]
[INFO] [stderr] warning: unresolved link to `maintain`
[INFO] [stderr] --> src/factory.rs:487:32
[INFO] [stderr] |
[INFO] [stderr] 487 | /// [`flush_uploads`] or [`maintain`] call
[INFO] [stderr] | ^^^^^^^^ no item named `maintain` in scope
[INFO] [stderr] |
[INFO] [stderr] = help: to escape `[` and `]` characters, add '\' before them like `\[` or `\]`
[INFO] [stderr]
[INFO] [stderr] warning: unresolved link to `flush_uploads`
[INFO] [stderr] --> src/factory.rs:537:21
[INFO] [stderr] |
[INFO] [stderr] 537 | /// upon next [`flush_uploads`] or [`maintain`] call to this `Factory`, and
[INFO] [stderr] | ^^^^^^^^^^^^^ no item named `flush_uploads` in scope
[INFO] [stderr] |
[INFO] [stderr] = help: to escape `[` and `]` characters, add '\' before them like `\[` or `\]`
[INFO] [stderr]
[INFO] [stderr] warning: unresolved link to `maintain`
[INFO] [stderr] --> src/factory.rs:537:42
[INFO] [stderr] |
[INFO] [stderr] 537 | /// upon next [`flush_uploads`] or [`maintain`] call to this `Factory`, and
[INFO] [stderr] | ^^^^^^^^ no item named `maintain` in scope
[INFO] [stderr] |
[INFO] [stderr] = help: to escape `[` and `]` characters, add '\' before them like `\[` or `\]`
[INFO] [stderr]
[INFO] [stderr] warning: unresolved link to `flush_uploads`
[INFO] [stderr] --> src/factory.rs:540:11
[INFO] [stderr] |
[INFO] [stderr] 540 | /// [`flush_uploads`] or [`maintain`] call
[INFO] [stderr] | ^^^^^^^^^^^^^ no item named `flush_uploads` in scope
[INFO] [stderr] |
[INFO] [stderr] = help: to escape `[` and `]` characters, add '\' before them like `\[` or `\]`
[INFO] [stderr]
[INFO] [stderr] warning: unresolved link to `maintain`
[INFO] [stderr] --> src/factory.rs:540:32
[INFO] [stderr] |
[INFO] [stderr] 540 | /// [`flush_uploads`] or [`maintain`] call
[INFO] [stderr] | ^^^^^^^^ no item named `maintain` in scope
[INFO] [stderr] |
[INFO] [stderr] = help: to escape `[` and `]` characters, add '\' before them like `\[` or `\]`
[INFO] [stderr]
[INFO] [stderr] warning: unresolved link to `flush_uploads`
[INFO] [stderr] --> src/factory.rs:566:21
[INFO] [stderr] |
[INFO] [stderr] 566 | /// upon next [`flush_uploads`] or [`maintain`] call to this `Factory`, and
[INFO] [stderr] | ^^^^^^^^^^^^^ no item named `flush_uploads` in scope
[INFO] [stderr] |
[INFO] [stderr] = help: to escape `[` and `]` characters, add '\' before them like `\[` or `\]`
[INFO] [stderr]
[INFO] [stderr] warning: unresolved link to `maintain`
[INFO] [stderr] --> src/factory.rs:566:42
[INFO] [stderr] |
[INFO] [stderr] 566 | /// upon next [`flush_uploads`] or [`maintain`] call to this `Factory`, and
[INFO] [stderr] | ^^^^^^^^ no item named `maintain` in scope
[INFO] [stderr] |
[INFO] [stderr] = help: to escape `[` and `]` characters, add '\' before them like `\[` or `\]`
[INFO] [stderr]
[INFO] [stderr] warning: unresolved link to `flush_uploads`
[INFO] [stderr] --> src/factory.rs:569:11
[INFO] [stderr] |
[INFO] [stderr] 569 | /// [`flush_uploads`] or [`maintain`] call
[INFO] [stderr] | ^^^^^^^^^^^^^ no item named `flush_uploads` in scope
[INFO] [stderr] |
[INFO] [stderr] = help: to escape `[` and `]` characters, add '\' before them like `\[` or `\]`
[INFO] [stderr]
[INFO] [stderr] warning: unresolved link to `maintain`
[INFO] [stderr] --> src/factory.rs:569:32
[INFO] [stderr] |
[INFO] [stderr] 569 | /// [`flush_uploads`] or [`maintain`] call
[INFO] [stderr] | ^^^^^^^^ no item named `maintain` in scope
[INFO] [stderr] |
[INFO] [stderr] = help: to escape `[` and `]` characters, add '\' before them like `\[` or `\]`
[INFO] [stderr]
[INFO] [stderr] warning: unresolved link to `flush_uploads`
[INFO] [stderr] --> src/factory.rs:590:21
[INFO] [stderr] |
[INFO] [stderr] 590 | /// upon next [`flush_uploads`] or [`maintain`] call to this `Factory`, and
[INFO] [stderr] | ^^^^^^^^^^^^^ no item named `flush_uploads` in scope
[INFO] [stderr] |
[INFO] [stderr] = help: to escape `[` and `]` characters, add '\' before them like `\[` or `\]`
[INFO] [stderr]
[INFO] [stderr] warning: unresolved link to `maintain`
[INFO] [stderr] --> src/factory.rs:590:42
[INFO] [stderr] |
[INFO] [stderr] 590 | /// upon next [`flush_uploads`] or [`maintain`] call to this `Factory`, and
[INFO] [stderr] | ^^^^^^^^ no item named `maintain` in scope
[INFO] [stderr] |
[INFO] [stderr] = help: to escape `[` and `]` characters, add '\' before them like `\[` or `\]`
[INFO] [stderr]
[INFO] [stderr] warning: unresolved link to `flush_uploads`
[INFO] [stderr] --> src/factory.rs:593:11
[INFO] [stderr] |
[INFO] [stderr] 593 | /// [`flush_uploads`] or [`maintain`] call
[INFO] [stderr] | ^^^^^^^^^^^^^ no item named `flush_uploads` in scope
[INFO] [stderr] |
[INFO] [stderr] = help: to escape `[` and `]` characters, add '\' before them like `\[` or `\]`
[INFO] [stderr]
[INFO] [stderr] warning: unresolved link to `maintain`
[INFO] [stderr] --> src/factory.rs:593:32
[INFO] [stderr] |
[INFO] [stderr] 593 | /// [`flush_uploads`] or [`maintain`] call
[INFO] [stderr] | ^^^^^^^^ no item named `maintain` in scope
[INFO] [stderr] |
[INFO] [stderr] = help: to escape `[` and `]` characters, add '\' before them like `\[` or `\]`
[INFO] [stderr]
[INFO] [stderr] warning: `rendy-factory` (lib doc) generated 31 warnings
[INFO] [stderr] Finished `dev` profile [unoptimized + debuginfo] target(s) in 0.61s
[INFO] [stderr] Generated /opt/rustwide/target/x86_64-unknown-linux-gnu/doc/rendy_factory/index.html
[INFO] running `Command { std: "docker" "inspect" "0a19e9bec613655f1d929c3c25e819422a071c8ecb79d0f227383a23af74c59c", kill_on_drop: false }`
[INFO] running `Command { std: "docker" "rm" "-f" "0a19e9bec613655f1d929c3c25e819422a071c8ecb79d0f227383a23af74c59c", kill_on_drop: false }`
[INFO] [stdout] 0a19e9bec613655f1d929c3c25e819422a071c8ecb79d0f227383a23af74c59c