Skip to content

Optimize join tables from different databases #470

Optimize join tables from different databases

Optimize join tables from different databases #470

Triggered via pull request November 1, 2024 11:35
@ea-rusea-rus
synchronize #412
optimize-join
Status Failure
Total duration 52s
Artifacts

test.yml

on: pull_request
Matrix: test
coverage
0s
coverage
Fit to window
Zoom out
Zoom in

Annotations

11 errors and 2 warnings
test (ubuntu-latest, 3.9)
Process completed with exit code 1.
test (ubuntu-latest, 3.10)
The job was canceled because "ubuntu-latest_3_9" failed.
test (ubuntu-latest, 3.10)
Process completed with exit code 1.
test (ubuntu-latest, 3.8)
The job was canceled because "ubuntu-latest_3_9" failed.
test (ubuntu-latest, 3.8)
Process completed with exit code 1.
test (windows-latest, 3.8)
The job was canceled because "ubuntu-latest_3_9" failed.
test (windows-latest, 3.8)
The operation was canceled.
test (windows-latest, 3.9)
The job was canceled because "ubuntu-latest_3_9" failed.
test (windows-latest, 3.9)
The operation was canceled.
test (windows-latest, 3.10)
The job was canceled because "ubuntu-latest_3_9" failed.
test (windows-latest, 3.10)
The operation was canceled.
test (ubuntu-latest, 3.9)
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/checkout@v2, actions/setup-python@v2. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
test (ubuntu-latest, 3.9)
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v2, actions/setup-python@v2. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/