Adam Murray

@BioCarmen @ninasarabia do you have any links to runs that you could share where this is happening?

@jazanne @lmeynberg what is your use-case for this? Based on the code from #166, I believe it's working as expected - at the end of a run via `onTestsFinished` ([line](https://github.com/cypress-io/github-action/blob/7479fb6cd111c87e4eca28d235c5f05edacee7d3/index.js#L570)).

@jazanne that's considered a separate step so the output isn't going to be available there. Have you seen the dashboard link that comes with the Workflow summary (PR #566)?

@jazanne this may be a bug. We'll have to look into it a bit more.

@dzzk yes. Here are the instructions for specifying the version: https://github.com/cypress-io/github-action#explicit-version

@Pearce-Ropion have you tried [turning on logs](https://docs.cypress.io/guides/references/troubleshooting#Print-DEBUG-logs) to see where the test is hanging? Maybe there's a specific spot it hangs each time?

@karlhorky based on our [hardware recommendations](https://docs.cypress.io/guides/getting-started/installing-cypress#CPU) 4-cores should be fine.

@kpturner the action relies on the project it’s running against to determine the version of Cypress that's installed. The action itself has nothing to do with the version. You can...

@kpturner have you tried using custom cache keys as documented [here](https://github.com/cypress-io/github-action#custom-cache-key)? The action does try to use the cached dependency folder and the cached Cypress binary. Binary caching definitely proved...

@kpturner I get that it's really frustrating, and wish that I had more to offer. I'm not entirely sure that it's a GH action issue, but a larger caching issue...