Comment 12 for bug 1323433

Ok, there is no significant activity for this bug for almost a year now and as I may assume from comments in activity log the problem related mostly to how we propagate error messages inside tests' infrastructure, not to the changes in committed PR (as given in description). Lets close this bug as invalid and create new one related more to the roots of the observed issue (incorrect error message).