From: "Aurélien Lajoie" <orel@melix.net>
To: Util-Linux <util-linux@vger.kernel.org>
Cc: Bruce Dubbs <bruce.dubbs@gmail.com>
Subject: Re: util-linux-2.35.2 test failures
Date: Wed, 27 May 2020 01:07:14 +0200 [thread overview]
Message-ID: <CAA0A08W0S8ZnZXJ1D0VDnC6qZ4F0sYP_tr9qK7_7Fxi5HGOqAw@mail.gmail.com> (raw)
In-Reply-To: <6b88784c-b130-27d4-2ec5-0d25320dd6fb@gmail.com>
On Wed, May 27, 2020 at 12:34 AM Bruce Dubbs <bruce.dubbs@gmail.com> wrote:
>
> I'm getting three test failures and hope I can get someone to help.
>
> The test failures are ipcs/mk-rm-msg, ipcs/mk-rm-sem, and ipcs/mk-rm-shm.
>
> Concentrating on mk-rm-msg, I found on the system:
>
> ./tests/output/ipcs/mk-rm-msg
> ./tests/ts/ipcs/mk-rm-msg
> ./tests/expected/ipcs/mk-rm-msg
>
> The contents of the output and the expected files are identical:
How have you checked it ?
Can be trailing spaces, final break line or other thing like this.
Can you share the files and the result of ./run.sh ipcs launch from
tests directory?
>
> Message queue id: <was_number>
> 1
> Message queue id: <was_number>
>
> I am running the tests as a non-privileged user.
>
> If I run the commands:
>
> $ ipcmk -Q (returns 24)
> $ ipcs -q -i 24
> $ ipcrm -q 24
> $ echo $?
> 0
>
> Everything looks OK. Does anyone have an idea why this test (these
> tests) are failing?
>
> -- Bruce Dubbs
> LFS
next prev parent reply other threads:[~2020-05-26 23:07 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-26 22:34 util-linux-2.35.2 test failures Bruce Dubbs
2020-05-26 23:07 ` Aurélien Lajoie [this message]
2020-05-26 23:36 ` Bruce Dubbs
2020-05-27 3:11 ` Aurélien Lajoie
2020-05-27 3:43 ` Bruce Dubbs
2020-05-27 5:13 ` Bruce Dubbs
2020-05-27 13:11 ` Karel Zak
2020-05-27 15:55 ` Bruce Dubbs
2020-05-27 18:07 ` Bruce Dubbs
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=CAA0A08W0S8ZnZXJ1D0VDnC6qZ4F0sYP_tr9qK7_7Fxi5HGOqAw@mail.gmail.com \
--to=orel@melix.net \
--cc=bruce.dubbs@gmail.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.