-
Notifications
You must be signed in to change notification settings - Fork 128
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Suspicous history writing errors with pgi #117
Comments
Debug runs with PGI include the |
If you want to add a PGI build to CI, I have a script at https://github.com/nemequ/pgi-travis which should make it pretty easy. |
@nemequ, cool, thanks for sharing! |
Unfortunately,Intel changed how their license server works after I wrote that. Now you can only have (IIRC) 5 active installations, and the only way to deactivate an installation is to log into their web site and manually remove it (i.e., we can't just uninstall the compiler after everything else is done). Unless you want to log in to Intel's web site every few builds you'll end up with build failures from Travis. I've pretty much stopped maintaining that repo since the change. |
I am not seeing this problem anymore. We have updated some of the pgi compiler options over the last few months among other things. I'm going to mark it wontfix and close it. |
We are getting errors in a limited number of test cases and machines,
conrad_pgi_smoke_gx3_1x2_debug_diag1_run5day
conrad_pgi_smoke_gx3_2x1_debug_diag1_run5day
throws this error,
0: Null pointer for a2d (/p/home/apcraig/cice-consortium/cice.travis/cicecore/cicedynB/analysis/ice_history.F90: 1344)
but the following non-debug runs pass
PASS conrad_pgi_smoke_gx3_1x2_diag1_run5day run
PASS conrad_pgi_smoke_gx3_1x1_diag1_run5day_thread run
PASS conrad_pgi_smoke_gx3_2x1_diag1_run5day_thread run
PASS conrad_pgi_restart_gx3_2x1_diag1 exact-restart
PASS conrad_pgi_restart_gx3_1x2_diag1 exact-restart
PASS conrad_pgi_restart_gx3_2x1_diag1_pondcesm exact-restart
PASS conrad_pgi_restart_gx3_2x1_diag1_pondtopo exact-restart
Not seeing this problem with other compilers. It could be pgi but we should look into it.
The text was updated successfully, but these errors were encountered: