baseservices-exceptions failing for unclear reason.

[tarekgh]

Build

https://dev.azure.com/dnceng-public/cbb18261-c48f-4abb-8651-8cdcb5474649/_build/results?buildId=1094333

Seeing this multiple times. Sometimes the artifacts are not provided at all. And when artifacts are available, it looks like the tests ran successfully and ended with the expected code.

Build leg reported

baseservices-exceptions.WorkItemExecution

Pull Request

https://github.com/dotnet/runtime/pull/117634

Known issue core information

Fill out the known issue JSON section by following the step by step documentation on how to create a known issue

 {
    "ErrorMessage" : ["baseservices-exceptions", "The Helix Work Item failed. Often this is due to a test crash. Please see the 'Artifacts' tab above for additional logs."],
    "BuildRetry": false,
    "ErrorPattern": "",
    "ExcludeConsoleLog": false
 }

@dotnet/dnceng

Release Note Category

• [ ] Feature changes/additions
• [ ] Bug fixes
• [ ] Internal Infrastructure Improvements

Release Note Description

Additional information about the issue reported

No response

Known issue validation

Build: :mag_right: https://dev.azure.com/dnceng-public/public/_build/results?buildId=1094333 Error message validated: [baseservices-exceptions The Helix Work Item failed. Often this is due to a test crash. Please see the 'Artifacts' tab above for additional logs.] Result validation: :x: Known issue did not match with the provided build. Validation performed at: 7/15/2025 4:45:02 PM UTC

Report

Summary

24-Hour Hit Count	7-Day Hit Count	1-Month Count
0	0	0

[jozkee]

The console.87f9f6d3.log and the test results say it all passed, yet it was flagged as an error.

[garath]

This looks like an infrastructure problem. I see "No space left on device" errors in telemetry on the dnceng side. It's a known problem with azurelinux.3 and we are working on a solution.