public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
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	[thread overview]
Message-ID: <bug-113899-4-h4kH5zBtTT@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-113899-4@http.gcc.gnu.org/bugzilla/>

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

--- 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=113899#c3
> (Maybe the run testcases are failing but you might not be noticing that.), 
> 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 = 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.
> 
> Executing on ssh: mkdir -p /tmp/runtest.1880844   (timeout = 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.
> 
> 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.

      parent reply	other threads:[~2024-02-15  9:05 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-02-13  8:37 [Bug testsuite/113899] New: Vect module test failures while running on remote host sadineniharish8446 at gmail dot com
2024-02-13 21:04 ` [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 pinskia at gcc dot gnu.org
2024-02-13 21:46 ` pinskia at gcc dot gnu.org
2024-02-13 21:52 ` pinskia at gcc dot gnu.org
2024-02-14 13:41 ` cvs-commit at gcc dot gnu.org
2024-02-14 13:42 ` pinskia at gcc dot gnu.org
2024-02-15  8:55 ` sadineniharish8446 at gmail dot com
2024-02-15  9:05 ` pinskia at gcc dot gnu.org [this message]

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=bug-113899-4-h4kH5zBtTT@http.gcc.gnu.org/bugzilla/ \
    --to=gcc-bugzilla@gcc.gnu.org \
    --cc=gcc-bugs@gcc.gnu.org \
    /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).