Add a central validator that ensures mutual exclusion and collective exhaustion

[GoogleCodeExporter]

In order to make sure that the mutual exclusion and collective exhaustion 
requirement is maintained, we need to add a new call to the server where after 
partitioning the balancer sends its PARTITION_NUMBER and the pruned list of 
tests to the server. 

    Whenever a new PARTITION sends its tests, the server should make sure that constraints are maintained. If its not, it should return a 409 of sorts and the build should fail.

Original issue reported on code.google.com by singh.janmejay on 17 Dec 2010 at 8:04

• Blocked on: #95

[GoogleCodeExporter]

This is useful. We should do it asap.

Original comment by itspa...@gmail.com on 17 Jan 2011 at 8:50

• Added labels: Milestone-0.4

[GoogleCodeExporter]

Original comment by singh.janmejay on 10 Oct 2011 at 2:52

• Changed title: Add a central validator that ensures mutual exclusion and collective exhaustion
• Changed state: Started

[GoogleCodeExporter]

We'll need to implement a notion of module for multiple-module projects. The 
param will be defaulted to 'default-module' or something similar, but it will 
be configurable at build task level. This will trickle into support libraries 
too.

Balancer will use a stateful call which alien support libs will use to populate 
module-name before balancing call is made.

This makes the correctness-check story significantly bigger too.

Original comment by singh.janmejay on 7 Nov 2011 at 6:18

[GoogleCodeExporter]

merged to tlb master in: 9fbc3f7634036ba7b6f5ab1c5b872d74317157be
tlb_rb: dc7d602052a0451e2180b1cc10a77297308ada4d
sample_projects: ede2e45505fb987ebd71342b2511bd9a1f103490
site updated in: 8d0ea1bbe14850703d1104405ed451e3dfdd70da

Original comment by singh.janmejay on 13 Dec 2011 at 7:14

• Changed state: Fixed