NightOwl888 commented on issue #935: URL: https://github.com/apache/lucenenet/issues/935#issuecomment-2079331429
> @NightOwl888 I remember this was an old bug relevant only to older dotnet core. so if its not reproducible on the new dotnet, and only happen on versions that out of support anyway, maybe we shouldn't too Nope. This happens on all operating systems and .NET versions. I got it to fail on .NET 7 after that post. We cannot rule out that the problem lies in the test or the test framework, but it almost certainly is in our codebase. We have a configuration that never existed in Lucene. We are somewhere between 4.8.0 and 4.8.1 on the documents writer stuff. We should go through the JIRA issues in the [Changes.txt](https://github.com/apache/lucene/blob/releases/lucene-solr/4.8.1/lucene/CHANGES.txt#L6-L62) to determine if we have all of the changes that are relevant to the documents writer. That may or may not be contributing to this. > @NightOwl888 If you apply the changes to DocumentsWriterFlushControl from that branch on top of the latest can you still reproduce it? I have no luck on 5.0, 6.0 or 7.0 - but asking because maybe I am doing something wrong >.< > > (I have not run the entire test suite yet, there is allot of test and I have problems compiling the IKVM stuff) IKVM can be tricky to get to compile the first time because it doesn't properly clean the build. I suggest closing the IDE and then doing the following: - Delete all of your /bin and /obj folders (be careful not to delete the objects folder below /.git) - Clear the IKVM cache in the `~\AppData\Local\Temp\ikvm\cache` folder - Clear the `~\.m2` cache If upon reopening you still have issues compiling, report the issue to [ikvm-maven](https://github.com/ikvmnet/ikvm-maven). The team is pretty responsive. ------------------ On Azure DevOps, I was able to reproduce the test failure, but this time it took 60 runs and it only happened once: https://dev.azure.com/lucene-net-temp4/Main/_build/results?buildId=266&view=ms.vss-test-web.build-test-results-tab&runId=191370&resultId=100202&paneView=debug I was also able to get it to fail locally with the seed from [#886](https://github.com/apache/lucenenet/issues/886#issuecomment-1822964001). Using the `[Repeat(1000)]` attribute on the test, it failed on the first run on `net6.0` on Windows.  I just put the attribute in the `TestRollingUpdates.cs` file, but be sure to remove it when you are done debugging.   It also failed on the first run with the seed from the above Azure DevOps failure on `net6.0` on Windows. ```c# [assembly: Lucene.Net.Util.RandomSeed("0x9f28125320b5e6c3")] [assembly: NUnit.Framework.SetCulture("lrc-IR")] ```` I also got it to fail on `net7.0` with that seed on the first run, but it took significantly longer.  -- 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: dev-unsubscr...@lucenenet.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
