Error: ENOENT: no such file or directory jest.results.json

[scurrilus-funke]

Hello @mattallty, I tried to use the Jest github-action as it is in the instructions. However, I get the following error every time. Can you please tell me what's going wrong here?

Best Peter

Run mattallty/jest-github-action@v1.0.24s
}
Run mattallty/jest-github-action@v1.0.2
Jest execution failed. Tests have likely failed.
Error: ENOENT: no such file or directory, open '/home/runner/work/_actions/mattallty/jest-github-action/v1.0.2/dist/jest.results.json'
    at Object.openSync (fs.js:440:3)
##[error]ENOENT: no such file or directory, open '/home/runner/work/_actions/mattallty/jest-github-action/v1.0.2/dist/jest.results.json'
    at Object.readFileSync (fs.js:342:35)
    at parseResults (/home/runner/work/_actions/mattallty/jest-github-action/v1.0.2/dist/index.js:1:24547)
    at Object.<anonymous> (/home/runner/work/_actions/mattallty/jest-github-action/v1.0.2/dist/index.js:1:21809)
    at Generator.next (<anonymous>)
    at fulfilled (/home/runner/work/_actions/mattallty/jest-github-action/v1.0.2/dist/index.js:1:20705)
    at processTicksAndRejections (internal/process/task_queues.js:93:5) {
  errno: -2,
  syscall: 'open',
  code: 'ENOENT',
  path: '/home/runner/work/_actions/mattallty/jest-github-action/v1.0.2/dist/jest.results.json'
}

My Github action in general is configured like this:

name: Jest Annotations & Coverage (Tests)
on:
  push:
    branches:
      - master
  pull_request:
    branches:
      - master
jobs:
  jest-tests:
    runs-on: ubuntu-latest
    steps:
      - uses: actions/checkout@v2
      - uses: actions/setup-node@v1
        with:
          node-version: '14.x'
          
      - run: yarn install

      - uses: mattallty/jest-github-action@v1.0.2
        if: github.event_name == 'pull_request'
        env: 
          GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
        with: 
          test-command: 'yarn test'
          changes-only: true
       
      - uses: mattallty/jest-github-action@v1.0.2
        if: github.event_name == 'push'
        env: 
          GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
        with: 
          test-command: 'yarn test'

[fahadshehzada]

I was getting same issue after following this link

[rajington]

what fixed it for me was making sure all my jest deps were installed with a yarn install

[pagameba]

I am also having this issue, I tried yarn install but that didn't change anything. If I run npx jest --coverage it runs my tests fine but with this plugin I get the above error. Here is my action:

name: Test Coverage Before Merge

on:
  pull_request:
    branches:
      - develop

jobs:
  build:
    runs-on: ubuntu-latest
    steps:
      - uses: actions/checkout@v1
      - uses: actions/setup-node@v1
        with:
          node-version: 12
      - run: yarn install 
      - run: pwd    
      - run: npx jest --coverage
      - uses: mattallty/jest-github-action@v1
        env:
          GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
        with:
          test-command: "npx jest --coverage"

The pwd looks fine and the coverage is also fine. It feels like the plugin is executing in the context of the plugin instead of the project directory.

Is there a setting that's missing in the action?

Also, what is the required jest configuration because jest does not output jest.results.json as far as I can tell.

[doochik]

Same error for me

[wildone]

to fix this add --coverage --json --outputFile=jest.results.json to your unit test command, my usage

"test:unit":` "vue-cli-service test:unit --coverage --json --outputFile=jest.results.json",`

[wildone]

@mattallty this would be good in the instructions, together with a bit more info on "If you use Vue enable use_vue_cli: true" :D

[wildone]

@mattallty need to be able to bypass const cmd = getJestCommand(RESULTS_FILE) and just allow processing of the jest.result.json.

[doochik]

Still have the same error.
My Action

      - name: Run tests
        uses: mattallty/jest-github-action@v1
        env:
          GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
        with:
          test-command: "npx jest --ci --maxWorkers=3 --coverage --json --outputFile=jest.results.json"

[davidcalhoun]

I have tried using test-command as well as working_directory and I still get this error - this is a blocker for me unfortunately.

##[warning]Unexpected input(s) 'working_directory', valid inputs are ['test-command', 'coverage-comment', 'changes-only']
Run mattallty/jest-github-action@v1
Jest command executed
Error: ENOENT: no such file or directory, open '/home/runner/work/_actions/mattallty/jest-github-action/v1/dist/jest.results.json'
    at Object.openSync (fs.js:440:3)
    at Object.readFileSync (fs.js:342:35)
    at parseResults (/home/runner/work/_actions/mattallty/jest-github-action/v1/dist/index.js:1:24547)
    at Object.<anonymous> (/home/runner/work/_actions/mattallty/jest-github-action/v1/dist/index.js:1:21809)
    at Generator.next (<anonymous>)
    at fulfilled (/home/runner/work/_actions/mattallty/jest-github-action/v1/dist/index.js:1:20705)
    at processTicksAndRejections (internal/process/task_queues.js:93:5) {
  errno: -2,
  syscall: 'open',
  code: 'ENOENT',
  path: '/home/runner/work/_actions/mattallty/jest-github-action/v1/dist/jest.results.json'
}
##[error]ENOENT: no such file or directory, open '/home/runner/work/_actions/mattallty/jest-github-action/v1/dist/jest.results.json'

