2009/3/5 Björn Tillenius <email address hidden>:
> Ok. That makes me wonder, was disabling the tests really appropriate
> here? That kind of defeats the purpose of having a testfix mode...
Agreed. A quick branch of db-devel and running the test locally in
isolation showed that it wasn't a spurious failure. Disabling the test
should be the last resort.
> It also makes me wonder, should we make ec2test fire up two instances,
> one that tests the branch against devel, and one against db-devel?
That's an idea, though in this case it might not have helped: the test
doesn't fail when run against devel; the problem is somewhere in
db-devel... I just haven't figured out where yet.
2009/3/5 Björn Tillenius <email address hidden>:
> Ok. That makes me wonder, was disabling the tests really appropriate
> here? That kind of defeats the purpose of having a testfix mode...
Agreed. A quick branch of db-devel and running the test locally in
isolation showed that it wasn't a spurious failure. Disabling the test
should be the last resort.
> It also makes me wonder, should we make ec2test fire up two instances,
> one that tests the branch against devel, and one against db-devel?
That's an idea, though in this case it might not have helped: the test
doesn't fail when run against devel; the problem is somewhere in
db-devel... I just haven't figured out where yet.