From: Philip Balister <philip@balister.org>
To: openembedded-devel@lists.openembedded.org
Subject: Re: patch queue: latest patches not listed in Patchwork
Date: Fri, 01 Apr 2011 10:05:36 -0400 [thread overview]
Message-ID: <4D95DBB0.7070606@balister.org> (raw)
In-Reply-To: <in4lkv$326$2@dough.gmane.org>
On 04/01/2011 09:57 AM, Koen Kooi wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> On 01-04-11 15:12, Philip Balister wrote:
>> On 04/01/2011 03:26 AM, Paul Menzel wrote:
>>> Dear OE folks,
>>>
>>>
>>> I do not see the latest patches in our patch queue [1]. Is that a known
>>> problem?
>>
>> The process that processes the patchwork emails started taking 100% cpu
>> yesterday. The admin team had to turn it off so other functions on the
>> machine would run.
>
> Can we have an announcement about that on oe-devel in the future? It
> would have saved me a lot of F5'ing in my browser :)
>
Sorry, things are hectic for me and Tom atm.
>
>> We need someone who understands enough about patchwork and/or the script
>> to figure out why it is stuck and how to fix it.
>
> Did anyone strace the process? If we enable it again, does it behave
> normally?
No, we are looking for someone to look at it.
philip
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.4.5 (Darwin)
>
> iD8DBQFNldnfMkyGM64RGpERAs9bAJ0detDErQaNJOXCfR0EY/kRSHu4ZACdFMt0
> pQS5JjeocqJyAzyBpbsG2eQ=
> =RtHU
> -----END PGP SIGNATURE-----
>
>
> _______________________________________________
> Openembedded-devel mailing list
> Openembedded-devel@lists.openembedded.org
> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel
>
next prev parent reply other threads:[~2011-04-01 14:07 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-01 7:26 patch queue: latest patches not listed in Patchwork Paul Menzel
2011-04-01 13:12 ` Philip Balister
2011-04-01 13:57 ` Koen Kooi
2011-04-01 14:05 ` Philip Balister [this message]
2011-04-01 18:48 ` Phil Blundell
2011-04-01 20:47 ` Yury Bushmelev
2011-04-02 9:44 ` Phil Blundell
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=4D95DBB0.7070606@balister.org \
--to=philip@balister.org \
--cc=openembedded-devel@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