Skip to content

Comments

[DO NOT MERGE] Trigger release test for 2.44.1 perf metrics#51690

Closed
omatthew98 wants to merge 4 commits intoray-project:masterfrom
omatthew98:mowen/trigger-release-test-2.44.1
Closed

[DO NOT MERGE] Trigger release test for 2.44.1 perf metrics#51690
omatthew98 wants to merge 4 commits intoray-project:masterfrom
omatthew98:mowen/trigger-release-test-2.44.1

Conversation

@omatthew98
Copy link
Contributor

Why are these changes needed?

Related issue number

Checks

  • I've signed off every commit(by using the -s flag, i.e., git commit -s) in this PR.
  • I've run scripts/format.sh to lint the changes in this PR.
  • I've included any doc changes needed for https://docs.ray.io/en/master/.
    • I've added any new APIs to the API Reference. For example, if I added a
      method in Tune, I've added it in doc/source/tune/api/ under the
      corresponding .rst file.
  • I've made sure the tests are passing. Note that there might be a few flaky tests, see the recent failures at https://flakey-tests.ray.io/
  • Testing Strategy
    • Unit tests
    • Release tests
    • This PR is not tested :(

aslonnie and others added 4 commits March 15, 2025 16:38
Signed-off-by: Lonnie Liu <lonnie@anyscale.com>
cherrypick ray-project#51450

Signed-off-by: Lonnie Liu <lonnie@anyscale.com>
for patch release

Signed-off-by: Lonnie Liu <lonnie@anyscale.com>
Signed-off-by: Matthew Owen <mowen@anyscale.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants