Re: Please stop committing on a broken build! ([Testbot] Plone 5.0 - Python 2.7 - Build # 1925 - Regression! - 6 failure(s))

Am 14.03.2014 04:10, schrieb Nathan Van Gheem:
> If anyone else can take a look, I'm pretty certain all remaining test
> failures have nothing to do with the CSRF merge.
> 
> http://jenkins.plone.org/job/plone-5.0-python-2.7/lastCompletedBuild/testReport/

The failing robot test seems to be CSRF related (see screenshot):

http://jenkins.plone.org/job/plone-5.0-python-2.7/2006/robot/report/robot_log.html#s1-s6

In any case, the person who broke the build is responsible to make it
green again. :)

This is why it is so important not to commit on a broken build. Every
commit on a broken build makes it harder to figure out which commit
broke which test.

Cheers,
Timo

------------------------------------------------------------------------------
Learn Graph Databases - Download FREE O'Reilly Book
"Graph Databases" is the definitive new guide to graph databases and their
applications. Written by three acclaimed leaders in the field,
this first edition is now available. Download your free book today!
http://p.sf.net/sfu/13534_NeoTech