-
-
Notifications
You must be signed in to change notification settings - Fork 359
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Typescript reports with error: property 'start' of undefined #733
Comments
@ozum are you still running into this issue? I haven't been able to reproduce so far running |
@bcoe, I was away from that code for a while. Currently, I also cannot reproduce. I'm closing this issue. I will open another ticket, if it happens again. Thanks, |
@ozum great, might have been something that was fixed upstream 👍 |
I've encountered the same problem, I don't think it's a good practice just to close the bug rather than fixing it? |
I have encountered the same problem as well. nyc keeps giving different results everytime I run it (alternating between 100% coverage & 50% coverage) and I am faced with the same error when it fails. (However I don't use typescript) |
No action will be taken without a reproduction against latest nyc. If you are experiencing an issue please post a new issue and include all required information. |
@coreyfarrell Thanks for the reply, I've created a ticket for it #1124 |
Expected Behavior
Same report during repeated execution.
Observed Behavior
I have a code with 100% coverage. Using typescript and without changing any file, when I execute
nyc
repeatedly, I get different coverage reports.(See repo below) I executed
npm run test:cover
6-7 times repeatedly and once every few I got reports below 100%. Reports below 100% has following error in HTML reports:Bonus Points! Code (or Repository) that Reproduces Issue
https://github.com/ozum/fix-set/tree/typescript-try
Forensic Information
Operating System: MacOS 10.12.6
Environment Information:
node v9.2.0
npm v5.5.1
nyc v11.3.0 or nyc v11.4.0 (Repo has v11.4.0 in package.json)
The text was updated successfully, but these errors were encountered: