Update TMB Signature CategoryVariant matching#51
Conversation
Codecov ReportAttention: Patch coverage is
❌ Your patch status has failed because the patch coverage (29.41%) is below the target coverage (80.00%). You can increase the patch coverage or adjust the target coverage. Additional details and impacted files@@ Coverage Diff @@
## develop #51 +/- ##
===========================================
+ Coverage 86.07% 86.11% +0.03%
===========================================
Files 18 18
Lines 2398 2412 +14
===========================================
+ Hits 2064 2077 +13
- Misses 334 335 +1
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
|
Tested on POG2021 (high tmb) with both current and develop branch, with one 'mutation burden ' statement on graphkbdev and all 'high mutation burden' statements on graphkbstaging. All behaviors seems as expected. |
|
Passes integration tests as well |
The goal is to match to either 'high mutation burden high signature' or 'mutation burden high signature' for now, until we fix the data to use 'mutation burden high signature' only.
What a KbMatches record looks like before/after: