From: Simon Marchi <simon.marchi@polymtl.ca>
To: Sandra Loosemore <sandra@codesourcery.com>
Cc: gdb@sourceware.org
Subject: Re: remote host testing expectations re multiple simultaneous connections
Date: Wed, 31 Oct 2018 12:20:00 -0000 [thread overview]
Message-ID: <e7127f5889952f01289e60610ca0dcfd@polymtl.ca> (raw)
In-Reply-To: <993f1ebe-d055-d1a1-879a-5cd2d8c8fd35@codesourcery.com>
On 2018-10-28 13:43, Sandra Loosemore wrote:
> Our local remote-host DejaGnu test support (for testing on Windows
> host, actually) maintains some global state about the spawned GDB
> connection that is getting clobbered by opening another connection to
> the same host to run shell commands, resulting in GDB getting killed
> (so all these tests fail). I've been struggling to find exactly what
> is going wrong, but wanted to make sure that this is actually a test
> harness bug and not broken testcases before spending any more time on
> it.
>
> It does seem like requiring support for multiple simultaneous
> connections to either a host or target would preclude testing on
> anything where all you have is a single serial connection to talk to
> it, and not (say) multiple ssh connections.
Ok, I understand. If we can modify the test you referred to (by
reordering operations) to make them work for your use case and it
doesn't impact the quality of the test, then I don't see why it wouldn't
be acceptable.
Simon
prev parent reply other threads:[~2018-10-31 12:20 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-26 19:22 Sandra Loosemore
2018-10-28 17:05 ` Simon Marchi
2018-10-28 17:43 ` Sandra Loosemore
2018-10-31 12:20 ` Simon Marchi [this message]
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=e7127f5889952f01289e60610ca0dcfd@polymtl.ca \
--to=simon.marchi@polymtl.ca \
--cc=gdb@sourceware.org \
--cc=sandra@codesourcery.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).