Open MPI logo

Open MPI Development 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: [OMPI devel] testing assignments/requests
From: Paul Hargrove (phhargrove_at_[hidden])
Date: 2014-01-24 17:04:50

It looks like, with the possible exception of iterating with Jeff on
Fortran configure tests, my (annual?) round of
torture-the-open-mpi-dev^H^H^Hsources is nearing its end.

Some of have probably noticed that I started mining the ticket system for
things to test. I've searched for my name, for certain platforms I have
access to, and have skimmed all the open CMRs and many defects for v1.7.
 I've added myself to the CC field on some where I may have the (unique?)
ability to verify that the fix was effective.

I did not search closed tickets. If there are any (non-documentation)
issues for 1.7.4 that have been closed, then my testing last night PROBABLY
covered them. However, if there are specific configure options (like
--enable-builtin-atomics for #3081) then I probably did NOT test it last
night. So, if there are any items in v1.7 that you would specifically like
me to (re)test, please let me know (CCing user "phargrov" in trac is
preferred if a ticket already exists).

For the future, when there are tickets for defects where I was the original
(devel list?) reporter OR you think I may be the best/only candidate to
verify a fix, please feel free to add me to the CC field. At worse I'll
ignore the emails, but at best I can (re)test to confirm that a fix (either
proposed or committed) actually works. By adding me to the CC field, a
portion of this process can continue year-round instead of being all
crammed into the RC period. This applies ESPECIALLY to CMRs to 1.7.5, to
avoid unnecessary delays of v1.8.

An aside:
At least twice in this round of testing it was discovered that issues I had
reported in 1.5/1.6 got fixed in the branch WITHOUT being fixed in the
trunk. If there is some flaw in the process that could be addressed by
changing how *I* operate, please let me know. I am hesitant to switch from
mailing-list reports to entering my own tickets, but could if that it


Paul H. Hargrove                          PHHargrove_at_[hidden]
Future Technologies Group
Computer and Data Sciences Department     Tel: +1-510-495-2352
Lawrence Berkeley National Laboratory     Fax: +1-510-486-6900