TAP output does not say which tests (or at least which file) failed after timeout

[tymfear]

So here is the output of timedout test report (there are passed tests as well).

# Exited because no new tests completed within the last 180000ms of inactivity
not ok 51 - Exited because no new tests completed within the last 180000ms of inactivity

It is impossible to figure out which test caused timeout.
Would be nice at least to narrow it down to test file, to understand where to start searching.

[novemberborn]

Yea… I think this may be a bug when you don't use verbose mode. If you try with verbose mode does it work?

[tymfear]

Well, I tried, but the output is completely the same - so either it doesn't work in verbose mode or --verbose doesn't work :)

[tymfear]

So found in docs that verbose works if tap is not enabled - and tap is enabled. But, anyway, it doesn't show where it failed (or I missed something, chances are not zero )

[tymfear]

@novemberborn would that be enough to change this
https://github.com/avajs/ava/blob/master/lib/reporters/tap.js#L174-L176

case 'timeout':
  this.writeCrash(evt, `Exited because no new tests completed within the last ${evt.period}ms of inactivity`);
  break;

to

case 'timeout':
  this.writeCrash(evt, `${evt.testFile} Exited because no new tests completed within the last ${evt.period}ms of inactivity`);
  break;

Or not so easy? 😂

[novemberborn]

Whatever you think makes sense 😄

[tymfear]

@novemberborn it's just I'm not that familiar with codebase and have no idea is that place correct - so was asking.

[novemberborn]

@tymfear looking at the snippet that seems like a good guess. I don't really know the TAP format either.

[tymfear]

@novemberborn - I'll try it out.
P.S. Just created another issue related to TAP reports generation, sorry