aboutsummaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorJosselin Poiret <dev@jpoiret.xyz>2024-05-05 19:51:03 +0200
committerLudovic Courtès <ludo@gnu.org>2024-08-31 10:45:01 +0200
commite72150039fa15d8f78fa5d2386f0289d7f94a8be (patch)
tree6da407e85e110b4626f158a1c3a6837d299d6d9e
parent7e7cd642d7e9ca9750872113afe1ed961e8a1224 (diff)
downloadguix-e72150039fa15d8f78fa5d2386f0289d7f94a8be.tar
guix-e72150039fa15d8f78fa5d2386f0289d7f94a8be.tar.gz
gnu: redis: Skip OOM score test.
Since "daemon: Sacrifice builders on OOM." the default OOM score has changed to 1000, which effictively render this test impossible to pass. * gnu/packages/databases.scm (redis): Skip OOM score test. Change-Id: I92ff49425faa755cd4d0a22a33bf8b1fea03d25a
-rw-r--r--gnu/packages/databases.scm5
1 files changed, 5 insertions, 0 deletions
diff --git a/gnu/packages/databases.scm b/gnu/packages/databases.scm
index f5283fe424..3bcade03f8 100644
--- a/gnu/packages/databases.scm
+++ b/gnu/packages/databases.scm
@@ -2606,6 +2606,11 @@ similar to BerkeleyDB, LevelDB, etc.")
;; "background AOF rewrite to finish", perhaps because dead
;; processes persist as zombies in the build environment.
(("unit/aofrw") "")
+ ;; The OOM score tests try to raise the current OOM score, but
+ ;; our build environment already sets it for all children to
+ ;; the highest possible one (1000). We can't lower it because
+ ;; we don't have CAP_SYS_RESOURCE.
+ (("unit/oom-score-adj") "")
(("integration/aof(-multi-part)?") "")
(("integration/failover") "")
(("integration/replication-4") "")