From: Christian Ohler <ohler@gnu.org>
To: Stefan Monnier <monnier@iro.umontreal.ca>
Cc: 11218@debbugs.gnu.org
Subject: bug#11218: with-demoted-errors use of condition-case-unless-debug; ert
Date: Sun, 20 May 2012 20:03:13 -0700 [thread overview]
Message-ID: <4FB9B071.1060907@gnu.org> (raw)
In-Reply-To: <jwvbom0ztnx.fsf-monnier+emacs@gnu.org>
Stefan Monnier, 2012-05-06:
>> Collecting additional information about why the test failed is useful
>> to virtually everyone who bothers running the test; there should be no
>> reason not to.
>
> I disagree here. I think it's just as well if the "check" and the
> "debug" are done in 2 different steps.
ERT originally worked like you describe, until I got tired of having to
re-run each failed test just to get a backtrace. The computer has the
information in memory at the time the test fails; it should store it
somewhere for me to look at later, rather than making me wait while it
tries to recompute it. The backtrace is so basic that I practically
always want to see it.
In batch mode, ERT also has to collect the backtrace on every failure;
the idea of re-running with debugging enabled makes no sense in that
context (if enabling debugging to collect backtraces in batch mode was
an optional flag to be set on a second run after noticing failures on
the first run, why not set that flag the first time around?). Also, a
continuous build system is much more useful if errors come with more
information since that increases the chances that the bug can be fixed
without first building a specific version on a specific architecture to
reproduce it.
>> The proper solution is to decouple the behaviors, perhaps by splitting
>> the variable, perhaps by some other means.
>
> No, the proper solution is to make with-demoted-error (when run with
> debug-on-error) continue execution (after hitting `c' in the debugger)
> as if debug-on-error were nil.
That sounds like a good idea; I would add that it should be possible to
invoke this "restart" (in CL terms) programmatically. (This does
decouple the behaviors: it allows errors to be demoted regardless of the
setting of `debug-on-error'.)
Christian.
next prev parent reply other threads:[~2012-05-21 3:03 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-11 3:37 bug#11218: with-demoted-errors use of condition-case-unless-debug; ert Glenn Morris
2012-04-11 12:03 ` Lars Magne Ingebrigtsen
2012-04-11 16:16 ` Glenn Morris
2012-04-11 16:28 ` Glenn Morris
2012-04-11 17:57 ` Stefan Monnier
2012-04-11 13:02 ` Stefan Monnier
2012-04-13 0:15 ` Glenn Morris
2012-04-13 13:44 ` Stefan Monnier
2012-04-17 21:30 ` Christian Ohler
2012-04-19 7:46 ` Stefan Monnier
2012-04-20 3:09 ` Christian Ohler
2012-04-20 12:13 ` Stefan Monnier
2012-04-20 21:02 ` Christian Ohler
2012-04-21 2:34 ` Stefan Monnier
2012-04-23 13:26 ` Lennart Borgman
2012-04-24 2:04 ` Stefan Monnier
2012-05-06 18:45 ` Christian Ohler
2012-05-07 1:12 ` Stefan Monnier
2012-05-21 3:03 ` Christian Ohler [this message]
2018-08-15 1:10 ` Noam Postavsky
2020-11-24 17:34 ` Philipp Stephani
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=4FB9B071.1060907@gnu.org \
--to=ohler@gnu.org \
--cc=11218@debbugs.gnu.org \
--cc=monnier@iro.umontreal.ca \
/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.