From: Steve Kargl <sgk@troutmask.apl.washington.edu>
To: Thomas Koenig <tkoenig@netcologne.de>
Cc: fortran@gcc.gnu.org, kargl@gcc.gnu.org
Subject: Re: co-arrays and libgfortran
Date: Tue, 22 Dec 2020 12:12:02 -0800 [thread overview]
Message-ID: <20201222201202.GA77441@troutmask.apl.washington.edu> (raw)
In-Reply-To: <20201222193325.GA16717@troutmask.apl.washington.edu>
On Tue, Dec 22, 2020 at 11:33:25AM -0800, Steve Kargl wrote:
>
> I started the make check command. I'm see a few failures
> of the form
>
> WARNING: program timed out.
> FAIL: gfortran.dg/caf-shared/dummy_1.f90 -pthread -fcoarray=shared \
> -O2 -lcaf_shared -lrt execution test
>
> I'll send more info once the checking completes.
>
Poking around.
% ps
3491 3 I+ 0:00.91 gmake check-fortran RUNTESTFLAGS=cas.exp=*.f*
3576 3 I+ 0:00.87 gmake TESTSUITEDIR=testsuite RUNTESTFLAGS=cas.exp=*.f* check_gfortran_pa
3660 3 I+ 0:00.00 /bin/sh -c (rootme=`${PWDCMD-pwd}`; export rootme; \\\nsrcdir=`cd ../../
3670 3 I+ 0:01.04 expect -- /usr/local/share/dejagnu/runtest.exp --tool gfortran cas.exp=*
3726 3 I+ 0:00.00 ./alloc_coarray_with_source_1.exe (alloc_coarray_with_)
3727 3 I+ 0:00.00 ./alloc_coarray_with_source_1.exe (alloc_coarray_with_)
3728 3 I+ 0:00.00 ./alloc_coarray_with_source_1.exe (alloc_coarray_with_)
3751 3 I+ 0:00.00 ./alloc_comp_1.exe
3786 3 I+ 0:00.00 ./arg_passing_1.exe
3787 3 I+ 0:00.00 ./arg_passing_1.exe
3788 3 I+ 0:00.00 ./arg_passing_1.exe
3807 3 I+ 0:00.00 ./assign_array_1.exe
3826 3 I+ 0:00.00 ./atomic_1.exe
3827 3 I+ 0:00.00 ./atomic_1.exe
3828 3 I+ 0:00.00 ./atomic_1.exe
3884 3 I+ 0:00.00 ./cobounds_torture_1.exe (cobounds_torture_1.)
3912 3 I+ 0:00.00 ./cobounds_torture_2.exe (cobounds_torture_2.)
3931 3 I+ 0:00.00 ./cobounds_torture_3.exe (cobounds_torture_3.)
4014 3 I+ 0:00.00 ./cosubscript_1.exe
4015 3 I+ 0:00.00 ./cosubscript_1.exe
4016 3 I+ 0:00.00 ./cosubscript_1.exe
4037 3 I+ 0:00.00 ./dummy_1.exe
4069 3 I+ 0:00.00 ./get_array.exe
4070 3 I+ 0:00.00 ./get_array.exe
4071 3 I+ 0:00.00 ./get_array.exe
4144 3 I+ 0:00.00 ./image_index_2.exe
4145 3 I+ 0:00.00 ./image_index_2.exe
4146 3 I+ 0:00.00 ./image_index_2.exe
4176 3 I+ 0:00.00 ./lower_cobound_1.exe
4177 3 I+ 0:00.00 ./lower_cobound_1.exe
4178 3 I+ 0:00.00 ./lower_cobound_1.exe
...
Looks like something is stuck in a deadlock.
--
Steve
next prev parent reply other threads:[~2020-12-22 20:12 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-18 4:28 Steve Kargl
2020-12-18 12:26 ` Thomas Koenig
2020-12-18 15:52 ` Steve Kargl
2020-12-19 21:59 ` Steve Kargl
2020-12-20 10:52 ` Thomas Koenig
2020-12-20 17:47 ` Steve Kargl
2020-12-21 1:04 ` Steve Kargl
2020-12-21 2:01 ` Damian Rouson
2020-12-21 13:15 ` Thomas Koenig
2020-12-21 15:18 ` Steve Kargl
2020-12-21 23:44 ` Thomas Koenig
2020-12-22 0:18 ` Steve Kargl
2020-12-22 1:40 ` Steve Kargl
2020-12-22 10:04 ` Thomas Koenig
2020-12-22 18:32 ` Steve Kargl
2020-12-22 19:33 ` Steve Kargl
2020-12-22 20:12 ` Steve Kargl [this message]
2020-12-22 20:20 ` Steve Kargl
2020-12-22 22:08 ` Steve Kargl
2020-12-22 22:22 ` Steve Kargl
2020-12-22 23:24 ` Steve Kargl
2020-12-22 23:46 ` Thomas Koenig
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20201222201202.GA77441@troutmask.apl.washington.edu \
--to=sgk@troutmask.apl.washington.edu \
--cc=fortran@gcc.gnu.org \
--cc=kargl@gcc.gnu.org \
--cc=tkoenig@netcologne.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).