TestResumeTransactionsFailure crazy timing call

Bug #1554088 reported by Curtis Hovey
12
This bug affects 2 people
Affects Status Importance Assigned to Milestone
Canonical Juju
Expired
Medium
Unassigned
juju-core
Won't Fix
Medium
Unassigned
1.25
Won't Fix
Medium
Unassigned

Bug Description

As seen at
     http://reports.vapour.ws/releases/issue/5571bdfb749a560afdca52ac
TestResumeTransactionsFailure fails with a crazy report

resumer_test.go:113:
    c.Assert(len(calls), jc.LessThan, maxCalls+1)
... obtained int = 4
... expected int = 4

The value might have been wrong when the test was evaluated, but it appears to be correct at the time of printing

Revision history for this message
William Reade (fwereade) wrote :

Less crazy than it seems: it's saying that len(calls) is 4, and maxCalls+1 is 4, and 4<4 is not true, so the assert fails. It... could be expressed better.

William Reade (fwereade)
Changed in juju-core:
assignee: nobody → William Reade (fwereade)
tags: added: 2.0-count
William Reade (fwereade)
Changed in juju-core:
assignee: William Reade (fwereade) → nobody
affects: juju-core → juju
Changed in juju-core:
importance: Undecided → Medium
status: New → Triaged
Changed in juju-core:
status: Triaged → Won't Fix
Revision history for this message
Tim Penhey (thumper) wrote :

It has been some time since the last failure.

Changed in juju:
status: Triaged → Incomplete
Revision history for this message
Launchpad Janitor (janitor) wrote :

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

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

Duplicates of this bug

Other bug subscribers

Remote bug watches

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