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

klarna / brod / 1071 / 1
79%
master: 80%

Build:
Build:
LAST BUILD BRANCH: klarna
DEFAULT BRANCH: master
Ran 10 May 2019 09:46PM UTC
Files 18
Run time 3s
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

10 May 2019 09:24PM UTC coverage: 79.648% (-0.04%) from 79.688%
1071.1

push

travis-ci

zmstone
Fix wrong handeling of empty fetch response.

Empty fetch response happens only in incremental fetch sessions.
The current parsing code is a copy-paste from kafka_protocol test_lib code
which is fine.
But the comment is wrong: It's fetch session not transactional session
which is a entirely different thing.
And the handling is even more wrong: In case empty fetch response is
received, it should not advance begin_offset, but keep retrying the one
used in the last fetch request, because essentially an empty
response implies no new offsets and no partition metadata change either.

2039 of 2560 relevant lines covered (79.65%)

5038.02 hits per line

Source Files on job 1071.1
  • Tree
  • List 0
  • Changed 13
  • Source Changed 1
  • Coverage Changed 13
Coverage ∆ File Lines Relevant Covered Missed Hits/Line
  • Back to Build 160
  • Travis Job 1071.1
  • fc3b54d3 on github
  • Prev Job for on fix-wrong-implementation-on-empty-fetch-response-handeling (#1069.1)
  • Next Job for on fix-wrong-implementation-on-empty-fetch-response-handeling (#1075.1)
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

© 2026 Coveralls, Inc