Jest 26.2.1 regression: “No tests found” on Windows #10339

ai · 2020-07-30T19:12:33Z

🐛 Bug Report

In PostCSS we found a problem with the new Jest release. After updating Jest to 26.2.1, Jest stopped to see tests on Windows in our Travis CI.

$ npx jest

No tests found, exiting with code 1
Run with `--passWithNoTests` to exit with code 0
No files found in C:\Users\travis\build\postcss\postcss.
Make sure Jest's configuration does not exclude this directory.
To set up Jest, make sure a package.json file exists.
Jest Documentation: facebook.github.io/jest/docs/configuration.html
Pattern:  - 0 matches
The command "npx jest" exited with 1.

Update commit: postcss/postcss@8722140
Before: https://travis-ci.org/github/postcss/postcss/jobs/713424784
After: https://travis-ci.org/github/postcss/postcss/jobs/713426131

To Reproduce

Seems like just call npx jest on Windows. Here is a config to call it on Travis CI

matrix:
  include:
    os: windows
    cache: false
    node_js: node
    script: npx jest
    env:
      - YARN_GPG=no

Expected behavior

https://travis-ci.org/github/postcss/postcss/jobs/713424784

Link to repl or repo (highly encouraged)

https://github.com/postcss/postcss/archive/8722140c5c55530b0c4091190f1557b42fd18c87.zip

envinfo

  System:
    OS: Windows 10 10.0.17763
    CPU: (2) x64 Intel(R) Xeon(R) CPU
  Binaries:
    Node: 14.7.0 - C:\ProgramData\nvs\node\14.7.0\x64\node.EXE
    Yarn: 1.22.4 - ~\.yarn\bin\yarn.CMD
    npm: 6.14.7 - C:\ProgramData\nvs\node\14.7.0\x64\npm.CMD
  npmPackages:
    jest: ^26.2.1 => 26.2.1

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

ahnpnl · 2020-07-30T19:57:45Z

Strange thing that even ts-jest hasn’t updated to jest 26.2.x but also saw the same issue https://travis-ci.com/github/kulshekhar/ts-jest/jobs/366826311

The issue occured right after 26.2 was released and CI still uses 26.1, and of course all PRs by dependabot to upgrade to jest 26.2 failed with the same reason.

The issue however only happens to ts-jest node 14 tests on external projects, unit tests on node 10 Windows work fine https://travis-ci.com/github/kulshekhar/ts-jest/jobs/366826310

ahnpnl · 2020-07-30T20:06:59Z

Seem like PostCSS and ts-jest CIs both failed with Node 14 Windows

sr258 · 2020-07-31T07:10:21Z

This affects me as well. I use Windows with Node v12.18.3 and Jest v26.2.1. Ts-Jest is at 26.1.4.

SimenB · 2020-07-31T07:22:18Z

I don't have access to a windows machine, unfortunately, so hard for me to debug this... Our own Windows CI passes on both GH Actions and Azure Pipelines, so I wonder if this is some weird config thing?

Does it just happen with ts-jest?

ai · 2020-07-31T07:23:23Z

@SimenB yeap, we have TypeScript tests too

ahnpnl · 2020-07-31T07:40:54Z

I tried to run ts-jest CI on tag 26.1.4 (which is the latest release) also failed with Windows Node 14. Tag 26.1.4 doesn't use jest 26.2 for e2e tests https://github.com/kulshekhar/ts-jest/blob/220f4fbfd2544ad23af494c2d5acd53d28fdac74/e2e/__external-repos__/custom-typings/yarn.lock#L296

The only clue I have is CI didn't fail with 26.1 until 26.2 released

SimenB · 2020-07-31T07:42:50Z

I'm guessing this is somehow related to #10308 - only windows change I can think of (although it's weird that our own tests pass...).

Does anyone here use Windows on their own machine, or have the possibility to test? If so, try reverting this change

in node_modules/jest-haste-map/build/crawlers/node.js. That should force an fs crawl using Node's APIs rather than using find on windows

ahnpnl · 2020-07-31T07:44:55Z

I think maybe an alpha version so we can point CI to it ?

SimenB · 2020-07-31T07:57:32Z

I'd rather avoid it if possible, but not a huge issue if no one here has a Windows machine

raviteja64 · 2020-07-31T08:05:37Z

Tests not being detected on WIndows. I use yarn, ts-jest for typescript.

Do we have an interim solution for windows?
Version is automatically being pointed to 26.2.1 even thought i explicitly mention ~26.1.0

SimenB · 2020-07-31T08:22:07Z

Interim solution is to revert the upgrade commit if you have a lockfile. For fresh installs you could try to use resolutions

ritterzk · 2020-07-31T08:46:30Z

I'm guessing this is somehow related to #10308 - only windows change I can think of (although it's weird that our own tests pass...).

Does anyone here use Windows on their own machine, or have the possibility to test? If so, try reverting this change

in node_modules/jest-haste-map/build/crawlers/node.js. That should force an fs crawl using Node's APIs rather than using find on windows

yes, as soon as you undo the change, it will run on Windows systems again.

SimenB · 2020-07-31T08:58:17Z

I was able to find the old windows images from modern.ie, and was able to confirm it. I'll try a couple of minutes to fix detection properly, if not I'll re-add the condition 👍 I'm very confused by why our CI passes with the changes...

SimenB · 2020-07-31T10:55:35Z

https://github.com/facebook/jest/releases/tag/v26.2.2

ahnpnl · 2020-07-31T11:35:40Z

Thanks a lot Simen !!, I see our CI is green again

pglejzer · 2020-07-31T11:41:46Z

Thanks, I also had problems with my tests after upgrade to version 26.2.1 but with 26.2.2 everything is working again. Thanks again.

