-
Notifications
You must be signed in to change notification settings - Fork 2
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Implement job priorities in daily report #100
Conversation
28a857f
to
f7c9339
Compare
Generated reports: |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
overall lgtm, minor nits, can you post a preview of the report in .md format before merging for the sake of taking a look?
I would advise not merging it until we come back from ROSCon, just in case to avoid having the scripts broken while we are not around.
# Get only maximum score for each job | ||
error_score_jobs.each_value.map {|e| e.max}.sum.round(3) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Why do we need the maximum here? If you are iterating over the error flakiness in each of the jobs, isn't the total priority of them the complete sum?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The idea behind this is to reduce the "amount of priority" that we get when an error appears in a lot of jobs.
Signed-off-by: Crola1702 <cristobal.arroyo@ekumenlabs.com>
Signed-off-by: Crola1702 <cristobal.arroyo@ekumenlabs.com>
Signed-off-by: Crola1702 <cristobal.arroyo@ekumenlabs.com>
Signed-off-by: Crola1702 <cristobal.arroyo@ekumenlabs.com>
Signed-off-by: Crola1702 <cristobal.arroyo@ekumenlabs.com>
Signed-off-by: Crola1702 <cristobal.arroyo@ekumenlabs.com>
Signed-off-by: Crola1702 <cristobal.arroyo@ekumenlabs.com>
f7c9339
to
6cf6b2e
Compare
Description
With a lot of new issues been created in the buildfarm for both ROS and Gazebo projects, a way to compare issues by importance or 'priority' is a good enhancement to get rid of most issues.
Changes
get_known_issue_errors.sql
to get the error names and jobs from a github issue linkjob_priorities.csv
defined from Buildfarm Issue Triage spreadsheet