Re: pytest results for 2.4.59

2024-04-06 Thread Rainer Jung
Hi Jean-Frederic and all, you didn't write at what point in time you take the thread dump. I see the SIGTERM messages logged during test execution always during the last test in each group (http2, md, ...) just because that is the time the logs are checked by teardown for error messages. At

Re: pytest results for 2.4.59

2024-04-06 Thread jean-frederic clere
On 4/6/24 13:10, Yann Ylavic wrote: On Sat, Apr 6, 2024 at 10:46 AM jean-frederic clere wrote: On 4/5/24 07:55, Ruediger Pluem wrote: Are you able to provide a stacktrace of the hanging process (thread apply all bt full)? It seems pthread_kill(t, 0) returns 0 even the thread t has

Re: pytest results for 2.4.59

2024-04-06 Thread Yann Ylavic
On Sat, Apr 6, 2024 at 10:46 AM jean-frederic clere wrote: > > On 4/5/24 07:55, Ruediger Pluem wrote: > > > > Are you able to provide a stacktrace of the hanging process (thread apply > > all bt full)? > > It seems pthread_kill(t, 0) returns 0 even the thread t has exited... > older version of

Re: pytest results for 2.4.59

2024-04-06 Thread jean-frederic clere
On 4/5/24 07:55, Ruediger Pluem wrote: On 4/5/24 12:59 AM, Rainer Jung wrote: I think I fixed all test failures, hopefully in the correct way. More eyes welcome. I have a few additional sporadic ERRORS: A] ERROR during teardown check for log file errors or warnings (twice): 04.04.2024