[
https://issues.apache.org/jira/browse/MESOS-7634?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16174241#comment-16174241
]
vandita commented on MESOS-7634:
--------------------------------
hi Vinod,
I tried the same docker script and same code from
https://github.com/vinodkone/mesos/tree/vinod/s390x on a local vm (s390x ) same
configuration,but it is not a ci slave. Other wise all the configurations are
same as the ci vm. The issue is not reproducible.Currently figuring out what is
the difference in the 2 vm's(mesos ci and local s390x vm)
> 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)
