On Mon, 24 Nov 2025, 17:10 Matthew Malcomson, <[email protected]> wrote:
> Hello both, > > I'm seeing a (non-public) testsuite hitting assertions after these > checks. It's going through the EDEADLK code path in `try_lock_until` so > is newly hitting an assertion. > > Is hitting these assertions indication that the testsuite source code is > incorrect and I should look into that? Or is it more that > `_GLIBCXX_ASSERTIONS` should not be enabled? > The tests should pass with and without the assertions enabled (I routinely test both), so it might be something non-portable in the test. Are you using glibc? > >
