On Tue, Aug 12, 2014 at 1:51 PM, Michal Čihař <michal@cihar.com> wrote:

Hi

Dne Wed, 6 Aug 2014 20:06:27 +0530
Chirayu Chiripal <chirayu.chiripal@gmail.com> napsal(a):

> It seems like this is having some side effects. Coveralls and Scrutinizer
> are now not properly working (inspecting) when the latest commit in the
> master is the translation commit with [CI Skip] and feature branch is on
> top of that. Or there is something else causing problem with Coveralls and
> Scrutinizer?

They both get coverage data from Travis and they probably just timeout
here.

Coveralls is considering such PR's as first build on master (targeted branch), maybe because coveralls sees that latest commit on master is not having coverage report but those changes are in po files only and he should be interested only in libraries/ directory (see [1]).

Scrutinizer cancels inspection due to some mismatch parent commits error (see [2]). I think scrutinizer behavior is kind of a bug.

[1]: https://coveralls.io/builds/1038671
[2]: https://scrutinizer-ci.com/g/phpmyadmin/phpmyadmin/inspections/963075d0-558f-4a6f-a17e-317021793d13