HostActivation.Tests failing and then running out of space

[jakobbotsch]

Example pipeline run: https://dev.azure.com/dnceng-public/public/_build/results?buildId=1064157&view=results
Work item: https://helix.dot.net/api/jobs/56b2a502-f847-4dd6-9336-b1aed86e0e37/workitems/HostActivation.Tests?api-version=2019-06-17
Console log: https://helixr1107v0xdcypoyl9e7f.blob.core.windows.net/dotnet-runtime-refs-pull-116502-merge-56b2a502f8474dd693/HostActivation.Tests/1/console.1ffbf0f9.log

Notice that:

...
[EXEC <] [FAIL] [00:00:00.266] > /datadisks/disk1/work/A740094B/w/A4430943/e/test_artifacts/ihpnots4.xcj/frameworkResolution/DotNetWithNETCoreAppReleaseAndPreRelease/dotnet --roll-forward Disable /datadisks/disk1/work/A740094B/w/A4430943/e/test_artifacts/ihpnots4.xcj/frameworkResolution/FrameworkReferenceApp/FrameworkReferenceApp.dll exited with 150. Expected: 0
...
OSError: [Errno 28] No space left on device

I am not sure if the tests fail because we have already run out of space, or if we run out of space because the tests start failing. There are a few coredumps attached which could be a sign of the latter.

When this happens Helix also fails to attach the console log to the work item as the actual console log, so known error analysis won't work for this I believe.

Known Issue Error Message

Fill the error message using step by step known issues guidance.

{
  "ErrorMessage": "",
  "ErrorPattern": "",
  "BuildRetry": false,
  "ExcludeConsoleLog": false
}

Report

Summary

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

[dotnet-policy-service]

Tagging subscribers to this area: @vitek-karas, @agocke, @VSadov
See info in area-owners.md if you want to be subscribed.

[elinor-fung]

The [EXEC <] [FAIL] ... exited with 150. Expected: 0 is bad logging on the part of the test. The test is actually that the command should fail.

All the tests actually succeed.

Test Run Successful.
Total tests: 2023
     Passed: 2021
    Skipped: 2
 Total time: 1.2952 Minutes