Skip to content
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

[Metrics] Fix shared memory is not displayed properly #34301

Merged
merged 2 commits into from
Apr 13, 2023

Conversation

rkooo567
Copy link
Contributor

Why are these changes needed?

Looks like we incorrectly recorded shared memory, and incorrectly displayed it to the metrics graph (I forgot to append ray_)

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 :(

Copy link
Contributor

@rickyyx rickyyx left a comment

Choose a reason for hiding this comment

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

oh good catch! Did you just eyeball it and realize the bug?

Does this need to be CP?

@rkooo567
Copy link
Contributor Author

What is CP? And I just found out from the dashboard when I navigate it through lol (I occasionally navigate around the dashboard from release tests for dogfooding..)

@rkooo567 rkooo567 merged commit 688ddf6 into ray-project:master Apr 13, 2023
@rickyyx
Copy link
Contributor

rickyyx commented Apr 13, 2023

CP, cherry-pick

@rkooo567
Copy link
Contributor Author

ah hmm.. yeah I think we should.

cadedaniel added a commit that referenced this pull request Apr 14, 2023
rkooo567 pushed a commit that referenced this pull request Apr 15, 2023
rkooo567 added a commit to rkooo567/ray that referenced this pull request Apr 17, 2023
vitsai pushed a commit to vitsai/ray that referenced this pull request Apr 17, 2023
)

Looks like we incorrectly recorded shared memory, and incorrectly displayed it to the metrics graph (I forgot to append ray_)
vitsai pushed a commit to vitsai/ray that referenced this pull request Apr 17, 2023
elliottower pushed a commit to elliottower/ray that referenced this pull request Apr 22, 2023
)

Looks like we incorrectly recorded shared memory, and incorrectly displayed it to the metrics graph (I forgot to append ray_)

Signed-off-by: elliottower <[email protected]>
elliottower pushed a commit to elliottower/ray that referenced this pull request Apr 22, 2023
ProjectsByJackHe pushed a commit to ProjectsByJackHe/ray that referenced this pull request May 4, 2023
)

Looks like we incorrectly recorded shared memory, and incorrectly displayed it to the metrics graph (I forgot to append ray_)

Signed-off-by: Jack He <[email protected]>
ProjectsByJackHe pushed a commit to ProjectsByJackHe/ray that referenced this pull request May 4, 2023
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