On Mon, Jul 10, 2023 at 03:31:23PM +0300, Max Gurtovoy wrote: > I think it is more than just commit message. Okay, starting to understand what's the problem. > A lot of code that we can avoid was added regarding the --context cmdline > argument. Correct and it's not optional to get the tests passing for the fc transport. > Maybe it's worth cleaning it.. It really solves the problem that the autoconnect setup of nvme-cli is distrubing the tests (*). The only other way I found to stop the autoconnect is by disabling the udev rule completely. If autoconnect isn't enabled the context isn't necessary. Though changing system configuration from blktests seems at bit excessive. Another option is to detect if autoconect is enabled and report this when starting the tests. In this case we could remove the context part completely. Obviously, I would prefer to keep it but I am certaintaly not against dropping it and make blktests a bit simpler if this is the preference. I just need to remember to disable the autoconnect stuff when using blktests. (*) Sure we can fix this but at this point. Though I think it's a bit strange for a test suite to depend/interact with external components in this way.
