Waiting for external code coverage should not block the container for analysis

[stof]

In the inspection triggered just now on FOSRestBundle, I saw an unexpected behavior. Running PhpAnalyzer and the other analysis is blocked waiting for the container, which looks used by the Waiting external coverage data step. this is really weird. Waiting the external code coverage should not prevent the other analysis to run.This step should have access to the container only once other analyzers have run IMO, blocking only the final processing of results

[stof]

This looks even worse in the retried inspection: https://scrutinizer-ci.com/g/FriendsOfSymfony/FOSRestBundle/inspections/afc45ad2-43a6-4410-a471-01f7c1e66d65. It is blocking the container after telling me that the data is already available

[theofidry]

+1