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

Assert failure currentProcessCpuCount == g_processAffinitySet.Count() #33031

Closed
benaadams opened this issue Mar 1, 2020 · 4 comments
Closed

Comments

@benaadams
Copy link
Member

https://helix.dot.net/api/2019-06-17/jobs/5c24c550-4c42-459f-bbfd-21e69cbf8a27/workitems/System.Diagnostics.Process.Tests/console

Libraries Test Run checked coreclr Linux x64 Debug

Assert failure(PID 15210 [0x00003b6a], Thread: 15210 [0x3b6a]): currentProcessCpuCount == g_processAffinitySet.Count()
File: /__w/1/s/src/coreclr/src/vm/gcenv.os.cpp Line: 123
Image: /home/helixbot/work/AB3D09A7/p/dotnet

System.Diagnostics.Tests.ProcessTests.TestProcessorAffinity [FAIL]
  System.InvalidOperationException : Cannot process request because the process (15210) has exited.
  Stack Trace:
	System.Diagnostics.Process/src/System/Diagnostics/Process.Unix.cs(343,0): at System.Diagnostics.Process.ThrowIfExited(Boolean refresh)
	System.Diagnostics.Process/src/System/Diagnostics/Process.cs(932,0): at System.Diagnostics.Process.EnsureState(State state)
	System.Diagnostics.Process/src/System/Diagnostics/Process.Linux.cs(191,0): at System.Diagnostics.Process.set_ProcessorAffinityCore(IntPtr value)
	System.Diagnostics.Process/src/System/Diagnostics/Process.cs(532,0): at System.Diagnostics.Process.set_ProcessorAffinity(IntPtr value)
	System.Diagnostics.Process/tests/ProcessTests.cs(861,0): at System.Diagnostics.Tests.ProcessTests.TestProcessorAffinity()
System.Diagnostics.Tests.ProcessTests.TestProcessRecycledPid [SKIP]
  Condition(s) not met: "IsStressModeEnabled"
Finished:    System.Diagnostics.Process.Tests

Seen in #32538

@AndyAyersMS
Copy link
Member

@jkotas
Copy link
Member

jkotas commented Mar 1, 2020

The other failures so far were on arm. It is interesting that we have hit it on x64 as well.

@jkotas
Copy link
Member

jkotas commented Mar 1, 2020

Resolving as dup of #12510

@jkotas jkotas closed this as completed Mar 1, 2020
@benaadams
Copy link
Member Author

Might be race with process exit? Cannot process request because the process (15210) has exited.

@jeffhandley jeffhandley removed the untriaged New issue has not been triaged by the area owner label Sep 17, 2020
@ghost ghost locked as resolved and limited conversation to collaborators Dec 10, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

5 participants