Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Investigate build failures for PostgreSQL on 3.1 and 3.2 #87

Closed
UndefinedOffset opened this issue Feb 9, 2016 · 0 comments
Closed

Investigate build failures for PostgreSQL on 3.1 and 3.2 #87

UndefinedOffset opened this issue Feb 9, 2016 · 0 comments
Labels
3.1.x 3.2.x investigating postgresql
Milestone
0.6.0

Comments

@UndefinedOffset
Copy link
Owner

Looks like potentially something introduced in 10a5246 is now causing the PostgreSQL builds to fail for 3.1 and 3.2 see here for an example.

In 3.1

[User Error]: Uncaught PHPUnit_Framework_Error_Warning: pg_query(): Query failed: ERROR:  current transaction is aborted, commands ignored until end of transaction block

In 3.2

[User Error]: Uncaught PHPUnit_Framework_Error_Warning: pg_query_params(): Query failed: ERROR:  current transaction is aborted, commands ignored until end of transaction block
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
3.1.x 3.2.x investigating postgresql
Projects
None yet
Milestone
0.6.0
Development

No branches or pull requests
1 participant
@UndefinedOffset