Revert "Add new SOS test harness" - #6006
Merged
Merged
Build Analysis / Build Analysis
succeeded
Sep 4, 2026 in 0s
.NET Result Analysis
Details
‼️ Build Analysis Check Result has been manually overridden
- The build analysis check result has been updated by the user for the following reason: Known eventpipe issue
- The check result has changed from Failure to Success
Tip
To unconditionally bypass the build analysis check (turn it green), you can use the escape mechanism feature. The completion time may vary, potentially taking several minutes, depending on the build analysis workload at the moment.
Build Failures
diagnostics-public-ci / Test Diagnostics / Alpine3_23_x64_Release / Test
[ 🚧 Create issue against infrastructure team] [ 📄 Create issue in this repo]-
❌Bash exited with code '1'.
Test Failures (1 tests failed)
🔹 [All failing tests from diagnostics-public-ci]
- Data Driven SubResults
- Exception Message
Assert.Equal() Failure: Strings differ\n ↓ (pos 0)\nExpected: \"Some warning message with 6\"\nActual: \"Warning message.\"\n ↑ (pos 0)
- Stack Trace
at Microsoft.Diagnostics.Monitoring.EventPipe.UnitTests.EventLogsPipelineUnitTests.ValidateLoggerRemoteCategoryInformationMessage(StreamReader reader) in /__w/1/s/src/tests/Microsoft.Diagnostics.Monitoring.EventPipe/EventLogsPipelineUnitTests.cs:line 249 at Microsoft.Diagnostics.Monitoring.EventPipe.UnitTests.EventLogsPipelineUnitTests.TestLogsAllCategoriesAllLevels(TestConfiguration config) in /__w/1/s/src/tests/Microsoft.Diagnostics.Monitoring.EventPipe/EventLogsPipelineUnitTests.cs:line 59 --- End of stack trace from previous location ---
❌ Microsoft.Diagnostics.Monitoring.EventPipe.UnitTests.EventLogsPipelineUnitTests.TestLogsAllCategoriesAllLevels [Details] [3.38% failure rate]
-
[ 🚧 Create issue against infrastructure team] [ 📄 Create issue in this repo]
Failing Configuration
-
❌ Microsoft.Diagnostics.Monitoring.EventPipe.UnitTests.EventLogsPipelineUnitTests.TestLogsAllCategoriesAllLevels(config: projectk.sdk.prebuilt.9.0.18)
Was this helpful?
Loading