ChristianEhrhardt [2016-02-19 14:02 -0000]:
> But due to that we found that in our case sse3 can't be guaranteed in the 
> test environment - so we agreed on ubuntu-devel that we should detect and 
> skip the test then to avoid false positives.

This indeed sounds like the most practical option. It also allows you
to skip only parts of your tests which depend on SSE3. You might have
others which don't.

> But later infinity pointed out if we shouldn't bump our scalingstack
> machine configs as all underlying HW would support that.  In our
> case that would be the flavour autopkgtest.

I'm not sure if such options can be specified in Openstack Nova
flavors, but I'm in no way an expert there. I suggest that you open an
RT and ask IS about that?

Even if we get that, I still suggest to test /proc/mounts and skip the
test -- after all, people want to run these tests in other envs than
the Canonical data center.

> In later discussions there were arguments that for specific software
> should have some kind of exception process where e.g. some part of the
> d/t/control should be able to specify those needs as Restriction/Class
> /or-else.

Class: would be possible, but this is a very specific requirement, and
dpdk would probably remain the only user of it. So let's not
over-design this :-) Also, we don't yet actually implement test
classes. But first and foremost, we don't have testbeds that support
SSE3, so the above Nova config discussion will have to be done either
way.

> I don't want to suggest how this would be implemented best:
> - bump flavours

> - implement new type of restriction in d/t/control

Not going to happen, sorry.

> - implement even qemu-opt in d/t/control

You can already specify options to adt-virt-qemu, so this is already
available. But QEMU options absolutely don't belong into d/t/control,
so this isn't going to happen either.

Thanks,
Martin

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1547528

Title:
  How to handle specific HW needs for dep8 tests in CI

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/dpdk/+bug/1547528/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Reply via email to