Skip to content
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

a collection of changes to ensure the fortran code compiles with gfortran v10.0 #23

Open
wants to merge 1 commit into
base: develop
Choose a base branch
from

Conversation

jdkloe
Copy link
Contributor

@jdkloe jdkloe commented Feb 29, 2020

Note that the code compiles but not all tests pass, so some additional work will be needed before this gfortran version can be used.

@FussyDuck
Copy link

FussyDuck commented Feb 29, 2020

CLA assistant check
All committers have signed the CLA.

@shahramn
Copy link
Collaborator

shahramn commented Jun 5, 2020

Dear Jos
Can you tell us precisely which tests fail?

@jdkloe
Copy link
Contributor Author

jdkloe commented Jun 8, 2020

Dear Jos
Can you tell us precisely which tests fail?

Sure. I see the following 4 tests fail after applying these patches and running the tests:

The following tests FAILED:
179 - eccodes_f_grib_copy_message (Failed)
180 - eccodes_f_bufr_copy_message (Failed)
198 - eccodes_f_read_message (Failed)
199 - eccodes_f_read_from_file (Failed)
Errors while running CTest

For your reference I also attached the logging output of the 4 test cases when I run them with extra verbosity like this:
ctest -VV -debug -R "eccodes_f_grib_copy_message|eccodes_f_bufr_copy_message|eccodes_f_read_message|eccodes_f_read_from_file" > log.txt 2>1
eccodes_2.15.0_failing_tests_gfortran_v10.txt.gz
Two of them show an ugly segmentation fault, and 2 others seem not ably to detect the 7777 code at the end of the grib message.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
3 participants