Project

General

Profile

Actions
Copy link

Bug #1775

closed

expid vs expId cause test image for runDogPicker.php to fail

Added by Anchi Cheng about 12 years ago. Updated about 10 years ago.

Status:
Closed
Priority:
Urgent
Assignee:
Amber Herold
Category:
-
Target version:
Appion/Leginon 2.2.0
Start date:
05/02/2012
Due date:
% Done:

0%

Estimated time:
Affected Version:
Appion/Leginon 2.2.0
Show in known bugs:
No
Workaround:

Description

runJob.py error. It seems to only happen in the specific condition of testimage that is submitted to job management system with runJob.py because --expid is not defined in commandlist before passing to showOrSubmitCommand

Traceback (most recent call last):
File "/home/acheng/myami/appion/bin/runJob.py", line 46, in ?
agent.Main(sys.argv[1:])
File "/home/acheng/myami/appion/appionlib/apAgent.py", line 63, in Main
self.updateJobStatus(self.currentJob, hostJobId)
File "/home/acheng/myami/appion/appionlib/apAgent.py", line 164, in updateJobStatus
projDB = self.__initDB(jobObject, hostJobId)
File "/home/acheng/myami/appion/appionlib/apAgent.py", line 250, in __initDB
clustq['session'] = apDatabase.getSessionDataFromSessionId(jobObject.getExpId())
File "/home/acheng/myami/appion/appionlib/apGenericJob.py", line 159, in getExpId
return self.expId

Actions
Copy link

Also available in: Atom PDF