[
https://issues.apache.org/jira/browse/AURORA-37?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13884805#comment-13884805
]
Kevin Sweeney commented on AURORA-37:
-------------------------------------
Doesn't look like there's a clear solution other than disabling or speeding up
the test - the timeout appears to be hard-coded to 2 minutes currently.
>From
>https://github.com/twitter/commons/blob/master/src/python/twitter/pants/python/test_builder.py#L105
{code}
105 # TODO(wickman) Expose these as configuratable parameters
106 TEST_TIMEOUT = Amount(2, Time.MINUTES)
107 TEST_POLL_PERIOD = Amount(100, Time.MILLISECONDS)
{code}
> investigate src.test.python.apache.aurora.executor.thermos_task_runner test
> timeout on builds.a.o
> -------------------------------------------------------------------------------------------------
>
> Key: AURORA-37
> URL: https://issues.apache.org/jira/browse/AURORA-37
> Project: Aurora
> Issue Type: Story
> Reporter: Jake Farrell
>
> Commit 343613a5c1c397b998e9dc086784c31a2d4d9109 by mkhutornenko
> Dropping scheduler_list_job_updates from aurora_admin
> Reviewed at https://reviews.apache.org/r/16834/
> causes src.test.python.apache.aurora.executor.thermos_task_runner test to
> timeout.
> local builds by both mkhutornenko and myself passed immediately afterwords
> and a secondary build on builds.a.o passed with no issues. open ticket to
> investigate why timeout occurred.
> https://builds.apache.org/job/Aurora/31
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)