You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@aurora.apache.org by "Kevin Sweeney (JIRA)" <ji...@apache.org> on 2014/05/27 22:23:01 UTC

[jira] [Commented] (AURORA-459) CronIT.testJobsAreScheduled takes ~16 seconds

    [ https://issues.apache.org/jira/browse/AURORA-459?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14010216#comment-14010216 ] 

Kevin Sweeney commented on AURORA-459:
--------------------------------------

This is an integration test that actually ticks the clock (seems kinda reasonable for cron). Since the finest scheduling granularity we support is minutely this test has the potential to sleep up to 59.999 seconds. Maybe we should split out an integration test target from the main set of unit tests?

> CronIT.testJobsAreScheduled takes ~16 seconds
> ---------------------------------------------
>
>                 Key: AURORA-459
>                 URL: https://issues.apache.org/jira/browse/AURORA-459
>             Project: Aurora
>          Issue Type: Story
>          Components: Scheduler, Testing
>            Reporter: Bill Farner
>
> This test case noticeably slows down the build.  It would be great to speed this test up considerably without sacrificing coverage.



--
This message was sent by Atlassian JIRA
(v6.2#6252)