[Dune-devel] tests with return code 77

Oliver Sander sander at igpm.rwth-aachen.de
Wed Dec 4 14:33:27 CET 2013


My AutoTools-setup actually lists them separately, e.g.

============================================================================
Testsuite summary for dune-grid 2.3-svn
============================================================================
# TOTAL: 16
# PASS:  16
# SKIP:  0  <---
# XFAIL: 0
# FAIL:  0
# XPASS: 0
# ERROR: 0


Am 04.12.2013 14:16, schrieb Christian Engwer:
> Oli is partially right. At least in previous verrsions of automake an
> exit-code of 77 indicated an expected failure.
> 
> Christian
> 
> On Wed, Dec 04, 2013 at 09:05:44AM +0100, Oliver Sander wrote:
>> Hi Markus,
>> I suppose that is to notify that at least there is a test, even if it is
>> not run.
>> Cheers,
>> Oliver
>>
>> Am 03.12.2013 23:39, schrieb Markus Blatt:
>>> Hi,
>>>
>>> it seems like some of the tests are always built and run no matter
>>> whether they actually compute anything due to the current
>>> configuration. An example is
>>> dune/common/parallel/test/indicestest. Without MPI it just returns an
>>> error code 77 and make check reports it as skipped.
>>>
>>> Can someone explain me what the rational behind this decision is? Why
>>> do we not simply exclude it from the test list if MPI is not there?
>>>
>>> Cheers,
>>>
>>> Markus
>>>
>>
>>
> 
> 
> 
>> _______________________________________________
>> Dune-devel mailing list
>> Dune-devel at dune-project.org
>> http://lists.dune-project.org/mailman/listinfo/dune-devel
> 
> 


-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 551 bytes
Desc: OpenPGP digital signature
URL: <https://lists.dune-project.org/pipermail/dune-devel/attachments/20131204/d21c9525/attachment.sig>


More information about the Dune-devel mailing list