tests: check blocking concurrent confdb accesses - #17027
Conversation
|
Fri May 15 08:53:37 UTC 2026 Failures:Preparing:
Restoring:
Skipped tests from snapd-testing-skipIf you wish to have any of the below tests run in your PR, in your PR description, add 'unskip:' followed by a copy-and-pasted list (without variants) of the below tests you wish to run (unskip plus test list must be valid yaml)
|
Tests that concurrent confdb accesses to the same databag block when appropriate (no concurrent writes, accesses that can't be parallelized are serviced in order to prevent starvation) and that it's possible to supply a timeout. Signed-off-by: Miguel Pires <miguel.pires@canonical.com>
777b3b3 to
5659226
Compare
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## master #17027 +/- ##
==========================================
- Coverage 79.07% 79.06% -0.01%
==========================================
Files 1378 1375 -3
Lines 191273 191326 +53
Branches 2465 2465
==========================================
+ Hits 151247 151271 +24
- Misses 30920 30944 +24
- Partials 9106 9111 +5
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
|
|
||
| restore: | | ||
| snap unset system experimental.confdb | ||
| rm first_read last_read || true |
There was a problem hiding this comment.
| rm first_read last_read || true | |
| rm first-read last-read password=last-password || true |
But tbh I don't even know if this is needed
There was a problem hiding this comment.
password=last-password isn't a file, it's the key-value set for one of the writes
Tests that concurrent confdb accesses to the same databag block when appropriate (no concurrent writes, accesses that can't be parallelized are serviced in order to prevent starvation) and that it's possible to supply a timeout.
https://warthogs.atlassian.net/browse/SNAPDENG-35594