Have a deterministic way to check OOPS generation in tests.

Bug #567689 reported by Karl Fogel
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Launchpad itself
Fix Released
Low
Tim Penhey

Bug Description

We have no way to reliably test OOPS generation. For example, see the race condition recently documented in bug #567257. While there is a mostly-okay fix for that particular bug, we'd be much better off with a generalized solution that is not vulnerable to race conditions at all. See that bug, and lib/lp/code/model/tests/test_diff.py:TestDiffInScripts.test_fromFile_withError(), for how we currently test OOPSes.

Related branches

Karl Fogel (kfogel)
description: updated
summary: - Have a guaranteed way to check OOPS generation in tests.
+ Have a deterministic way to check OOPS generation in tests.
Gary Poster (gary)
Changed in launchpad-foundations:
status: New → Triaged
importance: Undecided → Low
Tim Penhey (thumper)
Changed in launchpad-foundations:
status: Triaged → In Progress
assignee: nobody → Tim Penhey (thumper)
milestone: none → 10.04
Revision history for this message
Ursula Junque (ursinha) wrote : Bug fixed by a commit
Changed in launchpad-foundations:
status: In Progress → Fix Committed
tags: added: qa-needstesting
Tim Penhey (thumper)
tags: added: qa-ok
removed: qa-needstesting
Changed in launchpad-foundations:
status: Fix Committed → Fix Released
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.