On Mon, 30 Jul 2018, Florian Weimer wrote:
> > There are a lot of tests that set TIMEOUT to less than 20.
>
> We should fix all of them.
It's conceivable some are deliberately less than 20 (if e.g. the test
sleeps for a certain number of seconds and does nothing else that should
take a signifi
On 07/30/2018 06:07 PM, Andreas Schwab wrote:
On Jul 30 2018, Joseph Myers wrote:
On Mon, 30 Jul 2018, Alexey Brodkin wrote:
diff --git a/timezone/tst-tzset.c b/timezone/tst-tzset.c
index 27f986b56dab..534f7acdf75f 100644
--- a/timezone/tst-tzset.c
+++ b/timezone/tst-tzset.c
@@ -25,7 +25,7 @
On Jul 30 2018, Joseph Myers wrote:
> On Mon, 30 Jul 2018, Alexey Brodkin wrote:
>
>> diff --git a/timezone/tst-tzset.c b/timezone/tst-tzset.c
>> index 27f986b56dab..534f7acdf75f 100644
>> --- a/timezone/tst-tzset.c
>> +++ b/timezone/tst-tzset.c
>> @@ -25,7 +25,7 @@
>> #include
>> #include
>>
On Mon, 30 Jul 2018, Alexey Brodkin wrote:
> diff --git a/timezone/tst-tzset.c b/timezone/tst-tzset.c
> index 27f986b56dab..534f7acdf75f 100644
> --- a/timezone/tst-tzset.c
> +++ b/timezone/tst-tzset.c
> @@ -25,7 +25,7 @@
> #include
> #include
>
> -#define TIMEOUT 5
> +#define TIMEOUT 10
Th
On ARC HSDK board even though it operates @ 1GHz this test runs
~7 seconds which gives us failures all the time.
That's what happens now:
| # time .../build/timezone/tst-tzset
| Timed out: killed the child process
| Command exited with non-zero status 1
| real0m 5.11s
| user0m 3.59s
| sys
