Action failing after upgrading from Jest 26 to 27
See original GitHub issueDescribe a bug
This is for v2.0-rc.6
, but I’m not able to add labels to the issue.
After upgrading my project to use Jest 27 (from 26), jest-coverage-report-action
is running all the tests successfully but failing to mark the step as successful. The step seems to time out after close to 30 minutes (while a successful run takes about 6 minutes), and this error is included in the output: Error: The process '/opt/hostedtoolcache/node/14.18.2/x64/bin/npx' failed with exit code null
.
Expected behavior
Details
-
Action version:
v2.0-rc.6
-
OS, where your action is running (windows, linux):
linux
-
action.yml file
```ymlname: 'Test Coverage' on: pull_request: pull_request_target: jobs: code-coverage: runs-on: ubuntu-latest # If the PR is coming from a fork (pull_request_target), ensure it's opened by "dependabot[bot]". # Otherwise, clone it normally. if: | (github.event_name == 'pull_request_target' && github.actor == 'dependabot[bot]') || (github.event_name != 'pull_request_target' && github.actor != 'dependabot[bot]') steps: - uses: actions/checkout@v2 - uses: actions/setup-node@v2 with: node-version: '14' - name: Get yarn cache directory path id: yarn-cache-dir-path run: echo "::set-output name=dir::$(yarn cache dir)" - uses: actions/cache@v2 id: yarn-cache with: path: ${{ steps.yarn-cache-dir-path.outputs.dir }} key: ${{ runner.os }}-yarn-${{ hashFiles('**/yarn.lock') }} restore-keys: | ${{ runner.os }}-yarn- - uses: artiomtr/jest-coverage-report-action@v2.0-rc.6 with: github-token: ${{ secrets.GITHUB_TOKEN }} threshold: 50 package-manager: yarn annotations: failed-tests ```
-
Screenshots
Additional context
Final output from the failing step:
Test Suites: 266 passed, 266 total
Tests: 804 passed, 804 total
Snapshots: 0 total
Time: 147.017 s
Ran all test suites.
Test results written to: report.json
Running tests ended
Begin collecting coverage...
Collecting coverage ended
Begin parsing coverage...
Parsing coverage ended
Base coverage collection ended
Begin generating report...
Generating report ended
Begin report publish...
Report publish ended
Begin failed tests' annotations publication...
Failed tests' annotations publication skipped
Failed tests' annotations publication ended
Begin coverage annotations publication...
Coverage annotations publication skipped
Coverage annotations publication ended
Error: Jest coverage report action failed
Error: Process completed with exit code 1.
Issue Analytics
- State:
- Created 2 years ago
- Comments:7 (2 by maintainers)
Top Results From Across the Web
Upgrading from 26 to 27 breaks __mocks__ ... - GitHub
We had to hold off on upgrading to Jest 27 due to this. If we have time we might try again since it...
Read more >Jest 27: New Defaults for Jest, 2021 edition
We will explain those changes of defaults and other notable breaking changes in this post, but first, let's get into some exciting new...
Read more >Migration Guide | Detox
You have to upgrade your Jest version to at least 27.2.5 or higher. The recommended choice is 28.x or 29.x. All-in-one configs. If...
Read more >ts-jest - npm
There are 2819 other projects in the npm registry using ts-jest. ... Known vulnerabilities Coverage status GitHub actions GitHub license.
Read more >Jest 27 changes the default test environment - Release Radar
Developer Ready: A comprehensive JavaScript testing solution. Works out of the box for most JavaScript projects. Instant Feedback: Fast ......
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Hi @davecowart !
I’m going through the same problem. Did you find the cause of the problem?
Regards,
Hello @ArtiomTr !
Thanks for having answering me, in my case, I cloned again the project and my problem was solutioned.