summaryrefslogtreecommitdiffstats
path: root/libjava/classpath/gnu/java/beans/decoder/JavaHandler.java
diff options
context:
space:
mode:
authordnovillo <dnovillo@138bc75d-0d04-0410-961f-82ee72b054a4>2012-06-05 00:28:56 +0000
committerdnovillo <dnovillo@138bc75d-0d04-0410-961f-82ee72b054a4>2012-06-05 00:28:56 +0000
commit4de0f292e4bdfb084c68ef8c8d62980154f4bd6f (patch)
treec77879cf2b6cbb99c2ca5a756d1bd3f2ff9b3309 /libjava/classpath/gnu/java/beans/decoder/JavaHandler.java
parent8454dd0816b6c997b85dcf30cc8aa277d7da1227 (diff)
downloadppe42-gcc-4de0f292e4bdfb084c68ef8c8d62980154f4bd6f.tar.gz
ppe42-gcc-4de0f292e4bdfb084c68ef8c8d62980154f4bd6f.zip
Extend validate_failures.py to run outside the build directory.
This patch adds three new arguments to validate_failures.py so it can be used outside the build directory: --ignore_missing_failures When a failure is expected in the manifest but it is not found in the actual results, the script produces a note alerting to this fact. This means that the expected failure has been fixed, or it did not run, or it may simply be flaky. With this option, one can ask the script not to show the missing failures. --manifest Name of the manifest file to use. By default, the script will look for the manifest file in the source directory associated with this build. With this option, one can point to any arbitrary manifest file. I renamed the old --manifest flag to --produce_manifest. --results Space-separated list of .sum files with the testing results to check. The only content needed from these files are the lines starting with FAIL, XPASS or UNRESOLVED. git-svn-id: svn+ssh://gcc.gnu.org/svn/gcc/trunk@188217 138bc75d-0d04-0410-961f-82ee72b054a4
Diffstat (limited to 'libjava/classpath/gnu/java/beans/decoder/JavaHandler.java')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud