Bug #12058

[node manager] failing test

Added by Peter Amstutz almost 3 years ago. Updated almost 3 years ago.

Assigned To:
Target version:
Start date:
Due date:
% Done:


Estimated time:
Story points:


FAIL: test_unsatisfiable_jobs (tests.test_jobqueue.JobQueueMonitorActorTestCase)
Traceback (most recent call last):
  File "/home/peter/work/scripts/venv/local/lib/python2.7/site-packages/mock/mock.py", line 1305, in patched
    return func(*args, **keywargs)
  File "/home/peter/.arvbox/arvbox/arvados/services/nodemanager/tests/test_jobqueue.py", line 169, in test_unsatisfiable_jobs
  File "/home/peter/work/scripts/venv/local/lib/python2.7/site-packages/mock/mock.py", line 925, in assert_called_with
    raise AssertionError('Expected call: %s\nNot called' % (expected,))
AssertionError: Expected call: cancel(uuid='zzzzz-8i9sb-zzzzzzzzzzzzzzz')
Not called


#1 Updated by Peter Amstutz almost 3 years ago

  • Description updated (diff)

#2 Updated by Lucas Di Pentima almost 3 years ago

Yesterday I run the unit tests on my local environment, and didn't got the test test_unsatisfiable_jobs to fail.
OTOH, some other tests failed sometimes, so I did a run with --repeat 30 for every test file, this is the result:

OK! test_arguments.py
OK! test_clientactor.py
OK! test_computenode_dispatch.py
ERROR! (1 every 1) test_computenode_dispatch_slurm.py
OK! test_computenode_driver_azure.py
OK! test_computenode_driver_ec2.py
OK! test_computenode_driver_gce.py
OK! test_computenode_driver.py
OK! test_computenode.py
OK! test_config.py
ERROR! (1 every 2 or 3) test_daemon.py
ERROR! (1 every 26) test_failure.py
OK! test_jobqueue.py
OK! test_nodelist.py
OK! test_status.py
OK! test_timedcallback.py

#3 Updated by Tom Morris almost 3 years ago

  • Target version set to Arvados Future Sprints

Also available in: Atom PDF