Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Excessively long duration reported for "Queued" spans #19

Open
seh opened this issue Sep 18, 2024 · 0 comments
Open

Excessively long duration reported for "Queued" spans #19

seh opened this issue Sep 18, 2024 · 0 comments

Comments

@seh
Copy link

seh commented Sep 18, 2024

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:

const queueSpan = tracer.startSpan("Queued", { startTime }, queueCtx);
queueSpan.end(new Date(firstJob.started_at));

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant