From: Uros Bizjak <ubizjak@gmail.com>
To: "gcc-patches@gcc.gnu.org" <gcc-patches@gcc.gnu.org>
Cc: Ian Taylor <iant@golang.org>,
"gofrontend-dev@googlegroups.com"
<gofrontend-dev@googlegroups.com>
Subject: Re: gotools patch committed: Test runtime, misc/cgo/{test,testcarchive}
Date: Sat, 22 Jul 2017 18:08:00 -0000 [thread overview]
Message-ID: <CAFULd4bgd_YPe+yp2bwy5ShTLq4C78xeJ3_99o=+w5oFTFThDQ@mail.gmail.com> (raw)
> This patch to the gotools Makefile adds tests to `make check`. We now
> test the runtime package using the newly built go tool, and test that
> cgo works by running the misc/cgo/test and misc/cgo/testcarchive
> tests. Bootstrapped and ran Go testsuite on x86_64-pc-linux-gnu.
> Committed to mainline.
There is now only one remaining gotools testsuite failure on alpha:
FAIL: TestBreakpoint
crash_test.go:106: testprog Breakpoint exit status: exit status 2
crash_test.go:310: output:
SIGTRAP: trace trap
PC=2199039253124 m=0 sigcode=0
goroutine 1 [running]:
goroutine 3 [runnable]:
created by runtime.SetFinalizer
/space/homedirs/uros/gcc-svn/trunk/libgo/go/runtime/mfinal.go:355
+1280
want output containing: runtime.Breakpoint
I would like to debug this one failure only. Is there a way to run
only one gotools test? Can you perhaps give a hint where to look in
the source?
Uros.
next reply other threads:[~2017-07-22 18:08 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-22 18:08 Uros Bizjak [this message]
2017-07-26 20:27 ` Ian Lance Taylor
2017-08-04 10:54 ` Uros Bizjak
2017-08-04 13:46 ` Ian Lance Taylor
2017-08-14 8:27 ` Uros Bizjak
-- strict thread matches above, loose matches on Subject: below --
2017-06-30 6:40 Uros Bizjak
2017-07-13 19:56 ` Ian Lance Taylor
2017-07-14 18:41 ` Uros Bizjak
2017-07-14 22:21 ` Ian Lance Taylor
2017-06-29 16:01 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='CAFULd4bgd_YPe+yp2bwy5ShTLq4C78xeJ3_99o=+w5oFTFThDQ@mail.gmail.com' \
--to=ubizjak@gmail.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=gofrontend-dev@googlegroups.com \
--cc=iant@golang.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).