Skip to contentSkip to conversation

tests/acceptance: Enable AVOCADO_ALLOW_UNTRUSTED_CODE in the gitlab-CI

PATCH In review Thomas Huth 1 participant 2 messages Oct 22, 2020

lore
Share & tools
lore
#0 lore raw

PATCH 1/1 tests/acceptance: Enable AVOCADO_ALLOW_UNTRUSTED_CODE in the gitlab-CI

The tests are running in containers here, so it should be OK to run with AVOCADO_ALLOW_UNTRUSTED_CODE enabled in this case. We also have to set CONTINUOUS_INTEGRATION in this case to avoid that some tests from ppc_prep_40p.py are failing in the CI.

---
 .gitlab-ci.yml | 2 ++
 1 file changed, 2 insertions(+)
.gitlab-ci.yml +2 -0
index 66ad7aa5c2..f1b7df0b66 100644
@@ -66,6 +66,8 @@ include:
     - if [ -d ${CI_PROJECT_DIR}/avocado-cache ]; then
         du -chs ${CI_PROJECT_DIR}/avocado-cache ;
       fi
+    - export AVOCADO_ALLOW_UNTRUSTED_CODE=1
+    - export CONTINUOUS_INTEGRATION=1
   after_script:
     - cd build
     - python3 -c 'import json; r = json.load(open("tests/results/latest/results.json")); [print(t["logfile"]) for t in r["tests"] if t["status"] not in ("PASS", "SKIP", "CANCEL")]' | xargs cat
Signature · 1 line
2.18.2
#1 lore raw
Quoted 4 lines · Thomas Huth

The tests are running in containers here, so it should be OK to run with AVOCADO_ALLOW_UNTRUSTED_CODE enabled in this case. We also have to set CONTINUOUS_INTEGRATION in this case to avoid that some tests from ppc_prep_40p.py are failing in the CI.

Please disregard this patch ... CONTINUOUS_INTEGRATION also disables a test that has been working in the CI before ... so this should be handled differently.

Thomas