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.

Sign up for GitHub

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

Jump to bottom

Workflow failed - driver_ws2019 #4039

Closed
github-actions bot opened this issue Nov 23, 2024 · 5 comments
Closed

Workflow failed - driver_ws2019 #4039

github-actions bot opened this issue Nov 23, 2024 · 5 comments
Assignees
@mikeagun @shankarseal
Labels
bug Something isn't working ci/cd Issue is specific to CI/CD P2 triaged Discussed in a triage meeting
Milestone
2501

Comments

@github-actions
Copy link
Contributor

Failed Run
Codebase
Test name - driver_ws2019
@github-actions github-actions bot added bug Something isn't working ci/cd Issue is specific to CI/CD labels Nov 23, 2024
@github-actions GitHub Actions
Copy link
Contributor Author

Failed Run
Codebase
Test name - driver_ws2019

@shankarseal shankarseal self-assigned this Nov 25, 2024
@shankarseal shankarseal added this to the 2501 milestone Nov 25, 2024
@shankarseal shankarseal added the P2 label Nov 25, 2024
@shankarseal
Copy link
Collaborator

Test logs show that stopping netebpf ext driver hung and that caused the automation to collect some diagnostics information. I will investigate.

@shankarseal
Copy link
Collaborator

There is also a fuzzer debug failure. @mikeagun please investigate.

@shankarseal shankarseal added the triaged Discussed in a triage meeting label Nov 25, 2024
@mikeagun
Copy link
Collaborator

mikeagun commented Nov 25, 2024 •
edited
Loading

The fuzzer crash is from test timeout (I also ran the test case in the artifacts 1000 times on 8 workers a couple times with no crashes).

From the dump it is waiting in cxplat_wait_for_rundown_protection_release when killed, and from the test logs the timeout is set to 60 min, so it looks like it hanged after finishing the tests during cleanup.

@shankarseal
Copy link
Collaborator

The fuzzer crash was due to a hang that we should continue to debug.
This issue is for driver_ws2019 failure which was due to netebpext hanging on stop. The automation took a snapshot of the VM at this state, After resuming the netebpfext stopped on demand. So whatever it was, the repro was lost in the snapshot.

@shankarseal shankarseal closed this as not planned Won't fix, can't repro, duplicate, stale Nov 26, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@mikeagun mikeagun

@shankarseal shankarseal

Labels
bug Something isn't working ci/cd Issue is specific to CI/CD P2 triaged Discussed in a triage meeting
Projects
None yet
Milestone
2501
Development

No branches or pull requests
2 participants
@mikeagun @shankarseal