Elements: Avoid specificity bump for top-level element-only selectors #33735
Annotations
2 errors and 1 notice
|
tests/e2e/specs/install.test.js#L40
1) [chromium] › install.test.js:34:6 › WordPress installation process › should install WordPress with pre-existing database credentials
Error: should redirect to the installation page
Timed out 5000ms waiting for expect(locator).toHaveURL(expected)
Locator: locator(':root')
Expected pattern: /wp-admin\/install\.php$/
Received string: "http://localhost:8889/"
Call log:
- should redirect to the installation page with timeout 5000ms
- waiting for locator(':root')
- locator resolved to <html lang="en-US">…</html>
- unexpected value "http://localhost:8889/"
- locator resolved to <html lang="en-US">…</html>
- unexpected value "http://localhost:8889/"
- locator resolved to <html lang="en-US">…</html>
- unexpected value "http://localhost:8889/"
- locator resolved to <html lang="en-US">…</html>
- unexpected value "http://localhost:8889/"
- locator resolved to <html lang="en-US">…</html>
- unexpected value "http://localhost:8889/"
- locator resolved to <html lang="en-US">…</html>
- unexpected value "http://localhost:8889/"
- locator resolved to <html lang="en-US">…</html>
- unexpected value "http://localhost:8889/"
- locator resolved to <html lang="en-US">…</html>
- unexpected value "http://localhost:8889/"
- locator resolved to <html lang="en-US">…</html>
- unexpected value "http://localhost:8889/"
38 | page,
39 | 'should redirect to the installation page'
> 40 | ).toHaveURL( /wp-admin\/install\.php$/ );
| ^
41 |
42 | await expect(
43 | page.getByText( /WordPress database error/ ),
at /home/runner/work/wordpress-develop/wordpress-develop/tests/e2e/specs/install.test.js:40:5
|
|
tests/e2e/specs/profile/applications-passwords.test.js#L128
2) [chromium] › profile/applications-passwords.test.js:19:6 › Manage applications passwords › should correctly create a new application password
Error: apiRequestContext.get: 400 Bad Request
Call log:
- → GET http://localhost:8889/wp-admin/admin-ajax.php?action=rest-nonce
- user-agent: Playwright/1.45.0 (x64; ubuntu 22.04) node/20.15 CI/1
- accept: */*
- accept-encoding: gzip,deflate,br
- cookie: wordpress_test_cookie=WP%20Cookie%20check; wordpress_23778236db82f19306f247e20a353a99=admin%7C1720858672%7CSLhedNUa555CUEFMgIoy6AGfiTo8oW2Mxf4PWTaprFD%7C79c58af3c5cf4d5296d7a344d933f50bd7ebd21ab6ffe3255864b0b1c04a859b; wordpress_logged_in_23778236db82f19306f247e20a353a99=admin%7C1720858672%7CSLhedNUa555CUEFMgIoy6AGfiTo8oW2Mxf4PWTaprFD%7Caaae8646a3c7ccc370b95194c9bc8e2c455ee20af95361012ad9f85debb8a285; wp-settings-time-1=1720685873
- ← 400 Bad Request
- server: nginx/1.27.0
- date: Thu, 11 Jul 2024 08:17:53 GMT
- content-type: text/html; charset=UTF-8
- transfer-encoding: chunked
- connection: close
- x-powered-by: PHP/8.2.21
- x-robots-tag: noindex
- x-content-type-options: nosniff
- referrer-policy: strict-origin-when-cross-origin
- x-frame-options: SAMEORIGIN
- expires: Wed, 11 Jan 1984 05:00:00 GMT
- cache-control: no-cache, must-revalidate, max-age=0
126 |
127 | async delete() {
> 128 | await this.requestUtils.rest( {
| ^
129 | method: 'DELETE',
130 | path: '/wp/v2/users/me/application-passwords',
131 | } );
at RequestUtils.login (/home/runner/work/wordpress-develop/wordpress-develop/node_modules/@wordpress/e2e-test-utils-playwright/src/request-utils/login.ts:23:32)
at RequestUtils.setupRest (/home/runner/work/wordpress-develop/wordpress-develop/node_modules/@wordpress/e2e-test-utils-playwright/src/request-utils/rest.ts:42:29)
at RequestUtils.rest (/home/runner/work/wordpress-develop/wordpress-develop/node_modules/@wordpress/e2e-test-utils-playwright/src/request-utils/rest.ts:119:4)
at ApplicationPasswords.delete (/home/runner/work/wordpress-develop/wordpress-develop/tests/e2e/specs/profile/applications-passwords.test.js:128:3)
at /home/runner/work/wordpress-develop/wordpress-develop/tests/e2e/specs/profile/applications-passwords.test.js:16:3
|
|
2 flaky
[chromium] › install.test.js:34:6 › WordPress installation process › should install WordPress with pre-existing database credentials
[chromium] › profile/applications-passwords.test.js:19:6 › Manage applications passwords › should correctly create a new application password
22 passed (47.5s)
|
The logs for this run have expired and are no longer available.
Loading