Skip to content

feat(storage): enable parallel writes by using per-repo locking #3541

feat(storage): enable parallel writes by using per-repo locking

feat(storage): enable parallel writes by using per-repo locking #3541

Triggered via pull request February 15, 2025 15:13
Status Failure
Total duration 6h 1m 30s
Artifacts 4

gc-stress-test.yaml

on: pull_request
GC(with referrers) on filesystem with short interval
6h 0m
GC(with referrers) on filesystem with short interval
GC(without referrers) on filesystem with short interval
6h 0m
GC(without referrers) on filesystem with short interval
GC(with referrers) on S3(minio) with short interval
5m 5s
GC(with referrers) on S3(minio) with short interval
GC(without referrers) on S3(minio) with short interval
4m 41s
GC(without referrers) on S3(minio) with short interval
Fit to window
Zoom out
Zoom in

Annotations

8 errors
GC(with referrers) on S3(minio) with short interval
Process completed with exit code 1.
GC(with referrers) on S3(minio) with short interval
Process completed with exit code 1.
GC(without referrers) on S3(minio) with short interval
Process completed with exit code 1.
GC(without referrers) on S3(minio) with short interval
Process completed with exit code 1.
GC(with referrers) on filesystem with short interval
The job running on runner ubuntu-latest-8-cores_559e49d9ba9a has exceeded the maximum execution time of 360 minutes.
GC(with referrers) on filesystem with short interval
The operation was canceled.
GC(without referrers) on filesystem with short interval
The job running on runner ubuntu-latest-8-cores_6d4a70752a1f has exceeded the maximum execution time of 360 minutes.
GC(without referrers) on filesystem with short interval
The operation was canceled.

Artifacts

Produced during runtime
Name Size
gc-bench-local
68.3 KB
gc-bench-s3
33.3 KB
gc-referrers-bench-local
71 KB
gc-referrers-bench-s3
31.2 KB