make check fails with error message "wrong values"

Bug #994038 reported by Jens Doleschal
12
This bug affects 2 people
Affects Status Importance Assigned to Milestone
ETSF_IO Library
New
Undecided
Unassigned

Bug Description

Hi,

during the build of abinit I run make check and for etsf i/o it fails at some points:

== | check 'atom_species_names' values Failed ==

     ***
     *** ETSF I/O ERROR
     ***
     *** Backtrace : check_mem_str_1D()
     *** Action performed : specifications variable
     *** Target (name) : atom_species_names
     *** Target (id) : -1
     *** Error message : wrong values
     ***

== | read 'chemical_symbols' values OK ==
== | check 'chemical_symbols' values Failed ==

     ***
     *** ETSF I/O ERROR
     ***
     *** Backtrace : check_mem_str_1D()
     *** Action performed : specifications variable
     *** Target (name) : chemical_symbols
     *** Target (id) : -1
     *** Error message : wrong values
     ***

== | read 'pseudopotential_types' values OK ==
== | check 'pseudopotential_types' values Failed ==

     ***
     *** ETSF I/O ERROR
     ***
     *** Backtrace : check_mem_str_1D()
     *** Action performed : specifications variable
     *** Target (name) : pseudopotential_types
     *** Target (id) : -1
     *** Error message : wrong values

Any ideas?

Best regards, Jens

Revision history for this message
Damien (damien-caliste) wrote : Re: [Bug 994038] [NEW] make check fails with error message "wrong values"

Hello,

Le 03/05/2012, Jens Doleschal <email address hidden> a écrit :
> Hi,
>
> during the build of abinit I run make check and for etsf i/o it fails
> at some points:
Ok, that's interesting and need correction. May I ask which compiler
are you using (I guess which version of GFortran is more accurate) ?
I'll try to reproduce and provide a correction.

Damien.

Revision history for this message
Jens Doleschal (jens-doleschal) wrote :

Hi Damien,

I used the open64 compiler in version 4.5.1 with the following flags:
-O3 -mtune=bdver1 -mso

Best regards, Jens

On May 16, 2012, at 10:43 AM, Damien Caliste wrote:

> Hello,
>
> Le 03/05/2012, Jens Doleschal <email address hidden> a écrit :
>> Hi,
>>
>> during the build of abinit I run make check and for etsf i/o it fails
>> at some points:
> Ok, that's interesting and need correction. May I ask which compiler
> are you using (I guess which version of GFortran is more accurate) ?
> I'll try to reproduce and provide a correction.
>
> Damien.

--
Dipl.-Math. Jens Doleschal
Wissenschaftlicher Mitarbeiter

Technische Universität Dresden
Zentrum für Informationsdienste und Hochleistungsrechnen (ZIH)
(Center for Information Services and High Performance Computing (ZIH))
Interdisziplinäre Anwenderunterstützung und Koordination (IAK)
(Interdisciplinary Application Development and Coordination (IAK))

Willersbau A109
Zellescher Weg 12
01062 Dresden

phone +49-351-463-35876
fax +49-351-463-37773
email <email address hidden>

Revision history for this message
David Strubbe (dstrubbe) wrote :

I would like to report that I found the same failures for 1.0.3 and 1.0.4 for the "Create file test_write_geometry.nc" and "Create file test_copy_geometry.nc" sections of the test, using g95 0.93 on MacOS with "-O3", and also with "-g -O0".

Revision history for this message
Nick Papior (nickpapior) wrote :

Just as David Strubbe, I get the exact same errors on my setup.
It seems like it is due to a too big string array in the tests_module. The passed variable is in consecutive memory, which doesn't follow the readed values.

If I correct the routine interface:
subroutine check_read_nD(ncid, varname, type, dims, lstat, error_data)
    ...
    character(len = 256), allocatable :: strings(:)

to:

subroutine check_read_nD(ncid, varname, type, dims, lstat, error_data)
    ...
    character(len = dims(1)), allocatable :: strings(:)

all tests pass.

I have attached a patch for completeness.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.