-
-
Notifications
You must be signed in to change notification settings - Fork 147
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Unexpected state in afterSpecHandler when executing over Github actions #1217
Comments
This is related to #1217 [1]. [1] badeball/cypress-cucumber-preprocessor#1217
Hi @ccastanoAizon, thanks for reporting this. There's not really much to go on here, so I have a couple of questions for you.
Can you share your whole CI configuration / everything that pertains to the environment?
Do you mean that this happens every time?
Are you using pretty output?
Let's call the local variant for "appropriate failure" and behavior seen in CI for "inappropriate failure". During a failed step, I expect to see "✖ failed" in the pretty out, as seen below.
Do you not see this during the inappropriate failures in CI? Or in other words - does the step appear to succeed, while the test appears to mistakenly fail in a non-existing afterEach hook? Lastly, can you take this example-test and incorporate it into your CI system to see if it also fails? It's essentially a watered down example based on your information. Try to keep as much as your original configuration and setup, IE. only copy the index-file, the feature-file and the associated steps. |
package.json dependencies and other relevant content
cypress.config.ts e2e configuration and relevant data
Yes, it happens every time in the same scenario (the one referenced above)
Yes.
I don't see it. It does appear to succeed while te test appears to mistakenly fail in an non-existing afterEach hook, yes.
We have not been able to reproduce the issue (requested scenarios was executed immediately before the failing one in the flow). Result is
|
Therein may lie your issue. You're combining two workarounds. Either you invoke |
Seems like removing the afterRunHandler wait fixed the issue. Thanks. |
Current behavior
When executing a large test suite over Github actions using a Ubuntu Github hosted runner we are consistently reproducing an issue related with the rising of assertion errors after finishing the test execution. We have not been able to reproduce the issue when executing locally.
Step 8 (the one rising the assertion error) consist in a cy.wait of a cy.request defined in setp 6
Step 6 function:
Step 8 function:
The error described causes an uncontrolled exception that terminates cypress run execution.
Desired behavior
When executing locally the scenario fails in a controlled way.
Test code to reproduce
Unable to reproduce locally.
Versions
Checklist
[email protected]
(package name has changed and it is no longer the most recent version, see #689).The text was updated successfully, but these errors were encountered: