-
Notifications
You must be signed in to change notification settings - Fork 30
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 ReportDetails
/files_array
#911
Conversation
Codecov ReportAll modified and coverable lines are covered by tests ✅
✅ All tests successful. No failed tests found. Additional details and impacted files@@ Coverage Diff @@
## main #911 +/- ##
==========================================
- Coverage 96.23% 96.22% -0.01%
==========================================
Files 823 823
Lines 18972 18963 -9
==========================================
- Hits 18257 18248 -9
Misses 715 715
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Sentry. |
Codecov ReportAll modified and coverable lines are covered by tests ✅ ✅ All tests successful. No failed tests found. 📢 Thoughts on this report? Let us know! |
This PR includes changes to |
08efd1d
to
a22f1d5
Compare
This PR includes changes to |
a22f1d5
to
b6f7e58
Compare
This PR includes changes to |
❌ 4 Tests Failed:
View the top 3 failed tests by shortest run time
To view individual test run time comparison to the main branch, go to the Test Analytics Dashboard |
Test Failures Detected: Due to failing tests, we cannot provide coverage reports at this time. ❌ Failed Test Results:Completed 2637 tests with View the full list of failed testspytest
|
This removes all usage of `ReportDetails`. The base definitions still exist.
b6f7e58
to
90e7eb8
Compare
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 double checked and didn't see any impact of removing the ReportDetails
, files_array
usages as proposed here on the GraphQL apis and public REST apis.
Honestly, I'm puzzled why this was here in the first place? Did some digging in the history but didn't turn up anything obvious (my best guess is at some point we moved over from reading the results of the coverage reports in reports_reportdetails.files_array
and moved to a path at GCS at commits.report_storage_path
)?
All the places our frontend app fetches any files data, it appears to download from the GCS path at commits.report_storage_path
, so that's good, unaffected by this change.
I also smoke-tested clicked around the deployment at https://stage-app.codecov.dev/gh/codecov and didn't see anything out of place. So I think we should be good to go with this!
(disclaimer: I only lightly educated myself on the needs_recompute
logic that was edited in this PR but seems generally reasonable!)
Yes that was it, the The feature flag never made it, and I wanted to be extra careful rolling back all the changes. |
This removes all usage of
ReportDetails
. The base definitions still exist.