Handle empty target groups and improve dashboard deployment#2
Merged
Conversation
Avoid failing dashboard generation when a target group has no data. If plot_cumulative_state() receives an empty DataFrame, write a small placeholder HTML page and return before computing timestamp ranges. This fixes Deploy-Dashboard failures such as: ValueError: max() iterable argument is empty for empty groups like gcv_zve.
Add per-ref concurrency to Deploy-Dashboard and ignore dashboard-only pushes so dashboard auto-commits do not retrigger the workflow. This reduces non-fast-forward push races when multiple dashboard runs try to update main at the same time.
Collaborator
Author
|
The Pre-Pull-Request check has passed. The remaining pending checks appear to come from the Staging workflow, which invokes the full Run-Frequent build/test matrix. This PR only touches dashboard/plot.py and deploy-dashboard.yaml. It does not change GCC build/test workflows, target matrix, GCC checkout logic, release branch handling, or Binutils behavior. The fix addresses dashboard deployment robustness: handling empty dashboard target groups and reducing dashboard auto-commit push races. Given that this is a dashboard-only infrastructure fix and the lightweight checks have passed, I plan to merge this PR to restore dashboard stability unless there are objections. |
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.
Avoid failing dashboard generation when a target group has no data.
If plot_cumulative_state() receives an empty DataFrame, write a small
placeholder HTML page and return before computing timestamp ranges.
And add per-ref concurrency to Deploy-Dashboard and ignore dashboard-only
pushes so dashboard auto-commits do not retrigger the workflow.
This reduces non-fast-forward push races when multiple dashboard runs
try to update main at the same time.