Skip to content

Conversation

@hanwen-cluster
Copy link
Contributor

Description of changes

This commit makes the trend even clearer, because we won't be confused by sudden changes because we test some instance types (e.g. p6-b200) temporarily

Checklist

  • Make sure you are pointing to the right branch.
  • If you're creating a patch for a branch other than develop add the branch name as prefix in the PR title (e.g. [release-3.6]).
  • Check all commits' messages are clear, describing what and why vs how.
  • Make sure to have added unit tests or integration tests to cover the new/modified code.
  • Check if documentation is impacted by this change.

Please review the guidelines for contributing and Pull Request Instructions.

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

…eports, separate the report according to instance type

This commit makes the trend even clearer, because we won't be confused by sudden changes because we test some instance types (e.g. p6-b200) temporarily
@hanwen-cluster hanwen-cluster requested review from a team as code owners January 13, 2026 19:54
@hanwen-cluster hanwen-cluster added the skip-changelog-update Disables the check that enforces changelog updates in PRs label Jan 13, 2026
@hanwen-cluster hanwen-cluster enabled auto-merge (rebase) January 13, 2026 19:57
@hanwen-cluster hanwen-cluster merged commit e538384 into aws:develop Jan 13, 2026
26 of 27 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

skip-changelog-update Disables the check that enforces changelog updates in PRs

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants