From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Eli Zaretskii Newsgroups: gmane.emacs.devel Subject: Re: sqlite3 Date: Sun, 19 Dec 2021 18:34:45 +0200 Message-ID: <83y24g7dui.fsf@gnu.org> References: <87tufmjyai.fsf@gnus.org> <87mtl13vz2.fsf@gnus.org> <87ilvp3tzo.fsf@gnus.org> <83wnk5gduf.fsf@gnu.org> <87r1ab1y0r.fsf@gnus.org> <83sfurejs6.fsf@gnu.org> <871r2b1vu8.fsf@gnus.org> <83o85feitv.fsf@gnu.org> <87lf0jzifm.fsf@gnus.org> <83a6gze705.fsf@gnu.org> <87k0g2xsu9.fsf@gnus.org> <871r2axqp4.fsf@gnus.org> <83sfuqb5yo.fsf@gnu.org> <87fsqoyiao.fsf@gnus.org> <83v8zk96yh.fsf@gnu.org> <87zgowvmt5.fsf@gnus.org> <838rwg8z8i.fsf@gnu.org> <871r28vg4y.fsf@gnus.org> <834k748wez.fsf@gnu.org> <831r288vne.fsf@gnu.org> <83zgow7fpi.fsf@gnu.org> Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="22564"; mail-complaints-to="usenet@ciao.gmane.io" Cc: emacs-devel@gnu.org To: larsi@gnus.org Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Sun Dec 19 17:36:34 2021 Return-path: Envelope-to: ged-emacs-devel@m.gmane-mx.org Original-Received: from lists.gnu.org ([209.51.188.17]) by ciao.gmane.io with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1myzAo-0005aY-1J for ged-emacs-devel@m.gmane-mx.org; Sun, 19 Dec 2021 17:36:34 +0100 Original-Received: from localhost ([::1]:59116 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1myzAm-0001QX-1n for ged-emacs-devel@m.gmane-mx.org; Sun, 19 Dec 2021 11:36:32 -0500 Original-Received: from eggs.gnu.org ([209.51.188.92]:58006) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1myz9E-000077-5F for emacs-devel@gnu.org; Sun, 19 Dec 2021 11:34:56 -0500 Original-Received: from [2001:470:142:3::e] (port=38590 helo=fencepost.gnu.org) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1myz9D-00018u-5a; Sun, 19 Dec 2021 11:34:55 -0500 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=gnu.org; s=fencepost-gnu-org; h=References:Subject:In-Reply-To:To:From:Date: mime-version; bh=2uxnIsB7CexjcWx/w2/0lIkKhfbK+evYUUCORnif8jM=; b=dgM4QvFSU2wZ NDNpbUj8O0Bk0WTNYbzngNHGOS9QIWgoOX4u99ydsecyb7GjYREMhIWxoK+mk1RSnrm2II7uwPYs1 VC8cF5ZGzCYc2DofiI9r1jpgO7OUpTJhF5kqiT53/V+evIGaJIrcTsmdF7dmLRqr/DJA1kvSojyDV MBOI22HsR3e/UzmFcvvytCgOARe3cxerwC56YjbeBDP2sPcVEiJIY45cOOb5GabTiB55O7Ad5WSnv wqZxmQBxj/oNgBm8qNvvRRtUITdS94FnNHqh7HrlR2KcmFS4Z3BG7i8w1aSvb2aju+DpzaIgvcVGK fPg9pvNgBsFnhgpf1iU6VQ==; Original-Received: from [87.69.77.57] (port=2215 helo=home-c4e4a596f7) by fencepost.gnu.org with esmtpsa (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1myz9D-0001EA-23; Sun, 19 Dec 2021 11:34:55 -0500 In-Reply-To: <83zgow7fpi.fsf@gnu.org> (message from Eli Zaretskii on Sun, 19 Dec 2021 17:54:33 +0200) X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.29 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-mx.org@gnu.org Original-Sender: "Emacs-devel" Xref: news.gmane.io gmane.emacs.devel:282448 Archived-At: > Date: Sun, 19 Dec 2021 17:54:33 +0200 > From: Eli Zaretskii > Cc: emacs-devel@gnu.org > > > Date: Sun, 19 Dec 2021 17:24:53 +0200 > > From: Eli Zaretskii > > Cc: emacs-devel@gnu.org > > > > > Date: Sun, 19 Dec 2021 17:08:20 +0200 > > > From: Eli Zaretskii > > > Cc: emacs-devel@gnu.org > > > > > > Unfortunately, this breaks filelock-tests.el in some strange ways: > > > even if I replace file-error with permission-denied, the tests fail, > > > and it seems like should-error doesn't catch the error. That is, the > > > failure is not in comparing the error data with the expected value. > > > Does ERT somehow know all the error symbols or something? Or what am > > > I missing? > > > > Found what I was missing. Will install in a couple of minutes. > > Done. Running the tests now to find any that could be affected. All done, looks like we are ready to use this new error symbol.