[MITgcm-devel] testreport and cross compiling

[Martin Losch]

Nice idea, I'll try that:

in the first round I give testreport a stupid command such as "ls -l  
mitgcmuv" and the second on I submit in a batch job with the real  
mpirun-command. I don't think any changes to testreport a required.

Martin
On 5 Feb 2008, at 01:55, Jean-Michel Campin wrote:

> Hi Martin,
>
> Just a vague idea: Would it be possible to run 2 times
> testreport:
> - 1rst time just to compile (would require an other option
>  to testreport, but seems relatively easy to add)
> - 2nd time with "-q" (-quick) to just run.
> This way, would be easy to start the 2nd testreport once the 1rst
> one is done (no sync problems), and you would be able to
> run all the tests with a single "qsub".
> Cheers,
> Jean-Michel
>
> On Mon, Feb 04, 2008 at 03:56:50PM +0100, Martin Losch wrote:
>> Hi there,
>>
>> I am trying to set up an automated testreport on our SX8. This
>> machine involves cross-compiling, so that I have to define some
>> command ./testreport -command "qsub runthemodel" where "runthemodel"
>> is the job-script that includes "mpirun -np 2 ./mitgcmuv".
>> Unfortunately, the script testreport does not wait until the model
>> run is finished, so that there is no output to compare. With the
>> queueing system PBS I can use "qsub -W block=true" to achieve that
>> the  calling script waits.
>> Does anyone know of a similar option for NQSII (which is the queueing
>> system on SX8), or do you have another practical solution for running
>> testreport on a machine which requires cross compiling?
>>
>> Martin
>>
>> _______________________________________________
>> MITgcm-devel mailing list
>> MITgcm-devel at mitgcm.org
>> http://mitgcm.org/mailman/listinfo/mitgcm-devel
> _______________________________________________
> MITgcm-devel mailing list
> MITgcm-devel at mitgcm.org
> http://mitgcm.org/mailman/listinfo/mitgcm-devel