Lint is failing on css/css-fonts/cascading-font-sizes.html

[foolip]

Added in 8e05b11 and somehow got past Travis.

[foolip]

Noticed because https://ci.chromium.org/buildbot/chromium.infra.cron/wpt-importer/ is failing. (It runs the lint before uploading the changes to Chromium code review.)

[foolip]

It looks like there is no recent PR which brought in these changes, which would explain why Travis has not run. Trying to figure out how they ended up on master...

[foolip]

Hmm, so a02f1bc is the topmost commit on master, and as a self-contained commit that seems to make sense. But its parent commit was a merge commit, a backwards one which would have results from git pull. So probably this was an attempt to push a branch to create a PR, that went wrong because of the tracking branch being origin/master, so something like that.

But why was it possible to push to master accidentally? @svgeesus, are you an admin of the repo indirectly, by any chance?

[foolip]

Anyway, a02f1bc and the commits merged by 63c87e5 together account for the changes. The merge commit appears to have been accidental, so I'll revert that while leaving a02f1bc alone, let's say I've reviewed it.

[Hexcles]

Thanks for fixing this!

[gsnedders]

I've asked @svgeesus not to push directly to master before, as it isn't the first time he's caused lint failures that couldn't have landed had they gone through CI. :(

[svgeesus]

Apologies for causing trouble.

Hmm, so a02f1bc is the topmost commit on master, and as a self-contained commit that seems to make sense.

Yes, that is the one I was trying to commit. I didn't ask for review because the substance of the tests had not changed (just the spec link was bumped from Fonts 3 to Fonts 4, as that section of the spec was deferred to level 4).

I will do PR from now on, so that Travis CI can run.