Description of problem: Currently, there is no run which runs all the .t files. Ie, if a test is marked known-issue or bad, there is no way we can watch if it is still relevant or not because no tests touch it. It is good to run it at least in one of the jobs, and line-coverage is the best, mainly because it doesn't consider the failures. Version-Release number of selected component (if applicable): master Expected results: Provide proper options to regression run, so it can consider the bad tests and known issues tests to be running.
https://review.gluster.org/#/c/build-jobs/+/23052/
Above patch is now merged.