From: Tom Rini <trini@konsulko.com>
To: Martin Jansa <martin.jansa@gmail.com>
Cc: Patrick Ohly <patrick.ohly@intel.com>,
openembedded-devel@lists.openembedded.org,
Michael Halstead <michael@yoctoproject.org>
Subject: Re: meta-openembedded patchwork git hook
Date: Fri, 2 Dec 2016 07:29:23 -0500 [thread overview]
Message-ID: <20161202122923.GI2546@bill-the-cat> (raw)
In-Reply-To: <20161202083009.GB3721@jama>
On Fri, Dec 02, 2016 at 09:30:09AM +0100, Martin Jansa wrote:
> On Wed, Nov 30, 2016 at 12:41:20PM -0600, Jose Lamego wrote:
> >
> >
> > On 11/29/2016 07:50 PM, Khem Raj wrote:
> > >
> > >> On Nov 29, 2016, at 2:34 PM, Jose Lamego <jose.a.lamego@linux.intel.com> wrote:
> > >>
> > >>
> > >>
> > >> On 11/29/2016 02:43 PM, Tom Rini wrote:
> > >>> On Wed, Nov 30, 2016 at 06:52:46AM +1300, Paul Eggleton wrote:
> > >>>
> > >>>> Hi folks,
> > >>>>
> > >>>> Martin just brought to my attention that the git hook for the
> > >>>> meta-openembedded repository that's supposed to update patchwork still isn't
> > >>>> working and hasn't done so for a very long time. I thought we'd fixed this so
> > >>>> that merged patches get marked as "Accepted", but at least for meta-
> > >>>> openembedded it seems like that's not the case.
> > >>>>
> > >>>> Jose / Michael - can you look into this if you haven't already? Please let me
> > >>>> know if you need any help.
> > >>
> > >> The git hook was configured to update OE-core only, Michael will help us
> > >> to include meta-openembedded.
> > >>
> > >
> > > There are more repos using patchwork beyond OE-core and meta-opemebedded
> > > please enable it for all of them as well.
> > >
> >
> > Now all of the projects are enabled to receive automatic updates from
> > the git-hook (Thanks Michael). Please let me know if any undesired
> > behavior is detected.
>
> Still doesn't mark anything as accepted:
>
> OE @ ~/meta-openembedded $ git push origin master
> Counting objects: 293, done.
> Delta compression using up to 8 threads.
> Compressing objects: 100% (257/257), done.
> Writing objects: 100% (293/293), 48.83 KiB | 0 bytes/s, done.
> Total 293 (delta 179), reused 68 (delta 18)
> remote: E: failed to find patch for rev efd3696e70a6603f1a45faa4a172433514f0a487.
> remote: E: failed to find patch for rev 8c720146b718aae3bc194621f3e095cf11ecb2ed.
> remote: E: failed to find patch for rev fc2fc9097b2fa437d4af0338e418692b4dd6c989.
> remote: E: failed to find patch for rev 533826b7652a2cf86ca7b665c25b98c89afc266e.
> remote: E: failed to find patch for rev 6afb85d29286aaa4cdd892460f6adf68912917a5.
> remote: E: failed to find patch for rev a7f3ec87f957ff35b8a853cd0e04c6b18bac0ece.
> remote: E: failed to find patch for rev 877e52fd75c7d3b88add94691df3beb5e0c54529.
> remote: E: failed to find patch for rev 2f6e45baba961629bfe023599144be6cfcd45728.
> remote: E: failed to find patch for rev 86fed80d80bc33f0a3cdbf719c00ee5f05ed4d19.
> remote: E: failed to find patch for rev 41d7bac5d50091cab835eac0a5eaa6c431fb2023.
> remote: E: failed to find patch for rev a85e12928131fce057f777daa76a7f0c75cffa14.
> remote: E: failed to find patch for rev 45837e6c567b1b9ff9d152a7e2a752488d313455.
> remote: E: failed to find patch for rev 119e75e48dbf0539b4e440417901458ffff79b38.
> remote: E: failed to find patch for rev a4251575f41fa5aafe5072e562497b05c11b6702.
> remote: E: failed to find patch for rev b6ea2c0bacb21b83bae3605ef4da080de0cad15e.
> remote: E: failed to find patch for rev 4580e5ae201b320ed407eae26f58655b8768b387.
> remote: E: failed to find patch for rev c476219e845934f767927e81fe60dbaa157df9ee.
> remote: E: failed to find patch for rev 0288b204f3c12af1561218fa0cfcdfb9a5508b47.
> remote: E: failed to find patch for rev 5596b52d64c30d8e66ec6e379cf69a9fc9407fb1.
> remote: E: failed to find patch for rev 24e51a6a106bc10a8838b23e4bf9ea6304314bca.
> remote: E: failed to find patch for rev aac6bf8bf911c3f14ff9dce08f0f011838f5a426.
> remote: I: 0 patch(es) updated to state Accepted.
> remote: Sending notification emails to: openembedded-commits@lists.openembedded.org.
> To git.openembedded.org:meta-openembedded
> 761639b..aac6bf8 master -> master
I don't know how far apart the freedesktop.org one is from ozlabs but
when I was seeing that problem locally as part of what I was working on
it was because of some missing host deps (that are now not required).
FWIW you can pretty easily turn the hook into a script to run manually
and sh -x it to see _why_ it's not hashing out those patches.
--
Tom
next prev parent reply other threads:[~2016-12-02 12:29 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-29 17:52 meta-openembedded patchwork git hook Paul Eggleton
2016-11-29 20:43 ` Tom Rini
2016-11-29 22:34 ` Jose Lamego
2016-11-30 1:50 ` Khem Raj
2016-11-30 18:41 ` Jose Lamego
2016-12-02 8:30 ` Martin Jansa
2016-12-02 12:29 ` Tom Rini [this message]
2016-12-02 15:45 ` Jose Lamego
2016-12-09 11:09 ` Martin Jansa
2016-12-14 20:27 ` Jose Lamego
2016-12-14 21:02 ` Jose Lamego
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=20161202122923.GI2546@bill-the-cat \
--to=trini@konsulko.com \
--cc=martin.jansa@gmail.com \
--cc=michael@yoctoproject.org \
--cc=openembedded-devel@lists.openembedded.org \
--cc=patrick.ohly@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.