DAOS-11749 test: Use default svcn in /pool/create_capacity.py test
Update the /pool/create_capacity.py test to use the default pool svcn to avoid overutilizing engine 0, resulting in pool destroy timeouts.
Also fixing a pylint error in harness/advanced.py.
Quick-functional: true Test-tag: create_performance Test-repeat: 5
Required-githooks: true
Signed-off-by: Phil Henderson [email protected]
Bug-tracker data: Ticket title is 'pool/create_capacity.py timeout on pool destroy in teardown' Status is 'In Progress' Labels: 'triaged' https://daosio.atlassian.net/browse/DAOS-11749
Test stage Functional Hardware Large completed with status FAILURE. https://build.hpdd.intel.com//job/daos-stack/job/daos/view/change-requests/job/PR-10455/1/execution/node/480/log
Test stage Functional Hardware Large completed with status FAILURE. https://build.hpdd.intel.com//job/daos-stack/job/daos/view/change-requests/job/PR-10455/2/execution/node/480/log
All five repetitions of the pool/create_capacity.py test passed in https://build.hpdd.intel.com/job/daos-stack/job/daos/job/PR-10455/3
Quick-functional should not be used for landings. Does this pass bandit?
It doesn't make any changes that would fail the Bandit check. If we need, though, I can push another commit.