Skip to content

[WIP] Why the docker build for CI takes so long? #5036

[WIP] Why the docker build for CI takes so long?

[WIP] Why the docker build for CI takes so long? #5036

Triggered via pull request August 30, 2024 14:57
Status Failure
Total duration 47m 33s
Artifacts 12

ci.yml

on: pull_request
Create docker debug image
16m 29s
Create docker debug image
Matrix: build-and-test
Matrix: Run SDK-Go integration tests / sdk-test-suite
Matrix: Run SDK-Java integration tests with NeoInvocationStatus / sdk-test-suite
Matrix: Run SDK-Java integration tests / sdk-test-suite
Matrix: Run SDK-Python integration tests / sdk-test-suite
Matrix: Run SDK-Rust integration tests / sdk-test-suite
Matrix: Run SDK-Typescript integration tests / sdk-test-suite
Fit to window
Zoom out
Zoom in

Annotations

1 error and 1 warning
Run e2e tests / build
The job running on runner GitHub Actions 4 has exceeded the maximum execution time of 30 minutes.
Run SDK-Go integration tests / Features integration test (sdk-test-suite version 1.5)
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/setup-go@v4. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/

Artifacts

Produced during runtime
Name Size
container-logs
252 MB
restate.tar Expired
315 MB
restatedev~restate~MJGPDT.dockerbuild
61.7 KB
restatedev~restate~PYYH46.dockerbuild
40.2 KB
restatedev~restate~R8E08I.dockerbuild
42.5 KB
restatedev~restate~VHC2AM.dockerbuild
203 KB
sdk-go-integration-test-report
4.25 MB
sdk-java-integration-test-report
3.23 MB
sdk-java-neo-invocation-status-integration-test-report
3.32 MB
sdk-python-integration-test-report
2.66 MB
sdk-rust-integration-test-report
3.69 MB
sdk-typescript-integration-test-report
2.83 MB