1dune-runtest(1) Dune Manual dune-runtest(1)
2
6 dune-runtest - Run tests.
7
9 dune runtest [OPTION]... [DIR]...
10
12 This is a short-hand for calling:
13 dune build @runtest
15
17 -f, --force
18 Force actions associated to aliases to be re-executed even if their
19 dependencies haven't changed.
20 --help[=FMT] (default=auto)
22 Show this help in format FMT. The value FMT must be one of `auto',
23 `pager', `groff' or `plain'. With `auto', the format is `pager` or
24 `plain' whenever the TERM env var is `dumb' or undefined.
25 --version
27 Show version information.
28
30 These options are common to all commands.
31 --auto-promote
33 Automatically promote files. This is similar to running dune
34 promote after the build.
35 --build-dir=FILE (absent DUNE_BUILD_DIR env)
37 Specified build directory. _build if unspecified
38 --config-file=FILE
40 Load this configuration file instead of the default one.
41 --debug-backtraces
43 Always print exception backtraces.
44 --debug-dependency-path
46 In case of error, print the dependency path from the targets on the
47 command line to the rule that failed.
48 --debug-findlib
50 Debug the findlib sub-system.
51 --default-target=TARGET
53 Set the default target that when none is specified to dune build.
54 It defaults to @@default.
55 --dev
57 Same as --profile dev
58 --diff-command=VAL
60 Shell command to use to diff files
61 --display=MODE
63 Control the display mode of Dune. See dune-config(5) for more
64 details.
65 --ignore-promoted-rules
67 Ignore rules with (mode promote)
68 -j JOBS
70 Run no more than JOBS commands simultaneously.
71 --no-buffer
73 Do not buffer the output of commands executed by dune. By default
74 dune buffers the output of subcommands, in order to prevent
75 interleaving when multiple commands are executed in parallel.
76 However, this can be an issue when debugging long running tests.
77 With --no-buffer, commands have direct access to the terminal. Note
78 that as a result their output won't be captured in the log file.
79 You should use this option in conjunction with -j 1, to avoid
80 interleaving. Additionally you should use --verbose as well, to
81 make sure that commands are printed before they are being executed.
82 --no-config
84 Do not load the configuration file
85 --only-packages=PACKAGES
87 Ignore stanzas referring to a package that is not in PACKAGES.
88 PACKAGES is a comma-separated list of package names. Note that this
89 has the same effect as deleting the relevant stanzas from jbuild
90 files. It is mostly meant for releases. During development, it is
91 likely that what you want instead is to build a particular
92 <package>.install target.
93 -p PACKAGES, --for-release-of-packages=PACKAGES
95 Shorthand for --root . --only-packages PACKAGE --promote ignore
96 --no-config --profile release. You must use this option in your
97 <package>.opam files, in order to build only what's necessary when
98 your project contains multiple packages as well as getting
99 reproducible builds.
100 --profile=VAL
102 Select the build profile, for instance dev or release. The default
103 is dev.
104 --root=DIR
106 Use this directory as workspace root instead of guessing it. Note
107 that this option doesn't change the interpretation of targets given
108 on the command line. It is only intended for scripts.
109 --verbose
111 Same as --display verbose
112 --workspace=FILE
114 Use this specific workspace file instead of looking it up.
115 -x VAL
117 Cross-compile using this toolchain.
118
120 Use `dune COMMAND --help' for help on a single command.
121
123 These environment variables affect the execution of runtest:
124 DUNE_BUILD_DIR
126 Specified build directory. _build if unspecified
127
129 Check bug reports at https://github.com/ocaml/dune/issues
130Dune 11VERSION11 dune-runtest(1)