public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Doug Evans <dje@google.com>
To: Diego Novillo <dnovillo@google.com>
Cc: gcc-patches@gcc.gnu.org
Subject: Re: [RFA 4/8] validate_failures.py: rename --manifest to --manifest_path
Date: Thu, 29 Nov 2012 20:47:00 -0000	[thread overview]
Message-ID: <20663.51611.466694.808097@ruffy2.mtv.corp.google.com> (raw)
In-Reply-To: <CAD_=9DRWFR6kho8t90CfYfdgGsAy0n6ZxnyZk7ar1MQnhCEKGg@mail.gmail.com>

Diego Novillo writes:
 > On Sat, Nov 24, 2012 at 5:50 PM, Doug Evans <dje@google.com> wrote:
 > > Hi.
 > > This fourth patch renames option --manifest to --manifest_path.
 > > I have a later patch that adds a --manifest_name option, making "--manifest"
 > > too confusing/ambiguous.
 > >
 > > Ok to check in?
 > > [I still have to update invocations that use --manifest,
 > > but that's a separate patch.]
 > >
 > > 2012-11-24  Doug Evans  <dje@google.com>
 > >
 > >         * testsuite-management/validate_failures.py: Rename option --manifest to
 > >         --manifest_path.  Rename local variables manifest_name to manifest_path.
 > 
 > 
 > OK.

I ran into some issues, so I'm going to do this in baby steps.
This patch just renames the variables (for clarity's sake, at least for me :-)).

Ok to check in?

2012-11-29  Doug Evans  <dje@google.com>

	* testsuite-management/validate_failures.py: Rename variable
	manifest_name to manifest_path everywhere.

Index: validate_failures.py
===================================================================
--- validate_failures.py	(revision 193952)
+++ validate_failures.py	(working copy)
@@ -220,7 +220,7 @@
   return result_set
 
 
-def GetManifest(manifest_name):
+def GetManifest(manifest_path):
   """Build a set of expected failures from the manifest file.
 
   Each entry in the manifest file should have the format understood
@@ -228,8 +228,8 @@
 
   If no manifest file exists for this target, it returns an empty set.
   """
-  if os.path.exists(manifest_name):
-    return ParseSummary(manifest_name)
+  if os.path.exists(manifest_path):
+    return ParseManifest(manifest_path)
   else:
     return set()
 
@@ -334,14 +334,14 @@
     (srcdir, target, valid_build) = GetBuildData(options)
     if not valid_build:
       return False
-    manifest_name = _MANIFEST_PATH_PATTERN % (srcdir, target)
+    manifest_path = _MANIFEST_PATH_PATTERN % (srcdir, target)
   else:
-    manifest_name = options.manifest
-    if not os.path.exists(manifest_name):
-      Error('Manifest file %s does not exist.' % manifest_name)
+    manifest_path = options.manifest
+    if not os.path.exists(manifest_path):
+      Error('Manifest file %s does not exist.' % manifest_path)
 
-  print 'Manifest:         %s' % manifest_name
-  manifest = GetManifest(manifest_name)
+  print 'Manifest:         %s' % manifest_path
+  manifest = GetManifest(manifest_path)
   sum_files = GetSumFiles(options.results, options.build_dir)
   actual = GetResults(sum_files)
 
@@ -357,14 +357,14 @@
   if not valid_build:
     return False
 
-  manifest_name = _MANIFEST_PATH_PATTERN % (srcdir, target)
-  if os.path.exists(manifest_name) and not options.force:
+  manifest_path = _MANIFEST_PATH_PATTERN % (srcdir, target)
+  if os.path.exists(manifest_path) and not options.force:
     Error('Manifest file %s already exists.\nUse --force to overwrite.' %
-          manifest_name)
+          manifest_path)
 
   sum_files = GetSumFiles(options.results, options.build_dir)
   actual = GetResults(sum_files)
-  manifest_file = open(manifest_name, 'w')
+  manifest_file = open(manifest_path, 'w')
   for result in sorted(actual):
     print result
     manifest_file.write('%s\n' % result)

  reply	other threads:[~2012-11-29 20:46 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-11-24 22:50 Doug Evans
2012-11-25 15:41 ` Diego Novillo
2012-11-29 20:47   ` Doug Evans [this message]
2012-11-29 22:47     ` 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=20663.51611.466694.808097@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).