-
Notifications
You must be signed in to change notification settings - Fork 89
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
Make the Agent_Register_UseAliasCheck test more robust #203
Make the Agent_Register_UseAliasCheck test more robust #203
Conversation
3e6950e
to
ce63fa7
Compare
@@ -2,6 +2,7 @@ | |||
|
|||
<PropertyGroup> | |||
<TargetFrameworks>netcoreapp3.1;net5.0;net6.0</TargetFrameworks> | |||
<CheckEolTargetFramework>false</CheckEolTargetFramework> |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Removes warnings about net5.0 being out of support.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
ok, maybe we should remove these 2 unsupported targets at some point.
I guess these need fixing/more delay too in a follow up PR?
|
Yes, these happened few time as well, but it is definitely a problem for another PR. |
Fixes flakiness of the
Agent_Register_UseAliasCheck
test.It is still more of a guesswork, but I've tried 5 times (see statuses for last 5 commits), and the only failed check is not related to the Agent_Register_UseAliasCheck`.