-
Notifications
You must be signed in to change notification settings - Fork 4.9k
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
[WIP] Fix ValidateTunnelCmd test #8729
Conversation
Hi @11janci. 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 Once the patch is verified, the new status will be reflected by the 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. |
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: 11janci 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 |
Can one of the admins verify this patch? |
Failed test on windows hyperv |
@11janci thanks for picking this task 2020-07-15T18:45:18.4696923Z --- FAIL: TestFunctional/parallel/TunnelCmd/serial/AccessDirect (148.13s) |
35efb9b
to
74da82c
Compare
Codecov Report
@@ Coverage Diff @@
## master #8729 +/- ##
=======================================
Coverage 31.52% 31.52%
=======================================
Files 166 166
Lines 11325 11325
=======================================
Hits 3570 3570
Misses 7322 7322
Partials 433 433 |
e0d3848
to
d58c6cd
Compare
Travis tests have failedHey @11janci, 1st Buildmake test
TravisBuddy Request Identifier: 35dbf8d0-c749-11ea-999c-bf5bae978323 |
eb79da3
to
f4d2cdb
Compare
f4d2cdb
to
21b9eea
Compare
@medyagh I'm afraid I'm gonna need some help with this. For For Any help would be welcome! |
21b9eea
to
8f37f21
Compare
86c5b30
to
bb681f0
Compare
This is expected -- the Docker driver uses the loopback interface. I wouldn't expect it to be on port 80, however.
|
if runtime.GOOS == "windows" { | ||
t.Skip("skipping: access direct test is broken on windows: https://github.com/kubernetes/minikube/issues/8304") | ||
} | ||
//if runtime.GOOS == "windows" { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This should continue to be disabled for the Docker driver.
@@ -435,7 +435,9 @@ jobs: | |||
$env:MINIKUBE_HOME="${pwd}\testhome" | |||
.\minikube-windows-amd64.exe delete --all --purge | |||
Get-VM | Where-Object {$_.Name -ne "DockerDesktopVM"} | Foreach { | |||
Stop-VM -Name $_.Name -Force | |||
.\minikube-windows-amd64.exe delete -p $_.Name | |||
Suspend-VM $_.Name |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I don't think the Suspend-VM/Stop-VM call should be required.
Closing this stale PR - please reopen when you have a chance to address the PR comments. |
Fixes #8304
On windows, when tests run
minikube tunnel
, it does not inherit the elevated privileges of the parent process - it needs to be set explicitly during the invocation. The chosen approach is using powershell and Start-Process because (almost) no additional code changes are required (especially for termination). Other possible approach would be through lower level win specific API, but the required code changes would be much larger.