https://gerrit.wikimedia.org/r/#/c/operations/puppet/+/587531/ had:
Patch Set 2: Verified-1
Main test build failed.
> operations-puppet-tests-buster-docker ABORTED in 5m 07s
https://gerrit.wikimedia.org/r/#/c/operations/puppet/+/587531/ had:
Patch Set 2: Verified-1
Main test build failed.
> operations-puppet-tests-buster-docker ABORTED in 5m 07s
Subject | Repo | Branch | Lines +/- | |
---|---|---|---|---|
Slightly bump operations-puppet-tests timeout | integration/config | master | +1 -1 |
Status | Subtype | Assigned | Task | ||
---|---|---|---|---|---|
Resolved | hashar | T249726 operations-puppet-tests-buster-docker times out after 5 minutes | |||
Declined | None | T249727 Migrate integration-agent-puppet-docker-1001 to a different cloudvirt machine | |||
Resolved | Jdforrester-WMF | T250502 Rebuild integration-agent-puppet-docker-1001 to use Stretch |
Change 587539 had a related patch set uploaded (by Hashar; owner: Hashar):
[integration/config@master] Slightly bump operations-puppet-tests timeout
Change 587539 merged by jenkins-bot:
[integration/config@master] Slightly bump operations-puppet-tests timeout
I have raised the timeout https://integration.wikimedia.org/ci/computer/integration-agent-puppet-docker-1001/
The instance runs on cloudvirt1005.eqiad.wmnet which has bad performances (see T223971: Old cloudvirt (with Intel Xeon) are half the speed of newer ones (Intel Sky Lake) with the root cause most probably being T225713: CPU scaling governor audit).
So I guess we should have the instance migrated to another cloudvirt that is not affected.
The timeout raise is a workaround. The fix is to move the instance to a better cloudvirt machine: T249727: Migrate integration-agent-puppet-docker-1001 to a different cloudvirt machine.
All puppet patches are now run on integration-agent-puppet-docker-1002, which is on cloudvirt1015.