From: "Erik Šabič" <erik.sab@gmail.com>
To: Maxime Devos <maximedevos@telenet.be>
Cc: 55674@debbugs.gnu.org
Subject: [bug#55674] [PATCH 2/2] gnu: emacs-helpful: Update to 0.19.
Date: Fri, 27 May 2022 19:23:20 +0200 [thread overview]
Message-ID: <CABeAMA=dJ7N8GgReaM1S3iG0ctNSUFJrE3R6HMpBBTYqGZyqGQ@mail.gmail.com> (raw)
In-Reply-To: <56da0d503f04884a5b3e407c36db50c75517b90e.camel@telenet.be>
Okay, I figured it out. The test is indeed broken and
it's an easy fix. I will try sending a PR on github.
I have a lot to learn. I apologise for being a nuisance :)
Please tell me if there's anything else I can improve on.
Thank you!
here's a diff for the test:
diff --git a/test/helpful-unit-test.el b/test/helpful-unit-test.el
index a07aa8e..1a61a6f 100644
--- a/test/helpful-unit-test.el
+++ b/test/helpful-unit-test.el
@@ -119,7 +119,7 @@ bar")))
(should
(equal
(helpful--docstring #'test-foo-advised t)
- "Docstring here too.")))
+ "Docstring here too.\n\nThis function has :around advice:
`ad-Advice-test-foo-advised'.")))
(defun test-foo-no-docstring ()
nil)
On Fri, May 27, 2022 at 3:48 PM Maxime Devos <maximedevos@telenet.be> wrote:
>
> [Please keep 55675@debbugs.gnu.org in CC]
>
> Erik Šabič schreef op vr 27-05-2022 om 15:32 [+0200]:
> > Well it fails on a test defined like this:
> > (ert-deftest helpful--docstring ()
> > "Basic docstring fetching."
> > (should
> > (equal
> > (helpful--docstring #'test-foo t)
> > "Docstring here.")))
> >
> > And fails like so:
> > ...............s...s..Test helpful--docstring-advice backtrace:
>
>
> >
> > Test helpful--docstring-advice condition:
> >
> > (ert-test-failed
> > ((should
> > (equal
> > (helpful--docstring ... t)
> > "Docstring here too."))
> > :form
> > (equal "Docstring here too.\n\nThis function has :around
> > advice: `ad-Advice-test-foo-advised'." "Docstring here too.")
> > :value nil :explanation
> > (arrays-of-different-length 84 19 "Docstring here too.\n\nThis
> > function has :around advice: `ad-Advice-test-foo-advised'."
> > "Docstring here too." first-mismatch-at 19)))
> >
> > F............................................................s......
>
> Looks like a bug.
>
> > I don't know anything about emacs-ert. And I wasn't able to
> > figure out if it works for the upstream author.
> >
> > WDYT?
>
> I don't know if it fails for the upstream author, but I don't think
> that's relevant to Guix. More relevant I think, is that this bug
> appears in Guix, so it can cause problems for Guix users, so some
> fixing might be necessary.
>
> I don't know much about Emacs though, so you might need to contact
> upstream about the bug.
>
> Greetings,
> Maxime.
next prev parent reply other threads:[~2022-05-27 17:24 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-27 12:52 [bug#55675] [PATCH 1/2] gnu: emacs-elm-mode: Update to 0.21.0-1.1e27768 Erik Šabič
2022-05-27 12:52 ` [bug#55674] [PATCH 2/2] gnu: emacs-helpful: Update to 0.19 Erik Šabič
2022-05-27 13:12 ` Maxime Devos
[not found] ` <CABeAMAkLbQHB_aGAr_Tf8+1DPzjMSW1mKSUH6Zh7fPyZQCAeBg@mail.gmail.com>
2022-05-27 13:48 ` [bug#55675] " Maxime Devos
2022-05-27 17:23 ` Erik Šabič [this message]
2022-05-27 14:58 ` [bug#55674] Broken tests Erik Šabič
2022-05-29 5:05 ` [bug#55674] PR accepted yarl-baudig
2022-05-29 5:13 ` [bug#55674] [PATCH] gnu: emacs-helpful: Update to 209971b yarl-baudig
2022-05-29 7:41 ` Liliana Marie Prikler
2022-05-29 9:09 ` yarl-baudig
2022-05-29 10:12 ` Liliana Marie Prikler
2022-05-30 7:20 ` [bug#55674] [PATCH] gnu: emacs-helpful: Update to 0.19 yarl-baudig
2022-05-30 19:41 ` Liliana Marie Prikler
2022-05-30 21:11 ` yarl baudig
2022-06-04 7:00 ` bug#55674: " Liliana Marie Prikler
2022-05-27 13:21 ` [bug#55675] Question Erik Šabič
2022-05-27 13:49 ` Maxime Devos
2022-05-27 14:27 ` [bug#55675] emacs-dash Erik Šabič
2022-06-05 21:34 ` bug#55675: [PATCH 1/2] gnu: emacs-elm-mode: Update to 0.21.0-1.1e27768 Ludovic Courtès
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
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CABeAMA=dJ7N8GgReaM1S3iG0ctNSUFJrE3R6HMpBBTYqGZyqGQ@mail.gmail.com' \
--to=erik.sab@gmail.com \
--cc=55674@debbugs.gnu.org \
--cc=maximedevos@telenet.be \
/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 public inbox
https://git.savannah.gnu.org/cgit/guix.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).