Actions
Issue #5811
closedansible-pulp CI fails due to idempotence test taking 10+ mins
Status:
CLOSED - CURRENTRELEASE
Priority:
Normal
Assignee:
Category:
-
Sprint/Milestone:
Start date:
Due date:
Estimated time:
Severity:
2. Medium
Version:
Platform Release:
OS:
Triaged:
No
Groomed:
No
Sprint Candidate:
No
Tags:
CI/CD
Sprint:
Quarter:
Description
ansible-pulp CI is failing on the idempotence test.
Travis errors because there is no stdout or stderr for 10 minutes. The idempotence test runs the entire play, but shows no ouptut during it, so it can take over 10 mins.
It may be that Travis is running especially slow and therefore causing this.
Added by Mike DePaulo about 5 years ago
Added by Mike DePaulo about 5 years ago
Revision fbb5f2f8 | View on GitHub
Problem: ansible-pulp CI fails due to idempotence test taking 10+ mins
Solution: Use a travis_wait of 20 mins for the idempotence test.
Implementation includes:
- Calling the molecule scenarios & test sequences individually
- Not calling cleanup or destroy at the end (never needed, and interfere with Travis debugging anyway.)
- Using a defaults-to-empty-string TRAVIS_WAIT env var in tox.ini .
- Installing an open source go binary, travis-wait-enhanced. (travis_wait is a bash function, so it cannot be used inside tox.)
Fixes: #5811 https://pulp.plan.io/issues/5811 ansible-pulp CI fails due to idempotence test taking 10+ mins
Updated by Anonymous about 5 years ago
- Status changed from NEW to MODIFIED
Applied in changeset ansible-pulp3|fbb5f2f8a4e8f48ab890946e18d4792298e02355.
Updated by fao89 about 5 years ago
- Tags CI/CD added
- Tags deleted (
Pulp 3 installer)
Updated by bmbouter about 5 years ago
- Status changed from MODIFIED to CLOSED - CURRENTRELEASE
Actions
Problem: ansible-pulp CI fails due to idempotence test taking 10+ mins
Solution: Use a travis_wait of 20 mins for the idempotence test.
Implementation includes:
Fixes: #5811 https://pulp.plan.io/issues/5811 ansible-pulp CI fails due to idempotence test taking 10+ mins