Use and verify latch/event wait timeouts
Bug #1363739 reported by
Joshua Harlow
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| taskflow |
Fix Released
|
Medium
|
Joshua Harlow | ||
Bug Description
When verifying some async activity has occurred using the event set/wait paradigm or latch countdown/wait paradigm we should make sure that the return result of that wait function is verified to have reached the desired
state and that instead of blocking forever when this does not happen that we block until a reasonable timeout occurs and then fail.
| Changed in taskflow: | |
| importance: | Undecided → Medium |
| summary: |
- Use latch type instead of thread event in tests + Use and verify latch/event wait timeouts |
| description: | updated |
| Changed in taskflow: | |
| assignee: | nobody → Joshua Harlow (harlowja) |
| status: | New → In Progress |
| Changed in taskflow: | |
| milestone: | none → next-juno |
| Changed in taskflow: | |
| milestone: | next-juno → next-kilo |
Revision history for this message
| OpenStack Infra (hudson-openstack) wrote Fix merged to taskflow (master) | #1 |
| Changed in taskflow: | |
| status: | In Progress → Fix Committed |
| Changed in taskflow: | |
| status: | Fix Committed → Fix Released |
To post a comment you must log in.
Reviewed: https:/
Committed: https:/
Submitter: Jenkins
Branch: master
commit 7ca631356efd943
Author: Joshua Harlow <email address hidden>
Date: Tue Sep 2 12:36:52 2014 -0700
Use and verify event and latch wait() return using timeouts
Instead of blocking up the whole test suite when a latch or
event was not decremented to its desired value (or not set for
an event) we should use a reasonably high value that we use
when waiting for those actions to occur and verify that when those
wait() functions return that we have reached the desired state and
if not either raise an exception or stop further testing.
Fixes bug 1363739
Change-Id: I8b40282ac2db9c