mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Tim Tianyang Chen <tianyang.chen@oracle.com>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: linux-kernel@vger.kernel.org, dhaval.giani@oracle.com
Subject: Re: [PATCH 2/2][RFC]Ktest: Use dodie for critial failures
Date: Thu, 14 Dec 2017 16:11:31 -0800	[thread overview]
Message-ID: <9d01f0b6-9dc8-5c7a-df16-2ff089baa651@oracle.com> (raw)
In-Reply-To: <20171214190322.29d857ba@gandalf.local.home>



On 12/14/2017 04:03 PM, Steven Rostedt wrote:
> On Tue, 21 Nov 2017 10:53:35 -0800
> Tim Tianyang Chen <tianyang.chen@oracle.com> wrote:
>
>> Users should get emails when the script dies because of a critical failure. Critical
>> failures are defined as any errors that could terminate the script, via die().
>>
>> In order to add email support, this patch converts all die() to dodie() except:
>>    * when '-v' is used as an option to get the version of the script.
>>    * in Sig-Int handeler because it's not a fatal error to cancel the script.
>>    * the die() in dodie() itself actually kills the script.
> You basically converted all the "die" in the reading of the config file
> into "dodie" so that you could email. But since the reading of the
> config failed, there's no way to do the email, because that gets set by
> the config.
>
> Perhaps some can be converted, but most of these I would say, no.
Right, it shouldn't send emails when it fails to even parse the config. 
Since the script will yell immediately there is no need to email either.

Thanks,
Tim

      reply	other threads:[~2017-12-15  0:18 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20171120173738.34823-3-tianyang.chen@oracle.com>
2017-11-21 18:53 ` Tim Tianyang Chen
2017-12-15  0:03   ` Steven Rostedt
2017-12-15  0:11     ` Tim Tianyang Chen [this message]

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=9d01f0b6-9dc8-5c7a-df16-2ff089baa651@oracle.com \
    --to=tianyang.chen@oracle.com \
    --cc=dhaval.giani@oracle.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rostedt@goodmis.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

all inboxes | Powered by JetHome®