On 01/12/20 10:52 +, Jonathan Wakely wrote:
On 01/12/20 10:45 +0100, Christophe Lyon wrote:
On Mon, 30 Nov 2020 at 15:58, Jonathan Wakely wrote:
On 27/11/20 21:17 +0100, Christophe Lyon via Libstdc++ wrote:
On Fri, 27 Nov 2020 at 17:13, Jonathan Wakely via Gcc-patches
wrote:
The defau
On 01/12/20 10:45 +0100, Christophe Lyon wrote:
On Mon, 30 Nov 2020 at 15:58, Jonathan Wakely wrote:
On 27/11/20 21:17 +0100, Christophe Lyon via Libstdc++ wrote:
>On Fri, 27 Nov 2020 at 17:13, Jonathan Wakely via Gcc-patches
> wrote:
>>
>> The default for the GCC testsuite is 300, i.e. 5 minu
On Mon, 30 Nov 2020 at 15:58, Jonathan Wakely wrote:
>
> On 27/11/20 21:17 +0100, Christophe Lyon via Libstdc++ wrote:
> >On Fri, 27 Nov 2020 at 17:13, Jonathan Wakely via Gcc-patches
> > wrote:
> >>
> >> The default for the GCC testsuite is 300, i.e. 5 minutes, which is the
> >> same as the DejaG
On 27/11/20 21:17 +0100, Christophe Lyon via Libstdc++ wrote:
On Fri, 27 Nov 2020 at 17:13, Jonathan Wakely via Gcc-patches
wrote:
The default for the GCC testsuite is 300, i.e. 5 minutes, which is the
same as the DejaGnu default.
Libstdc++ overrides this to 600, i.e. 10 minutes.
This seems
On Fri, 27 Nov 2020 at 17:13, Jonathan Wakely via Gcc-patches
wrote:
>
> The default for the GCC testsuite is 300, i.e. 5 minutes, which is the
> same as the DejaGnu default.
>
> Libstdc++ overrides this to 600, i.e. 10 minutes.
>
> This seems ridiculously long. If any test takes that long on mode
The default for the GCC testsuite is 300, i.e. 5 minutes, which is the
same as the DejaGnu default.
Libstdc++ overrides this to 600, i.e. 10 minutes.
This seems ridiculously long. If any test takes that long on modern
hardware, something is wrong. We've seen this a lot recently with
buggy tests,
