Skip to content
CI/CD

fix: access built-in system Python instead of using venv for runtime #92

Sign in to view logs

fix: access built-in system Python instead of using venv for runtime

fix: access built-in system Python instead of using venv for runtime #92

Triggered via pull request September 25, 2025 20:46
@deanqdeanq
synchronize #30
deanq/ae-1165-bug-pytorchs-not-found
Status Success
Total duration 5m 8s
Artifacts 2

ci.yml

on: pull_request
Matrix: test
lint
15s
lint
Matrix: local-execution-test
release
0s
release
docker-pr
3m 6s
docker-pr
docker-prod-gpu
0s
docker-prod-gpu
docker-prod-cpu
0s
docker-prod-cpu
docker-main-gpu
0s
docker-main-gpu
docker-main-cpu
0s
docker-main-cpu
Fit to window
Zoom out
Zoom in

Annotations

16 warnings
lint
Failed to save: <h2>Our services aren't available right now</h2><p>We're working to restore all services as soon as possible. Please check back soon.</p>0J6rVaAAAAADHx+DeaINHSaWtyLH8pQ9DUEFPRURHRTA1MTgARWRnZQ==
lint
Failed to restore: Cache service responded with 400
test (3.11)
Failed to save: <h2>Our services aren't available right now</h2><p>We're working to restore all services as soon as possible. Please check back soon.</p>0NarVaAAAAADtj3DKaTIbT4W5pMWPrcWeREVOMzAxMDAwMTA2MDQ5AEVkZ2U=
test (3.11)
Failed to restore: Cache service responded with 400
test (3.9)
Failed to save: <h2>Our services aren't available right now</h2><p>We're working to restore all services as soon as possible. Please check back soon.</p>0NKrVaAAAAAA1XBcZPVOKTI6bsEEQAJCdQlkzRURHRTAxMjEARWRnZQ==
test (3.9)
Failed to restore: Cache service responded with 400
test (3.10)
Failed to save: <h2>Our services aren't available right now</h2><p>We're working to restore all services as soon as possible. Please check back soon.</p>0NqrVaAAAAAArUtscXOMlSI6PlC+1WAayUEhYMzFFREdFMDYxMwBFZGdl
test (3.10)
Failed to restore: Cache service responded with 400
test (3.13)
Failed to save: <h2>Our services aren't available right now</h2><p>We're working to restore all services as soon as possible. Please check back soon.</p>0NarVaAAAAACgYWWjAw3LSYMkNmS0oNDrQlkzRURHRTAxMTYARWRnZQ==
test (3.13)
Failed to restore: Cache service responded with 400
test (3.12)
Failed to save: <h2>Our services aren't available right now</h2><p>We're working to restore all services as soon as possible. Please check back soon.</p>0OarVaAAAAADI9SZ+NiUARqFGBfTH+T75UEFPRURHRTA2MTcARWRnZQ==
test (3.12)
Failed to restore: Cache service responded with 400
local-execution-test (cpu)
Failed to save: <h2>Our services aren't available right now</h2><p>We're working to restore all services as soon as possible. Please check back soon.</p>0iqrVaAAAAAC4qM2qdmhlRrCvhHf1HN0bQ0hJMzBFREdFMDMwOABFZGdl
local-execution-test (cpu)
Failed to restore: Cache service responded with 400
docker-pr
Failed to save: <h2>Our services aren't available right now</h2><p>We're working to restore all services as soon as possible. Please check back soon.</p>0SavVaAAAAAAHDo3ktyR5QprkI+TVspZEUEFPRURHRTA2MTUARWRnZQ==
docker-pr
Failed to restore: Cache service responded with 400

Artifacts

Produced during runtime
Name Size Digest
runpod-workers~worker-tetra~UGYK80.dockerbuild Expired
24.5 KB
sha256:1a069e228a204ad3b4d4537a8d0c78ae11265514fde7a73e06332efda427b62e
runpod-workers~worker-tetra~ZNEG8U.dockerbuild Expired
24.9 KB
sha256:713602650824e6835c8fc9907a99ed15a0db37a1868164a17eab3038c70ac941