public inbox for gdb-prs@sourceware.org help / color / mirror / Atom feed
From: "keiths at redhat dot com" <sourceware-bugzilla@sourceware.org> To: gdb-prs@sourceware.org Subject: [Bug testsuite/18067] many failures in testsuite Date: Tue, 17 Mar 2015 19:19:00 -0000 [thread overview] Message-ID: <bug-18067-4717-dnktYqQcCL@http.sourceware.org/bugzilla/> (raw) In-Reply-To: <bug-18067-4717@http.sourceware.org/bugzilla/> https://sourceware.org/bugzilla/show_bug.cgi?id=18067 Keith Seitz <keiths at redhat dot com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |keiths at redhat dot com --- Comment #1 from Keith Seitz <keiths at redhat dot com> --- The real test log would probably be more enlightening than the .sum file, but from what I can see in the .sum you supplied, there appears to be something quite suspicious about your build/test environment. Can you attach the gdb.log of: $ make check RUNTESTFLAGS=dw2-basic.exp This is showing: ERROR: remote_download to host of ./gdb.dwarf2/file1.txt to /home/yuri/gdb-7.8.2/gdb/testsuite/gdb.dwarf2/file.txt: cp: cannot stat './gdb.dwarf2/file1.txt': No such file or directory This same error appears in several places, along with: FAIL: gdb.dwarf2/gdb-index.exp: touch binary This is all very odd. What directory are you trying to run tests in? Is it read-only? A huge chunk of failures is in attach-into-signal.exp. That has, in the past, been one of a handful of racy tests. Try running it alone and see if it passes. We'll worry about the other big problem area, python, when we get the remote_download issues resolved. -- You are receiving this mail because: You are on the CC list for the bug.
next prev parent reply other threads:[~2015-03-17 16:50 UTC|newest] Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top 2015-03-02 13:31 [Bug testsuite/18067] New: " yuri at tsoft dot com 2015-03-17 19:19 ` keiths at redhat dot com [this message] 2015-07-22 12:40 ` [Bug testsuite/18067] " ciro.santilli at gmail dot com 2015-07-22 12:48 ` ciro.santilli at gmail dot com 2015-07-23 9:41 ` palves at redhat dot com 2015-07-31 11:46 ` ciro.santilli at gmail 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-18067-4717-dnktYqQcCL@http.sourceware.org/bugzilla/ \ --to=sourceware-bugzilla@sourceware.org \ --cc=gdb-prs@sourceware.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: linkBe 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).