openenclave: Testing: Sporadic failures in E2E tests

Some instances: https://oe-jenkins-dev.westeurope.cloudapp.azure.com/blue/organizations/jenkins/pipelines%2FAzure-Linux/detail/Azure-Linux/609/pipeline

TASK [linux/openenclave : Install all the Open Enclave prerequisites YUM packages for development] *** 
fatal: [localhost]: FAILED! => {"changed": false, "msg": "Failed to synchronize cache for repo 'epel'", "rc": 1, "results": []}

https://oe-jenkins-dev.westeurope.cloudapp.azure.com/blue/organizations/jenkins/pipelines%2FAzure-Linux/detail/Azure-Linux/570/pipeline

fatal: [localhost]: FAILED! => {"changed": false, "msg": "Failed to download packages: Curl error (28): Timeout was reached for https://mirrors.fedoraproject.org/metalink?repo=epel-8&arch=x86_64&infra=$infra&content=$contentdir [Connection timed out after 30000 milliseconds]", "results": []}

https://oe-jenkins-dev.westeurope.cloudapp.azure.com/blue/organizations/jenkins/pipelines%2FAzure-Linux/detail/Azure-Linux/603/pipeline

E: Unable to acquire the dpkg frontend lock (/var/lib/dpkg/lock-frontend), is another process using it?"], "stdout": "", "stdout_lines": []

About this issue

  • Original URL
  • State: closed
  • Created 4 years ago
  • Comments: 15 (15 by maintainers)

Commits related to this issue

Most upvoted comments

By e2e I’m referring to installation of prerequisites via ansible Linux or via install-prereqs script on Windows. This changelist introduces the term end-to-end/e2e tests. Have we been using the term e2e to refer to something else?