Tape and server.inject problem

[ArtZanko]

Hello.We are using tape+gulp for testing our hapi server. At first I create a mock:

var server;
serverMock(function(obj) {
        server = obj;
        test.end();
    });

serverMock is a module

var _ = require('lodash');
var Hapi = require('hapi');
var config = require('../../config');
var cacheMock = require('./cache');

module.exports = function(done) {
    var server = new Hapi.Server();

    server.connection();

    server.route(require('../../server/routes'));

    var cache = server.cache({segment: 'first', expiresIn: config.cache.expiresIn});
    cache._cache.start(_.noop); 

    var methods = require('../../server/methods');

    server.method('first.cache', methods.cache, {bind: cache});
    server.method('first.get', methods.get, {bind: cache});

    cache.set(cacheMock.id, cacheMock);

    server.start(function() {
        return done(server);
    });
};

Then test is passing. And at the end:

server.stop();

I want to notice that all tape.end() functions is called but process still alive. I think its because server keep it alive. Maybe you can help me..

[hueniverse]

You might want to give stop() a timeout option.

[ArtZanko]

Yes I did. Still doesn't work.

[hueniverse]

No idea. You can try to run the code without the testing setup just to make sure as a standalone app it runs and exits correctly.

[ArtZanko]

I tried to call server.stop in app without tesing setup and nothing happened(only stop callback was called but a process was alive).. Function server.stop should make a process exit, right?

[tthyer]

I had a similar problem using tape with hapi caching. I attempted using a timeout with stop, not starting the server and instead starting and stopping the cache itself, but still the test did not complete. I tracked the problem down to the timer set by Catbox-Memory and cleared it:
clearTimeout(server._caches._default.client.connection.cache['segmentName']['keyName'].timeoutId)
Then my test would complete.

Checking catbox-memory commits, it looks like there's a fix for this in master that hasn't been released yet.

[hueniverse]

@cjihrig what's the status of the catbox-memory fix?

[cjihrig]

I'll do a release right now.

[cjihrig]

@tthyer I just released v1.1.2 of catbox-memory. Care to give it a shot?

[tthyer]

Just confirmed that this works. Thanks!
@ArtZanko I used catbox-memory v1.1.2 as my cache engine, called server.stop and the tape test completed.

[hueniverse]

@cjihrig can you PR to update hapi with the new version

[cjihrig]

Sure thing

[ArtZanko]

Yes it works! Thank you very much!
One more question. When i call npm install hapi it install catbox-memory 1.1.1 as dependency I have to call npm update catbox-memory in hapi directory to update it. How to get catbox-memory latest version with just calling npm install in app directory?

I got it waiting for #2725

Thanks once again!