bug failure breaks our subunit output

Bug #1038250 reported by Gary Poster
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Launchpad itself
Expired
High
Unassigned

Bug Description

As found in http://ubuntuone.com/1J4THLUkQKfWMlpqvQgDmm , we had a test failure that broke our subunit output somehow. subunit was unable to recognize any tests from the stream after the failing test lp.bugs.browser.tests.test_bugtask.TestBugTaskView.test_rendered_query_counts_constant_with_team_memberships (http://pastebin.ubuntu.com/1153299/) . I don't yet clearly see what is broken in that subunit output, but whatever it is should be addressed. If we can also make subunit more robust, that's a bonus, but that should be a separate task/bug.

Brad Crittenden (bac)
Changed in launchpad:
assignee: nobody → Brad Crittenden (bac)
status: Triaged → In Progress
Revision history for this message
Robert Collins (lifeless) wrote :

test: lp.bugs.browser.tests.test_bugtask.TestBugTaskView.test_rendered_query_counts_constant_with_team_memberships
time: 2012-08-16 19:25:00.028197Z
tags: -zope:layer:lp.testing.layers.LaunchpadScriptLayer zope:layer:lp.testing.layers.BaseLayer -zope:layer:lp.codehosting.codeimport.tests.test_worker.ForeignBranchPluginLayer zope:layer:lp.testing.layers.LaunchpadFunctionalLayer zope:layer:lp.testing.layers.DatabaseLayer zope:layer:lp.testing.layers.RabbitMQLayer -zope:layer:lp.testing.layers.ZopelessLayer zope:layer:lp.testing.layers.LibrarianLayer -zope:layer:lp.codehosting.tests.test_acceptance.SSHServerLayer -zope:layer:lp.testing.layers.ZopelessAppServerLayer zope:layer:lp.testing.layers.MemcachedLayer zope:layer:lp.testing.layers.FunctionalLayer -zope:layer:lp.testing.layers.LaunchpadZopelessLayer zope:layer:lp.testing.layers.LaunchpadLayer
tags: worker-13
failure: lp.bugs.browser.tests.test_bugtask.TestBugTaskView.test_rendered_query_counts_constant_with_team_memberships [ multipart

Goes
test: A
time:
tags:
tags:
failure: B

That A and B need to match - subunit thinks its still waiting on an outcome for A. I see no further references to A in the stream.

Revision history for this message
Benji York (benji) wrote :

Robert Collins (lifeless) wrote:
> test: lp.bugs.browser.tests.test_bugtask.TestBugTaskView.test_rendered_query_counts_constant_with_team_memberships
> [...]
> failure: lp.bugs.browser.tests.test_bugtask.TestBugTaskView.test_rendered_query_counts_constant_with_team_memberships [ multipart
>
> Goes
> test: A
> time:
> tags:
> tags:
> failure: B

I don't follow. Both the "test:" and "failure:" lines reference
"lp.bugs.browser.tests.test_bugtask.TestBugTaskView.test_rendered_query_counts_constant_with_team_memberships".

Revision history for this message
Brad Crittenden (bac) wrote :

We have been unable to reproduce the problem using subunit filtering of the problem file. Marking the bug as incomplete.

Changed in launchpad:
status: In Progress → Incomplete
assignee: Brad Crittenden (bac) → nobody
Revision history for this message
Robert Collins (lifeless) wrote :

 Bah, this is why you don't do protocol debugging at 3:30am, no matter how helpful you want to be.

Revision history for this message
Robert Collins (lifeless) wrote :

Indeed, the attached stream looks fine to me, and subunit-stats sees:
Total tests: 21791
Passed tests: 21260
subunit-ls reports tests after the named one:
lp.bugs.browser.tests.test_bugtask.TestBugTaskView.test_rendered_query_counts_constant_with_team_memberships
lp.testing.layers.ZopelessAppServerLayer:setUp
...

Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for Launchpad itself because there has been no activity for 60 days.]

Changed in launchpad:
status: Incomplete → Expired
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

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