1 Jun
2015
1 Jun
'15
9:31 a.m.
Hi
Dne Sat, 30 May 2015 07:43:54 -0400 Isaac Bennetch bennetch@gmail.com napsal(a):
Hi, recently I've been seeing a lot of Scrutinizer failures such as[0].
Does anyone have any idea about this? I couldn't really find any information about this particular message online.
0 - https://scrutinizer-ci.com/g/phpmyadmin/phpmyadmin/inspections/1a2ea9a8-fcf9...
For this the Travis build failed and thus did not send coverage information. I don't see why as after_script on Travis should be executed even in case of build failure...
Anyway I think it makes sense to remove coverage from Scrutinizer, it makes the setup just more complex with no big benefits.
--
Michal Čihař | http://cihar.com | http://phpmyadmin.net