From 122b3770e2849150c4b9e56ac429669dad52229e Mon Sep 17 00:00:00 2001 From: Erik Schierboom Date: Wed, 7 Aug 2024 11:10:21 +0200 Subject: [PATCH] Fix timeout --- building/tooling/docker.md | 4 ++-- building/tooling/test-runners/interface.md | 2 +- 2 files changed, 3 insertions(+), 3 deletions(-) diff --git a/building/tooling/docker.md b/building/tooling/docker.md index 2e5112ac..b4bdcdb1 100644 --- a/building/tooling/docker.md +++ b/building/tooling/docker.md @@ -12,8 +12,8 @@ Our [Best Practices page](/docs/building/tooling/best-practices) has lots of tip ### Timeouts -Each tooling run has a ten-second window in which to execute. -At the end of that period it will be timed out with a 408 error code. +The test runner gets 100% CPU with 3GB of memory for a 20 second window per solution. +After 20 seconds, the process is halted and reports a time-out with a 408 error code. ### Stdout/stderr diff --git a/building/tooling/test-runners/interface.md b/building/tooling/test-runners/interface.md index bfce0b62..83cb1951 100644 --- a/building/tooling/test-runners/interface.md +++ b/building/tooling/test-runners/interface.md @@ -15,7 +15,7 @@ All interactions with the Exercism website are handled automatically and are not ### Allowed run time -The test runner gets 100% machine resources for a 20 second window per solution. +The test runner gets 100% CPU with 3GB of memory for a 20 second window per solution. After 20 seconds, the process is halted and reports a time-out. ## Output format