GitLab

After upgrading to LAVA 2021.05 it seems that the end_time JSON callback field can contain None instead of a proper date:

$ curl -s https://lava.collabora.co.uk/scheduler/job/4122603/job_data | zcat | jq .end_time
"None"
$ curl -s https://lava.collabora.co.uk/scheduler/job/4122603/job_data | zcat | jq .| cut -c 1-120
{
  "id": 4122603,
  "status": 2,
  "status_string": "complete",
  "state": 5,
  "state_string": "Finished",
  "health": 1,
  "health_string": "Complete",
  "submit_time": "2021-07-01 08:57:11.907343+00:00",
  "start_time": "2021-07-01 09:11:55.686152+00:00",
  "end_time": "None",
  "submitter_username": "apertis-validator",
  "failure_comment": null,
  "priority": 50,
  "description": "Iptables test on v2022dev3 QEMU using basesdk image 20210701.0018",
  "actual_device_id": "qemu-balsa-2",
  "definition": "actions:\n- deploy:\n    images:\n      rootfs:\n        compression: gz\n        image_arg: -m 1024 -e
  "metadata": [],
  "log": "- {\"dt\": \"2021-07-01T09:11:59.238318\", \"lvl\": \"info\", \"msg\": \"lava-dispatcher, installed at version
  "results": {
    "lava": "- id: '153694230'\n  job: '4122603'\n  level: ''\n  log_end_line: ''\n  log_start_line: ''\n  logged: '2021
    "0_sanity-check": "- id: '153694616'\n  job: '4122603'\n  level: ''\n  log_end_line: '2118'\n  log_start_line: '2118
    "1_disk-rootfs-fsck": "- id: '153694619'\n  job: '4122603'\n  level: ''\n  log_end_line: '2172'\n  log_start_line: '
  }
}

As you can imagine, our endpoint receiving the callback was not really expecting None as a date value in a JSON file. :D