>I might be missing something, but I get that behavior in my automatic
>builds by calling 'make check VERBOSE=1'.
This does not appear to have any effect when using the TAP framework.
So it seems. From grepping the installed automake, I see VERBOSE used
in exactly one line of
On Sat, 29 Sep 2018, Karl Berry wrote:
I might be missing something, but I get that behavior in my automatic
builds by calling 'make check VERBOSE=1'.
Yes! Thank you!!
This does not appear to have any effect when using the TAP framework.
Bob
--
Bob Friesenhahn
I might be missing something, but I get that behavior in my automatic
builds by calling 'make check VERBOSE=1'.
Yes! Thank you!!
Hi Karl,
On 9/13/2018 7:53 AM, Karl Berry wrote:
After make check runs, if there were any failures, I'm wishing for a way
to have automake to automatically show the relevant test-suite.log.
I might be missing something, but I get that behavior in my automatic
builds by calling 'make check
[adding autoconf, as this also affects testsuite.log generated by
projects using autotest instead of automake's built-in support]
On 9/21/18 12:37 PM, Bob Proulx wrote:
Bob Friesenhahn wrote:
Karl Berry wrote:
However, this seems like it would be fairly commonly useful and easy
enough to do
Bob Friesenhahn wrote:
> Karl Berry wrote:
> > However, this seems like it would be fairly commonly useful and easy
> > enough to do in the canonical test-driver script. So, any chance of
> > adding it as a standard feature? Any reasonable way of enabling it would
> > be fine, e.g., a flag that
On Wed, 12 Sep 2018, Karl Berry wrote:
However, this seems like it would be fairly commonly useful and easy
enough to do in the canonical test-driver script. So, any chance of
adding it as a standard feature? Any reasonable way of enabling it would
be fine, e.g., a flag that can be added to
After make check runs, if there were any failures, I'm wishing for a way
to have automake to automatically show the relevant test-suite.log.
The post at https://stackoverflow.com/questions/20961959 suggests that
the only way to do this is to modify the test-driver script. Is that correct?
There
