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

adds e2e test for anywhere cache #1900

Open
wants to merge 2 commits into
base: master
Choose a base branch
from
Open

Conversation

ankitaluthra1
Copy link
Collaborator

Description

run a set of existing integration for anywhere cache compatibility

Link to the issue in case of a bug fix.

337732802

Testing details

  1. Manual - NA
  2. Unit tests - NA
  3. Integration tests - NA

Copy link
Collaborator

@Tulsishah Tulsishah left a comment

Choose a reason for hiding this comment

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

Minor comments.
LGTM otherwise!

@@ -239,6 +239,25 @@ function run_e2e_tests_for_hns_bucket(){
return 0
}

function run_e2e_tests_for_anywhere_cache(){
local test_bucket_name="golang-grpc-test-lankita-anywhere-cache-test" ## TODO: adding temporary bucket name for testing purpose
Copy link
Collaborator

Choose a reason for hiding this comment

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

Can we set test bucket name with golang-grpc-test-gcsfuse-anywhere-cache-e2e-tests ?

Copy link
Collaborator Author

Choose a reason for hiding this comment

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

yes, in this PR just trying to run the test and see if cache is being used or not, will update final bucket name once cache usage is confirmed.

local test_bucket_name="golang-grpc-test-lankita-anywhere-cache-test" ## TODO: adding temporary bucket name for testing purpose

echo "Running tests for Anywhere Cache"
run_non_parallel_tests TEST_DIR_HNS_GROUP "$test_bucket_name" ## TODO: separate group will be created for anywhere cache in final tests
Copy link
Collaborator

Choose a reason for hiding this comment

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

nit: Should we add TODO above the code line?

Copy link
Collaborator Author

Choose a reason for hiding this comment

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

This will be deleted in final PR

non_parallel_tests_pid_anywhere_cache_group_exit_code=$?

# clean_up test_bucket_name

Copy link
Collaborator

Choose a reason for hiding this comment

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

nit: empty line

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.

None yet

2 participants