public inbox for openembedded-core@lists.openembedded.org
 help / color / mirror / Atom feed
From: "Alejandro Hernandez" <alhe@linux.microsoft.com>
To: openembedded-core@lists.openembedded.org,
	Alejandro Enedino Hernandez Samaniego <alejandro@enedino.org>
Subject: Re: [OE-core] ✗ patchtest: failure for newlib: Upgrade to latest yearly release 3.3.0
Date: Mon, 4 May 2020 14:12:09 -0700	[thread overview]
Message-ID: <f242e19e-c275-f0b0-b7f1-63f7c056c611@linux.microsoft.com> (raw)
In-Reply-To: <20200504210236.2273.59294@do>

[-- Attachment #1: Type: text/plain, Size: 1498 bytes --]

My bad, this meant to be a patch for Dunfell since its been merged on 
master already, please disregard this failure


Alejandro

On 5/4/20 2:02 PM, Patchwork wrote:
> == Series Details ==
>
> Series: newlib: Upgrade to latest yearly release 3.3.0
> Revision: 1
> URL   : https://patchwork.openembedded.org/series/23943/
> 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 26eb22191f)
>
>
>
> 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
>
>
> 

[-- Attachment #2: Type: text/html, Size: 2430 bytes --]

  reply	other threads:[~2020-05-04 21:12 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-05-04 20:57 [PATCH] newlib: Upgrade to latest yearly release 3.3.0 Alejandro Hernandez
2020-05-04 21:02 ` ✗ patchtest: failure for " Patchwork
2020-05-04 21:12   ` Alejandro Hernandez [this message]
2020-05-05  1:17     ` [OE-core] " Steve Sakoman
2020-05-05  1:21       ` Alejandro Hernandez

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=f242e19e-c275-f0b0-b7f1-63f7c056c611@linux.microsoft.com \
    --to=alhe@linux.microsoft.com \
    --cc=alejandro@enedino.org \
    --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