paulirwin opened a new issue, #1123: URL: https://github.com/apache/lucenenet/issues/1123
It looks like there is a problem with these tests on: - `net9.0` x64, Windows - `net9.0` x64 Linux - `net6.0` x64 Windows https://dev.azure.com/LuceneNET-Temp/Lucene.NET/_build/results?buildId=2410&view=ms.vss-test-web.build-test-results-tab ``` Expected: 1, Actual: 0 (Test: Lucene.Net.Support.Threading.TestLimitedConcurrencyLevelTaskScheduler.TestGetActiveCount) To reproduce this test result: Option 1: Apply the following assembly-level attributes: [assembly: Lucene.Net.Util.RandomSeed("0x9054fc2057c057c9")] [assembly: NUnit.Framework.SetCulture("ia")] Option 2: Use the following .runsettings file: <RunSettings> <TestRunParameters> <Parameter name="tests:seed" value="0x9054fc2057c057c9" /> <Parameter name="tests:culture" value="ia" /> </TestRunParameters> </RunSettings> Option 3: Create the following lucene.testsettings.json file somewhere between the test assembly and the root of your drive: { "tests": { "seed": "0x9054fc2057c057c9", "culture": "ia" } } Fixture Test Values Random Seed: 0x9054fc2057c057c9 Culture: ia Time Zone: (UTC-04:00) Georgetown, La Paz, Manaus, San Juan Default Codec: Lucene45 (Lucene45RWCodec) Default Similarity: RandomSimilarityProvider(queryNorm=False,coord=crazy): {} System Properties Nightly: False Weekly: False Slow: True Awaits Fix: False Directory: random Verbose: False Random Multiplier: 1 ``` ------------------------- ``` Expected: 1, Actual: 0 (Test: Lucene.Net.Support.Threading.TestLimitedConcurrencyLevelTaskScheduler.TestGetCompletedTaskCount) To reproduce this test result: Option 1: Apply the following assembly-level attributes: [assembly: Lucene.Net.Util.RandomSeed("0x9054fc2057c057c9")] [assembly: NUnit.Framework.SetCulture("ia")] Option 2: Use the following .runsettings file: <RunSettings> <TestRunParameters> <Parameter name="tests:seed" value="0x9054fc2057c057c9" /> <Parameter name="tests:culture" value="ia" /> </TestRunParameters> </RunSettings> Option 3: Create the following lucene.testsettings.json file somewhere between the test assembly and the root of your drive: { "tests": { "seed": "0x9054fc2057c057c9", "culture": "ia" } } Fixture Test Values Random Seed: 0x9054fc2057c057c9 Culture: ia Time Zone: (UTC-04:00) Georgetown, La Paz, Manaus, San Juan Default Codec: Lucene45 (Lucene45RWCodec) Default Similarity: RandomSimilarityProvider(queryNorm=False,coord=crazy): {} System Properties Nightly: False Weekly: False Slow: True Awaits Fix: False Directory: random Verbose: False Random Multiplier: 1 ``` _Originally posted by @NightOwl888 in https://github.com/apache/lucenenet/issues/1119#issuecomment-2609133593_ Additional context from @paulirwin: These tests rely on thread/task timing to assert properly, so there might be some thread or other contention causing them to take a while to begin or finish their queue. I'm wondering if these tests should be considered inconclusive if their counts aren't exact, rather than failures. They do succeed on GitHub actions for the same platforms. -- 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.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
