Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Patchwork <patchwork@patchwork.openembedded.org>
To: Randy MacLeod <randy.macleod@windriver.com>
Cc: openembedded-core@lists.openembedded.org
Subject: ✗ patchtest: failure for "util-linux: add setpriv utilit..." and 3 more (rev2)
Date: Fri, 14 Jun 2019 17:01:08 -0000	[thread overview]
Message-ID: <20190614170108.2331.27756@do> (raw)
In-Reply-To: <20190614160229.6144-1-Randy.MacLeod@windriver.com>

== Series Details ==

Series: "util-linux: add setpriv utilit..." and 3 more (rev2)
Revision: 2
URL   : https://patchwork.openembedded.org/series/18163/
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 ca737408bb)



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



  parent reply	other threads:[~2019-06-14 17:01 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-06-14 16:02 [PATCH 1/4] util-linux: add setpriv utility Randy MacLeod
2019-06-14 16:02 ` [PATCH 2/4] libcap-ng: split into libcap-ng/libcap-ng-python Randy MacLeod
2019-06-14 16:23   ` Richard Purdie
2019-06-14 16:45     ` [PATCH 1/4] util-linux: add setpriv utility Randy MacLeod
2019-06-14 16:45       ` [PATCH 2/4] libcap-ng: split into libcap-ng/libcap-ng-python Randy MacLeod
2019-06-14 16:45       ` [PATCH 3/4] ptest-runner: enable child procs as session leader Randy MacLeod
2019-06-14 16:45       ` [PATCH 4/4] bash: use setpriv, sed.sed to run ptests Randy MacLeod
2019-06-15 15:16       ` [PATCH 1/4] util-linux: add setpriv utility Richard Purdie
2019-06-16 15:49         ` Randy MacLeod
2019-06-14 16:02 ` [PATCH 3/4] ptest-runner: enable child procs as session leader Randy MacLeod
2019-06-14 16:02 ` [PATCH 4/4] bash: use setpriv, sed.sed to run ptests Randy MacLeod
2019-06-14 17:01 ` Patchwork [this message]
2019-06-14 17:01 ` ✗ patchtest: failure for "util-linux: add setpriv utilit..." and 3 more (rev4) Patchwork
2019-06-14 17:01 ` ✗ patchtest: failure for "util-linux: add setpriv utilit..." and 3 more (rev5) Patchwork
2019-06-14 17:13   ` Randy MacLeod
2019-06-17  3:59     ` Changqing Li

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=20190614170108.2331.27756@do \
    --to=patchwork@patchwork.openembedded.org \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=randy.macleod@windriver.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