[
https://issues.apache.org/jira/browse/MESOS-8124?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16388048#comment-16388048
]
Benjamin Bannier commented on MESOS-8124:
-----------------------------------------
Another failure from parallel test execution:
{noformat}
1 out of 1903 tests failed
[ RUN ] PosixRLimitsIsolatorTest.TaskExceedingLimit
../src/tests/containerizer/posix_rlimits_isolator_tests.cpp:342: Failure
Expected: TASK_STARTING
To be equal to: statusStarting->state()
Which is: TASK_FAILED
Ready
../src/tests/containerizer/posix_rlimits_isolator_tests.cpp:344: Failure
Failed to wait 15secs for statusRunning
../src/tests/containerizer/posix_rlimits_isolator_tests.cpp:333: Failure
Actual function call count doesn't match EXPECT_CALL(sched,
statusUpdate(&driver, _))...
Expected: to be called 3 times
Actual: called once - unsatisfied and active
[ FAILED ] PosixRLimitsIsolatorTest.TaskExceedingLimit (16986 ms)
{noformat}
It might make sense to think of a not time-based limit to reduce this kind of
flakiness.
> PosixRLimitsIsolatorTest.TaskExceedingLimit is flaky.
> -----------------------------------------------------
>
> Key: MESOS-8124
> URL: https://issues.apache.org/jira/browse/MESOS-8124
> Project: Mesos
> Issue Type: Bug
> Components: test
> Reporter: Benjamin Mahler
> Priority: Major
> Labels: flaky-test
> Attachments: failed.txt, success.txt
>
>
> This test fails flaky on CI:
> {noformat}
> ../../src/tests/containerizer/posix_rlimits_isolator_tests.cpp:348: Failure
> Failed to wait 15secs for statusFailed
> ../../src/tests/containerizer/posix_rlimits_isolator_tests.cpp:333: Failure
> Actual function call count doesn't match EXPECT_CALL(sched,
> statusUpdate(&driver, _))...
> Expected: to be called 3 times
> Actual: called twice - unsatisfied and active
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
