Sometimes compilation/build itself fails on glusterfs patches. It's wasted resources to run other tests/jobs if basic smoke doesn't pass. On an unrelated note: It is unfortunate to see developers (re)trigger centos7 regression *before* they have witnessed smoke test passing.
I have plans to fix this once distributed testing is in production. It will all be one pipeline job which will stop executing when it sees one failure.