Happens with this step (in a monorepo):

            - name: Coverage reporter with code annotations (for Github UI).
              uses: mattallty/jest-github-action@v1
              env:
                  GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
              with:
                  working_directory: 'packages/app'

And also this step (tweaked slightly - this is running in a Lerna monorepo):

            - name: Coverage reporter with code annotations (for Github UI).
              uses: mattallty/jest-github-action@v1
              env:
                  GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
              with:
                  test-command: 'jest src --coverage --json --testLocationInResults --outputFile=jest.results.json'

[MarcBT]

what fixed it for me was making sure all my jest deps were installed with a yarn install

I confirm that this solved the Error: ENOENT: no such file or directory jest.results.json issue on my side as well.

      - run: yarn install
      - name: Jest Annotations & Coverage
        uses: mattallty/jest-github-action@v1.0.3
        env:
          GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}

[leeuwd]

Same for us. Forcing a yarn install beforehand (i.e. skip module cache from Github Actions) doesn't work either.

~/D/frontend [feature/google-actions-firebase]× » yarn list --depth=0 --pattern=jest                                                                                        09:33:26
yarn list v1.22.10
warning ../../package.json: No license field
├─ @angular-builders/jest@8.3.2
├─ @jest/console@26.5.2
├─ @jest/core@26.5.3
├─ @jest/environment@26.5.2
├─ @jest/fake-timers@26.5.2
├─ @jest/globals@26.5.3
├─ @jest/reporters@26.5.3
├─ @jest/source-map@24.9.0
├─ @jest/test-result@26.5.2
├─ @jest/test-sequencer@26.5.3
├─ @jest/transform@26.5.2
├─ @jest/types@26.5.2
├─ @types/jest@26.0.14
├─ babel-jest@26.5.2
├─ babel-plugin-jest-hoist@26.5.0
├─ babel-preset-jest@26.5.0
├─ jest-changed-files@26.5.2
├─ jest-cli@26.5.3
├─ jest-config@26.5.3
├─ jest-diff@26.5.2
├─ jest-docblock@26.0.0
├─ jest-each@26.5.2
├─ jest-environment-jsdom-fifteen@1.0.2
├─ jest-environment-jsdom-thirteen@1.0.1
├─ jest-environment-jsdom@26.5.2
├─ jest-environment-node@26.5.2
├─ jest-get-type@26.3.0
├─ jest-haste-map@26.5.2
├─ jest-jasmine2@26.5.3
├─ jest-leak-detector@26.5.2
├─ jest-matcher-utils@26.5.2
├─ jest-message-util@26.5.2
├─ jest-mock@26.5.2
├─ jest-pnp-resolver@1.2.2
├─ jest-preset-angular@8.0.0
├─ jest-regex-util@26.0.0
├─ jest-resolve-dependencies@26.5.3
├─ jest-resolve@26.5.2
├─ jest-runner@26.5.3
├─ jest-runtime@26.5.3
├─ jest-serializer@26.5.0
├─ jest-snapshot@26.5.3
├─ jest-util@26.5.2
├─ jest-validate@26.5.3
├─ jest-watcher@26.5.2
├─ jest-worker@26.5.0
├─ jest@26.5.3
└─ ts-jest@24.1.0

[hollandjake]

Same for me, however this seems to fix it:

jobs:
  build:
    runs-on: ubuntu-latest
    steps:
      - uses: actions/checkout@v2
      - name: Install modules
        run: yarn
      - name: Run tests
        run: yarn jest --json --outputFile="jest.results.json"
      - name: Add Coverage Comment
        uses: mattallty/jest-github-action@v1.0.3
        env:
          GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
        with:
          changes-only: true
          test-command: "yarn jest"

[jcandrade]

Same here. I was able to workaround by running the tests before this action, like hollandjake did. However, I updated the test command to be only a test-command: ls and here's what I got:

Jest execution failed. Tests have likely failed. Error: The process '/bin/ls' failed with exit code 2
    at ExecState._setResult (/home/runner/work/_actions/mattallty/jest-github-action/v1.0.3/dist/index.js:1:15037)
    at ExecState.CheckComplete (/home/runner/work/_actions/mattallty/jest-github-action/v1.0.3/dist/index.js:1:14599)
    at ChildProcess.<anonymous> (/home/runner/work/_actions/mattallty/jest-github-action/v1.0.3/dist/index.js:1:13563)
    at ChildProcess.emit (events.js:210:5)
    at maybeClose (internal/child_process.js:1021:16)
    at Socket.<anonymous> (internal/child_process.js:430:11)
    at Socket.emit (events.js:210:5)
    at Pipe.<anonymous> (net.js:659:12)
    ```