In a recent trace published for a workflow run using this action as a final job within the same containing workflow (per https://github.com/corentinmusard/otel-cicd-action/issues/14#issuecomment-2334933875), one of the trace spans has the name "Queued" and a reported duration of 18446743100709.55 milliseconds, or 5,124,095 hours and eighteen minutes. The delay was never apparent while the workflow was running.
Is this action misinterpreting a duration reported by GitHub's API? I see that there's special handling of this span in this action's code:
In a recent trace published for a workflow run using this action as a final job within the same containing workflow (per https://github.com/corentinmusard/otel-cicd-action/issues/14#issuecomment-2334933875), one of the trace spans has the name "Queued" and a reported duration of 18446743100709.55 milliseconds, or 5,124,095 hours and eighteen minutes. The delay was never apparent while the workflow was running.
Is this action misinterpreting a duration reported by GitHub's API? I see that there's special handling of this span in this action's code:
https://github.com/corentinmusard/otel-cicd-action/blob/a335d59a09254777d738126eb6d3c2934720645e/src/tracing/job.ts#L139-L140