Closed Bug 1256676 Opened 8 years ago Closed 11 months ago

Webrtc testing needs some new python packages on the testers

Categories

(Release Engineering :: General, task)

task
Not set
normal

Tracking

(Not tracked)

RESOLVED WORKSFORME

People

(Reporter: bwc, Unassigned)

References

Details

Bug 1231981 is going to introduce some python dependencies on the testers, here are the import statements for the stuff that isn't part of python's standard library:

import ipaddr
import passlib.utils # for saslprep
from twisted.internet import reactor, protocol
from twisted.internet.task import LoopingCall
from twisted.internet.address import IPv4Address, IPv6Address
import txws
This should be in a releng/ateam component, and CC the relevant people.
Component: WebRTC: Networking → General Automation
Product: Core → Release Engineering
QA Contact: catlee
The copy of twisted that is already at http://puppetagain.pub.build.mozilla.org/data/python/packages/ is probably going to work fine, but ipaddr, passlib, and txws are still going to be necessary.
It looks like txws has a dependency that pypi doesn't know about:

six
Ah, we seem to have six already.
Who needs to be assigned to this?
Flags: needinfo?(catlee)
(In reply to Byron Campen [:bwc] from comment #5)
> Who needs to be assigned to this?

I'm handling this for catlee.

From IRC chat, I think we're done here... I was told to make sure we had `ipaddress` available on internal pypi, and then we also needed the following:

callek@Centaurus:~/tmp2$ for i in *.whl *.gz; do echo $i; done
passlib-1.6.5-py2.py3-none-any.whl
passlib-1.6.5.tar.gz
txWS-0.9.1.tar.gz

(well I wasn't told to do .tar.gz and .whl for passlib, but figured I might as well upload both).

If there are more packages to install, please reopen and n-i me, with their names and I'll get them up.

http://pypi.pub.build.mozilla.org/pub/
Status: NEW → RESOLVED
Closed: 8 years ago
Flags: needinfo?(catlee)
Resolution: --- → FIXED
It looks like the versions of twisted in our local pypi won't do the trick. 12.3.0 won't install on the windows testers (because that version of twisted has c code it needs to compile), and 10.2.0 doesn't work because it lacks IPv6 support. I see a couple of options:

1. Put a precompiled twisted wheel on our internal pypi.

2. Make sure the windows testers have the necessary software to install the copy of twisted we have.

If this is going to take a while, I can temporarily disable IPv6 in our ICE server, and see if that is enough to un-stick this. It may turn out that more stuff is missing though.
Status: RESOLVED → REOPENED
Flags: needinfo?(bugspam.Callek)
Resolution: FIXED → ---
Greg/Dustin, can you provide "us" advice on this bug. I'm not sure I'm particularly comfortable putting things up internally that are neither our own software creations nor on pypi.

However I'm also not certain how to proceed here (I know doing 'builds' of python stuff on windows is harder than it should be in our automation)
Flags: needinfo?(gps)
Flags: needinfo?(dustin)
Flags: needinfo?(bugspam.Callek)
also, "precompiled" for windows is a slippery thing, as it ends up being precompiled for a specific python version and, I think, for a specific path to that binary.

Tooltool might be a good choice for such things?
Flags: needinfo?(dustin)
We should aim to use Python wheels on Windows. These target a specific Python/Windows version, so there should be no binary compatibility problem. The Windows wheel at https://pypi.python.org/pypi/Twisted should "just work" (at least on 64 bit Python installs - not sure why they don't make a 32-bit wheel available).

We should avoid building Python 2.7 packages with C extensions on Windows in automation because this will require the VS2008 toolchain because Python 2.7 is built with VS2008. (https://www.microsoft.com/en-ca/download/details.aspx?id=44266 can be installed to provide this toolchain without the rest of Visual Studio 2008.)

The version of pip we have installed in automation may not be new enough to install wheels properly. We should upgrade to the latest version of pip throughout automation to ensure wheels work properly.
Flags: needinfo?(gps)
Component: General Automation → General

Presumably this happened at some point.

Status: REOPENED → RESOLVED
Closed: 8 years ago11 months ago
Resolution: --- → WORKSFORME
Type: defect → task
You need to log in before you can comment on or make changes to this bug.