-
Notifications
You must be signed in to change notification settings - Fork 33
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
Integration test currently broken #109
Comments
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 |
I run integration tests locally. But besides |
So far, only |
Well, at least I figured out why 3 regression tests failing when I run them locally. Failed tests with python3.5
1 Failed test with python3.6
|
Thanks @wingedRuslan 👍. 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. |
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 😭
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 👾
The text was updated successfully, but these errors were encountered: