Skip to content

Y axis of "Duration for last 30 commits" has unclear unit of measure 'm'

Summary

The Duration for the last 30 commits chart labels the Y axis as Minutes. When a project has pipelines that are relatively short in duration, the chart displays numbers with a unit of m and it's not clear what m is. See 200m, 400m, 600m and 800m in this screenshot:

Screen_Shot_2020-12-24_at_2.41.15_PM

It is not clear what unit of measure m is. (It does not appear to be Minutes .) Could this be "milliminutes" (not really a measure of time accepted by SI)?

For projects where pipelines regularly last longer than one minute, this unit is not seen. The example screenshot for the Duration for the last 30 commits is an example of this.

Steps to reproduce

  1. Create a project on GitLab.com
  2. Run pipelines in that project where the pipeline duration is less than one minute
  3. Browse to Analytics > CI/CD for that project
  4. Observe that the Duration for the last 30 commits graph divides a single minute into numbers with a unit of measure m

Example Project

I have replicated this in the gitlab-gold/briecarranza/issues/value-of-m project.

What is the current bug behavior?

The Duration for the last 30 commits graph divides 1 minute into an unclear unit of measure m where there are 1,000 m in 1 minute.

What is the expected correct behavior?

It would be nice to do one of the following:

  • Clarify what unit of measure m is
  • Use a more clear unit of measure when dividing a minute

Relevant logs and/or screenshots

Output of checks

This bug happens on GitLab.com (and on multiple self-managed instances).

Results of GitLab environment info

Expand for output related to GitLab environment info 

(For installations with omnibus-gitlab package run and paste the output of:
`sudo gitlab-rake gitlab:env:info`)

(For installations from source run and paste the output of:
`sudo -u git -H bundle exec rake gitlab:env:info RAILS_ENV=production`)

Results of GitLab application Check

Expand for output related to the GitLab application check 
(For installations with omnibus-gitlab package run and paste the output of:
sudo gitlab-rake gitlab:check SANITIZE=true)


(For installations from source run and paste the output of:
sudo -u git -H bundle exec rake gitlab:check RAILS_ENV=production SANITIZE=true)


(we will only investigate if the tests are passing)

Possible fixes

Edited by Brie Carranza