Bug #19207
The "VALIDATION ERROR" string in result.log is misleading
Status:
New
Priority:
Low
Assignee:
-
Target version:
-
Start date:
03/02/2018
Due date:
% Done:
0%
Estimated time:
Description
Looking at the result.log file produced by test_runner, it's quite confusing to find VALIDATION ERRORS! in a test that apparently succeeded.
It turns out that those are GDML validation errors, and not validation test errors.
Replacing that message with GDML VALIDATION ERRORS! would be clearer.