From: Patchwork <patchwork@patchwork.openembedded.org>
To: Tim Orling <timothy.t.orling@linux.intel.com>
Cc: openembedded-core@lists.openembedded.org
Subject: ✗ patchtest: failure for Add pypi.bbclass; python improvements
Date: Thu, 23 Nov 2017 18:37:55 -0000 [thread overview]
Message-ID: <20171123183755.2786.77539@do.openembedded.org> (raw)
In-Reply-To: <cover.1511458497.git.timothy.t.orling@linux.intel.com>
== Series Details ==
Series: Add pypi.bbclass; python improvements
Revision: 1
URL : https://patchwork.openembedded.org/series/9940/
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 master (currently at 33418ed064)
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
next prev parent reply other threads:[~2017-11-23 18:37 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-23 18:14 [PATCH 00/13] Add pypi.bbclass; python improvements Tim Orling
2017-11-23 18:14 ` [PATCH 01/13] pypi.bbclass: bring in from meta-python Tim Orling
2017-11-23 18:14 ` [PATCH 02/13] python-*-manifest/generator: add runpy; python3-plistlib Tim Orling
2017-11-23 18:14 ` [PATCH 03/13] python-setuptools: upgrade to 36.8.0; use pypi.bbclass; improvements Tim Orling
2017-11-23 18:14 ` [PATCH 04/13] python3-pip: use pypi.bbclass Tim Orling
2017-11-23 18:14 ` [PATCH 05/13] python-nose: " Tim Orling
2017-11-23 18:14 ` [PATCH 06/13] python-six: " Tim Orling
2017-11-23 18:14 ` [PATCH 07/13] python-async: " Tim Orling
2017-11-23 18:14 ` [PATCH 08/13] python-mako: " Tim Orling
2017-11-23 18:14 ` [PATCH 09/13] python-smmap: " Tim Orling
2017-11-23 18:14 ` [PATCH 10/13] python-gitdb: " Tim Orling
2017-11-23 18:14 ` [PATCH 11/13] python-git: " Tim Orling
2017-11-23 18:14 ` [PATCH 12/13] python3-iniparse: " Tim Orling
2017-11-23 18:14 ` [PATCH 13/13] python-scons: upgrade to v3.0.1; " Tim Orling
2017-11-23 18:37 ` Patchwork [this message]
2017-11-23 19:10 ` ✗ patchtest: failure for Add pypi.bbclass; python improvements Tim Orling
2017-11-23 19:31 ` Tim Orling
2017-11-23 19:48 ` Tim Orling
2017-11-23 20:25 ` Leonardo Sandoval
2017-11-23 21:51 ` Tim Orling
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=20171123183755.2786.77539@do.openembedded.org \
--to=patchwork@patchwork.openembedded.org \
--cc=openembedded-core@lists.openembedded.org \
--cc=timothy.t.orling@linux.intel.com \
/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