Process completed with exit code 1.

TimeoutError: waiting for selector `.wp-admin` failed: timeout 60000ms exceeded at new WaitTask (/home/runner/work/amp-wp/amp-wp/node_modules/@wordpress/scripts/node_modules/puppeteer-core/src/common/DOMWorld.ts:813:28) at DOMWorld.waitForSelectorInPage (/home/runner/work/amp-wp/amp-wp/node_modules/@wordpress/scripts/node_modules/puppeteer-core/src/common/DOMWorld.ts:656:22) at Object.internalHandler.waitFor (/home/runner/work/amp-wp/amp-wp/node_modules/@wordpress/scripts/node_modules/puppeteer-core/src/common/QueryHandler.ts:78:19) at DOMWorld.waitForSelector (/home/runner/work/amp-wp/amp-wp/node_modules/@wordpress/scripts/node_modules/puppeteer-core/src/common/DOMWorld.ts:511:25) at Frame.waitForSelector (/home/runner/work/amp-wp/amp-wp/node_modules/@wordpress/scripts/node_modules/puppeteer-core/src/common/FrameManager.ts:1290:47) at Page.waitForSelector (/home/runner/work/amp-wp/amp-wp/node_modules/@wordpress/scripts/node_modules/puppeteer-core/src/common/Page.ts:3222:29) at Object.waitForSelector (/home/runner/work/amp-wp/amp-wp/tests/e2e/specs/amp-onboarding/exit-links.js:43:14) at processTicksAndRejections (node:internal/process/task_queues:95:5)

Process completed with exit code 1.

Error: No node found for selector: tr[data-slug="gutenberg"] .deactivate a at assert (/home/runner/work/amp-wp/amp-wp/node_modules/@wordpress/scripts/node_modules/puppeteer-core/src/common/assert.ts:23:21) at DOMWorld.click (/home/runner/work/amp-wp/amp-wp/node_modules/@wordpress/scripts/node_modules/puppeteer-core/src/common/DOMWorld.ts:461:11) at processTicksAndRejections (node:internal/process/task_queues:95:5) at deactivate (/home/runner/work/amp-wp/amp-wp/tests/e2e/specs/admin/after-plugin-activation.js:15:3) at /home/runner/work/amp-wp/amp-wp/tests/e2e/specs/admin/after-plugin-activation.js:68:5

TimeoutError: waiting for selector `tr[data-slug="e2e-tests-demo-plugin"] .deactivate a` failed: timeout 60000ms exceeded at new WaitTask (/home/runner/work/amp-wp/amp-wp/node_modules/@wordpress/scripts/node_modules/puppeteer-core/src/common/DOMWorld.ts:813:28) at DOMWorld.waitForSelectorInPage (/home/runner/work/amp-wp/amp-wp/node_modules/@wordpress/scripts/node_modules/puppeteer-core/src/common/DOMWorld.ts:656:22) at Object.internalHandler.waitFor (/home/runner/work/amp-wp/amp-wp/node_modules/@wordpress/scripts/node_modules/puppeteer-core/src/common/QueryHandler.ts:78:19) at DOMWorld.waitForSelector (/home/runner/work/amp-wp/amp-wp/node_modules/@wordpress/scripts/node_modules/puppeteer-core/src/common/DOMWorld.ts:511:25) at Frame.waitForSelector (/home/runner/work/amp-wp/amp-wp/node_modules/@wordpress/scripts/node_modules/puppeteer-core/src/common/FrameManager.ts:1290:47) at Page.waitForSelector (/home/runner/work/amp-wp/amp-wp/node_modules/@wordpress/scripts/node_modules/puppeteer-core/src/common/Page.ts:3222:29) at waitForSelector (/home/runner/work/amp-wp/amp-wp/tests/e2e/specs/admin/after-plugin-activation.js:21:14) at processTicksAndRejections (node:internal/process/task_queues:95:5) at /home/runner/work/amp-wp/amp-wp/tests/e2e/specs/admin/after-plugin-activation.js:71:4

