unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Kenichi Handa <handa@gnu.org>
To: Glenn Morris <rgm@gnu.org>
Cc: 14781@debbugs.gnu.org
Subject: bug#14781: coding system changes cause make check to hang in icalendar tests
Date: Mon, 08 Jul 2013 21:08:02 +0900	[thread overview]
Message-ID: <87y59hp84d.fsf@gnu.org> (raw)
In-Reply-To: <6zju35ux8.fsf@fencepost.gnu.org> (message from Glenn Morris on Wed, 03 Jul 2013 15:02:11 -0400)

In article <6zju35ux8.fsf@fencepost.gnu.org>, Glenn Morris <rgm@gnu.org> writes:

> Current trunk, GNU/Linux, make check is broken by recent changes related
> to coding systems (I suspect):

> make check
> ...
> Converting iCalendar...done
>    passed  122/331  icalendar-import-with-uid
[...]
> Saving file /tmp/icalendar-test-diary133276Qn...
> Select coding system (default chinese-iso-8bit): 

> ...hangs waiting for input.

I've just committed a fix to the trunk.  Actually, the
culprit was test/automated/decoder-tests.el which changes
priorities of coding systems.  I didn't know that all tests
under test/automated are executed in a single Emacs session,
and thus they must be side-effect free.  Isn't it better to
execute each test file in its own Emacs session?

---
Kenichi Handa
handa@gnu.org






  reply	other threads:[~2013-07-08 12:08 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-07-03 19:02 bug#14781: coding system changes cause make check to hang in icalendar tests Glenn Morris
2013-07-08 12:08 ` Kenichi Handa [this message]
2013-07-08 16:52 ` Glenn Morris
2013-07-08 20:22   ` Stefan Monnier
2013-07-09 13:47   ` Handa Kenichi
2013-07-09 16:08     ` Glenn Morris
2013-07-09 16:15     ` Glenn Morris
2013-07-10  8:49       ` Stefan Monnier
2013-07-11 13:38       ` Handa Kenichi
2013-07-09  1:46 ` Glenn Morris

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

  List information: https://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87y59hp84d.fsf@gnu.org \
    --to=handa@gnu.org \
    --cc=14781@debbugs.gnu.org \
    --cc=rgm@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 public inbox

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

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).