Fix validate_failures.py in standalone testing.
commit828e50c53cc7d1d4e30ba32e2a7c7343d7f5fe46
authorDiego Novillo <dnovillo@google.com>
Wed, 6 Feb 2013 20:22:56 +0000 (6 15:22 -0500)
committerDiego Novillo <dnovillo@gcc.gnu.org>
Wed, 6 Feb 2013 20:22:56 +0000 (6 15:22 -0500)
treebc7faa6754990b2b335ea01836a03900191f9880
parentd0c4e31020ff1f11fe4db2dd1f66f111d2078217
Fix validate_failures.py in standalone testing.

When using validate_failures.py with --manifest and --results, we
don't need a GCC build directory.  This is useful when using the
validator outside of the build tree.  We were insisting on finding
a valid build tree regardless of those options.

Tested on x86_64.  Committed to trunk.

* testsuite-management/validate_failures.py: Update
Copyright years.
Request contributions not to use Python features newer
than 2.4.
(GetBuildData): If this is not a build directory,
emit an error only if --results or --manifest are missing.

From-SVN: r195817
contrib/ChangeLog
contrib/testsuite-management/validate_failures.py