Ping. Also, it would be nice to have our own test-only implementations of Timers etc.
On Tue, Dec 30, 2014 at 12:42 AM, Karthik Kambatla <[email protected]> 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. > > -- Karthik Kambatla Software Engineer, Cloudera Inc. -------------------------------------------- http://five.sentenc.es
