Bug #1775
closedexpid vs expId cause test image for runDogPicker.php to fail
0%
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
Updated by Anchi Cheng about 12 years ago
- Status changed from Assigned to In Code Review
- Assignee changed from Anchi Cheng to Amber Herold
r16575 change it in processing.inc
This need to be merged to branch 2.2 once tested.
Testing:
1. choose an image to test DogPicker and submit it to cluster and it should run.
Updated by Amber Herold over 11 years ago
- Status changed from In Code Review to In Test
- Affected Version changed from Appion/Leginon 2.2.0 (trunk) to Appion/Leginon 2.2.0
Updated by Amber Herold about 10 years ago
- Status changed from In Test to Closed