[
https://issues.apache.org/jira/browse/MESOS-7500?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16179000#comment-16179000
]
Andrei Budnik edited comment on MESOS-7500 at 9/25/17 2:18 PM:
---------------------------------------------------------------
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 [\-\-enable-fast-install=no
(--disable-fast-install)|http://mdcc.cx/pub/autobook/autobook-latest/html/autobook_85.html]
as $CONFIGURATION environment variable into docker helper script.
was (Author: abudnik):
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
[--disable-fast-install|http://mdcc.cx/pub/autobook/autobook-latest/html/autobook_85.html]
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: Andrei Budnik
> 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
(v6.4.14#64029)
