CircleCI: use postgres user

[blueyed]

"root" is not available anymore?!

Ref: https://circleci.com/gh/lock8/pinax-stripe/1256

[blueyed]

Hmm, seems to have been some temporary problem?!
At least #591 still failed with this commit.
Closing for now.

[blueyed]

Seems to be required?! - not sure what happened in https://circleci.com/gh/pinax/pinax-stripe/8542?utm_campaign=vcs-integration-link&utm_medium=referral&utm_source=github-build-link though..

[jpic]

We had to hardcode the user too in another project too with a similar setup (python + pg + cci)

[jpic]

Note that we also needed to extend wait timeout from 10 secs (as specified by their docs) to 20:

betagouv/mrs@0fba65b
betagouv/mrs@09e5480

Then it started working again

[blueyed]

@jpic
Thanks.
Do you know why this is necessary now? Have the circleci/postgres Docker images changed?

[blueyed]

Included in #618.

[blueyed]

@paltman
It might make sense to change the codecov/patch status to not being required - it disallows me to merge this at least.
IIRC I've closed/re-opened to get it reported, but without luck apparently.
@codecov is having some issues in this regard since a while.

[paltman]

fixed

…

Sent from my iPhone

On Oct 9, 2018, at 4:31 PM, Daniel Hahler ***@***.***> wrote: @paltman It might make sense to change the codecov/patch status to not being required - it disallows me to merge this at least. IIRC I've closed/re-opened to get it reported, but without luck apparently. @codecov is having some issues in this regard since a while. — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub, or mute the thread.

[blueyed]

@paltman
Thanks, next would be the "This branch is out-of-date with the base branch" check (like seen above).
Often it is not really necessary to ensure this, and in the unlikely case it would break master it is usually easy to fix.
E.g. in this case it does not really make sense to run CI again, just because a doc typo fix was merged.

[paltman]

@blueyed agreed and done.