Manifest updater should collapse conditions where possible
Categories
(Testing :: web-platform-tests, enhancement)
Tracking
(firefox69 fixed)
Tracking | Status | |
---|---|---|
firefox69 | --- | fixed |
People
(Reporter: kats, Assigned: jgraham)
References
Details
Attachments
(2 files)
Reporter | ||
Comment 1•6 years ago
|
||
Assignee | ||
Comment 2•5 years ago
|
||
Previously the wpt metadata update code generated rather conservative
conditionals, simply inclusing every possible condition unless all the
tests had the same outcome or similar. This isn't very nice to read
and makes the metadata rather fragile to changes in the configuration.
A better approach is to build a decision tree from the metadata,
choosing the properties to split on using a simple greedy algorithm,
as follows:
-
Given a set of test results, associated run_info_properties and
properties that we want to use, partition the test results by each
property we are using in turn. -
For each partition, generate a score for how uniform the results
are in each subset after partition. The score should be good if the
partition results in small numbers of groups with mostly uniform
test results and bad if it results in a large number of groups or
groups with a mix of test results. For this we adopt a metric based
on the Shannon entropy. -
Chose the partition resulting in the best score, and use that as a
condition in the tree. -
Recursively reapply the algorithm to each group that's been
created.
Comment 4•5 years ago
|
||
bugherder |
Updated•5 years ago
|
Comment 9•5 years ago
|
||
bugherder |
Description
•