Open tnelms1 opened 1 year ago
Hi @tnelms1 , are you seeing this problem with Cypress even when running outside of the Github Action? If it's only occurring within the action then it may be an issue with that package, in which case I would recommend reporting this issue there
Hi @mike-plummer & @lmiller1990 , sorry for the delay was on holiday. When not run on the GitHub Action after the tests finish an odd pop-up occurs where it asks to add project (it is pictured above at the very bottom of my ticket request)
Also, this issue has not been resolved since 12.17.1, I tested today
I reproduced, nothing to do with GHA... general bug. We have seen this before, though, let me dig up a commit that was supposedly meant to fix it. The hanging is Cypress opening. It was introduced somewhere in PW 1.34 and 1.35.
https://github.com/cypress-io/cypress/assets/19196536/99f1e83c-8b8a-446e-8ca4-7a5753b6364b
X 1.35.0-alpha-jun-3-2023
X 1.35.0-alpha-jun-2-2023
X 1.35.0-alpha-jun-1-2023
X 1.35.0-alpha-1685749070000
O 1.35.0-alpha-1685109821000
O 1.35.0-alpha-1685046878000
O 1.34.3
Looks like we broke between 1.35.0-alpha-1685109821000 -> 1.35.0-alpha-1685749070000.
I do not see a release with that tag, though. Best bet might be find out the exact publication date of both via npm, and see what commits happened around that time.
Similar bug: https://github.com/cypress-io/cypress/pull/15533#issuecomment-1211506734
I found it the fix for that original bug. We hit this same issue during initial webkit development, here's the line that fixed it then: https://github.com/cypress-io/cypress/pull/23662/files#r963165698
This should help when someone takes a look at this. Would you be interested in taking a look @tnelms1?
Glad the issue was identified. @lmiller1990 I don't believe I have proper time, with day-job + life
I had a look at adding webkit
to the set of browser examples on cypress-io/github-action to establish a baseline, however the webkit
implementation seems to be more on the experimental end of the scale at the moment and not mature enough to set up a solid example.
npx cypress run
has finished is quite confusing. I think this needs to be resolved first.npx cypress open
and not getting a list of test specs is something which needs to be sorted out (https://github.com/cypress-io/cypress/issues/24767). That should work out-of-the-box.We are looking at getting this fixed internally. Please wait a bit while we prioritize the issue.
For now I'm going to recommend using the playwright-webkit verison that is known to work, 1.34. cypress-io/cypress-documentation#5375
I believe I am also running into this issue on CircleCI so wanted to add my debugging info in case it is useful or if the solution in the works is targeting GHA only. My Chrome tests exit after success or fail as expected but the exit code doesn't seem to be communicated back to Circle. Debug info after the job failure:
cypress:server:cypress about to exit with code 2 +2m
cypress:server:browsers browsers.kill called with no active instance +2m
cypress:proxy:http:util:prerequests metrics: { browserPreRequestsReceived: 418, proxyRequestsReceived: 388, immediatelyMatchedRequests: 322, unmatchedRequests: 66, unmatchedPreRequests: 96 } +0ms
Build was canceled
The build-cancelation happens as a result of CI timeout or manual cancel.
@mkascel
... or if the solution in the works is targeting GHA only.
I haven't seen anything so far to indicate that a solution would only work on GitHub Actions. In fact in https://github.com/cypress-io/cypress/issues/27141#issuecomment-1630179586 it says:
I reproduced, nothing to do with GHA... general bug.
This issue has not had any activity in 180 days. Cypress evolves quickly and the reported behavior should be tested on the latest version of Cypress to verify the behavior is still occurring. It will be closed in 14 days if no updates are provided.
Testing on
22.04.4
LTSv20.11.1
LTS13.6.6
npx cypress run --e2e --browser webkit
After executing the above command, Cypress incorrectly launches in interactive (open) project mode:
16.4
)16.4
)latest
) with WebKit v17 (17.4
)So, possibly this issue should be closed?
Guides > Launching Browsers > WebKit (Experimental) says:
- Install the
playwright-webkit
NPM package in your repo to acquire WebKit itself:npm install --save-dev playwright-webkit@1.34
.
@tnelms1
Is this issue still reproducible for you if you use latest versions?
cypress@13.13.1
playwright-webkit@1.45.3
Current behavior
When testing with playwright-webkit@1.35.0 after the Cypress test completes the instance just pauses until Github times it out
Desired behavior
In previous versions (1.34.0) the test completes as it does for all my other GitHub Action Cypress test (non-safari)
(non-sa
Test code to reproduce
https://github.com/SmartBear/visualtest-cypress visualtest-cypress/test/webkit-test the test in that e2e is the one that fails
it is ran from a YAML file: https://github.com/SmartBear/visualtest-cypress/blob/main/.github/workflows/webkit-browser_test.yml I have changed the yaml file: https://github.com/SmartBear/visualtest-cypress/blob/dce910895b546dd7d6e90735733a5c33a800cbb2/.github/workflows/webkit-browser_test.yml#L25C14-L25C50 from run: npm install playwright-webkit@latest to run: npm install playwright-webkit@1.34.0
Cypress Version
12.16.0
Node version
v16.18.0
Operating System
macOS 13.4 && GitHub Ubuntu-latest
Debug Logs
Other
It pulls up this at the end of a npx cypress run -b webkit test