Ticket #1611 (new bug)

Opened 4 years ago

Last modified 4 years ago

t/library/pg.t fails with PostgreSQL 8.4.3 on ubuntu 9.10

Reported by: dukeleto Owned by:
Priority: normal Milestone:
Component: testing Version: 2.3.0
Severity: medium Keywords:
Cc: Language:
Patch status: Platform: linux

Description

$ prove -v t/library/pg.t 
t/library/pg.t .. 
1..43
ok 1 - load_bytecode
ok 2 - load_bytecode Pg
ok 3 - Pg class exists
ok 4 - con isa Pg;Conn
ok 5 - con is true after connect
ok 6 - con.status() == CONNECTION_OK 
ok 7 - status(PGconn) == CONNECTION_OK 
ok 8 - exec BEGIN called
ok 9 - res isa Pg;Result
ok 10 - res.resultStatus() == PGRES_COMMAND_OK 
ok 11 - notice receiver called
ok 12 - notice callback got a struct
not ok 13 - notice result is still ok
ok 14 - table created PGRES_COMMAND_OK 
ok 15 - insert row PGRES_COMMAND_OK 
ok 16 - select * PGRES_TUPLES_OK 
ok 17 - res.ntuples == 1
ok 18 - res.nfields == 3
ok 19 - res.fname(1) == "foo"
ok 20 - res.fname(1) == "bar"
ok 21 - res.fnumber("id") == 0
ok 22 - res.fnumber("bar") == 2
ok 23 - res.fnumber("no_such_col_name") == -1
ok 24 - getvalue(0, 1) == "a"
ok 25 - getvalue(0, 2) == "b"
ok 26 - insert w execParams PGRES_COMMAND_OK 
ok 27 - res.ntuples == 2
ok 28 - getvalue(1, 1) == "c"
ok 29 - getvalue(1, 2) == "d"
ok 30 - prepare PGRES_COMMAND_OK 
ok 31 - execPrepared PGRES_COMMAND_OK 
ok 32 - res.ntuples == 3
ok 33 - execPrepared PGRES_COMMAND_OK 
ok 34 - res.ntuples == 4
ok 35 - insert row PGRES_COMMAND_OK 
ok 36 - res.ntuples == 5
ok 37 - getvalue(4, 1) == "i"
ok 38 - getvalue(4, 2) == ""
ok 39 - getisnull(4, 1) == 0
ok 40 - getisnull(4, 2) == 1
ok 41 - ABORT succeeded
ok 42 - con.finish()
ok 43 - con is false after finish
Failed 1/43 subtests 

Test Summary Report
-------------------
t/library/pg.t (Wstat: 0 Tests: 43 Failed: 1)
  Failed test:  13
Files=1, Tests=43,  0 wallclock secs ( 0.01 usr  0.02 sys +  0.01 cusr  0.00 csys =  0.04 CPU)
Result: FAIL

Change History

Changed 4 years ago by dukeleto

My version of Parrot that this test was run on is r46303

Changed 4 years ago by moritz

I experience the same failure on Debian GNU/Linux stable ("lenny"), also with postgres 8.4.3 on parrot r46300

Changed 4 years ago by dukeleto

This problem continues. I just reproduced it at r48547 on 64bit linux, Ubuntu 10.04, gcc 4.4.3-4ubuntu5 and Postgres 9.0beta1.

Note: See TracTickets for help on using tickets.