https://gcc.gnu.org/bugzilla/show_bug.cgi?id=121043

Jerry DeLisle <jvdelisle at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
   Last reconfirmed|                            |2025-07-13
     Ever confirmed|0                           |1
             Status|UNCONFIRMED                 |NEW

--- Comment #3 from Jerry DeLisle <jvdelisle at gcc dot gnu.org> ---
There are a series of patches involved here.

The first failure occurs at:

commit 1be1970f97d05a07851cd826132fcf466827ebe5
Author: Andre Vehreschild <ve...@gcc.gnu.org>
Date:   Fri Mar 14 14:20:18 2025 +0100

    Fortran: Unify handling of STAT= and ERRMSG= optional arguments [PR87939]

The failure is:

      Start 23: sync_team
23/88 Test #23: sync_team
.............................................***Failed  Required regular
expression not found. Regex=[Test passed.
]  0.47 sec

After the following patch, the tests hang ...

commit 8f4ee36bd5248cd244f65282167e3a13a3c98bc2
Author: Andre Vehreschild <ve...@gcc.gnu.org>
Date:   Mon Apr 7 09:36:24 2025 +0200

    Fortran: Improve F2018 TEAM handling [PR87326, PR87556, PR88254, PR103896]

    Improve the implementation of F2018 TEAM handling routines. Add
    runtime-functions to caf_single to allow testing.

            PR fortran/87326
            PR fortran/87556
            PR fortran/88254
            PR fortran/103796

... here:

Test project /home/jerry/dev/opencoarrays-clean
      Start  1: initialize_mpi
 1/88 Test  #1: initialize_mpi ........................................  
Passed    0.42 sec
      Start  2: register
 2/88 Test  #2: register ..............................................  
Passed    0.42 sec
      Start  3: register_vector
 3/88 Test  #3: register_vector .......................................  
Passed    0.42 sec
      Start  4: register_alloc_vector
^Cmake: *** [Makefile:71: test] Interrupt

... and this blocks testing of the new -lcaf_shmem patches that are in review.

Reply via email to