Skip to content

adding ShouldStartMySQLAfterRestore #3116

adding ShouldStartMySQLAfterRestore

adding ShouldStartMySQLAfterRestore #3116

Triggered via push October 25, 2024 09:11
Status Success
Total duration 1h 6m 12s
Billable time 45m
Artifacts
Get Previous Release - Query Serving (Schema)
34s
Get Previous Release - Query Serving (Schema)
Run Upgrade Downgrade Test - Query Serving (Schema)
44m 11s
Run Upgrade Downgrade Test - Query Serving (Schema)
Fit to window
Zoom out
Zoom in

Annotations

4 warnings
Get Previous Release - Query Serving (Schema)
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
Run Upgrade Downgrade Test - Query Serving (Schema)
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v3, actions/setup-go@v3, actions/setup-python@v4, nick-fields/retry@v2. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
Run Upgrade Downgrade Test - Query Serving (Schema)
Attempt 1 failed. Reason: Child_process exited with error code 1
Run Upgrade Downgrade Test - Query Serving (Schema)
The `python-version` input is not set. The version of Python currently in `PATH` will be used.