-
Notifications
You must be signed in to change notification settings - Fork 120
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
Substituted sys.exit for corresponding exception, depending on the context. #719
Conversation
Do the tests pass? I had to make some changes after the last one |
Orherwise. I think this will be a great change for useability. |
Ugh, sorry @brentp, how does one run the tests in GEMINI? It's
Will have a look at that soon, brb. |
bash master-test.sh |
Yeah, I'm running into some issues both running the Making progress, will keep you posted.
|
I can pull it in and to the testing. I just use the gemini installer, then with the python that gemini installs, run |
Yes, same process here, it's just that those downloads will take a while to finish :/ Don't worry, I'll make tests pass no matter what. Have you guys considered to run those tests on smaller datasets (i.e: https:/brainstorm/tiny-test-data, if applicable), and then running it in a CI environment like bcbio does?: https:/chapmanb/bcbio-nextgen/blob/master/.travis.yml Very handy to spot bugs early and keep the tests running automatically on each pullrequest. |
yes, I have been pulling gemini out into separate modules (inheritance, geneimpacts, etc) for easier testing and continuous integration. once we have the new loader and gemini isn't dependent on the specific annotations, it will be simpler to have it rely on a small subset. that said, the functional tests in gemini are pretty comprehensive so it's nice to have them as a final defense. |
Wow, the output is quite sparse in that test... don't even know where to look at when tests fail :_S
A bit more context:
Any hints? |
so you can go and look at that test and see:
so that's one that is now an exception. YOu can probably change that section to something like:
if a test fails you can just run that specific test file (annotate-tool.sh) and modify to see what happened). |
@brentp, |
@brainstorm. I'm going to pull this in and figure out any remaining issues with the |
Absolutely, go ahead. Sorry I couldn't figure out what's going on with clinvar/eff :/ |
this is merged into master. thanks! |
Wow, thanks Brent! Wonder what was off with ClinVar et al :-S |
Now I see: 646109ce551a5 Thanks again! |
yeah, I introduced that change but didn't commit the change to tests. decide it was better to revert. thank you! |
Thanks @brentp for merging the previous related PR #712!
Here comes the followup on the exception system for GEMINI.
@robinandeer