lockutils test_synchronized_externally is racy and regularly fails
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
oslo-incubator |
Fix Released
|
High
|
Mark McLoughlin | ||
Grizzly |
Fix Released
|
High
|
Mark McLoughlin |
Bug Description
In Jenkins, we're very regularly seeing this test failure:
FAIL: We can lock across multiple processes
-----
Traceback (most recent call last):
File "/home/
f(rpipe2, wpipe1)
File "/home/
retval = f(*args, **kwargs)
File "/home/
AssertionError: The other process, which was supposed to be locked, wrote on its end of the pipe
'1 != 0' = '%s != %s' % (safe_repr(1), safe_repr(0))
'The other process, which was supposed to be locked, wrote on its end of the pipe' = self._formatMes
>> raise self.failureExc
It has gotten to the stage that we need to turn off this test, but this bug report will keep track of the fact that we still need to fix it.
Changed in oslo: | |
assignee: | nobody → Mark McLoughlin (markmc) |
status: | Triaged → In Progress |
summary: |
- lockutils test_synchronized_externally regularly fails + lockutils test_synchronized_externally is racy and regularly fails |
Changed in oslo: | |
milestone: | none → grizzly-2 |
status: | Fix Committed → Fix Released |
Here's an effort we made previously to fix it: https:/ /review. openstack. org/14556
Practically speaking, this bug is probably a duplicate of bug #1068316