Centipede not always setting sanitized_target

[jonathanmetzman]

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.

[jonathanmetzman]

I deleted centipede_chrome_asan. It was being used in variant task. Variant task should probably not mess with jobs that don't have a fuzzer.

[DonggeLiu]

Ah yes. I can make this fix while adding the support for using a sanitized binary only.

[DonggeLiu]

Is it a good idea to always download binaries to the sanitized binary directory? This is more consistent with the current design and automatically solves this issue.