google / google/clusterfuzz

Centipede not always setting sanitized_target

Open
#3,029 3 comments 0 reactions 1 assignee Claimed by @DonggeLiu View on GitHub
Dominant language
Python
Stars
5.6k
Forks
629
Avg merge
4d 6h
Merged PRs (30d)
22

Description

https://pantheon.corp.google.com/errors/detail/CNiDuO-3_6iKVg;time=P30D?project=google.com:clusterfuzz&utm_source=error-reporting-notification&utm_medium=email&utm_content=new-error&pli=1&rapt=AEjHL4M0aXmFBxioZrxgPwT6SQ-x8Y-w6ciz3IUeU1oVUTk9p3Ha5MOx8lJtxLeh-LPvN5ENvVzq-GNI1gSbwTvlI9dhJQ2i3g

It seems like the fix is making this log an error and bailing out instead of continuing since we can't recover from this error:
https://github.com/google/clusterfuzz/blob/master/src/clusterfuzz/_internal/bot/fuzzers/centipede/engine.py#L205

I'm not sure why this is happening at all though, I thought centipede isn't enabled (I configured the job but disabled) in Chrome clusterfuzz.

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.