remove ad-hoc check for dev SiteDB for march 12 transition, https://savannah.cern.ch/bugs/index.php?100835
adding check for new siteDB
Fix for bug #66620: now resubmission numbers in output numbering are contigous. If exception happens than use the old strategy: rely on runningJob submission counter
Fix candidate for bug #63406. In test on CNAF machine, more tests needed
Fix candidate for bug #63406. In test on CNAF machine, more tests needed
Fallback mechanism for problems with status XML retrieval from CommandManager. Rollback for problem with runningJob['submission'] alignment between ser/cli until I'll prepare a fix
Rollback for runningJob submission alignment. Will be investigated in next releases
Align with the head
runningJob submission field backpropagation to client for mixed cli/ser resubmission with unique names convention
Fix for bug #58043: now stageout uses unique names for the files sent to SE
Fix the value of isNew variable
add support for WMBS
Removing condition on created jobs status update
use proper field (job.closed and not job.standardInput) to handle close jobs
mods to use new filed "state" to check if action is allowed
set filed state to status Created when new running jobs are istanciated
adapting code to logging usage. (crab_logger removed)
First implementation of action/state field: Created, SubRequest + update the db field from the status
rollback for 250 compatibilty
Status deserialize updates new action info
minor fixes
define here the full task_id
Enabling client to work with NS status [Not Submitted jobs]
typos
added web monitoring info to PrintID functionality.
Printing ended tag instead of submission number
additional fix for running jobs
fix for problem creating new running job instaces
Removing Submitting status and special check
Removed set at Killing status on client side and related check
Adapted to the new load method in BL
fix on running jobs alignement on client sqlite DB wrt server DB
aligne local DB with grid ID infos from the server. Minor bug fix to avoid problem during status query. Added support to print grid ID using -printId command
Added Done (Failed) status to the retrievable list
patch for ended jobs status code, waiting for Server improvment
patch for ended jobs status code, waiting for Server improvment
fix for not status update... it is a workaround more than a fix
fix for not status update... it is a workaround more than a fix
fixes for Status reporting while using the server. Plus some print adjustment
fixes for Status reporting while using the server. Plus some print adjustment
removed EE temporary status...in case of server usage
removed EE temporary status...in case of server usage
some changes according to the head of CRAB (24/06/2008)
Killing status to hide latencies
FIX: using right status and printing debug info
Added TEMPORARY check on retrieved output avoiding multiple getOutput
added support to run on dataset with new blocks , skipping the already analyzed. Plus some minor cleaning
client server DB running instances alignment
now -list report also WMS name. (Service : )
Fix on subsequent submission identification condition
re-aligned
temporary rollback
Restored last commit on BL install part
Client-side first-submission-check fix
Aligned with BossLite HEAD
last fix for id--jobId
now resubmission working... still an optimization is needed on the status print on screen
Fix for submissionNumber disalignment
correct management of running instance during resubmit
More cautious get output for server
while create jobs create runnng jobs also
aligned with bLite head
bug fix
first implementation of -list
restored the inheritance between Status and StatusServer. Enabled the possibility to write an xml file instead of print the screen report, during the status query. Started to restore to sand infos to ML
Added taskname in front of job name
Many changes to have LSF working with BossLite Introduce Killer class to handle -kill which works again Work_space::res() return the correct output directory also in case user has set a non default one, Likewise for logDir() USER.outputdir is not to be used anywhere outside workspace class Some cleanup in submit logic, to reduce call of Scheduler specific classes from Submitter.py crab -clean works as well (well, almost, still need to remove twice the directory) Fill startDirectory and outputDirectory to Task GetOuput check status and not schedulerStatus (not stantard) Some cleanup in the use of BlackWhiteListParser No explicit check of scheduler concrete type in Submitter at listMatch level: move different behaviour in SchedulerXYZ implementation Plus other things I'm forgetting... Stefano
implementation of exception catching while interacting with Scheduler and Database
improvement on updateRunJobs method
restored -printId functionality using bosslite
still another fix on the job index plus bosslite integration optimization.
allignment to bosslite changes. many improvments on db interaction, minor changes on list usage to avoid error on job index
A small fix on the usage of the DBinterface facade pattern
Many changes to integrate BossLite. Creation step fully implemented and optimized... Submission is now working again. Here the missing things are the support for jobs submission by range, the message sending to ML, and the listmatch_match check. Actually the requirements can be changed on the fly as was in the past. The status is fully working with BossLite. The exit code display is not there since the new boss does not implement the RealTime mon.. here the functionality is under development by Federica: to be integrated.
initial mods to have LSF working with BossLite: still way to go...
First version which submit jobs using blite. Not yet fully working. Minor problem with jdl arguments. Submission dose not take range yet
added methods
added new methods to be used at the subission time
now use new db API (load by id)
new class. Designed to collect methods to intercact with databse bosslite API
This form allows you to request diffs between any two revisions of this file. For each of the two "sides" of the diff, select a symbolic revision name using the selection box, or choose 'Use Text Field' and enter a numeric revision.