BTW, you can run quick tests to see if the e-mail reporter is working
-- do something like:
./client/mtt ...your normal MTT command line args... \
--section trivial --test-build --force --section reporter
This will just build the "trivial" section (which is just 8 small
apps: ring and hello in C, C++, F77, F90) and then submit a report,
including the email reporter.
It's a quick-n-dirty way to test your reporter without doing a full-
blown MTT run.
On Jan 10, 2008, at 2:44 PM, Ethan Mallove wrote:
> On Thu, Jan/10/2008 06:27:03PM, Pavel Shamis (Pasha) wrote:
>> Ethan Mallove wrote:
>>> Hi Pasha,
>>> I confess that I don't use the Email reporter. I think the
>>> email_subject is out-of-date. Try this:
>>> email_subject = MPI test results: ¤t_section()
>>> I'm unsure about the empty email body, but have an idea.
>>> What does this output for you?
>>> $ which Mail mailx mail rmail mutt elm
>> which Mail mailx mail rmail mutt elm
>>> I'm guessing the problem is that your mail agent has a
>>> problem with doing this:
>>> $ cat foo.txt | <mail-agent> -s "MTT Mail Test"
>>> $ cat foo.txt
>>> start_timestamp: blah blah
>> the command : cat foo.txt | /usr/bin/Mail -s "MTT Mail Test"
>> worked nice for me, I got the mail with the subj.
> I might've misread your last email. Did the new
> email_subject INI parameter from above solve your issue? I'd
> have to see the --debug output to know why the Subject was
>> email_subject = MPI test results: $phase / $sectiona
>> In mail body I got:
>> start_timestamp: Thu Jan 10 12:25:56 2008
> Was the body of the email okay, or was it really blank
> following the start_timestamp line?
>> Pavel Shamis (Pasha)
>> Mellanox Technologies
>> mtt-users mailing list
> mtt-users mailing list