-
Notifications
You must be signed in to change notification settings - Fork 232
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
Workflow failed - km_mt_stress_tests_restart_extension #3097
Comments
Failed Run |
Failed Run |
Failed Run |
Failed Run |
Failed Run |
Failed Run |
Failed Run |
Failed Run |
Failed Run |
Failed Run |
Failed Run |
Failed Run |
First off, the generation of kernel-mode crash dumps in CI/CD runs (at least for the kernel-mode mt stress tests) seems to be inconsistent. i.e.: The https://github.com/microsoft/ebpf-for-windows/actions/runs/7327818979 run shows a failure for the debug version of the OTOH, the prior https://github.com/microsoft/ebpf-for-windows/actions/runs/7320276834 run also shows the same failure but does contain the related Test-Logs-km_mt_stress_tests_restart_extension-x64-Debug artifact with a valid kernel mode dump. (@rectified95: any idea why this is happening?) Based on the available dump, the crash is caused by an explicit
This code should've been skipped as we first check if the client is detached just above (seen in the data struct dumps below). This looks like some edge-case race between netebpfext and wfp. Data struct dumps at the point of the crash:
Stack trace:
|
Failed Run |
Failed Run |
Failed Run |
Failed Run |
Failed Run |
Failed Run |
Failed Run |
Failed Run |
Failed Run |
Failed Run
Codebase
Test name -
km_mt_stress_tests_restart_extension
The text was updated successfully, but these errors were encountered: