On Mon, 2008-03-03 at 23:59 -0500, Tom Lane wrote:
Not sure what advantage you see here. As to the first argument: if
the
Koji build fails in a way that is reproducible on your own machine, that
says that you didn't bother to do a trial build before submitting to
Koji; which is surely not a habit that we should condone or encourage.
Right, I'm talking about the case where it doesn't fail on one's own
machine, due to build environment differences.
As to the second: the only way that separate build and test steps
save
any resources is if a significant percentage of build jobs don't get
tested, which again is not something that I think we should encourage or
optimize for.
I think it is OK if some rawhide builds don't get tested. What we
should ensure is that builds that we're going to ship in a
alpha/beta/real release are tested. Although really this discussion is
kind of silly until we have some sort of testing framework.