Project

General

Profile

Actions

Bug #43566

closed

jenkins: ctest output size for failed test is too short

Added by Mykola Golub over 4 years ago. Updated over 2 years ago.

Status:
Resolved
Priority:
Normal
% Done:

0%

Source:
Tags:
Backport:
Octopus, Pacific
Regression:
No
Severity:
Reviewed:
Affected Versions:
ceph-qa-suite:
Pull request ID:
Crash signature (v1):
Crash signature (v2):

Description

We observe sporadic failures for rbd-mirror [1] and librbd [2] unit tests for jenkins make check. The problem is that the test's output buffer is too short and we don't see which test exactly fails to nail it down (trying to reproduce it locally rerunning the whole test set has not succeeded so far).

Can we increase somehow the output size? I suppose it can be tweaked by `--test-output-size-failed` ctest option [3]. Also, there is the cmake variable `CTEST_CUSTOM_MAXIMUM_FAILED_TEST_OUTPUT_SIZE` [1], which according to the documentation is 300K.

Interestingly, the amd64 jenkins shows the whole fail test output, though I failed to find any related difference in ceph-build scripts between x86 and amd64. Probably, ctest is built with different default values there.

The easiest way to see the problem, I think, is to add something like `exit 1` at the end of `src/test/run-rbd-unit-tests.sh` to make it fail.

[1] https://tracker.ceph.com/issues/43274
[2] https://tracker.ceph.com/issues/43228
[3] https://cmake.org/cmake/help/v3.4/manual/ctest.1.html
[4] https://cmake.org/cmake/help/v3.4/variable/CTEST_CUSTOM_MAXIMUM_FAILED_TEST_OUTPUT_SIZE.html


Related issues 2 (2 open0 closed)

Related to rbd - Bug #43274: unittest_rbd_mirror: Exception: SegFaultNeed More Info

Actions
Related to rbd - Bug #43228: run-rbd-unit-tests-0.sh failsNeed More Info

Actions
Actions

Also available in: Atom PDF