search

open-mpi / mtt

MPI Testing Tool
https://open-mpi.github.io/mtt
Other
63 stars 47 forks source link

Have "back links" from details to Test Build / MPI install #303

Open ompiteam opened 10 years ago

ompiteam commented 10 years ago

There are times when you're looking at a test run or test build and would like to see some detail of the corresponding MPI install. As such, we should add the following:

ompiteam commented 10 years ago

Imported from trac issue 302. Created by jsquyres on 2007-09-04T21:46:58, last modified: 2008-02-06T15:53:16

ompiteam commented 10 years ago

Trac comment by jsquyres on 2007-09-22 09:52:01:

In addition, it could also be useful to be able to visualize entire trees of lineage depicting an MPI install, all the Test Builds that are children of that, and all the Test Runs that are children of that. Pairing this with "drill down" methodology -- perhaps even with some web 2.0 technologies for visualization and dynamic updates -- could result in easily showing the lineage of a specific test run failure, further helping root cause efforts.

ompiteam commented 10 years ago

Trac comment by jjhursey on 2008-02-06 15:53:16:

Similar to this the main query used for summary is completely time base without regard to the dependency between the three stages. For example this [http://www.open-mpi.org/mtt/index.php?do_redir=527 permalink] shows a Cisco result in which the first entry has Test Run results, but no MPI Install or Test Build results.

This is because the MPI Install and Test Build occurred outside of the specified time window. The proper query should provide the time window and the upward dependencies of those results.

The problem is that this query becomes much more complex, but not impossible. For example we must consider the following cases: