Build:
- 0
2026-10-21 16:54.54: New job: build batsat.0.7 (472956956b02) 2026-10-21 16:54.54: Waiting for resource in pool day11-builds 2026-10-21 16:55.29: Got resource from pool day11-builds 2026-10-21 16:55.29: [profile odoc-master-mini] build batsat.0.7 2026-10-21 16:55.29: build batsat.0.7 (472956956b02) === DEPENDENCIES (7 transitive) === base-threads.base ca51096a9c5b base-unix.base 88a83b7ed333 conf-rust-2018.1 f79f120b7d35 dune.3.24.2 354f182a4824 ocaml.4.14.4 2cc549d6f8d5 ocaml-base-compiler.4.14.4 ecbd009faad9 ocaml-config.2 c0047cbf7f6a === STDOUT === Processing: [default: loading data] [batsat.0.7: dl] [batsat.0.7: extract] -> retrieved batsat.0.7 (https://opam.ocaml.org/cache) [batsat: ./build_rust.sh] + /home/opam/.opam/default/.opam-switch/build/batsat.0.7/./build_rust.sh (CWD=/home/opam/.opam/default/.opam-switch/build/batsat.0.7) - Compiling proc-macro2 v1.0.32 - Compiling unicode-xid v0.2.2 - Compiling cc v1.0.72 - Compiling syn v1.0.81 - Compiling ocaml-sys v0.22.0 - Compiling chlorine v1.0.10 - Compiling ocaml-interop v0.8.7 - Compiling static_assertions v1.1.0 - Compiling bit-vec v0.5.1 - Compiling batsat v0.5.0 - Compiling ocaml-boxroot-sys v0.2.0 - Compiling quote v1.0.10 - Compiling synstructure v0.12.6 - Compiling ocaml-derive v0.22.0 - Compiling ocaml v0.22.2 - Compiling batsat-stubs v0.1.0 (/home/opam/.opam/default/.opam-switch/build/batsat.0.7) - warning: unexpected `cfg` condition value: `no-std` - --> src/lib.rs:95:1 - | - 95 | #[ocaml::func] - | ^^^^^^^^^^^^^^ - | - = note: no expected values for `feature` - = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate - = help: try referring to `ocaml::body` crate for guidance on how handle this unexpected cfg - = help: the macro `ocaml::body` may come from an old version of the `ocaml` crate, try updating your dependency with `cargo update -p ocaml` - = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration - = note: `#[warn(unexpected_cfgs)]` on by default - = note: this warning originates in the macro `ocaml::body` which comes from the expansion of the attribute macro `ocaml::func` (in Nightly builds, run with -Z macro-backtrace for more info) - - warning: unexpected `cfg` condition value: `no-std` - --> src/lib.rs:101:1 - | - 101 | #[ocaml::func] - | ^^^^^^^^^^^^^^ - | - = note: no expected values for `feature` - = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate - = help: try referring to `ocaml::body` crate for guidance on how handle this unexpected cfg - = help: the macro `ocaml::body` may come from an old version of the `ocaml` crate, try updating your dependency with `cargo update -p ocaml` - = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration - = note: this warning originates in the macro `ocaml::body` which comes from the expansion of the attribute macro `ocaml::func` (in Nightly builds, run with -Z macro-backtrace for more info) - - warning: unexpected `cfg` condition value: `no-std` - --> src/lib.rs:107:1 - | - 107 | #[ocaml::func] - | ^^^^^^^^^^^^^^ - | - = note: no expected values for `feature` - = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate - = help: try referring to `ocaml::body` crate for guidance on how handle this unexpected cfg - = help: the macro `ocaml::body` may come from an old version of the `ocaml` crate, try updating your dependency with `cargo update -p ocaml` - = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration - = note: this warning originates in the macro `ocaml::body` which comes from the expansion of the attribute macro `ocaml::func` (in Nightly builds, run with -Z macro-backtrace for more info) - - warning: unexpected `cfg` condition value: `no-std` - --> src/lib.rs:127:1 - | - 127 | #[ocaml::func] - | ^^^^^^^^^^^^^^ - | - = note: no expected values for `feature` - = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate - = help: try referring to `ocaml::body` crate for guidance on how handle this unexpected cfg - = help: the macro `ocaml::body` may come from an old version of the `ocaml` crate, try updating your dependency with `cargo update -p ocaml` - = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration - = note: this warning originates in the macro `ocaml::body` which comes from the expansion of the attribute macro `ocaml::func` (in Nightly builds, run with -Z macro-backtrace for more info) - - warning: unexpected `cfg` condition value: `no-std` - --> src/lib.rs:135:1 - | - 135 | #[ocaml::func] - | ^^^^^^^^^^^^^^ - | - = note: no expected values for `feature` - = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate - = help: try referring to `ocaml::body` crate for guidance on how handle this unexpected cfg - = help: the macro `ocaml::body` may come from an old version of the `ocaml` crate, try updating your dependency with `cargo update -p ocaml` - = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration - = note: this warning originates in the macro `ocaml::body` which comes from the expansion of the attribute macro `ocaml::func` (in Nightly builds, run with -Z macro-backtrace for more info) - - warning: unexpected `cfg` condition value: `no-std` - --> src/lib.rs:152:1 - | - 152 | #[ocaml::func] - | ^^^^^^^^^^^^^^ - | - = note: no expected values for `feature` - = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate - = help: try referring to `ocaml::body` crate for guidance on how handle this unexpected cfg - = help: the macro `ocaml::body` may come from an old version of the `ocaml` crate, try updating your dependency with `cargo update -p ocaml` - = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration - = note: this warning originates in the macro `ocaml::body` which comes from the expansion of the attribute macro `ocaml::func` (in Nightly builds, run with -Z macro-backtrace for more info) - - warning: unexpected `cfg` condition value: `no-std` - --> src/lib.rs:164:1 - | - 164 | #[ocaml::func] - | ^^^^^^^^^^^^^^ - | - = note: no expected values for `feature` - = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate - = help: try referring to `ocaml::body` crate for guidance on how handle this unexpected cfg - = help: the macro `ocaml::body` may come from an old version of the `ocaml` crate, try updating your dependency with `cargo update -p ocaml` - = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration - = note: this warning originates in the macro `ocaml::body` which comes from the expansion of the attribute macro `ocaml::func` (in Nightly builds, run with -Z macro-backtrace for more info) - - warning: unexpected `cfg` condition value: `no-std` - --> src/lib.rs:177:1 - | - 177 | #[ocaml::func] - | ^^^^^^^^^^^^^^ - | - = note: no expected values for `feature` - = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate - = help: try referring to `ocaml::body` crate for guidance on how handle this unexpected cfg - = help: the macro `ocaml::body` may come from an old version of the `ocaml` crate, try updating your dependency with `cargo update -p ocaml` - = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration - = note: this warning originates in the macro `ocaml::body` which comes from the expansion of the attribute macro `ocaml::func` (in Nightly builds, run with -Z macro-backtrace for more info) - - warning: unexpected `cfg` condition value: `no-std` - --> src/lib.rs:192:1 - | - 192 | #[ocaml::func] - | ^^^^^^^^^^^^^^ - | - = note: no expected values for `feature` - = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate - = help: try referring to `ocaml::body` crate for guidance on how handle this unexpected cfg - = help: the macro `ocaml::body` may come from an old version of the `ocaml` crate, try updating your dependency with `cargo update -p ocaml` - = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration - = note: this warning originates in the macro `ocaml::body` which comes from the expansion of the attribute macro `ocaml::func` (in Nightly builds, run with -Z macro-backtrace for more info) - - warning: unexpected `cfg` condition value: `no-std` - --> src/lib.rs:205:1 - | - 205 | #[ocaml::func] - | ^^^^^^^^^^^^^^ - | - = note: no expected values for `feature` - = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate - = help: try referring to `ocaml::body` crate for guidance on how handle this unexpected cfg - = help: the macro `ocaml::body` may come from an old version of the `ocaml` crate, try updating your dependency with `cargo update -p ocaml` - = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration - = note: this warning originates in the macro `ocaml::body` which comes from the expansion of the attribute macro `ocaml::func` (in Nightly builds, run with -Z macro-backtrace for more info) - - warning: unexpected `cfg` condition value: `no-std` - --> src/lib.rs:211:1 - | - 211 | #[ocaml::func] - | ^^^^^^^^^^^^^^ - | - = note: no expected values for `feature` - = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate - = help: try referring to `ocaml::body` crate for guidance on how handle this unexpected cfg - = help: the macro `ocaml::body` may come from an old version of the `ocaml` crate, try updating your dependency with `cargo update -p ocaml` - = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration - = note: this warning originates in the macro `ocaml::body` which comes from the expansion of the attribute macro `ocaml::func` (in Nightly builds, run with -Z macro-backtrace for more info) - - warning: unexpected `cfg` condition value: `no-std` - --> src/lib.rs:217:1 - | - 217 | #[ocaml::func] - | ^^^^^^^^^^^^^^ - | - = note: no expected values for `feature` - = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate - = help: try referring to `ocaml::body` crate for guidance on how handle this unexpected cfg - = help: the macro `ocaml::body` may come from an old version of the `ocaml` crate, try updating your dependency with `cargo update -p ocaml` - = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration - = note: this warning originates in the macro `ocaml::body` which comes from the expansion of the attribute macro `ocaml::func` (in Nightly builds, run with -Z macro-backtrace for more info) - - warning: unexpected `cfg` condition value: `no-std` - --> src/lib.rs:223:1 - | - 223 | #[ocaml::func] - | ^^^^^^^^^^^^^^ - | - = note: no expected values for `feature` - = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate - = help: try referring to `ocaml::body` crate for guidance on how handle this unexpected cfg - = help: the macro `ocaml::body` may come from an old version of the `ocaml` crate, try updating your dependency with `cargo update -p ocaml` - = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration - = note: this warning originates in the macro `ocaml::body` which comes from the expansion of the attribute macro `ocaml::func` (in Nightly builds, run with -Z macro-backtrace for more info) - - warning: unexpected `cfg` condition value: `no-std` - --> src/lib.rs:229:1 - | - 229 | #[ocaml::func] - | ^^^^^^^^^^^^^^ - | - = note: no expected values for `feature` - = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate - = help: try referring to `ocaml::body` crate for guidance on how handle this unexpected cfg - = help: the macro `ocaml::body` may come from an old version of the `ocaml` crate, try updating your dependency with `cargo update -p ocaml` - = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration - = note: this warning originates in the macro `ocaml::body` which comes from the expansion of the attribute macro `ocaml::func` (in Nightly builds, run with -Z macro-backtrace for more info) - - warning: unexpected `cfg` condition value: `no-std` - --> src/lib.rs:244:1 - | - 244 | #[ocaml::func] - | ^^^^^^^^^^^^^^ - | - = note: no expected values for `feature` - = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate - = help: try referring to `ocaml::body` crate for guidance on how handle this unexpected cfg - = help: the macro `ocaml::body` may come from an old version of the `ocaml` crate, try updating your dependency with `cargo update -p ocaml` - = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration - = note: this warning originates in the macro `ocaml::body` which comes from the expansion of the attribute macro `ocaml::func` (in Nightly builds, run with -Z macro-backtrace for more info) - - warning: unexpected `cfg` condition value: `no-std` - --> src/lib.rs:250:1 - | - 250 | #[ocaml::func] - | ^^^^^^^^^^^^^^ - | - = note: no expected values for `feature` - = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate - = help: try referring to `ocaml::body` crate for guidance on how handle this unexpected cfg - = help: the macro `ocaml::body` may come from an old version of the `ocaml` crate, try updating your dependency with `cargo update -p ocaml` - = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration - = note: this warning originates in the macro `ocaml::body` which comes from the expansion of the attribute macro `ocaml::func` (in Nightly builds, run with -Z macro-backtrace for more info) - - warning: attribute should be applied to an `extern` block with non-Rust ABI - --> src/lib.rs:1:1 - | - 1 | #[link(name = "batsat")] - | ^^^^^^^^^^^^^^^^^^^^^^^^ - 2 | use ocaml::Pointer; - | ------------------- not an `extern` block - | - = warning: this was previously accepted by the compiler but is being phased out; it will become a hard error in a future release! - = note: `#[warn(unused_attributes)]` on by default - - warning: `batsat-stubs` (lib) generated 17 warnings - Finished `release` profile [optimized + debuginfo] target(s) in 26.83s [batsat: dune build] + /home/opam/.opam/default/bin/dune "build" "-p" "batsat" "-j" "39" (CWD=/home/opam/.opam/default/.opam-switch/build/batsat.0.7) -> compiled batsat.0.7 -> installed batsat.0.7 === STDERR === 2026-10-21 16:56.14: OK: build batsat.0.7 (runc: 29.7s, disk: 21KB) 2026-10-21 16:56.14: Job succeeded