From: Paul Eggleton <paul.eggleton@linux.intel.com>
To: openembedded-core@lists.openembedded.org
Cc: joshua.g.lock@intel.com
Subject: Re: ✗ patchtest: failure for python-git and 3 more upgrades
Date: Thu, 17 Nov 2016 11:03:21 +1300 [thread overview]
Message-ID: <5248602.HLsnDvu2hn@peggleto-mobl.ger.corp.intel.com> (raw)
In-Reply-To: <20161116215522.7692.73016@do.openembedded.org>
On Wed, 16 Nov 2016 21:55:22 Patchwork wrote:
> == Series Details ==
>
> Series: python-git and 3 more upgrades
> Revision: 1
> URL : https://patchwork.openembedded.org/series/3947/
> 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 (series 3947, revision 1) by patchtest resulting in
> the following failures:
>
>
> * Patch [1/4] python*-git: upgrade to 2.1.0
> 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>"
I guess our regex is being a bit strict here.
Cheers,
Paul
--
Paul Eggleton
Intel Open Source Technology Centre
next prev parent reply other threads:[~2016-11-16 22:03 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-16 21:22 [PATCH 0/4] python-git and 3 more upgrades Jose Lamego
2016-11-16 21:22 ` [PATCH 1/4] python*-git: upgrade to 2.1.0 Jose Lamego
2016-11-16 21:22 ` [PATCH 2/4] python*-mako: upgrade to 1.0.6 Jose Lamego
2016-11-16 21:22 ` [PATCH 3/4] python-pexpect: upgrade to 4.2.1 Jose Lamego
2016-11-16 21:22 ` [PATCH 4/4] python-scons*: upgrade to 2.5.1 Jose Lamego
[not found] ` <20161116215522.7692.73016@do.openembedded.org>
2016-11-16 22:03 ` Paul Eggleton [this message]
2016-11-16 22:19 ` ✗ patchtest: failure for python-git and 3 more upgrades Paul Eggleton
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=5248602.HLsnDvu2hn@peggleto-mobl.ger.corp.intel.com \
--to=paul.eggleton@linux.intel.com \
--cc=joshua.g.lock@intel.com \
--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