Closed Bug 1228068 Opened 6 years ago Closed 6 years ago

aws spot instances building Windows XP failing because of "/x86_amd64/cl.exe: No such file or directory"

Categories

(Infrastructure & Operations :: RelOps: General, task)

Product:
Infrastructure & Operations
Component:
RelOps: General
Type:
task
Priority:
Not set
Severity:
critical

Tracking

(Not tracked)

Status:
RESOLVED FIXED

People

(Reporter: aryx, Unassigned)

References

Details

We see many failing Windows XP build jobs, mozilla-inbound and fx-team are closed for that reason:

failed:
https://treeherder.mozilla.org/logviewer.html#?job_id=17832138&repo=mozilla-inbound#L11690 b-2008-spot-140
https://treeherder.mozilla.org/logviewer.html#?job_id=5907823&repo=fx-team#L6785 b-2008-spot-121
Issue seem to be "/x86_amd64/cl.exe: No such file or directory"

The successful clobber of the latter job doesn't have that issue:
http://archive.mozilla.org/pub/firefox/tinderbox-builds/fx-team-win32/1448456437/fx-team-win32-bm73-build1-build0.txt.gz
An easy way out of this is to disable sccache on windows builders. It was not enabled on in-house builders.
(In reply to Rob Thijssen (:grenade - GMT) from comment #1)
> https://bugzilla.mozilla.org/show_bug.cgi?id=1153480

It's probably not the same thing. That bug lacks log context, but I'm pretty sure sccache was not involved. OTOH, sccache *is* involved here.
... that said, sccache was enabled on try... it's surprising that it wasn't a problem there...
https://hg.mozilla.org/mozilla-central/rev/411ae8f9583d
Status: NEW → RESOLVED
Closed: 6 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.