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

TestFunctional/parallel/TunnelCmd into serial subtest #7956

Merged
merged 12 commits into from
May 6, 2020
Merged

TestFunctional/parallel/TunnelCmd into serial subtest #7956

merged 12 commits into from
May 6, 2020

Conversation

govargo
Copy link
Contributor

@govargo govargo commented May 1, 2020

What type of PR is this?

/kind cleanup
/area testing
/kind failing-test

What this PR does / why we need it:

This is improvement & deep investigation PR for #7809.
Now, Hyperkit_macOS integration test always fails due to not be able to resolving DNS.
DNS resolution works in local macOS. So I think root cause of fail is releated to Jenkins environment or test server's environment.

This PR splits TestFunctional/parallel/TunnelCmd and adds DNS resolution test step.
And if DNS resolution test step is failed, we can get dig command output.
This will be helpful for deep investigation.

(EDIT)
This PR changed test validateTunnelCmd of TestFunctional in order to make sure test execution serially.

Which issue(s) this PR fixes:

This will be helpful for #7809 and confirmed the issue fixed.
https://storage.googleapis.com/minikube-builds/logs/7956/884f0e2/HyperKit_macOS.html#pass_TestFunctional%2fparallel%2fTunnelCmd%2fserial%2fAccessThroughDNS

Does this PR introduce a user-facing change?

No. This PR changes TestFunctional/parallel/TunnelCmd testcode.

Before this PR

Test validateTunnelCmd is tested in TestFunctional.

Test.1 access through loadbalancer ingress IP
Test.2 access through DNS resolution            ← Always fail, we cannot get more information

After this PR

validateTunnelCmd has serial subtests.

# TestTunnel(Serial Test)
Test.1 access through loadbalancer ingress IP
Test.2-1 DNS resolution (experimental) by dig
Test.2-2 DNS resolution (experimental) by dscacheutil
Test.3 access through DNS resolution

Additional documentation e.g., KEPs (Kubernetes Enhancement Proposals), usage docs, etc.:

NONE

@k8s-ci-robot k8s-ci-robot added kind/cleanup Categorizes issue or PR as related to cleaning up code, process, or technical debt. area/testing kind/failing-test Categorizes issue or PR as related to a consistently or frequently failing test. cncf-cla: yes Indicates the PR's author has signed the CNCF CLA. labels May 1, 2020
@k8s-ci-robot
Copy link
Contributor

Hi @govargo. Thanks for your PR.

I'm waiting for a kubernetes member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

I understand the commands that are listed here.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

@k8s-ci-robot k8s-ci-robot added the needs-ok-to-test Indicates a PR that requires an org member to verify it is safe to test. label May 1, 2020
@k8s-ci-robot
Copy link
Contributor

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: govargo
To complete the pull request process, please assign priyawadhwa
You can assign the PR to them by writing /assign @priyawadhwa in a comment when ready.

The full list of commands accepted by this bot can be found here.

Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@k8s-ci-robot k8s-ci-robot added the size/M Denotes a PR that changes 30-99 lines, ignoring generated files. label May 1, 2020
@govargo
Copy link
Contributor Author

govargo commented May 1, 2020

/assign @priyawadhwa

@minikube-bot
Copy link
Collaborator

Can one of the admins verify this patch?

@medyagh
Copy link
Member

medyagh commented May 1, 2020

/ok-to-test

@k8s-ci-robot k8s-ci-robot added ok-to-test Indicates a non-member PR verified by an org member that is safe to test. and removed needs-ok-to-test Indicates a PR that requires an org member to verify it is safe to test. labels May 1, 2020
@minikube-pr-bot
Copy link

kvm2 Driver
docker Driver

@minikube-pr-bot
Copy link

kvm2 Driver
Times for minikube: [65.635405993 85.30171274799999 64.891659754]
Average time for minikube: 71.942926165

Times for Minikube (PR 7956): [67.16044052800001 64.244560162 66.422675896]
Average time for Minikube (PR 7956): 65.942558862

