Bug 483 - replicable test suite for LibreSOC 3D MESA library
Summary: replicable test suite for LibreSOC 3D MESA library
Status: CONFIRMED
Alias: None
Product: Libre-SOC's first SoC
Classification: Unclassified
Component: Source Code (show other bugs)
Version: unspecified
Hardware: PC Linux
: --- enhancement
Assignee: Luke Kenneth Casson Leighton
URL:
Depends on:
Blocks: 251
  Show dependency treegraph
 
Reported: 2020-08-30 21:02 BST by Luke Kenneth Casson Leighton
Modified: 2020-08-30 23:21 BST (History)
2 users (show)

See Also:
NLnet milestone: NLNet.2019.10.042.Vulkan
total budget (EUR) for completion of task and all subtasks: 0
budget (EUR) for this task, excluding subtasks' budget: 0
parent task for budget allocation:
child tasks for budget allocation:
The table of payments (in EUR) for this task; TOML format:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Luke Kenneth Casson Leighton 2020-08-30 21:02:49 BST
even if it is made from tutorials online a replicable test suite that helps
with the development of the 3D MESA library is needed.

interestingly this same test suite can be run against Kazan (or utilised
for testing of other 3D MESA Vulkan drivers)
Comment 1 Jacob Lifshay 2020-08-30 21:47:24 BST
The Vulkan conformance test suite should be the canonical location for all tests that are using the Vulkan API and not calling driver internals.

See https://salsa.debian.org/Kazan-team/kazan/-/blob/master/run-cts.sh
Comment 2 Luke Kenneth Casson Leighton 2020-08-30 23:21:47 BST
(In reply to Jacob Lifshay from comment #1)
> The Vulkan conformance test suite should be the canonical location for all
> tests that are using the Vulkan API and not calling driver internals.
> 
> See https://salsa.debian.org/Kazan-team/kazan/-/blob/master/run-cts.sh

excellent addition.

the idea here is not so much to prioritise or select one and only one "official" test suite, it is to collate *all* the test applications and suites (as submodules) that are used.

including that one you suggested about 8 or 9 days ago (what was it again?)

imagine vivek for example losing all work, the only thing he has online is the mesa branch being developed.  everything else has to be recreated.

imagine soneone else joining and helping, they have to laboriously and manually install the same test programs.