From: Michael Opdenacker <michael.opdenacker@bootlin.com>
To: Joshua Watt <jpewhacker@gmail.com>
Cc: michael.opdenacker@bootlin.com,
Richard Purdie <richard.purdie@linuxfoundation.org>,
BitBake developer list <bitbake-devel@lists.openembedded.org>
Subject: Re: [bitbake-devel] bitbake-selftest losing sqlite3 database contents!
Date: Tue, 23 Apr 2024 14:35:14 +0200 [thread overview]
Message-ID: <ee1bc3e1-9fcb-48e7-8d64-3461f66c0fb4@bootlin.com> (raw)
In-Reply-To: <CAJdd5GZYDtvvhkKKD4jukbWDatiWPXxQTwsjh+6HcFji+wNCHg@mail.gmail.com>
On 4/20/24 at 22:35, Joshua Watt wrote:
> I'm not exactly sure what the purpose of the read-only prserv is in
> the first place; based on these requirements, it sort of sounds like
> there isn't anyway to make a read-only server that has actual data in
> it :)
>
> Ostensibly, you should be able to write a test fixture that does
> whatever a real-life PR server installation would do to populate a
> database and then make it read-only. You would then do this process on
> the test database before each test where you needed to test the read
> only functionality. You have to do it for each test because as you
> noticed, you should not ever have "carry-over" in state from one test
> to another. Having carry-over between tests is not a good idea for a
> lot of reasons, which is why the hash server tests are setup the way
> that they are with an empty database for each test.
>
> If you need help figuring out how to do this I'm more than happy to
> talk though how you might do it.
I agree with the approach. It's just that I need to stop the read-write
server, and start it again in read-only mode, without losing the database.
For the moment, I managed to run read-only tests on the database I
created "manually", that by testing the database functions, not by using
a PR server client.
This being said, I now have non empty databases which I could use too
for read-only tests. No problem to generate one of them at every new
test series, provided I don't get an empty database again.
I'll continue later if I can, because my priority before the end of the
month is the image upgrade tests.
Cheers
Michael.
--
Michael Opdenacker, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
prev parent reply other threads:[~2024-04-23 12:35 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-18 19:42 bitbake-selftest losing sqlite3 database contents! Michael Opdenacker
2024-04-18 21:04 ` [bitbake-devel] " Richard Purdie
2024-04-19 9:13 ` Michael Opdenacker
2024-04-20 20:35 ` Joshua Watt
2024-04-22 10:00 ` Jan-Simon Möller
2024-04-22 14:47 ` Joshua Watt
2024-04-22 17:17 ` Jan-Simon Moeller
2024-04-23 12:29 ` Michael Opdenacker
2024-04-23 12:35 ` Michael Opdenacker [this message]
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=ee1bc3e1-9fcb-48e7-8d64-3461f66c0fb4@bootlin.com \
--to=michael.opdenacker@bootlin.com \
--cc=bitbake-devel@lists.openembedded.org \
--cc=jpewhacker@gmail.com \
--cc=richard.purdie@linuxfoundation.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).