Make WordPress Core

Opened 3 years ago

Last modified 22 months ago

#54397 new defect (bug)

e2e timeout errors: waiting for selection `.components-snackbar`

Reported by: hellofromtonya's profile hellofromTonya Owned by:
Milestone: Awaiting Review Priority: normal
Severity: normal Version:
Component: Build/Test Tools Keywords:
Focuses: Cc:


The CI is experiencing too many e2e time out errors, which may indicate a flaky test or instability. This ticket is opened to investigate and monitor for stability improvements.


TimeoutError: waiting for selector `.components-snackbar` failed: timeout 30000ms exceeded
    at new WaitTask (/home/runner/work/wordpress-develop/wordpress-develop/node_modules/puppeteer-core/src/common/DOMWorld.ts:780:28)
    at DOMWorld.waitForSelectorInPage (/home/runner/work/wordpress-develop/wordpress-develop/node_modules/puppeteer-core/src/common/DOMWorld.ts:632:22)
    at Object.internalHandler.waitFor (/home/runner/work/wordpress-develop/wordpress-develop/node_modules/puppeteer-core/src/common/QueryHandler.ts:78:19)
    at DOMWorld.waitForSelector (/home/runner/work/wordpress-develop/wordpress-develop/node_modules/puppeteer-core/src/common/DOMWorld.ts:490:25)
    at Frame.waitForSelector (/home/runner/work/wordpress-develop/wordpress-develop/node_modules/puppeteer-core/src/common/FrameManager.ts:1163:47)
    at Page.waitForSelector (/home/runner/work/wordpress-develop/wordpress-develop/node_modules/puppeteer-core/src/common/Page.ts:2100:29)
    at publishPost (/home/runner/work/wordpress-develop/wordpress-develop/node_modules/@wordpress/e2e-test-utils/build/@wordpress/e2e-test-utils/src/publish-post.js:19:14)
    at runMicrotasks (<anonymous>)
    at processTicksAndRejections (internal/process/task_queues.js:95:5)
    at Object.<anonymous> (/home/runner/work/wordpress-develop/wordpress-develop/tests/e2e/specs/edit-posts.test.js:25:3)

Capturing CI job runs where it failed:

Change History (6)

This ticket was mentioned in Slack in #core by hellofromtonya. View the logs.

3 years ago

This ticket was mentioned in Slack in #core-test by hellofromtonya. View the logs.

3 years ago

#3 @youknowriad
3 years ago

I noticed these as well, I think these failures are probably there since these tests have been added. My suspicions is CSS animations, in the Gutenberg tests relying on the same helpers, there's no flakiness, but there are two extra things done on the Gutenberg e2e setup:

#4 @isabel_brison
3 years ago

All of these failures are happening in the publishPost function imported from the e2e-test-utils package. What's interesting is that function is used in most of the tests from that suite and only one of them is consistently failing: shows a single post after one is published with the correct title (though allows an existing post to be deleted using the Trash button also failed in one of those runs).

#5 @justinahinon
3 years ago

This happens very randomly (at least on local env). I've run the test up to 20 times, for i in {1..20}; do npm run test:e2e -- tests/e2e/specs/edit-posts.test.js; done and had only one failure.

@isabel_brison in the publishPost() function, could we wait for the content in the body panel instead of the snack bar? See

#6 @desrosj
22 months ago

  • Type changed from task (blessed) to defect (bug)
Note: See TracTickets for help on using tickets.