[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Tests, Emacs-25 and Conditional Features
From: |
Phillip Lord |
Subject: |
Tests, Emacs-25 and Conditional Features |
Date: |
Wed, 16 Mar 2016 13:36:37 +0000 |
User-agent: |
Gnus/5.13 (Gnus v5.13) Emacs/24.5 (gnu/linux) |
I have two questions about tests.
First, does the "no changes on Emacs-25" rule apply to changes in the
test directory -- i.e. can next tests be added. Arguments for -- tests
are a good thing to add and should not break a release. Arguments
against -- we are in pre-test, and it's easier to have a simple rule.
Also, tests are currently painful to merge.
Second, should tests assume that all the conditional features (gnutls,
libxml) are available? If the answer is no, then how can we test that
conditional features are present when they should be; if the answer is
yes, then do we want tests that will fail some of the time.
Phil
- Tests, Emacs-25 and Conditional Features,
Phillip Lord <=
- Re: Tests, Emacs-25 and Conditional Features, Michael Albinus, 2016/03/16
- Re: Tests, Emacs-25 and Conditional Features, Phillip Lord, 2016/03/17
- Re: Tests, Emacs-25 and Conditional Features, Eli Zaretskii, 2016/03/17
- Re: Tests, Emacs-25 and Conditional Features, Phillip Lord, 2016/03/18
- Re: Tests, Emacs-25 and Conditional Features, Michael Albinus, 2016/03/18
- Re: Tests, Emacs-25 and Conditional Features, Phillip Lord, 2016/03/18
- Re: Tests, Emacs-25 and Conditional Features, Eli Zaretskii, 2016/03/18
- Re: Tests, Emacs-25 and Conditional Features, Eli Zaretskii, 2016/03/18
- Re: Tests, Emacs-25 and Conditional Features, Phillip Lord, 2016/03/18
- Re: Tests, Emacs-25 and Conditional Features, Eli Zaretskii, 2016/03/18