Process completed with exit code 1.

1) [chromium] › tests/e2e/cloudinary-video-delivery.spec.js:195:3 › Cloudinary video delivery › with Cloudinary player › renders a Cloudinary player iframe pointing at our cloud Retry #2 ─────────────────────────────────────────────────────────────────────────────────────── Error: Command failed: docker exec a5f8e834bffdce553115981e6b62a8ac-tests-cli-1 wp option patch insert cloudinary_media_display video_player wp --allow-root Error: Cannot create key "video_player" on data type boolean at utils/wizard.js:73 71 | ].join( ' ' ); 72 | > 73 | return execSync( cmd, { | ^ 74 | encoding: 'utf8', 75 | stdio: [ 'ignore', 'pipe', 'pipe' ], 76 | } ).trim(); at wpCli (/home/runner/work/cloudinary_wordpress/cloudinary_wordpress/tests/e2e/utils/wizard.js:73:9) at /home/runner/work/cloudinary_wordpress/cloudinary_wordpress/tests/e2e/cloudinary-video-delivery.spec.js:185:4

1) [chromium] › tests/e2e/cloudinary-video-delivery.spec.js:195:3 › Cloudinary video delivery › with Cloudinary player › renders a Cloudinary player iframe pointing at our cloud Retry #2 ─────────────────────────────────────────────────────────────────────────────────────── Error: Command failed: docker exec a5f8e834bffdce553115981e6b62a8ac-tests-cli-1 wp option patch insert cloudinary_media_display video_player cld --allow-root Error: Cannot create key "video_player" on data type boolean at utils/wizard.js:73 71 | ].join( ' ' ); 72 | > 73 | return execSync( cmd, { | ^ 74 | encoding: 'utf8', 75 | stdio: [ 'ignore', 'pipe', 'pipe' ], 76 | } ).trim(); at wpCli (/home/runner/work/cloudinary_wordpress/cloudinary_wordpress/tests/e2e/utils/wizard.js:73:9) at /home/runner/work/cloudinary_wordpress/cloudinary_wordpress/tests/e2e/cloudinary-video-delivery.spec.js:174:4

1) [chromium] › tests/e2e/cloudinary-video-delivery.spec.js:195:3 › Cloudinary video delivery › with Cloudinary player › renders a Cloudinary player iframe pointing at our cloud Retry #1 ─────────────────────────────────────────────────────────────────────────────────────── Error: Command failed: docker exec a5f8e834bffdce553115981e6b62a8ac-tests-cli-1 wp option patch insert cloudinary_media_display video_player wp --allow-root Error: Cannot create key "video_player" on data type boolean at utils/wizard.js:73 71 | ].join( ' ' ); 72 | > 73 | return execSync( cmd, { | ^ 74 | encoding: 'utf8', 75 | stdio: [ 'ignore', 'pipe', 'pipe' ], 76 | } ).trim(); at wpCli (/home/runner/work/cloudinary_wordpress/cloudinary_wordpress/tests/e2e/utils/wizard.js:73:9) at /home/runner/work/cloudinary_wordpress/cloudinary_wordpress/tests/e2e/cloudinary-video-delivery.spec.js:185:4

1) [chromium] › tests/e2e/cloudinary-video-delivery.spec.js:195:3 › Cloudinary video delivery › with Cloudinary player › renders a Cloudinary player iframe pointing at our cloud Retry #1 ─────────────────────────────────────────────────────────────────────────────────────── Error: Command failed: docker exec a5f8e834bffdce553115981e6b62a8ac-tests-cli-1 wp option patch insert cloudinary_media_display video_player cld --allow-root Error: Cannot create key "video_player" on data type boolean at utils/wizard.js:73 71 | ].join( ' ' ); 72 | > 73 | return execSync( cmd, { | ^ 74 | encoding: 'utf8', 75 | stdio: [ 'ignore', 'pipe', 'pipe' ], 76 | } ).trim(); at wpCli (/home/runner/work/cloudinary_wordpress/cloudinary_wordpress/tests/e2e/utils/wizard.js:73:9) at /home/runner/work/cloudinary_wordpress/cloudinary_wordpress/tests/e2e/cloudinary-video-delivery.spec.js:174:4

1) [chromium] › tests/e2e/cloudinary-video-delivery.spec.js:195:3 › Cloudinary video delivery › with Cloudinary player › renders a Cloudinary player iframe pointing at our cloud Error: Command failed: docker exec a5f8e834bffdce553115981e6b62a8ac-tests-cli-1 wp option patch insert cloudinary_media_display video_player wp --allow-root Error: Cannot create key "video_player" on data type boolean at utils/wizard.js:73 71 | ].join( ' ' ); 72 | > 73 | return execSync( cmd, { | ^ 74 | encoding: 'utf8', 75 | stdio: [ 'ignore', 'pipe', 'pipe' ], 76 | } ).trim(); at wpCli (/home/runner/work/cloudinary_wordpress/cloudinary_wordpress/tests/e2e/utils/wizard.js:73:9) at /home/runner/work/cloudinary_wordpress/cloudinary_wordpress/tests/e2e/cloudinary-video-delivery.spec.js:185:4

1) [chromium] › tests/e2e/cloudinary-video-delivery.spec.js:195:3 › Cloudinary video delivery › with Cloudinary player › renders a Cloudinary player iframe pointing at our cloud Error: Command failed: docker exec a5f8e834bffdce553115981e6b62a8ac-tests-cli-1 wp option patch insert cloudinary_media_display video_player cld --allow-root Error: Cannot create key "video_player" on data type boolean at utils/wizard.js:73 71 | ].join( ' ' ); 72 | > 73 | return execSync( cmd, { | ^ 74 | encoding: 'utf8', 75 | stdio: [ 'ignore', 'pipe', 'pipe' ], 76 | } ).trim(); at wpCli (/home/runner/work/cloudinary_wordpress/cloudinary_wordpress/tests/e2e/utils/wizard.js:73:9) at /home/runner/work/cloudinary_wordpress/cloudinary_wordpress/tests/e2e/cloudinary-video-delivery.spec.js:174:4

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/checkout@v4, actions/setup-node@v4. Actions will be forced to run with Node.js 24 by default starting June 16th, 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/checkout@v4, actions/setup-node@v4. Actions will be forced to run with Node.js 24 by default starting June 16th, 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/checkout@v4, actions/setup-node@v4, actions/upload-artifact@v4. Actions will be forced to run with Node.js 24 by default starting June 16th, 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/