unofficial mirror of bug-guix@gnu.org 
 help / color / mirror / code / Atom feed
From: Mark H Weaver <mhw@netris.org>
To: 44953@debbugs.gnu.org
Subject: bug#44953: lsof: LTlock test consistently fails (possibly due to btrfs)
Date: Sun, 29 Nov 2020 16:02:47 -0500	[thread overview]
Message-ID: <87zh2zdgfh.fsf@netris.org> (raw)

In the 'lsof' test suite, the 'LTlock' test consistently fails on my
system, possibly related to the fact that I use 'btrfs' for my local
filesystems.  Here's the relevant build log excerpt:

--8<---------------cut here---------------start------------->8---
Optional tests:
LTbigf ... OK
LTdnlc ... /tmp/guix-build-lsof-4.94.0.drv-0/lsof-4.94.0-checkout/tests found: 100.00%
           OK
LTlock ... lock mismatch: expected W, got " "
           lock mismatch: expected R, got " "
           lock mismatch: expected w, got " "
           lock mismatch: expected r, got " "
Failed tests: 1

make: *** [Makefile:118: opt] Error 1
command "make" "standard" "optional" failed with status 2
note: keeping build directory `/tmp/guix-build-lsof-4.94.0.drv-0'
builder for `/gnu/store/cgkl1prkfmaz7b7j37xlzyhh8nhqkdyw-lsof-4.94.0.drv' failed with exit code 1
build of /gnu/store/cgkl1prkfmaz7b7j37xlzyhh8nhqkdyw-lsof-4.94.0.drv failed
--8<---------------cut here---------------end--------------->8---

The following commit made this into a fatal build error, which I agree
is an improvement:

--8<---------------cut here---------------start------------->8---
commit 2bf502138c9c8cad945866061772fe0e1f4b7175
Author: Tobias Geerinckx-Rice <me@tobias.gr>
Date:   Mon Nov 23 05:05:41 2020 +0100

  gnu: lsof: Make test failures fatal.
  
  * gnu/packages/lsof.scm (lsof)[source]: Add patch to make test suite
  failures stop the build.
  * gnu/packages/patches/lsof-fatal-test-failures.patch: New file.
  * gnu/local.mk (dist_patch_DATA): Add it.
--8<---------------cut here---------------end--------------->8---

Previously, the same test failure occurred on my system with lsof-4.91,
but the failure was ignored and I didn't notice it until now.  Before
that, our lsof-4.89 package did not run the test suite, so I do not know
if it had the same bug.

     Mark




             reply	other threads:[~2020-11-29 21:04 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-11-29 21:02 Mark H Weaver [this message]
2020-11-29 21:25 ` bug#44953: lsof: LTlock test consistently fails (possibly due to btrfs) Mark H Weaver
2020-11-29 21:33 ` Tobias Geerinckx-Rice via Bug reports for GNU Guix
2020-11-30  1:30   ` Mark H Weaver
2020-12-05  1:57     ` raingloom
2021-10-15  4:15       ` Maxim Cournoyer
2021-10-15  9:11         ` Mark H Weaver
2021-10-15  4:29       ` Maxim Cournoyer
2022-06-09 21:23         ` Maxim Cournoyer

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=87zh2zdgfh.fsf@netris.org \
    --to=mhw@netris.org \
    --cc=44953@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).