inactivity warning does help drill down the issue

[gauntface]

Description

A project I'm working is intermittently displaying this error:

Exited because no new tests completed within the last 10000ms of inactivity

Sometimes duplicate entries are display with the same warning (I'm assuming it's something in a few of our tests that is causing this).

The problem is this error message doesn't callout which files, tests or test step (before, beforeEach, after, etc) that are being problematic.

Test Source

The tests are here: https://github.com/PolymerLabs/project-health/tree/master/src/test

Error Message & Stack Trace

 [email protected] test:ava /home/travis/build/PolymerLabs/project-health
> nyc --reporter=text --reporter=html ava 'build/**/*-test.js' --verbose "--timeout=10sec"
  ✔ cli › metrics › review-coverage-test › gen-typescript-declarations review coverage (1.1s)
  ✔ cli › metrics › issue-count-test › WebComponents issue count (3.3s)
  ✔ cli › metrics › review-coverage-test › webcomponents.org review coverage (2.9s)
  ✔ server › util › my-repos-test › top contributed repos for samuelli (3.2s)
  ✔ server › models › userModel-test › should return null for no user (195ms)
  ✔ server › models › userModel-test › should return data for existing user (348ms)
  ✔ server › models › userModel-test › should return a new user token (568ms)
  ✔ server › models › userModel-test › should return null for no token
  ✔ server › models › userModel-test › should return null for token that doesnt exit
  ✔ server › models › userModel-test › should return null for token that has no username (220ms)
  ✔ server › models › userModel-test › should return null for token that has username but no user info (221ms)
  ✔ server › models › PushSubscriptionModel-test › getSubscriptionsForUser, addPushSubscription and removeSubscriptionForUser test (1.1s)
  ✔ server › models › pullRequestsModel-test › should return null for no commits (273ms)
  ✔ server › models › pullRequestsModel-test › should set, get and delete commit details (592ms)
  ✔ server › models › hooksModel-test › should return true for new (199ms)
  ✔ server › models › hooksModel-test › should set, get and delete commit details (464ms)
  ✔ server › dash-server-test › /webhook/ ping should return 200 (217ms)
  ✔ server › models › hooksModel-test › should clean old commit details (775ms)
  ✖ Exited because no new tests completed within the last 10000ms of inactivity
  ✔ project-setup-test › should skip all top level directories
  ✔ server › apis › incoming-prs-test › dashincoming: sane output
  ✔ server › apis › incoming-prs-test › dashincoming: incoming PRs are ordered
  ✔ server › apis › incoming-prs-test › dashincoming: Incoming PR with old @mention before I reviewed
  ✔ server › apis › incoming-prs-test › dashincoming: Incoming PR with new @mention after I reviewed
  ✔ server › apis › incoming-prs-test › dashincoming: Incoming PR that I reviewed. New commit since
  ✔ server › apis › incoming-prs-test › dashincoming: Incoming PR, I requested changes
  ✔ server › apis › incoming-prs-test › dashincoming: Incoming review request
  ✖ Exited because no new tests completed within the last 10000ms of inactivity
  ✖ Exited because no new tests completed within the last 10000ms of inactivity
  26 tests passed
  3 uncaught exceptions

Config

Nothing in package.json

Command-Line Arguments

Copy your npm build scripts or the ava command used:

nyc --reporter=text --reporter=html ava 'build/**/*-test.js' --verbose "--timeout=10sec"

Relevant Links

• https://github.com/PolymerLabs/project-health

[novemberborn]

Could you give #1722 a try? I think it should fix the repeated timeout exits.

I just need to do a final refactor of the reporters before landing that PR. This refactor will make #583 much easier to implement, which would provide the information you're looking for.

(I'm closing this issue for housekeeping purposes, but let's keep the conversation going.)

[gauntface]

Just hit this issue again and it looks like a stack trace was display that helped be dig into the problem so thank you.

Is there any way the message could include the specific tests or test files that should be running but aren't? I'm assuming Ava knows what they are.

[novemberborn]

Is there any way the message could include the specific tests or test files that should be running but aren't? I'm assuming Ava knows what they are.

#583 covers that.