Repository navigation
Fix Mastodon runtime drift and Ferrum fuzz disk usage - #82
Merged
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Mastodon’s plus Dockerfile stayed on Ruby 4.0.7 after upstream moved to 4.0.8, failing all four plus jobs in run 39946643623. Generate the plus Dockerfile from each checked-out upstream version and apply only the compiler-cache changes. Preserve upstream runtime and library updates and the early
.ruby-versioncopy.Ferrum’s GitHub cache lane exhausted disk space with a 97.8 GB target directory in run 39939686067. Verify each fuzz executable after its successful smoke run, record completion, and remove its already-excluded executable and package objects before the next target. Apply the same cleanup to every provider, retain shared dependencies, and stop before verification or cleanup when a target fails.
Validation: 169 tests, 606 assertions, no failures; benchmark catalog and cache-interface checks; actionlint; shell syntax; generated Mastodon overlay against both its original Dockerfile and current upstream Ruby 4.0.8 / Node 26 / libvips 8.18.7. All PR checks, including CodeQL, passed. Hosted Mastodon verification passed all four plus lanes: BoringCache and GHA on x64 and ARM. Ferrum fresh GHA-plus verification is running. Full hosted workload verification remains pending.