Ian Henriksen
Ian Henriksen
Actually I'm seeing the weird at exit failure with thread sanitizer with a handful of other tests and they're distinct from the ones that hang, so my best guess is...
Haven't seen this one show up in a while. I'm assuming some other fix resolved it along the way.
Note, this is also a problem we have at build time for determining the size of certain data structures. If possible I'd like to at least get something semi-reasonable figured...
Thanks! Yah, sorry that one slipped through into the release. I'll get a fix up for it shortly.
This will probably be a pain to debug so I don't think it's feasible to get it fixed before the upcoming release, however I have confirmed that these new failures...
This seems to have gone away on its own. My best bet is that #297 fixed it, but I'm still not entirely sure.
Just saw this again the day after closing it, but it's not showing up today. Perhaps the timeouts just need to be increased. Running on a busier CI instance could...
Alright, we're still seeing these even after increasing the timeout thresholds. See https://github.com/sandialabs/qthreads/actions/runs/11448461793/job/31852093932?pr=305 for an example.
I wonder if this is related to https://github.com/sandialabs/qthreads/issues/267#issuecomment-2423163776 as well. Plausible, but currently unclear.
Figured out how to dig a backtrace out of this! Thanks to https://stackoverflow.com/a/8657833. The winning incantation ends up being: `for ((i=0; i