Averages Time Per Log

+--------------------------------+-----------+--------------------+
|              LOG               | MINIKUBE  | MINIKUBE (PR 7956) |
+--------------------------------+-----------+--------------------+
| * minikube v1.10.0-beta.2 on   |  0.068552 |           0.062580 |
| Debian 9.11                    |           |                    |
| * Using the kvm2 driver based  |  0.023346 |           0.023094 |
| on existing profile            |           |                    |
| * Starting control plane node  |  0.012520 |           0.003583 |
| minikube in cluster minikube   |           |                    |
| * Creating kvm2 VM (CPUs=2,    | 40.503228 |          40.283395 |
| Memory=3700MB, Disk=20000MB)   |           |                    |
| ...                            |           |                    |
| * Preparing Kubernetes v1.18.1 | 29.131203 |          23.185158 |
| on Docker 19.03.8 ...          |           |                    |
| * Verifying Kubernetes         |  1.501941 |           1.333008 |
| components...                  |           |                    |
| * Enabled addons:              |  0.620280 |           0.966116 |
| default-storageclass,          |           |                    |
| storage-provisioner            |           |                    |
| * Done! kubectl is now         |  0.078333 |           0.080005 |
| configured to use "minikube"   |           |                    |
|                                |  0.003522 |           0.005618 |
+--------------------------------+-----------+--------------------+

docker Driver
Times for minikube: [29.169620236 28.169981681 29.483255589000002]
Average time for minikube: 28.940952502

Times for Minikube (PR 7956): [26.673651135 27.172496464999995 26.077300579999996]
Average time for Minikube (PR 7956): 26.641149393333333

Averages Time Per Log

+----------------------------------------+-----------+--------------------+
|                  LOG                   | MINIKUBE  | MINIKUBE (PR 7956) |
+----------------------------------------+-----------+--------------------+
| * minikube v1.10.0-beta.2 on           |  0.078060 |           0.076448 |
| Debian 9.11                            |           |                    |
| * Using the docker driver              |  0.002585 |           0.002759 |
| based on existing profile              |           |                    |
| * Starting control plane node          |  0.060931 |           0.060098 |
| minikube in cluster minikube           |           |                    |
| * Creating docker container            |  7.892031 |           7.712727 |
| (CPUs=2, Memory=3700MB) ...            |           |                    |
| * Preparing Kubernetes v1.18.1         |  0.125557 |           0.126197 |
| on Docker 19.03.2 ...                  |           |                    |
|   -                                    | 19.406760 |          17.585129 |
| kubeadm.pod-network-cidr=10.244.0.0/16 |           |                    |
| * Verifying Kubernetes                 |  1.231661 |           0.888709 |
| components...                          |           |                    |
| * Enabled addons:                      |  0.073739 |           0.103855 |
| default-storageclass,                  |           |                    |
| storage-provisioner                    |           |                    |
| * Done! kubectl is now                 |  0.066681 |           0.079212 |
| configured to use "minikube"           |           |                    |
|                                        |  0.002948 |           0.006015 |
+----------------------------------------+-----------+--------------------+

@govargo
Copy link
Contributor Author

govargo commented May 1, 2020

/retest

@TravisBuddy
Copy link

Travis tests have failed

Hey @govargo,
Please read the following log in order to understand the failure reason.
It'll be awesome if you fix what's wrong and commit the changes.

TravisBuddy Request Identifier: 7b304550-8c1e-11ea-bf8a-61073f267ac6

@govargo
Copy link
Contributor Author

govargo commented May 2, 2020

I saw this failure first time...

E0502 02:40:48.608570   11443 out.go:102] [unset errFile]: * 
E0502 02:40:48.608798   11443 out.go:102] [unset errFile]: X Error getting primary control plane: remove /tmp/profile492025635/.minikube/profiles/config.json: no such file or directory
E0502 02:40:48.608826   11443 out.go:102] [unset errFile]: * 
E0502 02:40:48.608846   11443 out.go:102] [unset errFile]: * minikube is exiting due to an error. If the above message is not useful, open an issue:
E0502 02:40:48.608867   11443 out.go:102] [unset errFile]:   - https://github.com/kubernetes/minikube/issues/new/choose
FAIL	k8s.io/minikube/pkg/addons	0.032s

