1dune-runtest(1)                   Dune Manual                  dune-runtest(1)
2
3
4

NAME

6       dune-runtest - Run tests.
7

SYNOPSIS

9       dune runtest [OPTION]... [DIR]...
10

DESCRIPTION

12       This is a short-hand for calling:
13
14         dune build @runtest
15

OPTIONS

17       --build-info
18           Show build information.
19
20       -f, --force
21           Force actions associated to aliases to be re-executed even if their
22           dependencies haven't changed.
23
24       --help[=FMT] (default=auto)
25           Show this help in format FMT. The value FMT must be one of `auto',
26           `pager', `groff' or `plain'. With `auto', the format is `pager` or
27           `plain' whenever the TERM env var is `dumb' or undefined.
28
29       --version
30           Show version information.
31
32       -w, --watch
33           Instead of terminating build after completion, wait continuously
34           for file changes.
35

COMMON OPTIONS

37       These options are common to all commands.
38
39       --always-show-command-line
40           Always show the full command lines of programs executed by dune
41
42       --auto-promote
43           Automatically promote files. This is similar to running dune
44           promote after the build.
45
46       --build-dir=FILE (absent DUNE_BUILD_DIR env)
47           Specified build directory. _build if unspecified
48
49       --config-file=FILE
50           Load this configuration file instead of the default one.
51
52       --debug-backtraces
53           Always print exception backtraces.
54
55       --debug-dependency-path
56           In case of error, print the dependency path from the targets on the
57           command line to the rule that failed.
58
59       --debug-findlib
60           Debug the findlib sub-system.
61
62       --default-target=TARGET (absent=@@default)
63           Set the default target that when none is specified to dune build.
64
65       --dev
66           Same as --profile dev
67
68       --diff-command=VAL
69           Shell command to use to diff files. Use - to disable printing the
70           diff.
71
72       --display=MODE
73           Control the display mode of Dune. See dune-config(5) for more
74           details.
75
76       --ignore-promoted-rules
77           Ignore rules with (mode promote), except ones with (only ...). The
78           variable %{ignoring_promoted_rules} in dune files reflects whether
79           this option was passed or not.
80
81       -j JOBS
82           Run no more than JOBS commands simultaneously.
83
84       --no-buffer
85           Do not buffer the output of commands executed by dune. By default
86           dune buffers the output of subcommands, in order to prevent
87           interleaving when multiple commands are executed in parallel.
88           However, this can be an issue when debugging long running tests.
89           With --no-buffer, commands have direct access to the terminal. Note
90           that as a result their output won't be captured in the log file.
91           You should use this option in conjunction with -j 1, to avoid
92           interleaving. Additionally you should use --verbose as well, to
93           make sure that commands are printed before they are being executed.
94
95       --no-config
96           Do not load the configuration file
97
98       --no-print-directory
99           Suppress "Entering directory" messages
100
101       --only-packages=PACKAGES
102           Ignore stanzas referring to a package that is not in PACKAGES.
103           PACKAGES is a comma-separated list of package names. Note that this
104           has the same effect as deleting the relevant stanzas from jbuild
105           files. It is mostly meant for releases. During development, it is
106           likely that what you want instead is to build a particular
107           <package>.install target.
108
109       -p PACKAGES, --for-release-of-packages=PACKAGES
110           Shorthand for --root . --only-packages PACKAGE
111           --ignore-promoted-rules --no-config --profile release. You must use
112           this option in your <package>.opam files, in order to build only
113           what's necessary when your project contains multiple packages as
114           well as getting reproducible builds.
115
116       --profile=VAL (absent DUNE_PROFILE env)
117           Select the build profile, for instance dev or release. The default
118           is dev.
119
120       --root=DIR
121           Use this directory as workspace root instead of guessing it. Note
122           that this option doesn't change the interpretation of targets given
123           on the command line. It is only intended for scripts.
124
125       --store-orig-source-dir (absent DUNE_STORE_ORIG_SOURCE_DIR env)
126           Store original source location in dune-package metadata
127
128       --trace-file=FILE
129           Output trace data in catapult format (compatible with
130           chrome://tracing)
131
132       --verbose
133           Same as --display verbose
134
135       --workspace=FILE (absent DUNE_WORKSPACE env)
136           Use this specific workspace file instead of looking it up.
137
138       -x VAL
139           Cross-compile using this toolchain.
140

MORE HELP

142       Use `dune COMMAND --help' for help on a single command.
143

ENVIRONMENT

145       These environment variables affect the execution of runtest:
146
147       DUNE_BUILD_DIR
148           Specified build directory. _build if unspecified
149
150       DUNE_PROFILE
151           Build profile. dev if unspecified or release if -p is set.
152
153       DUNE_STORE_ORIG_SOURCE_DIR
154           Store original source location in dune-package metadata
155
156       DUNE_WORKSPACE
157           Use this specific workspace file instead of looking it up.
158

BUGS

160       Check bug reports at https://github.com/ocaml/dune/issues
161
162
163
164Dune n/a                                                       dune-runtest(1)