Mirror of the lttng-dev mailing list
 help / color / mirror / Atom feed
From: Nathan_Lynch@mentor.com (Nathan Lynch)
Subject: [lttng-dev] [PATCH] lttng-tools: remove bogus argument from prove invocation
Date: Mon, 27 Oct 2014 23:02:58 -0500	[thread overview]
Message-ID: <544F1572.2040702@mentor.com> (raw)
In-Reply-To: <CAF4oYfEgNmiThfUW9Kj8+pYu-3QdE4KtUivr9mztf-Jb-=rocQ@mail.gmail.com>

On 10/27/2014 09:38 PM, Jonathan Rajotte wrote:
> Hey
> 
> On Mon, Oct 27, 2014 at 10:00 PM, Nathan Lynch <nathan_lynch at mentor.com
> <mailto:nathan_lynch at mentor.com>> wrote:
> 
>     An argument of "$2" was added to the prove command line in
>     tests/run.sh by 68270f0f604e "Mi test: Basic test structure".  This is
>     harmless since run.sh is never called with more than one argument, but
> 
> 
> The multiple arguments could be overcome by adding "" to the multiple
> test files list but as you said it is confusing and error prone.  
> 
> This actually can be used to debug test with a "-v". Or add any basic
> arguments to the prove command and was simply convenient at the time.If
> this actually break patch from OE ( I assume OE stand for OpenEmbedded
> and you are talking about this commit [1])  I'm okai with reverting the
> change I introduced.

I didn't intend to imply that upstream LTTng is responsible for keeping
patches working in a downstream project like OE.  I mentioned OE because
that's how my attention was drawn to this change.

If the $2 argument has a legitimate use, I suggest that it be made a bit
more clear since 1) the commit that introduced it didn't mention it at
all, and 2) no code in-tree actually makes use of the extra argument.

I figured it was likely a mistake.




  reply	other threads:[~2014-10-28  4:02 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-10-28  2:00 Nathan Lynch
2014-10-28  2:38 ` Jonathan Rajotte
2014-10-28  4:02   ` Nathan Lynch [this message]
2014-10-28  4:15     ` Jonathan Rajotte
2014-10-29 18:28 ` David Goulet

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=544F1572.2040702@mentor.com \
    --to=nathan_lynch@mentor.com \
    /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