util-linux.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Chris Hofstaedtler <zeha@debian.org>
To: Karel Zak <kzak@redhat.com>
Cc: linux-kernel@vger.kernel.org, linux-fsdevel@vger.kernel.org,
	util-linux@vger.kernel.org
Subject: Re: [ANNOUNCE] util-linux v2.38-rc1
Date: Mon, 31 Jan 2022 20:23:37 +0100	[thread overview]
Message-ID: <20220131192337.lzpofr4pz3lhgtl3@zeha.at> (raw)
In-Reply-To: <20220131151432.mfk62bwskotc6w64@ws.net.home>

Hello,

* Karel Zak <kzak@redhat.com> [220131 16:15]:
> 
> The util-linux release v2.38-rc1 is available at
>      
>   http://www.kernel.org/pub/linux/utils/util-linux/v2.38/
>      
> Feedback and bug reports, as always, are welcomed.

Thanks.

Some lsfd tests appear to fail in a Debian sbuild build environment,
in that they differ in the expected/actual values of DEV[STR] (see
below). I did not find time to investigate this closer, but thought
it would be best to report it sooner than later.

Best,
Chris

---snip---
     script: /<<PKGBUILDDIR>>/tests/ts/lsfd/mkfds-ro-regular-file
   commands: /<<PKGBUILDDIR>>/
    helpers: /<<PKGBUILDDIR>>/
    sub dir: /<<PKGBUILDDIR>>/tests/ts/lsfd
    top dir: /<<PKGBUILDDIR>>/tests
       self: /<<PKGBUILDDIR>>/tests/ts/lsfd
  test name: mkfds-ro-regular-file
  test desc: read-only regular file
  component: lsfd
  namespace: lsfd/mkfds-ro-regular-file
    verbose: yes
     output: /<<PKGBUILDDIR>>/tests/output/lsfd/mkfds-ro-regular-file
  error log: /<<PKGBUILDDIR>>/tests/output/lsfd/mkfds-ro-regular-file.err
  exit code: /<<PKGBUILDDIR>>/tests/output/lsfd/mkfds-ro-regular-file.exit_code
   valgrind: /<<PKGBUILDDIR>>/tests/output/lsfd/mkfds-ro-regular-file.vgdump
   expected: /<<PKGBUILDDIR>>/tests/expected/lsfd/mkfds-ro-regular-file{.err}
 mountpoint: /<<PKGBUILDDIR>>/tests/output/lsfd/mkfds-ro-regular-file-mnt

         lsfd: read-only regular file         ... FAILED (lsfd/mkfds-ro-regular-file)
========= script: /<<PKGBUILDDIR>>/tests/ts/lsfd/mkfds-ro-regular-file =================
================= OUTPUT =====================
     1  ABC         3  r--  REG /etc/passwd   1
     2  COMMAND,ASSOC,MODE,TYPE,NAME,POS: 0
     3  PID[RUN]: 0
     4  PID[STR]: 0
     5  INODE[RUN]: 0
     6  INODE[STR]: 0
     7  UID[RUN]: 0
     8  UID[STR]: 0
     9  USER[RUN]: 0
    10  USER[STR]: 0
    11  SIZE[RUN]: 0
    12  SIZE[STR]: 0
    13  MNTID[RUN]: 0
    14  DEV[RUN]: 0
    15  FINDMNT[RUN]: 0
    16  DEV[STR]: 1
================= EXPECTED ===================
     1  ABC         3  r--  REG /etc/passwd   1
     2  COMMAND,ASSOC,MODE,TYPE,NAME,POS: 0
     3  PID[RUN]: 0
     4  PID[STR]: 0
     5  INODE[RUN]: 0
     6  INODE[STR]: 0
     7  UID[RUN]: 0
     8  UID[STR]: 0
     9  USER[RUN]: 0
    10  USER[STR]: 0
    11  SIZE[RUN]: 0
    12  SIZE[STR]: 0
    13  MNTID[RUN]: 0
    14  DEV[RUN]: 0
    15  FINDMNT[RUN]: 0
    16  DEV[STR]: 0
================= O/E diff ===================
--- /<<PKGBUILDDIR>>/tests/output/lsfd/mkfds-ro-regular-file    2022-01-31 19:12:43.802603811 +0000
+++ /<<PKGBUILDDIR>>/tests/expected/lsfd/mkfds-ro-regular-file  2022-01-31 14:57:47.000000000 +0000
@@ -13,4 +13,4 @@
 MNTID[RUN]: 0
 DEV[RUN]: 0
 FINDMNT[RUN]: 0
