Skip to content

hypothesis tests are failing on master #2441

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

Closed
shoyer opened this issue Sep 26, 2018 · 1 comment
Closed

hypothesis tests are failing on master #2441

shoyer opened this issue Sep 26, 2018 · 1 comment

Comments

@shoyer
Copy link
Member

shoyer commented Sep 26, 2018

Example failure: https://travis-ci.org/pydata/xarray/jobs/433231165

============================= test session starts ==============================
platform linux -- Python 3.6.6, pytest-3.8.1, py-1.6.0, pluggy-0.7.1
hypothesis profile 'default' -> database=DirectoryBasedExampleDatabase('/home/travis/build/pydata/xarray/.hypothesis/examples')
rootdir: /home/travis/build/pydata/xarray, inifile: setup.cfg
plugins: cov-2.6.0, hypothesis-3.73.1
collected 0 items / 1 errors                                                   
==================================== ERRORS ====================================
______________ ERROR collecting properties/test_encode_decode.py _______________
properties/test_encode_decode.py:16: in <module>
    settings.deadline = None
../../../miniconda/envs/test_env/lib/python3.6/site-packages/hypothesis/_settings.py:127: in __setattr__
    'to decorate your test instead.' % (name, value)
E   AttributeError: Cannot assign hypothesis.settings.deadline=None - the settings class is immutable.  You can change the global default settings with settings.load_profile, or use @settings(...) to decorate your test instead.
!!!!!!!!!!!!!!!!!!! Interrupted: 1 errors during collection !!!!!!!!!!!!!!!!!!!!
=========================== 1 error in 0.73 seconds ============================

cc @Zac-HD

@Zac-HD
Copy link
Contributor

Zac-HD commented Sep 26, 2018

Wow, this is embarrassing - I strengthened that check because I thought people might be relying on a silent no-op, and the first case I hear about... was me. Um. #2442 fixes it, at least?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants