Open danmoseley opened 2 years ago
Tagging subscribers to this area: @dotnet/area-system-text-regularexpressions See info in area-owners.md if you want to be subscribed.
Author: | danmoseley |
---|---|
Assignees: | - |
Labels: | `area-System.Text.RegularExpressions`, `untriaged` |
Milestone: | - |
cc: @veanes
As a datapoint, I just now ran the test on the same machine but alone, and got these times
<test name="System.Text.RegularExpressions.Tests.RegexMatchTests.Match_VaryingLengthStrings_Huge(engine: Interpreter)" type="System.Text.RegularExpressions.Tests.RegexMatchTests" method="Match_VaryingLengthStrings_Huge" time="0.0614033" result="Pass">
<test name="System.Text.RegularExpressions.Tests.RegexMatchTests.Match_VaryingLengthStrings_Huge(engine: Compiled)" type="System.Text.RegularExpressions.Tests.RegexMatchTests" method="Match_VaryingLengthStrings_Huge" time="0.0548128" result="Pass">
<test name="System.Text.RegularExpressions.Tests.RegexMatchTests.Match_VaryingLengthStrings_Huge(engine: NonBacktracking)" type="System.Text.RegularExpressions.Tests.RegexMatchTests" method="Match_VaryingLengthStrings_Huge" time="9.9688913" result="Pass">
<test name="System.Text.RegularExpressions.Tests.RegexMatchTests.Match_VaryingLengthStrings_Huge(engine: SourceGenerated)" type="System.Text.RegularExpressions.Tests.RegexMatchTests" method="Match_VaryingLengthStrings_Huge" time="3.1690631" result="Pass">
In the above case it timed out at 60 sec. Still can't say whether it's an actual hang vs concurrent tests monopolizing the machine.
Interesting. Did you only see issues with this particular test and this particular test assembly or other test assemblies as well? I ask because I'm not sure if the issue is more around the way we are executing different library tests in parallel.
On my i7-10th gen laptop. This was running all tests in the tree, so other test libraries would be executing in parallel.
Branch was at 27195f670937c7e21ab68a806396f9d17c57231a