Process completed with exit code 1.

TimeoutError: waiting for selector `div[data-slug="twentytwentyone"].active` 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/node_modules/@wordpress/e2e-test-utils/build/@wordpress/e2e-test-utils/src/activate-theme.js:31:13) at processTicksAndRejections (node:internal/process/task_queues:95:5) at Object.<anonymous> (/home/runner/work/amp-wp/amp-wp/tests/e2e/specs/core-themes/twentytwentyone.js:25:3)

TimeoutError: waiting for selector `div[data-slug="twentytwentyone"].active` 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/node_modules/@wordpress/e2e-test-utils/build/@wordpress/e2e-test-utils/src/activate-theme.js:31:13) at processTicksAndRejections (node:internal/process/task_queues:95:5) at Object.<anonymous> (/home/runner/work/amp-wp/amp-wp/tests/e2e/specs/core-themes/twentytwentyone.js:25:3)

Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, shivammathur/setup-php@2e947f1f6932d141d076ca441d0e1e881775e95b. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. 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 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, shivammathur/setup-php@2e947f1f6932d141d076ca441d0e1e881775e95b. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/

Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, actions/setup-node@60edb5dd545a775178f52524783378180af0d1f8. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/

Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, actions/setup-node@60edb5dd545a775178f52524783378180af0d1f8. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. 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 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, actions/setup-node@60edb5dd545a775178f52524783378180af0d1f8. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/

Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, actions/setup-node@60edb5dd545a775178f52524783378180af0d1f8, shivammathur/setup-php@2e947f1f6932d141d076ca441d0e1e881775e95b. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/

Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, actions/setup-node@60edb5dd545a775178f52524783378180af0d1f8, shivammathur/setup-php@2e947f1f6932d141d076ca441d0e1e881775e95b. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. 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