test-azure-win2012r2-x64-1 jobs failing with no space left on device errors

[smlambert]

15:28:51  Caused by: hudson.plugins.git.GitException: Command "git init D:\jenkins\workspace\Test_openjdk11_hs_sanity.openjdk_x86-32_windows\aqa-tests" returned status code 128:
15:28:51  stdout: 
15:28:51  stderr: error: copy-fd: write returned: No space left on device
15:28:51  fatal: cannot copy '/usr/share/git-core/templates/hooks/commit-msg.sample' to '/cygdrive/d/jenkins/workspace/Test_openjdk11_hs_sanity.openjdk_x86-32_windows/aqa-tests/.git/hooks/commit-msg.sample': No space left on device
15:28:51  

• test suite/name (e.g, BUILD_LIST, TARGET, CUSTOM_TARGET)? Any test job sent to the machines
• a link into recent Test_ job on https://ci.adoptopenjdk.net which showed the failure - https://ci.adoptopenjdk.net/job/Test_openjdk11_hs_sanity.openjdk_x86-32_windows/726 https://ci.adoptopenjdk.net/job/Test_openjdk11_hs_sanity.system_x86-32_windows/352 https://ci.adoptopenjdk.net/job/build-scripts/job/jobs/job/jdk11u/job/jdk11u-windows-x64-temurin_SmokeTests/99
• Hyperlink to re-run in Grinder:
• Is there an existing issue elsewhere covering this?
• Which machine(s) does it work on?
• Which machine(s) does it fail on? test-azure-win2012r2-x64-1

Other details: Will mark the machine offline to avoid other tests being sent to it and fail.

[steelhead31]

This looks like the size of the D: drive needs increasing, rather than additional housekeeping a single test run is using > 30Gb, In the interim, I'll add an additional check to this windows machines in nagios to monitor the size of D:

[sxa]

@smlambert Is this size of the working set expected for the new dev suites? We should check that we're not just creating lots of core files around or something like that (I'm not sure how much testing has been done with these suites on OpenJ9 to know if this is a symptom of a real underlying problem)

[smlambert]

New dev.system tests are loads of jcstress tests (and require some additional space during runs). dev.openjdk tests are container tests and would also have requirements, but do not run on Windows currently.

Core files should get packaged into the test artifact on the job, if they were happening and I do not see any bloat there (12-20KB on average for system_test_output.tar.gz artifacts).

[sxa]

Machine decommissioned and jstress tests have been disabled due to being resource hogs (can take up to 3 days) and are not particularly effective at identifying problems. May be useful to ensure that we can still run them on our systems for developers who want to verify that GC changes don't cause any new problems.