I've marked failing tests as expected failture.

Tim


On Thu, Nov 15, 2012 at 4:03 PM, rldhont <[email protected]> wrote:

>  Hi,
>
> I've corrected the PyQgsRectengle because it was my fault.
>
> The others isn't mine :
> * 
> PyQgsVectorFileWriter<http://jenkins.linfiniti.com/job/QGIS/lastBuild/testReport/%28root%29/TestSuite/PyQgsVectorFileWriter/>
> * 
> PyQgsComposerMap<http://jenkins.linfiniti.com/job/QGIS/lastBuild/testReport/%28root%29/TestSuite/PyQgsComposerMap/>
>
> René-Luc D'Hont
>
> Le 15/11/2012 12:58, Etienne Tourigny a écrit :
>
> Hi - can the person responsible for breaking the jenkins builds please fix it?
>
> Thanks
> Etienne
>
> ---------- Forwarded message ----------
> From: Linfiniti Jenkins <[email protected]> <[email protected]>
> Date: Wed, Nov 14, 2012 at 9:23 PM
> Subject: Jenkins build is still unstable: QGIS #831
> To: [email protected], [email protected]
>
>
> See <http://jenkins.linfiniti.com/job/QGIS/changes> 
> <http://jenkins.linfiniti.com/job/QGIS/changes>
> _______________________________________________
> Qgis-developer mailing 
> [email protected]http://lists.osgeo.org/mailman/listinfo/qgis-developer
>
>
>
> _______________________________________________
> Qgis-developer mailing list
> [email protected]
> http://lists.osgeo.org/mailman/listinfo/qgis-developer
>
>


-- 
Tim Sutton - QGIS Project Steering Committee Member (Release  Manager)
==============================================
Please do not email me off-list with technical
support questions. Using the lists will gain
more exposure for your issues and the knowledge
surrounding your issue will be shared with all.

Visit http://linfiniti.com to find out about:
 * QGIS programming and support services
 * Mapserver and PostGIS based hosting plans
 * FOSS Consulting Services
Skype: timlinux
Irc: timlinux on #qgis at freenode.net
==============================================
_______________________________________________
Qgis-developer mailing list
[email protected]
http://lists.osgeo.org/mailman/listinfo/qgis-developer

Reply via email to