ci: deploy to production#803
Merged
fricklerhandwerk merged 18 commits intoproductionfrom Feb 13, 2026
Merged
Conversation
This reverts commit deaf331. The calculation was too tight. It both OOMs on the evaluation and runs out of tmpfs disk space. Reverting so we can use staging for experimenting with evaluations again.
We never serialise the evaluated attribute, and the loop helper is not used anywhere.
This is a rather large change that does multiple things at once: - Rename a few helpers - Deduplicate derivations by degrees of freedom - Improve accuracy of time measurement We now capture the entire processing time for each data type separately. - Only add maintainers and licenses from the rolling release This is because we must assume that everything else is stale. There's a chance this can produce temporarily out-of-sync results: - A license is deprecated between commits A and B - `nixos-unstable-small` (B) evaluates before `nixos-unstable` (A) - State of A will be shown - Only when `nixos-unstable` (B) evaluates, state of B settles This can only be fixed by observing commit order, but this is far out of scope for this change. - Remove maintainers' GitHub handle uniqueness requirement While since recently, any given Nixpkgs commit will have unique GitHub handles, this is not necessarily true across commits. In particular this allows handling the special case where a maintainer changes GitHub IDs but recovers the handle: - commit A: id X, handle Y - commit B: id X, handle Z - commit C: id W, handle Y The change was primarily smoke-tested by running evaluations manually. This means, we're essentially relying on correctness by self-consistency via types and the logic being simple. It would be really good to have fine-grained tests of the desired behavior though (property testing would make most sense here).
This should have been part of the previous commit, but got lost in history rewrites.
We're not using that data for anything, but it takes up most of the space. So much that by now it's too much to meaningfully migrate around. If we ever need it, it can be recreated by evaluating the respective Nixpkgs commits.
Now that we're not tracking dependencies until further notice, there's no point in accessing the disk at all.
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
2 participants
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.
No description provided.