| 1 |
# @HEADER |
| 2 |
# ***************************************************************************** |
| 3 |
# TriBITS: Tribal Build, Integrate, and Test System |
| 4 |
# |
| 5 |
# Copyright 2013-2016 NTESS and the TriBITS contributors. |
| 6 |
# SPDX-License-Identifier: BSD-3-Clause |
| 7 |
# ***************************************************************************** |
| 8 |
# @HEADER |
| 9 |
|
| 10 |
|
| 11 |
# |
| 12 |
# Increase size of test output sent to CDash to increase the likelihood of |
| 13 |
# errors being visible on the dashboard results. |
| 14 |
# |
| 15 |
|
| 16 |
set(CTEST_CUSTOM_MAXIMUM_PASSED_TEST_OUTPUT_SIZE 50000) |
| 17 |
|
| 18 |
set(CTEST_CUSTOM_MAXIMUM_FAILED_TEST_OUTPUT_SIZE 20000000) |
| 19 |
|
| 20 |
# |
| 21 |
# These variables represent the maximum number of characters sent as test |
| 22 |
# output for an individual test in the Test.xml file that goes to the CDash |
| 23 |
# server. If 0, then all output is sent, regardless of size. 0 is not |
| 24 |
# recommended, however, because the maximum xml output that CDash can easily |
| 25 |
# parse (on a web server with default php and MySQL settings) appears to be in |
| 26 |
# the 50 to 100 MB range. |
| 27 |
# |
| 28 |
# So the sum of the output from all tests sent at one time in a Test.xml file |
| 29 |
# should strive to be under 50M. If output is larger than that, submissions |
| 30 |
# should be broken up into smaller, multiple Test.xml files... |
| 31 |
# |