public inbox for gdb-patches@sourceware.org
 help / color / mirror / Atom feed
From: Doug Evans <xdje42@gmail.com>
To: Yao Qi <yao@codesourcery.com>
Cc: <gdb-patches@sourceware.org>
Subject: Re: [PATCH] Fix parallel testing issues in gdb.guile tests
Date: Tue, 02 Dec 2014 01:35:00 -0000	[thread overview]
Message-ID: <m3tx1e6dh4.fsf@sspiff.org> (raw)
In-Reply-To: <1417268843-13652-1-git-send-email-yao@codesourcery.com> (Yao	Qi's message of "Sat, 29 Nov 2014 21:47:23 +0800")

Yao Qi <yao@codesourcery.com> writes:

> Some gdb.guile tests such as scm-error.exp copies .scm file to
> ${subdir}/, how ${subdir} doesn't exist in parallel testing
> (outputs/${subdir} exists).
>
> $ make -j3 check TESTS='gdb.guile/scm-section-script.exp gdb.guile/scm-error.exp gdb.guile/scm-frame-args.exp'
>
> ERROR: remote_download to host of ../../../../git/gdb/testsuite/gdb.guile/scm-section-script.scm to gdb.guile/t-scm-section-script.scm: cp: cannot create regular file 'gdb.guile/t-scm-section-script.scm': No such file or directory
> ERROR: remote_download to host of ../../../../git/gdb/testsuite/gdb.guile/scm-frame-args.scm to gdb.guile/t-scm-frame-args.scm: cp: cannot create regular file
> 'gdb.guile/t-scm-frame-args.scm': No such file or directory
> ERROR: remote_download to host of ../../../../git/gdb/testsuite/gdb.guile/scm-error-1.scm to gdb.guile/t-scm-error-1.scm: cp: cannot create regular file 'gdb.guile/t-scm-error-1.scm': No such file or directory

Hmmm, there's something more going on here that we need to understand.
[The patch may still be ok, but I'd still like to understand
this error.]

I don't see these fails.
The files are going into $obj/gdb/testsuite/gdb.guile,
which does exist.
They *should* go in $obj/gdb/testsuite/outputs/foo, sure.
But how come you're getting this error?

> [...]
> diff --git a/gdb/testsuite/gdb.guile/scm-section-script.exp b/gdb/testsuite/gdb.guile/scm-section-script.exp
> index 0c5e489..a1ebd10 100644
> --- a/gdb/testsuite/gdb.guile/scm-section-script.exp
> +++ b/gdb/testsuite/gdb.guile/scm-section-script.exp
> @@ -35,14 +35,11 @@ standard_testfile
>  
>  # Make this available to gdb before the program starts, it is
>  # automagically loaded by gdb.
> -# Give the file a new name so we don't clobber the real one if
> -# objfile == srcdir.
>  # We also need to do this before compiling the program because the name
>  # of the script file is encoded in the binary.
>  # FIXME: Can we get gdb_remote_download to call standard_output_file for us?

Please remove this FIXME while you're at it.

>  set remote_guile_file [gdb_remote_download host \
> -			   ${srcdir}/${subdir}/${testfile}.scm \
> -			   ${subdir}/t-${testfile}.scm]
> +			   ${srcdir}/${subdir}/${testfile}.scm]
>  
>  if {[build_executable $testfile.exp $testfile $srcfile \
>  	[list debug "additional_flags=-I${srcdir}/../../include -DSCRIPT_FILE=\"$remote_guile_file\""]] == -1} {

  reply	other threads:[~2014-12-02  1:35 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-11-29 13:47 Yao Qi
2014-12-02  1:35 ` Doug Evans [this message]
2014-12-05 11:36   ` Yao Qi
2014-12-05 16:20     ` Doug Evans

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=m3tx1e6dh4.fsf@sspiff.org \
    --to=xdje42@gmail.com \
    --cc=gdb-patches@sourceware.org \
    --cc=yao@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).