After I submitted a patch the testbot failed because of an error unrelated to my patch:
=== build (build) === Could not copy the patch to the VM: the "nc -q0 '10.42.42.130' '4242'" command returned 1
Should I resend my patch, or will this be resolved on its own?
Thanks
On Fri, Jun 27, 2014 at 9:34 PM, Joris van der Wel joris@jorisvanderwel.com wrote:
After I submitted a patch the testbot failed because of an error unrelated to my patch:
=== build (build) === Could not copy the patch to the VM: the "nc -q0 '10.42.42.130' '4242'" command returned 1
Should I resend my patch, or will this be resolved on its own?
It's generally a temporary error, so please resend.
If it persists, you can contact François Gouget, who manages the testbot.
On Fri, 27 Jun 2014, Joris van der Wel wrote:
After I submitted a patch the testbot failed because of an error unrelated to my patch:
=== build (build) === Could not copy the patch to the VM: the "nc -q0 '10.42.42.130' '4242'" command returned 1
Should I resend my patch, or will this be resolved on its own?
It is indeed unrelated to the patch. This particular error happens when the TestBot server fails to connect to the agent inside the VM to send it work to do. The next set of TestBot patches should cause it to retry when that happens to make this more robust.
Note that in the meantime if you get a boterror on a job and you have an account you can go to the web site and restart your job (which I did on your job).
Ah I see, thank you. I probably need to register first to restart jobs, I will do that now.
On Sun, Jun 29, 2014 at 12:13 PM, Francois Gouget fgouget@codeweavers.com wrote:
On Fri, 27 Jun 2014, Joris van der Wel wrote:
After I submitted a patch the testbot failed because of an error
unrelated
to my patch:
=== build (build) === Could not copy the patch to the VM: the "nc -q0 '10.42.42.130' '4242'" command returned 1
Should I resend my patch, or will this be resolved on its own?
It is indeed unrelated to the patch. This particular error happens when the TestBot server fails to connect to the agent inside the VM to send it work to do. The next set of TestBot patches should cause it to retry when that happens to make this more robust.
Note that in the meantime if you get a boterror on a job and you have an account you can go to the web site and restart your job (which I did on your job).
-- Francois Gouget fgouget@codeweavers.com
-
Francois Gouget -
Frédéric Delanoy -
Joris van der Wel