-
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
Block fixtures: Change port to 8889 to placate KSES #37100
Conversation
The unit tests runner handles those integrations tests and it has the following URL configured: gutenberg/test/unit/jest.config.js Line 24 in d2f0c66
|
Thanks @gziolo. The PR does seem to fix the fixture errors tho (although there's an unrelated error that's still present) -- compare e.g. https://github.com/WordPress/gutenberg/runs/4408490770?check_suite_focus=true (current Curious to hear your suggestion -- are you saying you'd rather remove the port altogether from the fixtures? Or is it okay to go ahead with this fix as-is? |
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.
You applied the changes correctly 👍 The same test fixtures are also used with PHPUnit, so it'd be the reason why it needs the same port. It probably is less critical for unit tests, but maybe we should align that separately from this PR.
I got confused because of the location of fixtures 🙈
Thanks @gziolo -- I'll go ahead and merge 😄 FWIW, the remaining PHP unit test that's failing
is probably due to WordPress/wordpress-develop@1270c89 (committed today at 11:34 UTC): I noticed it wasn't present on cc/ @audrasjb |
Thanks for looking at this @ockham ! |
Filed an issue for this: #37116 |
Unit tests are currently failing on `trunk` (when used with a current snapshot of the WordPress svn or git repo). Specifically: `Block_Fixture_Test::test_kses_doesnt_change_fixtures` fails for datasets #54 and #55. Reading WordPress/wordpress-develop#1998, I believe that the reason might be that our KSES routines are verifying that the specified port matches the one of the local install. And since our tests normally run `localhost:8889`, I'm updating the relevant test fixtures (from previously `8888`) to reflect that.
Unit tests are currently failing on `trunk` (when used with a current snapshot of the WordPress svn or git repo). Specifically: `Block_Fixture_Test::test_kses_doesnt_change_fixtures` fails for datasets #54 and #55. Reading WordPress/wordpress-develop#1998, I believe that the reason might be that our KSES routines are verifying that the specified port matches the one of the local install. And since our tests normally run `localhost:8889`, I'm updating the relevant test fixtures (from previously `8888`) to reflect that.
Description
Unit tests are currently failing on
trunk
(when used with a current snapshot of the WordPress svn or git repo).Specifically:
Block_Fixture_Test::test_kses_doesnt_change_fixtures
fails for datasets #54 and #55.Reading WordPress/wordpress-develop#1998, I believe that the reason might be that our KSES routines are verifying that the specified port matches the one of the local install. And since our tests normally run
localhost:8889
, I'm updating the relevant test fixtures (from previously8888
) to reflect that.How has this been tested?
Verify that CI goes green 🤞
Types of changes
Bug fix