Paul Smith wrote:
> I bumped the timeout to 10 seconds because, why not? I'll be
> interested to see if we still get these timeouts...
Yes, with tmout changed from 4 to 10 in tests/thelp.pl, I still
see these failures among the output-sync tests. On a machine with
minimal load.
Bruno
On Sun, 2022-10-23 at 16:17 +0200, Bruno Haible wrote:
> Paul Smith wrote:
> > I bumped the timeout to 10 seconds because, why not? I'll be
> > interested to see if we still get these timeouts...
>
> Yes, with tmout changed from 4 to 10 in tests/thelp.pl, I still
> see these failures among the
On Wed, 2022-10-19 at 04:44 +0200, Bruno Haible wrote:
> > I saw a similar test timeout.
>
> If the test hit a timeout, the timeout is definitely too small.
It's strange. The timeout on this is 4 seconds, but it's just waiting
for a file to be created by a different target. It's hard to
Dmitry Goncharov wrote:
> > On CentOS 8 Stream / x86_64 (a glibc 2.28 system), the compilation works
> > fine,
> > but the test suite has failures in the 'output-sync' category:
> > - 3 failures in a build with gcc,
> > - 4 failures in a build with clang-15.0.2.
>
>
> I saw a similar test
On Tue, Oct 18, 2022 at 7:55 PM Bruno Haible wrote:
> On CentOS 8 Stream / x86_64 (a glibc 2.28 system), the compilation works fine,
> but the test suite has failures in the 'output-sync' category:
> - 3 failures in a build with gcc,
> - 4 failures in a build with clang-15.0.2.
I saw a similar
On CentOS 8 Stream / x86_64 (a glibc 2.28 system), the compilation works fine,
but the test suite has failures in the 'output-sync' category:
- 3 failures in a build with gcc,
- 4 failures in a build with clang-15.0.2.
centos8s-gcc-failures.tar.gz
Description: application/compressed-tar
