This commit is contained in:
parent
aa2ff7b2f0
commit
2f3113f55d
11742 changed files with 1223940 additions and 0 deletions
|
|
@ -0,0 +1,24 @@
|
|||
We demonstrate the leaking of the display of internal processes when running
|
||||
cram tests.
|
||||
|
||||
First we make a cram test:
|
||||
|
||||
$ cat > dune-project << EOF
|
||||
> (lang dune 3.7)
|
||||
> EOF
|
||||
|
||||
$ cat > mytest.t << EOF
|
||||
> $ echo A
|
||||
> B
|
||||
> EOF
|
||||
|
||||
We need to avoid the special treatment of the test when INSIDE_DUNE is set:
|
||||
$ unset INSIDE_DUNE
|
||||
|
||||
We do not observe the leaking of the display of internal processes when running
|
||||
dune build. Note that we scrub the actual reported error due to the diff tool
|
||||
being bogus.
|
||||
$ bash -c 'set -o pipefail; dune build --always-show-command-line --root=. --diff-command="exit 1; echo" --display=short @runtest 2>&1 | grep -v "(cd"'
|
||||
File "mytest.t", line 1, characters 0-0:
|
||||
Command exited with code 1.
|
||||
[1]
|
||||
Loading…
Add table
Add a link
Reference in a new issue