Skip to content

Releases: Goddard-Fortran-Ecosystem/pFUnit

Minor bug fixes

08 Nov 23:47
4f11470
Compare
Choose a tag to compare

There is a ticket opened against Intel Fortran 19.2 which breaks some
fHamcrest functionality. A failing test has been added to the test
suite. 19.1.3 still has this bug. (I have not checked if earlier
compilers also had this problem, but quite possibly they do as
fHamcrest is still under development.)

Changed

  • Separated tests related to RobustRunner into separate test suite. This is to
    facilitate CI, as the tests do intermittently fail under CI, though rarely
    in any development environment used by the main developers.

  • Corrected so that default flags are with aggressive debugging. This had been
    the default in the past, but was apparently lost for NAG to workaround a compiler
    bug in an intermediate release. Also corrected the way the flags are managed
    for Debug vs Release.

Fixed

  • Added workaround for NAG+cmake+OpenMP. An issue has been filed with kitware
    https://gitlab.kitware.com/cmake/cmake/-/issues/21280

  • Missing PRESENT checks for arguments in TestMethod. Not sure how
    these were not being caught - probably related to change mentioned
    above about skipping debug flags with NAG Fortran.

  • Missing RECURSIVE attribute on function in Every.F90. Not necessary
    in F2008, but not all compilers have implemented this yet.

Bug fixes for fhamcrest layer

22 Aug 23:48
9a8e225
Compare
Choose a tag to compare

Fixed

  • Problem with FHamcrest equal_to where when the expected value is a numeric
    array and the actual value is any type except a numeric array the test still
    passes, such as: @assert_that(1, is(equal_to([2, 3, 4]))) passes.

  • Problem with FHamcrest tests causing a segment fault when a test fails that
    involves a complex number.

Workaround for gfortran-10 strict MPI interfaces

05 Aug 13:12
9e3211e
Compare
Choose a tag to compare

Added compiler flag that allows GFortran 10.x to compile with argument mismatches
in MPI layer. This apparently is only an issue for some MPI flavors, with
others importing the correct interface variability via use mpi.

Minor workaround for WSL using gfortran

29 Jul 12:05
14f8d2e
Compare
Choose a tag to compare
v4.1.10

Update CMakeLists.txt

minor bugfix

02 Jun 12:11
e9df502
Compare
Choose a tag to compare

In the early CMake adoption, pFUnit introduced a "tests" target which has always worked. But a simple "make test" would fail to build some targets that were protected by EXCLUDE_FROM_ALL. This release fixes that discrepancy.

Workarounds for GFortran 10.1

18 May 15:04
019f780
Compare
Choose a tag to compare

GFortran 10.1 introduced a regression. Minor workarounds implemented.

Various items

06 Apr 21:02
608657a
Compare
Choose a tag to compare

Added

Changed

  • Fixed support for building shared libraries
  • Updated to latest submodules

Various bug fixes

06 Apr 02:44
0732763
Compare
Choose a tag to compare

Fixes for two bugs:

  • Corrected problem with cmake -DSKIP_FHAMCREST
  • Command line arguments not working with MPI

Fixed XML functionality

20 Dec 15:57
932130e
Compare
Choose a tag to compare
  • Added a command line option to activate XML
  • Updated external dependencies (bugfix in fArgParse)
  • Added "-v" short name for "--verbose" command line options
  • Updated travis

Another OpenMP fix

18 Dec 20:10
7910e98
Compare
Choose a tag to compare
  • Fix bug in exported pFUnit.mk file. Was not correctly expanding
    openmp libraries for projects built with Make.

  • Improved pFunit driver to avoid name conflicts with
    user defined initialize()