/retest

@minikube-pr-bot
Copy link

kvm2 Driver
Times for minikube: [67.843545081 65.3053756 66.047429666]
Average time for minikube: 66.39878344899999

Times for Minikube (PR 7956): [63.84015205000001 66.40918797 64.89939340699999]
Average time for Minikube (PR 7956): 65.049577809

Averages Time Per Log

+--------------------------------+-----------+--------------------+
|              LOG               | MINIKUBE  | MINIKUBE (PR 7956) |
+--------------------------------+-----------+--------------------+
| * minikube v1.10.0-beta.2 on   |  0.058709 |           0.061733 |
| Debian 9.11                    |           |                    |
| * Using the kvm2 driver based  |  0.022101 |           0.023812 |
| on existing profile            |           |                    |
| * Starting control plane node  |  0.003742 |           0.003198 |
| minikube in cluster minikube   |           |                    |
| * Creating kvm2 VM (CPUs=2,    | 41.381635 |          40.585134 |
| Memory=3700MB, Disk=20000MB)   |           |                    |
| ...                            |           |                    |
| * Preparing Kubernetes v1.18.1 | 22.252521 |          21.980028 |
| on Docker 19.03.8 ...          |           |                    |
| * Verifying Kubernetes         |  1.709690 |           1.397866 |
| components...                  |           |                    |
| * Enabled addons:              |  0.880350 |           0.901625 |
| default-storageclass,          |           |                    |
| storage-provisioner            |           |                    |
| * Done! kubectl is now         |  0.086049 |           0.090416 |
| configured to use "minikube"   |           |                    |
|                                |  0.003986 |           0.005766 |
+--------------------------------+-----------+--------------------+

docker Driver
Times for minikube: [26.763817061999998 27.224714675 28.183157453999996]
Average time for minikube: 27.390563063666665

Times for Minikube (PR 7956): [28.006389807000005 27.175415786 26.786381156000004]
Average time for Minikube (PR 7956): 27.322728916333332

Averages Time Per Log

+----------------------------------------+-----------+--------------------+
|                  LOG                   | MINIKUBE  | MINIKUBE (PR 7956) |
+----------------------------------------+-----------+--------------------+
| * minikube v1.10.0-beta.2 on           |  0.075205 |           0.077798 |
| Debian 9.11                            |           |                    |
| * Using the docker driver              |  0.002548 |           0.002485 |
| based on existing profile              |           |                    |
| * Starting control plane node          |  0.061226 |           0.061640 |
| minikube in cluster minikube           |           |                    |
| * Creating docker container            |  7.920649 |           7.821947 |
| (CPUs=2, Memory=3700MB) ...            |           |                    |
| * Preparing Kubernetes v1.18.1         |  0.124111 |           0.125536 |
| on Docker 19.03.2 ...                  |           |                    |
|   -                                    | 18.062917 |          18.193350 |
| kubeadm.pod-network-cidr=10.244.0.0/16 |           |                    |
| * Verifying Kubernetes                 |  0.892976 |           0.906833 |
| components...                          |           |                    |
| * Enabled addons:                      |  0.179653 |           0.064855 |
| default-storageclass,                  |           |                    |
| storage-provisioner                    |           |                    |
| * Done! kubectl is now                 |  0.068328 |           0.064687 |
| configured to use "minikube"           |           |                    |
|                                        |  0.002951 |           0.003596 |
+----------------------------------------+-----------+--------------------+

}
dnsIP := "@" + ip.String()

// Test.2-1 DNS resolution by dig (experimental): https://minikube.sigs.k8s.io/docs/handbook/accessing/#dns-resolution-experimental
Copy link
Member

Choose a reason for hiding this comment

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

