Errors when running CICE test suite on Travis-CI about cice

[eclare108213]

We found with Icepack that some compilers that we didn't regularly run with turn up issues like this. Can you tell which compiler and configuration is crashing? And which line it's crashing on? It's likely that some of the things we fixed in the Icepack driver have not yet been fixed in CICE - we need to identify those and get them fixed.... I'll look back through the Icepack PRs for this kind of thing.

[eclare108213]

I looked through the Icepack PRs, and nothing jumped out at me. Most of the bug fixes were within the column physics modules themselves or the forcing, which is different from CICE's. There could be a missing parameter initialization... we'll need to debug specific cases.

Thank you, I will dig out some more information and report back.

I can reproduce this bug from my local machine and the CICE master branch by running the base_suite with the loft/gnu environment:

csh cice.setup --suite base_suite --testid travisCItest --mach loft --env gnu 

It turns out that the Division by 0 error message is cast by line 21 of configuration/scripts/cice.batch.sh. The variable $taskpernode evaluates to zero as maxtpn = 1 and nthrds = 2.

I can mitigate this behavior by setting setenv ICE_MACHINE_TPNODE 2 (instead of 1) in the environment file. However, I didn't do this for Icepack.

EDIT:
See the travis build log when ICE_MACHINE_TPNODE = 2. Some tests seem to pass, while others fail, again due to Division by 0 errors related to $taskpernode. I invoked configuration/scripts/cice.batch.sh in verbose mode.

@apcraig, @eclare108213 Could you please check if the following command runs on your system and the master branch of CICE?

./cice.setup --suite base_suite --testid travisCItest --mach loft --env gnu

I am not sure I am qualified to mess with configuration/scripts/cice.settings. Thanks!

I suggest we continue the conversation in #111, where we can work directly on the code.