[
https://issues.apache.org/jira/browse/MESOS-7634?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16161209#comment-16161209
]
Prajakta Bhatekar commented on MESOS-7634:
------------------------------------------
Hi Vinod,
Looks like the failure in OsTest.ChownNoAccess is due to wrong status set by
FTS functions of gnulib.They are provided by gnutils(coreutils on Ubuntu)
package and are resposible for traversing the directory structure
For s390x, the status flag is set to FTS_DP(i.e PostOrder Directory) instead of
expected FTS_DNR(Unreadable Directory) for a directory with 0 permissions.
At line 47, in file 3rdparty/stout/include/stout/os/posix/chown.hpp
,"fts_info" status flag of FTSENT structure returned by fts_read() is set to
6(FTS_DP)-PostOrder directory . The expected value is 4(FTS_DNR) - Unreadable
directory. Thus default case gets executed and an error is not returned causing
assertion to fail.
Investigating on why the status flag is set differently on x86 and s390x.
> OsTest.ChownNoAccess fails on s390x machines
> --------------------------------------------
>
> Key: MESOS-7634
> URL: https://issues.apache.org/jira/browse/MESOS-7634
> Project: Mesos
> Issue Type: Bug
> Reporter: Vinod Kone
> Assignee: Nayana Thorat
>
> Running a custom branch of Mesos (with some fixes in docker build scripts for
> s390x) on s390x based CI machines throws the following error when running
> stout tests.
> {code}
> [ RUN ] OsTest.ChownNoAccess
> ../../../../3rdparty/stout/tests/os_tests.cpp:839: Failure
> Value of: os::chown(uid.get(), gid.get(), "one", true).isError()
> Actual: false
> Expected: true
> ../../../../3rdparty/stout/tests/os_tests.cpp:840: Failure
> Value of: os::chown(uid.get(), gid.get(), "one/two", true).isError()
> Actual: false
> {code}
> One can repro this by building Mesos from my custom branch here:
> https://github.com/vinodkone/mesos/tree/vinod/s390x
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