TimeoutError: waiting for selector `tr[data-slug="gutenberg"] .deactivate a` failed: timeout 60000ms exceeded at new WaitTask (/home/runner/work/amp-wp/amp-wp/node_modules/@wordpress/scripts/node_modules/puppeteer-core/src/common/DOMWorld.ts:813:28) at DOMWorld.waitForSelectorInPage (/home/runner/work/amp-wp/amp-wp/node_modules/@wordpress/scripts/node_modules/puppeteer-core/src/common/DOMWorld.ts:656:22) at Object.internalHandler.waitFor (/home/runner/work/amp-wp/amp-wp/node_modules/@wordpress/scripts/node_modules/puppeteer-core/src/common/QueryHandler.ts:78:19) at DOMWorld.waitForSelector (/home/runner/work/amp-wp/amp-wp/node_modules/@wordpress/scripts/node_modules/puppeteer-core/src/common/DOMWorld.ts:511:25) at Frame.waitForSelector (/home/runner/work/amp-wp/amp-wp/node_modules/@wordpress/scripts/node_modules/puppeteer-core/src/common/FrameManager.ts:1290:47) at Page.waitForSelector (/home/runner/work/amp-wp/amp-wp/node_modules/@wordpress/scripts/node_modules/puppeteer-core/src/common/Page.ts:3222:29) at waitForSelector (/home/runner/work/amp-wp/amp-wp/tests/e2e/specs/admin/after-plugin-activation.js:21:14) at processTicksAndRejections (node:internal/process/task_queues:95:5) at Object.<anonymous> (/home/runner/work/amp-wp/amp-wp/tests/e2e/specs/admin/after-plugin-activation.js:34:3)

Node.js 20 is deprecated. The following actions target Node.js 20 but are being forced to run on Node.js 24: actions/cache@v4, shivammathur/setup-php@2e947f1f6932d141d076ca441d0e1e881775e95b. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/

When passing the $key parameter to get_post_meta(), it is recommended to also pass the $single parameter to explicitly indicate whether a single value or multiple values are expected to be returned.

When passing the $key parameter to get_post_meta(), it is recommended to also pass the $single parameter to explicitly indicate whether a single value or multiple values are expected to be returned.

When passing the $key parameter to get_post_meta(), it is recommended to also pass the $single parameter to explicitly indicate whether a single value or multiple values are expected to be returned.

When passing the $key parameter to get_post_meta(), it is recommended to also pass the $single parameter to explicitly indicate whether a single value or multiple values are expected to be returned.

When passing the $key parameter to get_post_meta(), it is recommended to also pass the $single parameter to explicitly indicate whether a single value or multiple values are expected to be returned.

When passing the $key parameter to get_post_meta(), it is recommended to also pass the $single parameter to explicitly indicate whether a single value or multiple values are expected to be returned.

When passing the $key parameter to get_post_meta(), it is recommended to also pass the $single parameter to explicitly indicate whether a single value or multiple values are expected to be returned.

When passing the $key parameter to get_post_meta(), it is recommended to also pass the $single parameter to explicitly indicate whether a single value or multiple values are expected to be returned.

When passing the $key parameter to get_post_meta(), it is recommended to also pass the $single parameter to explicitly indicate whether a single value or multiple values are expected to be returned.

When passing the $key parameter to get_post_meta(), it is recommended to also pass the $single parameter to explicitly indicate whether a single value or multiple values are expected to be returned.

Node.js 20 is deprecated. The following actions target Node.js 20 but are being forced to run on Node.js 24: actions/cache@v4, actions/setup-node@60edb5dd545a775178f52524783378180af0d1f8. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/

Prefer a more specific type to `Function`

Prefer a more specific type to `Function`

Prefer a more specific type to `Function`

Prefer a more specific type to `Function`

Prefer a more specific type to `Function`

Prefer a more specific type to `*`

Prefer a more specific type to `Function`

Prefer a more specific type to `any`

Prefer a more specific type to `any`

Prefer a more specific type to `any`

Node.js 20 is deprecated. The following actions target Node.js 20 but are being forced to run on Node.js 24: actions/cache@v4, actions/setup-node@60edb5dd545a775178f52524783378180af0d1f8. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/

Node.js 20 is deprecated. The following actions target Node.js 20 but are being forced to run on Node.js 24: actions/cache@v4, actions/setup-node@60edb5dd545a775178f52524783378180af0d1f8. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/

Node.js 20 is deprecated. The following actions target Node.js 20 but are being forced to run on Node.js 24: actions/cache@v4, actions/setup-node@60edb5dd545a775178f52524783378180af0d1f8, shivammathur/setup-php@2e947f1f6932d141d076ca441d0e1e881775e95b. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/

Node.js 20 is deprecated. The following actions target Node.js 20 but are being forced to run on Node.js 24: actions/cache@v4, shivammathur/setup-php@2e947f1f6932d141d076ca441d0e1e881775e95b. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/

Node.js 20 is deprecated. The following actions target Node.js 20 but are being forced to run on Node.js 24: actions/cache@v4, actions/setup-node@60edb5dd545a775178f52524783378180af0d1f8, shivammathur/setup-php@2e947f1f6932d141d076ca441d0e1e881775e95b. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/

Using Chromium from /home/runner/.cache/puppeteer/chrome/linux-127.0.6533.88/chrome-linux64/chrome