Skip to content

Support for PHP 8.3 and Laravel 11 #43

Support for PHP 8.3 and Laravel 11

Support for PHP 8.3 and Laravel 11 #43

Triggered via pull request March 18, 2024 17:23
Status Failure
Total duration 8m 34s
Artifacts 3

tests.yml

on: pull_request
Matrix: stub-tests
Matrix: tests
Fit to window
Zoom out
Zoom in

Annotations

12 errors and 18 warnings
Unit/Feature Tests - P8.3 - L11
Your requirements could not be resolved to an installable set of packages. Problem 1 - Root composer.json requires protonemedia/laravel-splade ^1.4.18 -> satisfiable by protonemedia/laravel-splade[1.4.18]. - Conclusion: don't install laravel/framework v10.0.0 (conflict analysis result) - Conclusion: don't install laravel/framework v10.0.1 (conflict analysis result) - Conclusion: don't install laravel/framework v10.0.2 (conflict analysis result) - Conclusion: don't install laravel/framework v10.0.3 (conflict analysis result) - Conclusion: don't install laravel/framework v10.1.0 (conflict analysis result) - Conclusion: don't install laravel/framework v10.1.1 (conflict analysis result) - Conclusion: don't install laravel/framework v10.1.2 (conflict analysis result) - Conclusion: don't install laravel/framework v10.1.3 (conflict analysis result) - Conclusion: don't install laravel/framework v10.1.4 (conflict analysis result) - Conclusion: don't install laravel/framework v10.1.5 (conflict analysis result) - Conclusion: don't install laravel/framework v10.2.0 (conflict analysis result) - Conclusion: don't install laravel/framework v10.3.0 (conflict analysis result) - Conclusion: don't install laravel/framework v10.3.1 (conflict analysis result) - Conclusion: don't install laravel/framework v10.3.2 (conflict analysis result) - Conclusion: don't install laravel/framework v10.3.3 (conflict analysis result) - Conclusion: don't install laravel/framework v10.4.0 (conflict analysis result) - Conclusion: don't install laravel/framework v10.4.1 (conflict analysis result) - Conclusion: don't install laravel/framework v10.5.0 (conflict analysis result) - Conclusion: don't install laravel/framework v10.5.1 (conflict analysis result) - Conclusion: don't install laravel/framework v10.6.0 (conflict analysis result) - Conclusion: don't install laravel/framework v10.6.1 (conflict analysis result) - Conclusion: don't install laravel/framework v10.6.2 (conflict analysis result) - Conclusion: don't install laravel/framework v10.7.0 (conflict analysis result) - Conclusion: don't install laravel/framework v10.7.1 (conflict analysis result) - Conclusion: don't install laravel/framework v10.8.0 (conflict analysis result) - Conclusion: don't install laravel/framework v10.9.0 (conflict analysis result) - Conclusion: don't install laravel/framework v10.10.0 (conflict analysis result) - Conclusion: don't install laravel/framework v10.10.1 (conflict analysis result) - Conclusion: don't install laravel/framework v10.11.0 (conflict analysis result) - Conclusion: don't install laravel/framework v10.12.0 (conflict analysis result) - Conclusion: don't install laravel/framework v10.13.0 (conflict analysis result) - Conclusion: don't install laravel/framework v10.13.1 (conflict analysis result) - Conclusion: don't install laravel/framework v10.13.2 (conflict analysis result) - Conclusion: don't install laravel/framework v10.13.3 (conflict analysis result) - Conclusion: don't install laravel/framework v10.13.5 (conflict analysis result) - Conclusion: don't install laravel/framework v10.14.0 (conflict analysis result) - Conclusion: don't install laravel/framework v10.14.1 (conflict analysis result) - Conclusion: don't install laravel/framework v10.15.0 (conflict analysis result) - Conclusion: don't install laravel/framework v10.16.0 (conflict analysis result) - Conclusion: don't install laravel/framework v10.16.1 (conflict analysis result) - Conclusion: don't install laravel/framework v10.17.0 (conflict analysis result) - Conclusion: don't install laravel/framework v10.17.1 (conflict analysis result) - Conclusion: don't install laravel/framework v10.18.0 (conflict analysis result) - Conclusion: don't install laravel/framework v10.19.0 (conflict analysis result) - Conclusion: don't install laravel/framework v10.20.0 (conflict analysis result) - Conclusion: don't install laravel
Unit/Feature Tests - P8.3 - L11
Process completed with exit code 2.
Unit/Feature Tests - P8.2 - L11
Your requirements could not be resolved to an installable set of packages. Problem 1 - Root composer.json requires protonemedia/laravel-splade ^1.4.18 -> satisfiable by protonemedia/laravel-splade[1.4.18]. - Conclusion: don't install laravel/framework v10.0.0 (conflict analysis result) - Conclusion: don't install laravel/framework v10.0.1 (conflict analysis result) - Conclusion: don't install laravel/framework v10.0.2 (conflict analysis result) - Conclusion: don't install laravel/framework v10.0.3 (conflict analysis result) - Conclusion: don't install laravel/framework v10.1.0 (conflict analysis result) - Conclusion: don't install laravel/framework v10.1.1 (conflict analysis result) - Conclusion: don't install laravel/framework v10.1.2 (conflict analysis result) - Conclusion: don't install laravel/framework v10.1.3 (conflict analysis result) - Conclusion: don't install laravel/framework v10.1.4 (conflict analysis result) - Conclusion: don't install laravel/framework v10.1.5 (conflict analysis result) - Conclusion: don't install laravel/framework v10.2.0 (conflict analysis result) - Conclusion: don't install laravel/framework v10.3.0 (conflict analysis result) - Conclusion: don't install laravel/framework v10.3.1 (conflict analysis result) - Conclusion: don't install laravel/framework v10.3.2 (conflict analysis result) - Conclusion: don't install laravel/framework v10.3.3 (conflict analysis result) - Conclusion: don't install laravel/framework v10.4.0 (conflict analysis result) - Conclusion: don't install laravel/framework v10.4.1 (conflict analysis result) - Conclusion: don't install laravel/framework v10.5.0 (conflict analysis result) - Conclusion: don't install laravel/framework v10.5.1 (conflict analysis result) - Conclusion: don't install laravel/framework v10.6.0 (conflict analysis result) - Conclusion: don't install laravel/framework v10.6.1 (conflict analysis result) - Conclusion: don't install laravel/framework v10.6.2 (conflict analysis result) - Conclusion: don't install laravel/framework v10.7.0 (conflict analysis result) - Conclusion: don't install laravel/framework v10.7.1 (conflict analysis result) - Conclusion: don't install laravel/framework v10.8.0 (conflict analysis result) - Conclusion: don't install laravel/framework v10.9.0 (conflict analysis result) - Conclusion: don't install laravel/framework v10.10.0 (conflict analysis result) - Conclusion: don't install laravel/framework v10.10.1 (conflict analysis result) - Conclusion: don't install laravel/framework v10.11.0 (conflict analysis result) - Conclusion: don't install laravel/framework v10.12.0 (conflict analysis result) - Conclusion: don't install laravel/framework v10.13.0 (conflict analysis result) - Conclusion: don't install laravel/framework v10.13.1 (conflict analysis result) - Conclusion: don't install laravel/framework v10.13.2 (conflict analysis result) - Conclusion: don't install laravel/framework v10.13.3 (conflict analysis result) - Conclusion: don't install laravel/framework v10.13.5 (conflict analysis result) - Conclusion: don't install laravel/framework v10.14.0 (conflict analysis result) - Conclusion: don't install laravel/framework v10.14.1 (conflict analysis result) - Conclusion: don't install laravel/framework v10.15.0 (conflict analysis result) - Conclusion: don't install laravel/framework v10.16.0 (conflict analysis result) - Conclusion: don't install laravel/framework v10.16.1 (conflict analysis result) - Conclusion: don't install laravel/framework v10.17.0 (conflict analysis result) - Conclusion: don't install laravel/framework v10.17.1 (conflict analysis result) - Conclusion: don't install laravel/framework v10.18.0 (conflict analysis result) - Conclusion: don't install laravel/framework v10.19.0 (conflict analysis result) - Conclusion: don't install laravel/framework v10.20.0 (conflict analysis result) - Conclusion: don't install laravel
Unit/Feature Tests - P8.2 - L11
Process completed with exit code 2.
Unit/Feature Tests - P8.2 - L10.2
The job was canceled because "_8_3_11" failed.
Unit/Feature Tests - P8.2 - L10.2
The operation was canceled.
Dusk Tests - P8.3 - L11
Process completed with exit code 1.
Unit/Feature Tests - P8.3 - L10.2
The job was canceled because "_8_3_11" failed.
Unit/Feature Tests - P8.3 - L10.2
The operation was canceled.
Dusk Tests - P8.2 - L11
Process completed with exit code 1.
Dusk Tests - P8.2 - L10.2
Final attempt failed. Child_process exited with error code 2
Dusk Tests - P8.3 - L10.2
Final attempt failed. Child_process exited with error code 2
Unit/Feature Tests - P8.3 - L11
Node.js 16 actions are deprecated. Please update the following actions to use Node.js 20: actions/checkout@v3. For more information see: https://github.blog/changelog/2023-09-22-github-actions-transitioning-from-node-16-to-node-20/.
Unit/Feature Tests - P8.2 - L11
Node.js 16 actions are deprecated. Please update the following actions to use Node.js 20: actions/checkout@v3. For more information see: https://github.blog/changelog/2023-09-22-github-actions-transitioning-from-node-16-to-node-20/.
Dusk Tests - P8.3 - L11
Node.js 16 actions are deprecated. Please update the following actions to use Node.js 20: actions/checkout@v2, actions/upload-artifact@v3. For more information see: https://github.blog/changelog/2023-09-22-github-actions-transitioning-from-node-16-to-node-20/.
Dusk Tests - P8.3 - L11
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/checkout@v2. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
Dusk Tests - P8.3 - L11
No files were found with the provided path: tests/Browser/console. No artifacts will be uploaded.
Dusk Tests - P8.3 - L11
No files were found with the provided path: tests/Browser/screenshots. No artifacts will be uploaded.
Dusk Tests - P8.2 - L11
Node.js 16 actions are deprecated. Please update the following actions to use Node.js 20: actions/checkout@v2, actions/upload-artifact@v3. For more information see: https://github.blog/changelog/2023-09-22-github-actions-transitioning-from-node-16-to-node-20/.
Dusk Tests - P8.2 - L11
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/checkout@v2. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
Dusk Tests - P8.2 - L11
No files were found with the provided path: tests/Browser/console. No artifacts will be uploaded.
Dusk Tests - P8.2 - L11
No files were found with the provided path: tests/Browser/screenshots. No artifacts will be uploaded.
Dusk Tests - P8.2 - L10.2
Node.js 16 actions are deprecated. Please update the following actions to use Node.js 20: actions/checkout@v2, nick-invision/retry@v2, actions/upload-artifact@v3. For more information see: https://github.blog/changelog/2023-09-22-github-actions-transitioning-from-node-16-to-node-20/.
Dusk Tests - P8.2 - L10.2
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/checkout@v2. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
Dusk Tests - P8.2 - L10.2
Attempt 1 failed. Reason: Child_process exited with error code 2
Dusk Tests - P8.2 - L10.2
Attempt 2 failed. Reason: Child_process exited with error code 2
Dusk Tests - P8.3 - L10.2
Node.js 16 actions are deprecated. Please update the following actions to use Node.js 20: actions/checkout@v2, nick-invision/retry@v2, actions/upload-artifact@v3. For more information see: https://github.blog/changelog/2023-09-22-github-actions-transitioning-from-node-16-to-node-20/.
Dusk Tests - P8.3 - L10.2
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/checkout@v2. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
Dusk Tests - P8.3 - L10.2
Attempt 1 failed. Reason: Child_process exited with error code 2
Dusk Tests - P8.3 - L10.2
Attempt 2 failed. Reason: Child_process exited with error code 2

Artifacts

Produced during runtime
Name Size
console Expired
3.29 KB
logs Expired
3.74 KB
screenshots Expired
95.2 KB