From: Ivan Vilata i Balaguer <ivan@selidor.net>
To: 63280@debbugs.gnu.org
Subject: bug#63280: encfs: Fails to build (test segfaults)
Date: Fri, 19 May 2023 13:40:27 +0200 [thread overview]
Message-ID: <ZGdgK2Ht4TkUEFxf@sax> (raw)
In-Reply-To: <ZFPhfgNIuuB2dzL5@sax>
[-- Attachment #1: Type: text/plain, Size: 1417 bytes --]
Ivan Vilata i Balaguer (2023-05-04 18:46:54 +0200) wrote:
> Hi! It looks like one of the tests in package `encfs` consistently segfaults
> in the version of Guix shown below:
>
> ```
> […]
> commit: 3f8c4899a9a67bb509a603bd21dcfcfab88c0e8e
> ```
>
> This is the final part of the build log:
>
> ```
> starting phase `check'
> Running tests...
> /gnu/store/ygab8v4ci9iklaykapq52bfsshpvi8pw-cmake-minimal-3.24.2/bin/ctest --force-new-ctest-process
> Test project /tmp/guix-build-encfs-1.9.5.drv-0/build
> Start 1: unit
> 1/1 Test #1: unit .............................***Exception: SegFault 0.01 sec
> Running main() from /tmp/guix-build-encfs-1.9.5.drv-0/encfs-1.9.5/vendor/github.com/google/googletest/googletest/src/gtest_main.cc
> […]
> ```
>
> I saw a couple of encfs issues regarding segfaults in tests, but I don't think
> they're related: <https://github.com/vgough/encfs/issues/378>
> <https://github.com/vgough/encfs/issues/600>
I repeated the build with Guix commit 14c03807 and `encfs` tests failed in the
same way. I tested the fix in <https://github.com/vgough/encfs/issues/600>,
i.e. `guix build encfs --with-input=openssl=openssl@1.1.1q`, and the build
succeeded, tests and all. I also tried `--with-graft` instead of
`--with-input`, but the issue happened again.
I hope that this is useful!
--
Ivan Vilata i Balaguer -- https://elvil.net/
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2023-05-19 11:41 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-04 16:46 bug#63280: encfs: Fails to build (test segfaults) Ivan Vilata i Balaguer
2023-05-19 11:40 ` Ivan Vilata i Balaguer [this message]
2023-05-19 12:11 ` Ivan Vilata i Balaguer
2023-05-20 10:33 ` Ivan Vilata i Balaguer
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=ZGdgK2Ht4TkUEFxf@sax \
--to=ivan@selidor.net \
--cc=63280@debbugs.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 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).