Re: [cross-project-issues-dev] Why allowing Hudson to write to your down

[Ed Willink <ed@xxxxxxxxxxxxx>]

Hi

> > 3. run a build and examine the execution trace.
> I can feel my brain overflowing and numbing just at the thought of this. 
More practically; select a stable deterministic subset of the JUnit tests.

Extract selected JVM allocation statistics during the normal build test 
to determine an allocation signature
- number/size/order of allocation of some key classes

Validate that the signed candidate for promotion demonstrates the same 
JVM allocation signature for these JUnit tests.

Not 100% proof, but automatable, project-independent and certainly able 
to detect naive replacement.

    Regards

        Ed Willink