-
-
Notifications
You must be signed in to change notification settings - Fork 37.1k
Submitting WPT results to wpt.fyi for comparison #46443
Copy link
Copy link
Closed
Labels
metaIssues and PRs related to the general management of the project.Issues and PRs related to the general management of the project.testIssues and PRs related to Node.js core tests and test infrastructure.Issues and PRs related to Node.js core tests and test infrastructure.
Description
Activity
Metadata
Metadata
Assignees
Labels
metaIssues and PRs related to the general management of the project.Issues and PRs related to the general management of the project.testIssues and PRs related to Node.js core tests and test infrastructure.Issues and PRs related to Node.js core tests and test infrastructure.
Is there interest in adding Node.js to the list of products that wpt.fyi supports displaying results and comparisons for?
If I understood the task right, it would require a daily CI job which checks out the WPT tests using a branch name that the wpt repo pushes to on a daily schedule, called
epochs/daily, executing our WPT runner, collecting its results, transforming and submitting them to the wpt.fyi together with metadata about the used Node.js version.This would be done in a matrix for all maintained release lines which wpt.fyi calls stable channels, plus one for the experimental channel which would be our
mainbranch checkout. So the job would e.g. checkout node's v18.x branch HEAD~1, updated the checked out WPTs toepochs/daily, ran the WPTs, transformed the results and submitted them.To submit the results we'd request an identifier/username to be created in the wpt.fyi API, an API key for that username would be given to us to be stored as a Github Actions Repository Secret.
We would still only be running the WPT suites we have an existing checkout for.
Example how Deno has their results submitted