Skip to content
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

Merged
merged 7 commits into from
Nov 6, 2024

Conversation

Crola1702
Copy link
Contributor

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

@Crola1702 Crola1702 self-assigned this Oct 9, 2024
@Crola1702 Crola1702 linked an issue Oct 9, 2024 that may be closed by this pull request
@Crola1702 Crola1702 force-pushed the Crola1702/implement-job-priorities branch from 28a857f to f7c9339 Compare October 18, 2024 17:04
@Crola1702
Copy link
Contributor Author

Copy link
Contributor

@Blast545 Blast545 left a 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.

database/scripts/get_known_issue_errors.sql Outdated Show resolved Hide resolved
database/scripts/lib/buildfarm_tools.rb Outdated Show resolved Hide resolved
Comment on lines +173 to +174
# Get only maximum score for each job
error_score_jobs.each_value.map {|e| e.max}.sum.round(3)
Copy link
Contributor

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?

Copy link
Contributor Author

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>
@Crola1702 Crola1702 force-pushed the Crola1702/implement-job-priorities branch from f7c9339 to 6cf6b2e Compare November 6, 2024 15:47
@Crola1702 Crola1702 merged commit 5bba611 into main Nov 6, 2024
1 check passed
@Crola1702 Crola1702 deleted the Crola1702/implement-job-priorities branch November 6, 2024 21:09
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Issue report priority calculation proposal
2 participants