-
-
Notifications
You must be signed in to change notification settings - Fork 1k
chore: Increase vstest timeout value #2753
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
Conversation
This does not appear to fix it. I saw you updated |
Yes, it seems not be resolved by increasing timeout.
I'll try to newer versions on separate PR. |
That's annoying. We can change those tests to use a different nuget package besides Newtonsoft. |
4356640
to
d52f738
Compare
d52f738
to
af5a66e
Compare
Close this PR. |
It seems As far as I've confirmed. So it expected not caused by recent NuGet package dependencies update. |
I've updated .NET SDK version. (#2762) Failed CI logs |
It seems above error is still occurred on CI. Failed CI logs
|
This PR intended to fix random CI test failure.
By increasing VSTest shutdown timeout. (1sec ->10 sec)
CI error details
Currently CI error happens on
test-linux
job.And following logs are recorded on finish test timing.
So, It is assumed to be related to the following vstest issue.
microsoft/vstest#2952
Related CI error logs.