[🐛 Bug]: RangeError: Maximum call stack size exceeded error with async jasmine tests

[BenoitZugmeyer]

Have you read the Contributing Guidelines on issues?

• I have 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.

git clone https://gist.github.com/5d2ce35e3291993d7dbaf31961c15069 test-wdio
cd test-wdio
npm i
npm run wdio

Relevant log output

[0-0] RUNNING in chrome - /test.js
...
[0-0] Error in "test timeout"
Error: Timeout - Async function did not complete within 5000ms (set by jasmine.DEFAULT_TIMEOUT_INTERVAL)
    at <Jasmine>
    at listOnTimeout (node:internal/timers:559:17)
    at processTimers (node:internal/timers:502:7)
[0-0] Error in "test foo"
RangeError: Maximum call stack size exceeded
[0-0] Error in "test bar"
RangeError: Maximum call stack size exceeded

Code of Conduct

• I agree to follow this project's Code of Conduct

Is there an existing issue for this?

• I have searched the existing issues

[praveendvd]

@BenoitZugmeyer Could we close this issue ? if the fix is merged

[BenoitZugmeyer]

I'm not aware of a fix. But sure, close the issue when it's fixed.

[praveendvd]

Sorry ignore the comments , I just saw the merge thought it was in wdio repo .

[christian-bromann]

@BenoitZugmeyer any chance you can provide a minimal reproducible example?

[BenoitZugmeyer]

I have, see "How to reproduce the bug"

[christian-bromann]

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!

[christian-bromann]

fixed in #8175

[erwinheitzman]

Nice going Christian and thanks for reporting @BenoitZugmeyer 👍

[BenoitZugmeyer]

Thank you very much @christian-bromann !