Slow Pact Mock Server results in timeout

[mefellows]

See https://groups.google.com/forum/#!topic/pact-support/53nMFlG3EGY for background.

[mboudreau]

Released a fix, 4.5.2, bit not positive if it will fix the issue. Added a test to add a delay for server initialization.

[willfalconer]

Thanks @mboudreau, unfortunately the issue has not been resolved.

[mboudreau]

@ScrumTech can you please set the log level to debug and post what's shown?

pact.logLevel('debug');

[willfalconer]

vagrant@vagrant-ubuntu-trusty-64:/vagrant$ npm t

> test-pact@1.0.0 test /vagrant
> node_modules/mocha/bin/mocha --compilers js:babel-register src/.mocha.js ./src/workItemServce.test.js

[2016-08-29T23:07:17.250Z]  INFO: pact-node@4.5.2/1797 on vagrant-ubuntu-trusty-64:
    Creating Pact Server with options:
    port = 9000,
    host = localhost,
    dir = /vagrant/pacts,
    ssl = false,
    cors = false,
    log = /vagrant/logs/mockserver-integration.log,
    spec = 2,
    consumer = ,
    provider =


  test pact
    with a single request
[2016-08-29T23:07:17.277Z]  INFO: pact-node@4.5.2/1797 on vagrant-ubuntu-trusty-64: Creating Pact with PID: 1802
[2016-08-29T23:07:19.845Z] DEBUG: pact-node@4.5.2/1797 on vagrant-ubuntu-trusty-64:
    /vagrant/node_modules/@pact-foundation/pact-mock-service-linux-x64/lib/ruby/lib/ruby/gems/2.1.0/gems/bundler-1.7.12/lib/bundler/runtime.rb:222: warning: Insecure world writable dir /vagrant/node_modules/.bin in PATH, mode 040777

[2016-08-29T23:07:24.694Z] DEBUG: pact-node@4.5.2/1797 on vagrant-ubuntu-trusty-64:
    [2016-08-29 23:07:24] INFO  WEBrick 1.3.1
    [2016-08-29 23:07:24] INFO  ruby 2.1.5 (2014-11-13) [x86_64-linux]

[2016-08-29T23:07:24.695Z] DEBUG: pact-node@4.5.2/1797 on vagrant-ubuntu-trusty-64:
    [2016-08-29 23:07:24] INFO  WEBrick::HTTPServer#start: pid=1803 port=9000

      1) "before each" hook for "successfully verifies"
[2016-08-29T23:07:47.295Z]  INFO: pact-node@4.5.2/1797 on vagrant-ubuntu-trusty-64: Removing Pact with PID: 1802
[2016-08-29T23:07:47.298Z] DEBUG: pact-node@4.5.2/1797 on vagrant-ubuntu-trusty-64:
    [2016-08-29 23:07:47] INFO  going to shutdown ...
    [2016-08-29 23:07:47] INFO  WEBrick::HTTPServer#start done.

[2016-08-29T23:07:47.301Z]  INFO: pact-node@4.5.2/1797 on vagrant-ubuntu-trusty-64:
    Deleting Pact Server with options:
    port = 9000,
    host = localhost,
    dir = /vagrant/pacts,
    ssl = false,
    cors = false,
    log = /vagrant/logs/mockserver-integration.log,
    spec = 2,
    consumer = ,
    provider =
[2016-08-29T23:07:47.305Z]  INFO: pact-node@4.5.2/1797 on vagrant-ubuntu-trusty-64: Removing all Pact servers.


  0 passing (30s)
  1 failing

  1) test pact "before each" hook for "successfully verifies":
     Error: timeout of 30000ms exceeded. Ensure the done() callback is being called in this test.




[2016-08-29T23:07:47.319Z]  INFO: pact-node@4.5.2/1797 on vagrant-ubuntu-trusty-64: Removing all Pact servers.
npm ERR! Test failed.  See above for more details.

[mboudreau]

@ScrumTech have you tried not setting up a directory?

[mboudreau]

@ScrumTech seems to me that the pact binary dies before you even start your tests. Maybe you should try to run the binary directly without going through pact-node with the same options. The binary is available under node_modules/@pact-foundation/pact-node/node_modules/@pact-foundation/pact-mock-service/bin

[mefellows]

I spoke to Wil on this and as I understand the Pact Binary runs just fine.

Looking at those logs, the service comes up at 23:07:24 and shuts down 23
seconds later at 23:07:47. So it is up, but for some reason the 'start'
event is never fired and the promise is never fulfilled. weird.

On Wed, Aug 31, 2016 at 10:17 AM, Michel Boudreau notifications@github.com
wrote:

@ScrumTech https://github.com/scrumtech seems to me that the pact
binary dies before you even start your tests. Maybe you should try to run
the binary directly without going through pact-node with the same options.
The binary is available under node_modules/@pact-foundation/
pact-node/node_modules/

—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
#20 (comment),
or mute the thread
https://github.com/notifications/unsubscribe-auth/AADSjL6OZQgy9FPfDF8fxtq23CHoFxdUks5qlMgbgaJpZM4Jsnni
.

Matt Fellows

• http://www.onegeek.com.au/

[mboudreau]

Hm, right. On the pact-node side, it calls the service to check that it's actually up (there's no other way of knowing). It could be that there's a weird network thing that it can't call pact from the node wrapper.

I might have to try this out further, however, I don't want to have to create a vagrant box to replicate. Can this be replicated using Docker?

[mefellows]

I'm working on a Docker setup for you now @mboudreau... standby.

[mefellows]

OK, I've ported it to Docker (still works, sorry), and here is the Dockerfile.

FROM ubuntu:trusty

RUN mkdir -p /vagrant/.vagrant-config/
RUN mkdir -p /home/vagrant/
COPY . /vagrant
RUN chmod +x /vagrant/.vagrant-config/*.sh
RUN /vagrant/.vagrant-config/provision.sh
RUN /vagrant/.vagrant-config/node_install.sh
WORKDIR /vagrant
RUN npm i
RUN npm t

Steps to run the tests:

docker build -t test-pact .
docker run -it test-pact bash
# now in shell...
npm t

Additionally, I had to replace the newer version of ruby on line 14 of provision.sh, with apt-get install -y ruby2.0 ruby2.0-dev. This of course may well be the original problem (although it didn't seem to effect me). Worth looking into.

@ScrumTech keen to see if you get the same error on Docker or if it disappears!

[mboudreau]

Why did you have to install Ruby? We don't need it for pact-node...

On Wed, Aug 31, 2016, 8:47 PM Matt Fellows notifications@github.com wrote:

OK, I've ported it to Docker (still works, sorry), and here is the
Dockerfile.

FROM ubuntu:trusty

RUN mkdir -p /vagrant/.vagrant-config/
RUN mkdir -p /home/vagrant/
COPY . /vagrant
RUN chmod +x /vagrant/.vagrant-config/*.sh
RUN /vagrant/.vagrant-config/provision.sh
RUN /vagrant/.vagrant-config/node_install.sh
WORKDIR /vagrant
RUN npm i
RUN npm t

Steps to run the tests:

docker build -t test-pact .
docker run -it test-pact bash

now in shell...

npm t

Additionally, I had to replace the newer version of ruby on line 14 of
provision.sh, with apt-get install -y ruby2.0 ruby2.0-dev. This of course
may well be the original problem (although it didn't seem to effect me).
Worth looking into.

@ScrumTech https://github.com/scrumtech keen to see if you get the same
error on Docker or if it disappears!

—
You are receiving this because you were mentioned.

Reply to this email directly, view it on GitHub
#20 (comment),
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAjA5B3GgQLaLcDGsSUBosFjoVC2h9g5ks5qlVusgaJpZM4Jsnni
.

[mefellows]

I think it's just part of a default image type thing. As I understand it's
part of their dev environment as their SOE is Windows, so they need a
linux-env to do a lot of this fun new stuff.

In any case, if it is Ruby that's the cause (I'm doubtful as it worked for
me, but remain open and skeptical) we want to know about any conflicts.

On Wed, Aug 31, 2016 at 9:18 PM, Michel Boudreau notifications@github.com
wrote:

Why did you have to install Ruby? We don't need it for pact-node...

On Wed, Aug 31, 2016, 8:47 PM Matt Fellows notifications@github.com
wrote:

OK, I've ported it to Docker (still works, sorry), and here is the
Dockerfile.

FROM ubuntu:trusty

RUN mkdir -p /vagrant/.vagrant-config/
RUN mkdir -p /home/vagrant/
COPY . /vagrant
RUN chmod +x /vagrant/.vagrant-config/*.sh
RUN /vagrant/.vagrant-config/provision.sh
RUN /vagrant/.vagrant-config/node_install.sh
WORKDIR /vagrant
RUN npm i
RUN npm t

Steps to run the tests:

docker build -t test-pact .
docker run -it test-pact bash

now in shell...

npm t

Additionally, I had to replace the newer version of ruby on line 14 of
provision.sh, with apt-get install -y ruby2.0 ruby2.0-dev. This of course
may well be the original problem (although it didn't seem to effect me).
Worth looking into.

@ScrumTech https://github.com/scrumtech keen to see if you get the
same
error on Docker or if it disappears!

—
You are receiving this because you were mentioned.

Reply to this email directly, view it on GitHub
<https://github.com/pact-foundation/pact-node/issues/
20#issuecomment-243727756>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/
AAjA5B3GgQLaLcDGsSUBosFjoVC2h9g5ks5qlVusgaJpZM4Jsnni>
.

—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
#20 (comment),
or mute the thread
https://github.com/notifications/unsubscribe-auth/AADSjPjTPepwHFcEm6ZtRf9gEA9_5op7ks5qlWMXgaJpZM4Jsnni
.

Matt Fellows

• http://www.onegeek.com.au/

[mboudreau]

This is getting weird and frustrating that we can't reproduce this anywhere... I've seen this for months and only affects certain people.