Request classic confinement for opencl-cts

[mckeesh]

To make the review of your request easier, please use the following template to provide all the required details and also include any other information that may be relevant.

---

• name: opencl-cts
• description: An OpenCL conformance test suite
• snapcraft: https://github.com/canonical/opencl-cts-snap/blob/main/snap/snapcraft.yaml
• upstream: GitHub - KhronosGroup/OpenCL-CTS: The OpenCL Conformance Tests
• upstream-relation: Developing tests at Canonical
• supported-category: System testing suite
• reasoning: Strict confinement is not ideal for system testing, as the checkbox framework has discovered. This will be consumed by checkbox graphics tests (currently in contrib), and the checkbox team directed us to provide conformance test suites as snaps to avoid fragile test setup scripts.

Sorry for the template edit; I’m only allowed two links as a new user

I understand that strict confinement is generally preferred over classic.

I’ve tried the existing interfaces to make the snap to work under strict confinement.

Note that snappy-debug can be used to identify possible required interfaces. See for more information.

[jslarraz]

Hey @mckeesh

If the main reason to ask for classic is that checkbox uses this test suite, maybe it will be better to stage the test suite directly in the checkbox snap (in the variants that requires this testsuite). It will ensure the presence of the required tests.

Is there any reason why this approach is not possible?

Thanks

[mckeesh]

Hi @jslarraz, the main reason is that we will be submitting several conformance test suites packaged this way at the checkbox team’s request (@Hook25, FYI). The test suites will be far too large to add to Checkbox itself