From: Denys Dmytriyenko <denis@denix.org>
To: openembedded-core@lists.openembedded.org
Subject: Re: ✗ patchtest: failure for bash 4.3.30 -> 4.4
Date: Fri, 20 Jan 2017 01:54:45 -0500 [thread overview]
Message-ID: <20170120065445.GZ15833@denix.org> (raw)
In-Reply-To: <20170119032342.23274.93140@do.openembedded.org>
On Thu, Jan 19, 2017 at 03:23:42AM -0000, Patchwork wrote:
> == Series Details ==
>
> Series: bash 4.3.30 -> 4.4
> Revision: 1
> URL : https://patchwork.openembedded.org/series/4836/
> 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:
Wow, nice report from Patchwork!
May I suggest adding corresponding Wiki links to "Suggested fix" field? E.g.
http://openembedded.org/wiki/Commit_Patch_Message_Guidelines
> * Patch bash 4.3.30 -> 4.4
> Issue Shortlog does not follow expected format [test_shortlog_format]
> Suggested fix Commit shortlog (first line of commit message) should follow the format "<target>: <summary>"
>
> * Issue Added patch file is missing Upstream-Status in the header [test_upstream_status_presence]
> Suggested fix Add Upstream-Status: <status> to the header of meta/recipes-extended/bash/bash/0001-patch-to-obtain-pkgconfig-sanity.patch (possible values: Pending, Submitted, Accepted, Backport, Denied, Inappropriate)
>
> * 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 a7cb408dd7)
>
>
>
> 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] -> ...).
>
> ---
> Test framework: http://git.yoctoproject.org/cgit/cgit.cgi/patchtest
> Test suite: http://git.yoctoproject.org/cgit/cgit.cgi/patchtest-oe
>
> --
> _______________________________________________
> Openembedded-core mailing list
> Openembedded-core@lists.openembedded.org
> http://lists.openembedded.org/mailman/listinfo/openembedded-core
next prev parent reply other threads:[~2017-01-20 6:54 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-19 2:52 [PATCH] bash 4.3.30 -> 4.4 Zheng Ruoqin
2017-01-19 3:23 ` ✗ patchtest: failure for " Patchwork
2017-01-20 6:54 ` Denys Dmytriyenko [this message]
2017-01-19 12:31 ` [PATCH] " Burton, Ross
2017-01-20 3:59 ` Zheng, Ruoqin
-- strict thread matches above, loose matches on Subject: below --
2017-01-23 2:38 [PATCH V2] bash: " Zheng Ruoqin
2017-01-23 2:53 ` ✗ patchtest: failure for " Patchwork
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=20170120065445.GZ15833@denix.org \
--to=denis@denix.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