Thanks to visit codestin.com
Credit goes to github.com

Skip to content

Conversation

filzrev
Copy link
Contributor

@filzrev filzrev commented Jun 6, 2025

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.

The active test run was aborted. Reason: Test host process crashed.

So, It is assumed to be related to the following vstest issue.
microsoft/vstest#2952

Related CI error logs.

@timcassell
Copy link
Collaborator

timcassell commented Jun 6, 2025

This does not appear to fix it. I saw you updated Microsoft.NET.Test.Sdk to 17.13.0 in #2750, which is not the latest version. microsoft/vstest#2952 (comment) mentioned that a newer preview version fixed it for them. You could try updating to the latest version 17.14.1, unless that breaks things for some reason?

@filzrev
Copy link
Contributor Author

filzrev commented Jun 6, 2025

Yes, it seems not be resolved by increasing timeout.
And it need to investigate vstest diag logs for details.

a newer preview version fixed it for them. You could try updating to the latest version 17.14.1, unless that breaks things for some reason?

I'll try to newer versions on separate PR.
(Microsoft.NET.Test.Sdk depends on NewtonsoftJson. So it need to modify WithNuGet relating code to update to latest versions)

@filzrev filzrev marked this pull request as draft June 6, 2025 19:05
@timcassell
Copy link
Collaborator

(Microsoft.NET.Test.Sdk depends on NewtonsoftJson. So it need to modify WithNuGet relating code to update to latest versions)

That's annoying. We can change those tests to use a different nuget package besides Newtonsoft.

@filzrev filzrev force-pushed the chore-increase-vstest-timeout branch 2 times, most recently from 4356640 to d52f738 Compare June 7, 2025 10:24
@filzrev filzrev force-pushed the chore-increase-vstest-timeout branch from d52f738 to af5a66e Compare June 7, 2025 10:59
@filzrev
Copy link
Contributor Author

filzrev commented Jun 7, 2025

Close this PR.
Test host process crashed issue is expected to be resolved by #2755

@filzrev filzrev closed this Jun 7, 2025
@filzrev
Copy link
Contributor Author

filzrev commented Jun 8, 2025

It seems Test host process crashed is not resolved by updating Microsoft.NET.Test.Sdk versions.
Because latest CI on master failed with this error.
https://github.com/dotnet/BenchmarkDotNet/actions/runs/15520368955

As far as I've confirmed.
This CI error started occurred from 3-weeks ago.
https://github.com/dotnet/BenchmarkDotNet/actions/runs/15117387191

So it expected not caused by recent NuGet package dependencies update.

@filzrev
Copy link
Contributor Author

filzrev commented Jun 10, 2025

I've updated .NET SDK version. (#2762)
But Test host process crashed issue seems still continued.

Failed CI logs
https://github.com/dotnet/BenchmarkDotNet/actions/runs/15535280088

@filzrev
Copy link
Contributor Author

filzrev commented Jul 5, 2025

The active test run was aborted. Reason: Test host process crashed.

It seems above error is still occurred on CI.
Error is raised when running DotMemoryTests of BenchmarkDotNet.IntegrationTests
And when error occurred. it seems some delay (about 5 seconds) is observed when detaching dotMemory.

Failed CI logs
https://github.com/dotnet/BenchmarkDotNet/actions/runs/16084412378/job/45393708556

2025-07-05T04:28:17.4559913Z Attaching dotMemory to the process...
2025-07-05T04:28:18.7868165Z dotMemory is successfully attached
2025-07-05T04:28:18.8034871Z WorkloadActual   1: 1 op, 37009.00 ns, 37.0090 us/op
2025-07-05T04:28:18.8035699Z Taking dotMemory snapshot...
2025-07-05T04:28:20.2047484Z dotMemory snapshot is successfully taken
2025-07-05T04:28:20.2047929Z Detaching dotMemory from the process...
2025-07-05T04:28:25.4637525Z dotMemory is successfully detached
2025-07-05T04:28:25.4638225Z WorkloadResult   1: 1 op, 37009.00 ns, 37.0090 us/op
2025-07-05T04:28:27.5299589Z The active test run was aborted. Reason: Test host process crashed

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants