Andrei Budnik commented on MESOS-7500:

The issue is caused by recompilation/relinking of an executable by libtool 
wrapper script. E.g. when we launch `mesos-io-switchboard` for the first time, 
executable might be missing, so wrapper script starts to compile/link 
corresponding executable. On slow machines compilation takes quite a while, 
hence these tests become flaky.

One possible solution is to pass 
 as $CONFIGURATION environment variable into docker helper script.

> Command checks via agent lead to flaky tests.
> ---------------------------------------------
>                 Key: MESOS-7500
>                 URL: https://issues.apache.org/jira/browse/MESOS-7500
>             Project: Mesos
>          Issue Type: Bug
>            Reporter: Alexander Rukletsov
>            Assignee: Gastón Kleiman
>              Labels: check, flaky-test, health-check, mesosphere
> Tests that rely on command checks via agent are flaky on Apache CI. Here is 
> an example from one of the failed run: https://pastebin.com/g2mPgYzu

This message was sent by Atlassian JIRA

Reply via email to