f56bf4caf7
Due to a design problem and misunderstanding between the Avocado framework and QEMU, Avocado is fetching many asset artifacts it shouldn't be fetching, exhausting the jobs CI timeout. Since Avocado artifacts are cached, this is not an issue with old forks, which already have populated the cache and do not need to download new artifacts to run the tests. However this is very confusing to new contributors who start to fork the project and keep having failing CI pipelines. As a temporary kludge, add the QEMU_CI_AVOCADO_TESTING variable to allow old forks to keep running the Avocado tests, while still allowing new forks to use the mainstream set of CI tests. Keep the tests enabled by default on the mainstream namespace which is old enough to have a populated cache, hoping we will keep this cache long enough until the Avocado/QEMU design issue is fixed. Signed-off-by: Philippe Mathieu-Daudé <f4bug@amsat.org> Reviewed-by: Alex Bennée <alex.bennee@linaro.org> Message-Id: <20210525082556.4011380-9-f4bug@amsat.org> |
||
---|---|---|
.. | ||
edk2 | ||
opensbi | ||
buildtest-template.yml | ||
buildtest.yml | ||
check-dco.py | ||
check-patch.py | ||
container-core.yml | ||
container-cross.yml | ||
container-template.yml | ||
containers.yml | ||
crossbuild-template.yml | ||
crossbuilds.yml | ||
edk2.yml | ||
opensbi.yml | ||
qemu-project.yml | ||
stages.yml | ||
static_checks.yml |