Open gsnedders opened 6 months ago
Adding --properties-file metadata/update-properties.json
made it work, so presumably it isn't using that path by default?
I made a patch for ladybird to fix this, as we don't have the metadata/update-properties.json
file locked down yet. (or... even generated, or know how to generate it or ...)
Perhaps that should be added? or the fallback should be removed entirely.
@jgraham might have a stronger opinion here, but IMO we should fix what's broken. On the other hand, the fact that it has been broken for a while suggests that maybe we should just drop support.
I made a patch for ladybird to fix this, as we don't have the metadata/update-properties.json file locked down yet. (or... even generated, or know how to generate it or ...)
see https://web-platform-tests.org/tools/wptrunner/docs/expectation.html#property-configuration
The Python exception is actually a dupe of https://github.com/web-platform-tests/wpt/issues/42823, which @jgraham has a pending PR for (https://github.com/web-platform-tests/wpt/pull/42839).
Adding
--properties-file metadata/update-properties.json
made it work, so presumably it isn't using that path by default?
I suppose I should file a different bug for this.
Is there any work remaining on this issue? Or should we close it?
Per the docs, https://web-platform-tests.org/tools/wptrunner/docs/expectation.html, we should be using
metadata/update-properties.json
as the metadata update properties?