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

[autoscaler v2] add unit tests for NodeProviderConfig #35590

Merged
merged 10 commits into from
May 22, 2023

Conversation

scv119
Copy link
Contributor

@scv119 scv119 commented May 22, 2023

Why are these changes needed?

add tests and fix bugs for NodeProviderConfig

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

@scv119 scv119 marked this pull request as ready for review May 22, 2023 07:04
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.


via GIPHY

self._calculate_hashes()
self._sync_continuously = self._node_configs.get(
"generate_file_mounts_contents_hash", True
)

def _calculate_hashes(self) -> None:
self._runtime_hash, self._file_mounts_contents_hash = hash_runtime_conf(
self._node_configs["file_mounts"],
self._node_configs["cluster_synced_files"],
self._node_configs.get("file_mounts", {}),
Copy link
Contributor

Choose a reason for hiding this comment

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

I think if we use dataclasses, it will be much easier to validate the config.

Copy link
Contributor

@rkooo567 rkooo567 left a comment

Choose a reason for hiding this comment

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

LGTM... Feel like in the medium term, we need a schema to enforce the types for the yaml files. It is pretty complicated..

@DmitriGekhtman
Copy link
Contributor

LGTM... Feel like in the medium term, we need a schema to enforce the types for the yaml files. It is pretty complicated..

wooooo Dict[str, Any]

@edoakes
Copy link
Contributor

edoakes commented May 22, 2023

LGTM... Feel like in the medium term, we need a schema to enforce the types for the yaml files. It is pretty complicated..

Pydantic pls

@scv119 scv119 merged commit ea5bcb9 into ray-project:master May 22, 2023
1 of 2 checks passed
@scv119 scv119 added the tests-ok The tagger certifies test failures are unrelated and assumes personal liability. label May 22, 2023
scv119 added a commit to scv119/ray that referenced this pull request Jun 16, 2023
)

Why are these changes needed?
add tests and fix bugs for NodeProviderConfig
arvind-chandra pushed a commit to lmco/ray that referenced this pull request Aug 31, 2023
)

Why are these changes needed?
add tests and fix bugs for NodeProviderConfig

Signed-off-by: e428265 <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
tests-ok The tagger certifies test failures are unrelated and assumes personal liability.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

5 participants