ci: Skip memorydb tests

The test drivers are now written for persistent storage to properly excercise the whole process from library initialization, reading data from persistent storage, writing them and more. The memorydb is specific as it is not persistent. In the tests, we are able to initialize it successfully, but the content is thrown away and then a new empty token is created again, which does not have the expected content. Signed-off-by: Jakub Jelen <[email protected]>
latchset · Dec 10, 2024 · 951bd54 · 951bd54
1 parent acc4f3f
commit 951bd54
Showing 1 changed file with 1 addition and 1 deletion.
diff --git a/.github/workflows/build.yml b/.github/workflows/build.yml
@@ -15,7 +15,7 @@ jobs:
       fail-fast: false
       matrix:
         name: [ossl3, fips, release, dynamic, i686, minimal]
-        db: [memorydb, jsondb, sqlitedb, nssdb]
+        db: [jsondb, sqlitedb, nssdb] # FIXME: Add "memorydb" when it will be persistent
     container: fedora:latest
     steps:
       - name: Get Date for DNF cache entry