Closed nktch1 closed 11 months ago
Nothing obvious stands out to me. It doesn't start any separate processes like on the consumer side (with the mock provider).
I would fork the pact-ruby gem, and add a bunch of puts into the following classes to see if you can work out where it stops.
Then in your Gemfile, use your forked repo by configuring gem "pact", git: "https://github.com/<your org>/pact-ruby"
Hi, this fix worked for us, for some reason exit exit_code
was not working as expected.
https://github.com/ilyasovd/pact-ruby/commit/5aba022ffd3d8de3fdeb38c05558973d907c028f
Very odd. You're welcome to submit a PR with that change if you'd like it to be part of the standard ruby gem. It should be exactly the same thing!
Hey, guys! I have a problem. I am using gem ruby pact 1.63.0. I run provider tests locally in a container and they complete successfully. But. When I try to run them in a Gitlab runner, the tests run successfully, the results are sent to the broker, but then the rails pact:verify command just hangs. The job only completes on timeout.
Maybe you have some ideas?
I attach pact file, provider test code, logs on local computer in container and logs in runner.
pact.json
pact_helper.rb
pact_test.rb
Gitlab runner output: