[
https://issues.apache.org/jira/browse/MESOS-7634?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16109485#comment-16109485
]
Vinod Kone commented on MESOS-7634:
-----------------------------------
Sorry for the delay in response.
We do not want to run the docker commands as root user for several reasons 1)
there are several mesos tests that when run under root inside docker do not
work 2) all the other distros/platforms we support run as non-root user so
would like to not make an exception for s390x if possible 3) running as a root
user inside the container means any changes to the kernel (e.g., cgroups) done
by the tests will potentially persist after the build finishes which we should
avoid.
Do you know why the test doesn't pass as a non-root user on s390x? I think we
need to find the root cause for this and fix it.
Also, when run as root user do all the tests (not just stout tests but also
mesos tests) pass?
> 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)
