[oe] meta-openembedded patchwork git hook

Fri Dec 2 08:30:09 UTC 2016

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 at 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 at lists.openembedded.org.
To git.openembedded.org:meta-openembedded
   761639b..aac6bf8  master -> master

> >>>
> >>> Since I brought this up on IRC, I wanted to chime in here.  First, if
> >>> you want to use top-of-tree patchwork you'll also want to grab
> >>> https://patchwork.ozlabs.org/bundle/stephenfin/post-receive%20fixes/
> >>
> >>
> >> Hi Tom, nice meeting you. OE-Patchwork is using a fork in [1] from
> >> freedesktop.org's patchwork at [2]. I will look at the hook fixes you
> >> mentioned at the first chance, thanks for the tip.
> >>
> >>> (and fwiw, I also have been setting the DJANGO part to 'dev' rather than
> >>> production for my use-case).  Second, I think part of the problem is
> >>> that there are just some cases where the hashing fails, which for me is
> >>> around 10% of the time.  Depending on how much one uses bundles and
> >>> tracks what ends up being committed this may or may not be a problem.
> >>> And I'm sure upstream patchwork would appreciate any changes to improve
> >>> hashing success :)
> >>>
> >>
> >> Regards
> >> Jose
> >>
> >> -- 
> >> Jose Lamego | OTC Embedded Platforms & Tools | GDC
> >>
> >> -- 
> >> _______________________________________________
> >> Openembedded-devel mailing list
> >> Openembedded-devel at lists.openembedded.org
> >> http://lists.openembedded.org/mailman/listinfo/openembedded-devel
> > 
> 
> -- 
> Jose Lamego | OTC Embedded Platforms & Tools | GDC
> 

> -- 
> _______________________________________________
> Openembedded-devel mailing list
> Openembedded-devel at lists.openembedded.org
> http://lists.openembedded.org/mailman/listinfo/openembedded-devel

-- 
Martin 'JaMa' Jansa     jabber: Martin.Jansa at gmail.com
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 195 bytes
Desc: Digital signature
URL: <http://lists.openembedded.org/pipermail/openembedded-devel/attachments/20161202/79208913/attachment-0002.sig>