search

SpectoLabs / hoverfly-java

Java binding for Hoverfly
Apache License 2.0
168 stars 58 forks source link

Test fail in Jenking #177

Closed naman90 closed 6 years ago

naman90 commented 6 years ago

I get the following error when jenkins is building project and run test cases.

13:58:25.058 [main] INFO io.specto.hoverfly.junit.core.TempFileManager - Selecting the following binary based on the current operating system: hoverfly_linux_amd64 13:58:25.062 [main] INFO io.specto.hoverfly.junit.core.TempFileManager - Storing binary in temporary directory /tmp/hoverfly.1856279864141179710/hoverfly_linux_amd64 13:58:25.162 [main] INFO io.specto.hoverfly.junit.core.Hoverfly - Executing binary at /tmp/hoverfly.1856279864141179710/hoverfly_linux_amd64 13:58:25.227 [main] DEBUG org.zeroturnaround.exec.ProcessExecutor - Executing [/tmp/hoverfly.1856279864141179710/hoverfly_linux_amd64, -db, memory, -pp, 42681, -ap, 46601] in /tmp/hoverfly.1856279864141179710. 13:58:25.235 [main] ERROR org.zeroturnaround.exec.ProcessExecutor - Could not start process: java.io.IOException: Cannot run program "/tmp/hoverfly.1856279864141179710/hoverfly_linux_amd64" (in directory "/tmp/hoverfly.1856279864141179710"): error=2, No such file or directory at java.lang.ProcessBuilder.start(ProcessBuilder.java:1048)

tommysitu commented 6 years ago

That's interesting. Does it fail on your local machine? Which version of Hoverfly-java are you using?

naman90 commented 6 years ago

It doesn't fail on local windows and linux machines. It is failing in a job running inside jenkins pipeline. Hoverfly java Version- 0.9.1. May be there are executable permission issues?

tommysitu commented 6 years ago

It sounds very likely to be executable permission issue, as it didn't fail at copying the binary.

tommysitu commented 6 years ago

It might be related to this one: https://github.com/jenkinsci/docker/issues/422, you can try out some of the suggestions there, like changing the tmp folder location

tommysitu commented 6 years ago

Hi @naman90 please re-open this issue if you are still having the problem.