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
[🐛 Bug]: RangeError: Maximum call stack size exceeded
error with async jasmine tests
#8126
Comments
@BenoitZugmeyer Could we close this issue ? if the fix is merged |
I'm not aware of a fix. But sure, close the issue when it's fixed. |
Sorry ignore the comments , I just saw the merge thought it was in wdio repo . |
@BenoitZugmeyer any chance you can provide a minimal reproducible example? |
I have, see "How to reproduce the bug" |
Ah, cheers! I must have missed that. Any contributions that resolves the bug are highly appreciated. Please take a look into our contribution guidelines and let us know if you have any questions. Cheers! |
fixed in #8175 |
Nice going Christian and thanks for reporting @BenoitZugmeyer 👍 |
Thank you very much @christian-bromann ! |
Have you read the Contributing Guidelines on issues?
WebdriverIO Version
7.18.0
Node.js Version
17.6.0
Mode
WDIO Testrunner
Which capabilities are you using?
No response
What happened?
When running asynchronous jasmine tests, if a test timeout, all remaining tests are failing with
RangeError: Maximum call stack size exceeded
with no call stack.After investigation, the culprit seems to be the
expectAsyncShim
function calling itself indefinitely.What is your expected behavior?
Remaining tests are correctly run.
How to reproduce the bug.
Relevant log output
Code of Conduct
Is there an existing issue for this?
The text was updated successfully, but these errors were encountered: