Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Robert Yang <liezhi.yang@windriver.com>
To: <openembedded-core@lists.openembedded.org>
Subject: Re: ✗ patchtest: failure for valgrind/bluez5/perl: Fix race issues when parallel build
Date: Fri, 28 Dec 2018 17:45:54 +0800	[thread overview]
Message-ID: <f326097b-655a-e37e-107c-e13a467ca221@windriver.com> (raw)
In-Reply-To: <20181228093314.2331.95571@do>



On 12/28/18 5:33 PM, Patchwork wrote:
> == Series Details ==
> 
> Series: valgrind/bluez5/perl: Fix race issues when parallel build
> Revision: 1
> URL   : https://patchwork.openembedded.org/series/15481/
> 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 65c419b8c4)

Seems that something is wrong with patchtest, the current master branch should be:

commit caa776bdcf8ea34c857f45970370bf771075f4bc
Author: Kai Kang <kai.kang@windriver.com>
Date:   Tue Dec 25 04:39:43 2018 -0500

     testimage.bbclass: remove boot parameter systemd.log_target


But patchtest says it is 65c419b8c4, I can't find it in my repo.

// Robert

> 
> 
> 
> 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
> 
> 


      reply	other threads:[~2018-12-28  9:41 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-12-28  9:01 [PATCH 0/3] valgrind/bluez5/perl: Fix race issues when parallel build Robert Yang
2018-12-28  9:01 ` [PATCH 1/3] valgrind: Fix a race issue for libcoregrind.a Robert Yang
2018-12-28  9:01 ` [PATCH 2/3] bluez5: Fix a race issue for tools Robert Yang
2018-12-28  9:01 ` [PATCH 3/3] perl: Fix race issue for cpan/Pod-Simple Robert Yang
2018-12-28  9:33 ` ✗ patchtest: failure for valgrind/bluez5/perl: Fix race issues when parallel build Patchwork
2018-12-28  9:45   ` Robert Yang [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=f326097b-655a-e37e-107c-e13a467ca221@windriver.com \
    --to=liezhi.yang@windriver.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