-
Notifications
You must be signed in to change notification settings - Fork 10
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
Remove usage of the report_builder
#710
base: main
Are you sure you want to change the base?
Conversation
I think the intention of the `report_builder` setting was to build a `Report` from various database tables, instead of from the `report_json` blob. However, it is unclear if that is actually faster, as some of the involved tables are slow to query, and the `files_array` field was doing a storage request anyway. So the code was still doing two storage requests (`chunks` and `files_array`) plus various SELECTs, instead of doing just two storage requests (`report_json` and `chunks`).
❌ 2 Tests Failed:
View the top 2 failed tests by shortest run time
To view individual test run time comparison to the main branch, go to the Test Analytics Dashboard |
❌ 2 Tests Failed:
View the top 2 failed tests by shortest run time
To view individual test run time comparison to the main branch, go to the Test Analytics Dashboard |
Codecov ReportAll modified and coverable lines are covered by tests ✅
@@ Coverage Diff @@
## main #710 +/- ##
==========================================
- Coverage 98.09% 91.10% -6.99%
==========================================
Files 434 434
Lines 36607 36512 -95
==========================================
- Hits 35911 33266 -2645
- Misses 696 3246 +2550
Flags with carried forward coverage won't be shown. Click here to find out more.
|
Test Failures Detected: Due to failing tests, we cannot provide coverage reports at this time. ❌ Failed Test Results:Completed 1683 tests with View the full list of failed testspytest
|
I think the intention of the
report_builder
setting was to build aReport
from various database tables, instead of from thereport_json
blob.However, it is unclear if that is actually faster, as some of the involved tables are slow to query, and the
files_array
field was doing a storage request anyway.So the code was still doing two storage requests (
chunks
andfiles_array
) plus various SELECTs, instead of doing just two storage requests (report_json
andchunks
).