-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi,
I have a library that, among other things, has a number of functions
related to event handling with timeouts. In order to get reliable
results, I have to use long timeouts, which add up in the total test
time. Is there a way to have tests run in
On 02/19/2013 02:39 PM, Simon Richter wrote:
Hi,
I have a library that, among other things, has a number of functions
related to event handling with timeouts. In order to get reliable
results, I have to use long timeouts, which add up in the total test
time. Is there a way to have tests run
] docs: parallel-tests is no longer experimental
So don't declare it as such in the documentation.
Reported by Brandon Black:
http://lists.gnu.org/archive/html/automake/2013-01/msg00052.html
* doc/automake.texi: Adjust.
* THANKS: Update.
Signed-off-by: Stefano Lattarini stefano.lattar
On Thu, Oct 11, 2012 at 6:53 AM, Reuben Thomas r...@sc3d.org wrote:
This whole problem is an instance of a more general problem, of which
another example is parallel make: for best performance, it should
probably batch up calls to gcc, for example, so that multiple source
files are compiled by
On 11 October 2012 22:12, Jack Kelly j...@jackkelly.name wrote:
We had a discussion along these lines when refactoring elisp
compilation: in the past it was all done in one big batch. Now it's
done with an emacs invocation per .el file. The result of that
discussion was that while you slow
With the recent work on parallel tests in automake I thought it was
time to give them a spin, so I did, for the zee branch of GNU Zile.
This has about 100 tests, the total wall clock time being around 8s on
my 2.5GHz 4-core Sandy Bridge machine, with the following target:
check-local: $(builddir
That test was checking for automake#7868 parallel-tests and command-line
length limit issue. That bug is still open, and the tests was xfailing.
What concerns us is that the test was also causing an annoying problem.
On Solaris 10, it produced a '.log' file with two overly-long lines (more
than
recipes) a use of the 'xargs' utility.
These issues will likely be tackled by later patches.
* Makefile.am (XFAIL_TESTS): Remove 't/parallel-tests-many.sh'.
* lib/am/clean.am (.am.clean-cmd.f, .am.clean-cmd.d, .am.rm-f,
.am.rm-rf): Moved their definitions …
Move
* lib/am/header-vars.am
will likely be tackled by later patches.
* Makefile.am (XFAIL_TESTS): Remove 't/parallel-tests-many.sh'.
* lib/am/clean.am (.am.clean-cmd.f, .am.clean-cmd.d, .am.rm-f,
.am.rm-rf): Moved their definitions ...
* lib/am/header-vars.am: ... here, because we need to use them ...
* lib/am/parallel-tests.am
* lib/am/check.am: Here. The new implementation is shorter, slightly
more efficient (requiring less forks), less brittle in the face of
signals or unexpected interruptions in the make process, and should
also be easier to merge in the 'ng/master' branch (as of now, due to
the difficulties in
On 07/01/2012 01:29 PM, Stefano Lattarini wrote:
* lib/am/check.am: Here. The new implementation is shorter, slightly
more efficient (requiring less forks), less brittle in the face of
signals or unexpected interruptions in the make process, and should
also be easier to merge in the
* lib/am/check.am: Here. The new implementation is shorter, slightly
more efficient (requiring less forks), less brittle in the face of
signals or unexpected interruptions in the make process, and should
also be easier to merge in the 'ng/master' branch (as of now, due to
the difficulties in
On 07/01/2012 01:29 PM, Stefano Lattarini wrote:
* lib/am/check.am: Here. The new implementation is shorter, slightly
more efficient (requiring less forks), less brittle in the face of
signals or unexpected interruptions in the make process, and should
also be easier to merge in the
* lib/am/check.am: Here. They have distinctly diverged recently, and
the reduction in code duplication obtained keeping their recipes united
is not anymore worth the extra complications.
Signed-off-by: Stefano Lattarini stefano.lattar...@gmail.com
---
lib/am/check.am | 89
* lib/am/check.am: Here. They have distinctly diverged recently, and
the reduction in code duplication obtained keeping their recipes united
is not anymore worth the extra complications.
Signed-off-by: Stefano Lattarini stefano.lattar...@gmail.com
---
Oops, I sent a mangled version of the
, the 'parallel-tests' option is a no-op
(but still explicitly recognized, for backward compatibility), while the
'serial-tests' option is recognized and registered.
* automake.in: Adjust to ensure that the parallel test harness is used by
default; mostly, this amounts at using ! option('serial-tests') where
On 05/15/2012 10:44 PM, Stefano Lattarini wrote:
This will help our transition from 'serial-tests' to 'parallel-tests'
as the default test suite driver enabled by a TESTS assignment in the
input Makefile.am. Note that that change of default will only take
place in master, though.
---
I
1.12 on Ubuntu 12.04 LTS.
The first was the 'lex-clean' issue that was already reported. The
other I couldn't find any report for, so please find test-suite.log
output for the failing test below.
/Simon
FAIL: t/parallel-tests-fork-bomb
[SNIP]
It's a spurious failure due
that was already reported. The
other I couldn't find any report for, so please find test-suite.log
output for the failing test below.
/Simon
FAIL: t/parallel-tests-fork-bomb
[SNIP]
It's a spurious failure due to internationalization/localization. Does
the attached patch fix the problem
report for, so please find test-suite.log
output for the failing test below.
/Simon
FAIL: t/parallel-tests-fork-bomb
[SNIP]
It's a spurious failure due to internationalization/localization. Does
the attached patch fix the problem for you?
Regards,
Stefano
From
I got two self-test failures with automake 1.12 on Ubuntu 12.04 LTS.
The first was the 'lex-clean' issue that was already reported. The
other I couldn't find any report for, so please find test-suite.log
output for the failing test below.
/Simon
FAIL: t/parallel-tests-fork-bomb
After commit v1.12-21-g5eeb366 parallel-tests: optimize global log
creation, the log files copied in the global log are not anymore
separated by a blank line, causing unclear output like this:
FAIL: test1
===
output from test 1
FAIL: test2
===
output from test 2
On 04/30/2012 05:54 PM, Stefano Lattarini wrote:
I will push this to maint in a couple of days if there is no objection.
Stefano Lattarini (4):
coverage: add performance tests on some parallel-tests aspects
parallel-tests: optimize 'recheck' target for speed
parallel-tests: optimize
* NEWS: Document the improved performances of the parallel-tests targets
'check' and 'recheck'. See recent commits:
- v1.12-20-gf5733aa of 2012-04-26,
parallel-tests: optimize 'recheck' target for speed
- v1.12-21-g5eeb366 of 2012-02-26,
parallel-tests: optimize global log creation
I will push this to maint in a couple of days if there is no objection.
Reviews are most welcome.
Regards,
Stefano
-*-*-*-
Stefano Lattarini (3):
coverage: add performance tests on some parallel-tests aspects
parallel-tests: optimize 'recheck' target for speed
parallel-tests: optimize
With this change, the time required to execute the test case
'testsuite-recheck-speed.sh' has dropped as follows:
+ Slow Debian i686 system, 1 core x 1.5 GHz, 768 MB of RAM,
GNU make 3.81:
- 1 run: 6 minutes = 40 seconds
+ Fast Solaris 10 i686 system, 4 cores x 3 GHz, 20 GB of RAM,
* t/testsuite-recheck-speed.sh: New test.
* t/testsuite-summary-speed.sh: Likewise.
* t/list-of-tests.mk: Update.
The new tests are not meant to PASS/FAIL, but rather to help us to
obtain quantitative measurements of the performance improvements
offered by soon-to-appear optimization patches.
With this change, the time required to execute the test case
'testsuite-summary-speed.sh' has dropped as follows:
+ Slow Debian i686 system, 1 core x 1.5 GHz, 768 MB of RAM,
GNU make 3.81:
- 1 run: 4 minutes = 30/40 seconds
+ Fast Solaris 10 i686 system, 4 cores x 3 GHz, 20 GB of
On 04/30/2012 05:54 PM, Stefano Lattarini wrote:
I will push this to maint in a couple of days if there is no objection.
Reviews are most welcome.
Regards,
Stefano
-*-*-*-
Stefano Lattarini (3):
coverage: add performance tests on some parallel-tests aspects
parallel-tests
* lib/am/check.am (am__check_pre): Save some forks, by analyzing more
carefully the value of '$@' to decide how to extract its dirname part,
and whether that should be created as a directory.
Signed-off-by: Stefano Lattarini stefano.lattar...@gmail.com
---
And this trivial optimization could be
* lib/am/check.am ($(TEST_SUITE_LOG)): Be sure to print error messages
on stderr, not on stdout.
Signed-off-by: Stefano Lattarini stefano.lattar...@gmail.com
---
lib/am/check.am |4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/lib/am/check.am b/lib/am/check.am
index
* tests/parallel-tests-many.test: Adjust grepping of make check
and make recheck output to match the new format of the testsuite
summary. Remove redundant 'set -e' call since we are at it.
---
tests/parallel-tests-many.test |8
1 files changed, 4 insertions(+), 4 deletions(-)
diff
On 02/18/2012 11:12 PM, Stefano Lattarini wrote:
On 02/18/2012 02:09 PM, Stefano Lattarini wrote:
[CC:ing bug-autoconf for Yet Another BSD make Bug, in case someone
cares to documenting it ...]
When BSD make is run in parallel mode, it apparently strips any leading
directory component from
: 3115f7a37445fd404b0de300894a790d1ce0cb68.1329570443.git.stefano.lattar...@gmail.com
From: Stefano Lattarini stefano.lattar...@gmail.com
Date: Sat, 18 Feb 2012 13:59:26 +0100
Subject: [PATCH] parallel-tests: fix another BSD parallel make issue
When BSD make is run in parallel mode, it apparently strips any
leading directory
On 02/18/2012 02:09 PM, Stefano Lattarini wrote:
[CC:ing bug-autoconf for Yet Another BSD make Bug, in case someone
cares to documenting it ...]
When BSD make is run in parallel mode, it apparently strips any leading
directory component from the automatic variable '$*' (of course, against
On 01/15/2012 05:15 PM, Stefano Lattarini wrote:
On 01/13/2012 10:46 PM, Stefano Lattarini wrote:
Reference:
http://lists.gnu.org/archive/html/automake/2012-01/msg5.html
Stefano Lattarini (4):
docs: deprecate .log - .html conversion by parallel-tests
check: separate .log - .html
On 01/13/2012 10:46 PM, Stefano Lattarini wrote:
Reference:
http://lists.gnu.org/archive/html/automake/2012-01/msg5.html
Stefano Lattarini (4):
docs: deprecate .log - .html conversion by parallel-tests
check: separate .log - .html conversion from core testsuite harness
recheck
Reference:
http://lists.gnu.org/archive/html/automake/2012-01/msg5.html
Stefano Lattarini (4):
docs: deprecate .log - .html conversion by parallel-tests
check: separate .log - .html conversion from core testsuite harness
recheck: behave better with non-GNU make
recheck: fix
That feature is to be deprecated in the 1.11.x series, and
removed in the 1.12 release.
Reference:
http://lists.gnu.org/archive/html/automake/2012-01/msg5.html
* doc/automake.texi (Simple Tests using parallel-tests): Deprecate
the '.log' - '.html' conversion and the targets 'check-html
On 01/08/2012 07:27 PM, Stefano Lattarini wrote:
Reference:
http://lists.gnu.org/archive/html/automake/2012-01/msg5.html
On 01/05/2012 11:14 PM, Bob Friesenhahn wrote:
On Thu, 5 Jan 2012, Stefano Lattarini wrote:
So, in conclusion, here is my simple proposal:
1. We deprecate the
Lattarini stefano.lattar...@gmail.com
Date: Sun, 8 Jan 2012 19:26:18 +0100
Subject: [PATCH] docs: deprecate .log - .html conversion by parallel-tests
That feature is to be deprecated in the 1.11.x series, and
removed in the 1.12 release.
Reference:
http://lists.gnu.org/archive/html/automake/2012-01
Lattarini stefano.lattar...@gmail.com
Date: Sun, 8 Jan 2012 19:26:18 +0100
Subject: [PATCH] docs: deprecate .log - .html conversion by parallel-tests
That feature is to be deprecated in the 1.11.x series, and
removed in the 1.12 release.
Reference:
http://lists.gnu.org/archive/html/automake/2012-01
On 01/05/12 06:07, Stefano Lattarini wrote:
Which sort of thing exactly? I could find only one place which suffers
of the problem you've pointed out, i.e., the `recheck recheck-html' rules
in lib/am/check.am. Am I missing something?
Sorry, that appears to have been a miscount on my part:
I
2001
Message-Id: e3b0e12400f5fa4220fc0aa79dd0989e56def9c6.1325772813.git.stefano.lattar...@gmail.com
From: Stefano Lattarini stefano.lattar...@gmail.com
Date: Thu, 5 Jan 2012 15:13:30 +0100
Subject: [PATCH] parallel-tests: avoid issue with overly long lines in sed
input
See automake bug#10437
On Thu, 5 Jan 2012, Stefano Lattarini wrote:
So, in conclusion, here is my simple proposal:
1. We deprecate the support for HTML testsuite output in the documentation of
the 1.11.3 release.
2. In the 1.12 release, we remove it from the automake core, providing instead
(in the
...@gmail.com
Date: Wed, 28 Dec 2011 22:37:44 +0100
Subject: [PATCH 1/2] coverage: expose automake bug#7868
Expose the command-line length limit issue that can affect the
Automake-generated parallel-tests harness, especially on systems
where this limit is smaller (e.g., MinGW/MSYS).
Suggestion
...@gmail.com
Date: Wed, 28 Dec 2011 22:37:44 +0100
Subject: [PATCH 1/2] coverage: expose automake bug#7868
Expose the command-line length limit issue that can affect the
Automake-generated parallel-tests harness, especially on systems
where this limit is smaller (e.g., MinGW/MSYS).
Suggestion
On Fri, 30 Dec 2011, Stefano Lattarini wrote:
OK, I hope I've finally managed to partially fix this incredibly annoying bug
-- I say partially because the fix is sadly *for GNU make*. Even more sadly,
the solution is pretty hacky and somewhat brittle. Still, it should cause no
regression
Hi Bob.
On 12/30/2011 05:10 PM, Bob Friesenhahn wrote:
On Fri, 30 Dec 2011, Stefano Lattarini wrote:
OK, I hope I've finally managed to partially fix this incredibly annoying bug
-- I say partially because the fix is sadly *for GNU make*. Even more
sadly,
the solution is pretty hacky and
parallel-tests harness, especially on systems
where this limit is smaller (e.g., MinGW/MSYS).
Suggestion by Bob Friesenhahn.
* tests/parallel-tests-many.test: New test. We have verified that
it actually exposes the bug#7868, as it passes when we opportunely
reduce the number of test cases in $(TESTS
at 05:10:38AM CEST:
I'm applying the following patch to maint to avoid the issue.
Unfortunately, the same technique will not work for recheck and
recheck-html. So no rechecking unless the number of failures is
lower than the command-line length limit allows.
parallel-tests: avoid command-line
parallel-tests harness, especially on systems
where this limit is smaller (e.g., MinGW/MSYS).
Suggestion by Bob Friesenhahn.
* tests/parallel-tests-many.test: New test. We have verified that
it actually exposes the bug#7868, as it passes when we opportunely
reduce the number of test cases in $(TESTS
On Sunday 09 October 2011, Stefano Lattarini wrote:
On Sunday 18 September 2011, Stefano Lattarini wrote:
On Sunday 18 September 2011, Stefano Lattarini wrote:
Severity: serious
The bug is demonstrated by the attached test script.
I hope I'll be able to take a look into it soonish.
On Tuesday 18 October 2011, Stefano Lattarini wrote:
On Tuesday 18 October 2011, Stefano Lattarini wrote:
Reference:
http://debbugs.gnu.org/cgi/bugreport.cgi?bug=8788
[SNIP]
Now, the right fix for the bug is *not* to work around this behaviour
of the Korn shell; rather, we should
On Tuesday 18 October 2011, Stefano Lattarini wrote:
On Tuesday 18 October 2011, Stefano Lattarini wrote:
Reference:
http://debbugs.gnu.org/cgi/bugreport.cgi?bug=8788
[SNIP]
Now, the right fix for the bug is *not* to work around this behaviour
of the Korn shell; rather, we should
Reference:
http://debbugs.gnu.org/cgi/bugreport.cgi?bug=8788
[Adding bug-autoconf in CC]
On Thursday 02 June 2011, Stefano Lattarini wrote:
Hello automakers.
While teststing the `testsuite-work' branch on NetBSD 5, I've encountered
a weird failure in the test `parallel-tests3.test', which
[Dropping bug-autoconf from CC]
[Adding automake-patches to CC]
On Tuesday 18 October 2011, Stefano Lattarini wrote:
Reference:
http://debbugs.gnu.org/cgi/bugreport.cgi?bug=8788
On Thursday 02 June 2011, Stefano Lattarini wrote:
While teststing the `testsuite-work' branch on NetBSD 5,
On Sunday 18 September 2011, Stefano Lattarini wrote:
On Sunday 18 September 2011, Stefano Lattarini wrote:
Severity: serious
The bug is demonstrated by the attached test script.
I hope I'll be able to take a look into it soonish.
The test script has a couple of bugs, which I've now
stefano.lattar...@gmail.com
+
+ parallel-tests: warn on conditional TEST_EXTENSIONS definition
+ Before this change, automake would have still bailed out, but
+ with a confusing error message (about an invalid redefinition
+ of TEST_EXTENSIONS).
+ * automake.in
On Friday 07 October 2011, Stefano Lattarini wrote:
Before this change, automake would have still bailed out, but
with a confusing error message (about an invalid redefinition
of TEST_EXTENSIONS).
* automake.in (handle_tests): Warn explicitly if TEST_EXTENSIONS
has conditional contents.
*
tags 9400 patch
close 9400
thanks
Reference:
http://debbugs.gnu.org/cgi/bugreport.cgi?bug=9400#8
On Saturday 01 October 2011, Stefano Lattarini wrote:
For the moment, I've decided to take the easiest route, documenting the
limitation and correcting the diagnostic. Such restriction could
tags 9400 patch
close 9400
thanks
Reference:
http://debbugs.gnu.org/cgi/bugreport.cgi?bug=9400#8
On Saturday 01 October 2011, Stefano Lattarini wrote:
For the moment, I've decided to take the easiest route, documenting the
limitation and correcting the diagnostic. Such restriction could
/test-extensions.test: Adjust and extend.
+
2011-10-01 Stefano Lattarini stefano.lattar...@gmail.com
parallel-tests: automake error our on invalid TEST_EXTENSIONS
diff --git a/automake.in b/automake.in
index a60bc9f..ef53049 100755
--- a/automake.in
+++ b/automake.in
@@ -213,8 +213,6 @@ my
On Monday 29 August 2011, Stefano Lattarini wrote:
I catched this while working some more on the Automake testsuite:
$ cat Makefile.am
TEST_EXTENSIONS = .t-1
TESTS = foo.t-1
$ cat configure.ac
AC_INIT([foo], [1.0])
AM_INIT_AUTOMAKE([foreign -Wall parallel-tests])
AC_CONFIG_FILES
-tests.am $(top_srcdir)/lib/mkinstalldirs \
+ $(top_srcdir)/lib/test-driver
subdir = tests
ACLOCAL_M4 = $(top_srcdir)/aclocal.m4
am__aclocal_m4_deps = $(top_srcdir)/m4/amversion.m4 \
@@ -296,8 +297,7 @@ EXTRA_DIST = ChangeLog-old gen-parallel-tests instspc-tests.sh \
XFAIL_TESTS = all.test auxdir2
Severity: serious
The bug is demonstrated by the attached test script.
I hope I'll be able to take a look into it soonish.
Regards,
Stefano
test-driver-is-distributed.test
Description: application/shellscript
The branches python-work, java-work and parallel-tests-maint have been
merged into maint and/or master; also, no more work on them is planned
in the short(ish) term. So I've removed them.
Regards,
Stefano
: f15d31661ef94e5d549dbdfb0f60cea1bc17683a.1316371402.git.stefano.lattar...@gmail.com
From: Stefano Lattarini stefano.lattar...@gmail.com
Date: Sun, 18 Sep 2011 20:42:56 +0200
Subject: [PATCH] parallel-tests: expose automake bug#9546
* tests/test-driver-is-distributed.test: New test.
* tests/Makefile.am (TESTS, XFAIL_TESTS): Add
I catched this while working some more on the Automake testsuite:
$ cat Makefile.am
TEST_EXTENSIONS = .t-1
TESTS = foo.t-1
$ cat configure.ac
AC_INIT([foo], [1.0])
AM_INIT_AUTOMAKE([foreign -Wall parallel-tests])
AC_CONFIG_FILES([Makefile])
AC_OUTPUT
$ aclocal
$ autoconf
$ : install
* tests/backcompat5.test (parallel_tests): Define to no, to
prevent the generation of a sibling test script that uses the
'parallel-tests' driver. That would be useless anyway, since
we manually override the contents of configure.in, thus clobbering
the `parallel-tests' option in AM_INIT_AUTOMAKE
-driver |4 ++--
4 files changed, 13 insertions(+), 4 deletions(-)
diff --git a/ChangeLog b/ChangeLog
index bfd156f..3fefbd3 100644
--- a/ChangeLog
+++ b/ChangeLog
@@ -1,5 +1,14 @@
2011-08-17 Stefano Lattarini stefano.lattar...@gmail.com
+ parallel-tests: fix help screen for test driver
+ parallel-tests: work around Solaris XPG4 make segfault
+ Issue exposed by test `posixsubst-tests-p.test', and similar to
+ the problem solved by commit `v1.11-159-ge7aa360'.
+ * lib/am/check.am [%?PARALLEL_TESTS%] (check-TESTS): Trim trailing
+ whitespace from $list
@@
2011-08-07 Stefano Lattarini stefano.lattar...@gmail.com
+ parallel-tests: work around Solaris XPG4 make segfault
+ Issue exposed by test `posixsubst-tests-p.test', and similar to
+ the problem solved by commit `v1.11-159-ge7aa360'.
+ * lib/am/check.am [%?PARALLEL_TESTS
* tests/parallel-tests-extra-programs.test: New test.
* tests/Makefile.am (TESTS): Update.
* doc/automake.texi (Parallel Test Harness): Add a comment
pointing to the new test.
---
ChangeLog|8 ++
doc/automake.texi|1 +
tests
On Wednesday 20 July 2011, Ralf Wildenhues wrote:
* Stefano Lattarini wrote on Wed, Jul 20, 2011 at 10:05:14PM CEST:
Hi Ralf, thanks for the tips.
Rather, 5 minutes of searching the web. But sure, anytime. ;-)
On Tuesday 19 July 2011, Ralf Wildenhues wrote:
Test suite environments:
Hi Ralf, thanks for the tips.
On Tuesday 19 July 2011, Ralf Wildenhues wrote:
* Stefano Lattarini wrote on Tue, Jul 19, 2011 at 11:54:09AM CEST:
Please, this is really important: we need to research the other test
protocols, what they do to be robust here. Don't NIH here, because the
`:test-results:' arguments.
* NEWS: Update.
* tests/trivial-test-driver: Update.
* tests/parallel-tests.test: Likewise.
* tests/parallel-tests-harderror.test: Likewise.
* tests/parallel-tests-no-spurious-summary.test: Likewise.
* tests/test-driver-global-log.test: Likewise.
* tests/test
.
* tests/parallel-tests-no-spurious-summary.test: New test.
* tests/test-driver-end-test-results.test: Likewise.
* tests/Makefile.am (TESTS): Update.
I'm still not sold on this.
I'm surely open to discuss changes to this new log format (which I
admittedly concocted quite in a hurry
* Stefano Lattarini wrote on Tue, Jul 19, 2011 at 11:54:09AM CEST:
Please, this is really important: we need to research the other test
protocols, what they do to be robust here. Don't NIH here, because the
experience we have is not enough to not mess up this. Consider this
research as
as the special :test-result:END directive is seen.
Related changes and enhancements.
* lib/test-driver: Protect the rest of the log after the result
lined with a :test-result:END directive.
* tests/parallel-tests-no-spurious-summary.test: New test.
* tests/test-driver-end-test-results.test: Likewise
-test-driver: Update.
* tests/parallel-tests.test: Likewise.
* tests/parallel-tests-harderror.test: Likewise.
* tests/parallel-tests-no-spurious-summary.test: Likewise.
* tests/test-driver-global-log.test: Likewise.
* tests/test-driver-recheck.test: Likewise.
* tests/test-driver-custom
-driver: Protect the rest of the log after the result
lined with a :test-result:END directive.
* tests/parallel-tests-no-spurious-summary.test: New test.
* tests/test-driver-end-test-results.test: Likewise.
* tests/Makefile.am (TESTS): Update.
---
ChangeLog | 36
-tests-harderror.test: Likewise.
* tests/parallel-tests-no-spurious-summary.test: Likewise.
* tests/test-driver-global-log.test: Likewise.
* tests/test-driver-recheck.test: Likewise.
* tests/test-driver-custom-multitest-recheck.test: Likewise.
* tests/test-driver-custom-multitest-recheck2.test
AutoFoo 7.3
harness: parallel-tests; version: 1; automake: 1.12;
==
# TOTAL: 113
# PASS: 97
...
or to make line-by-line parsing even easier:
@TestSuite - harness: parallel-tests; version: 1; automake: 1.12
On Thursday 07 July 2011, Ralf Wildenhues wrote:
[SNIP longish discussion I'd like to keep for a later date]
You mean want them *even in the test-suite.log*?
Hmm. --color is good enough, if it forces color on stdout, IMVHO.
Point is, it doesn't. It only tells that the colors are to be
On Thu, Jul 07, 2011 at 07:02:58PM +0200, Stefano Lattarini wrote:
On Wednesday 06 July 2011, Ralf Wildenhues wrote:
But tools like autobuild have another requirement: they would like to be
able to detect, as reliably as possible, some statistics based on
whatever output is thrown at them.
`$mgn' and `$brg'.
[%?COLOR%, %!?COLOR%] (am__tty_colors): Use that new variable.
(am__text_box): Delete, is not needed anymore.
($(TEST_SUITE_LOG)): Rewrite associated rules to implement the
new testsuite summary format.
* NEWS: Update.
* tests/check10.test: Don't run with the parallel-tests
* Stefano Lattarini wrote on Wed, Jul 06, 2011 at 02:49:15PM CEST:
On Wednesday 06 July 2011, Ralf Wildenhues wrote:
* Stefano Lattarini wrote on Sun, Jul 03, 2011 at 03:31:22PM CEST:
Prefer a more deterministic, tabular format for the testsuite
summary, always listing the numbers of
On Thursday 30 June 2011, Stefano Lattarini wrote:
I've applied the attached patch to the 'GSoC/experimental/test-results-work'
branch Note that this is not an FYI, since that branch is temporary, and can
thus be amended and modified. Reviews are welcome!
Thanks,
Stefano
And consider
While working on the next patch (which introduces a more rational testsuite
summary report), I have made the `color*.test' tests even stricter (see
attachements); and I think that it would be useful to have these stricter
versions in this earlier change already. I have thus amended the present
On Friday 01 July 2011, Stefano Lattarini wrote:
While working on the next patch (which introduces a more rational testsuite
summary report), I have made the `color*.test' tests even stricter (see
attachements); and I think that it would be useful to have these stricter
versions in this
: Stefano Lattarini stefano.lattar...@gmail.com
Date: Thu, 30 Jun 2011 16:37:19 +0200
Subject: [PATCH] coverage: new test on parallel-tests TESTS runtime overriding
* tests/parallel-tests-cmdline-override.test: New test, check that
we can use indirections when overriding TESTS and TEST_LOGS from
Message-Id: 2df72384ab57d165c7e1da0f88e513171a0035e8.1309445709.git.stefano.lattar...@gmail.com
From: Stefano Lattarini stefano.lattar...@gmail.com
Date: Thu, 30 Jun 2011 14:55:43 +0200
Subject: [PATCH] parallel-tests: new recognized test result 'ERROR'
* lib/am/check.am ($(TEST_SUITE_LOG
* Stefano Lattarini wrote on Thu, Jun 30, 2011 at 04:40:51PM CEST:
I'd like to add this new test case to master. OK?
Sure, note typo below.
This could actually find bugs in older makes, but hey, we'd want to know
about them.
Thanks,
Ralf
Subject: [PATCH] coverage: new test on parallel-tests
can.
Changing semantics requires a NEWS entry. It's actually an
incompatibility, but a very minor one, so it's not a big problem.
Thanks,
Ralf
Subject: [PATCH] parallel-tests: new recognized test result 'ERROR'
* lib/am/check.am ($(TEST_SUITE_LOG)): Recognize a new test result
`ERROR
, we'd want to know
about them.
Thanks,
Ralf
Subject: [PATCH] coverage: new test on parallel-tests TESTS runtime
overriding
* tests/parallel-tests-cmdline-override.test: New test, check that
we can use indirections when overriding TESTS and TEST_LOGS from
the command line
...@gmail.com
From: Stefano Lattarini stefano.lattar...@gmail.com
Date: Wed, 29 Jun 2011 16:02:52 +0200
Subject: [PATCH] parallel-tests: make parsing of test results safer
The new code for parsing the testsuite-generated `.log' files,
as introduced in commit `v1.11-872-gc96b881', considers each
On Monday 27 June 2011, Ralf Wildenhues wrote:
* Stefano Lattarini wrote on Mon, Jun 27, 2011 at 03:48:58PM CEST:
I now think that the parallel-tests-maint should be merged
to maint. Objections?
OK.
Thanks,
Ralf
Merged and pushed.
Thanks,
Stefano
* Stefano Lattarini wrote on Fri, Jun 24, 2011 at 09:32:53AM CEST:
Subject: [PATCH] Revert docs: parallel-tests is not experimental anymore
This reverts commit a9eef973b5ea47cc3495f1a8307d4f7b85aea46f.
It turned out that the current work to introduce TAP and SubUnit
support in Automake
On Monday 27 June 2011, Ralf Wildenhues wrote:
* Stefano Lattarini wrote on Fri, Jun 24, 2011 at 09:32:53AM CEST:
Subject: [PATCH] Revert docs: parallel-tests is not experimental anymore
This reverts commit a9eef973b5ea47cc3495f1a8307d4f7b85aea46f.
It turned out that the current work
1 - 100 of 198 matches
Mail list logo
