mesos-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Vinod Kone (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (MESOS-7634) OsTest.ChownNoAccess fails on s390x machines
Date Wed, 20 Sep 2017 15:58:00 GMT

    [ https://issues.apache.org/jira/browse/MESOS-7634?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16173396#comment-16173396
] 

Vinod Kone commented on MESOS-7634:
-----------------------------------

[~vandita] You said earlier that you were able to repro the issue with the docker script,
what changed? 
[~Prajakta Bhatekar] Were you able to repro?

> 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)

Mime
View raw message