Re: How do you set VERBOSE for parallel testin

2015-05-15 Thread Andrew W. Nosenko
On Fri, May 15, 2015 at 6:15 AM, Eric Blake ebl...@redhat.com wrote: On 05/14/2015 08:29 PM, Peter Johansson wrote: On 05/15/2015 10:36 AM, Arthur Schwarz wrote: And, if I guess correctly, the user can write make check TESTSUITEFLAGS=-jN I've never seen

Re: How do you set VERBOSE for parallel testin

2015-05-14 Thread Nick Bowler
On 2015-05-13 13:18 -0700, Arthur Schwarz wrote: There are 3 normal ways a make variable can be set (this is not the complete picture but it will do): (1) In the environment (FOO=bar make) (2) In the Makefile (FOO=bar in the Makefile) (3) on the make command line (make FOO=bar)

RE: How do you set VERBOSE for parallel testin

2015-05-14 Thread Arthur Schwarz
And as a simple question, why are you using make -j8? Shouldn't this be part of the automake generated test code? The short answer is because I wanna use 8 cpus. There is no sensible way Automake can know how many cpus I wanna use. $ make check TESTSUITEFLAGS=-j8 I just searched the

Re: How do you set VERBOSE for parallel testin

2015-05-14 Thread Peter Johansson
On 05/15/2015 12:24 AM, Arthur Schwarz wrote: And as a simple question, why are you using make -j8? Shouldn't this be part of the automake generated test code? The short answer is because I wanna use 8 cpus. There is no sensible way Automake can know how many cpus I wanna use. $ make check

RE: How do you set VERBOSE for parallel testin

2015-05-14 Thread Arthur Schwarz
The short answer is because I wanna use 8 cpus. There is no sensible way Automake can know how many cpus I wanna use. Just a some idle speculation, Automake knows two things at this point, that the user wants to run a Parallel Test Harness and the Total number of test

Re: How do you set VERBOSE for parallel testin

2015-05-14 Thread Peter Johansson
On 05/15/2015 10:36 AM, Arthur Schwarz wrote: And, if I guess correctly, the user can write make check TESTSUITEFLAGS=-jN I've never seen TESTSUITEFLAG before, so I don't know. As a nit-noy, don't you mean processor and not cpu? And

Re: How do you set VERBOSE for parallel testin

2015-05-14 Thread Eric Blake
On 05/14/2015 08:29 PM, Peter Johansson wrote: On 05/15/2015 10:36 AM, Arthur Schwarz wrote: And, if I guess correctly, the user can write make check TESTSUITEFLAGS=-jN I've never seen TESTSUITEFLAG before, so I don't know. TESTSUITEFLAGS is the suggested variable

Re: How do you set VERBOSE for parallel testin

2015-05-14 Thread Andrew W. Nosenko
On Thu, May 14, 2015 at 2:31 AM, Peter Johansson troj...@gmail.com wrote: On 05/14/2015 01:20 AM, Arthur Schwarz wrote: And as a simple question, why are you using make -j8? Shouldn't this be part of the automake generated test code? The short answer is because I wanna use 8 cpus. There

RE: How do you set VERBOSE for parallel testin

2015-05-13 Thread Arthur Schwarz
There are 3 normal ways a make variable can be set (this is not the complete picture but it will do): (1) In the environment (FOO=bar make) (2) In the Makefile (FOO=bar in the Makefile) (3) on the make command line (make FOO=bar) Before I go out on a limb and say something I'll regret,

RE: How do you set VERBOSE for parallel testin

2015-05-13 Thread Arthur Schwarz
(3) on the make command line (make FOO=bar) Sorry to be a pest on this but which (or both) formats are correct for a test: make check FOO=bar or make FOO=bar check Ditto for recheck and other make options.

Re: How do you set VERBOSE for parallel testin

2015-05-13 Thread Peter Johansson
On 05/14/2015 01:20 AM, Arthur Schwarz wrote: My question is is this the only way to use VERBOSE? The Automake Manual seems to say that VERBOSE is a variable, not a make argument. And, as a variable, if the user (you) can change it's value then the appropriate way to do it is either: env

RE: How do you set VERBOSE for parallel testin

2015-05-13 Thread Arthur Schwarz
Usually I run my tests with something like this: make check -j8 VERBOSE=1 Thanks Peter. My question is is this the only way to use VERBOSE? The Automake Manual seems to say that VERBOSE is a variable, not a make argument. And, as a variable, if the user (you) can change it's value then the

