diff options
author | Bill Hoffman <bill.hoffman@kitware.com> | 2017-07-27 16:30:34 (GMT) |
---|---|---|
committer | Brad King <brad.king@kitware.com> | 2017-08-07 15:01:49 (GMT) |
commit | 1c61d240ddd5fe493427a10ad571b662ded97eb8 (patch) | |
tree | b260387cf2694e4cc698c2498a578695e721fcc5 /Modules/Platform/BlueGeneP-static-XL-C.cmake | |
parent | af9708881f4c2d8f501ae63a4088c020edb6f070 (diff) | |
download | CMake-1c61d240ddd5fe493427a10ad571b662ded97eb8.zip CMake-1c61d240ddd5fe493427a10ad571b662ded97eb8.tar.gz CMake-1c61d240ddd5fe493427a10ad571b662ded97eb8.tar.bz2 |
CTest: Report lines matched by launchers
Since launchers show the entire stderr/stdout for a command and only
skip it if all of the lines are suppressed, it can be hard to tell if
individual suppressions are working. Mark up the output reported to
CDash with a prefix for each line indicating whether it was a matched or
suppressed warning. Lines that are suppressed are prefixed with
`[CTest: warning suppressed]` and lines that match the warning
expression are prefixed with `[CTest: warning matched]`. This should
make it easier for people to add suppressions as they will know what
they need to match and what they have already suppressed. This is an
issue because if there is more than one warning in a single compiler
output you have to suppress all of them before it will go away.
Diffstat (limited to 'Modules/Platform/BlueGeneP-static-XL-C.cmake')
0 files changed, 0 insertions, 0 deletions