Skip to content
GitLab
Projects Groups Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
  • Sign in
  • MC Job Options MC Job Options
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
    • Locked Files
  • Issues 2
    • Issues 2
    • List
    • Boards
    • Service Desk
    • Milestones
    • Iterations
  • Jira
    • Jira
  • Merge requests 5
    • Merge requests 5
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Packages and registries
    • Packages and registries
    • Package Registry
    • Container Registry
    • Infrastructure Registry
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Code review
    • Issue
    • Repository
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • atlas-physics
  • pmg
  • MC Job OptionsMC Job Options
  • Issues
  • #83
Closed
Open
Issue created Feb 25, 2020 by Spyros Argyropoulos@sargyropMaintainer

Use python's logging module instead of print

When running the commit script on hundreds of files buffering of the stderr/out seems to mangle the output.

./scripts/commit_new_dsid.sh -n -d=421332-421475
INFO: will use following remote for pushing: origin
Checking jO consistency and DSID ranges ...
ERROR in jO consistency checks
ERROR: file 421xxx/421332/mc.MGPy8EG_A14N23LO_VBFWBCpCp_150_145_MET75_MS.py

We should switch to using python's logging module or handle this in a smarter way so that flushing is handled in a better way.

Reported by @gstark

Assignee
Assign to
Time tracking