Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Move dracut into its own extratest module #6745

Merged
merged 1 commit into from
Feb 22, 2019

Conversation

paolostivanin
Copy link
Contributor

@paolostivanin paolostivanin commented Feb 11, 2019

As discussed in poo#47123, we are going to move dracut into its own module.

Verification still running.

SLE:

openSUSE:

@paolostivanin paolostivanin changed the title [WIP] Move dracut into its own extratest module Move dracut into its own extratest module Feb 22, 2019
@paolostivanin
Copy link
Contributor Author

ping to @okurz :)

@okurz okurz merged commit 1b9972f into os-autoinst:master Feb 22, 2019
@okurz
Copy link
Member

okurz commented Feb 22, 2019

please adjust the test suites and scenarios on o3 and osd. However I think the module should not be added to extra_tests_in_textmode but rather be defined as it's own testsuite, e.g. like docker_image, e.g.

a new test suite "dracut"

BOOT_HDD_IMAGE=1
DESKTOP=textmode
HDD_1=%DISTRI%-%VERSION%-%ARCH%-%BUILD%-%DESKTOP%@%MACHINE%.qcow2
START_AFTER_TEST=create_hdd_textmode
UEFI_PFLASH_VARS=%DISTRI%-%VERSION%-%ARCH%-%BUILD%-%DESKTOP%@%MACHINE%-uefi-vars.qcow2
EXTRATEST=dracut

@paolostivanin paolostivanin deleted the fix-poo47123 branch February 22, 2019 08:29
@czerw
Copy link
Contributor

czerw commented Feb 22, 2019

Yes, we will update osd first and qam jobs, wait for results, than I will start discussion with job owners on ooo and owners of product qa job groups on osd.

@paolostivanin
Copy link
Contributor Author

+1

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
3 participants