bug#70070: FAIL: test-localtime_r

2024-03-29 Thread Bruno Haible
Andreas Schwab wrote: > > Yes. And make sure that it has a time zone database installed at all. > > Why? That doesn't make any sense. You can leave the consideration of which test case makes sense or not on my side. What we need from you, as a reporter, is a statement on which platform (distro

bug#70070: FAIL: test-localtime_r

2024-03-29 Thread Andreas Schwab
On Mär 29 2024, Bruno Haible wrote: > Yes. And make sure that it has a time zone database installed at all. Why? That doesn't make any sense.

bug#70070: FAIL: test-localtime_r

2024-03-29 Thread Bruno Haible
Andreas Schwab wrote: > > FAIL: test-localtime_r > > == > > > > test-localtime_r.c:58: assertion 'result->tm_hour == 18' failed > > FAIL test-localtime_r (exit status: 134) > > > > FAIL: test-localtime_r-mt > > = > > > > thread2 disturbed by thread1!

bug#70070: FAIL: test-localtime_r

2024-03-29 Thread Pádraig Brady
On 29/03/2024 12:40, Andreas Schwab wrote: FAIL: test-localtime_r == test-localtime_r.c:58: assertion 'result->tm_hour == 18' failed FAIL test-localtime_r (exit status: 134) FAIL: test-localtime_r-mt = thread2 disturbed by thread1! thread1 disturbed

bug#70070: FAIL: test-localtime_r

2024-03-29 Thread Andreas Schwab
FAIL: test-localtime_r == test-localtime_r.c:58: assertion 'result->tm_hour == 18' failed FAIL test-localtime_r (exit status: 134) FAIL: test-localtime_r-mt = thread2 disturbed by thread1! thread1 disturbed by thread2! FAIL test-localtime_r-mt (exit