investigate seemingly non-deterministic nyc output #3155
Description
I don't believe the coverage data out of nyc. I've also seen this sort of thing happen with my own two eyes.
It is likely a misconfiguration on our part, but I don't know where. It may involve the way we are aggregating the results.
I would be indebted to @bcoe if he could take a look at our command-line usage and config file. Is there something obviously amiss?
Hey, at least we aren't in sourcemap hell...