Skip to content
GitLab
Projects Groups Topics Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • bliss bliss
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributor statistics
    • Graph
    • Compare revisions
  • Issues 605
    • Issues 605
    • List
    • Boards
    • Service Desk
    • Milestones
  • Jira
    • Jira
  • Merge requests 165
    • Merge requests 165
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Artifacts
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Packages and registries
    • Packages and registries
    • Model experiments
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Wiki
    • Wiki
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • BlissBliss
  • blissbliss
  • Issues
  • #2353

motor motion tests

Can we finally do something about these? I have to check failing pipelines too often, only to find the same old jog and motion tests fail. This reduces productivity and motivation.

https://gitlab.esrf.fr/bliss/bliss/-/jobs/163278 (test_bad_start_group)

https://gitlab.esrf.fr/bliss/bliss/-/jobs/163284 (test_jog, test_maxee)

https://gitlab.esrf.fr/bliss/bliss/-/jobs/162743 (test_asynchronous_stop)

Edited Nov 29, 2020 by Wout De Nolf
Assignee
Assign to
Time tracking