Marcus Hodgson

@serathius Out of the box, no. But there are other options to consider- like a test composer command that could do something similar?

@glycerine Antithesis can definitely find concurrency & race condition bugs! We use thread pausing on instrumented code (documented [here](https://antithesis.com/docs/instrumentation/#benefits-of-instrumentation) if you are curious, and we have a bunch of other...

Adding more context here to help with the investigation: [Bug report](https://linuxfoundation.antithesis.com/report/wrXDp8Ojw57Cj8OWw6BTwrvDvh3Di0bCosKYIiNX/Xmk6IoKvz9IU9VO0Gsc6fA-H2zRHdlM3LEp4yELhI-I.html?auth=v2.public.eyJuYmYiOiIyMDI1LTA4LTEzVDE5OjA4OjAzLjcyNDUzMjk0MloiLCJzY29wZSI6eyJSZXBvcnRTY29wZVYxIjp7ImFzc2V0IjoiWG1rNklvS3Z6OUlVOVZPMEdzYzZmQS1IMnpSSGRsTTNMRXA0eUVMaEktSS5odG1sIiwicmVwb3J0X2lkIjoid3JYRHA4T2p3NTdDajhPV3c2QlR3cnZEdmgzRGkwYkNvc0tZSWlOWCJ9fX1XNzbf2AkQ26jOJjR9d9vZsVtoVWmO5Ri8ozo3bQ-GML0KucpEUQijIe8bhp2W8khCTsEXkxUgYSUfDkrkTBQG) Any section that might be confusing has some explanation in [our documentation here](https://antithesis.com/docs/reports/#the-bug-report). What I gather from the report...

@serathius Pointing out here that the line #s and col #s might be on instrumented code, which is something that I would have to check. The statistical debug information is...

Looks like we have another reproduction of a linearization failure from this report: https://linuxfoundation.antithesis.com/report/w5AjMMKhwqLDksK6CgDDoyUawpFSw54Qw45j/8jICMyoSWR24qW-J6NfeaukB31JBNpQlD3MVIwmJvC4.html?auth=v2.public.eyJuYmYiOiIyMDI1LTA4LTI2VDEzOjE2OjQ4Ljc2NDIyNTU0OFoiLCJzY29wZSI6eyJSZXBvcnRTY29wZVYxIjp7ImFzc2V0IjoiOGpJQ015b1NXUjI0cVctSjZOZmVhdWtCMzFKQk5wUWxEM01WSXdtSnZDNC5odG1sIiwicmVwb3J0X2lkIjoidzVBak1NS2h3cUxEa3NLNkNnRERveVVhd3BGU3c1NFF3NDVqIn19fUsvbqFp7xtGva25OumBuZlxCyW-5SDeRKEUPrKC5H3sg7zb6rXd90k_s0DKcMETux49_53MRd-Id6mJDCNnfQs I'm looking into why the artifact isn't on the report! [var_report_dump_15.tar.gz](https://github.com/user-attachments/files/21990763/var_report_dump_15.tar.gz)