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

Use the same scripts/infrastructure for running ACE and Syzkaller tests #2

Open
hayley-leblanc opened this issue Nov 18, 2023 · 1 comment
Labels
help wanted Extra attention is needed

Comments

@hayley-leblanc
Copy link
Collaborator

Right now the ACE and Syzkaller tests have distinct test harnesses and separate workflows, which is complicated and increases the amount of effort if you want to run both. We should have a single workflow with an option to choose which one you want to run (plus additional options to specify ACE tests, etc.)

@hayley-leblanc hayley-leblanc added the help wanted Extra attention is needed label Nov 18, 2023
@hayley-leblanc
Copy link
Collaborator Author

An additional thing that would be useful here is to improve handling of kernel panics that occur during ACE tests; right now the developer has to monitor the tests and watch for these. Syzkaller already has some ways to handle kernel panics and restart a VM that has crashed, so the same logic could likely be reused.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
help wanted Extra attention is needed
Projects
None yet
Development

No branches or pull requests

1 participant