| Message ID | 20201022120145.207094-1-thuth@redhat.com |
|---|---|
| State | New |
| Headers | show |
| Series | tests/acceptance: Enable AVOCADO_ALLOW_UNTRUSTED_CODE in the gitlab-CI | expand |
On 22/10/2020 14.01, Thomas Huth wrote: > 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
diff --git a/.gitlab-ci.yml b/.gitlab-ci.yml index 66ad7aa5c2..f1b7df0b66 100644 --- a/.gitlab-ci.yml +++ b/.gitlab-ci.yml @@ -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
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. Signed-off-by: Thomas Huth <thuth@redhat.com> --- .gitlab-ci.yml | 2 ++ 1 file changed, 2 insertions(+)