[wpt-sync] Sync PR 33373 - Support metadata properties outside wptrunner
Categories
(Testing :: web-platform-tests, task, P4)
Tracking
(firefox106 fixed)
Tracking | Status | |
---|---|---|
firefox106 | --- | fixed |
People
(Reporter: wpt-sync, Unassigned)
References
(Depends on 1 open bug, )
Details
(Whiteboard: [wptsync downstream])
Sync web-platform-tests PR 33373 into mozilla-central (this bug is closed when the sync is complete).
PR: https://github.com/web-platform-tests/wpt/pull/33373
Details from upstream follow.
James Graham <james@hoppipolla.co.uk> wrote:
Support metadata properties outside wptrunner
For each CI system we run in there's a set of metadata properties
required to distinguish different configurations. For example on
GitHub when running infrastructure tests, that's the browser product
name, whereas in vendor CI it's typically different platform
configurations.Until now the properties used when updating the metadata have been
stored in the browser product definition in wptrunner. But given they
vary per system that doesn't make much sense. Instead it should be
possible to pass in the properties relevant to the metadata being
updated.To do that this PR adds the concept of a "metadata properties"
file. That's a JSON file of the form{
"property": ["name"],
"dependent": {"name": ["other"]}
}which specifies which properties can be used for update (this matches
the data format of theupdate_properties
functions in wptrunner
products).By default a file name
update_properties.json
in the root metadata
will be used to specify the properties. This makes sense since it puts
the properties together with the relevant metadata on the filesystem.For now reading the properties from wptrunner is still supported,
because users need time to transition to the new format. But the
intent is to remove that later.
Assignee | ||
Updated•3 years ago
|
Assignee | ||
Updated•2 years ago
|
Assignee | ||
Comment 1•2 years ago
|
||
Comment 3•2 years ago
|
||
bugherder |
Description
•