-
Notifications
You must be signed in to change notification settings - Fork 344
Gauge (v. 1.1.8) with Java (v. 0.7.13) in Kubernetes #1969
Replies: 2 comments · 1 reply
-
Hi, I was really hoping that someone who's deployed Gauge in k8s can pitch in. I don't have access to a k8s cluster, but can do my best and work with you on this. I admit I've never seen that stacktrace before. It seems that the gauge-java launcher could not start the java process that hosts the runner and your test code. Do you see any details in the |
Beta Was this translation helpful? Give feedback.
All reactions
-
Hi, thx for your reply, we can see a lot of log files in our workspace, such as gauge.log, .*-java.out files:
I wil just print some of the log files:
Hopefully these logs can help you or can give you any hint? Best regards |
Beta Was this translation helpful? Give feedback.
All reactions
-
Hi, FYI, this issue has been resolved. The problem was caused by Instana, a monitoring tool with auto-instrumentation capabilities. Instana attaches to all JVMs running on a host. The process of dynamically attaching to a JVM includes sending a SIGQUIT signal. Unfortunately, Instana detected gauge-java as a JVM process which caused the behaviour described above. Thanks |
Beta Was this translation helpful? Give feedback.
All reactions
-
👍 1
-
Hi at all,
we are trying to run Gauge Tests in Kubernetes provisioned by Jenkins, but we fail, as we receive a strange exception, maybe some can give us a helpful hint.
Our setup:
Is our setup working?
Yes, we think so, when we downloaded an Example of GaugeTests (https://github.com/mstykt/gauge-demo) and let it run in our setup, the tests are running and we receive a report, so this shouldn't be the problem.
What did we tried to fix it:
Open questions?
Best regards
Beta Was this translation helpful? Give feedback.
All reactions