From: Doug Evans <dje@google.com>
To: dnovillo@google.com, gcc-patches@gcc.gnu.org
Subject: [RFA 2/8] validate_failures.py: use target_alias
Date: Sat, 24 Nov 2012 22:43:00 -0000 [thread overview]
Message-ID: <yjt238zy7hb9.fsf@ruffy2.mtv.corp.google.com> (raw)
Hi.
This second patch uses "target_alias" instead of "target" in the help text,
and makes some minor whitespace changes.
Ok to check in?
2012-11-24 Doug Evans <dje@google.com>
* testsuite-management/validate_failures.py: Use <target_alias> instead of
<target>. Minor whitespace changes.
--- validate_failures.py= 2012-11-19 11:47:29.997632548 -0800
+++ validate_failures.py 2012-11-24 13:22:25.805598185 -0800
@@ -217,8 +217,7 @@ def GetManifest(manifest_name):
Each entry in the manifest file should have the format understood
by the TestResult constructor.
- If no manifest file exists for this target, it returns an empty
- set.
+ If no manifest file exists for this target, it returns an empty set.
"""
if os.path.exists(manifest_name):
return ParseSummary(manifest_name)
@@ -409,7 +408,7 @@ def Main(argv):
parser.add_option('--manifest', action='store', type='string',
dest='manifest', default=None,
help='Name of the manifest file to use (default = '
- 'taken from contrib/testsuite-managment/<target>.xfail)')
+ 'taken from contrib/testsuite-managment/<target_alias>.xfail)')
parser.add_option('--produce_manifest', action='store_true',
dest='produce_manifest', default=False,
help='Produce the manifest for the current '
@@ -436,6 +435,7 @@ def Main(argv):
else:
return 1
+
if __name__ == '__main__':
retval = Main(sys.argv)
sys.exit(retval)
next reply other threads:[~2012-11-24 22:43 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-24 22:43 Doug Evans [this message]
2012-11-25 15:34 ` Diego Novillo
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=yjt238zy7hb9.fsf@ruffy2.mtv.corp.google.com \
--to=dje@google.com \
--cc=dnovillo@google.com \
--cc=gcc-patches@gcc.gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).