[OE-core] ✗ patchtest: failure for openssl: Upgrade from 1.0.2k to 1.0.2n

[robert_joslyn at selinc.com]

Patchwork <patchwork at patchwork.openembedded.org> wrote on 02/13/2018 
12:04:30 PM:

> == Series Details ==
> 
> Series: openssl: Upgrade from 1.0.2k to 1.0.2n
> Revision: 1
> URL   : https://urldefense.proofpoint.com/v2/url?
> 
u=https-3A__patchwork.openembedded.org_series_10958_&d=DwICaQ&c=zVFQZQ67ypsA9mYKSCqWmQHiVkCCaN-
> 
Gb60_N6TVnLk&r=jKjb9x138uKtDnkEJ0l_Ks7NxaK4YpEWM1o0MkNOIx0&m=e7jg3aTWVYdmFaC21AlrNvOx1_qajpaOj2OHjsTZ654&s=9QNMi3VNaubjQf3y9jBZmv5TBjaNNWdE9v75bBdAzR8&e=
> State : failure
> 
> == Summary ==
> 
> 
> Thank you for submitting this patch series to OpenEmbedded Core. This is
> an automated response. Several tests have been executed on the proposed
> series by patchtest resulting in the following failures:
> 
> 
> 
> * Issue             Series does not apply on top of target branch 
> [test_series_merge_on_head] 
>   Suggested fix    Rebase your series on top of targeted branch
>   Targeted branch  pyro (currently at 2c61e60cc5)
> 
> 
> 
> If you believe any of these test results are incorrect, please reply to 
the
> mailing list (openembedded-core at lists.openembedded.org) raising 
yourconcerns.
> Otherwise we would appreciate you correcting the issues and submitting a 
new
> version of the patchset if applicable. Please ensure you add/increment 
the
> version number when sending the new version (i.e. [PATCH] -> [PATCH v2] 
->
> [PATCH v3] -> ...).
> 
> ---
> Guidelines:     https://urldefense.proofpoint.com/v2/url?
> 
u=https-3A__www.openembedded.org_wiki_Commit-5FPatch-5FMessage-5FGuidelines&d=DwICaQ&c=zVFQZQ67ypsA9mYKSCqWmQHiVkCCaN-
> 
Gb60_N6TVnLk&r=jKjb9x138uKtDnkEJ0l_Ks7NxaK4YpEWM1o0MkNOIx0&m=e7jg3aTWVYdmFaC21AlrNvOx1_qajpaOj2OHjsTZ654&s=-
> jCJpJdJRPInvZ3mPBypauSGq16-k4Z4vRCcXMQ9F70&e=
> Test framework: https://urldefense.proofpoint.com/v2/url?
> 
u=http-3A__git.yoctoproject.org_cgit_cgit.cgi_patchtest&d=DwICaQ&c=zVFQZQ67ypsA9mYKSCqWmQHiVkCCaN-
> 
Gb60_N6TVnLk&r=jKjb9x138uKtDnkEJ0l_Ks7NxaK4YpEWM1o0MkNOIx0&m=e7jg3aTWVYdmFaC21AlrNvOx1_qajpaOj2OHjsTZ654&s=QrASQqaT3MEEj1zQgTDQ5iQO93aJ2zooq57BdIgB1cU&e=
> Test suite:     https://urldefense.proofpoint.com/v2/url?
> 
u=http-3A__git.yoctoproject.org_cgit_cgit.cgi_patchtest-2Doe&d=DwICaQ&c=zVFQZQ67ypsA9mYKSCqWmQHiVkCCaN-
> 
Gb60_N6TVnLk&r=jKjb9x138uKtDnkEJ0l_Ks7NxaK4YpEWM1o0MkNOIx0&m=e7jg3aTWVYdmFaC21AlrNvOx1_qajpaOj2OHjsTZ654&s=fqNrlIHFwuTo2gHbIXgrogfoHFxaSl1EvqECV2p4Y-
> w&e=
> 

Unfortunately, this is caused by my company's email filter replacing URLs 
with redirects from proofpoint (which you can see more of above). It's an 
attempt at preventing us from clicking on malicious URLs, but I had no 
idea it did the replacement on outgoing email as well as incoming... I'll 
try to send the patch from a personal email account later.

Thanks,
Robert