[
https://issues.apache.org/jira/browse/MESOS-7634?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16065327#comment-16065327
]
Vinod Kone commented on MESOS-7634:
-----------------------------------
Sorry for the delay in getting back.
It definitely did fail on the CI job.
https://builds.apache.org/view/M-R/view/Mesos/job/Mesos-s390x-WIP/14/BUILDTOOL=autotools,COMPILER=gcc,CONFIGURATION=--verbose%20--enable-libevent%20--enable-ssl,ENVIRONMENT=GLOG_v=1%20MESOS_VERBOSE=1,label_exp=mesos/console
https://builds.apache.org/view/M-R/view/Mesos/job/Mesos-s390x-WIP/14/BUILDTOOL=autotools,COMPILER=gcc,CONFIGURATION=--verbose,ENVIRONMENT=GLOG_v=1%20MESOS_VERBOSE=1,label_exp=mesos/console
Do you have ssh access to the VM that runs these Jenkins jobs? It is labeled
"mesos1". Maybe try to see if you can repro on that particular VM (running as
Jenkins user).
> 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
>
> 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)
