mr.roboto and Jenkins false positives

It looks like there was some kind of temporary condition on whatever
build slave is used for Plone 4.3 / Python 2.6 that caused these
issues:

  http://jenkins.plone.org/job/plone-4.3-python-2.6/2109/testReport/

These were unrelated to changes preceding the build, and were also
evident in the previous
http://jenkins.plone.org/job/plone-4.3-python-2.6/2108/

These were also cleared in the next build --
http://jenkins.plone.org/job/plone-4.3-python-2.6/2110/

This brings two questions:

1. What should be the protocol for handling the false-positive
automated comments mister-roboto places on github commits (e.g. [1])?
Should they merely be responded to, or deleted?

2. Is there any way mr.roboto can be modified to omit blame for a
broken build if the previous build (prior to a commit) was broken for
the same reasons?

Sean

[1] https://github.com/plone/plone.supermodel/commit/f16f480b6062a44bda6f729f03de4555c65c82b0#commitcomment-6508044

------------------------------------------------------------------------------
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/NeoTech