On Sunday 19 June 2005 15:42, Josh Berkus wrote:
What are they testing and how? How often?
Regression tests on PostgreSQL, their own php tests on phpPgAdmin, and
standard JDBC test on pgJDBC.
Tests are based on when there have been submissions to CVS. They are doing
their best to do tests
Robert,
I'd be interested in getting failure reports on phpPgAdmin... can you
put me in touch with someone wrt that ?
I'll post to you KL as soon as it's publicly available. Currently you
can only access the tests on Spike's intranet.
--
--Josh
Josh Berkus
Aglio Database Solutions
San
Andrew,
If people don't monitor the buildfarm then it isn't serving its purpose
of catching these things quickly.
Related to that , Spikesource has started their automated tests (which
currently include JDBC, php and phpPgAdmin as well as PostgreSQL). They have
a web services interface; I
Josh Berkus wrote:
Andrew,
If people don't monitor the buildfarm then it isn't serving its purpose
of catching these things quickly.
Related to that , Spikesource has started their automated tests (which
currently include JDBC, php and phpPgAdmin as well as PostgreSQL). They
Andrew,
Er, who?
www.spikesource.com. Also see my announcement to this list last Thursday.
What are they testing and how? How often?
Regression tests on PostgreSQL, their own php tests on phpPgAdmin, and
standard JDBC test on pgJDBC.
Tests are based on when there have been submissions to
Josh Berkus wrote:
I am expecting that for the most part people will want the lists of
state changes, rather than the lists of all builds or failures. Will
Spikesource tests track state changes?
They'd like to. CVS makes this kind of challenging.They'd be happy to
have
Andrew Dunstan wrote:
all: every build status received
failures: every non-OK build status received
all_changes: every time status changes
green_changes: every time status changes to/from OK
The digest mailing lists for these notifications are now alive.
Corresponding subscription
[from 2pc post mortem thread on -patches]
Stefan Kaltenbrunner wrote:
Looks suspicious, doesn't it. How long since you last tested on that
machine?
*argl* - it's not 2PC ...
the machine had some issues a week ago or so - but it looks like the
problem occured first here:
Andrew Dunstan [EMAIL PROTECTED] writes:
comments welcome (buildfarm exists to help people on this list - if you
want something speak up).
There are a number of buildfarm machines that don't seem to have *ever*
posted a successful run. In some cases this represents a genuine
portability issue
Tom Lane wrote:
Andrew Dunstan [EMAIL PROTECTED] writes:
comments welcome (buildfarm exists to help people on this list - if you
want something speak up).
There are a number of buildfarm machines that don't seem to have *ever*
posted a successful run. In some cases this represents
10 matches
Mail list logo
