Open KirstieJane opened 5 years ago
Hi @KirstieJane ๐ Integration test fails on my iMac as well ๐There's also a whole bunch of warnings from running the test suite too, some deprecation warnings and some RemovedInPytest4Warning
. I'll create an issue with my output so we can see where the warnings are coming from and what might need updating. (Update: Issue #111 )
I run integration tests locally. But besides test_lm_against_fixture
the following tests test_rich_against_fixture
and test_gm_against_fixture
failed as well.
So far, only test_lm_against_fixture
is failing for me. Unless I set up a Python 3.6 environment, then 6 other tests fail. But none of those 6 are test_rich_against_fixture
or test_gm_against_fixture
.
Well, at least I figured out why 3 regression tests failing when I run them locally.
I used python3.5
to run regression tests, and I had 3 of them fail.
Switching to the python3.6
has helped to have only test_lm_against_fixture
failing, the one described in the issue.
Thanks @wingedRuslan :+1:. The failing in 3.5 is an issue I understand. The procedure we're testing involves randomisation and due to differences in pythons 3.5 and 3.6 even when we set a seed we don't get exactly the same thing. We used to have test fixtures for each python version, but while troubleshooting the local measures problem I've been just testing python 3.6. The test fixtures can be a bit of a pain to produce. Currently when I make them I create a minimal python environment in Anaconda, install only the dependencies of scona and then generate the fixtures. This can be a bit time consuming- does anyone have a smarter way of doing this?
We have a green tick on our CI but that's kind of a lie..... this line in the .travis.yml file is currently ignoring the integration test :sob:
Everything runs but we get a different hash for the
test_lm_against_fixture
test: https://travis-ci.org/WhitakerLab/scona/jobs/529092803#L548 (lm stands for local measures). That Travis report is from thekw-test-tests
branch which adds the regression test back in.From my recollection this runs correctly on @islast's local machine....but gets an error on Travis. So a first step is for someone to run these tests locally and see if they pass or fail on their own machine.
Checkout the development guide for a lot of instructions on how to run the code locally ๐พ