From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <gcc-bugzilla@gcc.gnu.org>
Received: by sourceware.org (Postfix, from userid 48)
	id 13DCE386184F; Thu, 15 Feb 2024 09:05:46 +0000 (GMT)
DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 13DCE386184F
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org;
	s=default; t=1707987946;
	bh=PJsu2t8fLBAvP42LXLHMIGuMS4bBwDC8RQAPyelGrJM=;
	h=From:To:Subject:Date:In-Reply-To:References:From;
	b=JGjxB1nbSOGwxvnbxbsub1ptYDhft7Y6+FDPhM0//Ob38Jy3AJrr1qWcgQNJjjmuF
	 0qBNYRE63g/LmZIj6FRy7nWm/Vw8O883oxIjO8q8YwlkQVsiRIm+8LXDtOTQ1qFS22
	 pL0F4800I157+bU3RpLf8P5QU1MX0KMVs7O6tWUY=
From: "pinskia at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug testsuite/113899] Vect module test failures while running on
 remote host due to default dg-do set to compile and additional-sources being
 used
Date: Thu, 15 Feb 2024 09:05:44 +0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: testsuite
X-Bugzilla-Version: 13.2.0
X-Bugzilla-Keywords: testsuite-fail
X-Bugzilla-Severity: normal
X-Bugzilla-Who: pinskia at gcc dot gnu.org
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Resolution: FIXED
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: pinskia at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 14.0
X-Bugzilla-Flags: 
X-Bugzilla-Changed-Fields: 
Message-ID: <bug-113899-4-h4kH5zBtTT@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-113899-4@http.gcc.gnu.org/bugzilla/>
References: <bug-113899-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
List-Id: <gcc-bugs.sourceware.org>

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

--- Comment #7 from Andrew Pinski <pinskia at gcc dot gnu.org> ---
(In reply to sadineniharish8446 from comment #6)
> Also as you said in https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D113899=
#c3
> (Maybe the run testcases are failing but you might not be noticing that.)=
,=20
> I have gone through summary file and i checked a few 'dg-do run' tests and
> those were marked as unresolved. We have observed some failure from the
> gcc.log as below,
> Executing on ssh: mkdir -p /tmp/runtest.3549458   (timeout =3D 300)
> spawn [open ...]^M
> kex_exchange_identification: read: Connection reset by peer^M
> Connection reset by 192.168.7.2 port 22^M
> ERROR: Couldn't create remote directory /tmp/runtest.3549458 on ssh
> Download of ./sse_hw_available3549458.exe to ssh failed.
>=20
> Executing on ssh: mkdir -p /tmp/runtest.1880844   (timeout =3D 300)
> spawn [open ...]^M
> Host key verification failed.^M
> ERROR: Couldn't create remote directory /tmp/runtest.1880844 on ssh
> Download of ./sse2_hw_available1880844.exe to ssh failed.
>=20
> what could be the reason for this and how can we fix this? .

Well it is ssh that is failing so you need to check why ssh to the host is =
no
longer working. Note one trick is to use one ssh connection but multiple
sessions which should speed up things.  See
https://tutonics.com/articles/allow-multiple-ssh-sessions-over-an-existing-=
connection/
for more info on that.=