Using 'pip freeze' to print versions can help, as can either using requirements.txt or 'pip install -U' to do the installs.
On Mon, May 5, 2014 at 2:46 PM, Glyph <gl...@twistedmatrix.com> wrote: > > On May 5, 2014, at 4:43 AM, exar...@twistedmatrix.com wrote: > >> On 02:17 am, gl...@twistedmatrix.com wrote: >>> cyli was working on <https://twistedmatrix.com/trac/ticket/7144> and >>> encountered this peculiar failure on her branch (and not on trunk): >>> <https://buildbot.twistedmatrix.com/builders/python-3.3-tests/builds/2212/steps/shell/logs/stdio>. >>> >>> The interesting bit of the failure is that in one case, the ImportError's >>> message is "import of 'service_identity' halted; None in sys.modules" and >>> on trunk it's apparently 'No module named service_identity'. >>> >>> The branch in question changes conch, which isn't even tested on python 3. >>> >>> So... anyone have an idea what's going on? >> >> Here's the "versions" report from a build on that builder which recently >> succeeded: >> >> http://buildbot.twistedmatrix.com/builders/python-3.3-tests/builds/2210/steps >> /report-module-versions/logs/versions >> >> And here's the "versions" report from a build of that branch on that builder: >> >> http://buildbot.twistedmatrix.com/builders/python-3.3-tests/builds/2212/steps >> /report-module-versions/logs/versions >> >> Notice that the state of a somewhat relevant dependency is different between >> the two builds. Backing up, look at which build slave did each of those >> builds: >> >> http://buildbot.twistedmatrix.com/builders/python-3.3-tests/builds/2210 >> http://buildbot.twistedmatrix.com/builders/python-3.3-tests/builds/2212 >> >> So I suppose the test only passes by accident on trunk because it happened >> to be run on one slave with one configuration rather than the other slave >> with the other configuration... >> >> Considering we seem to have no mechanism whatsoever for ensuring the >> configuration of two different slaves for a particular builder is the same, >> I wonder if we should reconsider using multiple slaves for individual >> builders. > > Actually, one of the areas I was hoping that we could focus on for 14.1 would > be to upgrade our packaging infrastructure and have our builders acquire > dependencies automatically via 'pip install' or similar. > > See for example <https://twistedmatrix.com/trac/ticket/3696>. > > It's interesting to me that I've had issues with the divergent dependencies > on this exact builder twice, and both times re-building trunk multiple times > has happened to always hit the "good" builder, making it look like the branch > is somehow at fault. What's up with that? Just luck of the draw > > -glyph > > > _______________________________________________ > Twisted-Python mailing list > Twisted-Python@twistedmatrix.com > http://twistedmatrix.com/cgi-bin/mailman/listinfo/twisted-python _______________________________________________ Twisted-Python mailing list Twisted-Python@twistedmatrix.com http://twistedmatrix.com/cgi-bin/mailman/listinfo/twisted-python
