Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Baurjan Ismagulov <ibr@ata.cs.hun.edu.tr>
To: gdb-patches@sources.redhat.com
Subject: Re: testcase for "absolute source" patch
Date: Wed, 18 Aug 2004 22:03:00 -0000	[thread overview]
Message-ID: <20040818220613.GA3143@ata.cs.hun.edu.tr> (raw)
In-Reply-To: <4123A736.nail5OO17XN7L@mindspring.com>

Hello Michael,

On Wed, Aug 18, 2004 at 03:00:06PM -0400, Michael Chastain wrote:
> The problem is default_target_compile in dejagnu.
> default_target_compile really wants to be in charge of downloading files
> from build to host and managing the filenames on the host.  This
> directly conflicts with your script, which wants to manage the names
> on the host.

As far as I could understand, there are also other tests that do not
work well in build != host scenario. I don't remember any decision from
the recent thread on this issue. OTOH, this test functions locally and
checks a number of cases, at least two of which have been subject to
regressions. I think this was the reason why Andrew asked for it in the
first place. While I agree that fixing the infrastructure is also
important, may I suggest that we have at least local checking in the
trunk? After all, whatever the state of the infrastructure, we still
want to check for bugs; a non-ideal test is better than no test at all,
IMHO. I also don't see any problem in modifying the test as the
infrastructure changes, whereas not having the test is going to lead to
bugs, especially given an open PR involving the respective subsystem.

To summarize: the test is working probably for 95% of the users. I'm
willing to make the test as close to the ideal in your head as possible,
and I can do it only now. I suggest that we improve what can be improved
and leave the rest for better times.

What do you think?

With kind regards,
Baurjan.


  reply	other threads:[~2004-08-18 22:03 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-08-16 14:41 Baurzhan Ismagulov
2004-08-16 15:56 ` Michael Chastain
2004-08-16 18:21   ` Baurjan Ismagulov
2004-08-16 19:15 ` Michael Chastain
2004-08-16 20:38   ` Andreas Schwab
2004-08-18 13:03   ` Baurzhan Ismagulov
2004-08-18 15:31     ` Michael Chastain
2004-08-18 15:50       ` Daniel Jacobowitz
2004-08-18 15:56         ` Baurjan Ismagulov
2004-08-18 16:04           ` Andreas Schwab
2004-08-18 15:50       ` Baurzhan Ismagulov
2004-08-18 17:10         ` Michael Chastain
2004-08-18 19:00         ` Michael Chastain
2004-08-18 22:03           ` Baurjan Ismagulov [this message]
2004-08-18 22:46             ` Michael Chastain
2004-08-18 23:33             ` Michael Chastain
2004-08-19  4:03               ` Eli Zaretskii
2004-08-19  8:34                 ` Michael Chastain
2004-08-19  8:56               ` Michael Chastain
2004-08-19  9:37                 ` Baurjan Ismagulov
2004-08-19  9:34               ` Baurjan Ismagulov
2004-08-19  9:55                 ` Michael Chastain
2004-08-19 10:10                   ` Baurjan Ismagulov
2004-08-19 10:20                     ` Michael Chastain
2004-08-26 20:36                   ` Baurjan Ismagulov
2004-08-26 20:52                     ` Michael Chastain
2004-08-26 20:32               ` Baurjan Ismagulov
2004-08-27 14:16                 ` Michael Chastain
2004-08-27 16:45                   ` Baurjan Ismagulov
2004-08-29 11:56                     ` Michael Chastain
2004-08-31 15:01                     ` Michael Chastain
2004-09-25 21:12                       ` Baurjan Ismagulov

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=20040818220613.GA3143@ata.cs.hun.edu.tr \
    --to=ibr@ata.cs.hun.edu.tr \
    --cc=gdb-patches@sources.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