Skip to content
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

Test failure: IPython.parallel.tests.test_client.TestClient.test_purge_everything #2807

Closed
takluyver opened this issue Jan 18, 2013 · 3 comments · Fixed by #2808
Closed

Test failure: IPython.parallel.tests.test_client.TestClient.test_purge_everything #2807

takluyver opened this issue Jan 18, 2013 · 3 comments · Fixed by #2808

Comments

@takluyver
Copy link
Member

Traceback (most recent call last):
  File "/sp/lib/python/cpython-2.7/lib/python2.7/unittest/case.py", line 327, in run
    testMethod()
  File "/home/slave/jenkins/shiningpanda/f786c3c0/virtualenvs/ff035a1d/lib/python2.7/site-packages/IPython/parallel/tests/test_client.py", line 467, in test_purge_everything
    self.assertEqual(len(hist), 0, msg="hub history not empty")
  File "/sp/lib/python/cpython-2.7/lib/python2.7/unittest/case.py", line 511, in assertEqual
    assertion_func(first, second, msg=msg)
  File "/sp/lib/python/cpython-2.7/lib/python2.7/unittest/case.py", line 504, in _baseAssertEqual
    raise self.failureException(msg)
AssertionError: hub history not empty
    '1 != 0' = '%s != %s' % (safe_repr(1), safe_repr(0))
    'hub history not empty' = self._formatMessage('hub history not empty', '1 != 0')
>>  raise self.failureException('hub history not empty')

https://jenkins.shiningpanda-ci.com/ipython/job/ipython-multi/PLATFORM=debian6,PYTHON=CPython-2.7/343/testReport/IPython.parallel.tests.test_client/TestClient/test_purge_everything/

@minrk
Copy link
Member

minrk commented Jan 18, 2013

This is a case of async on a super slow VM. I'll try to make those tests more patient.

@minrk
Copy link
Member

minrk commented Jan 18, 2013

see #2808

@takluyver
Copy link
Member Author

OK, feel free to close this, if it's just another instance of the time-dependent bugs. I'm used to seeing them, I just filed this because it didn't look like the normal timeout messages I get.

@minrk minrk closed this as completed in 59bc5cd Jan 19, 2013
minrk added a commit that referenced this issue Jan 19, 2013
improve patience for slow Hub in client tests

adds a first step in `_wait_for_idle`, where it waits for all tasks to arrive before waiting for no tasks to be running.  On a super slow machine, it was possible for `_wait_for_idle` to return prematurely, before tasks had even started.

closes #2807
minrk added a commit to minrk/ipython that referenced this issue Jan 26, 2013
adds a first step in `_wait_for_idle`,
where it waits for all tasks to arrive before waiting for
no tasks to be running.  On a super slow machine,
it was possible for `_wait_for_idle` to return prematurely,
before tasks had even started.

ought to close ipython#2807
mattvonrocketstein pushed a commit to mattvonrocketstein/ipython that referenced this issue Nov 3, 2014
adds a first step in `_wait_for_idle`,
where it waits for all tasks to arrive before waiting for
no tasks to be running.  On a super slow machine,
it was possible for `_wait_for_idle` to return prematurely,
before tasks had even started.

ought to close ipython#2807
mattvonrocketstein pushed a commit to mattvonrocketstein/ipython that referenced this issue Nov 3, 2014
improve patience for slow Hub in client tests

adds a first step in `_wait_for_idle`, where it waits for all tasks to arrive before waiting for no tasks to be running.  On a super slow machine, it was possible for `_wait_for_idle` to return prematurely, before tasks had even started.

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

Successfully merging a pull request may close this issue.

2 participants