From: Simon Marchi <simon.marchi@ericsson.com>
To: Jan Kratochvil <jan.kratochvil@redhat.com>
Cc: Joel Brobecker <brobecker@adacore.com>,
Pedro Alves <palves@redhat.com>, <gdb-patches@sourceware.org>
Subject: Re: [testsuite 7.11] Regression for i386-biarch-core.exp and others [Re: [PATCH] Always organize test artifacts in a directory hierarchy]
Date: Fri, 12 Feb 2016 19:38:00 -0000 [thread overview]
Message-ID: <56BE349A.1090505@ericsson.com> (raw)
In-Reply-To: <20160212184710.GA21838@host1.jankratochvil.net>
On 16-02-12 01:47 PM, Jan Kratochvil wrote:
> On Fri, 12 Feb 2016 19:34:16 +0100, Simon Marchi wrote:
>> I think this patch should fix it. It simply makes the test use standard_output_file
>> for its output directory.
>
> OK, thanks. I did not expect almost all the other 42 failed testfiles are
> Fedora-only ones so I have to fix them on my own.
> gdb.arch/i386-interface.exp gdb.arch/x86_64-pid0-core.exp gdb.arch/x86_64-vla-typedef.exp gdb.base/attach-32.exp gdb.base/attach-see-vdso.exp gdb.base/charsign.exp gdb.base/corefile.exp gdb.base/datalib.exp gdb.base/execl-update-breakpoints.exp gdb.base/fork-detach.exp gdb.base/gcore-excessive-memory.exp gdb.base/gcorebg.exp gdb.base/lineno-makeup.exp gdb.base/move-dir.exp gdb.base/readline-overflow.exp gdb.base/rhbz981154-misleading-yum-install-warning.exp gdb.base/step-over-trampoline.exp gdb.base/unwind-leak.exp gdb.base/vla-overflow.exp gdb.base/vla.exp gdb.base/watchpoint-cond.exp gdb.base/watchpoint-during-step.exp gdb.cp/b146835.exp gdb.cp/constructortest.exp gdb.cp/namespace-nested-imports.exp gdb.cp/namespace-no-imports.exp gdb.dwarf2/dw2-errno.exp gdb.dwarf2/dw2-errno2.exp gdb.dwarf2/dw2-included.exp gdb.fortran/dynamic.exp gdb.fortran/string.exp gdb.pascal/arrays.exp gdb.pie/attach.exp gdb.pie/break.exp gdb.pie/corefile.exp gdb.threads/bt-clone-stop.exp gdb.threads/simul
taneous-step-resume-breakpoint.exp gdb.threads/threadcrash.exp gdb.threads/threaded-exec.exp gdb.threads/tls-rhbz947564.exp gdb.threads/tls-sepdebug.exp gdb.threads/watchthreads-threaded.exp
>
> (gdb.base/corefile.exp gdb.base/execl-update-breakpoints.exp listed there do
> not reproduce it for me locally now, I will re-check those.)
>
>
> Jan
I'll run the testsuite with GDB_INOTIFY=1, it might catch a few problems of the same kind.
next prev parent reply other threads:[~2016-02-12 19:38 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-08 15:52 [PATCH] Always organize test artifacts in a directory hierarchy Simon Marchi
2016-01-12 13:00 ` Pedro Alves
[not found] ` <56952A6C.8070507@ericsson.com>
2016-01-13 11:11 ` Pedro Alves
2016-01-17 6:37 ` Joel Brobecker
2016-01-20 23:29 ` Simon Marchi
2016-01-25 21:24 ` Simon Marchi
2016-01-25 21:54 ` Simon Marchi
2016-02-01 22:41 ` Simon Marchi
2016-02-07 7:10 ` Joel Brobecker
2016-02-08 19:01 ` Simon Marchi
2016-02-08 19:26 ` Simon Marchi
2016-02-11 21:22 ` [testsuite 7.11] Regression for i386-biarch-core.exp and others [Re: [PATCH] Always organize test artifacts in a directory hierarchy] Jan Kratochvil
2016-02-12 18:34 ` Simon Marchi
2016-02-12 18:41 ` Pedro Alves
2016-02-12 18:56 ` Simon Marchi
2016-02-12 21:54 ` Simon Marchi
2016-02-12 23:01 ` Pedro Alves
2016-02-15 16:17 ` Simon Marchi
2016-02-12 18:47 ` Jan Kratochvil
2016-02-12 19:38 ` Simon Marchi [this message]
2016-02-15 17:58 ` [testsuite obv+7.11] Fix more testcases with standard_output_file [Re: [testsuite 7.11] Regression for i386-biarch-core.exp and others] Jan Kratochvil
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=56BE349A.1090505@ericsson.com \
--to=simon.marchi@ericsson.com \
--cc=brobecker@adacore.com \
--cc=gdb-patches@sourceware.org \
--cc=jan.kratochvil@redhat.com \
--cc=palves@redhat.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).