From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 102878 invoked by alias); 22 Feb 2018 00:36:59 -0000 Mailing-List: contact fortran-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Post: List-Help: , Sender: fortran-owner@gcc.gnu.org Received: (qmail 102855 invoked by uid 89); 22 Feb 2018 00:36:58 -0000 Authentication-Results: sourceware.org; auth=none X-Virus-Found: No X-Spam-SWARE-Status: No, score=-1.9 required=5.0 tests=BAYES_00,HTML_MESSAGE,RCVD_IN_DNSWL_NONE,SPF_PASS autolearn=ham version=3.3.2 spammy=Hx-languages-length:4516, H*c:alternative, H*c:HHH X-HELO: mail-pf0-f169.google.com Received: from mail-pf0-f169.google.com (HELO mail-pf0-f169.google.com) (209.85.192.169) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with ESMTP; Thu, 22 Feb 2018 00:36:56 +0000 Received: by mail-pf0-f169.google.com with SMTP id 68so1398431pfx.3 for ; Wed, 21 Feb 2018 16:36:56 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:date:from:to:cc:message-id:in-reply-to :references:subject:mime-version; bh=i7+Vv+q4OoPqX4RbUBQGHGD7Ubwe01gFLryD2Kbmj3k=; b=KtRPddWTI0qkbjmjjTtprye+E5ZbuIPgP10oK9psH3zd2bPzQjdqGvwGuV81jVtxGu yJ0Q57cmkVMo1txz3C+7im1e7YCrha1BQ69qLf8YYEgpQqgtm11tGnBgFvYEcxVs4m7C sFvXuQ7B+W1yqvrGYQtgNYUrUnxPYphaHQXAvd7k1D2RHIGQZSHxahjusJ054/AsQl1F IgnzNLhhvETLjS740wxE6qrbi1oKrWbwNzs2xUrS/4U+Ay3tnsdPtvOQADPz+AEeAp8S cDrj2n8pXZvBQvD8DCFLk7+jdktsdqfPxKOwS6jaWU3dcBDK3+Oqc9RckrAcQemAITnP DlLA== X-Gm-Message-State: APf1xPDWpspqWwYRAnkO3G2lIVJD6Wc8sRvsvUvDNxkyVyL9ICcmYK2g 76KcyepfWm4aZWebmFSxP3Ex0g== X-Google-Smtp-Source: AH8x226iKPZQ21xmGuN/EFaTj5aTRzTKqgcvHTGkw7qGbfOTTDMQSOU//xyf/Eg+HANtCfZGFguTjQ== X-Received: by 10.99.148.17 with SMTP id m17mr4112505pge.367.1519259814867; Wed, 21 Feb 2018 16:36:54 -0800 (PST) Received: from localhost.mail ([2600:1010:b014:59c:444e:c832:29f9:bb9f]) by smtp.gmail.com with ESMTPSA id y124sm15673492pgb.29.2018.02.21.16.36.52 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Wed, 21 Feb 2018 16:36:53 -0800 (PST) Date: Thu, 22 Feb 2018 00:36:00 -0000 From: Damian Rouson To: Janne Blomqvist Cc: Andre Vehreschild , "=?utf-8?Q?Izaak=40izaakbeekman.com?=" , Fortran List , Alessandro Fanfarillo , GCC Patches Message-ID: In-Reply-To: References: <1518192646-9702-1-git-send-email-blomqvist.janne@gmail.com> Subject: Re: [PATCH] Character length cleanup for Coarray Fortran library MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Disposition: inline Content-Transfer-Encoding: quoted-printable X-IsSubscribed: yes X-SW-Source: 2018-02/txt/msg00152.txt.bz2 Hi Janne, To be more specific, the new OpenCoarrays test failures after applying the = patch are the following ones: =C2=A0image_fail_test_1 (Timeout) =C2=A0image_fail_and_sync_test_2 (Timeout) =C2=A0image_fail_and_sync_test_3 (Timeout) =C2=A0image_fail_and_get_test_1 (Timeout) There are four. =C2=A0I was mistaken when I wrote that there are three. Damian On February 21, 2018 at 12:56:05 PM, Janne Blomqvist (blomqvist.janne@gmail= .com) wrote: On Wed, Feb 21, 2018 at 10:18 PM, Damian Rouson=20=20 wrote:=20=20 >=20=20 >=20=20 >=20=20 >=20=20 > On February 21, 2018 at 11:35:47 AM, Janne Blomqvist (blomqvist.janne@gma= il.com(mailto:blomqvist.janne@gmail.com)) wrote:=20=20 >=20=20 >> PING=20=20 >>=20=20 >> Is anybody planning to work on this on the opencoarrays side? Or do=20=20 >> you prefer that this is just committed and you can sort it out on your= =20=20 >> own schedule?=20=20 >=20=20 > Hi Janne,=20=20 >=20=20 > The trunk didn=E2=80=99t build for me the first time I tried soon after y= our initial email and it took me until yesterday to find time to try again.= Once I succeeded, the patch created three new test failures. I=E2=80=99m w= ondering if Andre=E2=80=99s recent patch (r257813) helped reduce the number= . All new failures involve the failed-images features developed by Alessand= ro and Andre, both of whom now have new employment or contracts that preven= t making significant contributions to OpenCoarrays (although I hope that wi= ll change and am working with Alessandro=E2=80=99s organization to attempt = to get some of his time allocated to gfortran/OpenCoarrays development).=20= =20 >=20=20 > I think the most sustainable path forward is for me to assist any interes= ted gfortran developer in building OpenCoarrays on your local system and ru= nning the test suite. At least that eliminates the reliance on OpenCoarrays= developers to run the tests every time a patch impacts OpenCoarrays. If we= can work together on building OpenCoarrays on your system, we can also loo= k together at the requisite changes to see if we can eliminate the failures= .=20=20 >=20=20 > Oxford University Ph.D. student Daniel Garza visit Sourcery Institute Mar= ch 17 - June 2 to integrate the building of OpenCoarrays into the GCC build= system so I hope this will all be easier sooner.=20=20 Ok, I'll see if I find the time to get opencoarrays built.=20=20 --=20=20 Janne Blomqvist=20=20