GenericCommitStatus can have empty started_at

Everyone can contribute. Help move this issue forward while earning points, leveling up and collecting rewards.

• Close this issue

Old title

some pipelines don't display duration data

Summary

Customer in this support ticket, running v11.2.8-ee, finds that sometimes their completed pipeline jobs show duration data, and sometimes they do not:

What is the current bug behavior?

Looking at entries for one "good" and one "bad" pipeline in the database, they found that the "bad" one does not have "started_at" or "duration" entries in the table:

gitlabhq_production=> select * from ci_pipelines where id=506212 or id=506253;
   id   |  ref   |                   sha                    |                before_sha                |         created_at         |         updated_at         | tag | yaml_errors | committed_at | project_id | status  |         started_at         |        finished_at
      | duration | user_id | lock_version | auto_canceled_by_id | pipeline_schedule_id | source | protected | config_source | failure_reason |  iid
--------+--------+------------------------------------------+------------------------------------------+----------------------------+----------------------------+-----+-------------+--------------+------------+---------+----------------------------+----------------------
------+----------+---------+--------------+---------------------+----------------------+--------+-----------+---------------+----------------+-------
 506212 | master | 80188da5b792508758e3e91348c334a8f1cb9762 | 0000000000000000000000000000000000000000 | 2018-12-13 00:20:32.608653 | 2018-12-13 00:21:22.641149 | f   |             |              |       4711 | success | 2018-12-13 00:21:02.872672 | 2018-12-13 00:21:22.5
8841  |       49 |    1301 |            3 |                     |                      |      3 | f         |             1 |                | 47124
 506253 | master | 80188da5b792508758e3e91348c334a8f1cb9762 | 0000000000000000000000000000000000000000 | 2018-12-13 00:25:32.663215 | 2018-12-13 00:27:34.626504 | f   |             |              |       4711 | success |                            | 2018-12-13 00:27:34.6
25001 |          |    1301 |            2 |                     |                      |      3 | f         |             1 |                | 47125
(2 rows)

Any ideas what might be happening?

cc @grzesiek