Activity log for bug #1363739

Date Who What changed Old value New value Message
2014-08-31 21:37:25 Joshua Harlow bug added bug
2014-08-31 21:37:33 Joshua Harlow taskflow: importance Undecided Medium
2014-09-02 19:40:10 Joshua Harlow summary Use latch type instead of thread event in tests Use and verify latch/event wait timeouts
2014-09-02 19:41:05 Joshua Harlow description When verifying some async activity has occurred using the event set/wait paradigm we should instead use our customized latch type that can return if the latch amount was reached with-in the given timeout. This latch type also performs this operation correctly (the threading event class does not return whether it was set in python 2.6 from the wait() method) so we will be able to use this correctly on all supported python versions without issue... 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.
2014-09-08 00:50:46 Joshua Harlow taskflow: assignee Joshua Harlow (harlowja)
2014-09-08 00:50:48 Joshua Harlow taskflow: status New In Progress
2014-09-12 22:00:14 Joshua Harlow taskflow: milestone next-juno
2014-09-15 21:32:50 Doug Hellmann taskflow: milestone next-juno next-kilo
2014-10-19 02:53:50 OpenStack Infra taskflow: status In Progress Fix Committed
2014-12-19 02:38:29 Joshua Harlow taskflow: status Fix Committed Fix Released