Project

General

Profile

Actions
Copy link

action #49031

closed

[functional][u][sle][kernel] test to verify kernel-source matches kernel-default

Added by lnussel about 5 years ago. Updated over 3 years ago.

Status:
Resolved
Priority:
Normal
Assignee:
pcervinka
Category:
New test
Target version:
QE Kernel - QE Kernel Done
Start date:
2019-03-11
Due date:
% Done:

0%

Estimated time:
Difficulty:

Description

Sometimes it happens that kernel-source fails to build but kernel-default succeeds. Both packages need to be in sync though otherwise it's not possible to compile kernel modules, including nvidia, virtualbox etc. So would be nice to have a test that verfies that eg kernel-devel, which is a subpackage of kernel-source matches.

Actions
Copy link
 #1

Updated by SLindoMansilla about 5 years ago

  • Subject changed from test to verify kernel-source matches kernel-default to [functional][sle] test to verify kernel-source matches kernel-default

As a result of backlog triaging (see https://progress.opensuse.org/projects/openqatests/wiki#ticket-backlog-triaging for more information).

Please, feel free to adjust the category or the "[label]" if you think different.

Actions
Copy link
 #2

Updated by okurz about 5 years ago

  • Subject changed from [functional][sle] test to verify kernel-source matches kernel-default to [functional][u][sle] test to verify kernel-source matches kernel-default
  • Target version set to Milestone 26
Actions
Copy link
 #3

Updated by mgriessmeier over 4 years ago

  • Target version changed from Milestone 26 to Milestone 27

to be discussed with jose

Actions
Copy link
 #4

Updated by pcervinka over 4 years ago

  • Subject changed from [functional][u][sle] test to verify kernel-source matches kernel-default to [functional][u][sle][kernel] test to verify kernel-source matches kernel-default
  • Assignee set to pcervinka
  • Target version changed from Milestone 27 to 454

Could be planned for next sprint(not now), let's update status after next planning meeting.

Actions
Copy link
 #5

Updated by metan over 4 years ago

We do have a LTP tests that are testing basic functionality by building a kernel module, inserting it and then parsing dmesg for tests results, you can have a look at 'testcases/kernel/device-drivers' in LTP source. Such tests would assert, at least partially that kernel-devel is working, unfortunately these tests are not executed on SLES because as far as I can tell we cannot load unsigned modules into the kernel at all, but maybe I haven't looked into the matter deep enough.

Actions
Copy link
 #6

Updated by pcervinka over 4 years ago

I guess that primary target is Tumbleweed, as kernel changes are frequent that these glitches can happen.

@metan what about to make test (without ltp) based on https://www.tldp.org/LDP/lkmpg/2.6/html/x121.html ?
We can check on openSUSE that module was builded and inserted and on SLES at least that module was builded.

Actions
Copy link
 #7

Updated by pcervinka over 4 years ago

  • Status changed from New to In Progress
  • Target version changed from 454 to 445
Actions
Copy link
 #9

Updated by pcervinka over 4 years ago

PR merged. Test suite extra_tests_kernel defined in Test Development: Kernel on osd.
Same will be done for ooo.

Actions
Copy link
 #10

Updated by pcervinka over 4 years ago

Defined extra_tests_kernel test suite on ooo in openSUSE Tumbleweed Kernel job group.

Actions
Copy link
 #11

Updated by pcervinka over 4 years ago

  • Status changed from In Progress to Feedback
Actions
Copy link
 #12

Updated by pcervinka over 4 years ago

  • Status changed from Feedback to Resolved
Actions
Copy link
 #13

Updated by jlausuch over 4 years ago

  • Target version changed from 445 to 457
Actions
Copy link
 #14

Updated by pcervinka over 3 years ago

  • Target version changed from 457 to QE Kernel Done
Actions
Copy link

Also available in: Atom PDF