[ovs-dev] robot suggestion

Ben Pfaff blp at ovn.org
Tue Jul 31 19:59:10 UTC 2018

Today we've seen some failure reports from the robot because the build
was broken on master.  That will happen occasionally (often, as in this
case, because the robot uses a GCC version different from the
submitter).  Maybe the robot should even report it, probably in a
general email to the list rather than a followup to a particular patch.
But it's not helpful to report those errors as related to a particular

So, maybe the robot should build the upstream branch before it applies
the patch.  If that build fails, it shouldn't bother to report the error
relative to the patch in question (but maybe as a general error to the
list).  It could then apply the patch and report anything from

More information about the dev mailing list