public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: "Lynn A. Boger" <laboger@linux.vnet.ibm.com>
To: Ian Lance Taylor <iant@golang.org>, Uros Bizjak <ubizjak@gmail.com>
Cc: "gcc-patches@gcc.gnu.org" <gcc-patches@gcc.gnu.org>,
	       "gofrontend-dev@googlegroups.com"
	<gofrontend-dev@googlegroups.com>
Subject: Re: libgo patch committed: Update to Go 1.5 release
Date: Tue, 03 Nov 2015 15:48:00 -0000	[thread overview]
Message-ID: <5638D737.8050303@linux.vnet.ibm.com> (raw)
In-Reply-To: <CAOyqgcXg+4i2ZpcpC5h=6bQ5-s44N3CsEED0kvpL8X_d7+sWuw@mail.gmail.com>

We are seeing failures on all the libgo tests when gccgo is built with 
the latest trunk
on ppc64 (BE) and when running the testsuite for 64 bit.  The failures
do not occur if run on ppc64 BE with m32 and do not occur on ppc64le.

The messages say this:

make[3]: Entering directory 
`/home/boger/gccgo.work/trunk/bld/powerpc64-linux/libgo'
gotest: warning: no tests matching Test([^a-z].*)? in _gotest_.o _xtest_.o
FAIL: bufio
make[3]: *** [bufio/check] Error 1
gotest: warning: no tests matching Test([^a-z].*)? in _gotest_.o _xtest_.o
FAIL: bytes
make[3]: *** [bytes/check] Error 1
gotest: warning: no tests matching Test([^a-z].*)? in _gotest_.o _xtest_.o
FAIL: errors

......  same message for all

On 11/03/2015 09:07 AM, Ian Lance Taylor wrote:
> On Mon, Nov 2, 2015 at 11:48 PM, Uros Bizjak <ubizjak@gmail.com> wrote:
>>> I have committed a patch to libgo to update it to the Go 1.5 release.
>>>
>>> As usual for libgo updates, the actual patch is too large to attach to
>>> this e-mail message.  I've attached the changes to the gccgo-specific
>>> files.
>>>
>>> Bootstrapped and ran Go testsuite on x86_64-pc-linux-gnu.  Committed
>>> to mainline.
>>>
>>> This may cause trouble on non-GNU/Linux operating systems.  Please let
>>> me know about any problems you encounter.
>> There is one new testsuite failure on CentOS 5.11 (kernel 2.6.18),
>> where namespaces are not supported:
>>
>> exec_linux_test.go:29:23: error: reference to undefined identifier
>> 'syscall.CLONE_NEWUSER'
>>     Cloneflags: syscall.CLONE_NEWUSER,
>>                         ^
>> FAIL: syscall
>>
>> The test would be skipped, since "/proc/self/ns/user" doesn't exist,
>> however, the test doesn't compile due to missing CLONE_NEWUSER define.
> Thanks.  I committed this patch which should fix the problem.
>
> Ian

  reply	other threads:[~2015-11-03 15:48 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-11-03  7:48 Uros Bizjak
2015-11-03 15:07 ` Ian Lance Taylor
2015-11-03 15:48   ` Lynn A. Boger [this message]
2015-11-03 17:34     ` Ian Lance Taylor
2015-11-03 20:17       ` Lynn A. Boger
2015-11-04  1:53         ` Ian Lance Taylor
2015-11-03 22:14       ` Andreas Schwab
  -- strict thread matches above, loose matches on Subject: below --
2015-10-31  3:35 Ian Lance Taylor
2015-11-01  8:40 ` Andreas Schwab
2015-11-01 20:33   ` Ian Lance Taylor
2015-11-01 20:52   ` Ian Lance Taylor
2015-11-02  9:38     ` Andreas Schwab
2015-11-02 15:40       ` Lynn A. Boger
2015-11-02 20:23         ` Ian Lance Taylor
2015-11-02 20:59           ` Lynn A. Boger
2015-11-02 19:58       ` Ian Lance Taylor
2015-11-06 13:01 ` Rainer Orth
2015-11-06 19:16   ` Ian Lance Taylor
2015-11-08 17:21     ` Rainer Orth
2015-11-10 21:39       ` Ian Lance Taylor
2015-11-11 11:48         ` Rainer Orth
2015-11-11 13:25           ` Ian Lance Taylor

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=5638D737.8050303@linux.vnet.ibm.com \
    --to=laboger@linux.vnet.ibm.com \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=gofrontend-dev@googlegroups.com \
    --cc=iant@golang.org \
    --cc=ubizjak@gmail.com \
    /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).