Skip to content
Build

Fix client backward compatibility when reapplying runs (#2558) #4427

Sign in to view logs

Fix client backward compatibility when reapplying runs (#2558)

Fix client backward compatibility when reapplying runs (#2558) #4427

Triggered via push April 24, 2025 06:38
@r4victorr4victor
pushed d9c8312
master
Status Success
Total duration 3m 56s
Artifacts 2

build.yml

on: push
python-lint
17s
python-lint
frontend-build
7s
frontend-build
runner-test
54s
runner-test
gateway-build
11s
gateway-build
docs-build
1m 10s
docs-build
Matrix: python-test
Matrix: runner-compile
update-get-dstack
9s
update-get-dstack
generate-json-schema
19s
generate-json-schema
runner-upload
21s
runner-upload
Fit to window
Zoom out
Zoom in

Annotations

4 warnings
runner-upload
Empty workdir detected. This may cause unexpected behavior. You can enable ignore-empty-workdir to mute this warning.
runner-upload
No file matched to [**/uv.lock,**/requirements*.txt]. The cache will never get invalidated. Make sure you have checked out the target repository and configured the cache-dependency-glob input correctly.
update-get-dstack
Empty workdir detected. This may cause unexpected behavior. You can enable ignore-empty-workdir to mute this warning.
update-get-dstack
No file matched to [**/uv.lock,**/requirements*.txt]. The cache will never get invalidated. Make sure you have checked out the target repository and configured the cache-dependency-glob input correctly.

Artifacts

Produced during runtime
Name Size Digest
dstack-runner-linux-amd64 Expired
18.3 MB
sha256:7ca1273841ccba13b590292683175e9f9f631f7efccc43923b1ab482726cbd89
frontend-build Expired
14.3 MB
sha256:63e49c23ae59e596d23e8eb041c4fe68af46b7157bab0560ea87bbd26ec8d68a