because the results are rendered in chunks during reporting phase. (100 pieces every flush) This caused same benchmark line to appear more then once in the final report.
You can configure the reporter to issue results not by number, but for same benchmark at once: put this in the ini file: [MTT] submit_group_results=1 Also, html report is nicer and allows you easy navigation to the errors regards Mike 2009/3/19 Jeff Squyres <jsquy...@cisco.com> > I got a fairly odd mtt text report (it's super wide, sorry): > > | Test Run | intel | 1.3.1rc5 | 00:12 | 5 | | > | | Test_Run-intel-developer-1.3.1rc5.html | > | Test Run | intel | 1.3.1rc5 | 02:59 | 101 | | > | | Test_Run-intel-developer-1.3.1rc5.html | > | Test Run | intel | 1.3.1rc5 | 03:08 | 101 | | > | | Test_Run-intel-developer-1.3.1rc5.html | > | Test Run | intel | 1.3.1rc5 | 02:51 | 101 | | > | | Test_Run-intel-developer-1.3.1rc5.html | > | Test Run | intel | 1.3.1rc5 | 02:59 | 101 | | > | | Test_Run-intel-developer-1.3.1rc5.html | > | Test Run | intel | 1.3.1rc5 | 03:48 | 101 | | > | | Test_Run-intel-developer-1.3.1rc5.html | > | Test Run | intel | 1.3.1rc5 | 03:10 | 101 | | > | | Test_Run-intel-developer-1.3.1rc5.html | > | Test Run | intel | 1.3.1rc5 | 03:05 | 101 | | > | | Test_Run-intel-developer-1.3.1rc5.html | > | Test Run | intel | 1.3.1rc5 | 03:09 | 101 | | > | | Test_Run-intel-developer-1.3.1rc5.html | > | Test Run | intel | 1.3.1rc5 | 03:25 | 101 | | > | | Test_Run-intel-developer-1.3.1rc5.html | > | Test Run | intel | 1.3.1rc5 | 02:46 | 101 | | > | | Test_Run-intel-developer-1.3.1rc5.html | > | Test Run | intel | 1.3.1rc5 | 02:59 | 101 | | > | | Test_Run-intel-developer-1.3.1rc5.html | > | Test Run | intel | 1.3.1rc5 | 03:23 | 101 | | > | | Test_Run-intel-developer-1.3.1rc5.html | > | Test Run | intel | 1.3.1rc5 | 02:50 | 100 | 1 | > | | Test_Run-intel-developer-1.3.1rc5.html | > | Test Run | intel | 1.3.1rc5 | 02:56 | 101 | | > | | Test_Run-intel-developer-1.3.1rc5.html | > | Test Run | intel | 1.3.1rc5 | 02:53 | 101 | | > | | Test_Run-intel-developer-1.3.1rc5.html | > | Test Run | intel | 1.3.1rc5 | 03:22 | 101 | | > | | Test_Run-intel-developer-1.3.1rc5.html | > | Test Run | intel | 1.3.1rc5 | 04:21 | 100 | | > 1 | | Test_Run-intel-developer-1.3.1rc5.html | > | Test Run | intel | 1.3.1rc5 | 04:12 | 101 | | > | | Test_Run-intel-developer-1.3.1rc5.html | > | Test Run | intel | 1.3.1rc5 | 03:36 | 101 | | > | | Test_Run-intel-developer-1.3.1rc5.html | > | Test Run | intel | 1.3.1rc5 | 02:48 | 101 | | > | | Test_Run-intel-developer-1.3.1rc5.html | > | Test Run | intel | 1.3.1rc5 | 02:47 | 101 | | > | | Test_Run-intel-developer-1.3.1rc5.html | > | Test Run | intel | 1.3.1rc5 | 03:08 | 101 | | > | | Test_Run-intel-developer-1.3.1rc5.html | > | Test Run | intel | 1.3.1rc5 | 02:57 | 101 | | > | | Test_Run-intel-developer-1.3.1rc5.html | > | Test Run | intel | 1.3.1rc5 | 02:43 | 101 | | > | | Test_Run-intel-developer-1.3.1rc5.html | > | Test Run | intel | 1.3.1rc5 | 02:48 | 101 | | > | | Test_Run-intel-developer-1.3.1rc5.html | > > Notice that there are *many* "intel" lines, each with 101 passes. The only > difference between them is the times that they ran -- but there's even > repeats of that. > > Do we know why there is so many different lines for the intel test suite? > > Did this get changed in the text reporter changes from Voltaire (somewhat) > recently? > > -- > Jeff Squyres > Cisco Systems > > _______________________________________________ > mtt-devel mailing list > mtt-de...@open-mpi.org > http://www.open-mpi.org/mailman/listinfo.cgi/mtt-devel >
