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.

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

Failure in GitHub Actions CI #16

Open
parsonsmatt opened this issue Mar 9, 2021 · 1 comment
Open

Failure in GitHub Actions CI #16

parsonsmatt opened this issue Mar 9, 2021 · 1 comment

Comments

@parsonsmatt
Copy link

The persistent-postgresql CI is currently failing with an error message emitted by libpq, probably the underlying C library.

Cf yesodweb/persistent#1197

The error message is here:

Failures:

  src/MigrationTest.hs:41:5: 
  1) Migration is idempotent
       uncaught exception: IOException of type OtherError
       libpq: failed (server closed the connection unexpectedly
       	This probably means the server terminated abnormally
       	before or while processing the request.
       could not send SSL negotiation packet: Success
       )

  To rerun use: --match "/Migration/is idempotent/"

  test/PgIntervalTest.hs:37:5: 
  2) Postgres Interval Property tests Round trips
       uncaught exception: IOException of type OtherError
       libpq: failed (server closed the connection unexpectedly
       	This probably means the server terminated abnormally
       	before or while processing the request.
       could not send SSL negotiation packet: Success
       )
       (after 25 tests)
         15.333255892191s

I have no idea if this is happening for anyone else, but the only results for Googling it are my own tweets complaining about it. Posting here as a pointer to an issue in case anyone else runs across it.

@robx
Copy link
Contributor

robx commented Feb 20, 2023

This error is from libpq, and seems to indicate some networking issue. https://git.postgresql.org/gitweb/?p=postgresql.git;a=blob;f=src/interfaces/libpq/fe-connect.c;h=50b5df3490bfa77ef21e3a6aec56ca562b8f3995;hb=refs/heads/master#l2884

It doesn't appear that postgresql-libpq is at fault here. Judging by the fix in yesodweb/persistent#1197, the error seems to surface correctly as an exception.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants