View Issue Details [ Jump to Notes ]

[ Print ]

Project

Category

View Status

Date Submitted

Last Update

0012406

CDash

(No Category)

public

2011-08-17 05:27

2011-08-17 11:25

Reporter

Stephen Kelly

Assigned To

David Cole

Priority

normal

Severity

minor

Reproducibility

have not tried

Status

resolved

Resolution

no change required

Platform

OS Version

Product Version

Target Version

Fixed in Version

2.0

Summary

0012406: CDash sometimes cuts off output of build

Description

For example,

http://www.cdash.org/CDash/testDetails.php?test=110005920&build=1438544 [^]

There is one line which presumably exceeds 1024 chars before the next newline. As a result that line and all following lines are truncated.

At least, the following lines should not be truncated, and ideally, the char limit would be discarded. If the issue is that it makes the page too wide, I'm certain there are ways to make the text wrap on the page.

As it is there appears to be no way for me to see the output of the test (unless it's somewhere else too?)

Tags

No tags attached.

Attached Files

Relationships

Notes
(0027214) Bill Hoffman (manager) 2011-08-17 09:58	No, that is not what is going on. CTest truncates that data before it even gets to CDash. The total number of chars allowed by default is 1024 for a passing test. This can be overridden by using something like this: MESSAGE("To prevent CTest from stripping output, you have to display: CTEST_FULL_OUTPUT") So, if CTEST_FULL_OUTPUT is in the output of a test, no truncation will happen. This is to keep the CDash DB from getting full of passing test data that is usually not even looked at. Failing test allow more output by default.

(0027217) David Cole (manager) 2011-08-17 11:25	CDash displays all output that ctest sends it... ctest is the one doing the output truncation. You can emit "CTEST_FULL_OUTPUT" on the stdout stream to preserve all the output for a given test. Or you can set the CTestCustom variable, CTEST_CUSTOM_MAXIMUM_PASSED_TEST_OUTPUT_SIZE to increase it for all tests for your project. If you do take this approach, that variable should be set to an integer that is the maximum size in bytes.

Issue History
Date Modified	Username	Field	Change
2011-08-17 05:27	Stephen Kelly	New Issue
2011-08-17 09:46	David Cole	Assigned To	=> David Cole
2011-08-17 09:46	David Cole	Status	new => assigned
2011-08-17 09:58	Bill Hoffman	Note Added: 0027214
2011-08-17 11:25	David Cole	Note Added: 0027217
2011-08-17 11:25	David Cole	Status	assigned => resolved
2011-08-17 11:25	David Cole	Fixed in Version	=> 2.0
2011-08-17 11:25	David Cole	Resolution	open => no change required