new afl++ token/libafl experiment

[vanhauser-thc]

hopefully fuzzbench is not throwing up again :)

[jonathanmetzman]

Weird that CI is actually in a good state now

[vanhauser-thc]

I meant the state the last weeks when there were spurious build failures.

but it seems they are here again. aflplusplus, _tokens, _tokens_only all share the same commit hash, but one fails in standard, one in oss and another one in oss too.
if aflplusplus fails in oss, the other two have to as well if there would really be a bug. and _tokens and tokens_only need to fail the same tests, but one is oss and the other is standard.

[vanhauser-thc]

hmm it is again spurious checkout failures, at least for one. @alan32liu

[DonggeLiu]

Hi @vanhauser-thc, I was investigating this, but I really did not find a possible explanation:
It seems more like a strange issue in git/docker than in your code or FuzzBench.

But I guess there are several more things we can try together, although they might not matter:

1. Specify and only pull the belonging branch of the commit. Given the commit e4ff0eb is in dev instead of the default (stable), maybe do git clone -b dev https://github.com/AFLplusplus/AFLplusplus /afl.
2. Reorganise the docker commands, e.g. splitting cd /afl and git checkout to two RUNs.

Again, I don't think these will somehow solve the issue, but it might avoid triggering them.
Please let me know what you think.