Re: 4 pgcrypto regressions failures - 1 unsolved - Mailing list pgsql-hackers

From Andrew Dunstan
Subject Re: 4 pgcrypto regressions failures - 1 unsolved
Date
Msg-id 4881.24.211.165.134.1121079032.squirrel@www.dunslane.net
Whole thread Raw
In response to 4 pgcrypto regressions failures - 1 unsolved  (Marko Kreen <marko@l-t.ee>)
Responses Re: 4 pgcrypto regressions failures - 1 unsolved
List pgsql-hackers
Marko Kreen said:
>

>
>
http://www.pgbuildfarm.org/cgi-bin/show_log.pl?nm=canary&dt=2005-07-11%2002:30:00>
> NetBSD 1.6 with older OpenSSL.  OpenSSL < 0.9.7 does not have
> AES, but most of PGP tests use it as it is the preferred cipher.
> And the AES tests fails anyway.  I guess it can stay as expected
> failure.
>

Please try to avoid expected failures if possible. If you must have them,
move them into a test file of their own. Consider the possibility of using
alternative .out files.

This doesn't matter to Buildfarm quite so much for contrib as it does for
main or PL regression sets, as contrib is the last thing checked, so a
failure there doesn't block any other steps in the checking process. Still,
a contrib failure will show up as yellow rather than green.

Buildfarm does not currently have a way of knowing what failure is expected
and what is not - it currently treats any regression failure as unexpected.
Changing that is on my TODO list, but it's not going to happen any time soon.

cheers

andrew




pgsql-hackers by date:

Previous
From: Marko Kreen
Date:
Subject: 4 pgcrypto regressions failures - 1 unsolved
Next
From: "Merlin Moncure"
Date:
Subject: Re: Hide source code