[Buildbot-devel] testing a not-yet-installed version of Buildbot (was: test regression...)

Charles Lepple clepple at gmail.com
Sat Apr 18 01:17:08 UTC 2009

On Tue, Mar 3, 2009 at 9:46 AM, Charles Lepple <clepple at gmail.com> wrote:
> On Mar 3, 2009, at 5:54 AM, Axel Hecht wrote:
>> Hrm. I suspect my test_limitlogs.py test, can you try to rename that locally
>> to .bak and rerun? That suspection comes from run-away process happily
>> mixing up the trial reports in my experience.
> I will try that tonight (after I switch back to Python 2.5)

(Guess that part didn't happen. If it's only one specific combination
of Twisted and Python, I'm not so worried.)

>> As you can see in
>> http://github.com/djmitche/buildbot/blob/518520af5676b295f403e634237d0e0902fe40e2/buildbot/test/test_limitlogs.py#LC54,
>> I'm actually calling out to 'buildbot create-master', which needs to support
>> the options. Which would mean that the PYTHONPATH trick isn't working.
> Hmm, would it work better with PYTHONPATH=$PWD? We really should have some
> way of testing the to-be-installed version separate from the currently
> installed version.

This question still stands, though - is there any way we could move
towards making sure that the tests try to use the not-yet-installed
tree first, with PATH and PYTHONPATH additions? Otherwise, it seems
like this could potentially mask a bug until after a new release has
been installed.

- Charles Lepple

More information about the devel mailing list