Comment 2 for bug 419689

On Sat, Aug 29, 2009 at 6:59 AM, Francis J.
Lacoste<email address hidden> wrote:
> Running against stable would mean not doing integration testing against
> the missing revisions. Which is most likely to happen?
>
> Encountering a broken devel, encountering errors related to your changes
> or encountering integration problems?
>

The first one, in my experience.

> As the bug title is stated, I'd mark it as Won't fix.  Maybe what we are
> looking for is an option to ec2test to run it against --stable.
>
> Personnally, when I encountered a similar situation, I compared and my
> failures with the one of the failed build. And submitted again once the
> [testfix] revision was landed without using ec2test (because I confirmed
> that all the failures were identical, and thus not related to my
> branch).
>

But this is not ideal at all:
  - it's repeated work (you have to submit again)
  - it's extra thinking (you have to compare test results)
  - it's extra waiting (you have to wait for test fix)

I think none of this work is creating extra value for the customer,
particularly since the change is *guaranteed* to be tested against the
missing revisions by buildbot.

jml