Actions
Bug #23504
closedtests: unittest_pglog timeout
% Done:
0%
Source:
Tags:
Backport:
luminous, jewel
Regression:
No
Severity:
3 - minor
Reviewed:
Affected Versions:
ceph-qa-suite:
Pull request ID:
Crash signature (v1):
Crash signature (v2):
Description
The ASSERT_DEATH test in unittest_pglog (at the very end of merge_log test) seems to cause transient test failure due to timeout. We already removed the EXPECT_DEATH tests in http://tracker.ceph.com/issues/18030 so I'm guessing the solution in this case is similar (remove the test).
---------------------------------------------------------- [==========] Running 42 tests from 4 test cases. [----------] Global test environment set-up. [----------] 23 tests from PGLogTest [ RUN ] PGLogTest.rewind_divergent_log [ OK ] PGLogTest.rewind_divergent_log (1 ms) [ RUN ] PGLogTest.merge_old_entry [ OK ] PGLogTest.merge_old_entry (0 ms) [ RUN ] PGLogTest.merge_log [WARNING] /opt/j/ws/mkck/src/googletest/googletest/src/gtest-death-test.cc:836:: Death tests use fork(), which is unsafe particularly in a threaded context. For this test, Google Test detected 3 threads.
Updated by Nathan Cutler about 6 years ago
- Description updated (diff)
- Status changed from New to In Progress
Updated by Nathan Cutler about 6 years ago
- Related to Bug #18030: tests: unittest_pglog timeout added
Updated by Nathan Cutler about 6 years ago
- Status changed from In Progress to Fix Under Review
Updated by Nathan Cutler about 6 years ago
- Status changed from Fix Under Review to Pending Backport
Updated by Nathan Cutler about 6 years ago
- Copied to Backport #23522: luminous: tests: unittest_pglog timeout added
Updated by Nathan Cutler about 6 years ago
- Copied to Backport #23523: jewel: tests: unittest_pglog timeout added
Updated by Nathan Cutler about 6 years ago
- Status changed from Pending Backport to Resolved
Actions