all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: "João Távora" <joaotavora@gmail.com>
To: emacs-devel <emacs-devel@gnu.org>, Alan Mackenzie <acm@muc.de>
Subject: Apropos 54f297904e0c: Temporarily comment out CC Mode from tests which are incompatible with it.
Date: Thu, 17 Jan 2019 14:57:04 +0000	[thread overview]
Message-ID: <CALDnm52_uLf+Wi4pfU9MwZrApii2S2Wos7cEimBKt1AqgAM9gA@mail.gmail.com> (raw)

Hi Alan,

Please revert this change ASAP:

commit 54f297904e0c641fcfd81f16e9a87177124a27be
Author: Alan Mackenzie
Date:   Thu Jan 17 12:51:40 2019 +0000

    Temporarily comment out CC Mode from tests which are incompatible
with it.

    * tests/electric-tests (electric-pair-test-for): comment out
c++-mode from the
    list of modes to be used in tests.
    (electric-pair-whitespace-chomping-2-at-point-4-in-c++-mode-in-strings)
    (ert-deftest electric-layout-int-main-kernel-style)
    (ert-deftest electric-layout-int-main-allman-style): Comment out.

I thought we had agreed that the way to "work around" other people's
unit tests, even if temporarily, is to work in a separate git branch.

The other electric-pair-test that I disabled 6 months ago, that was one that
also temporary, is till there. But now you destroyed even the "expected
failure" mark.  Why?? Is the test passing unexpectedly?

@@ -396,10 +397,10 @@ whitespace-chomping-2
 ;; mode will sort this out eventually, using some new e-p-m machinery.
 ;; See
 ;; https://lists.gnu.org/archive/html/emacs-devel/2018-06/msg00535.html
-(setf
- (ert-test-expected-result-type
-  (ert-get-test
'electric-pair-whitespace-chomping-2-at-point-4-in-c++-mode-in-strings))
- :failed)
+;; (setf
+;;  (ert-test-expected-result-type
+;;   (ert-get-test
'electric-pair-whitespace-chomping-2-at-point-4-in-c++-mode-in-strings))
+;;  :failed)

But this is much more intrusive.  In particular

;; Tests commented out, since C Mode does not use
;; electric-layout-mode.  2019-01-17, ACM

C Mode doesn't use electric-layout mode, but a user can surely
decide we wants to use it in c-mode, can he not??  These tests
pass fine currently.

Please revert this fix and lets discuss why you need to disable tests.

If we come to the conclusion that some tests are asserting unreasonable
expectations about the functionality you develop, we can disable them on a
case by case basis!

If on the other hand, if you need to do some work "temporarily", then
the best way to do it without disturbing other people's developments
is to do it in a separate branch.

João



             reply	other threads:[~2019-01-17 14:57 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-01-17 14:57 João Távora [this message]
2019-01-17 16:43 ` Apropos 54f297904e0c: Temporarily comment out CC Mode from tests which are incompatible with it Alan Mackenzie
2019-01-17 17:57   ` João Távora
2019-01-17 18:55     ` João Távora
2019-01-18 17:54     ` Alan Mackenzie
2019-01-18 19:55       ` João Távora
2019-01-18 22:53         ` Alan Mackenzie
2019-01-19  3:18           ` João Távora
2019-01-19 11:07             ` Alan Mackenzie
2019-01-19 13:52               ` João Távora
2019-01-19 17:45                 ` Alan Mackenzie
2019-01-19 19:15                   ` João Távora
2019-01-19 20:58                     ` Alan Mackenzie
2019-01-19 23:18                       ` João Távora
2019-01-21 18:04                       ` Stefan Monnier
2019-01-21 20:45                         ` Alan Mackenzie
2019-01-21 21:46                           ` Stefan Monnier
2019-01-21 22:41                             ` João Távora
2019-01-19 22:37                     ` Drew Adams
2019-01-20 19:05                 ` Richard Stallman
2019-01-20 21:18                   ` João Távora
2019-01-21 20:59                     ` Richard Stallman
2019-01-21 21:49                       ` João Távora
2019-01-18 21:06       ` Stefan Monnier
2019-01-19  3:25         ` João Távora
2019-01-18 22:47       ` Michael Albinus
2019-01-19 20:18       ` Richard Stallman

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=CALDnm52_uLf+Wi4pfU9MwZrApii2S2Wos7cEimBKt1AqgAM9gA@mail.gmail.com \
    --to=joaotavora@gmail.com \
    --cc=acm@muc.de \
    --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.