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 patch.
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 checkpatch. _______________________________________________ dev mailing list d...@openvswitch.org https://mail.openvswitch.org/mailman/listinfo/ovs-dev
