fix(recipes): retry setup-apkrepos until the apk lock frees - #35
Conversation
setup-apkrepos runs apk update internally and takes no --wait flag, so another apk holding the database lock fails it with exit 99. That is the line the provision kept dying on, since --wait only covers apk add. Each Alpine recipe now retries setup-apkrepos, up to ~60s, so a brief lock hold waits the holder out instead of aborting the run. The until condition keeps set -e from tripping on a locked-out attempt.
|
Warning Review limit reached
Next review available in: 40 minutes You've used all free OSS reviews for now. Wait for the free limit to reset to keep reviewing this public repository. How can I continue?After more reviews become available, a review can be triggered using the To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews. How do review limits work?CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability. For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window. Please refer docs for additional details. Review details⚙️ Run configurationConfiguration used: Organization UI Review profile: ASSERTIVE Plan: Pro Plus Run ID: 📒 Files selected for processing (4)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
1 participant
Follow-up to the apk-lock work.
setup-apkreposrunsapk updateinternally and takes no--waitflag, so the earlier--waitchange could not cover it. That is the exact line provision runs kept dying on with exit 99:Unable to lock database: Resource temporarily unavailable.Each Alpine recipe (devtools, docker, tailscale, xfce) now retries
setup-apkreposfor up to ~60s, so a brief lock hold from any apk waits the holder out instead of aborting the run. Theuntilcondition keepsset -efrom tripping on a locked-out attempt.The per-VM provision lock removes stoat-side contention; this retry covers the rest (a boot-time apk, or someone sshing in mid-run).
just check,just test, andsh -non all four scripts pass.