From: John Wiegley <jwiegley@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: emacs-devel@gnu.org
Subject: Re: Volunteers to implement test for stuff called at startup?
Date: Tue, 10 May 2016 19:05:40 -0700 [thread overview]
Message-ID: <m2postbb7v.fsf@newartisans.com> (raw)
In-Reply-To: <83y47tn5tv.fsf@gnu.org> (Eli Zaretskii's message of "Sun, 01 May 2016 18:41:48 +0300")
[-- Attachment #1: Type: text/plain, Size: 1031 bytes --]
>>>>> Eli Zaretskii <eliz@gnu.org> writes:
> So with this in mind, one idea that could help us detect similar situations
> in the future would be to have a test in the test suite that would record
> every primitive called during startup, compare it against some expected
> list, and flag any changes (at least additions, not sure about deletions).
> Then both people who run the test suite regularly and bots like Hydra could
> flag any changes and let us handle these potential problems when they are
> young.
> Does that make sense? If so, would someone like to volunteer for the job?
I like this idea. The approach of gathering a "primitives" list, and comparing
it after each test run, doesn't require as much legwork as Richard's
suggestion -- where we'd need to know ahead of time every such flag of
interest.
I'll second the call: any volunteers?
--
John Wiegley GPG fingerprint = 4710 CF98 AF9B 327B B80F
http://newartisans.com 60E1 46C4 BD1A 7AC1 4BA2
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 629 bytes --]
prev parent reply other threads:[~2016-05-11 2:05 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-01 15:41 Volunteers to implement test for stuff called at startup? Eli Zaretskii
2016-05-01 23:07 ` Richard Stallman
2016-05-02 15:08 ` Kaushal Modi
2016-05-02 15:15 ` Robert Pluim
2016-05-02 15:23 ` Kaushal Modi
2016-05-02 15:32 ` Eli Zaretskii
2016-05-02 15:44 ` Kaushal Modi
2016-05-02 15:56 ` Eli Zaretskii
2016-05-02 16:23 ` Kaushal Modi
2016-05-11 2:05 ` John Wiegley [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=m2postbb7v.fsf@newartisans.com \
--to=jwiegley@gmail.com \
--cc=eliz@gnu.org \
--cc=emacs-devel@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.