Closed M-Davies closed 4 years ago
Builds on 27th may were ok. The 28th was when we first started seeing these failures
It was caused by https://github.com/AdoptOpenJDK/openjdk-tests/pull/1794. I was looking in the wrong repo 😅
ping @AdamBrousseau
Looks like HOME
doesn't exist on Windows https://superuser.com/questions/607105/is-the-home-environment-variable-normally-set-in-windows. We would have to add in an alternative variable for windows tests. I'll see if I can make a draft PR before Canada wakes up
From memory I think it's HOMEPATH
or something like that on Windows
https://github.com/AdoptOpenJDK/openjdk-tests/pull/1794
Do test jobs also fail at the openj9 and internal servers? or have those machines been configured differently?
I think this is due to a pending script approval at the Jenkins server, which I will check for.
Edit: no pending approvals, someone else must have approved the testJobTemplate change (from #1794) already.
From a test job at openj9 project:
@sxa Do we set the HOME
variable in our playbooks (or at any point prior to kick_off_build)?
I can see that we set HOME for windows playbook testing https://github.com/AdoptOpenJDK/openjdk-infrastructure/blob/8b955671b060eef7770febec312172b270ecc48c/ansible/pbTestScripts/testJDKWin.sh#L5
@M-Davies It's standard on all UNIX systems (I would expect this to include cygwin) so no it's not something we set
(Not sure what you were referencing in that link - that line is moving something into $HOME, not setting it to anything)
Odd that it's not picking it up. HOME is set on the last passing test scripts e.g. https://ci.adoptopenjdk.net/job/Test_openjdk11_j9_sanity.openjdk_x86-64_windows_xl/223/console
15:13:45 HOME=/home/jenkins
Platform: All Windows builds and versions Architecture: All archs and variants
Windows builds are completely broken this morning across the nightlies. Exhibit A: https://ci.adoptopenjdk.net/view/Test_openjdk/job/Test_openjdk8_j9_sanity.openjdk_x86-64_windows/211/console