-
Notifications
You must be signed in to change notification settings - Fork 47
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Merge pull request #640 from jjhursey/topic/update-README
README: Update links, and add paper citation
- Loading branch information
Showing
1 changed file
with
19 additions
and
8 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -10,6 +10,7 @@ Copyright (c) 2004-2005 The Regents of the University of California. | |
All rights reserved. | ||
Copyright (c) 2006-2007 Cisco Systems, Inc. All rights reserved. | ||
Copyright (c) 2006-2007 Sun Microsystems, Inc. All rights reserved. | ||
Copyright (c) 2018 IBM Corporation. All rights reserved. | ||
$COPYRIGHT$ | ||
|
||
Additional copyrights may follow | ||
|
@@ -87,6 +88,16 @@ The main (loose) requirements that we had for the MTT are: | |
well-defined interface. | ||
|
||
|
||
How to cite this software | ||
------------------------- | ||
Hursey J., Mallove E., Squyres J.M., Lumsdaine A. (2007) An Extensible | ||
Framework for Distributed Testing of MPI Implementations. In Recent | ||
Advances in Parallel Virtual Machine and Message Passing Interface. | ||
EuroPVM/MPI 2007. Lecture Notes in Computer Science, vol 4757. Springer, | ||
Berlin, Heidelberg. | ||
https://doi.org/10.1007/978-3-540-75416-9_15 | ||
|
||
|
||
Overview | ||
-------- | ||
|
||
|
@@ -123,7 +134,7 @@ configuration file is used to specify which MPI implementations to use | |
and which tests to run. | ||
|
||
The Open MPI Project uses MTT for nightly regression testing. A | ||
sample client configuration file is included in | ||
sample Perl client configuration file is included in | ||
samples/perl/ompi-core-template.ini. This template will require | ||
customization for each site's specific requirements. It is also | ||
suitable as an example for organizations outside of the Open MPI | ||
|
@@ -144,8 +155,8 @@ necessary. See comments in the ompi-core-template.ini file for | |
details. | ||
|
||
|
||
Running the MTT client | ||
---------------------- | ||
Running the MTT Perl client | ||
--------------------------- | ||
|
||
Having run the MTT client across several organizations within the Open | ||
MPI Project for quite a while, we have learned that even with common | ||
|
@@ -190,10 +201,9 @@ testing software -- we do want to keep it somewhat focused on the | |
needs and requires of testing MPI implementations. As such, the usage | ||
flow is somewhat structured towards that bias. | ||
|
||
As of October 2007, we are finally ready for a public release. But | ||
note that the software has been developed internally to the Open MPI | ||
project and will likely experience some growing pains while adjusting | ||
to a larger community. | ||
It should be noted that the software has been mostly developed internally | ||
to the Open MPI project and will likely experience some growing pains | ||
while adjusting to a larger community. | ||
|
||
|
||
License | ||
|
@@ -221,14 +231,15 @@ [email protected] is considered different than | |
[email protected]!). Visit this page to subscribe to the | ||
user's list: | ||
|
||
http://www.open-mpi.org/mailman/listinfo.cgi/mtt-users | ||
https://lists.open-mpi.org/mailman/listinfo/mtt-users | ||
|
||
Developer-level bug reports, questions, and comments should generally | ||
be sent to the developer's mailing list ([email protected]). | ||
Please do not post the same question to both lists. As with the | ||
user's list, only subscribers are allowed to post to the developer's | ||
list. Visit the following web page to subscribe: | ||
|
||
https://lists.open-mpi.org/mailman/listinfo/mtt-devel | ||
http://www.open-mpi.org/mailman/listinfo.cgi/mtt-devel | ||
|
||
When submitting bug reports to either list, be sure to include as much | ||
|