Glance

tox and nosetests not showing consistent results

Bug #1010579 reported by Duncan McGreggor
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Glance
Won't Fix
Undecided
Unassigned

Bug Description

When checking glance for a bug I found in a running instance (see bug #1010560), I ran tox against the unit tests and was surprised to find that all the unit tests passed.

I then ran the same unit tests using nosetests, and the unit test that I had expected to fail, did.

This might be as simple as tox setting environments up that nosetests doesn't use. Or it could be more insidious. Regardless, probably something that should be looked into ;-)

See original description
Revision history for this message
Brian Waldon (bcwaldon) wrote :

My googling skills are failing me...what is 'nox'?

Revision history for this message
Duncan McGreggor (oubiwann) wrote :

Nox, well... that's a symptom of a chronic case of cryptodyslexia.

I'm updating the ticket to read "tox." I think it will sound much better that way ;-)

description: updated
summary: - nox and nosetests not showing consistent results
+ tox and nosetests not showing consistent results
Revision history for this message
Brian Waldon (bcwaldon) wrote :

Ah, that makes much more sense. So I haven't have any trouble with discrepancies between the two...perhaps your tox environment has different dependencies installed than whatever is used with nosetests?

Revision history for this message
Duncan McGreggor (oubiwann) wrote : Re: [Bug 1010579] Re: tox and nosetests not showing consistent results

On Fri, Jun 8, 2012 at 6:44 PM, Brian Waldon <email address hidden> wrote:
> Ah, that makes much more sense. So I haven't have any trouble with
> discrepancies between the two...perhaps your tox environment has
> different dependencies installed than whatever is used with nosetests?

Could be. But my brand-new devstack Ubuntu install fails to spawn new
instances due to this issue (it specifically raises exceptions at that
line of code).

When I set the request.environ so that it's not "None," the instances
get spawned correctly...

d

Revision history for this message
Brian Waldon (bcwaldon) wrote :

As the other bug you filed has been fixed https://bugs.launchpad.net/glance/+bug/1010560, are you confident this was just an issue of different webob dependencies in two different environments?

Changed in glance:
status: New → Incomplete
Revision history for this message
Duncan McGreggor (oubiwann) wrote :

On Wed, Jun 20, 2012 at 5:36 PM, Brian Waldon
<email address hidden> wrote:
> As the other bug you filed has been fixed
> https://bugs.launchpad.net/glance/+bug/1010560, are you confident this
> was just an issue of different webob dependencies in two different
> environments?

I'm not actually sure why nosetests and nox were getting different
results :-/ I didn't have time to dig into the "why" of it, only
enough time to report it :-(

d

Revision history for this message
Brian Waldon (bcwaldon) wrote :

Is this currently reproducible?

Revision history for this message
Duncan McGreggor (oubiwann) wrote :

On Tue, Jul 3, 2012 at 8:15 PM, Brian Waldon <email address hidden> wrote:
> Is this currently reproducible?

Nah. The only issue I was running into with it, I submitted a patch
for, and is now in master.

This bug was opened more as a "heads up, not all unit tests are
getting run in the same environment, it seems" ... so that anyone who
knew all the gory details on the testing infrastructure might take a
peek and be able to fix any underlying problems.

Brian Waldon (bcwaldon)
Changed in glance:
status: Incomplete → Won't Fix
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.