Skip to content

[CP-SAT] internal protocol improvements; bug fixes #1456

[CP-SAT] internal protocol improvements; bug fixes

[CP-SAT] internal protocol improvements; bug fixes #1456

Triggered via push September 4, 2024 06:35
Status Failure
Total duration 5m 10s
Artifacts
Matrix: native
Fit to window
Zoom out
Zoom in

Annotations

5 errors and 7 warnings
windows-2022 • Bazel • Python-3.10
A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond. (api.github.com:443)
windows-2022 • Bazel • Python-3.11
Process completed with exit code 1.
windows-2022 • Bazel • Python-3.11
unable to access 'https://github.com/google/or-tools/': Failed to connect to github.com port 443 after 21133 ms: Could not connect to server
windows-2022 • Bazel • Python-3.9
Process completed with exit code 1.
windows-2022 • Bazel • Python-3.12
Process completed with exit code 1.
windows-2022 • Bazel • Python-3.10
Failed to download action 'https://api.github.com/repos/actions/setup-java/zipball/0ab4596768b603586c0de567f2430c30f5b0d2b0'. Error: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond. (api.github.com:443)
windows-2022 • Bazel • Python-3.10
Back off 17.486 seconds before retry.
windows-2022 • Bazel • Python-3.10
Failed to download action 'https://api.github.com/repos/actions/setup-java/zipball/0ab4596768b603586c0de567f2430c30f5b0d2b0'. Error: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond. (api.github.com:443)
windows-2022 • Bazel • Python-3.10
Back off 24.401 seconds before retry.
windows-2022 • Bazel • Python-3.11
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/setup-java@v3, actions/setup-python@v4. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
windows-2022 • Bazel • Python-3.9
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/setup-java@v3, actions/setup-python@v4. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
windows-2022 • Bazel • Python-3.12
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/setup-java@v3, actions/setup-python@v4. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/