-
Notifications
You must be signed in to change notification settings - Fork 998
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
Stabilize flaky e2e tests #1173
Merged
Merged
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
pyalex
requested review from
davidheryanto,
khorshuheng,
woop and
zhilingc
as code owners
November 17, 2020 03:33
feast-ci-bot
added
do-not-merge/release-note-label-needed
approved
needs-kind
size/S
size/M
and removed
size/S
labels
Nov 17, 2020
Signed-off-by: Oleksii Moskalenko <[email protected]>
Signed-off-by: Oleksii Moskalenko <[email protected]>
Signed-off-by: Oleksii Moskalenko <[email protected]>
Signed-off-by: Oleksii Moskalenko <[email protected]>
Signed-off-by: Oleksii Moskalenko <[email protected]>
Signed-off-by: Oleksii Moskalenko <[email protected]> pipeline fails Signed-off-by: Oleksii Moskalenko <[email protected]> pipeline fails Signed-off-by: Oleksii Moskalenko <[email protected]> pipeline fails Signed-off-by: Oleksii Moskalenko <[email protected]>
Signed-off-by: Oleksii Moskalenko <[email protected]>
Signed-off-by: Oleksii Moskalenko <[email protected]>
Signed-off-by: Oleksii Moskalenko <[email protected]>
khorshuheng
approved these changes
Nov 17, 2020
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: khorshuheng, pyalex 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 |
/lgtm |
pyalex
added a commit
that referenced
this pull request
Nov 24, 2020
* use mvn cache in e2e & skip auth Signed-off-by: Oleksii Moskalenko <[email protected]> * correct path & pytest param Signed-off-by: Oleksii Moskalenko <[email protected]> * use artifacts to store ingestion jar Signed-off-by: Oleksii Moskalenko <[email protected]> * add mvn cache Signed-off-by: Oleksii Moskalenko <[email protected]> * download artifact to path Signed-off-by: Oleksii Moskalenko <[email protected]> * mvn cache Signed-off-by: Oleksii Moskalenko <[email protected]> pipeline fails Signed-off-by: Oleksii Moskalenko <[email protected]> pipeline fails Signed-off-by: Oleksii Moskalenko <[email protected]> pipeline fails Signed-off-by: Oleksii Moskalenko <[email protected]> * check failing Signed-off-by: Oleksii Moskalenko <[email protected]> * cache for master build of ingestion jar Signed-off-by: Oleksii Moskalenko <[email protected]> * drop auth=true completely Signed-off-by: Oleksii Moskalenko <[email protected]>
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.
Signed-off-by: Oleksii Moskalenko [email protected]
What this PR does / why we need it:
This PR addresses
Which issue(s) this PR fixes:
Fixes #
Does this PR introduce a user-facing change?: