From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!.POSTED!not-for-mail From: =?UTF-8?B?Sm/Do28gVMOhdm9yYQ==?= Newsgroups: gmane.emacs.devel Subject: Re: CC Mode and electric-pair "problem". Date: Mon, 18 Jun 2018 16:37:33 +0100 Message-ID: References: <20180531123747.GA24752@ACM> <20180617201351.GA4580@ACM> <20180618103654.GA9771@ACM> <8336xkt967.fsf@gnu.org> NNTP-Posting-Host: blaine.gmane.org Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="000000000000f057b5056eec588d" X-Trace: blaine.gmane.org 1529336193 30356 195.159.176.226 (18 Jun 2018 15:36:33 GMT) X-Complaints-To: usenet@blaine.gmane.org NNTP-Posting-Date: Mon, 18 Jun 2018 15:36:33 +0000 (UTC) Cc: Alan Mackenzie , emacs-devel@gnu.org, tino.calancha@gmail.com, Glenn Morris To: Eli Zaretskii Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Mon Jun 18 17:36:29 2018 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([208.118.235.17]) by blaine.gmane.org with esmtp (Exim 4.84_2) (envelope-from ) id 1fUwCi-0007jp-Qe for ged-emacs-devel@m.gmane.org; Mon, 18 Jun 2018 17:36:29 +0200 Original-Received: from localhost ([::1]:35385 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1fUwEo-0000eu-6r for ged-emacs-devel@m.gmane.org; Mon, 18 Jun 2018 11:38:38 -0400 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:59540) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1fUwE3-0000Iv-O3 for emacs-devel@gnu.org; Mon, 18 Jun 2018 11:37:52 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1fUwE2-0000ce-Sm for emacs-devel@gnu.org; Mon, 18 Jun 2018 11:37:51 -0400 Original-Received: from mail-io0-x22a.google.com ([2607:f8b0:4001:c06::22a]:42835) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1fUwE0-0000bg-3r; Mon, 18 Jun 2018 11:37:48 -0400 Original-Received: by mail-io0-x22a.google.com with SMTP id r24-v6so17201256ioh.9; Mon, 18 Jun 2018 08:37:47 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=W5gFA75Sid7dKYOkvmQLEwY5v8WsBO5JkgiZi5lr6mA=; b=Qm0RNSLdi4bxq0TN3LJxG1egoE9vnA6ZYj9TxXTfE8zf3pUHcOlQbEtxvKJaBVxBu2 JgJCkcMtgDpoXM7EUuji77WQMPsNVC3RpXmKpISEe/xu/HHmLBMLf9Sq6Pt4IKlCcYYQ ZDz7x10dHTTYGZOxZKxGF9v+dJedYs6Cl/fvXNJAhBxnrvwbi5f0gvv+BrBSqhhGwVC+ pr6EVvKhPPGAf4UVvLFMbqE+lPuELGBZH+w8Q6Aadqf3k6Owe1Dphqcn+zB6F8ZrLYhV GThUwqyproqzRNun4KgWeY+f0xH6ctepg3FzZPuCxWRby4lXEvN6Y2PsM4064BS3Ajv2 ZI5A== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=W5gFA75Sid7dKYOkvmQLEwY5v8WsBO5JkgiZi5lr6mA=; b=G3MDUEC/4ZeKT2FwnKxgbBcDrnm+zVtQrDjclX/2Db/ESVTcmgkiBz6rQoeNXAd0a6 QM7yk0fy1ob2qvsLdCeCtzZmGzrnGArpUzqomkIGsAWXsVM+ycQUEmdRzZjCCxrkerym XGFZdZqyym1dWbuN3w0ap7v5yavgP4FTFxaTsoYKn5wcim6EzsqPmGotdr487XWcSisv GMyBomwNO2RIokNKAQEUT5EAgNXmi/y2HK4bZYEiVWh34ArbgwAyewJ6e28dy8bI1gE2 +L1937Mzhso3tVZvo3fpnw8Y9eDWv9YrtSxKrYLoy+RulLsORbmh4UvihzJjBdicnnkV gg1w== X-Gm-Message-State: APt69E3xtMX0LAR68dleqPcZT0Kv70NHqlXC7XyNMgXyN/KpjQLJz15B Hxc0sFLtjYOBUynjL9Fy7cYDloWMpQwvW/Q7C0Rnew== X-Google-Smtp-Source: ADUXVKLRMHWDh+MIwsbR65vn8Z4fPFrs9N24h8sdNTayFVFpq1CUY49PnFRyAr2yL/3zdquaQDa5t4JAi32GlIlsFYo= X-Received: by 2002:a6b:9041:: with SMTP id s62-v6mr10043242iod.231.1529336267034; Mon, 18 Jun 2018 08:37:47 -0700 (PDT) In-Reply-To: <8336xkt967.fsf@gnu.org> X-detected-operating-system: by eggs.gnu.org: Genre and OS details not recognized. X-Received-From: 2607:f8b0:4001:c06::22a X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.21 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Original-Sender: "Emacs-devel" Xref: news.gmane.org gmane.emacs.devel:226459 Archived-At: --000000000000f057b5056eec588d Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Yes, and I'll probably do that. But in my experience, this has a very high probability of burying the problem, i.e. the incentive for actually fixing the problem is reduced dramatically. It's better to do test-breaking things on separate branches when possible. IMO expected failures are for when a feature is being designed and still incomplete, not when it was already working. Jo=C3=A3o On Mon, Jun 18, 2018, 16:18 Eli Zaretskii wrote: > > From: Jo=C3=A3o T=C3=A1vora > > Date: Mon, 18 Jun 2018 14:24:39 +0100 > > Cc: Glenn Morris , Emacs developers , > > Tino Calancha > > > > > Yes. But it is the master branch, where not everything can be expect= ed > > > to work all the time. I think the main thing is, we're _going_ to fi= x > > > this bug. > > > > Well, I respectfully and totally disagree. The reason we have automate= d > > tests in Hydra is to catch unintentional breakage, not intentional > > breakage. And, IIUC that test is the only one preventing a successful > > "make check". > > Isn't there a way to mark a test as expected to fail? > --000000000000f057b5056eec588d Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Yes, and I'll probably do that. But in my experience,= this has a very high probability of burying the problem, i.e. the incentiv= e for actually fixing the problem is reduced dramatically.=C2=A0 =C2=A0It&#= 39;s better to do test-breaking things on separate branches when possible.= =C2=A0 IMO expected failures are for when a feature is being designed and s= till incomplete, not when it was already working.

Jo=C3=A3o

On Mon, Jun 18, 2018, 16:18 Eli Zaret= skii <eliz@gnu.org> wrote:
> From: Jo=C3=A3o T=C3=A1vora <jo= aotavora@gmail.com>
> Date: Mon, 18 Jun 2018 14:24:39 +0100
> Cc: Glenn Morris <rgm@gnu.org>, Emacs developers <emacs-devel@g= nu.org>,
>=C2=A0 =C2=A0 =C2=A0 =C2=A0Tino Calancha <tino.calancha@gmail.c= om>
>
> > Yes.=C2=A0 But it is the master branch, where not everything can = be expected
> > to work all the time.=C2=A0 I think the main thing is, we're = _going_ to fix
> > this bug.
>
> Well, I respectfully and totally disagree.=C2=A0 The reason we have au= tomated
> tests in Hydra is to catch unintentional breakage, not intentional
> breakage.=C2=A0 And, IIUC that test is the only one preventing a succe= ssful
> "make check".

Isn't there a way to mark a test as expected to fail?
--000000000000f057b5056eec588d--