GitLab

Only redefine locally methods in Bio::EnsEMBL::Hive::Process (to allow the later implementation of runWorker to use them)

* master: (21 commits)
  bugfix: record job_id, role_id and worker_id of the job that deadlocked when checking in
  logging of deadlocks via callback
  interface_change: protected_prepare_execute() takes all sql-related parameters as first argument
  wait for random time with increasing upper boundary
  log deadlocks and retries in log_message
  grab_jobs_for_role now uses PPE instead of bare do()
  PPE now returns a value
  capture all "dies" during worker->run() and try to record them in log_message
  bugfix: specialization failures should not be considered critical
  bugfix: the claimed batch was not released
  MySQL and PostgreSQL have a maximum length for database names
  Added 'meadow_user' to Worker object+schema which is now routinely recorded. Also renamed 'host' to 'meadow_host' for consistency
  Allow script-based schema patches that can use API in addition to pure SQL-based patches
  Updated the copyright to 1999-2015
  don't mix missing and incomplete options in the report
  No references to "self_burial" any more as the concept is gon
  Test that it is defined, not logically true
  cause_of_death can be undefined here (for local meadows, for instance)
  Backported the recent changes from Ensembl's DBConnection
  Numbers are returned as real numbers, not strings;
  ...

Conflicts:
	modules/Bio/EnsEMBL/Hive/Queen.pm
	modules/Bio/EnsEMBL/Hive/Worker.pm

The function can thus be called from both the usual script
standaloneJob.pl and the test interface

The function can thus be called from both the usual script init_pipeline.pl
and the test interface

Conflicts:
	modules/Bio/EnsEMBL/Hive/Worker.pm

Conflicts:
	modules/Bio/EnsEMBL/Hive/Worker.pm

Conflicts:
	modules/Bio/EnsEMBL/Hive/Worker.pm

The problem was when a worker is contaminated and has to die: remainings jobs
of the batch were not released.
We now have an explicit list of all the cause_of_death that could happen through
a batch, and for which we should free the jobs

(resp 64 and 63 characters).
This simple patch prevents db_cmd from creating such databases with an
explicit message as opposite to the default MySQL error message:
"ERROR 1102 (42000) at line 1: Incorrect database name "

Added 'meadow_user' to Worker object+schema which is now routinely recorded. Also renamed 'host' to 'meadow_host' for consistency