Open MPI logo

MTT Devel Mailing List Archives

  |   Home   |   Support   |   FAQ   |  

This web mail archive is frozen.

This page is part of a frozen web archive of this mailing list.

You can still navigate around this archive, but know that no new mails have been added to it since July of 2016.

Click here to be taken to the new web archives of this list; it includes all the mails that are in this frozen archive plus all new mails that have been sent to the list since it was migrated to the new archives.

Subject: Re: [MTT devel] MTT feature request
From: Jeff Squyres (jsquyres) (jsquyres_at_[hidden])
Date: 2013-03-28 07:53:56


Sorry for the delay in replying to this; somehow this mail slipped by me.

I'm all for what you described. Does your patch still apply to the current trunk? (Texteeporter was just recently split up a bit)

Sent from my phone. No type good.

On Feb 28, 2013, at 10:07 PM, "Thomas Naughton" <naughtont_at_[hidden]> wrote:

> Hey,
>
> First, thank you for MTT!
>
> I was curious if you would be willing to add a basic feature related to
> detailed emails. Basically, we only want the detailed test results if
> something fails.
>
> Initially I thought I could use an &if() funclet on the
> 'email_detailed_report' field, but it turns out the summary value used for
> "$overall_mtt_status" generated inside the TextFile reporter.
>
> So my solution is to just add another field for this case:
>
> # If true (1), send the detailed report if there were failures
> email_detailed_report_onfail
>
> Attached is a small patch against mtt-trunk (r1590).
>
> Thanks,
> --tjn
>
> _________________________________________________________________________
> Thomas Naughton naughtont_at_[hidden]
> Research Associate (865) 576-4184
> <email-detailed-report-onfail.patch>