[LTP] [PATCH] setpriority01: Fix failure on read-only machine
Hoang Nguyen
the_hoang0709@yahoo.com
Fri May 5 05:11:06 CEST 2017
Hi Alexey
I've realized that tst_brk did not exist immediately and it makes the return value become 36, while we need 32. cleanup() does not need to run in this case.
root@mx6q:~# ./setpriority01
tst_test.c:847: INFO: Timeout per run is 0h 05m 00s
setpriority01.c:120: CONF: /etc/passwd is not accessible
userdel: user 'ltp_setpriority01' does not exist
setpriority01.c:133: WARN: 'userdel -r ltp_setpriority01' failed: ENOENT
Summary:
passed 0
failed 0
skipped 0
warnings 1
root@mx6q:~# echo $?
36
Could you please to check it again?
Thanks and regards,
Hoang
On Tue, Apr 11, 2017 at 16:46, Alexey Kodanev<alexey.kodanev@oracle.com> wrote: Hi,
On 09.04.2017 11:38, the_hoang0709@yahoo.com wrote:
> Return 32 if /etc/passwd is read-only.
> Fixes: #137
> See also: #88
Applied both patches, thanks! Modified the last one a little bit:
added __GNU_SOURCE foreaccess() and renamed tst_brkm() to
tst_brk() as the test converted to newer LTP API.
Thanks,
Alexey
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.linux.it/pipermail/ltp/attachments/20170505/739f273c/attachment.html>
More information about the ltp
mailing list