[NeXus-code-tickets] [NeXusCode] #68: Failure of Absoft Fortran 90

[NeXus Data Format Library and Applications]

#68: Failure of Absoft Fortran 90
-------------------------+--------------------------------------------------
  Reporter:  Ray Osborn  |       Owner:  Freddie Akeroyd
      Type:  defect      |      Status:  assigned       
  Priority:  major       |   Milestone:  NeXus 4.1      
 Component:  napi        |     Version:  4.0rc3         
Resolution:              |    Keywords:                 
-------------------------+--------------------------------------------------
Comment (by Ray Osborn):

 Replying to [comment:14 Freddie Akeroyd]:
 > The failure in testsuite.log is:
 > {{{
 > 9. testsuite.at:373: testing ...
 > testsuite.at:407:  $HAVE_F90 && $HAVE_HDF5 && $SETUP_TEST && NXtest |
 sed -e 's/\r$//'
 > --- - 2007-05-24 09:25:42.000000000 -0400
 > +++ /Users/roadmin/Desktop/nexus-4.0_branch_r938/test/testsuite.dir/at-
 stdout 2007-05-24 09:25:42.000000000 -0400
 > @@ -26,7 +26,7 @@
 >            :   17.0000000  18.0000000  19.0000000  20.0000000
 >     ch_attribute : NeXus
 >     i4_attribute :       42
 > -   r4_attribute :    3.1415927
 > +   r4_attribute :    3.1415930
 >     target : /entry/r8_data
 >     Subgroup: sample(NXsample)
 >  Link Check OK
 > 9. testsuite.at:373: 9. Check the F90 binding using HDF5.
 (testsuite.at:373): FAILED (testsuite.at:407)
 > }}}
 > It appears reading and writing of a r4 attribute has a precision
 problem. Given that both an r4_array and an r8_array have passed OK, i
 think it is an issue with how this test is constructed. Fixing it,
 however, would require us to re-run all f90 tests on our systems and so is
 probably too risky to do now. I'll add a comment to the release notes and
 go for 4.0.0 as is

 That's fine by me.

 Ray

-- 
Ticket URL: <http://trac.nexusformat.org/code/ticket/68#comment:15>
NeXus Data Format Library and Applications <http://www.nexusformat.org/>
NeXus Data Format Library and Applications