Closed dkoslicki closed 5 months ago
Fixed a lot of these due to a missing comma in the blocklist. The now failing tests are:
FAILED test_ARAX_expand.py::test_xdtd_expand - AssertionError: assert ('ERROR' == 'OK'
FAILED test_ARAX_expand.py::test_xdtd_multiple_categories - AssertionError: assert ('ERROR' == 'OK'
FAILED test_ARAX_expand.py::test_xdtd_different_predicates - AssertionError: assert ('ERROR' == 'OK'
FAILED test_ARAX_infer.py::test_xdtd_infer_castleman_disease_1 - AssertionError: assert 'ERROR' == 'OK'
FAILED test_ARAX_infer.py::test_xdtd_infer_castleman_disease_2 - AssertionError: assert 'ERROR' == 'OK'
FAILED test_ARAX_infer.py::test_xdtd_with_qg2 - AssertionError: assert 'ERROR' == 'OK'
FAILED test_ARAX_infer.py::test_xdtd_with_qg3 - AssertionError: assert 'ERROR' == 'OK'
FAILED test_ARAX_infer.py::test_xdtd_with_only_qg - AssertionError: assert 'ERROR' == 'OK'
fixed in commit https://github.com/RTXteam/RTX/commit/0f3af48b51ce4a3f6c3226017f46601b81f384ca that I forgot to reference.
So looks like this only needs attention from @chunyuma
Culprit seems to be here: https://github.com/RTXteam/RTX/blob/dev/code/ARAX/ARAXQuery/Infer/scripts/ExplianableDTD_db.py#L118-L120
Where self
has not response
attribute
All xDTD
tests pass now. I didn't fix any code but did the following three steps:
git pull origin
to update all recent changes and the changes in the master
branch from merging master
into dev
because I have recently updated the name of xDTD database to ExplainableDTD_v1.0_KG2.8.4.db.ExplainableDTD_v1.0_KG2.8.4.db
locally. Otherwise, you need to manually run python ARAX_database_manager.py
to update your local database (this is also the solution to fix issue 2257. /RTX/code/ARAX/ARAXQuery/Expand
directory and run python kp_info_cacher.py
(this is also the solution to fix issue 2252)Note that step 2 and 3 can't be done automatically. So we may need to pay attention to them because they might result in some test failures.
Now, in dev
branch, all tests have passed in my side locally.
Hi @chunyuma this is super helpful. I'm thinking that instructions (2) and (3) would be good additions to the Dev Info wiki page, right? Since they are relevant to setting up a local dev area in order to be able to successfully run tests (or troubleshooting when those tests won't all run):
@saramsey, I think David or someone has added those two instructions into the wiki page. I close this issue as it have been resolved.
While merging
master
intodev
did not result in any conflicts, there are newly failing tests:@edeutsch @saramsey , any idea who "owns" the standup and json query tests?