Skip to content

GitLab

  • Menu
Projects Groups Snippets
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
  • Sign in
  • E ensembl-hive
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
    • Locked Files
  • Issues 0
    • Issues 0
    • List
    • Boards
    • Service Desk
    • Milestones
    • Iterations
    • Requirements
  • Jira
    • Jira
  • Merge requests 7
    • Merge requests 7
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
    • Test Cases
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Packages & Registries
    • Packages & Registries
    • Package Registry
    • Container Registry
    • Infrastructure Registry
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Code review
    • Insights
    • Issue
    • Repository
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • ensembl-gh-mirror
  • ensembl-hive
  • Merge requests
  • !14

Closed
Created Jan 27, 2016 by Marek Szuba@mks
  • Report abuse
Report abuse

Update LSF.pm to parse year- and year-less responses of LSF bacct cmd

  • Overview 2
  • Commits 1
  • Changes 1

Created by: tweep

Our installation of LSF returns the year in the bacct response - which is not parsed by the regex in parse_report_source_line(). The fix will parse year- and year-less responses of bacct. This is a quickfix as the _yearless_2_datetime() method is still invoked - best would be to not invoke it if the year is returned; however I think it increases the complexity of the code too much. Regex now parses both lines:

Sat Jan 23 22:48:28 2016: Completed <exit>; TERM_RUNLIMIT: job killed after reaching LSF run time limit.

Sat Jan 23 22:48:28: Completed <exit>; TERM_RUNLIMIT: job killed after reaching LSF run time limit.

screen shot 2016-01-26 at 4 06 05 pm

We're using LSF version 9.1.2.0 - would be interesting if the different response formats are due to different LSF versions. Maybe it's time to create Bio::EnsEMBL::Hive::Meadow::LSF::SUBVERSION ?

Assignee
Assign to
Reviewer
Request review from
Time tracking
Source branch: github/fork/tweep/patch-3