Re: 4 pgcrypto regressions failures - 1 unsolved

From: "Andrew Dunstan" <andrew(at)dunslane(dot)net>
To: <marko(at)l-t(dot)ee>
Cc: <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: 4 pgcrypto regressions failures - 1 unsolved
Date: 2005-07-11 10:50:32
Message-ID: 4881.24.211.165.134.1121079032.squirrel@www.dunslane.net
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers pgsql-patches

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

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Simon Riggs 2005-07-11 10:52:09 Re: Checkpoint cost, looks like it is WAL/CRC
Previous Message Simon Riggs 2005-07-11 08:17:38 Re: Checkpoint cost, looks like it is WAL/CRC

Browse pgsql-patches by date

  From Date Subject
Next Message Marko Kreen 2005-07-11 10:54:21 4 pgcrypto regressions failures - 1 unsolved
Previous Message Satoshi Nagayasu 2005-07-11 03:13:20 Re: A couple of p.tches for PostgreSQL 64bit support