If you do not write or review web platform tests, you can skip this email.
Hello blink-dev,
TL;DR: There are .ini files under web_tests/external/wpt/ and web_tests/wpt_internal/ you can ignore for now.
What are these files?
These files were added as part of an ongoing project to run web platform tests in Chromium CQ/CI with wptrunner, the harness that ships with web-platform-tests/wpt.
Like baselines and TestExpectations, each .ini file corresponds to a test and contains expectation data in the structured format wptrunner natively understands. web-platform-tests.org and the Chromium wptrunner user guide document the file format (named “WPT metadata”).
Do I need to update metadata files when making a change?
No, although these files are safe to add, modify, or remove. The WPT importer will use try build results to keep these files up-to-date automatically. These files are not upstreamed to the GitHub repository.
Do I still need to rebaseline or add TestExpectations for web platform tests?
Yes. Because CQ and sheriffed CI still use run_web_tests.py, not wptrunner, the workflow for landing web platform tests in chromium/src has not changed.
Thanks,
Jonathan (on behalf of Blink EngProd)