container-builder-github-ci-status
container-builder-github-ci-status copied to clipboard
Last step is misreported as failure step
If there are multiple steps running when a failure occurs, the latest task to start is reported as the failure reason, rather than the task with status=FAILURE
In the report from cloud container builds describe
, isort
has a (very slightly!) later start time:
id: run-tests
status: FAILURE
timing:
endTime: '2018-04-22T18:51:47.129276336Z'
startTime: '2018-04-22T18:41:13.672572721Z'
[...]
id: isort
status: SUCCESS
timing:
endTime: '2018-04-22T18:41:28.186709447Z'
startTime: '2018-04-22T18:41:13.672967786Z'
Thanks for reporting this @maxim-lian 👋 I think the status field is new, so we can probably rewrite the filter to use that: https://github.com/stealthybox/container-builder-github-ci-status/blob/94d715be8a1135b73470b49644d982182c821291/index.js#L53-L56
I was able to grab a failing build that demonstrates this issue. I've started writing the necessary patch.