Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Fix timeout in regex source generated test #80459

Merged
merged 2 commits into from
Jan 12, 2023

Conversation

stephentoub
Copy link
Member

The test is using Roslyn to dynamically emit a Regex with the source generator, as we do throughout the test suite. However, this test is about validating the default static regex timeout, and the Roslyn code itself uses a regex. To work around this, this PR splits off the source generated test into its own dedicated one that doesn't rely on Roslyn.

Fixes #77814

@ghost
Copy link

ghost commented Jan 10, 2023

Tagging subscribers to this area: @dotnet/area-system-text-regularexpressions
See info in area-owners.md if you want to be subscribed.

Issue Details

The test is using Roslyn to dynamically emit a Regex with the source generator, as we do throughout the test suite. However, this test is about validating the default static regex timeout, and the Roslyn code itself uses a regex. To work around this, this PR splits off the source generated test into its own dedicated one that doesn't rely on Roslyn.

Fixes #77814

Author: stephentoub
Assignees: -
Labels:

area-System.Text.RegularExpressions

Milestone: -

The test is using Roslyn to dynamically emit a Regex with the source generator, as we do throughout the test suite.  However, this test is about validating the default static regex timeout, and the Roslyn code itself uses a regex.  To work around this, this PR splits off the source generated test into its own dedicated one that doesn't rely on Roslyn.
Copy link
Member

@danmoseley danmoseley left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I guess I didn't do this because it means the latest source generator bits are not being tested? Practically speaking the SDK we build with might have bits up to a few weeks old, right.

@stephentoub
Copy link
Member Author

I guess I didn't do this because it means the latest source generator bits are not being tested?

Correct:
https://github.com/dotnet/runtime/pull/80459/files#diff-2bdc6a6839e8ce7675737db0067c7cf288d190e0af1559feed81d5be92c9b216R1290-R1293

@stephentoub stephentoub merged commit 1d0a69f into dotnet:main Jan 12, 2023
@stephentoub stephentoub deleted the fixregextimeout branch January 12, 2023 14:35
@ghost ghost locked as resolved and limited conversation to collaborators Feb 11, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
2 participants