Project

General

Profile

Bug #923

celery version makes error

Added by Rogers, Chris almost 12 years ago. Updated over 11 years ago.

Status:
Closed
Priority:
Normal
Assignee:
Jackson, Mike
Category:
Online reconstruction
Target version:
MAUS-v0.2.0
Start date:
02 March 2012
Due date:
% Done:

100%

Estimated time:
Workflow:
New Issue

Description

I'm getting a test failure from latest version of celery 2.5.1 like

======================================================================
ERROR: Failure: ImportError (No module named registry)
----------------------------------------------------------------------
Traceback (most recent call last):
  File "/home/jenkins/workspace/MAUS_trunk_batch/label/heplnm071/third_party/install/lib/python2.7/site-packages/nose-1.1.2-py2.7.egg/nose/loader.py", line 390, in loadTestsFromName
    addr.filename, addr.module)
  File "/home/jenkins/workspace/MAUS_trunk_batch/label/heplnm071/third_party/install/lib/python2.7/site-packages/nose-1.1.2-py2.7.egg/nose/importer.py", line 39, in importFromPath
    return self.importFromDir(dir_path, fqname)
  File "/home/jenkins/workspace/MAUS_trunk_batch/label/heplnm071/third_party/install/lib/python2.7/site-packages/nose-1.1.2-py2.7.egg/nose/importer.py", line 86, in importFromDir
    mod = load_module(part_fqname, fh, filename, desc)
  File "/home/jenkins/workspace/MAUS_trunk_batch/label/heplnm071/build/test_mauscelery/test_mausworker.py", line 23, in <module>
    from mauscelery.mausworker import get_maus_configuration
  File "/home/jenkins/workspace/MAUS_trunk_batch/label/heplnm071/src/common_py/mauscelery/mausworker.py", line 49, in <module>
    from celery.worker.control.registry import Panel
ImportError: No module named registry

looks like they changed the code from 2.4.6 to 2.5.1 - short term patch is to hold at 2.4.6 for now.

#1

Updated by Jackson, Mike almost 12 years ago

My tests failed due to this too. The fix is to change the import to be

from celery.worker.control import Panel

#2

Updated by Tunnell, Christopher over 11 years ago

We can explicity set the version of code in the python_extras.bash install script. And I think there's an example, FYI.

#3

Updated by Jackson, Mike over 11 years ago

  • Status changed from Open to Closed
  • % Done changed from 0 to 100

Two possible solutions then. Mine is implemented in my branch.

#4

Updated by Rogers, Chris over 11 years ago

I prefer to follow the latest celery if we can (so we can access new features, patches) - I did use the specific version for the previous release just to get it out.

#5

Updated by Rogers, Chris over 11 years ago

  • Target version changed from Future MAUS release to MAUS-v0.2.0

Also available in: Atom PDF