bug#70070: FAIL: test-localtime_r
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 and version) you saw the test failure. If we don't have this, there is no good way for us to reproduce the issue, and we'll have to close the ticket. Bruno
bug#70070: FAIL: test-localtime_r
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
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 by thread2! > > FAIL test-localtime_r-mt (exit status: 134) The second failure is a consequence of the first one. So, there is no MT-safety problem, "just" that localtime_r produces wrong results. I've seen this happen on OSes with a time zone database that is older than 5 or 10 years. Pádraig Brady wrote: > It may help to detail your platform. Yes. And make sure that it has a time zone database installed at all. Bruno
bug#70070: FAIL: test-localtime_r
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 by thread2! FAIL test-localtime_r-mt (exit status: 134) CC'ing gnulib as those tests are from gnulib. It may help to detail your platform. thanks, Pádraig.
bug#70070: FAIL: test-localtime_r
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 status: 134) -- Andreas Schwab, sch...@linux-m68k.org GPG Key fingerprint = 7578 EB47 D4E5 4D69 2510 2552 DF73 E780 A9DA AEC1 "And now for something completely different."
