-
Notifications
You must be signed in to change notification settings - Fork 3.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Lint can regress on master because CSS-COLLIDING-* lints don't get all paths #9171
Comments
gsnedders
added a commit
to gsnedders/web-platform-tests
that referenced
this issue
Jan 24, 2018
This gets rid of the CSS-COLLIDING-SUPPORT-NAME failure on master from 1f69b42 (see web-platform-tests#9171 for how that landed)
This was referenced Jan 24, 2018
One obvious solution could just be to make |
Hello, I could not replicate this error. Thank you |
belaeifert
added a commit
to belaeifert/web-platform-tests
that referenced
this issue
Mar 8, 2018
This was referenced Aug 8, 2018
This was referenced Oct 2, 2018
Downgrading this as #13311 should mean we don't land cases where it regresses (though it'll still show up locally, which still isn't great!). |
This really is just a special case of #10021? |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
This seems to have started failing with 1f69b42 from #9089 (where CI passed, including lint).
The underlying cause of this is that in CI we call lint with only the changed paths, and the CSS-COLLIDING-* lints need to know all filenames to consider whether they collide or not.
cc/ @jgraham
The text was updated successfully, but these errors were encountered: