-
Notifications
You must be signed in to change notification settings - Fork 3.8k
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
95795: ui: add CPU time to statement and transaction tables r=maryliag a=maryliag Adds CPU time as a column on Statement and Transaction tables under SQL Activity and List of fingerprints on Index Details. Part Of #87213 Statements Page <img width="1300" alt="Screen Shot 2023-01-24 at 5 38 32 PM" src="https://user-images.githubusercontent.com/1017486/214437590-70fb8b08-93ab-4588-b7ea-ac564c75c13d.png"> Transactions Page <img width="1424" alt="Screen Shot 2023-01-24 at 5 38 09 PM" src="https://user-images.githubusercontent.com/1017486/214437573-aaadc388-8886-419c-ba5b-75389aa5481e.png"> Transaction Details Page <img width="1535" alt="Screen Shot 2023-01-24 at 5 22 27 PM" src="https://user-images.githubusercontent.com/1017486/214437551-b14d5d3a-3629-46a5-90ae-c57aabd1f5f5.png"> Table on Index Stats Details <img width="1534" alt="Screen Shot 2023-01-24 at 5 21 55 PM" src="https://user-images.githubusercontent.com/1017486/214437371-1940294b-3433-40bb-af74-2086ae190f94.png"> Release note (ui change): Add CPU time as a column on Statement and Transaction tables. 95831: roachtest: better logging of GitHub-related logic r=srosenberg a=renatolabs Whenever a roachtest fails on a release branch, we should either create a new issue with the failure, or comment on an existing issue. However, the logic to decide when to create an issue and the creation process itself are relatively complex. If a roachtest fails on a nightly build and we don't get a corresponding issue, there's no way to understand _why_ that happened: issue posting could have been mistakenly skipped, or maybe an error creating the issue was swallowed in the process. This commit adds appropriate logging to the GitHub issue poster: if issue creation is skipped, the corresponding reason is logged; in addition, any errors encountered in the process of creating the issue/comment are also logged. Epic: None Release note: None Co-authored-by: maryliag <[email protected]> Co-authored-by: Renato Costa <[email protected]>
- Loading branch information
Showing
16 changed files
with
173 additions
and
30 deletions.
There are no files selected for viewing
This file contains 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
This file contains 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
This file contains 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
This file contains 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
This file contains 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
This file contains 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
This file contains 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
This file contains 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
This file contains 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
This file contains 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
This file contains 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
Oops, something went wrong.