build-azure-win2012r2-x64-1 J:\jenkins\workspace\build-scripts\release\create_installer_windows locked and can't be deleted

[andrew-m-leonard]

Installed jobs are failing on node build-azure-win2012r2-x64-1 due to an old install output locked file within J:\jenkins\workspace\build-scripts\release\create_installer_windows locked and can't be deleted

Please can this folder be deleted?

[andrew-m-leonard]

I've disconnected until fixed: https://ci.adoptopenjdk.net/computer/build-azure-win2012r2-x64-1/

[Haroon-Khel]

jenkins@bld-2012r2-1 /cygdrive/j
$ ls -la jenkins/workspace/build-scripts/release/create_installer_windows/wix/ReleaseDir/
total 88240
drwxrwxr-x+ 1 jenkins      None                 0 Jun 15 16:51 .
drwxrwxr-x+ 1 jenkins      None                 0 Jun 16 01:48 ..
-rw-r-----  1 Unknown+User Unknown+Group 90353664 Jun 15 16:51 OpenJDK8U-jdk_x64_windows_hotspot_2022-06-15-13-34.msi

Likely caused by this file. I'll see if I can determine the reason for the Unknown+User Unknown+Group before deleting it

[Haroon-Khel]

As far as I can tell from googling, Cygwin must have hit an error when mapping windows accounts to posix accounts. Annoyingly I can't access the particular create_installer job which created that file as the job has expired. I'll delete the file for now

[Haroon-Khel]

Took a while to delete the file. It was being used by a java.exe process which refused to die. The workspace should be 'deletable' now

[Haroon-Khel]

Reopening as it occurred again. Looking into this

[andrew-m-leonard]

Cleared, now re-running multiple times to try and force

[Haroon-Khel]

Took a while to delete the file. It was being used by a java.exe process which refused to die. The workspace should be 'deletable' now

That's interesting, last week the process that was locking the directory was a leftover java.exe process, today's failure was caused by a leftover sh.exe process

[andrew-m-leonard]

The only sh.exe I can see in the log is at the end:

[create_installer_windows] $ sh -xe C:\Users\jenkins.bld-2012r2-1\AppData\Local\Temp\jenkins3919534905505936000.sh
+ set -x
+ cd wix/SourceDir/
+ for FILEWITHEXTENSION in OpenJDK*-${PRODUCT_CATEGORY}*zip
+ FILENAME=OpenJDK-jdk_x64_windows_hotspot_2022-07-01-07-52.msi
+ cd 'J:\jenkins\workspace\build-scripts\release\create_installer_windows/wix/ReleaseDir/'
+ for FILE in *.msi
+ mv OpenJDK20-jdk_x64_windows_hotspot-20.0.0.0.4.msi OpenJDK-jdk_x64_windows_hotspot_2022-07-01-07-52.msi
Installer "Extract *.zip/*.tar.gz" cannot be used to install "jdk-11.0.13+8" on the node "build-azure-win2012r2-x64-1"
Installer "Extract *.zip/*.tar.gz" cannot be used to install "jdk-11.0.13+8" on the node "build-azure-win2012r2-x64-1"
Installer "Extract *.zip/*.tar.gz" cannot be used to install "jdk-11.0.13+8" on the node "build-azure-win2012r2-x64-1"
Installer "Extract *.zip/*.tar.gz" cannot be used to install "jdk-11.0.13+8" on the node "build-azure-win2012r2-x64-1"
Installer "Extract *.zip/*.tar.gz" cannot be used to install "jdk-11.0.13+8" on the node "build-azure-win2012r2-x64-1"
Installer "Extract *.zip/*.tar.gz" cannot be used to install "jdk-11.0.13+8" on the node "build-azure-win2012r2-x64-1"
Archiving artifacts
Installer "Extract *.zip/*.tar.gz" cannot be used to install "jdk-11.0.13+8" on the node "build-azure-win2012r2-x64-1"
Installer "Extract *.zip/*.tar.gz" cannot be used to install "jdk-11.0.13+8" on the node "build-azure-win2012r2-x64-1"
Installer "Extract *.zip/*.tar.gz" cannot be used to install "jdk-11.0.13+8" on the node "build-azure-win2012r2-x64-1"
Installer "Extract *.zip/*.tar.gz" cannot be used to install "jdk-11.0.13+8" on the node "build-azure-win2012r2-x64-1"
Installer "Extract *.zip/*.tar.gz" cannot be used to install "jdk-11.0.13+8" on the node "build-azure-win2012r2-x64-1"
Installer "Extract *.zip/*.tar.gz" cannot be used to install "jdk-11.0.13+8" on the node "build-azure-win2012r2-x64-1"
[Slack Notifications] found #19139 as previous completed, non-aborted build
Finished: SUCCESS

[Haroon-Khel]

@sxa ref #2662 (comment)
Do you think you could add leftover jcmd processes to your ProcessCheck job? I see that the job currently stops java, xvfb and revokeall processes

[sxa]

@sxa ref #2662 (comment) Do you think you could add leftover jcmd processes to your ProcessCheck job? I see that the job currently stops java, xvfb and revokeall processes

Done, and it did the right thing at https://ci.adoptopenjdk.net/view/Tooling/job/SXA-processCheck/label=test-azure-win2012r2-x64-1/309/console

[Haroon-Khel]

Yep. I cant see the jcmd processes on the machine anymore. Thanks

[sxa]

Closing as this should be fixed more reliably by including jcmd in the SXA-ProcessCheck job - we can reopen again later if required.