Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Leonardo Sandoval <leonardo.sandoval.gonzalez@linux.intel.com>
To: openembedded-core@lists.openembedded.org
Cc: Patchwork <patchwork@patchwork.openembedded.org>
Subject: Re: ✗ patchtest: failure for Restructure python2 and python3 packaging system (rev2)
Date: Thu, 19 Oct 2017 15:34:43 -0500	[thread overview]
Message-ID: <20171019153443.568ef8ada34a79e099b3e76d@linux.intel.com> (raw)
In-Reply-To: <20171019201458.2783.51659@do.openembedded.org>

On Thu, 19 Oct 2017 20:14:58 -0000
Patchwork <patchwork@patchwork.openembedded.org> wrote:

> == Series Details ==
> 
> Series: Restructure python2 and python3 packaging system (rev2)
> Revision: 2
> URL   : https://patchwork.openembedded.org/series/8314/
> 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 cannot be parsed correctly due to malformed diff lines [test_mbox_format] 
>   Suggested fix    Create the series again using git-format-patch and ensure it can be applied using git am
>   Diff line         diff --git a/meta/recipes-devtools/python/python-native_2.7.13.bb b/meta/recipes-devtools/python/python-native_2.7.13.bb

Alex, please ignore this error. This is actually not a false-positive, is the long line patch issue that git-send-email truncates (thus malformat the patch itself) and it is what you indirectly trying to solve with your new approach. Just Ross needs to take it directly from poky-contrib.

Leo


> 
> 
> * 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 3b413a8057)
> 
> 
> 
> 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
> 
> -- 
> _______________________________________________
> Openembedded-core mailing list
> Openembedded-core@lists.openembedded.org
> http://lists.openembedded.org/mailman/listinfo/openembedded-core


-- 
Leonardo Sandoval <leonardo.sandoval.gonzalez@linux.intel.com>


      reply	other threads:[~2017-10-19 20:24 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-10-18 21:07 [PATCH 0/4] Restructure python2 and python3 packaging system Alejandro Hernandez
2017-10-18 21:07 ` [PATCH 1/4] python: Restructure python packaging and replace it with autopackaging Alejandro Hernandez
2017-11-24 16:57   ` Burton, Ross
2017-11-24 23:49     ` Alejandro Hernandez
2017-11-24 17:06   ` Burton, Ross
2017-11-24 23:51     ` Alejandro Hernandez
2017-11-25  5:04       ` Tim Orling
2017-11-25 23:45         ` Alejandro Hernandez
2017-11-26  2:08           ` Alejandro Hernandez
2017-10-18 21:07 ` [PATCH 2/4] python3: Restructure python3 " Alejandro Hernandez
2017-11-24 17:05   ` Burton, Ross
2017-11-24 23:50     ` Alejandro Hernandez
2017-10-18 21:07 ` [PATCH 3/4] python3: fix RDEPENDS on several recipes, due to non-existent python3 packages Alejandro Hernandez
2017-10-18 21:07 ` [PATCH 4/4] hwlatdetect: fix RDEPENDS to avoid QA failures Alejandro Hernandez
2017-10-19 20:14 ` ✗ patchtest: failure for Restructure python2 and python3 packaging system (rev2) Patchwork
2017-10-19 20:34   ` Leonardo Sandoval [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=20171019153443.568ef8ada34a79e099b3e76d@linux.intel.com \
    --to=leonardo.sandoval.gonzalez@linux.intel.com \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=patchwork@patchwork.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