You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In a recent trace published for a workflow run using this action as a final job within the same containing workflow (per #14 (comment)), 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 #14 (comment)), 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:
otel-cicd-action/src/tracing/job.ts
Lines 139 to 140 in a335d59
The text was updated successfully, but these errors were encountered: