From 5a914b606547294841f4e691e10b3b5be2aef13e Mon Sep 17 00:00:00 2001 From: Aniekan Eshiet <40662154+kapelo@users.noreply.github.com> Date: Fri, 18 Oct 2024 15:45:00 +0100 Subject: [PATCH] Add more troubleshooting entry (#1590) * Add more troubleshooting entry This covers cases when a user session times out during E2E test run * address comments --------- Co-authored-by: aeshiet --- .../en/contribute/code/core/automated-tests.md | 17 +++++++++++++++++ 1 file changed, 17 insertions(+) diff --git a/content/en/contribute/code/core/automated-tests.md b/content/en/contribute/code/core/automated-tests.md index f9b0b1324..8532c6e54 100644 --- a/content/en/contribute/code/core/automated-tests.md +++ b/content/en/contribute/code/core/automated-tests.md @@ -225,6 +225,23 @@ Try the following: - Manually downloaded the images. To download images manually, you can use either docker-compose or docker: - With docker, you'd do a docker pull for every image you want to download. - With docker-compose, you'd save all docker-compose files in a folder, do a docker-compose pull, and point to your files as a source. Read more on [docker compose pull](https://docs.docker.com/engine/reference/commandline/compose_pull/) + +If you experience errors such as: + +``` +A user session timing out while running the test. +``` +This could be because there are some issues with data or there could be a large number of images and volumes that caused docker to crash. +We recommend cleaning all the docker data to be able to start afresh and clean. It is important, however, to note that these commands will delete everything. +And the e2e tests might take a little longer to run because all the images need to be downloaded again. + +Try running the following commands: +- `docker system prune` +- `docker image prune -a` +- `docker volume prune -a` +- `docker network prune` + +Repeat the above steps until all data has been deleted. ### Test Architecture