Conversation
derived_task_summary.execution is wall-clock seconds, not minutes. Verified May 2026: gecko-t win11 p50 is ~1409 s (~23 min/task); as minutes that would be 23 h, which is impossible given task deadlines. Using minutes makes task-hours off by 60x in cost-per-task analysis. Updates the column note, the sample query alias, and the outlier-filter caveat (86400 s, not 1440 min).
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
derived_task_summary.executionis wall-clock seconds, not minutes. The azure-cost-analysis reference doc (taskcluster-task-counting.md) says minutes in three places.Verified against May 2026 data: gecko-t win11 p50 is ~1409 s (~23 min/task). If the unit were minutes, p50 would be ~23 hours, which is impossible given task deadlines (observed max ~7519 s ≈ 2.1 h). Treating the column as minutes makes task-hours off by 60x in any cost-per-task or utilization analysis.
Changes:
execution(minutes) → (seconds, wall-clock task runtime)avg_exec_minutes→avg_exec_seconds< 86400s (24 h), not< 1440minDoc-only change.