From: Omar Sandoval <osan...@fb.com>
Since commit acd9525e93d7 ("PR31265 - rework debuginfod archive-extract
fdcache"), the fdcache limit is only applied when a new file is interned
and it has been at least 10 seconds since the limit was last applied.
This means that the fdcache can go over the limit temporarily.
run-debuginfod-fd-prefetch-caches.sh happens to avoid tripping over this
because of lucky sizes of the files used in the test. However, adding
new files for an upcoming test exposed this failure.
Disable this part of the test for now.
Signed-off-by: Omar Sandoval <osan...@fb.com>
---
tests/run-debuginfod-fd-prefetch-caches.sh | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/tests/run-debuginfod-fd-prefetch-caches.sh
b/tests/run-debuginfod-fd-prefetch-caches.sh
index 3db78ade..90730555 100755
--- a/tests/run-debuginfod-fd-prefetch-caches.sh
+++ b/tests/run-debuginfod-fd-prefetch-caches.sh
@@ -99,6 +99,9 @@ kill $PID1
wait $PID1
PID1=0
+# Since we now only limit the fd cache every 10 seconds, it can temporarily go
+# over the limit. That makes this part of the test unreliable.
+if false; then
#########
# Test mb limit on fd cache
#########
@@ -148,3 +151,4 @@ kill $PID1
wait $PID1
PID1=0
exit 0
+fi
--
2.45.2
