diff options
| author | Diego Novillo <dnovillo@google.com> | 2012-08-13 14:00:55 -0400 |
|---|---|---|
| committer | Diego Novillo <dnovillo@gcc.gnu.org> | 2012-08-13 14:00:55 -0400 |
| commit | c577382e7b00c09e89f0b0e8cff4361795f9499a (patch) | |
| tree | c5ecf16dc9bbfbcd6c56c37913b6446d7b75177d /gcc/cfgexpand.c | |
| parent | 621bc04640ee2dd1894285c6a536c78c826d8d4e (diff) | |
| download | gcc-c577382e7b00c09e89f0b0e8cff4361795f9499a.zip gcc-c577382e7b00c09e89f0b0e8cff4361795f9499a.tar.gz gcc-c577382e7b00c09e89f0b0e8cff4361795f9499a.tar.bz2 | |
Implement support for expiring expected results in validate_failures.py.
I noticed recently that while the validator was accepting the
'expire=YYYYMMDD' attribute, it was not actually doing anything with
it.
This patch fixes the oversight.
2012-08-13 Diego Novillo <dnovillo@google.com>
* testsuite-management/validate_failures.py: Import datetime.
(TestResult.ExpirationDate): New.
(TestResult.HasExpired): New.
(ParseSummary): Call it. If it returns True, warn that the
expected failure has expired and do not add it to the set of
expected results.
(GetResults): Clarify documentation.
From-SVN: r190351
Diffstat (limited to 'gcc/cfgexpand.c')
0 files changed, 0 insertions, 0 deletions