Instead of making the default flag to the python command in the mpi call be
python -m mpi4py -m fv3gfs.run
I accidentally made it call
python -m mpi4py -m fv3config.fv3run.
This has the effect of infinitely recursing into fv3config I think. I also used
the wrong main module name in the tests. I don't believe this effects any
workflows, since it hasn't been incorporated in the master fv3gfs-python image
yet. Both changes should be fixed now.
Instead of making the default flag to the python command in the mpi call be
I accidentally made it call
This has the effect of infinitely recursing into fv3config I think. I also used the wrong main module name in the tests. I don't believe this effects any workflows, since it hasn't been incorporated in the master fv3gfs-python image yet. Both changes should be fixed now.