unofficial mirror of bug-guix@gnu.org 
 help / color / mirror / code / Atom feed
From: Tobias Geerinckx-Rice via Bug reports for GNU Guix <bug-guix@gnu.org>
To: Mark H Weaver <mhw@netris.org>
Cc: 44953@debbugs.gnu.org
Subject: bug#44953: lsof: LTlock test consistently fails (possibly due to btrfs)
Date: Sun, 29 Nov 2020 22:33:05 +0100	[thread overview]
Message-ID: <874kl7zw4u.fsf@nckx> (raw)
In-Reply-To: <87zh2zdgfh.fsf@netris.org>

[-- Attachment #1: Type: text/plain, Size: 883 bytes --]

Mark,

Mark H Weaver 写道:
> 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.

Thanks for the report!  I can reproduce this by formatting a btrfs 
image file and loop-mounting it to /tmp.

This looks like an upstream bug to me.  Do you have time to file 
one?  We're using the <https://github.com/lsof-org/lsof> upstream 
since Victor Abell retired.

Alternatively we could disable this test in Guix ‘for now’ with a 
comment--but we both know how long it will remain unfixed.

Side note: I tried to implement upstream's test workflow[0] but 
got new failures (i.e. we're not running all the tests yet).  I 
haven't tried fixing those yet.

Kind regards,

T G-R

[0]: 
https://github.com/lsof-org/lsof/pull/144#issuecomment-732204193

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 247 bytes --]

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

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-11-29 21:02 bug#44953: lsof: LTlock test consistently fails (possibly due to btrfs) Mark H Weaver
2020-11-29 21:25 ` Mark H Weaver
2020-11-29 21:33 ` Tobias Geerinckx-Rice via Bug reports for GNU Guix [this message]
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=874kl7zw4u.fsf@nckx \
    --to=bug-guix@gnu.org \
    --cc=44953@debbugs.gnu.org \
    --cc=me@tobias.gr \
    --cc=mhw@netris.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).