You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
How about handling pre/post plugin scripts (right not they are only for pip installation) mapped with cfg files ?
We can maintain a list of scripts in a directory, and use them only if needed when a cfg needs it.
We need to additionally maintain a mapping of cfg to scripts, and avocado-setup.py needs to handle it.
Example:
[io_nvme]
pre = <pre_script_path/name within wrapper>
post = <post_script_path/name within wrapper>
Additionally, in future we may have profiler commands, files also added.
The text was updated successfully, but these errors were encountered:
@narasimhan-v yes I agree with the proposal as the wrapper is tightly coupled with misc test and avocado so at least what our Test require (in this pip package) we need part of wrapper for maintenance point it will be good that we can make sure our test should not fail, and avoid to run every time those test cases handling in cfg will really help
How about handling pre/post plugin scripts (right not they are only for pip installation) mapped with cfg files ?
We can maintain a list of scripts in a directory, and use them only if needed when a cfg needs it.
We need to additionally maintain a mapping of cfg to scripts, and avocado-setup.py needs to handle it.
Example:
Additionally, in future we may have profiler commands, files also added.
The text was updated successfully, but these errors were encountered: