Skip to content
GitLab
Projects Groups Topics Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • T tails
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributor statistics
    • Graph
    • Compare revisions
  • Issues 968
    • Issues 968
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 32
    • Merge requests 32
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Artifacts
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • tails
  • tails
  • Issues
  • #11589
Closed
Open
Issue created Jul 22, 2016 by bertagaz@bertagaz

Time syncing over bridge is fragile

Originally created by @bertagaz on #11589 (Redmine)

While referencing the test suite failure in Jenkins for 2016 June (see #11087 (closed)), we noticed two failures of the time syncing over bridge scenario. It sometimes happens in this case that tordate fails to set the time. That was already discussed a bit in #10288 (closed), and the long term plan is #5774. But until this is implemented (or any other shorter term plan), this scenario is marked as fragile.

Attachments

  • stable_319.log
  • devel_373.log
Edited Jun 29, 2021 by intrigeri
To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information
Assignee
Assign to
Time tracking