Re: oecommit ml

[Martin Jansa <martin.jansa@gmail.com>]

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

On Mon, Nov 16, 2015 at 09:52:35PM +0100, Martin Jansa wrote:
> On Fri, Nov 13, 2015 at 02:03:07PM -0800, Michael Halstead wrote:
> > 
> > On 11/13/2015 01:50 PM, Khem Raj wrote:
> > >> On Nov 13, 2015, at 1:45 PM, Michael Halstead <michael@yoctoproject.org> wrote:
> > >>
> > >> Bitbake is disabled with the note:
> > >>
> > >> # interferes with patchwork sice it sends emails after the patches are
> > >> closed
> > >> # we could re-enable it if the mails went to someother ml may be
> > >> bitbake-commits
> > >>
> > >> This happens because it was mailing bitbake-devel@lists.openembedded.org
> > >>
> > >> We can mail openembedded-commits@lists.openembedded.org which would work
> > >> fine. Or I can create a bitbake-commits@lists.openembedded.org. Which is
> > >> better?
> > > I think mailing to openembedded-commits@lists.openembedded.org might be ok. with [bitbake] in message subject for filtering help.
> > 
> > I've altered the script to include [reponame] in the subject of all
> > e-mails and enabled for bitbake.
> 
> Seems to be causing some new warnings when pushing to the repo:
> 
> OE @ ~/meta-openembedded $ git push origin master
> Counting objects: 204, done.
> Delta compression using up to 8 threads.
> Compressing objects: 100% (193/193), done.
> Writing objects: 100% (204/204), 38.00 KiB | 0 bytes/s, done.
> Total 204 (delta 147), reused 0 (delta 0)
> remote: Scalar found where operator expected at /home/git/git-notify line 140, near "$subject"
> remote:         (Missing semicolon on previous line?)
> remote: Global symbol "@openembedded" requires explicit package name at /home/git/git-notify line 60.
> remote: syntax error at /home/git/git-notify line 140, near "$subject "
> remote: Execution of /home/git/git-notify aborted due to compilation errors.
> remote: E: failed to find patch for rev 7df2b574f1c4ad445b1656666878cb2ceffca2e0.
> remote: E: failed to find patch for rev ea5bc66444a1e9b5fb330d8a6d42dc95e4bc9500.
> remote: E: failed to find patch for rev 1ec69e6b3891c01734e57a908a2a675128f126eb.
> remote: E: failed to find patch for rev a1d3dce036f80867d30993742d55abb17c6bc057.
> ...

and it got stuck (maybe 5 mins sofar) after few more "failed to find patch" messages
...

remote: E: failed to find patch for rev 035374299937302bf15d14a4175b15b6bfcb4cfa.
remote: E: failed to find patch for rev 1d35641ab6da3d381af511ee406e2c1d3eaf636b.
remote: E: failed to find patch for rev a497a46ef629788b77b9b0b23d1618a673d08709.
remote: E: failed to find patch for rev 45a6d2537dac421803fcefe8d2e4899a3fc39e43.
remote: E: failed to find patch for rev f558b195c3b880069dd51a29be4aefd50eaec329.
remote: E: failed to find patch for rev 9ba2e55b0f1f7f8326523c1b418997eb38276f2e.
remote: E: failed to find patch for rev 2200a08dc60486017e59c1950fd3138f79e21030.
remote: E: failed to find patch for rev 9a381e8c4d4f3ce074a1f934e2f6dfc3172efe8e.
remote: E: failed to find patch for rev b145a503839840c0ea43cdab5dcab3a9c6ca7f7b.
remote: E: failed to find patch for rev 1f96c7d8ce6e18a2c87a180a94afc179f407c5ab.
remote: E: failed to find patch for rev 72c82837f614fa5d1d3677db71243fe74bf5a496.
remote: E: failed to find patch for rev f6a3cd4dcd1654a953c505ff779090717314871a.
remote: E: failed to find patch for rev c3d88ca50de5657b9b6c05ed19ac1702c95b3c9c.
remote: E: failed to find patch for rev e51b35fdbd6bd64b4e8e1b67d76c7e90d7b9f6d6.
remote: E: failed to find patch for rev 99d96c933f3fa4f4d7ef5727154b0d8ef6533caa.
remote: E: failed to find patch for rev 437f22e9aa4977a95cfab5f0dd8359410281bcfd.
remote: E: failed to find patch for rev 926eeea7c613721cf30105f7c6d7ecc531ccc736.
remote: E: failed to find patch for rev 1b2a08a9f1a27426662c703d0cea8091aa77ab11.
remote: E: failed to find patch for rev d70899b30f7acea4eba3870bbe14a37a44ea7528.
remote: E: failed to find patch for rev e528f2e16033dc011e5c8ac2d843af6c78808077.
remote: E: failed to find patch for rev 907037a7f989c5bfe699109cef7aa456995d2fea.
remote: E: failed to find patch for rev df552bed28c6ed983a94ebad4185bc9b2d04486f.

"failed to find patch for rev" isn't new, patchwork hook never finds anything and
I have to mark the reviews manually, but it shouldn't be stuck (maybe trying to
send e-mails?).

Also strange that I was pushing 33 changes and only 26 messages were shown (sofar).

Regards,

-- 
Martin 'JaMa' Jansa     jabber: Martin.Jansa@gmail.com

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 188 bytes --]