Skip to content
GitLab
Projects Groups Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
  • Sign in
  • Corryvreckan Corryvreckan
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
    • Locked Files
  • Issues 38
    • Issues 38
    • List
    • Boards
    • Service Desk
    • Milestones
    • Iterations
    • Requirements
  • Merge requests 13
    • Merge requests 13
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
    • Test Cases
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Packages and registries
    • Packages and registries
    • Container Registry
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Code review
    • Insights
    • Issue
    • Repository
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • CorryvreckanCorryvreckan
  • CorryvreckanCorryvreckan
  • Issues
  • #146
Closed
Open
Issue created Apr 29, 2021 by Keerthi Nakkalil@knakkaliContributor

jobsub freezing after the first run

Hello. While running jobsub with the command corryvreckan/jobsub/jobsub.py -c runcorry.conf -csv W5_E2_runs.csv -v debug 6275,6298,6300,6305,6306, it starts off smoothly and freezes after the first run. Corry is still running and not exciting even after typing ctrl+c. I can see the root files and histograms of the first run in the output directory. The log file of the first run generated is incomplete with the last bits of the analysis information missing. The wall clock timing (seconds) displayed at the end of the analysis only shows the information of [EventDefenitionM26] and [EventLoaderEuDAQ2] modules while I was expecting to see other modules as well ([Clustering4D],[Correlations], [Tracking4D]...Please see the screenshot below). The exact same runs work properly when we run them individually (without using jobsub).

These are my csv and conf files: runcorry.conf W5_E2_runs.csv Screenshot: Screenshot__86_

Assignee
Assign to
Time tracking