You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
While writing #346, I realized the existing logs at https://r.ryantm.com/log/ could be used to build interesting statistics for the nixpkgs-update failure reasons.
The idea would be to crawl the (latest) logs at https://r.ryantm.com/log/ and collect data for the nixpkgs-update failure reasons. This data could then be used to categorize the errors and attempt to answer questions such as:
What are the most common nixpkgs-update failure reasons? Would it be possible to fix some of these in nixpkgs-update or in the packages themselves that fail to auto-update, to increase the number of packages that nixpkgs-update can update automatically?
Are there packages where nixpkgs-update has not even tried to run the update in the past N weeks? If there are, what's the reason for that?
I'm writing this suggestion here, in a hope to get notified in case someone has already done something like this earlier.
The text was updated successfully, but these errors were encountered:
While writing #346, I realized the existing logs at https://r.ryantm.com/log/ could be used to build interesting statistics for the nixpkgs-update failure reasons.
The idea would be to crawl the (latest) logs at https://r.ryantm.com/log/ and collect data for the nixpkgs-update failure reasons. This data could then be used to categorize the errors and attempt to answer questions such as:
I'm writing this suggestion here, in a hope to get notified in case someone has already done something like this earlier.
The text was updated successfully, but these errors were encountered: