Here we test what happens when rocq c --config or --print-version fails in an unexpected way and how dune reacts to this failure. First we create a wrapper around coqc so we can make it fail. It should only fail on --config and --print-version. $ mkdir bin $ cat > bin/rocq <<'EOF' > #!/bin/sh > if [ "$1" = c ] && [ "$2" = --config ] && [ -n "$FAIL_CONFIG" ]; then > echo "rocq c --config has failed for some reason" >&2 > exit 1 > elif [ "$1" = --print-version ] && [ -n "$FAIL_VERSION" ]; then > echo "rocq --print-version has failed for some reason" >&2 > exit 1 > fi > EOF > echo "$(which rocq) \$@" >> bin/rocq > chmod +x bin/rocq $ export PATH=$PWD/bin:$PATH To make sure these are working correctly we test them. These should succeed. $ rocq --print-version > /dev/null $ rocq c --config > /dev/null These should fail. $ FAIL_VERSION=1 \ > rocq --print-version 2> /dev/null [1] $ FAIL_CONFIG=1 \ > rocq c --config 2> /dev/null [1] Now we create a simple project that uses this coqc wrapper, should fail when Corelib cannot be determined $ cat > dune < (rocq.theory > (flags -noinit) > (name foo)) > > (rule > (deps > (env_var FAIL_VERSION) > (env_var FAIL_CONFIG)) > (action > (write-file a.v ""))) > EOF Should fail: first warning that installed theories are being skipped due to the failure, then, as the library requires Corelib, it fails: $ FAIL_CONFIG=1 \ > dune build Warning: Skipping installed theories due to 'rocq c --config' failure: - $TESTCASE_ROOT/bin/rocq c --config failed with exit code 1. Hint: Try running 'rocq c --config' manually to see the error. Couldn't find Rocq Corelib, and the theory does not disable automatic Corelib inclusion with (no_corelib). -> required by _build/default/.foo.theory.d -> required by alias all -> required by alias default [1] Here we build a simple Coq project. Neither a failing --config or --print-version should block this as it doesn't depend on Corelib. $ cat > dune < (rocq.theory > (flags -noinit) > (name foo) > (stdlib no)) > > (rule > (deps > (env_var FAIL_VERSION) > (env_var FAIL_CONFIG)) > (action > (write-file a.v ""))) > EOF Should succeed, warning that installed theories are being skipped due to the failure (c.f. #8958): $ FAIL_CONFIG=1 \ > dune build Warning: Skipping installed theories due to 'rocq c --config' failure: - $TESTCASE_ROOT/bin/rocq c --config failed with exit code 1. Hint: Try running 'rocq c --config' manually to see the error. $ FAIL_VERSION=1 \ > dune build $ dune build Here we query the version of Coq. Due to the expansion of %{coq:_} macros we need coqc --config. A failing --print-version or --config will block this value from being realised. $ cat > dune < (rule > (alias version) > (action > (echo %{rocq:version}))) > EOF Succeeds after PR #10631 $ FAIL_CONFIG=1 \ > dune build @version 9.2 Should fail. $ FAIL_VERSION=1 \ > dune build @version File "dune", line 4, characters 8-23: 4 | (echo %{rocq:version}))) ^^^^^^^^^^^^^^^ Error: Could not expand %{rocq:version} as running rocq failed. $TESTCASE_ROOT/bin/rocq --print-version failed with exit code 1. [1] Here we query the config. A failing --config will block this value from being realised however a failing --print-version will not. $ cat > dune < (rule > (alias config) > (action > (echo %{rocq:rocqlib}))) > EOF Should fail. $ export coqlib="$(rocq c --config | grep COQLIB | sed 's/COQLIB=//')" $ FAIL_CONFIG=1 \ > dune build @config File "dune", line 4, characters 8-23: 4 | (echo %{rocq:rocqlib}))) ^^^^^^^^^^^^^^^ Error: Could not expand %{rocq:rocqlib} as running rocq failed. $TESTCASE_ROOT/bin/rocq c --config failed with exit code 1. [1] Should succeed. $ FAIL_VERSION=1 \ > dune build @config | sed "s,$coqlib,COQLIB," > /dev/null Should succeed. $ dune build @config | sed "s,$coqlib,COQLIB," > /dev/null