all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Reuben Thomas <rrt@sc3d.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 28319@debbugs.gnu.org
Subject: bug#28319: emacsclient tests interfere with running Emacs, hang
Date: Fri, 8 Sep 2017 00:10:52 +0100	[thread overview]
Message-ID: <CAOnWdogPm+vM-DZ6T5HS6ErcNT-Q5=9-GjaACG4FVDWQhULL8A@mail.gmail.com> (raw)
In-Reply-To: <83pob324u6.fsf@gnu.org>

[-- Attachment #1: Type: text/plain, Size: 745 bytes --]

On 6 September 2017 at 17:02, Eli Zaretskii <eliz@gnu.org> wrote:

>
> In any case, why are we running the test suite with Emacs compiled
> with profiling?  Is there a good reason for doing that?  Does that
> bring us some useful data?  If not, simply building without profiling
> might easily fix this problem.
>

​Nonetheless, it should be possible to run the test suite when building
with --enable-profiling.

However, it's not obvious that profiling is of great interest for the
programs in lib-src, so an option would be to change the build system so
that --enable-profiling applies only to emacs itself. This would obviate
potential similar problems testing other lib-src binaries in future.

-- 
https://rrt.sc3d.org

[-- Attachment #2: Type: text/html, Size: 1456 bytes --]

      reply	other threads:[~2017-09-07 23:10 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-09-01 16:40 bug#28319: emacsclient tests interfere with running Emacs, hang Glenn Morris
2017-09-01 17:23 ` Reuben Thomas
2017-09-01 20:37   ` Reuben Thomas
2017-09-01 22:19     ` Glenn Morris
2017-09-01 22:44       ` Reuben Thomas
2017-09-05 19:55         ` Glenn Morris
2017-09-05 21:11           ` Reuben Thomas
2017-09-05 22:24             ` Glenn Morris
2017-09-06  1:14               ` Glenn Morris
2017-09-06 16:02             ` Eli Zaretskii
2017-09-07 23:10               ` Reuben Thomas [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='CAOnWdogPm+vM-DZ6T5HS6ErcNT-Q5=9-GjaACG4FVDWQhULL8A@mail.gmail.com' \
    --to=rrt@sc3d.org \
    --cc=28319@debbugs.gnu.org \
    --cc=eliz@gnu.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: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.