Skip to content

[CI] buildBwcOssWindowsZip failing with Illegal char < at index 32: C:\Users\jenkins\.java\java8\jre #64048

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
astefan opened this issue Oct 22, 2020 · 8 comments
Assignees
Labels
:Delivery/Build Build or test infrastructure :Delivery/Packaging RPM and deb packaging, tar and zip archives, shell and batch scripts Team:Delivery Meta label for Delivery team >test-failure Triaged test failures from CI

Comments

@astefan
Copy link
Contributor

astefan commented Oct 22, 2020

Build scan:
https://gradle-enterprise.elastic.co/s/yddbfk6f6vync
https://gradle-enterprise.elastic.co/s/o3tj4pdqxxm5k
https://gradle-enterprise.elastic.co/s/uor75gsxbbepo

Repro line:

Reproduces locally?:

Applicable branches: master

Failure history:

Failure excerpt:


:distribution:bwc:staged:buildBwcOssWindowsZip FAILED |  
-- | --
  | build complete, generating: C:\Users\jenkins\workspace\elastic+elasticsearch+master+multijob-windows-compatibility\os\windows-2019\build\307.tar.bz2 |  
  |   |  
  | FAILURE: Build failed with an exception. |  
  |   |  
  | * What went wrong: |  
  | Execution failed for task ':distribution:bwc:staged:buildBwcOssWindowsZip'. |  
  | > Could not determine the details of Java installation in directory C:\Users\jenkins\.java\java8. |  
  | > Illegal char < |  
  | > at index 32: C:\Users\jenkins\.java\java8\jre

..........


Caused by: java.nio.file.InvalidPathException: Illegal char < |  
-- | --
  | > at index 32: C:\Users\jenkins\.java\java8\jre |  
  |   |  
  | at java.base/sun.nio.fs.WindowsPathParser.normalize(WindowsPathParser.java:182) |  
  | at java.base/sun.nio.fs.WindowsPathParser.parse(WindowsPathParser.java:153) |  
  | at java.base/sun.nio.fs.WindowsPathParser.parse(WindowsPathParser.java:77) |  
  | at java.base/sun.nio.fs.WindowsPath.parse(WindowsPath.java:92) |  
  | at java.base/sun.nio.fs.WindowsFileSystem.getPath(WindowsFileSystem.java:229) |  
  | at java.base/java.nio.file.Path.of(Path.java:147) |  
  | at java.base/java.nio.file.Paths.get(Paths.java:69) |  
  | at org.gradle.jvm.toolchain.internal.JavaInstallationProbe$ProbeResult.getJavaHome(JavaInstallationProbe.java:100) |  
  | at org.gradle.jvm.toolchain.internal.DefaultJavaInstallationRegistry$DefaultJavaInstallation.<init>(DefaultJavaInstallationRegistry.java:106) |  
  | at org.gradle.jvm.toolchain.internal.DefaultJavaInstallationRegistry$1.call(DefaultJavaInstallationRegistry.java:77)


@astefan astefan added :Delivery/Build Build or test infrastructure :Delivery/Packaging RPM and deb packaging, tar and zip archives, shell and batch scripts >test-failure Triaged test failures from CI labels Oct 22, 2020
@elasticmachine
Copy link
Collaborator

Pinging @elastic/es-core-infra (:Core/Infra/Packaging)

@elasticmachine
Copy link
Collaborator

Pinging @elastic/es-core-infra (:Core/Infra/Build)

@elasticmachine elasticmachine added the Team:Core/Infra Meta label for core/infra team label Oct 22, 2020
@rjernst
Copy link
Member

rjernst commented Oct 22, 2020

@breskeby Can you take a look? Seems like an issue with the java home we pull for building bwc distros, specifically on windows CI hosts.

@davidkyle
Copy link
Member

Task :distribution:bwc:maintenance:buildBwcOssZip is also failing with the same error.

https://gradle-enterprise.elastic.co/s/fcbt2somad2wc
https://gradle-enterprise.elastic.co/s/rqr52nupnh4ea
https://gradle-enterprise.elastic.co/s/ccqw7gdgayylo

breskeby added a commit that referenced this issue Oct 26, 2020
breskeby added a commit that referenced this issue Oct 28, 2020
Moving back to Gradle 6.6.1 till #64048 is resolved which seem to be root caused by updating to gradle 6.7
breskeby added a commit to breskeby/elasticsearch that referenced this issue Oct 28, 2020
…64300)

Moving back to Gradle 6.6.1 till elastic#64048 is resolved which seem to be root caused by updating to gradle 6.7
breskeby added a commit that referenced this issue Oct 28, 2020
…64303)

Moving back to Gradle 6.6.1 till #64048 is resolved which seem to be root caused by updating to gradle 6.7
@breskeby
Copy link
Contributor

should be fixed by moving back to gradle 6.6.1 on master and 7.x branches. I'll close this once all ci builds have passed

@jtibshirani
Copy link
Contributor

I think another failure just popped up on CI: https://gradle-enterprise.elastic.co/s/evort4spsvx6g

@breskeby
Copy link
Contributor

breskeby commented Nov 2, 2020

@jtibshirani that is a different issue you see which should also be fixed by now. I'm closing this as windows CI jobs are passing again after the gradle downgrade

@breskeby breskeby closed this as completed Nov 2, 2020
@mark-vieira mark-vieira added Team:Delivery Meta label for Delivery team and removed Team:Core/Infra Meta label for core/infra team labels Nov 11, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
:Delivery/Build Build or test infrastructure :Delivery/Packaging RPM and deb packaging, tar and zip archives, shell and batch scripts Team:Delivery Meta label for Delivery team >test-failure Triaged test failures from CI
Projects
None yet
Development

No branches or pull requests

7 participants