Stewart X Addison

[It's back](https://ci.adoptopenjdk.net/computer/test-ibmcloud-win2012r2-x64-1/) and has survived a subsequent reboot to apply security updates :+1: It's running https://ci.adoptopenjdk.net/job/Test_openjdk8_hs_sanity.perf_x86-64_windows/323/console just now

Although build-ibmcloud-win2012r2-x64-2 seems to have gone offline again :-( Have pinged Adam who will try and recover it again. We should take a close look at the event log when...

@Haroon-Khel Can you see anything in the event log on the ibmcloud systems? Those machines have historically been stable enough for us.

Current offline systems: - [test-azure-win2012r2-x64-1](https://ci.adoptopenjdk.net/computer/test%2Dazure%2Dwin2012r2%2Dx64%2D1/) (Low disk space on C:) - [test-azure-win2012r2-x64-3](https://ci.adoptopenjdk.net/computer/test%2Dazure%2Dwin2012r2%2Dx64%2D3/) (Low disk space on C:) - [test-azure-win2019-x64-1](https://ci.adoptopenjdk.net/computer/test%2Dazure%2Dwin2019%2Dx64%2D1/) (Low disk space on C:) - [test-equinix-win2012r2-x64-1](https://ci.adoptopenjdk.net/computer/test%2Dequinix%2Dwin2012r2%2Dx64%2D1/) (Generally broken and likely...

Almost certainly from test cases. There are definitely ones that create files of that sort of size outside the workspace (See https://github.com/adoptium/infrastructure/issues/2448 for an issue with that on AIX when...

`.dat` files covered in the separate issue now. The Packet machine will not be re-enabled and will soon be decomissioned. Closing as the others alls eem to be live now.

It can always be overriden with `JDK7_BOOT_DIR` if needed, but I know we've tried to let the autodetection work. My preference is for it not to fall back if possible,...

> Looks like the test script needs to be updated to support the new name of the tests repo Hmmm all requests to the old repo should redirect so there...

> arm32 debian8 - Fails to download GCC 7.5 binary. URL is invalid That looks from the log as though the job was tested using a fork of the repository...

> I received this error in my own time when I was running some tests using the tests repo. This error would pop up when using the ./get.sh script. Ah...