Skip to content
GitLab
  • Menu
Projects Groups Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • R RNO-G Data Tools
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 11
    • Issues 11
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 0
    • Merge requests 0
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Packages & Registries
    • Packages & Registries
    • Package Registry
    • Container Registry
    • Infrastructure Registry
  • Monitor
    • Monitor
    • Metrics
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • Steffen Hallmann
  • RNO-G Data Tools
  • Issues
  • #3
Closed
Open
Created Aug 28, 2021 by Steffen Hallmann@steffen.hallmannOwner

Run comments wrong

Run comments are sometimes wrong, e.g. runs 483-590 indicate "in-situ pulsing run" (see runtable; comment was not removed after pulsing ended.

Maybe someone involved in deployment can check if comments are correct?

In the long term, maybe some safety measures can be taken, to help run selection (switch to pre-defined run setups, or -maybe quicker to implement - issue warning if the config has changed?)

Assignee
Assign to
Time tracking

imprint | privacy | Conditions of Use