Re: How do you set VERBOSE for parallel testin

2015-05-13 Thread Roman Neuhauser
# aschwarz1...@att.net / 2015-05-13 08:20:19 -0700: Usually I run my tests with something like this: make check -j8 VERBOSE=1 Thanks Peter. My question is is this the only way to use VERBOSE? The Automake Manual seems to say that VERBOSE is a variable, not a make argument. And, as a

Re: How do you set VERBOSE for parallel testin

2015-05-13 Thread Nick Bowler
On 2015-05-13 08:20 -0700, Arthur Schwarz wrote: Usually I run my tests with something like this: make check -j8 VERBOSE=1 Thanks Peter. My question is is this the only way to use VERBOSE? The Automake Manual seems to say that VERBOSE is a variable, not a make argument. And, as a

Re: How do you set VERBOSE for parallel testin

2015-05-13 Thread Peter Johansson
On 05/13/2015 08:42 AM, Arthur Schwarz wrote: Yes, this is expected. test-suite.log is created no matter what, but the rules associated with creating it fail if the log contains any failure reports, so that make will quit running and let you investigate those failures. If I understand this

RE: How do you set VERBOSE for parallel testin

2015-05-12 Thread Arthur Schwarz
If any test causes a FAIL, XPASS, or ERROR condition, then 'make check' will likewise fail. The output from make is telling you that your testsuite caught failures that should not be present if the testsuite were passing. My issue is that the output indicates that the rule for

RE: How do you set VERBOSE for parallel testin

2015-05-08 Thread Arthur Schwarz
-Original Message- From: Eric Blake [mailto:ebl...@redhat.com] Sent: Thursday, May 07, 2015 4:02 PM To: Arthur Schwarz; automake@gnu.org Subject: Re: How do you set VERBOSE for parallel testin On 05/07/2015 03:42 PM, Arthur Schwarz wrote: I'm trying to set VERBOSE

RE: How do you set VERBOSE for parallel testin

2015-05-08 Thread Arthur Schwarz
On 05/08/2015 04:55 PM, Arthur Schwarz wrote: I just checked the latest iteration of my output listing (VERBOSE = 1) and saw the rule for Makefile:478 showing test-suite.log failed. Don't know why. If any test causes a FAIL, XPASS, or ERROR condition, then 'make check' will

Re: How do you set VERBOSE for parallel testin

2015-05-08 Thread Eric Blake
On 05/08/2015 05:13 PM, Arthur Schwarz wrote: On 05/08/2015 04:55 PM, Arthur Schwarz wrote: I just checked the latest iteration of my output listing (VERBOSE = 1) and saw the rule for Makefile:478 showing test-suite.log failed. Don't know why. If any test causes a FAIL, XPASS, or ERROR

RE: How do you set VERBOSE for parallel testin

2015-05-08 Thread Arthur Schwarz
I just checked the latest iteration of my output listing (VERBOSE = 1) and saw the rule for Makefile:478 showing test-suite.log failed. Don't know why. The output listing is below and the Makefile.am is included in an attachment. Heck, I don't know what I'm doing. If anyone can explain what I

Re: How do you set VERBOSE for parallel testin

2015-05-08 Thread Eric Blake
On 05/08/2015 04:55 PM, Arthur Schwarz wrote: I just checked the latest iteration of my output listing (VERBOSE = 1) and saw the rule for Makefile:478 showing test-suite.log failed. Don't know why. If any test causes a FAIL, XPASS, or ERROR condition, then 'make check' will likewise fail.

Re: How do you set VERBOSE for parallel testin

2015-05-07 Thread Eric Blake
On 05/07/2015 03:42 PM, Arthur Schwarz wrote: I'm trying to set VERBOSE in a parallel test setup and it doesn't seem to work. I've used: VERBOSE = yesand VERBOSE = 1 Where were you making that setting, in Makefile.am? But I get the normal output listing. The Automake manual (Section

How do you set VERBOSE for parallel testin

2015-05-07 Thread Arthur Schwarz
I'm trying to set VERBOSE in a parallel test setup and it doesn't seem to work. I've used: VERBOSE = yesand VERBOSE = 1 But I get the normal output listing. The Automake manual (Section 15.2.3 Parallel Test Harness) says: The output from failed tests is collected in the test-suite.log file.