Skip to content

Introduce effective_spec for runs and fleets #4443

Introduce effective_spec for runs and fleets

Introduce effective_spec for runs and fleets #4443

Triggered via pull request April 28, 2025 10:24
Status Success
Total duration 6m 55s
Artifacts 3

build.yml

on: pull_request
Matrix: python-test
Matrix: runner-compile
update-get-dstack
15s
update-get-dstack
generate-json-schema
23s
generate-json-schema
runner-upload
27s
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:400ac1123341b99c59337e38713c46b4b42a5051a713a99dc86be0843608d6a8
dstack-runner-linux-arm64 Expired
17.1 MB
sha256:d2d91178e246bd88ec5661589fcbfa15d6f87135ea4a31da72ca1531dec4920e
frontend-build Expired
14.3 MB
sha256:0b6883ac7d6092c7a6e7e3b5178e467e3e6896f142dd6c1b584b36a2b0522c2c