-
Notifications
You must be signed in to change notification settings - Fork 1k
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
Enable linting and formatting for e2e tests #832
Conversation
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: woop The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
return None, is_ok | ||
|
||
wait_retry_backoff(retry_fn=try_get_features, | ||
timeout_secs=90, | ||
timeout_msg="Timed out trying to get online feature values") |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This wait_retry_backoff
is unreachable @mrzzy. Not sure if you have context on it?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I will remove it for the time being. Please submit a new PR if it's actually being used.
/test test-end-to-end-batch |
What this PR does / why we need it:
We currently have Python based formatting and linting for the Python SDK (code and tests), however our end to end test suite also uses Python but isn't covered by linting or formatting. This PR includes the
tests/e2e
folder under the coverage ofmake format-python
andmake lint-python
Does this PR introduce a user-facing change?: