Hi,
> Which is why people should just compare testsuite results from earlier run
> on the same configuration to watch for regressions, especially in the
> guality testsuite.
All this gives the idea of a test framework that is too rigid, or tests that
are too fragile. I mean, The accumulation of
Martin Jambor writes:
> Hi,
>
> On Sat, Jul 15 2023, FX Coudert via Gcc wrote:
>> Hi,
>>
>> I am finding it very hard to reliably compare test results and regressions
>> with the very large number of gcc.dg/guality test failures that are
>> apparently the new norm on x86_64-linux: more than one
Hi,
On Sun, Jul 16, 2023 at 09:50:24AM +0200, FX Coudert via Gcc wrote:
> > Which is why people should just compare testsuite results from earlier run
> > on the same configuration to watch for regressions, especially in the
> > guality testsuite.
>
> All this gives the idea of a test framework t
Hi -
Hi -
> (CC Frank, the fedrawhide builder doesn't seem to include guality.exp,
> do you know why?)
Good question. The gcc.log testsuite file appears to be truncated as
it arrived into bunsen. The test does appear to be running on the
bot. Maybe the gcc's own dg* log processing scripts are
Snapshot gcc-14-20230716 is now available on
https://gcc.gnu.org/pub/gcc/snapshots/14-20230716/
and on various mirrors, see http://gcc.gnu.org/mirrors.html for details.
This snapshot has been generated from the GCC 14 git branch
with the following options: git://gcc.gnu.org/git/gcc.git branch
