I’m facing some strange behavior when using Sweep Parameter step with multiple resources. It seems that only the default selected resource is initialized/used while others won’t be open and steps that use them neither execute the part that involves the resource nor complain.
Steps to reproduce using example code:
- Create two Power Analyzer resources:
PSU1
and PSU2
.
- Create a test plan:
Sweep Parameter
parent + Charge
child.
- Parametrize over
Charge / Power Analyzer
and add two rows to sweep: PSU1
, PSU2
.
- Run the plan and observe only the PSU selected by default is initialized/used properly.
Am I doing something wrong or this use case is not supported?
2 Likes
@pythonized this appears to be a bug and I was able to reproduce. I’m not sure if this is an acceptable alternative, but it does seem if you select “Short Lived Connections” from Settings > Engine > Resource Strategy the resources are swept.
I’ve submitted an issue here: Sweeping Resources Does not work correctly (#664) · Issues · OpenTAP / OpenTAP · GitLab
1 Like
Thank you @brennen_direnzo! I’ll try the suggested workaround, it might be acceptable for the time being.
1 Like
@pythonized FYI this issue has been resolved and will be part of our 9.15 release at the end of the month:
1 Like
Thank you @brennen_direnzo, I already applied the fix locally and can confirm it works fine!
1 Like