Two Windows testers fail every job before building, with the sandbox unable to read the job's working directory #111
Labels
No labels
kind
bug
kind
chore
kind
docs
kind
feature
kind
performance
kind
question
priority
critical
priority
high
priority
low
risk
high
risk
low
risk
medium
status
blocked
status
confirmed
status
duplicate
status
invalid
status
needs-info
status
wontfix
ci: approved
No milestone
No project
No assignees
2 participants
Notifications
Due date
No due date set.
Dependencies
No dependencies set
Reference
MagicBeanDev/Beanstalk#111
Loadingβ¦
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
π€ Two Windows testers have failed every job they took from Longshot PRs for at least two days, in the main-base or PR-pack step. No metric comes back, so every Windows cell they take reports
error. Seen on agents nightly-172 through nightly-191.Tester 1: hidden, RTX 3050 Ti Laptop (Ryzen 7 5800H, Windows 10.0.26200).
dev_packs.py basestops atgit -C Z:\longshot diff --name-only HEAD, exit status 128:Its log also starts with
Failed to find real location of Z:\tools\python\python.exe. Reports on several authors' PRs:Tester 2:
akkusativ/agent-0a71fc, RTX 4070 Ti (Ryzen 9 5900X, Windows 10.0.26200). It builds main, then the PR pack fails:The last line comes from the unchecked
git merge-base --is-ancestorindev_packs.py, whose git also exited 128. So the "rebase it" advice is wrong: the tree is on the base. Reports:What both share:
Z:.Z:(or its parent folders), not just toZ:itself.Smokedribbs/agent-d43eb8passed on #1807 (rp_71fb8f9d9a11dabc). So it looks specific to how these two machines' work drive is set up.Related, but not the same:
Asked:
error?git merge-base --is-ancestorindev_packs.py, so a git failure isn't reported as "not built on the base".Possibly related, for context: