[MESOS-8635] Flaky tests on ARM

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Component/s: test
• Labels: arm
• Assignee: Tomasz Janiszewski
• Reporter: Tomasz Janiszewski
• Created: 05/Mar/18 12:19
• Updated: 24/May/18 09:18
• Resolved: 19/Mar/18 15:19

Description

Some tests are failing on ARM when ran together. When ran separately they are passing.

Problematic tests are listed below:

https://builds.apache.org/job/Mesos-Buildbot-ARM/BUILDTOOL=autotools,COMPILER=gcc,CONFIGURATION=--verbose%20--disable-java%20--disable-python,ENVIRONMENT=GLOG_v=1%20MESOS_VERBOSE=1,label_exp=arm/403/display/redirect?page=changes

[  FAILED  ] CommandExecutorCheckTest.CommandCheckDeliveredAndReconciled
[  FAILED  ] CommandExecutorCheckTest.HTTPCheckDelivered
[  FAILED  ] DefaultExecutorCheckTest.CommandCheckDeliveredAndReconciled
[  FAILED  ] DefaultExecutorCheckTest.CommandCheckStatusChange
[  FAILED  ] DefaultExecutorCheckTest.CommandCheckSeesParentsEnv
[  FAILED  ] DefaultExecutorCheckTest.CommandCheckSharesWorkDirWithTask
[  FAILED  ] DefaultExecutorCheckTest.CommandCheckTimeout
[  FAILED  ] DefaultExecutorCheckTest.MultipleTasksWithChecks
[  FAILED  ] DefaultExecutorCheckTest.HTTPCheckDelivered
[  FAILED  ] DefaultExecutorCheckTest.TCPCheckDelivered
[  FAILED  ] HealthCheckTest.DefaultExecutorCommandHealthCheck
[  FAILED  ] HealthCheckTest.DefaultExecutorWithDockerImageCommandHealthCheck

Issue Links

• relates to: MESOS-8949 DefaultExecutorCheckTest.CommandCheckSharesWorkDirWithTask is flaky
• relates to: MESOS-7500 Command checks via agent lead to flaky tests.