Disable EventSource tests #95498
Disable EventSource tests #95498
Conversation
|
Tagging subscribers to this area: @tarekgh, @tommcdon, @pjanotti Issue DetailsThe manifest generation tests use lots of sleeps and are problematic with longer running targets, i.e. jitstress and gcstress. The ETW tests keep failing because the process is not elevated even though we should be guarding against that, further research is necessary to determine what the issue is. For now we should disable these tests to get them off the blocking CI list
|
ghost
assigned 
| @@ -30,7 +30,7 @@ public partial class TestsManifestGeneration | |||
|
|
|||
| /// ETW only works with elevated process | |||
| [ConditionalFact(nameof(IsProcessElevatedAndNotWindowsNanoServerAndRemoteExecutorSupported))] | |||
| [ActiveIssue("https://github.com/dotnet/runtime/issues/48798", typeof(PlatformDetection), nameof(PlatformDetection.IsX86Process))] | |||
| [ActiveIssue("https://github.com/dotnet/runtime/issues/48798")] | |||
There was a problem hiding this comment.
I don't see any non win-x86 failures in #48798. Why disable it on other platforms too?
|
I agree - disabling the manifest generation ETW tests while we resolve test parallelization and timing issues will help reduce unnecessary noise on PR's and daily builds. |
The manifest generation tests use lots of sleeps and are problematic with longer running targets, i.e. jitstress and gcstress.
The ETW tests keep failing because the process is not elevated even though we should be guarding against that, further research is necessary to determine what the issue is. For now we should disable these tests to get them off the blocking CI list