-
Notifications
You must be signed in to change notification settings - Fork 592
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
GenomicsDB Allele-specific Annotation Support and Bug Fixes #4261
GenomicsDB Allele-specific Annotation Support and Bug Fixes #4261
Conversation
Codecov Report
@@ Coverage Diff @@
## master #4261 +/- ##
=============================================
+ Coverage 78.463% 78.7% +0.237%
- Complexity 16440 16480 +40
=============================================
Files 1039 1040 +1
Lines 59173 59338 +165
Branches 9686 9706 +20
=============================================
+ Hits 46429 46699 +270
+ Misses 8993 8888 -105
Partials 3751 3751
|
There is a disabled test in |
@psfoley Did you just push another bug fix into this branch? Can you explain what the bug was, and create a github ticket with the bug description for our records? We really need tests for each of the fixes in this branch, as well -- currently there are only tests for the allele-specific annotation support. I may attempt to add some tests later today if time permits. |
@psfoley The branch is failing tests after your latest commit with the error:
|
@jamesemery and @droazen thank you for reviewing. @jamesemery I have enabled @droazen I incremented the GenomicsDB release that incorporates a fix for resizing LUTs when dealing with spanning deletions - this was a single line change in GenomicsDB that should fall under the umbrella of enabling allele-specific annotation support 3707. This updated jar has been uploaded, but isn't available on Maven yet (it should be within the next hour). I agree that additional tests should be added for the bugs that this PR addresses. I'll plan on adding tests for the two high priority fixes (4160 and 3736) this afternoon. |
The bug was in an internal structure of GenomicsDB reported by a user |
public void testGenomicsDBImportWithoutDBField() throws IOException { | ||
//Test for https://github.com/broadinstitute/gatk/issues/3736 | ||
final List<String> vcfInputs = Arrays.asList(NA_24385); | ||
final String workspace = createTempDir("genomicsdb-tests").getAbsolutePath() + "/workspace"; |
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've noticed that the indentation in your PRs is always a little off @psfoley -- for future PRs, you may want to look at your IDE settings. We generally set our IDEs to expand tabs into 4 spaces, which may be the issue here.
(Not a blocker for merge of this PR, however)
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.
👍
public void testLongWorkspacePath() throws IOException { | ||
//Test for https://github.com/broadinstitute/gatk/issues/4160 | ||
final List<String> vcfInputs = LOCAL_GVCFS; | ||
final String workspace = createTempDir("long_aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa_genomicsdb").getAbsolutePath() + "/should_not_fail_aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa"; |
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.
As discussed in person, can you open a separate PR that adds about 150 additional a's to this path @psfoley, and confirm that the test fails if you downgrade the GenomicsDB version in our build.gradle
? Thanks!
* Incremented GenomicsDB version - Allele annotation support and multiple bug fixes * Enabled GenomicsDBAlleleSpecificAnnotations Test * Increment version - Fix for resizing LUTs when dealing with spanning deletions * Added tests for Issues 4160 and 3736
This PR adds:
and fixes: