Bug #10712
TestFlush intermittent failure on scatter_writebehind event
0%
Description
The flush code isn't fully deterministic, sometimes the single log segment left behind just has a subtreemap event, and sometimes there is an extra scatter_writebehind in there too.
Either make the code deterministic or make the test tolerant.
Associated revisions
tasks: fix intermittent failure in TestFlush
This was an overly strict success condition: the
flush operation doesn't promise to leave you an empty
journal, it promises that anything in the journal
before the flush will be flushed.
Fixes: #10712
Signed-off-by: John Spray <john.spray@redhat.com>
tasks: fix intermittent failure in TestFlush
This was an overly strict success condition: the
flush operation doesn't promise to leave you an empty
journal, it promises that anything in the journal
before the flush will be flushed.
Fixes: #10712
Signed-off-by: John Spray <john.spray@redhat.com>
(cherry picked from commit d20d9238cd59bca002d682cbcdc444e15e856de1)
History
#2 Updated by Sage Weil about 9 years ago
- Priority changed from Normal to Urgent
urgent by default since this causes qa tests to fail
#3 Updated by Sage Weil about 9 years ago
- Source changed from other to Q/A
#4 Updated by John Spray about 9 years ago
- Status changed from New to 7
Updating the test to tolerate this condition, as it's a valid outcome from flush
#5 Updated by John Spray about 9 years ago
- Status changed from 7 to Fix Under Review
#6 Updated by John Spray about 9 years ago
- Status changed from Fix Under Review to Resolved
#7 Updated by Loïc Dachary almost 9 years ago
- Status changed from Resolved to Pending Backport
- Backport set to hammer
- hammer backport https://github.com/ceph/ceph-qa-suite/pull/429
#9 Updated by Loïc Dachary almost 9 years ago
- Status changed from Pending Backport to Resolved
- Regression set to No