aboutsummaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorMarcoFalke <*~=`'#}+{/-|&$^_@721217.xyz>2023-06-26 15:51:52 +0200
committerMarcoFalke <*~=`'#}+{/-|&$^_@721217.xyz>2023-08-23 15:40:05 +0200
commitfa378bed56db66119b7f5847b749c4900b04c0a1 (patch)
treee3dd9864a0d73fda8872a177f99b79c3e2e0967a
parentfa8c250c2f6b43f828020a35a8ee4262755c39ed (diff)
ci: Start with clean env
This should help to avoid non-determinism.
-rw-r--r--ci/README.md7
1 files changed, 4 insertions, 3 deletions
diff --git a/ci/README.md b/ci/README.md
index b4158d0183..096b75324f 100644
--- a/ci/README.md
+++ b/ci/README.md
@@ -20,10 +20,11 @@ requires `bash`, `docker`, and `python3` to be installed. To install all require
sudo apt install bash docker.io python3
```
-To run the test stage with a specific configuration,
+It is recommended to run the ci system in a clean env. To run the test stage
+with a specific configuration,
```
-FILE_ENV="./ci/test/00_setup_env_arm.sh" ./ci/test_run_all.sh
+env -i HOME="$HOME" PATH="$PATH" USER="$USER" bash -c 'FILE_ENV="./ci/test/00_setup_env_arm.sh" ./ci/test_run_all.sh'
```
### Configurations
@@ -45,7 +46,7 @@ It is also possible to force a specific configuration without modifying the
file. For example,
```
-MAKEJOBS="-j1" FILE_ENV="./ci/test/00_setup_env_arm.sh" ./ci/test_run_all.sh
+env -i HOME="$HOME" PATH="$PATH" USER="$USER" bash -c 'MAKEJOBS="-j1" FILE_ENV="./ci/test/00_setup_env_arm.sh" ./ci/test_run_all.sh'
```
The files starting with `0n` (`n` greater than 0) are the scripts that are run