CFlite artifacts are called "cifuzz-****" about clusterfuzzlite HOT 5 CLOSED

@jonathanmetzman thoughts? It doesn't seem too important to me, and enabling both at the same time doesn't make much sense AFAICT.

from clusterfuzzlite.

I think as long as CIFuzz is incompatible with forks due to google/oss-fuzz#3731 it kind of makes sense to use both CIFuzz and CFLite. I don't think anyone does this in practice though.

from clusterfuzzlite.

I think ideally we should use "clusterfuzzlite" rather than CIFuzz which isn't really the "brand" we are going to use moving forward.
I can change the name but it will break existing users. Better to do this sooner rather than later but I'm leaning towards not changing it.

from clusterfuzzlite.

There is another place where CFLite doesn't pop up even though I think it should. As far as I can tell there is no alternative to the CIFUZZ environment variable on CFLite.

from clusterfuzzlite.

I think there is exactly one project where both CIFuzz and CFLite are used and I'm pretty sure it can live with artifacts named like this :-) Closing.

from clusterfuzzlite.