hadoop-yarn-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Ted Yu <yuzhih...@gmail.com>
Subject Re: Long unit test runs
Date Wed, 14 Jan 2015 03:56:29 GMT
In HBase, tests are categorized.
See http://hbase.apache.org/book.html#hbase.unittests

Small tests are run in a single JVM.

Can YARN tests be categorized ?

Cheers

On Mon, Dec 29, 2014 at 11:12 AM, Karthik Kambatla <kasha@cloudera.com>
wrote:

> Hi folks,
>
> I am sure you all have noticed the time to run YARN unit tests has been
> increasing constantly. Shortening this will let us run more tests for
> individual patches (all yarn tests for changes to yarn-common etc.) and
> faster turnaround times.
>
> Attached is the sorted list of tests on CDH (slightly behind upstream
> branch-2, and uses FairScheduler). I propose we look at them in decreasing
> order of runtimes, and do the following:
> 1. Move tests using MiniYARNCluster to a separate profile or module that
> runs only on nightly builds and not pre-commit.
> 2. Where possible, use @BeforeClass instead of @Before.
> 3. Use mock clocks where possible instead of explicit sleeps in tests.
> 4. Where sleeps are required, split a long sleep into multiple shorter
> sleeps.
>
> Thoughts?
>
> --
> Karthik Kambatla
> Software Engineer, Cloudera Inc.
>
>

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message