No, but from my experience it happens only with some targets and, sometimes, re-running the autotuning process from scratch solves the issue.
@gasgallo could you please share target that work. Im a bit lost, trying to brute force target that work for some time now 
I had no problem when targeting x86 but I’m having trouble with arm-cpu. You could also try to rerun a quick autotuning from scratch and double check if you still get the same error from the new log.