From: Cyril Hrubis <chrubis@suse.cz>
To: Naresh Kamboju <naresh.kamboju@linaro.org>
Cc: ltp@lists.linux.it,
Linux-Next Mailing List <linux-next@vger.kernel.org>,
open list <linux-kernel@vger.kernel.org>,
alexey.kodanev@oracle.com, the_hoang0709@yahoo.com,
Jan Stancek <jstancek@redhat.com>
Subject: Re: Linux-next-20190823: x86_64/i386: prot_hsymlinks.c:325: Failed to run cmd: useradd hsym
Date: Mon, 26 Aug 2019 12:41:27 +0200 [thread overview]
Message-ID: <20190826104127.GA14729@haruka> (raw)
In-Reply-To: <CA+G9fYtN2tjHZtjtc8isdsD5hF76teeh2-pngUp+uj3WYdj7jA@mail.gmail.com>
Hi!
> Do you see this LTP prot_hsymlinks failure on linux next 20190823 on
> x86_64 and i386 devices?
>
> test output log,
> useradd: failure while writing changes to /etc/passwd
> useradd: /home/hsym was created, but could not be removed
This looks like an unrelated problem, failure to write to /etc/passwd
probably means that filesystem is full or some problem happend and how
is remounted RO.
I do not see the kernel messages from this job anywhere at the job
pages, is it stored somewhere?
--
Cyril Hrubis
chrubis@suse.cz
WARNING: multiple messages have this Message-ID (diff)
From: Cyril Hrubis <chrubis@suse.cz>
To: ltp@lists.linux.it
Subject: [LTP] Linux-next-20190823: x86_64/i386: prot_hsymlinks.c:325: Failed to run cmd: useradd hsym
Date: Mon, 26 Aug 2019 12:41:27 +0200 [thread overview]
Message-ID: <20190826104127.GA14729@haruka> (raw)
In-Reply-To: <CA+G9fYtN2tjHZtjtc8isdsD5hF76teeh2-pngUp+uj3WYdj7jA@mail.gmail.com>
Hi!
> Do you see this LTP prot_hsymlinks failure on linux next 20190823 on
> x86_64 and i386 devices?
>
> test output log,
> useradd: failure while writing changes to /etc/passwd
> useradd: /home/hsym was created, but could not be removed
This looks like an unrelated problem, failure to write to /etc/passwd
probably means that filesystem is full or some problem happend and how
is remounted RO.
I do not see the kernel messages from this job anywhere at the job
pages, is it stored somewhere?
--
Cyril Hrubis
chrubis@suse.cz
next prev parent reply other threads:[~2019-08-26 10:34 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-26 9:47 Linux-next-20190823: x86_64/i386: prot_hsymlinks.c:325: Failed to run cmd: useradd hsym Naresh Kamboju
2019-08-26 9:47 ` [LTP] " Naresh Kamboju
2019-08-26 10:41 ` Cyril Hrubis [this message]
2019-08-26 10:41 ` Cyril Hrubis
2019-08-26 11:05 ` Jan Stancek
2019-08-26 11:05 ` [LTP] " Jan Stancek
2019-08-26 13:50 ` Naresh Kamboju
2019-08-26 13:50 ` [LTP] " Naresh Kamboju
2019-08-26 14:38 ` Jan Stancek
2019-08-26 14:38 ` [LTP] " Jan Stancek
2019-08-26 15:58 ` Trond Myklebust
2019-08-26 15:58 ` [LTP] " Trond Myklebust
2019-08-26 23:12 ` Jan Stancek
2019-08-26 23:12 ` [LTP] " Jan Stancek
2019-08-27 0:59 ` Trond Myklebust
2019-08-27 0:59 ` [LTP] " Trond Myklebust
2019-08-27 10:25 ` Jan Stancek
2019-08-27 10:25 ` [LTP] " Jan Stancek
2019-08-27 12:58 ` Trond Myklebust
2019-08-27 12:58 ` [LTP] " Trond Myklebust
2019-08-27 13:20 ` Jan Stancek
2019-08-27 13:20 ` [LTP] " Jan Stancek
2019-08-27 6:34 ` Naresh Kamboju
2019-08-27 6:34 ` [LTP] " Naresh Kamboju
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=20190826104127.GA14729@haruka \
--to=chrubis@suse.cz \
--cc=alexey.kodanev@oracle.com \
--cc=jstancek@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=ltp@lists.linux.it \
--cc=naresh.kamboju@linaro.org \
--cc=the_hoang0709@yahoo.com \
/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.