Skip to content

Improved MySQL acceptance test resets #46482

Improved MySQL acceptance test resets

Improved MySQL acceptance test resets #46482

Triggered via pull request June 12, 2026 16:19
Status Failure
Total duration 5m 20s
Artifacts

ci.yml

on: pull_request
Build & Publish Artifacts
0s
Build & Publish Artifacts
Matrix: job_unit-tests
Matrix: job_acceptance-tests
Tinybird Tests
0s
Tinybird Tests
Build E2E Public App Assets
0s
Build E2E Public App Assets
Admin tests - Chrome
0s
Admin tests - Chrome
Matrix: App Playwright Acceptance Tests
Matrix: job_legacy-tests
Check app version bump
32s
Check app version bump
Check migration integrity
44s
Check migration integrity
i18n
1m 0s
i18n
Ghost-CLI tests
0s
Ghost-CLI tests
Trigger Pro CD
0s
Trigger Pro CD
Matrix: build_packages
Deploy Tinybird
0s
Deploy Tinybird
Build E2E Docker Image
0s
Build E2E Docker Image
Coverage
0s
Coverage
Publish Ghost to npm
0s
Publish Ghost to npm
Matrix: publish_packages
Matrix: job_e2e_tests
Create GitHub Release
Create GitHub Release
Merge Reports
Merge Reports
All required tests passed or skipped
3s
All required tests passed or skipped
Notify release failure
Notify release failure
Fit to window
Zoom out
Zoom in

Annotations

14 errors and 5 warnings
[unit-isolated] test/unit/server/adapters/scheduling/scheduling-default.test.js > Scheduling Default Adapter > success > pingUrl > pingUrl (GET, and detect publish in the past): ghost/core/test/unit/server/adapters/scheduling/scheduling-default.test.js#L304
Error: Test timed out in 5000ms. If this is a long-running test, pass a timeout value as the last argument or configure it globally with "testTimeout". ❯ test/unit/server/adapters/scheduling/scheduling-default.test.js:304:13
[unit-isolated] test/unit/server/adapters/scheduling/scheduling-default.test.js > Scheduling Default Adapter > success > pingUrl > pingUrl (PUT, and detect publish in the past): ghost/core/test/unit/server/adapters/scheduling/scheduling-default.test.js#L287
Error: Test timed out in 5000ms. If this is a long-running test, pass a timeout value as the last argument or configure it globally with "testTimeout". ❯ test/unit/server/adapters/scheduling/scheduling-default.test.js:287:13
[unit-isolated] test/unit/server/adapters/scheduling/scheduling-default.test.js > Scheduling Default Adapter > success > pingUrl > pingUrl (PUT, and detect publish in the past): ghost/core/test/unit/server/adapters/scheduling/scheduling-default.test.js#L287
Error: Test timed out in 5000ms. If this is a long-running test, pass a timeout value as the last argument or configure it globally with "testTimeout". ❯ test/unit/server/adapters/scheduling/scheduling-default.test.js:287:13
[unit-isolated] test/unit/server/adapters/scheduling/scheduling-default.test.js > Scheduling Default Adapter > success > pingUrl > pingUrl (PUT, and detect publish in the past): ghost/core/test/unit/server/adapters/scheduling/scheduling-default.test.js#L287
Error: Test timed out in 5000ms. If this is a long-running test, pass a timeout value as the last argument or configure it globally with "testTimeout". ❯ test/unit/server/adapters/scheduling/scheduling-default.test.js:287:13
[unit-isolated] test/unit/server/adapters/scheduling/scheduling-default.test.js > Scheduling Default Adapter > success > pingUrl > pingUrl (GET): ghost/core/test/unit/server/adapters/scheduling/scheduling-default.test.js#L270
Error: Test timed out in 5000ms. If this is a long-running test, pass a timeout value as the last argument or configure it globally with "testTimeout". ❯ test/unit/server/adapters/scheduling/scheduling-default.test.js:270:13
[unit-isolated] test/unit/server/adapters/scheduling/scheduling-default.test.js > Scheduling Default Adapter > success > pingUrl > pingUrl (GET): ghost/core/test/unit/server/adapters/scheduling/scheduling-default.test.js#L270
Error: Test timed out in 5000ms. If this is a long-running test, pass a timeout value as the last argument or configure it globally with "testTimeout". ❯ test/unit/server/adapters/scheduling/scheduling-default.test.js:270:13
[unit-isolated] test/unit/server/adapters/scheduling/scheduling-default.test.js > Scheduling Default Adapter > success > pingUrl > pingUrl (GET): ghost/core/test/unit/server/adapters/scheduling/scheduling-default.test.js#L270
Error: Test timed out in 5000ms. If this is a long-running test, pass a timeout value as the last argument or configure it globally with "testTimeout". ❯ test/unit/server/adapters/scheduling/scheduling-default.test.js:270:13
[unit-isolated] test/unit/server/adapters/scheduling/scheduling-default.test.js > Scheduling Default Adapter > success > pingUrl > pingUrl (PUT): ghost/core/test/unit/server/adapters/scheduling/scheduling-default.test.js#L253
Error: Test timed out in 5000ms. If this is a long-running test, pass a timeout value as the last argument or configure it globally with "testTimeout". ❯ test/unit/server/adapters/scheduling/scheduling-default.test.js:253:13
[unit-isolated] test/unit/server/adapters/scheduling/scheduling-default.test.js > Scheduling Default Adapter > success > pingUrl > pingUrl (PUT): ghost/core/test/unit/server/adapters/scheduling/scheduling-default.test.js#L253
Error: Test timed out in 5000ms. If this is a long-running test, pass a timeout value as the last argument or configure it globally with "testTimeout". ❯ test/unit/server/adapters/scheduling/scheduling-default.test.js:253:13
[unit-isolated] test/unit/server/adapters/scheduling/scheduling-default.test.js > Scheduling Default Adapter > success > pingUrl > pingUrl (PUT): ghost/core/test/unit/server/adapters/scheduling/scheduling-default.test.js#L253
Error: Test timed out in 5000ms. If this is a long-running test, pass a timeout value as the last argument or configure it globally with "testTimeout". ❯ test/unit/server/adapters/scheduling/scheduling-default.test.js:253:13
Acceptance tests (Node 22.18.0, sqlite3)
Process completed with exit code 1.
Acceptance tests (Node 22.18.0, mysql8)
The strategy configuration was canceled because "job_acceptance-tests._22_18_0_sqlite3_testing" failed
Acceptance tests (Node 22.18.0, mysql8)
The operation was canceled.
All required tests passed or skipped
Process completed with exit code 1.
Setup
'base' input parameter is ignored when action is triggered by pull request event
Unit tests (Node 22.18.0)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: szenius/set-timezone@1f9716b0f7120e344f0c62bb7b1ee98819aefd42. 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/
Unit tests (Node 22.18.0)
Unit tests attempt 1 failed — retrying
Acceptance tests (Node 22.18.0, sqlite3)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: szenius/set-timezone@1f9716b0f7120e344f0c62bb7b1ee98819aefd42. 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/
Acceptance tests (Node 22.18.0, mysql8)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: szenius/set-timezone@1f9716b0f7120e344f0c62bb7b1ee98819aefd42. 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/