This repository was archived by the owner on Aug 4, 2022. It is now read-only.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
In some cases TESTDIR is read-only, so storing an .err file on a test
failure is impossible which makes Cram itself fail.
For example, if Cram is invoked as a part of 'make distcheck', which
deliberately runs a VPATH build with 'srcdir' and all its contents made
read-only, any test failure leads to Cram failing with a Python
traceback in the test log. Having a diff file instead would still be
handy to diagnose the failure.
With the new '-e' / '--no-err-files' option Cram does not try to create
.err files on test failures, but still prints the diff.