call set_netcdf_env_vars in prepare_step rather than configure_step in WRF easyblock#746
Conversation
|
@wpoely86: please review? |
|
Easyblocks unit test suite PASSed (see https://jenkins1.ugent.be/job/easybuild-easyblocks-pr-builder/1373/console for more details). This pull request is now ready for review/testing. Please try and find someone who can tackle this; contact @boegel if you're not sure what to do. |
|
looks good |
|
Thanks for the review @wpoely86! |
call set_netcdf_env_vars in prepare_step rather than configure_step in WRF easyblock
|
Hmm, unit tests are broken after this got merged: The fail makes sense (and I can reproduce it locally), but I'm not sure why the PR tester didn't pick up on this... |
|
Jenkins: test this please |
|
Problem with test not failing when it should be was caused by the |
This change makes the WRF module generated using
--module-only --forceactually useable.Without this, the WRF module would contains
setenv NETCDF None, since the$NETCDF*environment variables do not get defined when using--module-onlybecauseconfigure_stepis skipped.