Publish the feature-level interop CSVs - #297
Open
yulunwu2 wants to merge 1 commit into
Open
Conversation
yulunwu2
force-pushed
the
feature-interop-publish
branch
from
September 3, 2026 23:50
e00b8ff to
80272e7
Compare
yulunwu2
force-pushed
the
feature-interop-publish
branch
from
September 4, 2026 00:02
80272e7 to
cf73522
Compare
yulunwu2
force-pushed
the
feature-interop-publish
branch
from
September 4, 2026 00:33
cf73522 to
526a167
Compare
yulunwu2
force-pushed
the
feature-interop-publish
branch
2 times, most recently
from
September 4, 2026 04:06
79f92a4 to
346ecee
Compare
yulunwu2
force-pushed
the
feature-interop-publish
branch
from
September 4, 2026 04:20
346ecee to
fcea4ff
Compare
DanielRyanSmith
left a comment
DanielRyanSmith
left a comment
Contributor
There was a problem hiding this comment.
The PR description seems to be inaccurate
build.sh scores both channels, seeding each from the master already on gh-pages. The deploy no longer wipes gh-pages first, so the per-date detail files earlier builds published survive.
Nothing seems to be seeded from gh-pages, and we're re-scoring runs without looking at previously scored runs. However, this is intended at the moment, right? If we're following the same paradigm as how interop scores are aggregated today
yulunwu2
force-pushed
the
feature-interop-publish
branch
from
September 8, 2026 17:43
fcea4ff to
10b9000
Compare
yulunwu2
force-pushed
the
feature-interop-publish
branch
from
September 8, 2026 18:14
10b9000 to
8b4bc9d
Compare
build.sh now scores both channels, from the date the web features catalogue settled. Every build rescores the whole range and writes every CSV from scratch, as the browser-specific-failures scoring above it does, so nothing depends on what a previous build published.
yulunwu2
force-pushed
the
feature-interop-publish
branch
from
September 8, 2026 18:19
8b4bc9d to
1538daa
Compare
Contributor
Author
|
@DanielRyanSmith the commit message was stale, sorry about that! |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
build.sh now scores both channels, from the date the web features catalogue
settled. Every build rescores the whole range and writes every CSV from
scratch, as the browser-specific-failures scoring above it does, so nothing
depends on what a previous build published.