-
Notifications
You must be signed in to change notification settings - Fork 446
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
feat(lint): migrate lint command #4732
Conversation
The spread linter test failed due to |
1627106
to
b0d718a
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Code looks great but I'm not sure what we should do with error: snap "core24" is not available on stable
It's probably not worth our time to add a workaround since core24
will be on stable later this month.
What do you think about an xfail
style check in the core24
linter spread test? The spread test would pass if error: snap "core24" is not available on stable
is in the logs.
b0d718a
to
c7f3510
Compare
1e70929
to
a11cd29
Compare
a11cd29
to
d515d93
Compare
2 workarounds, install edge |
d515d93
to
04f22bc
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks great and the commits are nicely organized.
04f22bc
to
18f1fdd
Compare
I'll re-address the core24 linter spread test after core24 is stable. |
Same logic from core22.
2 workarounds, install edge
core24
if stable failed and check only part of the linter warning due to glibcundefined symbol
in bash.