-
Notifications
You must be signed in to change notification settings - Fork 4.3k
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
Fix flaky test by finalising request resolution in Nav block e2e test #39633
Conversation
Size Change: 0 B Total Size: 1.21 MB ℹ️ View Unchanged
|
@talldan I wonder if your expert knowledge of e2e tests can shed any light on this. It passes locally but is flaky on CI. When the block is added with the The question is why does the request sometimes not match? |
cd58c9d
to
8f3de45
Compare
@getdave I don't know for sure. I'd recommend having a look through the docs for request interception and then taking a look at how I wonder if there's an issue in that this code never calls Having said that, I don't know that the request technically needs to resolve. The promise code might not be necessary at all. The tests don't do anything after the promise resolves, so maybe the easiest option is to not resolve. |
I guess I didn't want to risk having a unfulfilled |
@talldan I took a more careful look at |
Github Actions are down now so I'll have to wait until tomorrow to see if this works on CI. Oh the suspense! |
0d97f3b
to
a624392
Compare
Ok this passed 5 times without issue. Going to merge and 🙏 that fixes it. |
What?
Fixes to the e2e tests to resolve #39231.
Closes #39231.
Why?
This e2e test keeps failing #39231 because the resolution function maybe be null and not callable.
How?
Conditionalises the calling of the resolution function to check whether it is a function.
Testing Instructions
Screenshots or screencast