nyc on Windows shows 0 coverage #1381

osher · 2021-01-14T22:36:58Z

Link to bug demonstration repository

https://github.com/mariszin/nyc-coverage-0-sample

(Taken from #1076...)

Expected Behavior

After tests, nyc should show 100% coverage

Observed Behavior

When running tests on Windows, the coverage is 0. Not even after upgrading to nyc@15

C:\ws\nyc-coverage-0-sample>nyc mocha


  HelloWorld
    √ should return hello world with no arguments
    √ should return passed argument


  2 passing (6ms)

---------------|----------|----------|----------|----------|-------------------|
File           |  % Stmts | % Branch |  % Funcs |  % Lines | Uncovered Line #s |
---------------|----------|----------|----------|----------|-------------------|
All files      |        0 |        0 |        0 |        0 |                   |
 helloWorld.js |        0 |        0 |        0 |        0 |         1,2,3,5,9 |
---------------|----------|----------|----------|----------|-------------------|


C:\ws\nyc-coverage-0-sample>npm ls nyc
[email protected] C:\nyc-coverage-0-sample
`-- [email protected]


C:\ws\nyc-coverage-0-sample>npm i nyc@15 --save-dev
npm WARN [email protected] No description                                                                                                                                          bel\helper-module-transforms-1c5a7680 (356ms)
npm WARN [email protected] No repository field.

+ [email protected]
added 65 packages from 26 contributors, removed 29 packages and updated 25 packages in 11.652s

25 packages are looking for funding
  run `npm fund` for details


C:\ws\nyc-coverage-0-sample>nyc mocha


  HelloWorld
    √ should return hello world with no arguments
    √ should return passed argument


  2 passing (7ms)

---------------|---------|----------|---------|---------|-------------------
File           | % Stmts | % Branch | % Funcs | % Lines | Uncovered Line #s
---------------|---------|----------|---------|---------|-------------------
All files      |       0 |        0 |       0 |       0 |
 helloWorld.js |       0 |        0 |       0 |       0 | 1-9
---------------|---------|----------|---------|---------|-------------------

Troubleshooting steps

still occurring when I put cache: false in my nyc config

Environment Information

C:\ws\nyc-coverage-0-sample>npx envinfo@latest --preset nyc
'npx' is not recognized as an internal or external command,
operable program or batch file.

C:\ws\nyc-coverage-0-sample>npm i -g envinfo
C:\Program Files (x86)\Nodist\bin\envinfo -> C:\Program Files (x86)\Nodist\bin\node_modules\envinfo\dist\cli.js                                                                       node_modules\.staging
+ [email protected]
added 1 package from 1 contributor in 0.862s

C:\ws\nyc-coverage-0-sample>envinfo --preset nyc

  System:
    OS: Windows 10 10.0.19041
    CPU: (8) x64 Intel(R) Core(TM) i7-8550U CPU @ 1.80GHz
    Memory: 2.95 GB / 15.85 GB
  Binaries:
    Node: 12.18.4 - C:\Program Files (x86)\Nodist\bin\node.EXE
    npm: 6.14.6 - C:\Program Files (x86)\Nodist\bin\npm.EXE
  npmPackages:
    nyc: ^15.1.0 => 15.1.0

The text was updated successfully, but these errors were encountered:

osher · 2021-01-17T13:46:53Z

yea, I know it's frustrating, I saw how the other issue fell in the abyss.
but I would like to help with that - and I'm ready for a lot:

we can exchange quicker correspondences in a personal channel
we can setup a google-meet/zoom and share screen if that will help
I can also do the PR and pass your CI f you'll only point me in the right direction and save me time of getting in to this so I understand what I'm looking for

Osher

osher · 2021-01-31T16:06:42Z

I'm still standing, yea yea yea...

osher · 2021-02-11T16:05:37Z

Oh, aaai - I'm still alive, yeeoo

PhakornKiong · 2021-02-12T18:17:46Z

I was not able to reproduce the error by cloning and running it on my own machine.

I've tried both v14 and v15, it is working as intended.

nyc mocha



  HelloWorld
    √ should return hello world with no arguments
    √ should return passed argument


  2 passing (15ms)

---------------|---------|----------|---------|---------|-------------------
File           | % Stmts | % Branch | % Funcs | % Lines | Uncovered Line #s
---------------|---------|----------|---------|---------|-------------------
All files      |     100 |      100 |     100 |     100 |
 helloWorld.js |     100 |      100 |     100 |     100 |
---------------|---------|----------|---------|---------|-------------------

  System:
    OS: Windows 10 10.0.21286
    CPU: (12) x64 Intel(R) Core(TM) i7-9750H CPU @ 2.60GHz
    Memory: 5.58 GB / 15.86 GB
  Binaries:
    Node: 15.0.1 - E:\CodeProgram\Node\node.EXE
    npm: 7.5.2 - E:\CodeProgram\Node\npm.CMD
  npmPackages:
    nyc: ^14.0.0 => 14.0.0

osher · 2021-02-18T08:48:56Z

WTF. I also just cloned a project where it worked on windows.
It tried on v15.1, v15.1 and v14 and they all worked, the culprit is not there.

I'll find the differences and update, but will be able to do it next week.

osher · 2021-02-22T09:58:11Z

bullseye! 🎯
I manage to find a reproduction scenario. @Darkripper214 - lets hope it's the only one.

First - disclaimer

when I posted the issue I edited out parts from the paths because I did not think it makes a difference.
But evidently, it did, because one of the edited out path folders was a symlink (junction).

I use a symlink because the ops guys destroyed my name when creating my ldap username. By the time I got to open a ticket to fix that - they could fix everything except for the original underlying LDAP username - and sadly, that happens a lot with my consultation customers.
So I hide it with a symlink, and since I did not want my name in the bug description - I edited it out.

Anyway - see for yourself:

reproduction scenario

C:\git clone https://github.com/mariszin/nyc-coverage-0-sample 
//... bla bla bla...
C:\cd nyc-coverage-0-sample
C:\nyc-coverage-0-sample>npm i
// ... bla bla bla ...
C:\nyc-coverage-0-sample>nyc mocha

  HelloWorld
    √ should return hello world with no arguments
    √ should return passed argument


  2 passing (14ms)

---------------|---------|----------|---------|---------|-------------------
File           | % Stmts | % Branch | % Funcs | % Lines | Uncovered Line #s
---------------|---------|----------|---------|---------|-------------------
All files      |     100 |      100 |     100 |     100 |
 helloWorld.js |     100 |      100 |     100 |     100 |
---------------|---------|----------|---------|---------|-------------------

C:\nyc-coverage-0-sample>cd ..
C:\>mklink /J nyc-coverage-0-sample-symlink nyc-coverage-0-sample
Junction created for nyc-coverage-0-sample-symlink <<===>> nyc-coverage-0-sample
C:\>cd nyc-coverage-0-sample-symlink
C:\nyc-coverage-0-sample-symlink>nyc mocha


  HelloWorld
    √ should return hello world with no arguments
    √ should return passed argument


  2 passing (14ms)

---------------|---------|----------|---------|---------|-------------------
File           | % Stmts | % Branch | % Funcs | % Lines | Uncovered Line #s
---------------|---------|----------|---------|---------|-------------------
All files      |       0 |        0 |       0 |       0 |
 helloWorld.js |       0 |        0 |       0 |       0 | 1-9
---------------|---------|----------|---------|---------|-------------------

C:\nyc-coverage-0-sample-symlink>

This leads me to suspect that when symlinks are involved nyc may be watching the wrong paths

osher · 2021-02-22T10:02:37Z

@Darkripper214 - whats the procedure here, should I update the bug description above to make it easier for future readers that land on the issue from something they googled?
I mean, is that something you do here, or you prefer to preserve the narrative?

osher · 2021-02-22T12:47:24Z

ha. I've got it.

follow up here: istanbuljs/test-exclude#46

osher · 2021-02-22T14:19:52Z

actually, we may not need to wait for the PR on test-exclude if we pass it from nyc side a path already resolved through fs.realpath.
LMK what you think.

osher · 2021-03-16T12:45:22Z

@Darkripper214 - sup?

osher · 2021-03-30T07:25:44Z

Summary: I found the culprit, it's in test-exclude.
We can wait for them, or we can pass them an already resolved path.
@Darkripper214 - what do you think?|

osher · 2021-03-30T12:09:09Z

omg. sorry for the noise. I thought I was getting maintainers in the autocomplete when I type"@".

@coreyfarrell, you look a frequent committer on both projects - are you a maintainer of this project? Can we have your opinion?

osher · 2021-05-18T13:01:21Z

so. what's the move?

GerHobbelt · 2021-07-03T09:33:06Z

Same problem here. This time, SUBST-based. See istanbuljs/test-exclude#46 (comment)

updated build environment fixed some bother, filed mochajs/mocha#4675 noted istanbuljs/nyc#1381 but no dice

osher · 2021-09-19T08:05:25Z

any decision?

andyleejordan · 2021-10-06T20:39:15Z

I hope that nyc gets fixed for Windows and updated, I'd like to use it, but right now it's not usable on Windows at all.

This was referenced Feb 22, 2021

windows symlinks (aka junctions) mess up the is-outside-dir logic istanbuljs/test-exclude#46

Open

Fix Windows symlinks is-outside-dir bug istanbuljs/test-exclude#47

Open

GerHobbelt added a commit to GerHobbelt/markdown-it-footnote that referenced this issue Jul 3, 2021

updated npm packages

1efb472

updated build environment fixed some bother, filed mochajs/mocha#4675 noted istanbuljs/nyc#1381 but no dice

andyleejordan mentioned this issue Oct 6, 2021

WIP: Setup unit test code coverage using nyc PowerShell/vscode-powershell#3600

Closed

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

nyc on Windows shows 0 coverage #1381

nyc on Windows shows 0 coverage #1381

osher commented Jan 14, 2021 •

edited

osher commented Jan 17, 2021 •

edited

osher commented Jan 31, 2021

osher commented Feb 11, 2021

PhakornKiong commented Feb 12, 2021

osher commented Feb 18, 2021 •

edited

osher commented Feb 22, 2021 •

edited

osher commented Feb 22, 2021 •

edited

osher commented Feb 22, 2021

osher commented Feb 22, 2021 •

edited

osher commented Mar 16, 2021

osher commented Mar 30, 2021 •

edited

osher commented Mar 30, 2021 •

edited

osher commented May 18, 2021

GerHobbelt commented Jul 3, 2021

osher commented Sep 19, 2021

andyleejordan commented Oct 6, 2021

nyc on Windows shows 0 coverage #1381

nyc on Windows shows 0 coverage #1381

Comments

osher commented Jan 14, 2021 • edited

Link to bug demonstration repository

Expected Behavior

Observed Behavior

Troubleshooting steps

Environment Information

osher commented Jan 17, 2021 • edited

osher commented Jan 31, 2021

osher commented Feb 11, 2021

PhakornKiong commented Feb 12, 2021

osher commented Feb 18, 2021 • edited

osher commented Feb 22, 2021 • edited

First - disclaimer

reproduction scenario

osher commented Feb 22, 2021 • edited

osher commented Feb 22, 2021

osher commented Feb 22, 2021 • edited

osher commented Mar 16, 2021

osher commented Mar 30, 2021 • edited

osher commented Mar 30, 2021 • edited

osher commented May 18, 2021

GerHobbelt commented Jul 3, 2021

osher commented Sep 19, 2021

andyleejordan commented Oct 6, 2021

osher commented Jan 14, 2021 •

edited

osher commented Jan 17, 2021 •

edited

osher commented Feb 18, 2021 •

edited

osher commented Feb 22, 2021 •

edited

osher commented Feb 22, 2021 •

edited

osher commented Feb 22, 2021 •

edited

osher commented Mar 30, 2021 •

edited

osher commented Mar 30, 2021 •

edited