As far as I could see, the current behavior doesn't allow for extra arguments to be given to ctest. This is a bit limiting. Personally, I find it very annoying to have to search for output logs to get more in-depth test reports, as well as have some longer tests being executed when stopping on previous errors would be desired. All of that can be fixed with a couple of extra arguments.
A simple solution would be to have an extra field on the setup config object perhaps called ctest_extra_args.
I thought about having it in the executor opts, but that doesn't make much sense since reading the documentation this seems to be intended to be passed to the executor plugin only.
Alternatively, running the ctest module with some environment variable would work as well, but this looks less flexible and unless it is targeted at the ctest module, would possibly contaminate other environments unnecessarily.
I created a simple implementation for that proposal, which for now is working fine for me, but I think this is generic enough so others might benefit from it as well. Also having it upstreamed is much better than having to sync my forked version.
It's been nearly a decade since I seriously programmed in Lua, so I'm not up-to-date with best practices. Any input is highly appreciated here :D.
This is the link for the changes I made.
As far as I could see, the current behavior doesn't allow for extra arguments to be given to ctest. This is a bit limiting. Personally, I find it very annoying to have to search for output logs to get more in-depth test reports, as well as have some longer tests being executed when stopping on previous errors would be desired. All of that can be fixed with a couple of extra arguments.
A simple solution would be to have an extra field on the setup config object perhaps called ctest_extra_args.
I thought about having it in the executor opts, but that doesn't make much sense since reading the documentation this seems to be intended to be passed to the executor plugin only.
Alternatively, running the ctest module with some environment variable would work as well, but this looks less flexible and unless it is targeted at the ctest module, would possibly contaminate other environments unnecessarily.
I created a simple implementation for that proposal, which for now is working fine for me, but I think this is generic enough so others might benefit from it as well. Also having it upstreamed is much better than having to sync my forked version.
It's been nearly a decade since I seriously programmed in Lua, so I'm not up-to-date with best practices. Any input is highly appreciated here :D.
This is the link for the changes I made.