Regression in the JSON output of debci

(Moved from !270 (comment 510790) into its own issue)

To be honest, I don't remember the last time I actually used debci-status, and I don't think anything in the rest of debci depends on it.

I assume https://ci.debian.net/data/status/unstable/amd64/packages.json is built with the output of "debci-status" because tracker.debian.org has been failing to import JSON data from ci.debian.net since April 22.

The tracker code is failing because the JSON output has lost the "duration_seconds" key. I haven't reviewed the changes of Ben but it really seems that there's something fishy there.

All the entries are limited to those fields:

  {
    "trigger": null,
    "package": "step",
    "arch": "amd64",
    "suite": "unstable",
    "version": "4:17.08.3-1",
    "status": "fail",
    "run_id": 952,
    "is_private": false,
    "extra_apt_sources": [

    ],
    "updated_at": "2019-05-12T15:27:26.201Z",
    "date": "2018-03-16T04:53:36.000Z"
  },

This is much shorter than the examples that @g0tmi1k showed about what we used to have.

And tracker.debian.org also relies on the "previous_status" field that disappeared too. :-( (Well it only displays the field, but that was useful information to have)

It would be nice to fix this regression and re-add the fields associated to the job.