s filled in by LoadBuilds in the same file (i.e., when the results of a
> prior test build is loaded in from the dump file) and at the bottom of
> lib/MTT/Test/Build.pm::_do_build(), when the build has completed and it saves
> the results to the MTT:Test::builds hash.
>
>
>
egards,
On 11/5/10 9:01 AM, DongInn Kim wrote:
> Hi Josh,
>> Do you need to restart the FTB daemons before every test, or just start them
>> once before running an entire test suite?
> I believe that the daemon needs to run once before running an entire test
> set. Abhish
v' => undef,
'result_message' => 'Success',
'append_path' => undef,
'ftb_name' => undef,
'ftb_install_simple_section_name' => 'platform',
'test_result' => 1,
'description' => undef,
'exit_status' => 0,
Jeff, thank you.
BTW, I have looked at the ompi-core-perf-testing.ini file which seems to have
used the mpi detail sections and I tried to use it in our ftb.ini file but I
still get the same warning message.
*** Test Run phase starting
>> Test Run [ftb]
>> Running with [ftb-nightly-trunk] /
Get section?
>
> I believe that the mpi_details section is filled in via the MPI Get phase and
> then propagated down through all the other phases (i.e., each of the other
> phases looks a the way back to their corresponding mpi get phase to find
> the mpi_details value).
&