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

pulibrary / bibdata / e66f4c96-dbb8-4639-b652-e5dc920cc89b
91%
main: 91%

Build:
Build:
LAST BUILD BRANCH: signoz_two_electric
DEFAULT BRANCH: main
Ran 13 May 2026 02:13PM UTC
Jobs 2
Files 199
Run time 1min
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

13 May 2026 02:07PM UTC coverage: 90.522%. Remained the same
e66f4c96-dbb8-4639-b652-e5dc920cc89b

Pull #3281

circleci

christinach
Update test method to run the batches considering only the parent bid and not the to_a
order of the redis ZRANGE. The ZRNAGE to_a order changes in sidekiq-pro 8 to be [child, parent]
so this test method will cause the spec that has an incremental and a full dump to fail
because the parent job will wait for all the children jobs that are inside the block to run and finish.
Then based on that test method it will run last with the sequence of the methods: reindex! will call .wipe! and delete the records that were indexed from the child.

notes:
zadd - a redis command that adds a member to a sorted set with a numeric score.
Redis sorted sets store members in order by their score.

Pro 7 — score based when Batch.new was called creation time + expiry:
m.zadd("batches", @created_f + expiry, bid)

Pro 8 — score based when the jobs block finishes, now + expiry:
m.zadd("batches", (Time.now + expiry).to_f, bid)

This difference changes to_a ordering only in tests because of the Sidekiq::Testing.inline!: with inline! the jobs calls perform_async which runs the job synchronously. this job calls index_next_dump
to_a order in pro7 is [parent,child] <- ZRANGE
to_a order in pro8 is [child, parent] <- ZRANGE

In pro7 the test assumes that to_a.last is the child because of the ZRANGE.
In pro8 the parent will not finish until everything inside the parent block has run. because of the ZRANGE if we use to_a.last the parent will wait for everyhting inside to run then it will run last and the reindex! will call .wipe! and delete the records that were indexed from the child. So in this case to_a.last will call the parent.

helps with upgrading sidekiq-pro to 8
https://github.com/pulibrary/bibdata/pull/3280/
Pull Request #3281: Update test method to run the batches considering only the parent bid and not the to_a

11012 of 12165 relevant lines covered (90.52%)

84.74 hits per line

Jobs
ID Job ID Ran Files Coverage
1 e66f4c96-dbb8-4639-b652-e5dc920cc89b.1 13 May 2026 02:13PM UTC 89
89.93
2 e66f4c96-dbb8-4639-b652-e5dc920cc89b.2 13 May 2026 02:18PM UTC 110
92.19
Source Files on build e66f4c96-dbb8-4639-b652-e5dc920cc89b
  • Tree
  • List 199
  • Changed 0
  • Source Changed 0
  • Coverage Changed 0
Coverage ∆ File Lines Relevant Covered Missed Hits/Line
  • Back to Repo
  • CircleCI Build #E66F4C96...
  • Pull Request #3281
  • PR Base - main (#91F000EF...)
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