Skip to content
Runnable native lifecycle

fix: fail environment import when its readiness validation refuses the workspace (#760) #236

Sign in to view logs

fix: fail environment import when its readiness validation refuses the workspace (#760)

fix: fail environment import when its readiness validation refuses the workspace (#760) #236

Triggered via pull request September 21, 2026 21:50
@antoinetoussaint-byteantoinetoussaint-byte
opened #769
issue-760-fix-environment-import-exits-0-when-its-own
Status Failure
Total duration 2m 27s
Artifacts 1

runnable-native.yml

on: pull_request
native
1m 55s
native
Fit to window
Zoom out
Zoom in

Annotations

1 error, 1 warning, and 1 notice
native
Process completed with exit code 1.
native
No file matched to [/home/runner/work/cli/cli/**/*requirements*.txt,/home/runner/work/cli/cli/**/*requirements*.in,/home/runner/work/cli/cli/**/*constraints*.txt,/home/runner/work/cli/cli/**/*constraints*.in,/home/runner/work/cli/cli/**/pyproject.toml,/home/runner/work/cli/cli/**/uv.lock,/home/runner/work/cli/cli/**/*.py.lock]. The cache will never get invalidated. Make sure you have checked out the target repository and configured the cache-dependency-glob input correctly.
native
"The ubuntu-latest label will migrate to Ubuntu 26 beginning October 19, 2026. For more information, see https://github.com/actions/runner-images/issues/14748"

Artifacts

Produced during runtime
Name Size Digest
runnable-native
1.91 KB
sha256:d0e216aae2188f649772e2d507b104906946ca60580666b9d4aa68e073b83d0c