[MESOS-7986] ExecutorHttpApiTest.ValidJsonButInvalidProtobuf and ExecutorHttpApiTest.NoContentType fail in parallel test execution

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Won't Fix
• Affects Version/s: 1.5.0
• Component/s: test
• Labels: flaky-test mesosphere
• Epic Link: parallel-tests
• Assignee: Unassigned
• Reporter: Benjamin Bannier
• Created: 18/Sep/17 11:35
• Updated: 24/Jan/19 20:20
• Resolved: 24/Jan/19 20:20

Description

When running cmake-built Mesos test in parallel, I reliably encounter failing ExecutorHttpApiTest.ValidJsonButInvalidProtobuf or ExecutorHttpApiTest.NoContentType,

$ ../support/mesos-gtest-runner.py ./src/mesos-tests -j10
[ RUN      ] ExecutorHttpApiTest.ValidJsonButInvalidProtobuf
../src/tests/executor_http_api_tests.cpp:197: Failure
Value of: (response).get().status
  Actual: "401 Unauthorized"
Expected: BadRequest().status
Which is: "400 Bad Request"
[  FAILED  ] ExecutorHttpApiTest.ValidJsonButInvalidProtobuf (17 ms)

[ RUN      ] ExecutorHttpApiTest.NoContentType
../src/tests/executor_http_api_tests.cpp:158: Failure
Value of: (response).get().status
  Actual: "401 Unauthorized"
Expected: BadRequest().status
Which is: "400 Bad Request"
[  FAILED  ] ExecutorHttpApiTest.NoContentType (20 ms)

The machine has 16 physical cores.