G-Rath · 2020-09-09T05:19:47Z

@SimenB stumbled on this while lazily scrolling through the issues - I dev on Windows (w/ WSL for CLI) so feel free to ping me on future Windows issues if you'd like :)

SimenB · 2020-09-09T11:37:37Z

Thanks @G-Rath! Will do 🙂

arose · 2020-11-26T02:12:05Z

Hi, I still have this issue with 26.2.2 or later on one of my windows machines (on others it does work). On the machine where it does not work, I can make it work by manually changing forceNodeFilesystemAPI in jest-haste-map (packages/jest-haste-map/src/crawlers/node.ts) to true.

exaucae · 2021-01-22T12:56:24Z

Hi there,

I'm facing the exact same error aforementioned. on my local machine.

I'm using CRA and the following packages:
jest:: 26.6.3
jest-transform-stub: 2.0.0,
@testing-library/jest-dom: 5.11.4
@testing-library/react: 11.1.0
@testing-library/user-event: 12.1.10
@types/jest: 26.0.15
ts-jest: 26.4.4

System:
OS: Microsoft Windows [Version 10.0.18363 N/A Build 18363]
CPU: (2) x64 IIntel64 Family 6 Model 142 Stepping 10 GenuineIntel ~1910 Mhz
Binaries:
typescript: 4.1.3
npx: 6.14.11
Node: 14.7.0
Yarn: 1.22.10
npm: 6.14.11

All tests are ran Mac os, docker container and CI ( with ubuntu image).
Sounds like the issue is from the Windows OS compatibility. Looking for any clue.

Martibis · 2021-02-01T16:38:21Z

Same issue here

exaucae · 2021-04-04T13:34:29Z

It's odd that no one pays attention our demand. It's been 3 months since my post.

github-actions · 2021-05-10T21:05:49Z

This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.
Please note this issue tracker is not a help forum. We recommend using StackOverflow or our discord channel for questions.

ai added Bug Report Needs Repro Needs Triage labels Jul 30, 2020

ahnpnl mentioned this issue Jul 30, 2020

build(deps-dev): bump @jest/types from 26.1.0 to 26.2.0 kulshekhar/ts-jest#1839

Merged

AviVahl mentioned this issue Jul 31, 2020

breaking: fix audit failures; node 10+ lerna/lerna#2680

Closed

9 tasks

SimenB added 💥 Regression Help Wanted Windows and removed Bug Report Needs Repro Needs Triage labels Jul 31, 2020

SimenB mentioned this issue Jul 31, 2020

chore: add ts-jest example #10343

Closed

SimenB mentioned this issue Jul 31, 2020

fix: correct check for compatible find binary #10346

Merged

SimenB closed this as completed in #10346 Jul 31, 2020

jmtelljohann mentioned this issue Jul 31, 2020

Getting Started tutorial fails to find test #10338

Closed

github-actions bot locked as resolved and limited conversation to collaborators May 10, 2021

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Jest 26.2.1 regression: “No tests found” on Windows #10339

Jest 26.2.1 regression: “No tests found” on Windows #10339

ai commented Jul 30, 2020

ahnpnl commented Jul 30, 2020 •

edited

ahnpnl commented Jul 30, 2020 •

edited

sr258 commented Jul 31, 2020

SimenB commented Jul 31, 2020

ai commented Jul 31, 2020

ahnpnl commented Jul 31, 2020

SimenB commented Jul 31, 2020 •

edited

ahnpnl commented Jul 31, 2020

SimenB commented Jul 31, 2020

raviteja64 commented Jul 31, 2020 •

edited

SimenB commented Jul 31, 2020

ritterzk commented Jul 31, 2020

SimenB commented Jul 31, 2020

SimenB commented Jul 31, 2020

ahnpnl commented Jul 31, 2020 •

edited

pglejzer commented Jul 31, 2020

G-Rath commented Sep 9, 2020

SimenB commented Sep 9, 2020

arose commented Nov 26, 2020

exaucae commented Jan 22, 2021

Martibis commented Feb 1, 2021

exaucae commented Apr 4, 2021

github-actions bot commented May 10, 2021

Jest 26.2.1 regression: “No tests found” on Windows #10339

Jest 26.2.1 regression: “No tests found” on Windows #10339

Comments

ai commented Jul 30, 2020

🐛 Bug Report

To Reproduce

Expected behavior

Link to repl or repo (highly encouraged)

envinfo

ahnpnl commented Jul 30, 2020 • edited

ahnpnl commented Jul 30, 2020 • edited

sr258 commented Jul 31, 2020

SimenB commented Jul 31, 2020

ai commented Jul 31, 2020

ahnpnl commented Jul 31, 2020

SimenB commented Jul 31, 2020 • edited

ahnpnl commented Jul 31, 2020

SimenB commented Jul 31, 2020

raviteja64 commented Jul 31, 2020 • edited

SimenB commented Jul 31, 2020

ritterzk commented Jul 31, 2020

SimenB commented Jul 31, 2020

SimenB commented Jul 31, 2020

ahnpnl commented Jul 31, 2020 • edited

pglejzer commented Jul 31, 2020

G-Rath commented Sep 9, 2020

SimenB commented Sep 9, 2020

arose commented Nov 26, 2020

exaucae commented Jan 22, 2021

Martibis commented Feb 1, 2021

exaucae commented Apr 4, 2021

github-actions bot commented May 10, 2021

ahnpnl commented Jul 30, 2020 •

edited

ahnpnl commented Jul 30, 2020 •

edited

SimenB commented Jul 31, 2020 •

edited

raviteja64 commented Jul 31, 2020 •

edited

ahnpnl commented Jul 31, 2020 •

edited