[
https://issues.apache.org/jira/browse/MESOS-970?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15408302#comment-15408302
]
Bing Li commented on MESOS-970:
-------------------------------
It has been running for a week and still didn't finish.
Didn't see any errors. It's still going.
Looks like it spends most of the time on
SlaveAndFrameworkCount/HierarchicalAllocator_BENCHMARK_Test.DeclineOffers.
[ OK ]
SlaveAndFrameworkCount/HierarchicalAllocator_BENCHMARK_Test.DeclineOffers/0
(2274 ms)
[ OK ]
SlaveAndFrameworkCount/HierarchicalAllocator_BENCHMARK_Test.DeclineOffers/1
(961218 ms)
[ OK ]
SlaveAndFrameworkCount/HierarchicalAllocator_BENCHMARK_Test.DeclineOffers/2
(6008455 ms)
[ OK ]
SlaveAndFrameworkCount/HierarchicalAllocator_BENCHMARK_Test.DeclineOffers/3
(16382221 ms)
[ OK ]
SlaveAndFrameworkCount/HierarchicalAllocator_BENCHMARK_Test.DeclineOffers/4
(105058559 ms)
[ OK ]
SlaveAndFrameworkCount/HierarchicalAllocator_BENCHMARK_Test.DeclineOffers/5
(372416826 ms)
Now my s390x machine is running DeclineOffers/6.
And I have also an x86 machine which I started the run a little later. It's
running DeclineOffers/5.
I'm afraid the benchmark test takes too long. Not sure the test case
SlaveAndFrameworkCount/HierarchicalAllocator_BENCHMARK_Test.DeclineOffers is
changed on purpose or by accident.
> Upgrade bundled leveldb to 1.18
> -------------------------------
>
> Key: MESOS-970
> URL: https://issues.apache.org/jira/browse/MESOS-970
> Project: Mesos
> Issue Type: Improvement
> Components: replicated log
> Reporter: Benjamin Mahler
> Assignee: Tomasz Janiszewski
>
> We currently bundle leveldb 1.4, and the latest version is leveldb 1.18.
> Upgrade to 1.18 could solve the problems when build Mesos in some non-x86
> architecture CPU.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
