Testem process exits (times out?) after 10s with code 1, no error

It seems to happen when my webpack process takes longer than 10s to build, I have this in my config:

{
  "framework": "tap",
  "launch_in_dev": ["PhantomJS"],
  "launch_in_ci": ["PhantomJS"],
  "src_files": ["tests/bundle.js"],
  "serve_files": ["tests/bundle.js"],
  "on_start": {
    "command": "npm run build:test:watch",
    "wait_for_text": "[built]"
  },
  "on_exit": {
    "command": "rm tests/bundle.js"
  }
}

The build:test:watch script basically does webpack --define process.env.NODE_ENV='\"test\"' tests/index.js tests/bundle.js --watch

Is there some timeout in testem that will kill the process if it doesn’t see the wait_for_text after 10s?

[stefanpenner]

ah, ya that seems like a different case then what my pr resolved. For reference, I used wtfnode to figure out what was going on.

[adamyonk]

This just won’t die! On testem 1.10.2 with the following config:

{
…
  "hook": {
    "wait_for_text_timeout": 60000
  }
}

I’m still seeing it crash quite often with this at the end of the testem log:

…
info ok 118 should have only exclude condition for less inclusive wildcard

info Browser PhantomJS finished all tests. undefined
info PhantomJS 2.1 onEnd
WARN PhantomJS closed 1
info Process PhantomJS terminated. 1 null

Is there anything else I can do to try to help debug this?