From f7665858828b3b936e3d8375efd69f3d7b7ff29d Mon Sep 17 00:00:00 2001 From: "Mark C. Miller" Date: Wed, 27 Jan 2021 09:08:27 -0800 Subject: Doc default behavior of install tests (#21309) Co-authored-by: Tamara Dahlgren <35777542+tldahlgren@users.noreply.github.com> --- lib/spack/docs/packaging_guide.rst | 7 +++++-- 1 file changed, 5 insertions(+), 2 deletions(-) (limited to 'lib') diff --git a/lib/spack/docs/packaging_guide.rst b/lib/spack/docs/packaging_guide.rst index 1d25dda2fd..c989a48f92 100644 --- a/lib/spack/docs/packaging_guide.rst +++ b/lib/spack/docs/packaging_guide.rst @@ -4016,8 +4016,11 @@ the package being tested when ``installed`` is ``True``. The executable runs in ``work_dir``, when specified, using the provided ``options``. The return code is checked against the ``status`` argument, which can be an integer or list of integers representing status codes -corresponding to successful execution. Spack also checks that every string -in ``expected`` is a regex matching part of the output from the test run. +corresponding to successful execution (e.g. ``status=[0,3,7]``). +Spack also checks that every string in ``expected`` is a regex matching +part of the output from the test run (e.g. +``expected=['completed successfully', 'converged in']``). Default behavior +is to behave as though ``status=[0]`` and ``expected=[]`` are specified. Output from the test is written to its log file. The ``purpose`` argument serves as the heading in text logs to highlight the start of each test part. -- cgit v1.2.3-60-g2f50