NightOwl888 commented on issue #1295: URL: https://github.com/apache/lucenenet/issues/1295#issuecomment-4383101304
> I had Claude Code orchestrate dotnet and run through these with the specified seeds many times. None of them were able to be reproduced at all (let alone reliably) on macOS .NET 10 arm64. I will try later on Windows and Linux x64. https://dev.azure.com/LuceneNET-Temp/Lucene.NET/_build/results?buildId=2513&view=results Yeah, the fact that the seed doesn't trigger it is a solid indicator that this is a concurrency problem (in addition to the fact that it only seems to fail on concurrent tests). Azure DevOps triggers failures on most runs. I haven't seen `net9.0` or `net8.0` fail with any of these exceptions. It is definitely TFM-related, not something that is likely to be fixed by something we are seeing on all TFMs. Most likely, it is one of: - Some `FEATURE_` is mismatching with what the target framework actually supports - Microsoft changed something concurrency-related that we depend on between `net9.0` and `net10.0` that broke an assumption we made based on implementation details of the BCL (such as with `UninterruptableMonitor` or `NativeFSLockFactory`). It could be something else, but those would be the places to check first. For the latter, it may help to diff the last release of .NET 9 and .NET 10 and look for files that are concurrency-related. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
