You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.)
The text was updated successfully, but these errors were encountered:
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.
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.)
The text was updated successfully, but these errors were encountered: