Skip to content
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

Execution failed for task ':test:fixtures:krb5kdc-fixture:extractJar' #33201

Closed
javanna opened this issue Aug 28, 2018 · 4 comments · Fixed by #33272
Closed

Execution failed for task ':test:fixtures:krb5kdc-fixture:extractJar' #33201

javanna opened this issue Aug 28, 2018 · 4 comments · Fixed by #33272
Assignees
Labels
:Delivery/Build Build or test infrastructure Team:Delivery Meta label for Delivery team >test-failure Triaged test failures from CI

Comments

@javanna
Copy link
Member

javanna commented Aug 28, 2018

This one failed four times in the last ten days. Last two failures are:

https://elasticsearch-ci.elastic.co/job/elastic+elasticsearch+master+multijob-unix-compatibility/os=centos/2628/console
https://elasticsearch-ci.elastic.co/job/elastic+elasticsearch+master+multijob-unix-compatibility/os=centos/2637/console

Looks like a test infra problem:

02:53:54 java.nio.file.NoSuchFileException: /var/lib/jenkins/workspace/elastic+elasticsearch+master+multijob-unix-compatibility/os/centos/test/fixtures/krb5kdc-fixture/build/distributions/krb5kdc-fixture-7.0.0-alpha1-SNAPSHOT.jar
02:53:54 	at java.base/sun.nio.fs.UnixException.translateToIOException(UnixException.java:92)
02:53:54 :test:fixtures:krb5kdc-fixture:extractJar (Thread[Task worker for ':' Thread 6,5,main]) completed. Took 0.095 secs.
02:53:54 3917 actionable tasks: 2565 executed, 1352 up-to-date
02:53:54 	at java.base/sun.nio.fs.UnixException.rethrowAsIOException(UnixException.java:111)
02:53:54 	at java.base/sun.nio.fs.UnixException.rethrowAsIOException(UnixException.java:116)
02:53:54 	at java.base/sun.nio.fs.UnixFileAttributeViews$Basic.readAttributes(UnixFileAttributeViews.java:55)
02:53:54 	at java.base/sun.nio.fs.UnixFileSystemProvider.readAttributes(UnixFileSystemProvider.java:145)
02:53:54 	at java.base/sun.nio.fs.LinuxFileSystemProvider.readAttributes(LinuxFileSystemProvider.java:99)
02:53:54 	at java.base/java.nio.file.Files.readAttributes(Files.java:1755)
02:53:54 	at java.base/java.util.zip.ZipFile$Source.get(ZipFile.java:1220)
02:53:54 	at java.base/java.util.zip.ZipFile$CleanableResource.<init>(ZipFile.java:727)
02:53:54 	at java.base/java.util.zip.ZipFile$CleanableResource.get(ZipFile.java:845)
02:53:54 	at java.base/java.util.zip.ZipFile.<init>(ZipFile.java:245)
02:53:54 	at java.base/java.util.zip.ZipFile.<init>(ZipFile.java:175)
02:53:54 	at java.base/java.util.zip.ZipFile.<init>(ZipFile.java:146)
02:53:54 	at jdk.jartool/sun.tools.jar.Main.extract(Main.java:1377)
02:53:54 	at jdk.jartool/sun.tools.jar.Main.run(Main.java:396)
02:53:54 	at jdk.jartool/sun.tools.jar.Main.main(Main.java:1669)
@javanna javanna added :Delivery/Build Build or test infrastructure >test-failure Triaged test failures from CI labels Aug 28, 2018
@elasticmachine
Copy link
Collaborator

Pinging @elastic/es-core-infra

@alpar-t
Copy link
Contributor

alpar-t commented Aug 30, 2018

Looking at the logs, :test:fixtures:krb5kdc-fixture:jar never ran, despite the extractJar task having dependsOn jarTask. Indeed checking on the build machine, the Jar is not there, only the src and doc jars are. I suspect this is a bug in Gradle around lazy task evaluation introduced in 4.8 and publicized in 4.9. We recently updated to 4.10 which might have fixed it.

In general it's very time consuming to create reproductions for intermittent issues like this one, instead I will remove the failing tasks completely because:

  • there's no up to date checking on them - so it does needles work when running check on dev machines
  • it does the extract in an external process, which takes more time
  • but most importantly, we have testkit now and that's a better place to assert that the build plugin does indeed add those files.

@nik9000
Copy link
Member

nik9000 commented Aug 31, 2018

This reproduces consistently for me on 6.x on my desktop. If you want access I can give it. But if you are removing the tasks you probably don't need it.

@javanna
Copy link
Member Author

javanna commented Aug 31, 2018

I have exactly the same on my box, whenever I build 6.x. I talked to Alpar about it yesterday. His PR should address it.

alpar-t added a commit that referenced this issue Sep 3, 2018
Remove tasks to check license and notice and add build integration test instead.

Closes #33201
alpar-t added a commit that referenced this issue Sep 3, 2018
Remove tasks to check license and notice and add build integration test instead.

Closes #33201
@mark-vieira mark-vieira added the Team:Delivery Meta label for Delivery team label 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 Team:Delivery Meta label for Delivery team >test-failure Triaged test failures from CI
Projects
None yet
Development

Successfully merging a pull request may close this issue.

5 participants