Add drush cr before running config:status

[mmatsoo]

In a multisite environment, perhaps because of running Tugboat tasks in parallel(?), a false positive reported a config diff between a multisite and the default config, even though the multisite in question was not being touched. Manually clearing the offending site's cache with drush cr allowed for the drush config:status test to complete successfully.

One possible solution is to run drush cr before running drush config:status. It will slow down the testing, but hopefully compare apples to apples.

usher/src/Robo/Plugin/Commands/ValidateConfigCommands.php

Line 66 in 90b5979

$result = $this->taskExec("$this->drupalRoot/../vendor/bin/drush config:status --format=json")