WIP: Debug flaky parallel/DryRun

[lingsamuel]

Signed-off-by: Ling Samuel [email protected]

a debug PR, do not merge #9785

[k8s-ci-robot]

Hi @lingsamuel. 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]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: lingsamuel
To complete the pull request process, please assign afbjorklund after the PR has been reviewed.
You can assign the PR to them by writing /assign @afbjorklund 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:

• OWNERS

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

[minikube-bot]

Can one of the admins verify this patch?

[medyagh]

@lingsamuel thank you very much for taking this task, this is one of the most annoying flakes on windows and I would love to get to the bottom of it.

I wonder if you have acesss to a windows machine to try it locally ?
if not I could provide you with a Windows machine on Azure for testing, if needed please ping me on Slack, I will provide u credentials for our test machine

[lingsamuel]

@medyagh Thanks! That's what I need, pinged on Slack.
(To verification: my Slack member ID is U01G6SGJQTA)

[k8s-ci-robot]

@lingsamuel: PR needs rebase.

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.

[medyagh]

@lingsamuel any finding from this finding ? Could it be we just have to skip the part of the dry run test on windows that checks the exit code to be a specific code ?

It seems like the exits code as expected is still non 0 but the difference is in What Exact code it is (1 or 128(

[lingsamuel]

Nothing found till now. The exit is abnormal and unstable, couldn't find any way to reproduce it stably.
And I am very sorry, recently I am not working on this, it's harder than what I thought and I am busy in real life.