• Home
  • Features
  • Pricing
  • Docs
  • Announcements
  • Sign In

zalando-incubator / postgres-operator / 979
11%
master: 24%

Build:
Build:
LAST BUILD BRANCH: set-human-role-var
DEFAULT BRANCH: master
Ran 16 Feb 2018 03:49PM UTC
Jobs 1
Files 31
Run time 1s
Badge
Embed ▾
README BADGES
x

If you need to use a raster PNG badge, change the '.svg' to '.png' in the link

Markdown

Textile

RDoc

HTML

Rst

pending completion
979

push

travis-ci

alexeyklyukin
Continue recreating the master pod after the failed failover.

Previously, the failover failure aborted the pod recreation process,
potentially leaving an 'old' version of the former master pod. With
these changes such a failure will not stop the process of recreating
pods.

There is one case when it would be more beneficial to retry the failover,
namely, when the failover failed because of the candidate (that is no
longer healthy, died or not available.) In that case it would be better
to retry with another candidate. However, Patroni API requires matching
text output against a known failure reason, and the chances of candidate's
failure during the pod recreating are not high enough to justify
additional complexity in the operator failure code.

545 of 4977 relevant lines covered (10.95%)

0.61 hits per line

Jobs
ID Job ID Ran Files Coverage
1 979.1 16 Feb 2018 03:49PM UTC 0
10.95
Travis Job 979.1
Source Files on build 979
  • List 0
  • Changed 2
  • Source Changed 2
  • Coverage Changed 2
Coverage ∆ File Lines Relevant Covered Missed Hits/Line
  • Back to Repo
  • Travis Build #979
  • 17e01100 on github
  • Prev Build on no_sync_failure_on_cluster_without_master (#917)
STATUS · Troubleshooting · Open an Issue · Sales · Support · CAREERS · ENTERPRISE · START FREE · SCHEDULE DEMO
ANNOUNCEMENTS · TWITTER · TOS & SLA · Supported CI Services · What's a CI service? · Automated Testing

© 2025 Coveralls, Inc