From: Michael Halstead <mhalstead@linuxfoundation.org>
To: openembedded-core@lists.openembedded.org
Subject: Re: ✗ patchtest: failure for Shorten file names in sstate-cache
Date: Fri, 11 Jan 2019 11:06:22 -0800 [thread overview]
Message-ID: <09a15c6d-cb5e-7741-d718-bbee3a3e8741@linuxfoundation.org> (raw)
In-Reply-To: <1547226989.885609.1632072120.4FE7D8CF@webmail.messagingengine.com>
On 1/11/19 9:16 AM, Paul Barker wrote:
> On Fri, 11 Jan 2019, at 17:05, Patchwork wrote:
>> == Series Details ==
>>
>> Series: Shorten file names in sstate-cache
>> Revision: 1
>> URL : https://patchwork.openembedded.org/series/15617/
>> State : failure
> That's weird... the patch applies fine onto master here, I've just tested applying it to a clean clone of openembedded-core.
The patchtest server was stuck resetting its working repository to a
local merge. I've repaired the issue on the patchtest server and
submitted
https://lists.yoctoproject.org/pipermail/yocto/2019-January/043790.html
to prevent it from reoccurring.
>> == 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 master (currently at 65c419b8c4)
> Git can't find a commit hash starting with 65c419b8c4 in poky or oe-core.
>
>>
>>
>> If you believe any of these test results are incorrect, please reply to the
>> mailing list (openembedded-core@lists.openembedded.org) raising your concerns.
>> 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://www.openembedded.org/wiki/Commit_Patch_Message_Guidelines
>> Test framework: http://git.yoctoproject.org/cgit/cgit.cgi/patchtest
>> Test suite: http://git.yoctoproject.org/cgit/cgit.cgi/patchtest-oe
>>
>
--
Michael Halstead
Linux Foundation / SysAdmin
prev parent reply other threads:[~2019-01-11 19:06 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-11 16:44 [PATCH 0/1] [RFC/RFT] Shorten file names in sstate-cache Paul Barker
2019-01-11 16:44 ` [PATCH 1/1] [RFC/RFT] sstate: " Paul Barker
2019-01-12 16:20 ` Richard Purdie
2019-01-11 17:05 ` ✗ patchtest: failure for " Patchwork
2019-01-11 17:16 ` Paul Barker
2019-01-11 19:06 ` Michael Halstead [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=09a15c6d-cb5e-7741-d718-bbee3a3e8741@linuxfoundation.org \
--to=mhalstead@linuxfoundation.org \
--cc=openembedded-core@lists.openembedded.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox