Haroon Khel

At https://github.com/adoptium/infrastructure/blob/95fb017b04f8921bfa08ff923e8a3d77f5a2a3d7/ansible/playbooks/AdoptOpenJDK_Unix_Playbook/roles/adoptopenjdk_install/tasks/main.yml#L117 (between the two tasks) there should be a task which checks for a jdk without a symlink (perhaps the task can search for `{{ path }}.*`) and removes...

So something along the lines of ``` - name: Check if jdk-{{ jdk_version }} binary is present but not symlinked shell: ls -ld {{ path }}.* >/dev/null 2>&1 failed_when: false...

The 3 machines, test-azure-win2012r2-x64-1 and -3, and test-ibmcloud-win2012r2-x64-1 have hanging processes which I can't delete as the jenkins user. The processes are ``` /Users/jenkins/workspace/Test_openjdk8_dragonwell_extended.openjdk_x86-64_windows_testList_0/openjdkbinary/j2sdk-image/bin/java /Users/jenkins/workspace/Test_openjdk11_j9_extended.functional_x86-64_windows/openjdkbinary/j2sdk-image/bin/java /e/workspace/Test_openjdk8_hs_sanity.openjdk_x86-64_windows/openjdkbinary/j2sdk-image/bin/jdb ``` respectively. I get...

I was able to kill the process running on test-ibmcloud-win2012r2-x64-1 Running the failed jenkins job on the machine https://ci.adoptopenjdk.net/job/Test_openjdk8_hs_sanity.openjdk_x86-64_windows/512/console

The hanging processes on the azure machines were ended too

Running https://ci.adoptopenjdk.net/job/Test_openjdk8_dragonwell_extended.openjdk_x86-64_windows_testList_0/9/console on test-azure-win2012r2-x64-1 and https://ci.adoptopenjdk.net/job/Test_openjdk11_j9_extended.functional_x86-64_windows/140/console on test-azure-win2012r2-x64-3

https://ci.adoptopenjdk.net/job/Test_openjdk11_j9_extended.functional_x86-64_windows/140/console failed on test-azure-win2012r2-x64-3 because it couldn't delete the workspace, strange ``` ERROR: Cannot delete workspace :Unable to delete 'C:\Users\jenkins\workspace\Test_openjdk11_j9_extended.functional_x86-64_windows'. Tried 3 times (of a maximum of 3) waiting 0.1...

On test-azure-win2012r2-x64-3, I've deleted the problem workspace, ended the hanging process and kicked off another job https://ci.adoptopenjdk.net/job/Test_openjdk11_j9_extended.functional_x86-64_windows/141/console

The job on test-ibmcloud-win2012r2-x64-1 ran without a workspace error or hanging processes. Running another job on the same machine to observe any 'failure to delete workspace' errors https://ci.adoptopenjdk.net/job/Test_openjdk8_hs_sanity.openjdk_x86-64_windows/513/console

test-ibmcloud-win2012r2-x64-1 looks to be fine. Two sanity jobs ran back to back without a workspace complaint or a hanging process