Skip to content

Fix PHP 8.4 execute() return type and add PHP 8.5 / Magento 2.4.9 support #46

Fix PHP 8.4 execute() return type and add PHP 8.5 / Magento 2.4.9 support

Fix PHP 8.4 execute() return type and add PHP 8.5 / Magento 2.4.9 support #46

Status Failure
Total duration 2m 50s
Artifacts

integration.yml

on: pull_request
Magento 2 Integration Tests (Magento 2.4.5)
1m 9s
Magento 2 Integration Tests (Magento 2.4.5)
Magento 2 Integration Tests (Magento 2.4.6)
2m 28s
Magento 2 Integration Tests (Magento 2.4.6)
Magento 2 Integration Tests (Magento 2.4.7)
2m 44s
Magento 2 Integration Tests (Magento 2.4.7)
Magento 2 Integration Tests (Magento 2.4.8)
49s
Magento 2 Integration Tests (Magento 2.4.8)
Magento 2 Integration Tests (Magento 2.4.9)
57s
Magento 2 Integration Tests (Magento 2.4.9)
Fit to window
Zoom out
Zoom in

Annotations

5 errors and 3 warnings
Magento 2 Integration Tests (Magento 2.4.8)
One or more containers failed to start.
Magento 2 Integration Tests (Magento 2.4.8)
Failed to initialize container docker.io/wardenenv/elasticsearch:8.1
Magento 2 Integration Tests (Magento 2.4.9)
One or more containers failed to start.
Magento 2 Integration Tests (Magento 2.4.9)
Failed to initialize container docker.io/wardenenv/opensearch:3.4
Magento 2 Integration Tests (Magento 2.4.5)
Your requirements could not be resolved to an installable set of packages. Problem 1 - Root composer.json requires magento/product-community-edition 2.4.5-p12 -> satisfiable by magento/product-community-edition[2.4.5-p12]. - magento/product-community-edition 2.4.5-p12 requires webonyx/graphql-php ~14.11.6 -> found webonyx/graphql-php[v14.11.6, ..., v14.11.10] but these were not loaded, because they are affected by security advisories ("PKSA-xwpn-zs9j-6wy5", "PKSA-sf9j-1gs7-xzvx", "PKSA-7h5p-prw9-w5nr"). Go to https://packagist.org/security-advisories/ to find advisory details. To ignore the advisories, add them to the audit "ignore" config. To turn the feature off entirely, you can set "block-insecure" to false in your "audit" config.
Magento 2 Integration Tests (Magento 2.4.5)
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 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/
Magento 2 Integration Tests (Magento 2.4.6)
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 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/
Magento 2 Integration Tests (Magento 2.4.7)
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 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/