Ensure Gutenberg e2e tests pass for WP core trunk

[ellatrix]

Gutenberg e2e tests should generally pass when run on top of WP core without Gutenberg enabled, except for features that are not in core of course. There are currently only 19 failures in total, none of them seem to be related to Gutenberg-only features, so we should investigate them. This is a better number than I expected though, so we are in a pretty good shape.

​https://github.com/WordPress/gutenberg/pull/73440

Side note: I remember core running these tests on GitHub Actions, but I don't see them anymore. I'm not sure what happened to them.

[wildworks]

This ticket is related to the workflow, so I'll leave it as is for now. If there's no progress by the RC1 release next week, we'll punt this issue to 7.0.

[ellatrix]

I will be re-running these tests and checking the failures today. I think we should look into these failures to have more confidence in 6.9.

[ellatrix]

Btw, there's more failures because we still have to put template activation behind an experiment in Gutenberg. We can re-run after that.

[desrosj]

Is this a duplicate of #59659?

[ellatrix]

This is about specifically making sure they pass for WP 6.9 (which is a manual task right now), while the other ticket is about CI integration I think. Speaking about CI integration, wasn't it the case the GB e2e test were run in the wordpress-develop CI, or did I imagine that? 🙂

[ellatrix]

Summary: there's only two e2e test failures after removing GB-only features:

• A global styles revisions issue that's been there since last year, and fixed now: ​https://github.com/WordPress/wordpress-develop/pull/10541. Since it's been there for a while, we don't fix for 6.9.
• An interactivity API failure that is due to a change in Preact versions, it will be investigated, but it's not really an issue for 6.9. Cc @luisherranz.

So with that, I'm closing this ticket.