You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jun 4, 2024. It is now read-only.
I'm seeing a similar (maybe related?) issue with a core dump on node:carbon-alpine (node@sha256:396b157f138a837de34fc48dc0ca8e37bf04d2fefc568e962acf429418950948 ) with sequelize using native postgres bindings.
It was working a week ago, in the mean time alpine has updated it's postgres (and libpq) version from 10.7-r0 to 11.2-r0
It does, however, work fine on my development machine. There are a lot of differences between my machine, my AWS instance, and your Travis CI instance, but the one similarity I can see between your failing TravisCI pipeline and my failing AWS VM is the kernel version 4.4.0. My dev machine is at 5.0.9.
TravicCI: 4.4.0-101-generic
Failing EC2: 4.4.0-1074-aws (based on ami-09677e0a6b14905b0)
Test suite on Travis using Node 11 seems to fail with a segmentation fault.
(cfr. https://travis-ci.org/brianc/node-pg-native/jobs/492244123)
Associated PR for Node 11 testing using Travis: #77
The text was updated successfully, but these errors were encountered: