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

No report is written if a benchmark run crashes before finishing #28

Open
gnuvince opened this issue Apr 8, 2016 · 1 comment
Open

Comments

@gnuvince
Copy link

gnuvince commented Apr 8, 2016

If benchmarks 1, 2, and 3 have been correctly executed, but benchmark 4 fails, wu report will not show the timings for benchmarks 1, 2, 3. This is annoying when running a large number of long-running benchmarks and one fails; the entire suite needs to be re-executed rather than resuming from the failure point.

@elavoie
Copy link
Member

elavoie commented Apr 13, 2016

Yes. The work around for now is to first execute all the benchmarks once with a small input to check they all execute correctly, and then launch the long running ones for peformance analysis.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants