Ashish Varma <ashishvarma....@gmail.com> writes: > Hi Aaron, > > My patch is already committed by Ben. Not sure what is wrong here.
Thanks for the heads up. This happens - usually if the patch is committed before the bot has run against it. I have it on my list of TODOs, so as soon as my next 'work on the bot' time comes, I'll fix it. > Is there something that I need to do now? (or should have done correctly) Without looking too deeply, most likely a false positive. Feel free to not worry about it :) I'll ping if it's a real issue somewhere. > Thanks, > Ashish > VMware OVS team > > On Mon, Aug 6, 2018 at 7:15 PM, 0-day Robot <ro...@bytheb.org> wrote: > > Bleep bloop. Greetings Ashish Varma, I am a robot and I have tried out your > patch. > Thanks for your contribution. > > I encountered some error that I wasn't expecting. See the details below. > > git-am: > Failed to merge in the changes. > Patch failed at 0001 tests: Test for ovs-ofctl snoop command > The copy of the patch that failed is found in: > > /var/lib/jenkins/jobs/upstream_build_from_pw/workspace/.git/rebase-apply/patch > When you have resolved this problem, run "git am --resolved". > If you prefer to skip this patch, run "git am --skip" instead. > To restore the original branch and stop patching, run "git am --abort". > > Please check this out. If you feel there has been an error, please email > acon...@bytheb.org > > Thanks, > 0-day Robot _______________________________________________ dev mailing list d...@openvswitch.org https://mail.openvswitch.org/mailman/listinfo/ovs-dev
