Обсуждение: Fwd: Re: Buildfarm now building but with test failures
This is from Andras Bodor I am afraid, simply enabling ssl will not be enough to pass the test. Different databases with different pg_hba.conf configurations must be set up, as documented in certdir/README. I do not think, it can be expected from every buildfarm host, so ssl tests might be switched off by default, or we must streamline its customization. Andras > Mike, > > Thanks for the update. > > Yes, you have to enable ssl for the tests to succeed. > > > Curious about HEAD failing though . > > Dave Cramer > > dave.cramer(at)credativ(dot)ca > http://www.credativ.ca
On 04/01/12 21:34, Dave Cramer wrote: > This is from Andras Bodor > > I am afraid, simply enabling ssl will not be enough > to pass the test. Different databases with different > pg_hba.conf configurations must be set up, as > documented in certdir/README. > I do not think, it can be expected from every buildfarm > host, so ssl tests might be switched off by default, or > we must streamline its customization. > Andras > OK, it's going to require some thought as I haven't a clue how a buildfarm run can use different pg_hba.conf configurations. I'd suggest disabling the SSL tests that require bespoke pg_hba.confs in the short term so that we can get the build testing running again. Long term I'll see what is possible within the buildfarm framework, hopefully I'll get some time this weekend. Regards, -- Mike Fowler Registered Linux user: 379787
On 04/01/12 22:18, Mike Fowler wrote: > On 04/01/12 21:34, Dave Cramer wrote: >> This is from Andras Bodor >> >> I am afraid, simply enabling ssl will not be enough >> to pass the test. Different databases with different >> pg_hba.conf configurations must be set up, as >> documented in certdir/README. >> I do not think, it can be expected from every buildfarm >> host, so ssl tests might be switched off by default, or >> we must streamline its customization. >> Andras >> > > OK, it's going to require some thought as I haven't a clue how a > buildfarm run can use different pg_hba.conf configurations. I'd suggest > disabling the SSL tests that require bespoke pg_hba.confs in the short > term so that we can get the build testing running again. Long term I'll > see what is possible within the buildfarm framework, hopefully I'll get > some time this weekend. > > Regards, I had a look at the tests and with SSL enabled and 216 tests pass but 432 still fail. Looking at the the way the test suites are built there is no easy way to separate out the ones that are working from the ones that are not. I also noticed that the tests are looking for test databases for which there are no creation scripts - hostnossldb, hostdb, hostssldb, hostsslcertdb and certdb. It seems to me the simplest way to get the buildfarm running again is to apply the patch I've attached. Once applied I'll re-enable to cron jobs on the buildfarm. Regards, -- Mike Fowler Registered Linux user: 379787
Вложения
Mike, I committed this. let me know if the buildfarm passes Dave Cramer dave.cramer(at)credativ(dot)ca http://www.credativ.ca On Sun, Jan 15, 2012 at 11:25 AM, Mike Fowler <mike@mlfowler.com> wrote: > On 04/01/12 22:18, Mike Fowler wrote: >> >> On 04/01/12 21:34, Dave Cramer wrote: >>> >>> This is from Andras Bodor >>> >>> I am afraid, simply enabling ssl will not be enough >>> to pass the test. Different databases with different >>> pg_hba.conf configurations must be set up, as >>> documented in certdir/README. >>> I do not think, it can be expected from every buildfarm >>> host, so ssl tests might be switched off by default, or >>> we must streamline its customization. >>> Andras >>> >> >> OK, it's going to require some thought as I haven't a clue how a >> buildfarm run can use different pg_hba.conf configurations. I'd suggest >> disabling the SSL tests that require bespoke pg_hba.confs in the short >> term so that we can get the build testing running again. Long term I'll >> see what is possible within the buildfarm framework, hopefully I'll get >> some time this weekend. >> >> Regards, > > > I had a look at the tests and with SSL enabled and 216 tests pass but 432 > still fail. Looking at the the way the test suites are built there is no > easy way to separate out the ones that are working from the ones that are > not. I also noticed that the tests are looking for test databases for which > there are no creation scripts - hostnossldb, hostdb, hostssldb, > hostsslcertdb and certdb. It seems to me the simplest way to get the > buildfarm running again is to apply the patch I've attached. Once applied > I'll re-enable to cron jobs on the buildfarm. > > > Regards, > -- > Mike Fowler > Registered Linux user: 379787
> Mike, > > I committed this. let me know if the buildfarm passes > > Dave Cramer > > dave.cramer(at)credativ(dot)ca > http://www.credativ.ca > > Dave, The buildfarm has succesfully built. HEAD is still listed as a failure on the buildfarm reporting server as the logs were too old. It seems that you have 3 hours to build and test and the HEAD build exceeded that - a disadvantage of running it on an EC2 mirco instance I guess. I'll keep an eye on that over the next few days. Regards, -- Mike Fowler Registered Linux user: 379787