Skip to content
GitLab
Projects Groups Topics Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
  • Sign in
  • autosubmit autosubmit
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributor statistics
    • Graph
    • Compare revisions
  • Issues 338
    • Issues 338
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 21
    • Merge requests 21
  • Deployments
    • Deployments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • Repository
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Commits
  • Issue Boards
Collapse sidebar
  • Earth SciencesEarth Sciences
  • autosubmitautosubmit
  • Issues
  • #706
Closed
Open
Issue created Jun 04, 2021 by Miguel Castrillo@mcastrilOwner

A couple of possible GUI glitches

I create an issue to do it in the proper way. I am monitoring the 3.3.3.1 experiments and I noticed some strange behaviors.

  • First, the calculation of the wrapper queues, as discussed in Slack. It seems that in some cases the queuing time is attributed to the 2nd or 3rd job. Also, the running time for the previous jobs is not calculated properly in those cases, like if it started to count only from a determined chunk.

  • When activating the job monitor in the Graph mode, I see some messages that I didn't see before:

Screenshot_from_2021-06-04_19-13-45

  • Then, if pressing on any of the nodes, some edges are highlighted in green, as if they were part of a wrapper. In the beginning, I thought that it maybe was kind of showing the critical path, but I think we only use that colour for wrappers.

Screenshot_from_2021-06-04_19-13-50

Assignee
Assign to
Time tracking