-DEV[STR]: 1
+DEV[STR]: 0
==============================================

     script: /<<PKGBUILDDIR>>/tests/ts/lsfd/mkfds-rw-character-device
   commands: /<<PKGBUILDDIR>>/
    helpers: /<<PKGBUILDDIR>>/
    sub dir: /<<PKGBUILDDIR>>/tests/ts/lsfd
    top dir: /<<PKGBUILDDIR>>/tests
       self: /<<PKGBUILDDIR>>/tests/ts/lsfd
  test name: mkfds-rw-character-device
  test desc: character device with O_RDWR
  component: lsfd
  namespace: lsfd/mkfds-rw-character-device
    verbose: yes
     output: /<<PKGBUILDDIR>>/tests/output/lsfd/mkfds-rw-character-device
  error log: /<<PKGBUILDDIR>>/tests/output/lsfd/mkfds-rw-character-device.err
  exit code: /<<PKGBUILDDIR>>/tests/output/lsfd/mkfds-rw-character-device.exit_code
   valgrind: /<<PKGBUILDDIR>>/tests/output/lsfd/mkfds-rw-character-device.vgdump
   expected: /<<PKGBUILDDIR>>/tests/expected/lsfd/mkfds-rw-character-device{.err}
 mountpoint: /<<PKGBUILDDIR>>/tests/output/lsfd/mkfds-rw-character-device-mnt

         lsfd: character device with O_RDWR   ... FAILED (lsfd/mkfds-rw-character-device)
========= script: /<<PKGBUILDDIR>>/tests/ts/lsfd/mkfds-rw-character-device =================
================= OUTPUT =====================
     1      3  rw-  CHR /dev/zero  mem:5   0     1:5    mem    char  1:5
     2  ASSOC,MODE,TYPE,NAME,SOURCE,POS,MAJ:MIN,CHRDRV,DEVTYPE,RDEV: 0
     3  MNTID[RUN]: 0
     4  DEV[RUN]: 0
     5  FINDMNT[RUN]: 0
     6  DEV[STR]: 1
================= EXPECTED ===================
     1      3  rw-  CHR /dev/zero  mem:5   0     1:5    mem    char  1:5
     2  ASSOC,MODE,TYPE,NAME,SOURCE,POS,MAJ:MIN,CHRDRV,DEVTYPE,RDEV: 0
     3  MNTID[RUN]: 0
     4  DEV[RUN]: 0
     5  FINDMNT[RUN]: 0
     6  DEV[STR]: 0
================= O/E diff ===================
--- /<<PKGBUILDDIR>>/tests/output/lsfd/mkfds-rw-character-device        2022-01-31 19:12:44.358597427 +0000
+++ /<<PKGBUILDDIR>>/tests/expected/lsfd/mkfds-rw-character-device      2022-01-31 14:57:47.000000000 +0000
@@ -3,4 +3,4 @@
 MNTID[RUN]: 0
 DEV[RUN]: 0
 FINDMNT[RUN]: 0
-DEV[STR]: 1
+DEV[STR]: 0
==============================================

---snip---


  parent reply	other threads:[~2022-01-31 19:23 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-01-31 15:14 [ANNOUNCE] util-linux v2.38-rc1 Karel Zak
2022-01-31 18:20 ` Samuel Thibault
2022-02-01 13:01   ` Karel Zak
2022-02-01 13:24     ` Samuel Thibault
2022-02-01 14:14   ` Karel Zak
2022-02-01 14:25     ` Samuel Thibault
2022-01-31 19:23 ` Chris Hofstaedtler [this message]
2022-02-01 14:17   ` Karel Zak
2022-02-02  9:57   ` Anatoly Pugachev
2022-02-02 14:21     ` Masatake YAMATO
2022-02-04 18:03       ` Masatake YAMATO
2022-02-06 16:47         ` Chris Hofstaedtler
2022-02-10  7:32           ` Masatake YAMATO
2022-02-26 19:27           ` Masatake YAMATO

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=20220131192337.lzpofr4pz3lhgtl3@zeha.at \
    --to=zeha@debian.org \
    --cc=kzak@redhat.com \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=util-linux@vger.kernel.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).