-
-
Notifications
You must be signed in to change notification settings - Fork 731
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
Tests don't fail gracefully when encountering errors after test execution and stall the CI #4211
Comments
Interesting @sethvanwykJET , i'm not sure i have same issue, but have you this kind of error message in report allure or terminal ?
or like that
|
I've also been seeing those errors, but they're not necessarily the same as this. Those don't stall the pipeline / stop a test from retrying itself on my end. |
I have both in my case, the pipeline are stuck and i get this kind of error. I will check about throw exception That happens when i go to the 200th test all the begining works fine |
I believe my condition relates to a test failing in the After(async () => {
throw new error goes here
}); |
Ok i will check that, i have teardown on after with async request that can lead to throw error |
I've checked if the fail happens in the It's only when test execution fails in I tried to explain the test failing in |
Hey @sethvanwykJET have you some news on this issue have you try some fix on CodeceptJs ? |
I'm not really familiar with the codeceptJS repository to make changes to it :( Between work and my free time I've not had the chance to investigate this myself, which was why I opened the issue. Is there information missing in this thread for investigation? |
What are you trying to achieve?
Test pipelines should continue gracefully when encountering an error during "after" test execution
What do you get instead?
When the test fails, codeceptJS fails to properly scale down the test run and keeps the browser session open, essentially turning the test thread into a zombie codeceptJS process.
Tests running in pipelines will time out as the thread that's running these tests don't know the test has completed and that they should start the next test.
The terminal stalls here and leaves a broken browser session open that doesn't close anymore.
Details
The text was updated successfully, but these errors were encountered: