Comment # 19 on bug 1178453 from Oliver Kurz

(In reply to Stefan Br������ns from comment #17)
> Sorry I haven't followed up on this.
> 
> I tried enabling the test suite in openCV, and the gapi test is also
> segfaulting on OBS. Unfortunately the test suite has to many external
> dependencies to be useful without much more work, so I have kept it disabled
> for now.
> 
> The gapi code seems to trigger some error probably related to qemu/kvm in
> its dispatch code (so either CPU dispatching chooses the wrong path, or the
> dispatched code is failing).
> 
> Will try to create trivial reproducer the coming days.
> 
> @dimstar, @fokurz - for runtime dispatched code it would be useful to have
> different (emulated) hardware, both on OBS (internal testsuite) and on
> openQA. Do we have something in place for this? I.e. request a host which
> has only SSE2.

Hm, I think what's possible is to run `osc build` locally or within
respectively configured VMs. For openQA we can configure the VMs that are used
for tests on the fly. E.g. with

```
openqa-clone-job --skip-chained-deps --within-instance
https://openqa.opensuse.org 1583395 TEST=gnuhealth_only_sse2 QEMUCPU=base,sse2
_GROUP=0 BUILD=debug_bsc1178453
```

I could create
https://openqa.opensuse.org/t1583917
which (hopefully) will spawn a test job on a machine that has only sse2
enabled. We can tweak that with the "QEMUCPU" parameter which is directly
passed to `qemu -cpu ���������`

Everyone with operator permissions on an openQA instance can run the same. You
already have according permissions.