Build analytics on Hydra builds #86
Labels
No labels
Compat/Breaking
Difficulty/Architectural
Difficulty/Easy
Difficulty/Hard
Help Wanted
Kind/Bug
Kind/Documentation
Kind/Enhancement
Kind/Feature
Kind/Testing
Priority/Critical
Priority/High
Priority/Low
Priority/Medium
Reviewed/Confirmed
Reviewed/Duplicate
Reviewed/Invalid
Reviewed/Won't Fix
Security
Silenced Alert
Status/Abandoned
Status/Blocked
Status/Need More Info
Status/Postponed
Tracking Issue
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference: afnix/infra#86
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Currently, we don't really know beyond what analytics Hydra provides on a certain attribute path in a jobset whether a certain derivation makes use of:
To better inform scheduling in the future, we can start learning this information. This is also useful to guide buying decisions for hardware upgrades.
May I ask if you have something in mind around that already? Sounds like cgroup accounting on the builder side for jobs might be useful (still a pending CL IIRC?), right? And this is something Hydra could gather already I guess.