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

afl++ shows up on openssl_x509 benchmark in 2020-03-11 report even though build is broken #112

Closed
jonathanmetzman opened this issue Mar 16, 2020 · 0 comments · Fixed by #307
Closed

afl++ shows up on openssl_x509 benchmark in 2020-03-11 report even though build is broken #112

jonathanmetzman opened this issue Mar 16, 2020 · 0 comments · Fixed by #307
Assignees
@jonathanmetzman
Labels
bug Something isn't working

Comments

@jonathanmetzman
Copy link
Contributor

jonathanmetzman commented Mar 16, 2020 •
edited
Loading

See https://www.fuzzbench.com/reports/2020-03-11/index.html
As i reported in #110 the afl++/openssl_x509 failed.
I assume FuzzBench used old docker image. I need to change things to not run trials for a fuzzer,benchmark pair when the build fails.
@jonathanmetzman jonathanmetzman self-assigned this Mar 16, 2020
@jonathanmetzman jonathanmetzman changed the title afl++ shows up in 2020-03-11 report even though it is broken afl++ shows up on openssl_x509 benchmark in 2020-03-11 report even though build is broken Mar 16, 2020
@inferno-chromium inferno-chromium added the bug Something isn't working label Mar 21, 2020
@jonathanmetzman jonathanmetzman mentioned this issue May 6, 2020
Merged
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@jonathanmetzman jonathanmetzman

Labels
bug Something isn't working
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Don't start trials for failed builds google/fuzzbench
2 participants
@inferno-chromium @jonathanmetzman