CI issue

[vitaly-t]

GitHub Actions started showing problems recently, with the following error:

Connection for invalid connection must report the right error
   Message:
     Expected 'getaddrinfo EAI_AGAIN base' to contain 'password authentication failed for user'.
   Stacktrace:
=============================================================================
Writing coverage object [/home/runner/work/pg-promise/pg-promise/coverage/coverage.json]
     Error: Expected 'getaddrinfo EAI_AGAIN base' to contain 'password authentication failed for user'.
    at jasmine.Spec.<anonymous> (/home/runner/work/pg-promise/pg-promise/test/db.spec.js:264:43)
    at listOnTimeout (internal/timers.js:557:[17](https://github.com/vitaly-t/pg-promise/actions/runs/5098248657/jobs/9255178557#step:8:18))
    at processTimers (internal/timers.js:500:7)

This error has nothing to do with the project itself, it just appeared on its own, and relates to CI.

Need help finding the cause and fixing it. Any help is welcome!

---

@dplewis You originally integrated CI to this project, so maybe you know how to fix this?

[thezanke]

This appears to be an error being caused by a test in db.spec.js. When pgp('blah-blah').connect() gets called, it's attempting to make a network connection. The test does expect there to be an error but not the error it's seeing; so you're seeing it as a matcher fail. The error the test expects to receive is one containing the text about "password authentication failure" but instead it's getting the "EAI_AGAIN" error, which is a DNS error in my experience.

Does this happen every time it runs or just intermittently?

[dplewis]

@vitaly-t Can you try to rerun the CI a few times to see if this issue still exists?

[vitaly-t]

Thank you everybody for your help, the issue is now resolved, and a new release 11.5.1 has been published.

The issue was, as @thezanke pointed, in a broken test, which weirdly, started failing for reasons outside this library. I had to amend an old test, in order to make it pass again.