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       -f, --force
18           Force actions associated to aliases to be re-executed even if their
19           dependencies haven't changed.
20
21       --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
26       --version
27           Show version information.
28
29       -w, --watch
30           Instead of terminating build after completion, wait continuously
31           for file changes.
32

COMMON OPTIONS

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

MORE HELP

135       Use `dune COMMAND --help' for help on a single command.
136

ENVIRONMENT

138       These environment variables affect the execution of runtest:
139
140       DUNE_BUILD_DIR
141           Specified build directory. _build if unspecified
142
143       DUNE_PROFILE
144           Build profile. dev if unspecified or release if -p is set.
145
146       DUNE_STORE_ORIG_SOURCE_DIR
147           Store original source location in dune-package metadata
148

BUGS

150       Check bug reports at https://github.com/ocaml/dune/issues
151
152
153
154Dune 11VERSION11                                               dune-runtest(1)