Project

General

Profile

Actions

Bug #23504

closed

tests: unittest_pglog timeout

Added by Nathan Cutler about 6 years ago. Updated about 6 years ago.

Status:
Resolved
Priority:
Normal
Assignee:
Category:
-
Target version:
-
% 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.

Related issues 3 (0 open3 closed)

Related to Ceph - Bug #18030: tests: unittest_pglog timeoutResolvedLoïc Dachary11/24/2016

Actions
Copied to Ceph - Backport #23522: luminous: tests: unittest_pglog timeoutResolvedNathan CutlerActions
Copied to Ceph - Backport #23523: jewel: tests: unittest_pglog timeoutResolvedNathan CutlerActions
Actions #1

Updated by Nathan Cutler about 6 years ago

  • Description updated (diff)
  • Status changed from New to In Progress
Actions #2

Updated by Nathan Cutler about 6 years ago

  • Related to Bug #18030: tests: unittest_pglog timeout added
Actions #3

Updated by Nathan Cutler about 6 years ago

  • Status changed from In Progress to Fix Under Review
Actions #4

Updated by Nathan Cutler about 6 years ago

  • Status changed from Fix Under Review to Pending Backport
Actions #5

Updated by Nathan Cutler about 6 years ago

Actions #6

Updated by Nathan Cutler about 6 years ago

Actions #7

Updated by Nathan Cutler about 6 years ago

  • Status changed from Pending Backport to Resolved
Actions

Also available in: Atom PDF