On Thu, Sep 8, 2011 at 2:26 PM, Diego Novillo <dnovi...@google.com> wrote: > On Thu, Sep 8, 2011 at 08:20, Richard Guenther > <richard.guent...@gmail.com> wrote: > >> Cache the comparison result? If you specify a (minimum) revision >> required for testing just test against a cached revision that fulfils >> the requirement. Something I never implemented for ours. > > Nope. Build must be functionally independent from other state. If > the manifest of known failures lives together with the source code, > that's acceptable. Depending on previous builds is not.
It _does_ live with the source code. Think of implicitly "checking in" the build result with the tested revision. That's not different from your idea of checking in some sort of whitelist of fails. > This also > helps individual developers doing builds and packagers doing spins off > of the main source branches. A svn revision is unique. Or do you mean in other _repositories_? Then the repository:revision combination is unique. You don't test whole source tarballs, do you? Richard. > > Diego. >
