Skip to content

Setup AGI to be built with Kokoro #2

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

Merged
merged 7 commits into from
Jan 28, 2020
Merged

Setup AGI to be built with Kokoro #2

merged 7 commits into from
Jan 28, 2020

Conversation

pmuetschard
Copy link
Member

No description provided.

GAPID_VERSION_MINOR="7"
GAPID_VERSION_POINT="0"
AGI_VERSION_MAJOR="0"
AGI_VERSION_MINOR="9"
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Should this be 0.1.0 (not sure how pre-1.0.0 habits are)?

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We are so close to the 1.0 release, I picked 0.9. I expect us to do at most 1 minor release, before we bump this to 1.0.

@pmuetschard pmuetschard merged commit d6f6d42 into master Jan 28, 2020
@pmuetschard pmuetschard deleted the agi_build branch January 31, 2020 19:11
stellama0208 added a commit to stellama0208/agi that referenced this pull request Feb 21, 2020
 - Rather than the combinition of name and start time ts.
 - It will avoid losing track of the selection when quantization do some
 approximations on the time.
 - Bug 1: http://b/147922469, google#5.
 - Bug 2: http://b/149959272, google#2.
stellama0208 added a commit to stellama0208/agi that referenced this pull request Feb 21, 2020
 - Rather than the combinition of name and start time ts.
 - It will avoid losing track of the selection when quantization do some
 approximations on the time.
 - Bug 1: http://b/147922469, google#5.
 - Bug 2: http://b/149959272, google#2.
stellama0208 added a commit that referenced this pull request Feb 24, 2020
 - Identify a counter selection by counter id rather than the combinition of name and start time ts.
 - It will avoid losing track of the selection when quantization do some approximations on the time.
 - Bug 1: http://b/147922469, #5.
 - Bug 2: http://b/149959272, #2.
 - Bug 3: http://b/149959272. #1.
stellama0208 added a commit that referenced this pull request Mar 12, 2020
 - Add drag-selection to the Process Panel.
 - Change CPU slices' color after drag-selecting in Thread Panel.
 - Bug: http://b/147922469. #2 and #3.
stellama0208 added a commit to stellama0208/agi that referenced this pull request May 6, 2020
 - Combine *SliceSelectionView.java and *SlicesSelectionView.java into
 one, do selection count checking at selection view composite creation
 time, and set the composite layout accordingly.
 - This can help reduce file numbers and make it easier to locate
 selection view composite.
stellama0208 added a commit to stellama0208/agi that referenced this pull request May 26, 2020
stellama0208 added a commit to stellama0208/agi that referenced this pull request Jul 21, 2020
stellama0208 added a commit to stellama0208/agi that referenced this pull request Jul 23, 2020
 - When user right click on a command in the Performance tab, there
 would be an option "Select in Command Tab", which lets user quickly jump
 to the same command in the Command tab, and have all other resource tabs
 start loading.
stellama0208 added a commit to stellama0208/agi that referenced this pull request Aug 21, 2020
 - Change the two pass performance loading mechanism, in which the first
 pass server calculate crude data and save inside database, and the second
 pass the client query server dynamically based on expanding action.
 - Instead, server derive and calculate performance for all possible parent
 command nodes at intialization time, altogether with the performance
 calculation for the leaf commands (renderpass commands). All the perf
 data will be passed back to client once and all.
stellama0208 added a commit to stellama0208/agi that referenced this pull request Aug 21, 2020
 - Change the two pass performance loading mechanism, in which the first
 pass server calculate crude data and save inside database, and the second
 pass the client query server dynamically based on expanding action.
 - Instead, server derive and calculate performance for all possible parent
 command nodes at intialization time, altogether with the performance
 calculation for the leaf commands (renderpass commands). All the perf
 data will be passed back to client once and all.
stellama0208 added a commit to stellama0208/agi that referenced this pull request Sep 15, 2020
 - Change the two pass performance loading mechanism, in which the first
 pass server calculate crude data and save inside database, and the second
 pass the client query server dynamically based on expanding action.
 - Instead, server derive and calculate performance for all possible parent
 command nodes at intialization time, altogether with the performance
 calculation for the leaf commands (renderpass commands). All the perf
 data will be passed back to client once and all.
stellama0208 added a commit to stellama0208/agi that referenced this pull request Sep 21, 2020
 - Change the two pass performance loading mechanism, in which the first
 pass server calculate crude data and save inside database, and the second
 pass the client query server dynamically based on expanding action.
 - Instead, server derive and calculate performance for all possible parent
 command nodes at intialization time, altogether with the performance
 calculation for the leaf commands (renderpass commands). All the perf
 data will be passed back to client once and all.
stellama0208 added a commit to stellama0208/agi that referenced this pull request Nov 6, 2020
stellama0208 added a commit to stellama0208/agi that referenced this pull request Jul 2, 2021
@angusto angusto mentioned this pull request Sep 7, 2022
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

Successfully merging this pull request may close these issues.

2 participants