chore: Limit integration runs back to a single python version due to rate limiting errors #4169
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…rate limiting errors Signed-off-by: Jeremy Ary <jary@redhat.com>
tmihalac
pushed a commit
to tmihalac/feast
that referenced
this pull request
May 3, 2024
…rate limiting errors (feast-dev#4169) Signed-off-by: Jeremy Ary <jary@redhat.com>
tmihalac
pushed a commit
to tmihalac/feast
that referenced
this pull request
May 3, 2024
…rate limiting errors (feast-dev#4169) Signed-off-by: Jeremy Ary <jary@redhat.com> Signed-off-by: Theodor Mihalache <tmihalac@redhat.com>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Even with recent workflow improvements, the recent change to increase scope of integration tests from only python v3.9 to v's 3.9-3.11 has caused us to begin hitting rate limiting errors with google cloud resources due to 3 simultaneous executions per action trigger. This PR reduces integration tests back to a single version scope using v3.11 so that actions won't require constant monitoring and re-triggers.