Thread: Intermittent buildfarm failures in sequence test
Have a look at http://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=raven&dt=2011-01-05%2001%3A30%3A12 http://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=currawong&dt=2011-01-06%2002%3A30%3A01 I recall seeing a couple of similar failures in the past few weeks but can't dredge them up at the moment. The test case is pretty simple: CREATE SEQUENCE foo_seq; ALTER TABLE foo_seq RENAME TO foo_seq_new; SELECT * FROM foo_seq_new; SELECT nextval('foo_seq_new'); SELECT nextval('foo_seq_new'); SELECT * FROM foo_seq_new; DROP SEQUENCE foo_seq_new; In the failure reports, all the SELECTs give the expected values except that "log_cnt" in the last one is 31 instead of expected 32. Anybody have any idea what's causing that? I can't avoid the suspicion that this is a consequence of some replication-related hack or other, but I haven't been keeping close enough tabs to guess just what. regards, tom lane
I wrote: > Have a look at > http://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=raven&dt=2011-01-05%2001%3A30%3A12 > http://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=currawong&dt=2011-01-06%2002%3A30%3A01 > Anybody have any idea what's causing that? Oh, never mind. The failure mechanism is explained here: http://archives.postgresql.org/pgsql-hackers/2008-08/msg01359.php and the reason it's started to fail again in the past few days is that Peter didn't bother to update sequence_1.out here: http://git.postgresql.org/gitweb?p=postgresql.git;a=commitdiff;h=39b88432968a2f4c01c20948f12bf9c8e388474d Tut tut. regards, tom lane
Le 06/01/2011 16:03, Tom Lane a écrit : > Have a look at > http://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=raven&dt=2011-01-05%2001%3A30%3A12 > http://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=currawong&dt=2011-01-06%2002%3A30%3A01 > I recall seeing a couple of similar failures in the past few weeks but > can't dredge them up at the moment. > > The test case is pretty simple: > > CREATE SEQUENCE foo_seq; > ALTER TABLE foo_seq RENAME TO foo_seq_new; > SELECT * FROM foo_seq_new; > SELECT nextval('foo_seq_new'); > SELECT nextval('foo_seq_new'); > SELECT * FROM foo_seq_new; > DROP SEQUENCE foo_seq_new; > > In the failure reports, all the SELECTs give the expected values except > that "log_cnt" in the last one is 31 instead of expected 32. > > Anybody have any idea what's causing that? I can't avoid the suspicion > that this is a consequence of some replication-related hack or other, > but I haven't been keeping close enough tabs to guess just what. > > regards, tom lane > For information, I have the same with jaguar and centaur : http://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=jaguar&dt=2011-01-03%2004%3A00%3A02 http://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=centaur&dt=2011-01-04%2007%3A06%3A01 regards, maache mehdi (Pyrenet)