From: Michael Opdenacker <michael.opdenacker@bootlin.com>
To: Khem Raj <raj.khem@gmail.com>,
Richard Purdie <richard.purdie@linuxfoundation.org>
Cc: michael.opdenacker@bootlin.com,
Joshua Watt <JPEWhacker@gmail.com>,
Thomas Petazzoni <thomas.petazzoni@bootlin.com>,
Tim Orling <ticotimo@gmail.com>,
bitbake-devel@lists.openembedded.org
Subject: Re: [bitbake-devel] [PATCH v5 2/5] prserv: move code from __init__ to bitbake-prserv
Date: Wed, 8 May 2024 23:10:57 +0530 [thread overview]
Message-ID: <f4e7af33-b0ac-4620-9f96-f1c83460cd01@bootlin.com> (raw)
In-Reply-To: <CAMKF1srwkF=UOLvd3Een+uVLSjH6yo0XjKwG+=kDzF4g3vbjvQ@mail.gmail.com>
Richard, Khem,
On 5/8/24 at 20:43, Khem Raj wrote:
> On Wed, May 8, 2024 at 6:35 AM Richard Purdie
> <richard.purdie@linuxfoundation.org> wrote:
>> On Fri, 2024-05-03 at 07:14 -0700, Khem Raj via lists.openembedded.org
>> wrote:
>>>
>>> On Fri, May 3, 2024 at 1:04 AM Michael Opdenacker
>>> <michael.opdenacker@bootlin.com> wrote:
>>>> Hi Khem
>>>>
>>>> On 5/2/24 at 18:57, Khem Raj wrote:
>>>>> Hi Michael
>>>>>
>>>>> I am seeing a problem with this series, specifically following
>>>>> patchset is causing a regression
>>>>>
>>>>> * ea1d7b8a36e bitbake: prserv: add bitbake selftests
>>>>> * 5c66d345300 bitbake: prserv: import simplification
>>>>> * c23f2c1680f bitbake: prserv: store_value() improvements
>>>>> * 395b321af29 bitbake: prserv: avoid possible race condition in
>>>>> database code
>>>>> * 8022dc1029d bitbake: prserv: enable database sharing
>>>>> * b81bfdfbed8 bitbake: prserv: add "upstream" server support
>>>>> * 9539ce3b14a bitbake: prserv: move code from __init__ to
>>>>> bitbake-prserv
>>>>> * 4ec1553710b bitbake: prserv: declare "max_package_pr" client
>>>>> hook
>>>>>
>>>>>
>>>>> error seen during packagedata task of base-files
>>>>>
>>>>> WARNING: base-files-3.0.14-r0 do_packagedata: Error talking to
>>>>> server:
>>>>> Connection closed
>>>>> ERROR: Error from client ('127.0.0.1', 59846): 'PRTable' object
>>>>> has no
>>>>> attribute 'sync'
>>>>> Traceback (most recent call last):
>>>>
>>>> Thanks for the review. Actually, did you test with the V6 update I
>>>> sent?
>>>>
>>>
>>> I think it was version in master-next that Richard has staged
>>>
>> It was against v6 so I'm not able to merge these until that is fixed.
>>
> Right, I will try a clean from scratch build and see if it was something
> intermediate to be sure.
Thanks for testing.
I confirm the issue is still there. My apologies for this overlook!
This is a busy week for me, but I will submit a fix as soon as I get the
time, and before the end of the week anyway.
Kind regards
Michael.
--
Michael Opdenacker, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
next prev parent reply other threads:[~2024-05-08 17:41 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-29 20:14 [PATCH v5 0/5] prserv: add support for an "upstream" server michael.opdenacker
2024-04-29 20:14 ` [PATCH v5 1/5] prserv: declare "max_package_pr" client hook michael.opdenacker
2024-04-29 20:14 ` [PATCH v5 2/5] prserv: move code from __init__ to bitbake-prserv michael.opdenacker
2024-05-02 16:57 ` [bitbake-devel] " Khem Raj
2024-05-03 8:04 ` Michael Opdenacker
2024-05-03 14:14 ` Khem Raj
2024-05-08 13:35 ` Richard Purdie
2024-05-08 15:13 ` Khem Raj
2024-05-08 17:40 ` Michael Opdenacker [this message]
2024-05-14 17:03 ` Khem Raj
2024-04-29 20:14 ` [PATCH v5 3/5] prserv: add "upstream" server support michael.opdenacker
2024-04-29 20:14 ` [PATCH v5 4/5] prserv: enable database sharing michael.opdenacker
2024-04-29 20:34 ` Joshua Watt
2024-04-30 12:58 ` Michael Opdenacker
2024-04-30 13:23 ` Joshua Watt
2024-04-30 13:55 ` Joshua Watt
2024-04-30 14:38 ` Michael Opdenacker
2024-04-29 20:14 ` [PATCH v5 5/5] prserv: add bitbake selftests michael.opdenacker
2024-04-29 21:08 ` Joshua Watt
2024-04-30 8:29 ` Michael Opdenacker
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=f4e7af33-b0ac-4620-9f96-f1c83460cd01@bootlin.com \
--to=michael.opdenacker@bootlin.com \
--cc=JPEWhacker@gmail.com \
--cc=bitbake-devel@lists.openembedded.org \
--cc=raj.khem@gmail.com \
--cc=richard.purdie@linuxfoundation.org \
--cc=thomas.petazzoni@bootlin.com \
--cc=ticotimo@gmail.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.