[
https://issues.apache.org/jira/browse/MESOS-9287?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16689639#comment-16689639
]
Vinod Kone commented on MESOS-9287:
-----------------------------------
Observed this via Windows Reviewbot.
{noformat}
[ RUN ] DockerFetcherPluginTest.INTERNET_CURL_FetchImage
'hadoop' is not recognized as an internal or external command,
operable program or batch file.
d:\dcos\mesos\mesos\src\tests\uri_fetcher_tests.cpp(358): error:
(fetcher.get()->fetch(uri, dir)).failure(): Collect failed: Unexpected 'curl'
output:
d:\dcos\mesos\mesos\3rdparty\stout\include\stout\tests\utils.hpp(46): error:
TearDownMixin(): Failed to rmdir 'C:\Users\jenkins\AppData\Local\Temp\XpsPZ0':
The process cannot access the file because it is being used by another process.
[ FAILED ] DockerFetcherPluginTest.INTERNET_CURL_FetchImage (7460 ms)
{noformat}
> DockerFetcherPluginTest.INTERNET_CURL_FetchImage is flaky
> ---------------------------------------------------------
>
> Key: MESOS-9287
> URL: https://issues.apache.org/jira/browse/MESOS-9287
> Project: Mesos
> Issue Type: Bug
> Affects Versions: 1.7.0
> Environment: Windows tests on Azure
> Reporter: Andrew Schwartzmeyer
> Priority: Minor
> Labels: ci, flaky, integration
>
> The test DockerFetcherPluginTest.INTERNET_CURL_FetchImage is flaky on the CI,
> probably due to the 60 second timeout. A 10 minute timeout would probably be
> sufficient for slow Azure networks and big Docker images.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