instead of adding comment test1
please use a t.Run("serial"){ } with 3 subtests, that run in a for loop. (to make sure they are in order. like this test

t.Run("serial", func(t *testing.T) {

Copy link
Contributor Author

@govargo govargo May 2, 2020

Choose a reason for hiding this comment

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

Thanks for your advice!
I'll look it.

@k8s-ci-robot k8s-ci-robot added size/L Denotes a PR that changes 100-499 lines, ignoring generated files. and removed size/M Denotes a PR that changes 30-99 lines, ignoring generated files. labels May 2, 2020
@codecov-io
Copy link

codecov-io commented May 2, 2020

Codecov Report

Merging #7956 into master will decrease coverage by 0.26%.
The diff coverage is n/a.

Impacted file tree graph

@@            Coverage Diff             @@
##           master    #7956      +/-   ##
==========================================
- Coverage   36.04%   35.78%   -0.27%     
==========================================
  Files         144      143       -1     
  Lines        9196     9174      -22     
==========================================
- Hits         3315     3283      -32     
- Misses       5480     5490      +10     
  Partials      401      401              
Impacted Files Coverage Δ
cmd/minikube/cmd/start.go 15.39% <0.00%> (-0.23%) ⬇️
cmd/minikube/cmd/start_flags.go 50.97% <0.00%> (-0.18%) ⬇️
pkg/minikube/sshutil/sshutil.go

@govargo
Copy link
Contributor Author

govargo commented May 2, 2020

@medyagh
I tried t.Run("serial"){ } with subtests in test/integration/fn_tunnel_cmd.go, but it doesn't work correclty first time.
Perhaps nested t.Run might have caused conflict.
(TestFunctional(parallel) -> validateTunnelCmd -> (added)t.Run("serial"){} not working )

So I made the tests independent such as test/integration/pause_test.go.
I renamed test/integration/fn_tunnel_cmd.go to tunnel_test.go.
And I deleted validateTunnelCmd from TestFunctional.

I don't understand E2E integration test scripts at all.
If I have to change those scripts, please let me know.

@minikube-pr-bot
Copy link

kvm2 Driver
Times for minikube: [67.39496730299999 66.135696167 65.265688536]
Average time for minikube: 66.26545066866666

Times for Minikube (PR 7956): [65.154739951 65.058502576 64.455458615]
Average time for Minikube (PR 7956): 64.88956704733333

Averages Time Per Log

+--------------------------------+-----------+--------------------+
|              LOG               | MINIKUBE  | MINIKUBE (PR 7956) |
+--------------------------------+-----------+--------------------+
| * minikube v1.10.0-beta.2 on   |  0.060861 |           0.067727 |
| Debian 9.11                    |           |                    |
| * Using the kvm2 driver based  |  0.022373 |           0.022002 |
| on existing profile            |           |                    |
| * Starting control plane node  |  0.003713 |           0.003918 |
| minikube in cluster minikube   |           |                    |
| * Creating kvm2 VM (CPUs=2,    | 40.243758 |          40.053515 |
| Memory=3700MB, Disk=20000MB)   |           |                    |
| ...                            |           |                    |
| * Preparing Kubernetes v1.18.1 | 23.382182 |          22.361183 |
| on Docker 19.03.8 ...          |           |                    |
| * Verifying Kubernetes         |  1.795223 |           1.441926 |
| components...                  |           |                    |
| * Enabled addons:              |  0.655062 |           0.856645 |
| default-storageclass,          |           |                    |
| storage-provisioner            |           |                    |
| * Done! kubectl is now         |  0.096870 |           0.077911 |
| configured to use "minikube"   |           |                    |
|                                |  0.005407 |           0.004739 |
+--------------------------------+-----------+--------------------+

docker Driver
Times for minikube: [28.035486844999998 27.193199762000003 27.859204724999998]
Average time for minikube: 27.695963777333333

Times for Minikube (PR 7956): [27.821524239000002 26.020596425999997 26.618272315]
Average time for Minikube (PR 7956): 26.820130993333333

Averages Time Per Log

+----------------------------------------+-----------+--------------------+
|                  LOG                   | MINIKUBE  | MINIKUBE (PR 7956) |
+----------------------------------------+-----------+--------------------+
| * minikube v1.10.0-beta.2 on           |  0.084297 |           0.078992 |
| Debian 9.11                            |           |                    |
| * Using the docker driver              |  0.004847 |           0.002549 |
| based on existing profile              |           |                    |
| * Starting control plane node          |  0.063397 |           0.062681 |
| minikube in cluster minikube           |           |                    |
| * Creating docker container            |  8.209816 |           7.797646 |
| (CPUs=2, Memory=3700MB) ...            |           |                    |
| * Preparing Kubernetes v1.18.1         |  0.148553 |           0.127745 |
| on Docker 19.03.2 ...                  |           |                    |
|   -                                    | 17.892057 |          17.754036 |
| kubeadm.pod-network-cidr=10.244.0.0/16 |           |                    |
| * Verifying Kubernetes                 |  1.219900 |           0.820529 |
| components...                          |           |                    |
| * Enabled addons:                      |  0.002607 |           0.100137 |
| default-storageclass,                  |           |                    |
| storage-provisioner                    |           |                    |
| * Done! kubectl is now                 |  0.066948 |           0.070770 |
| configured to use "minikube"           |           |                    |
|                                        |  0.003543 |           0.005047 |
+----------------------------------------+-----------+--------------------+

@govargo
Copy link
Contributor Author

govargo commented May 2, 2020

/retest

@k8s-ci-robot k8s-ci-robot removed the size/L Denotes a PR that changes 100-499 lines, ignoring generated files. label May 2, 2020
@minikube-pr-bot
Copy link

kvm2 Driver
Times for minikube: [71.357046532 66.972948381 63.496560684]
Average time for minikube: 67.27551853233334

Times for Minikube (PR 7956): [64.192190425 66.647977383 67.25618308899998]
Average time for Minikube (PR 7956): 66.03211696566666

Averages Time Per Log

+--------------------------------+-----------+--------------------+
|              LOG               | MINIKUBE  | MINIKUBE (PR 7956) |
+--------------------------------+-----------+--------------------+
| * minikube v1.10.0-beta.2 on   |  0.067708 |           0.061101 |
| Debian 9.11                    |           |                    |
| * Using the kvm2 driver based  |  0.021904 |           0.021511 |
| on existing profile            |           |                    |
| * Starting control plane node  |  0.003795 |           0.003716 |
| minikube in cluster minikube   |           |                    |
| * Creating kvm2 VM (CPUs=2,    | 42.184798 |          41.202026 |
| Memory=3700MB, Disk=20000MB)   |           |                    |
| ...                            |           |                    |
| * Preparing Kubernetes v1.18.1 | 22.914234 |          22.352510 |
| on Docker 19.03.8 ...          |           |                    |
| * Verifying Kubernetes         |  1.501011 |           1.382474 |
| components...                  |           |                    |
| * Enabled addons:              |  0.495741 |           0.926250 |
| default-storageclass,          |           |                    |
| storage-provisioner            |           |                    |
| * Done! kubectl is now         |  0.081759 |           0.077048 |
| configured to use "minikube"   |           |                    |
|                                |  0.004568 |           0.005482 |
+--------------------------------+-----------+--------------------+

docker Driver
Times for minikube: [27.878947863000004 28.320203163000002 26.8867371]
Average time for minikube: 27.695296042000006

Times for Minikube (PR 7956): [27.988238541 28.051676789 28.168322204000003]
Average time for Minikube (PR 7956): 28.069412511333336

Averages Time Per Log

+----------------------------------------+-----------+--------------------+
|                  LOG                   | MINIKUBE  | MINIKUBE (PR 7956) |
+----------------------------------------+-----------+--------------------+
| * minikube v1.10.0-beta.2 on           |  0.082571 |           0.083562 |
| Debian 9.11                            |           |                    |
| * Using the docker driver              |  0.002527 |           0.003402 |
| based on existing profile              |           |                    |
| * Starting control plane node          |  0.062522 |           0.062373 |
| minikube in cluster minikube           |           |                    |
| * Creating docker container            |  7.932356 |           7.989743 |
| (CPUs=2, Memory=3700MB) ...            |           |                    |
| * Preparing Kubernetes v1.18.1         |  0.150355 |           0.127969 |
| on Docker 19.03.2 ...                  |           |                    |
|   -                                    | 18.131151 |          18.596666 |
| kubeadm.pod-network-cidr=10.244.0.0/16 |           |                    |
| * Verifying Kubernetes                 |  1.256870 |           1.000555 |
| components...                          |           |                    |
| * Enabled addons:                      |  0.003324 |           0.133143 |
| default-storageclass,                  |           |                    |
| storage-provisioner                    |           |                    |
| * Done! kubectl is now                 |  0.068324 |           0.066444 |
| configured to use "minikube"           |           |                    |
|                                        |  0.005297 |           0.005556 |
+----------------------------------------+-----------+--------------------+

@govargo govargo added the do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. label May 2, 2020
@govargo
Copy link
Contributor Author

govargo commented May 2, 2020

After trying source change, only HyperKit_macOS failed although nginx-svc has correct IP 10.108.42.59.

https://storage.googleapis.com/minikube-builds/logs/7956/83fd200/HyperKit_macOS.html#fail_TestTunnel%2fserial%2fAccessDirect

--- FAIL: TestTunnel/serial/AccessDirect (135.43s)
tunnel_test.go:203: failed to hit nginx at "http://10.108.42.59": Temporary Error: Get http://10.108.42.59: net/http: request canceled while waiting for connection (Client.Timeout exceeded while awaiting headers)
tunnel_test.go:205: (dbg) Run:  kubectl --context tunnel-20200502040252-4586 get svc nginx-svc
tunnel_test.go:209: failed to kubectl get svc nginx-svc:
NAME        TYPE           CLUSTER-IP     EXTERNAL-IP    PORT(S)        AGE
nginx-svc   LoadBalancer   10.108.42.59   10.108.42.59   80:32189/TCP   2m25s
tunnel_test.go:216: expected body to contain "Welcome to nginx!", but got *""*

But other tests on other OS are success.

Does anyone have any ideas why is macOS test failure? (macOS jenkins flake? Or need to set PROXY env?)
My thought is that macOS server's DNS configuration doesn't works correctly...

@govargo
Copy link
Contributor Author

govargo commented May 3, 2020

/retest

@k8s-ci-robot k8s-ci-robot added size/XL Denotes a PR that changes 500-999 lines, ignoring generated files. and removed size/L Denotes a PR that changes 100-499 lines, ignoring generated files. labels May 4, 2020
@minikube-pr-bot
Copy link

kvm2 Driver
Times for minikube: [68.729854817 65.823622738 67.381234861]
Average time for minikube: 67.31157080533333

Times for Minikube (PR 7956): [65.281246283 66.44230932800001 63.993592288]
Average time for Minikube (PR 7956): 65.23904929966668

Averages Time Per Log

+--------------------------------+-----------+--------------------+
|              LOG               | MINIKUBE  | MINIKUBE (PR 7956) |
+--------------------------------+-----------+--------------------+
| * minikube v1.10.0-beta.2 on   |  0.061972 |           0.061600 |
| Debian 9.11                    |           |                    |
| * Using the kvm2 driver based  |  0.021684 |           0.020907 |
| on existing profile            |           |                    |
| * Starting control plane node  |  0.003282 |           0.002951 |
| minikube in cluster minikube   |           |                    |
| * Creating kvm2 VM (CPUs=2,    | 41.915075 |          41.066992 |
| Memory=3700MB, Disk=20000MB)   |           |                    |
| ...                            |           |                    |
| * Preparing Kubernetes v1.18.1 | 23.268462 |          22.003351 |
| on Docker 19.03.8 ...          |           |                    |
| * Verifying Kubernetes         |  1.282900 |           1.402687 |
| components...                  |           |                    |
| * Enabled addons:              |  0.678176 |           0.579536 |
| default-storageclass,          |           |                    |
| storage-provisioner            |           |                    |
| * Done! kubectl is now         |  0.075797 |           0.094015 |
| configured to use "minikube"   |           |                    |
|                                |  0.004222 |           0.007011 |
+--------------------------------+-----------+--------------------+

docker Driver
Times for minikube: [29.672172490999998 26.877697932000004 28.682116876]
Average time for minikube: 28.410662433

Times for Minikube (PR 7956): [28.441599499999995 28.603291416999994 28.586532047]
Average time for Minikube (PR 7956): 28.543807654666665

Averages Time Per Log

+----------------------------------------+-----------+--------------------+
|                  LOG                   | MINIKUBE  | MINIKUBE (PR 7956) |
+----------------------------------------+-----------+--------------------+
| * minikube v1.10.0-beta.2 on           |  0.077384 |           0.080379 |
| Debian 9.11                            |           |                    |
| * Using the docker driver              |  0.002235 |           0.002566 |
| based on existing profile              |           |                    |
| * Starting control plane node          |  0.065336 |           0.064702 |
| minikube in cluster minikube           |           |                    |
| * Creating docker container            |  8.097431 |           7.798320 |
| (CPUs=2, Memory=3700MB) ...            |           |                    |
| * Preparing Kubernetes v1.18.1         |  0.149685 |           0.124554 |
| on Docker 19.03.2 ...                  |           |                    |
|   -                                    | 18.620177 |          19.187961 |
| kubeadm.pod-network-cidr=10.244.0.0/16 |           |                    |
| * Verifying Kubernetes                 |  1.075840 |           1.207771 |
| components...                          |           |                    |
| * Enabled addons:                      |  0.255318 |           0.002450 |
| default-storageclass,                  |           |                    |
| storage-provisioner                    |           |                    |
| * Done! kubectl is now                 |  0.062961 |           0.068742 |
| configured to use "minikube"           |           |                    |
|                                        |  0.004294 |           0.006364 |
+----------------------------------------+-----------+--------------------+

@@ -124,7 +124,6 @@ func TestFunctional(t *testing.T) {
{"ServiceCmd", validateServiceCmd},
{"AddonsCmd", validateAddonsCmd},
{"PersistentVolumeClaim", validatePersistentVolumeClaim},
{"TunnelCmd", validateTunnelCmd},
Copy link
Member

Choose a reason for hiding this comment

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

I think tunnel test should still be part of Functional Tests, since we consider this test as a Core Test that tests all functionalities of minikube.

when I meant to do it in serial, I meant tunnel test itself runs in parallel but all of it is own sub tests run in serial.

Copy link
Contributor Author

@govargo govargo May 5, 2020

Choose a reason for hiding this comment

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

@medyagh
First time I tried to add the serial test into validateTunnelCmd , but the subtests failed because the process stopped like a deadlock then.

After your this comment, I tried to add serial test into validateTunnelCmd of TestFunctional again.
And now serial tunnel tests works and the HyperKit_macOS test all successed!!! 💯

https://storage.googleapis.com/minikube-builds/logs/7956/884f0e2/HyperKit_macOS.html#pass_TestFunctional%2fparallel%2fTunnelCmd%2fserial%2fAccessThroughDNS

@k8s-ci-robot k8s-ci-robot added size/L Denotes a PR that changes 100-499 lines, ignoring generated files. and removed size/XL Denotes a PR that changes 500-999 lines, ignoring generated files. labels May 5, 2020
@minikube-pr-bot
Copy link

kvm2 Driver
Times for minikube: [64.47253854200001 64.756078382 64.442763547]
Average time for minikube: 64.55712682366665

Times for Minikube (PR 7956): [65.41044705099999 64.529045405 67.00706772199999]
Average time for Minikube (PR 7956): 65.64885339266668

Averages Time Per Log

+--------------------------------+-----------+--------------------+
|              LOG               | MINIKUBE  | MINIKUBE (PR 7956) |
+--------------------------------+-----------+--------------------+
| * minikube v1.10.0-beta.2 on   |  0.067323 |           0.061460 |
| Debian 9.11                    |           |                    |
| * Using the kvm2 driver based  |  0.023143 |           0.020954 |
| on existing profile            |           |                    |
| * Starting control plane node  |  0.011237 |           0.003286 |
| minikube in cluster minikube   |           |                    |
| * Creating kvm2 VM (CPUs=2,    | 39.504397 |          39.927032 |
| Memory=3700MB, Disk=20000MB)   |           |                    |
| ...                            |           |                    |
| * Preparing Kubernetes v1.18.1 | 22.402480 |          23.266184 |
| on Docker 19.03.8 ...          |           |                    |
| * Verifying Kubernetes         |  1.577527 |           1.800224 |
| components...                  |           |                    |
| * Enabled addons:              |  0.886218 |           0.480557 |
| default-storageclass,          |           |                    |
| storage-provisioner            |           |                    |
| * Done! kubectl is now         |  0.081299 |           0.082630 |
| configured to use "minikube"   |           |                    |
|                                |  0.003504 |           0.006527 |
+--------------------------------+-----------+--------------------+

docker Driver
Times for minikube: [27.532069904 27.471825003000003 26.637269338]
Average time for minikube: 27.213721415

Times for Minikube (PR 7956): [31.624924904000004 28.928593534999997 28.407475956]
Average time for Minikube (PR 7956): 29.653664798333335

Averages Time Per Log

+----------------------------------------+-----------+--------------------+
|                  LOG                   | MINIKUBE  | MINIKUBE (PR 7956) |
+----------------------------------------+-----------+--------------------+
| * minikube v1.10.0-beta.2 on           |  0.074603 |           0.081685 |
| Debian 9.11                            |           |                    |
| * Using the docker driver              |  0.002646 |           0.002653 |
| based on existing profile              |           |                    |
| * Starting control plane node          |  0.062903 |           0.061384 |
| minikube in cluster minikube           |           |                    |
| * Creating docker container            |  8.056829 |           7.758828 |
| (CPUs=2, Memory=3700MB) ...            |           |                    |
| * Preparing Kubernetes v1.18.1         |  0.122584 |           0.146134 |
| on Docker 19.03.2 ...                  |           |                    |
|   -                                    | 17.975859 |          20.674972 |
| kubeadm.pod-network-cidr=10.244.0.0/16 |           |                    |
| * Verifying Kubernetes                 |  0.846846 |           0.856376 |
| components...                          |           |                    |
| * Enabled addons:                      |  0.002676 |           0.003933 |
| default-storageclass,                  |           |                    |
| storage-provisioner                    |           |                    |
| * Done! kubectl is now                 |  0.064270 |           0.063810 |
| configured to use "minikube"           |           |                    |
|                                        |  0.004504 |           0.003889 |
+----------------------------------------+-----------+--------------------+

@govargo govargo removed the do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. label May 5, 2020
@govargo govargo changed the title Moved TestFunctional/parallel/TunnelCmd into TestTunnel & Changed serial test TestFunctional/parallel/TunnelCmd into serial subtest May 5, 2020
Copy link
Member

@medyagh medyagh left a comment

Choose a reason for hiding this comment

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

looks good to me. thank you

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/testing cncf-cla: yes Indicates the PR's author has signed the CNCF CLA. kind/cleanup Categorizes issue or PR as related to cleaning up code, process, or technical debt. kind/failing-test Categorizes issue or PR as related to a consistently or frequently failing test. ok-to-test Indicates a non-member PR verified by an org member that is safe to test. size/L Denotes a PR that changes 100-499 lines, ignoring generated files.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

8 participants