From: emacsomancer <emacsomancer@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: mu: update to 1.4
Date: Sun, 19 Apr 2020 17:56:53 +0200 [thread overview]
Message-ID: <20200419155653.7WpS6sYczZXE6zLprW4FxK1qraQNPIDhr_kNdGVt6z8@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-21131@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 2699 bytes --]
New comment by emacsomancer on void-packages repository
https://github.com/void-linux/void-packages/pull/21131#issuecomment-616168998
Comment:
> `xbps-src check` segfault.
This is odd, because while
`xbps-src check` does produce one failure:
```
make[1]: Entering directory '/builddir/mu-1.4/lib'
make check-recursive
make[2]: Entering directory '/builddir/mu-1.4/lib'
Making check in utils
make[3]: Entering directory '/builddir/mu-1.4/lib/utils'
make check-TESTS
make[3]: Leaving directory '/builddir/mu-1.4/lib/utils'
make[2]: Leaving directory '/builddir/mu-1.4/lib'
make[1]: Leaving directory '/builddir/mu-1.4/lib'
Making check in m4
make[1]: Entering directory '/builddir/mu-1.4/m4'
make[1]: Nothing to be done for 'check'.
make[1]: Leaving directory '/builddir/mu-1.4/m4'
Making check in man
make[1]: Entering directory '/builddir/mu-1.4/man'
make[1]: Nothing to be done for 'check'.
make[1]: Leaving directory '/builddir/mu-1.4/man'
Making check in lib
make[1]: Entering directory '/builddir/mu-1.4/lib'
make check-recursive
make[2]: Entering directory '/builddir/mu-1.4/lib'
Making check in utils
make[3]: Entering directory '/builddir/mu-1.4/lib/utils'
make check-TESTS
make[4]: Entering directory '/builddir/mu-1.4/lib/utils'
make[5]: Entering directory '/builddir/mu-1.4/lib/utils'
PASS: test-mu-util
../../build-aux/test-driver: line 107: 20588 Aborted "$@" > $log_file 2>&1
FAIL: test-mu-utils
PASS: test-mu-str
PASS: test-sexp-parser
lsPASS: test-command-parser
============================================================================
Testsuite summary for mu 1.4
============================================================================
# TOTAL: 5
# PASS: 4
# SKIP: 0
# XFAIL: 0
# FAIL: 1
# XPASS: 0
# ERROR: 0
============================================================================
```
Building it by hand on Void and running `make check` passes everything:
```
....
make[5]: Entering directory '/home/slade/Documents/sourcecode/mu/lib/utils'
PASS: test-mu-util
PASS: test-mu-utils
PASS: test-mu-str
PASS: test-sexp-parser
PASS: test-command-parser
============================================================================
Testsuite summary for mu 1.4
============================================================================
# TOTAL: 5
# PASS: 5
# SKIP: 0
# XFAIL: 0
# FAIL: 0
# XPASS: 0
# ERROR: 0
============================================================================
...
```
The package itself seems to work fine as far as I can tell - I've been using it extensively since yesterday. Maybe related to https://github.com/djcb/mu/issues/1187 ?
next prev parent reply other threads:[~2020-04-19 15:56 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-18 19:25 [PR PATCH] " emacsomancer
2020-04-19 10:58 ` sgn
2020-04-19 15:56 ` emacsomancer [this message]
2020-04-19 15:57 ` emacsomancer
2020-04-19 23:49 ` [PR PATCH] [Updated] " emacsomancer
2020-04-20 13:14 ` sgn
2020-04-20 13:34 ` sgn
2020-04-20 13:36 ` sgn
2020-04-20 15:23 ` emacsomancer
2020-04-20 16:08 ` [PR PATCH] [Closed]: " sgn
-- strict thread matches above, loose matches on Subject: below --
2020-04-18 15:22 [PR PATCH] " ralsei
2020-04-19 3:02 ` sgn
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=20200419155653.7WpS6sYczZXE6zLprW4FxK1qraQNPIDhr_kNdGVt6z8@z \
--to=emacsomancer@users.noreply.github.com \
--cc=ml@inbox.vuxu.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.
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 NNTP newsgroup(s).