Rollback transactions properly
Open
- Dominant language
- Python
- Stars
- 1.2k
- Forks
- 302
- PR merge metrics
- No merged PRs in 30d
Description
During the halloweeen experiment and sometime a few months ago (when @inferno-chromium upgraded the size of the db instance), we had to manually intervene in the db because Fuzzbench could not properly recover from a failed transaction. We need to fix this.
I'm about >50% this is an issue that can/should be fixed. I'm not 100% on the details but want to mention it to ensure it doesn't get lost.
Contributor guide
Assessment
This issue has not been assessed yet.