From 999595c74a6b838de099945e3c74bb4187381694 Mon Sep 17 00:00:00 2001 From: Casey Rodarmor Date: Mon, 21 Aug 2023 14:06:31 -0700 Subject: [PATCH 1/2] Mention increasing maximum number of open files --- README.md | 3 +++ 1 file changed, 3 insertions(+) diff --git a/README.md b/README.md index be2203823b..2761826aa5 100644 --- a/README.md +++ b/README.md @@ -151,6 +151,9 @@ just doc just watch ltest --all ``` +If the tests are failing or hanging, you might need to increase the maximum +number of open files with `ulimit -n 1024`. + We also try to follow a TDD (Test-Driven-Development) approach, which means we use tests as a way to get visibility into the code. Tests have to run fast for that reason so that the feedback loop between making a change, running the test and From 683f5042962be46394044963abcb511e75d2561d Mon Sep 17 00:00:00 2001 From: Casey Rodarmor Date: Mon, 21 Aug 2023 14:08:45 -0700 Subject: [PATCH 2/2] Clarify --- README.md | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/README.md b/README.md index 2761826aa5..8f8db824db 100644 --- a/README.md +++ b/README.md @@ -152,7 +152,8 @@ just watch ltest --all ``` If the tests are failing or hanging, you might need to increase the maximum -number of open files with `ulimit -n 1024`. +number of open files by running `ulimit -n 1024` in your shell before you run +the tests, or in your shell configuration. We also try to follow a TDD (Test-Driven-Development) approach, which means we use tests as a way to get visibility into the code. Tests have to run fast for that