Bug 1449387

Summary: Request for upstream inclusion of kmod sanity test
Product: [Fedora] Fedora Reporter: Mike Gahagan <mgahagan>
Component: kmodAssignee: kmod development team <kmod-maint>
Status: CLOSED NOTABUG QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: rawhideCC: jonathan, kmod-maint, mgahagan, skozina, ykaliuta
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2017-05-23 14:41:17 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
patch to add kmod sanity test to tests/ none

Description Mike Gahagan 2017-05-09 21:01:05 UTC
Created attachment 1277450 [details]
patch to add kmod sanity test to tests/

Description of problem:
 
There is a proposal to upstream our RHEL test cases into Fedora, as well as
standardize our test interface using Ansible, more details can be found here:
https://fedoraproject.org/wiki/Changes/InvokingTestsAnsible
 
As a result many downstream test cases are being reviewed for upstream use.
I have attached a patch for a downstream kmod sanity test for the
dist-git repo for kmod under the "tests" sub-directory. The initial
step is to port the downstream test, later on will add the required tooling,
Ansible playbook, etc.
 
Can you please review/accept this patch to enable the kmod sanity test for upstream use ?


Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:

Comment 1 Josh Boyer 2017-05-09 21:08:55 UTC
Which branch(es)?

Also, just so I'm clear on this, the test isn't expected to work at all at this
point, correct?

Who will maintain the test going forward?  Does that require commit access for
new people?