QA (public) » openQA Project (public) » openQA Tests (public)

okurz wrote:

Good that you have this reported. I will change category to "New test" though as this is what we commonly use according to https://progress.opensuse.org/projects/openqatests/wiki#ticket-workflow do describe any "extension of test coverage". "Bugs in existing tests" means basically: "It fails now but worked in before" which might be misleading to some because the test actually is "green" :)

It worked in the past because RT planned to be released 3 months later after SLES FCS. At that time, RT kernel version higher than the SLES GA version and thus it can always boot to RT kernel.

For SLE15, RT aligned the release cycle with SLES, thus RT kernel version always behind SLES. It is due to RT accept the commit that has been stable in SLES and not update the kernel as frequent as SLES.

The current workaround is to mention this in RT Release Notes

Jeffreycheung wrote:

The current workaround is to mention this in RT Release Notes

As long as we are talking about workarounds, do we plan to ship adequate grub configs for RT in the future ? So the system boots RT kernel without any user intervention.

mloviska wrote:

Jeffreycheung wrote:

The current workaround is to mention this in RT Release Notes

As long as we are talking about workarounds, do we plan to ship adequate grub configs for RT in the future ? So the system boots RT kernel without any user intervention.

Well, I left comment in bug that this would be WONFIX in RT15 SP1, I will try to fix it in RT15 SP2.

Jeffreycheung wrote:

mloviska wrote:

Jeffreycheung wrote:

The current workaround is to mention this in RT Release Notes

As long as we are talking about workarounds, do we plan to ship adequate grub configs for RT in the future ? So the system boots RT kernel without any user intervention.

Well, I left comment in bug that this would be WONFIX in RT15 SP1, I will try to fix it in RT15 SP2.

Alright then, so basically this means that we need to come with a workaround in our test suites as long as we want keep rt test modules as they are designed (kmp_modules, rt_is_realtime, rt_peak_pci, rt_preempt_test). I guess that rt_devel_packages can stay as it is in any case.
https://openqa.suse.de/tests/2226731#

It was not so hard to resurrect boot_rt_kernel
http://eris.suse.cz/tests/11336#step/boot_rt_kernel/7

awesome you could reuse that :)

PR merged.

https://openqa.suse.de/tests/2435812 failed, one test suite failed due to mismatching needle. As for rt_preempt_test we could exclude it as we plan to replace it anyway. WDYT?

Needle issue has been already fixed.
https://openqa.suse.de/tests/2436306#step/kmp_modules/37

Sure we can exclude rt_preempt_test, I just intended to make it visible that it has a problem. Beside that, I have already labeled the job run with a bug report and poo, to make it easier for reviewers.