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

Support resuming failed runs #14

Open
jvilk opened this issue Feb 8, 2018 · 1 comment
Open

Support resuming failed runs #14

jvilk opened this issue Feb 8, 2018 · 1 comment
Labels
enhancement

Comments

@jvilk
Copy link
Member

jvilk commented Feb 8, 2018 •
edited
Loading

While BLeak works well on most applications / websites that I throw at it, others throw curveballs that often turn up during the diagnose step.

BLeak should serialize an early version of bleak_results.json to disk after the leak locating / ranking stage. If it sees an incomplete bleak_results.json in the specified output folder, it should use it to resume at the diagnose phase.

This will also greatly reduce user frustration if BLeak bugs out on their website after a long run.
@jvilk
Copy link
Member Author

jvilk commented Feb 17, 2018

BLeak should properly do this now, but I haven't tested the functionality yet. :-)

@msridhar msridhar mentioned this issue Mar 30, 2018
Closed
jvilk pushed a commit that referenced this issue Mar 30, 2018
Flush bleak_results.json and bleak_report.log to disk after finding l…
833dce0 
…eaks.

Enables resuming (#14), but not closing until I add a unit test.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
enhancement
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@jvilk