On Wed, 2017-11-15 at 09:15 -0600, Larry Finger wrote:
Would it be a good thing to add a test for the VB KMP to openQA? At least passing the test would provide some assurance that VMs would function after an update. If such a test would be useful, could someone help with the openQA test? It could be as simple as running "modprobe vboxdrv | lsmod | grep vboxdrv" as root and checking for an output that is not empty. Unfortunately, I have no clue on how to write such a test.
There is currently one thing I don't understand yet: virtualbox is part of ring2, which means before a new kernel could be merged, it was guaranteed to build. Also, when looking at the build history of VBox, it had one build fail which was recovered by OBS shortly after (bad buildhost) osc jobhist openSUSE:Factory virtualbox standard x86_64 2017-10-23 19:37:56 virtualbox source change succeeded 3m 11s lamb10:3 2017-10-31 16:12:16 virtualbox source change succeeded 3m 56s lamb08:1 2017-11-04 19:08:25 virtualbox source change failed 0m 12s lamb02:7 2017-11-05 01:22:19 virtualbox retrying bad bu succeeded 2m 55s lamb57:5 2017-11-14 15:40:34 virtualbox source change succeeded 4m 13s lamb57:5 so at least from a 'build' PoV, there should never have been an issue (unless we had an issue with a rebuildtrigger on uninstallable - which is certainly possible) An openQA test might be an option - the question then would rather be if VBox is important enough to delay snapshots and for how long. Cheers Dominique