Bug 1723781 - Run 'known-issues' and 'bad-tests' in line-coverage test (nightly)
Summary: Run 'known-issues' and 'bad-tests' in line-coverage test (nightly)
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: GlusterFS
Classification: Community
Component: tests
Version: mainline
Hardware: Unspecified
OS: Unspecified
low
medium
Target Milestone: ---
Assignee: Amar Tumballi
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2019-06-25 11:43 UTC by Amar Tumballi
Modified: 2019-07-23 05:01 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2019-07-23 05:01:17 UTC
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Embargoed:


Attachments (Terms of Use)

Description Amar Tumballi 2019-06-25 11:43:54 UTC
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.

Comment 1 Amar Tumballi 2019-07-16 04:52:21 UTC
https://review.gluster.org/#/c/build-jobs/+/23052/

Comment 2 Amar Tumballi 2019-07-23 05:01:17 UTC
Above patch is now merged.


Note You need to log in before you can comment on or make changes to this bug.