public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "ro at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug go/48121] New: websocket and netchan test occasionally fail with EISCONN
Date: Mon, 14 Mar 2011 19:55:00 -0000	[thread overview]
Message-ID: <bug-48121-4@http.gcc.gnu.org/bugzilla/> (raw)

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=48121

           Summary: websocket and netchan test occasionally fail with
                    EISCONN
           Product: gcc
           Version: 4.6.0
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: go
        AssignedTo: ian@airs.com
        ReportedBy: ro@gcc.gnu.org
              Host: i386-pc-solaris2.11
            Target: i386-pc-solaris2.11
             Build: i386-pc-solaris2.11


With your last patches, libgo testsuite results are almost clean on Solaris
11/x86
(thanks!).  There are two new failures, though:

/bin/ksh: line 1: 2594: Abort
FAIL: websocket
2011/03/12 14:46:29 Test WebSocket server listening on 127.0.0.1:54884
panic: Dial failed: websocket.Dial ws://127.0.0.1:54884/echo: dial tcp
127.0.0.1:54884: Transport endpoint is already connected
/vol/gcc/src/hg/trunk/solaris/libgo/testsuite/gotest: line 318: 2962: Abort
make: *** [websocket/check] Error 1

FAIL: netchan
2011/03/12 14:50:46 netchan export: error decoding client header:EOF
2011/03/12 14:50:46 netchan export: sending error to client:no such channel:
notAChannel
2011/03/12 14:50:46 netchan import: response error:no such channel: notAChannel
--- FAIL: netchan.TestCrossConnect
    new importer: dial tcp 127.0.0.1:55598: Transport endpoint is already
connected
FAIL
make[2]: *** [netchan/check] Error 1

The errors happen only occasionally, though.


             reply	other threads:[~2011-03-14 19:55 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-03-14 19:55 ro at gcc dot gnu.org [this message]
2011-04-04 23:57 ` [Bug go/48121] " ian at airs dot com

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-48121-4@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).