[
https://issues.apache.org/jira/browse/MESOS-6907?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alexander Rojas updated MESOS-6907:
-----------------------------------
Description:
After playing with the latest patch solving MESOS-6484 we found out that the
modifications done introduce a flakyness in the test {{FutureTest.After3}}. The
flakyness occurs, depending on the machine and the load of it between once
every 10000 runs and once every 500000 runs, being most likely a race condition
in the code.
To reproduce run:
{code}
${MESOS_BUILD_DIR}/3rdparty/libprocess/libprocess-tests
--gtest_filter="*.After3" --gtest_repeat=-1 --gtest_break_on_failure
{code}
was:
After playing with the latest patch solving MESOS-6484 we found out that the
modifications done introduce a flakyness in the test {{FutureTest.After3}}. The
flakyness occurs, depending on the machine and the load of it between once
every 10000 runs and once every 500000 runs, being most likely a race condition
in the code.
To reproduce run:
{{${MESOS_BUILD_DIR}/3rdparty/libprocess/libprocess-tests
--gtest_filter="*.After3" --gtest_repeat=-1 --gtest_break_on_failure}}
> FutureTest.After3 is flaky
> --------------------------
>
> Key: MESOS-6907
> URL: https://issues.apache.org/jira/browse/MESOS-6907
> Project: Mesos
> Issue Type: Bug
> Components: libprocess
> Reporter: Alexander Rojas
>
> After playing with the latest patch solving MESOS-6484 we found out that the
> modifications done introduce a flakyness in the test {{FutureTest.After3}}.
> The flakyness occurs, depending on the machine and the load of it between
> once every 10000 runs and once every 500000 runs, being most likely a race
> condition in the code.
> To reproduce run:
> {code}
> ${MESOS_BUILD_DIR}/3rdparty/libprocess/libprocess-tests
> --gtest_filter="*.After3" --gtest_repeat=-1 --gtest_break_on_failure
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
