Report has bogus uncovered lines report

[aredridel]

Files in .nyc_output are at https://gist.github.com/aredridel/67a635a727047e541c32

Output:

:; nyc report
------------|----------|----------|----------|----------|----------------|
File        |  % Stmts | % Branch |  % Funcs |  % Lines |Uncovered Lines |
------------|----------|----------|----------|----------|----------------|
 __root__/  |    94.92 |    81.13 |      100 |    94.92 |                |
  common.js |    94.37 |    69.23 |      100 |    94.37 | 94,146,150,154 |
  index.js  |    95.74 |    92.59 |      100 |    95.74 |          48,68 |
------------|----------|----------|----------|----------|----------------|
All files   |    94.92 |    81.13 |      100 |    94.92 |                |
------------|----------|----------|----------|----------|----------------|

[bcoe]

@aredridel are you running nyc on an open-source project? This could relate to a subprocess we're failing to cover, or a code path that's difficult to hit during the spawning process.

[aredridel]

Yeah, this is on https://github.com/aredridel/dust-makara-helpers/tree/browser-support

[aredridel]

Oh! That's not a number of uncovered lines. That's a list of them. Geez.

[aredridel]

I thought it was literally calculating 94 billion uncovered lines.

[aredridel]

Okay, this is not a bug. This is me misunderstanding the information in that column since it happened to parse as a number with thousands separators.

[bcoe]

@aredridel what do you think a better heading would be? a similar issue was here:

gotwarlost/istanbul#390

we should be more clear!

[aredridel]

If there'd been spaces instead of commas it'd have been clear for me; not sure how that'd be interpreted internationally.

[aredridel]

"Which lines uncovered" would have made it clear too.

[willhayslett]

I know this is old, but I ran into this and was so confused. How about "Uncovered Line #'s" or "Uncovered Line Numbers"? "Uncovered Lines" isn't very clear.