Closed Bug 860503 Opened 7 years ago Closed 7 years ago

Somehow make it possible to get a clobbered Windows PGO build on mozilla-inbound

Categories

(Release Engineering :: General, defect, blocker)

x86
Windows Server 2003
defect
Not set
blocker

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: philor, Assigned: kmoir)

Details

(Whiteboard: [buildduty])

We have bug 860426 on the long-path issues that we certainly have with .deleteme directories, and we have bug 859426 on investigating all the problems we have (since apparently build.deleteme had long-path issues but build.a didn't, and we have other failures with just build/), but this bug is about a single thing:

https://tbpl.mozilla.org/?tree=Mozilla-Inbound&rev=78e13e815d62 needs to run a clobbered Windows PGO build, to tell us whether or not we need to back out a patch from a few pushes before that, but after 12 tries we haven't gotten a single build which has gotten past failures trying to clobber other directories before they even got around to inbound pgo.

Because we can't merge inbound if we can't build Win PGO, and being able to merge it is its reason for being, even after we clean up any other bustage which currently has it closed we can't reopen it, so, blocker.
trying to clobber some slaves manually now
I cleaned up w64-ix-slave[03-110] with 

mv e:\builds\moz2_slave\m-in-w32-pgo-00000000000000000 e:\builds\moz2_slave\k
rmdir /S /Q e:\builds\moz2_slave\k
mv e:\builds\moz2_slave\m-in-w32-d-0000000000000000000 e:\builds\moz2_slave\k
rmdir /S /Q e:\builds\moz2_slave\k

hope this helps
Fantastic, thank you!
And we're unblocked, just waiting for another PGO to confirm we got the right thing backed out.
Status: NEW → RESOLVED
Closed: 7 years ago
Resolution: --- → FIXED
Assignee: nobody → kmoir
Whiteboard: [buildduty]
Product: mozilla.org → Release Engineering
Component: General Automation → General
You need to log in before you can comment on or make changes to this bug.