Edit report at https://bugs.php.net/bug.php?id=65384&edit=1
ID: 65384 Updated by: m...@php.net Reported by: ni...@php.net Summary: pg_last_notice test failures Status: Assigned Type: Bug Package: PostgreSQL related PHP Version: 5.5.2RC1 Assigned To: yohgaki Block user comment: N Private report: N New Comment: Could it just be that they configured client_min_messages=WARNING? Previous Comments: ------------------------------------------------------------------------ [2013-08-05 01:18:45] yohg...@php.net I cannot reproduce on my Fedora19 and PHP 5.5 branch [yohgaki@dev PHP-5.5]$ rpm -q postgresql postgresql-9.2.4-1.fc19.x86_64 Anyone know what the PostgreSQL version on Travis CI? ------------------------------------------------------------------------ [2013-08-03 15:04:51] ni...@php.net Description: ------------ The following pg_last_notice related tests currently fail on Travis CI: PostgreSQL notice function [ext/pgsql/tests/09notice.phpt] Bug #32223 (weird behaviour of pg_last_notice) [ext/pgsql/tests/80_bug32223.phpt] Bug #32223 (weird behaviour of pg_last_notice using define) [ext/pgsql/tests/80_bug32223b.phpt] The diffs are: 09notice.phpt: 001+ Cannot find notice message in hash 002+ bool(false) 003+ 001- Notice: pg_query(): %s already a transaction in progress in %s on line %d 002- %s already a transaction in progress 80_bug32223.phpt: 005+ bool(false) 005- string(14) "NOTICE: 11111" 80_bug32223b.phpt: 005+ bool(false) 005- string(14) "NOTICE: 11111" ------------------------------------------------------------------------ -- Edit this bug report at https://bugs.php.net/bug.php?id=65384&edit=1
