-
Notifications
You must be signed in to change notification settings - Fork 4.2k
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
Performance Tests: Support the Site Editor's legacy spinner #54784
Conversation
Without this selector, this locator resolves immediately because it doesn't find a spinner element.
ℹ️ Running Base branch validation in https://github.com/WordPress/gutenberg/actions/runs/6299641228 |
Size Change: -3 B (0%) Total Size: 1.62 MB
ℹ️ View Unchanged
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM, thanks 👍 Just one minor nit on the inline comment.
@WunderBart, is there a reason performance tests don't output the failure errors? Currently, they're not visible in the CI logs. I came across a similar failure last week and had to make a "wild guess" to fix it 😅 |
Co-authored-by: Marin Atanasov <[email protected]>
@Mamaduka, yeah it's been on my radar for a while now but I still don't know why it suddenly stopped printing in CI. I did attempt to log everything out to see if the logs work at all and they do, so I assume it's something with the Anyway, if nothing's printed, you can also check the failures-artifacts.zip because you'll usually find a trace.zip there that you'll be able to view via https://trace.playwright.dev/. It's usually the fastest way of telling what's wrong with the test! |
What?
This is needed for older branches where the current
loader
element is referred to asspinner
. We need to be able to compare the current code to the older one (e.g. iframed vs legacy canvas) so some elements that are now legacy still need support in the performance tests.Without this selector, this locator resolves immediately because it doesn't find a spinner element. This can cause the consequent canvas body click to timeout (flaky). See the attached trace as an example (taken from a failed CI job):
👉 trace.zip (open via https://trace.playwright.dev/)