-
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
Report formatter base #64
Conversation
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.
Important concerns and I think we should wait until we cover urgent
section completely before merging.
database/scripts/generate_report.rb
Outdated
@@ -51,3 +50,4 @@ def generate_report(report_name, exclude_set) | |||
end | |||
|
|||
generate_report(options[:report_name], options[:exclude]) | |||
puts report_name |
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 is this needed?
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 default report name is the current DateTime. Because of this, the report name varies every minute.
The idea is to keep track of which report was generated.
JOB_URL_PATTERN = { | ||
/^gz|^sdformat|^ros_gz/ => 'https://build.osrfoundation.org/job/', | ||
/^[A-Z]ci/ => 'https://build.ros2.org/job/', | ||
/^nightly_/ => 'https://ci.ros2.org/job/', |
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.
What about packaging jobs?
I think this could cause a maintenance burden, can we pull this directly from database/fetcher?
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 database does not contain any information about the server we're fetching the information.
We can modify the fetcher to add a new domain
column to server_status
table. WDYT?
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.
That sounds good to me
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.
Like we had avoided it, but I think it's worth doing it now that we are favoring pulling the info coming from the dev repos
database/scripts/format_report.rb
Outdated
# These are not implemented yet!!! | ||
report['urgent']['test_regressions_consecutive'] = [] | ||
report['urgent']['test_regressions_flaky'] = [] |
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.
I think this PR should wait until this is finished, otherwise could be misleading even for the internal team.
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.
Agreed
c5dd1e0
to
2d14e8c
Compare
Current report with changes:
UrgentMaintenancePending |
Converted to draft until all urgent section is finished |
2d14e8c
to
c67c1d3
Compare
Current report:
UrgentTest regressions consecutive
MaintenancePending |
c67c1d3
to
295b236
Compare
Current state of report format: UrgentBuild regressions
Test regressions consecutive
Test regressions flaky
MaintenancePending |
@Blast545 I added the "Reports" column adding the URL. I think to prevent daily mentions to multiple issues we should wrap the links in backquotes (`). WDYT? EDIT: I applied the change from above. Let me know if you think leaving the link as normal is a better idea |
8b57921
to
b08b4dc
Compare
Current state of report format: UrgentBuild regressions
Test regressions consecutiveTest regressions
Warnings
Test regressions flakyTest regressions
MaintenancePending |
@Blast545 this is ready to be reviewed |
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.
This is great work!
Signed-off-by: Crola1702 <[email protected]>
Signed-off-by: Crola1702 <[email protected]>
Signed-off-by: Crola1702 <[email protected]>
Signed-off-by: Crola1702 <[email protected]>
Signed-off-by: Crola1702 <[email protected]>
Signed-off-by: Crola1702 <[email protected]>
Signed-off-by: Crola1702 <[email protected]>
Signed-off-by: Crola1702 <[email protected]>
Signed-off-by: Crola1702 <[email protected]>
Signed-off-by: Crola1702 <[email protected]>
Signed-off-by: Crola1702 <[email protected]>
Signed-off-by: Crola1702 <[email protected]>
b08b4dc
to
b3cc556
Compare
Description
Part of #57
#62 adds
generate_report.rb
script, which generates a json file with daily issues (e.g., buildfarm-report_2024-06-25_12-10.json). The idea is to parse this report into a Markdown format to be posted daily in buildfarmer log report.Current output is pretty simple:
Example output:
urgent
build_regressions
Emtpy!!test_regressions_consecutive
Emtpy!!test_regressions_flaky
maintenance
Emtpy!!jobs_failing
Emtpy!!gh_issues_reported
Emtpy!!tests_disabled
pending
Emtpy!!test_regressions_all
Emtpy!!test_regressions_known
Emtpy!!build_regressions_known