Closed Bug 804873 Opened 10 years ago Closed 10 years ago

Build with Python 2.7 on Windows build slaves

Categories

(Infrastructure & Operations Graveyard :: CIDuty, task, P2)

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: gps, Assigned: coop)

References

Details

(Whiteboard: [buildfaster:p2])

Attachments

(1 file)

I pushed a try build (https://tbpl.mozilla.org/?tree=Try&rev=7179f7d5713f) requiring Python 2.7 to build the tree and it appears that the Windows builders are all building with Python 2.6.

Please update the Windows builders to build the tree with Python 2.7.

I'm not sure what goes into updating the Windows builders. But, if you put a python2.7.exe or 2.7 version of python.exe on $PATH before whatever is there now, that should be all that is needed for configure to pick up the newer Python.
Adding coop as he might know what is needed.
IIRC correctly, the version of python that gets used (2.6) lives in D:\mozilla-build\python. We should be able to simply change the PATH.

Let me try some things in staging.
Assignee: nobody → coop
Status: NEW → ASSIGNED
Priority: -- → P2
Whiteboard: [buildfaster:p2]
(In reply to Chris Cooper [:coop] from comment #2)
> IIRC correctly

Sigh. I need coffee badly.
Python 2.7 is, in fact, installed on these slaves already, but the pywin32 extensions for it are not. This was causing builds to fail out early in the setup.

I've figured out a method to install the win32 extensions silently as Administrator, and am now running a build through staging to make sure the build itself is unaffected. 

Aside from the extensions install, I've only needed to move python27 to the front of our PATHs on Windows in the buildbot-configs so far.
Nothing in the build itself requires pywin32. Is this something in the automation?
(In reply to Ted Mielczarek [:ted.mielczarek] from comment #5)
> Nothing in the build itself requires pywin32. Is this something in the
> automation?

Yes, I believe the pre-build file removal/cleanup steps on Windows rely on those apis.
(In reply to Chris Cooper [:coop] from comment #4) 
> I've figured out a method to install the win32 extensions silently as
> Administrator, and am now running a build through staging to make sure the
> build itself is unaffected. 

I've deployed this to all the w64 builders. I'm now checking whether we need this for the w32 builders.

Should have the configs patch ready this afternoon.
(In reply to Chris Cooper [:coop] from comment #7) 
> I've deployed this to all the w64 builders. I'm now checking whether we need
> this for the w32 builders.

Deployed on the w32 slaves now too.

Working on the configs patch now.
I've done successful dep/nightly builds on win64 and l10n repacks on win32 using this patch.
Attachment #683741 - Flags: review?(armenzg)
Comment on attachment 683741 [details] [diff] [review]
Add python 2.7 ahead of the buildbotve version of python on win32 and win64

Review of attachment 683741 [details] [diff] [review]:
-----------------------------------------------------------------

Excellent!
Attachment #683741 - Flags: review?(armenzg) → review+
Comment on attachment 683741 [details] [diff] [review]
Add python 2.7 ahead of the buildbotve version of python on win32 and win64

https://hg.mozilla.org/build/buildbot-configs/rev/fc70444b37f7
Attachment #683741 - Flags: checked-in+
Depends on: 814523
Second times the charm. Here's a log from one of Ehsan's check-ins today that shows python 2.7 being used successfully to purge_builds at the start of a run:

https://tbpl.mozilla.org/php/getParsedLog.php?id=17309992&tree=Mozilla-Inbound&full=1
Status: ASSIGNED → RESOLVED
Closed: 10 years ago
Resolution: --- → FIXED
(In reply to Chris Cooper [:coop] from comment #13)
> Second times the charm. Here's a log from one of Ehsan's check-ins today
> that shows python 2.7 being used successfully to purge_builds at the start
> of a run:

And for the rest of the build process as well, natch. Is my releng bias showing?
Try is still on 2.6:

https://tbpl.mozilla.org/?tree=Try&rev=c5d14c3a9e17
Status: RESOLVED → REOPENED
Resolution: FIXED → ---
Here's a rebuild of Greg's failed try push that's working now:

https://tbpl.mozilla.org/?tree=Try&rev=c5d14c3a9e17&jobname=WINNT%205.2%20try%20build
Status: REOPENED → RESOLVED
Closed: 10 years ago10 years ago
Resolution: --- → FIXED
Blocks: 817345
Depends on: 827497
There was never a bug filed to have this rolled into the automated image, and the attempt to do that now is failing.  Bug 827497 is tracking that work.
Status: RESOLVED → REOPENED
Resolution: FIXED → ---
From what I can gather the story is this:

 * Python-2.7.3 + pywin32 was installed by hand on all w64 systems in this bug

 * That was not reflected in the MDT task sequence

 * As a result, systems built with the new MDT task sequence don't work, and we're iterating through trying to get them to work in bug 827497.  Hopefully learning something about how Python is used in the Build process while doing so!

So the only remaining action here is to close 827497.
(In reply to Dustin J. Mitchell [:dustin] from comment #18)
> From what I can gather the story is this:
> 
>  * Python-2.7.3 + pywin32 was installed by hand on all w64 systems in this
> bug
> 
>  * That was not reflected in the MDT task sequence

It was reflected in our reference platform docs, that aiui was the baseline for MDT task sequence for this

https://wiki.mozilla.org/ReferencePlatforms/Win64#Python_2.7.3
Depends on: 833838
Turns out we figured out enough of the details to get this installed.
Status: REOPENED → RESOLVED
Closed: 10 years ago10 years ago
Resolution: --- → FIXED
Product: mozilla.org → Release Engineering
Product: Release Engineering → Infrastructure & Operations
Product: Infrastructure & Operations → Infrastructure & Operations Graveyard
You need to log in before you can comment on or make changes to this bug.