From: Michael Albinus <michael.albinus@gmx.de>
To: "Basil L. Contovounesios" <contovob@tcd.ie>
Cc: 39491@debbugs.gnu.org, lg.zevlg@gmail.com,
Richard Stallman <rms@gnu.org>,
Stefan Monnier <monnier@iro.umontreal.ca>
Subject: bug#39491: 28.0.50; two bugs in battery-upower
Date: Thu, 11 Jun 2020 20:17:32 +0200 [thread overview]
Message-ID: <87lfkteabn.fsf@gmx.de> (raw)
In-Reply-To: <87ftb1zja1.fsf@tcd.ie> (Basil L. Contovounesios's message of "Thu, 11 Jun 2020 16:58:30 +0100")
"Basil L. Contovounesios" <contovob@tcd.ie> writes:
> --- a/test/lisp/battery-tests.el
> +++ b/test/lisp/battery-tests.el
> @@ -48,6 +48,69 @@ battery-linux-proc-apm-regexp
> (should (equal (match-string 8 str) "1792"))
> (should (equal (match-string 9 str) "min"))))
>
> +(ert-deftest battery-upower-state ()
> +(ert-deftest battery-upower-state-unknown ()
Shouldn't theses tests be skipped, unless battery-upower is used?
Something like
(skip-unless (eq battery-status-function #'battery-upower))
next prev parent reply other threads:[~2020-06-11 18:17 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-07 20:14 bug#39491: 28.0.50; two bugs in battery-upower Richard Stallman
2020-02-08 7:30 ` Eli Zaretskii
2020-02-08 8:10 ` lg.zevlg
2020-03-21 10:45 ` Nicolas Richard
2020-04-26 14:47 ` Eli Zaretskii
2020-04-26 15:44 ` Evgeny Zajcev
2020-04-26 16:53 ` Eli Zaretskii
2020-05-26 16:23 ` Eli Zaretskii
2020-05-26 16:42 ` Evgeny Zajcev
2020-05-26 16:45 ` Eli Zaretskii
2020-05-26 17:42 ` Stefan Monnier
2020-05-26 17:47 ` lg.zevlg
2020-05-27 3:19 ` Richard Stallman
2020-05-27 3:19 ` Richard Stallman
2020-05-27 13:59 ` Stefan Monnier
2020-05-28 3:15 ` Richard Stallman
2020-06-11 15:58 ` Basil L. Contovounesios
2020-06-11 18:17 ` Michael Albinus [this message]
2020-06-11 19:41 ` Basil L. Contovounesios
2020-06-18 15:48 ` Basil L. Contovounesios
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=87lfkteabn.fsf@gmx.de \
--to=michael.albinus@gmx.de \
--cc=39491@debbugs.gnu.org \
--cc=contovob@tcd.ie \
--cc=lg.zevlg@gmail.com \
--cc=monnier@iro.umontreal.ca \
--cc=rms@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.