[users at bb.net] Unit Tests Failing after clean install

Wed Oct 28 15:14:02 UTC 2015

Ah, OK, I can replicate this now.  It appears that the issue appears with
mock-1.3.0, but not with mock-0.8.0.  0.8.12 was released a while ago,
presumably before mock-1.3.0.

You can fix this by installing pip-0.8.0:

  ./bin/pip install mock==0.8.0

but really it's nothing to worry about -- an error in the test suite
itself, rather than in the "real" code (which doesn't use Mock at all).

Thanks for bringing this up!

Dustin

On Wed, Oct 28, 2015 at 9:21 AM, Justin Fehr <Justin.Fehr at kinze.com> wrote:

> This is the pip freeze from the virtualenv that contains my master install,
>
>
>
> buildbot==0.8.12
>
> decorator==4.0.4
>
> funcsigs==0.4
>
> Jinja2==2.8
>
> MarkupSafe==0.23
>
> mock==1.3.0
>
> pbr==1.8.1
>
> python-dateutil==2.4.2
>
> six==1.10.0
>
> SQLAlchemy==0.7.10
>
> sqlalchemy-migrate==0.7.2
>
> Tempita==0.5.2
>
> Twisted==15.4.0
>
> wheel==0.24.0
>
> zope.interface==4.1.3
>
>
>
>
>
> Additionally, just to double check that I ran the tests correctly in the
> virtualenv, from my bb-master directory I ran:    ./bin/trial buildbot.test
>
>
>
> *From:* Pierre Tardy [mailto:tardyp at gmail.com]
> *Sent:* Tuesday, October 27, 2015 6:10 PM
> *To:* Justin Fehr; Bill Deegan
>
> *Cc:* Dustin J. Mitchell; users at buildbot.net
> *Subject:* Re: [users at bb.net] Unit Tests Failing after clean install
>
>
>
> Interesting... Can you send us the result of pip freeze?
>
>
>
> Le mar. 27 oct. 2015 22:43, Justin Fehr <Justin.Fehr at kinze.com> a écrit :
>
> I reinstalled everything into a virtualenv using the buildbot guide, and
> after running the tests received the same two errors as before. For
> reference I am running python 2.7.6 on Ubuntu 14.04.3 LTS
>
>
>
> *From:* Bill Deegan [mailto:bill at baddogconsulting.com]
> *Sent:* Tuesday, October 27, 2015 2:35 PM
> *To:* Pierre Tardy
> *Cc:* Justin Fehr; Dustin J. Mitchell; users at buildbot.net
>
>
> *Subject:* Re: [users at bb.net] Unit Tests Failing after clean install
>
>
>
> I'll second Pierre's recommendation.
>
> Plus. I'm always loath to mess with system installed packages via pip.
>
> Much cleaner to use a virtualenv.
>
> That also allows you to try new versions on the same system when they come
> out without displacing your running buildbot instance..
>
> -Bill
>
>
>
> On Tue, Oct 27, 2015 at 11:55 AM, Pierre Tardy <tardyp at gmail.com> wrote:
>
> The recommended method is to use virtualenv, so that you know you have a
> clean setup.
>
>
>
> Le mar. 27 oct. 2015 à 19:48, Justin Fehr <Justin.Fehr at kinze.com> a
> écrit :
>
> I used pip to install it. I believe that is the recommended method,
> correct?
>
>
>
> *KINZE *
> *Manufacturing, Inc. **Justin.Fehr at kinze.com <Justin.Fehr at kinze.com>*
> 319.668.1300
>
>
>
> *From:* Bill Deegan [mailto:bill at baddogconsulting.com]
> *Sent:* Tuesday, October 27, 2015 1:44 PM
> *To:* Justin Fehr
> *Cc:* Dustin J. Mitchell; users at buildbot.net
>
>
> *Subject:* Re: [users at bb.net] Unit Tests Failing after clean install
>
>
>
> Justin,
>
> Looks like you install buildbot in your system python.
>
> How did you install buildbot?
>
> (distro package, pip, other?)
>
> -Bill
>
>
>
> On Tue, Oct 27, 2015 at 11:36 AM, Justin Fehr <Justin.Fehr at kinze.com>
> wrote:
>
> After searching my machine I can only find one version of buildbot. Do you
> have any other suggestions? Thanks for the help
>
>
>
> J
>
>
>
> *From:* djmitche at gmail.com [mailto:djmitche at gmail.com] *On Behalf Of *Dustin
> J. Mitchell
> *Sent:* Tuesday, October 27, 2015 8:35 AM
> *To:* Justin Fehr
> *Cc:* users at buildbot.net
> *Subject:* Re: [users at bb.net] Unit Tests Failing after clean install
>
>
>
> Hi Justin --
>
> What version of Buildbot do you have installed?
>
> Most times, test failures like this are due to having multiple copies of
> Buildbot installed in such a way that Python is finding some modules from
> one version and some modules from another.  Did you, by chance, install
> Buildbot with your system package manager (dnf or apt-get), then install it
> systemwide with pip?
>
> Dustin
>
>
>
> On Mon, Oct 26, 2015 at 5:32 PM, Justin Fehr <Justin.Fehr at kinze.com>
> wrote:
>
> Hi all,
>
>
>
> I am setting up buildbot for the first time, after installing buildbot I
> ran the unit tests to confirm that everything is installed correctly. I
> received two errors and now am unsure of how to proceed. They are as
> follows:
>
>
>
>
> ===============================================================================
>
> [ERROR]
>
> Traceback (most recent call last):
>
>   File
> "/usr/local/lib/python2.7/dist-packages/buildbot/test/unit/test_process_buildstep.py",
> line 386, in test_updateSu
>
> mmary_running_empty_dict
>
>     step._step_status.setText.assert_not_called()
>
>   File "/usr/local/lib/python2.7/dist-packages/mock/mock.py", line 915, in
> assert_not_called
>
>     raise AssertionError(msg)
>
> exceptions.AssertionError: Expected 'setText' to not have been called.
> Called 1 times.
>
>
>
>
> buildbot.test.unit.test_process_buildstep.TestBuildStep.test_updateSummary_running_empty_dict
>
>
> ===============================================================================
>
> [ERROR]
>
> Traceback (most recent call last):
>
>   File
> "/usr/local/lib/python2.7/dist-packages/buildbot/test/unit/test_util.py",
> line 269, in test_broken_locale
>
>     config.error.assert_called()
>
>   File "/usr/local/lib/python2.7/dist-packages/mock/mock.py", line 721, in
> __getattr__
>
>     raise AttributeError(name)
>
> exceptions.AttributeError: assert_called
>
>
>
> buildbot.test.unit.test_util.FunctionalEnvironment.test_broken_locale
>
>
>
> Thanks,
>
>
>
> J
>
>
> ------------------------------
>
>
> Electronic Privacy Notice: This e-mail, and any attachments, contains
> information that is, or may be, covered by electronic communications
> privacy laws, and is confidential and proprietary in nature. If you are not
> the intended recipient, please be advised that retaining, using, copying,
> distributing, or otherwise disclosing this information is strictly
> prohibited. Instead, please reply to the sender that you have received this
> communication in error, and then immediately delete and/or destroy your
> copy. Thank you for your cooperation.
>
>
> _______________________________________________
> users mailing list
> users at buildbot.net
> https://lists.buildbot.net/mailman/listinfo/users
>
>
>
>
> _______________________________________________
> users mailing list
> users at buildbot.net
> https://lists.buildbot.net/mailman/listinfo/users
>
>
>
> _______________________________________________
> users mailing list
> users at buildbot.net
> https://lists.buildbot.net/mailman/listinfo/users
>
>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.buildbot.net/pipermail/users/attachments/20151028/45460773/attachment.html>