Cypress Dashboard - Tests run completed in GitHub action but show continuously running in dashboard and not stop until I cancel it manually.

[KrupalVaghasiya]

Current behavior

I am running my cypress test with GitHub action. The GitHub action test takes a maximum of 6 minutes to complete the run. After the test is completed run in the GitHub action. when I go to my cypress dashboard, it will show a test running. and not stop until I cancel it manually.

Desired behavior

It should show test run completed if in the GitHub action completed test execution.

Test code to reproduce

This is my cypress.yml file.

name: Legrande GitHub Actions
on:
  schedule:
  - cron: "0 0 * * *"

  push:
    branches:
      - 'master'
      
env: 
  CYPRESS_CACHE_FOLDER: cypress/cache
  
jobs:
 cypress-test:
  name: Run on windows
  runs-on: windows-latest
  steps: 
    - uses: actions/checkout@v2

    - name: Cache Node Modules
      id: cache-node-modules
      uses: actions/cache@v2
      with:
        path: node_modules
        key: node-modules-${{ hashFiles('package-lock.json') }}

    - name: Cache Cypress Binary
      id: cache-cypress-binary
      uses: actions/cache@v2
      with:
        path: cypress/cache
        key: cypress-binary-${{ hashFiles('package-lock.json') }}

    - name: Install Dependencies
      if: steps.cache-node-modules.outputs.cache-hit != 'true'
      run: |
        npm install
        npm install --dev

    - uses: cypress-io/github-action@v2
      continue-on-error: true
      with:
        record: true
      env:
        CYPRESS_RECORD_KEY: ${{ secrets.CYPRESS_RECORD_KEY }}

Cypress Version

9.5.4

Other

Here is my Github action page for reference. https://github.com/KrupalVaghasiya/cypressBug/actions

Check this video for current behavior.
https://www.loom.com/share/19b84181594e421a8b687c1362db12ef

[tanimaroy2012]

im facing the same issue, i dont have a cron job, but when a test fails, github actions updates the failure but cypress dashboard continues to run till 90 mins

[adilsonfuta]

https://www.freeformatter.com/cron-expression-generator-quartz.html

look if your cron is correct config ...

[KrupalVaghasiya]

@adilsonfuta cron is correctly configured.

[patrick-silvera-pp]

We have a similar issue on Github Actions. We configured timeout-minutes: 15, when this timeout is reached then the job correctly fails on github side but keeps running on Cypress Dashboard for 90 minutes.

We're running 10 parallel jobs so when a job fails it cancels the other jobs. The automatic cancel on github side may not be handled correctly.

[dlively1]

I am running into a similar situation from a different context.

On my workflow that runs against PRs I have a concurrency option set to cancel the in-progress run to avoid wasting CI cycles testing old commits.

concurrency:
    group: ${{ github.workflow }}-${{ github.ref }}
    cancel-in-progress: true

This successfully stops things in Github actions but my recording continues in Cypress Cloud.

[Lexe003]

Same issue here!

[yusriyunus]

any update on this issue? @nagash77

[nabsta-eth]

We are also getting this issue and it is blowing up our GH CI credits!
We actually have tests that despite a 3min timeout default, 57% of the time continue running beyond that and even if then cancelled!
This only happens for CI run tests. None of the tests stall/fail running tests locally.
I've just upgraded to v13.16.2 without any change.
Any update?

[adiharush]

We're encountering a similar issue.
Our GitHub actions complete successfully within approximately 3 minutes. However, unless we manually cancel the run on Cypress, it continues to see the underlying specs as running and the run lasts for approximately 100 minutes :/

[ifoca]

Similar issue as described here, when the concurrency job cancels another in progress workflow, this run is still ongoing in cypress cloud.

[hatemeby]

Same issue here!
Is there any solution/fix???

[zhangxy95]

same here!!
someone help to take a look??

[jbeef710]

@jennifer-shehane any chance this is on the radar to be worked on? We would love to be able to kill the cypress cloud run when we cancel in GHA.

[aravindreddyk10]

same here!!
someone help to take a look??

[pat-convex]

This is still an issue and Cypress is ignoring it.

[jennifer-shehane]

The run timeout is now configurable via the Cloud when recording. The default is 90 minutes. You can find instructions to update this to a smaller timeout, if you know your run should never be this long, here: https://docs.cypress.io/guides/cloud/account-management/projects#Run-Timeout