cb354a5af2
Previously, we set timeout in each step such as Lock testbed, Prepare testbed, Run test and KVM dump. When some issue suck like retry happens in one step, it will cause timeout error, but actually, it only needs more time to success. In this pr, we remove the timeout limit in each step and control the timeout outside in each job. When the job runs more than four hours, it will be cancelled. Why I did it Previously, we set timeout in each step such as Lock testbed, Prepare testbed, Run test and KVM dump. When some issue suck like retry happens in one step, it will cause timeout error, but actually, it only needs more time to success. In this pr, we remove the timeout limit in each step and control the timeout outside in each job. When the job runs more than four hours, it will be cancelled. How I did it Remove the timeout parameter in each step, and control the timeout outside in each job. How to verify it Set the timeout of one job to 4 hours, and when timeout happens, azure pipeline will cancel this job. |
||
---|---|---|
.. | ||
azure-pipelines-build.yml | ||
azure-pipelines-download-certificate.yml | ||
azure-pipelines-image-template.yml | ||
azure-pipelines-job-groups.yml | ||
azure-pipelines-Official.yml | ||
azure-pipelines-repd-build-variables.yml | ||
azure-pipelines-UpgrateVersion.yml | ||
build-commonlib.yml | ||
build-template.yml | ||
check-dirty-version.yml | ||
cleanup.yml | ||
docker-sonic-mgmt.yml | ||
docker-sonic-slave-template.yml | ||
docker-sonic-slave.yml | ||
dpkg-cache-cleanup.yml | ||
official-build-cache.yml | ||
official-build-cisco-8000.yml | ||
official-build-multi-asic.yml | ||
official-build.yml | ||
run-test-scheduler-template.yml | ||
run-test-template.yml | ||
template-clean-sonic-slave.yml | ||
template-commonlib.yml | ||
template-skipvstest.yml | ||
template-variables.yml | ||
trigger-publish-artifacts-build.yml | ||
vstest-exclude | ||
vstest-include |