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

Dualstack test case #108

Merged
merged 31 commits into from
Jul 31, 2024
Merged

Dualstack test case #108

merged 31 commits into from
Jul 31, 2024

Conversation

larry-safran
Copy link
Contributor

@larry-safran larry-safran commented Jul 24, 2024

Have a test case that initializes 3 servers. They will each have different --address_type arguments from: "ipv4_ipv6", "ipv4", "ipv6". It will then create a client and run the round robin test ensuring that all 3 receive traffic. Due to warmup, we aren't concerned about equal traffic.

Once Java 1.66 is cut, update canonical server to point to it so that it has support for the address_type argument

@larry-safran larry-safran requested a review from a team as a code owner July 26, 2024 21:16
framework/test_app/runners/k8s/k8s_base_runner.py Outdated Show resolved Hide resolved
tests/dualstack_test.py Outdated Show resolved Hide resolved
tests/dualstack_test.py Show resolved Hide resolved
@larry-safran larry-safran force-pushed the dualstack_test branch 2 times, most recently from 4f726ce to f5e643c Compare July 30, 2024 18:09
…ified. This is only needed after aborting a run that had created a client before it could cleanup.
Copy link
Member

@sergiitk sergiitk left a comment

Choose a reason for hiding this comment

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

Mostly LGTM, but let's make sure to fix server namespace cleanup order

kubernetes-manifests/server.deployment.yaml Show resolved Hide resolved
tests/dualstack_test.py Outdated Show resolved Hide resolved
tests/dualstack_test.py Outdated Show resolved Hide resolved
tests/dualstack_test.py Outdated Show resolved Hide resolved
tests/dualstack_test.py Outdated Show resolved Hide resolved
tests/dualstack_test.py Outdated Show resolved Hide resolved
tests/dualstack_test.py Outdated Show resolved Hide resolved
tests/dualstack_test.py Outdated Show resolved Hide resolved
tests/dualstack_test.py Outdated Show resolved Hide resolved
@larry-safran larry-safran requested a review from sergiitk July 31, 2024 02:04
kubernetes-manifests/server.deployment.yaml Outdated Show resolved Hide resolved
tests/dualstack_test.py Show resolved Hide resolved
tests/dualstack_test.py Outdated Show resolved Hide resolved
tests/dualstack_test.py Outdated Show resolved Hide resolved
@sergiitk
Copy link
Member

Previous test runs passed, deflaking CSM:

@larry-safran larry-safran requested a review from sergiitk July 31, 2024 21:52
tests/dualstack_test.py Show resolved Hide resolved
tests/dualstack_test.py Outdated Show resolved Hide resolved
@sergiitk
Copy link
Member

Re deflaking CSM: I just realized the grpcroute test is now expected to fail, so Arvin added a temporary skip in another PR. So no need to wait for the other adhoc run to finish.

Co-authored-by: Sergii Tkachenko <[email protected]>
tests/dualstack_test.py Outdated Show resolved Hide resolved
@larry-safran larry-safran merged commit b3d0417 into grpc:main Jul 31, 2024
7 checks passed
@larry-safran larry-safran deleted the dualstack_test branch July 31, 2024 23:05
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.

2 participants