Skip to content

fix lint and require issues causing 'bin/rake ci' to fail #268

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

Merged
merged 1 commit into from
Apr 20, 2016

Conversation

thewoolleyman
Copy link
Contributor

This change is Reviewable

@thewoolleyman thewoolleyman force-pushed the fix-rake-ci-failures branch from 815c91f to 5429563 Compare April 6, 2016 13:25
@thewoolleyman
Copy link
Contributor Author

I don't know why these didn't fail on travis CI, but they failed for me locally.

@@ -28,7 +28,7 @@ describe('CommentList', () => {
id: 2,
author: 'Furter',
text: 'ho',
}),
})
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think we're supposed to have a trailing comma.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The linter failed on the trailing comma when I ran locally, with latest code, with just a bundle and npm install and rake ci. If it doesn't for you or on travis, then there's something non-deterministic that is bleeding in from those environments or mine, and that should be locked down / prevented. I didn't dig into why, I just made this change and the linter passed.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@thewoolleyman in some cases, we tried using docker for linting. I don't like that it as it doesn't seem to lock down the linter versions.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

OK, this one isnlt failing any more against master, but the other one is. I've removed this change.

@thewoolleyman thewoolleyman force-pushed the fix-rake-ci-failures branch from 5429563 to bd283b2 Compare April 7, 2016 03:32
@justin808
Copy link
Member

:lgtm:


Reviewed 1 of 2 files at r1, 1 of 1 files at r2.
Review status: all files reviewed at latest revision, all discussions resolved.


Comments from Reviewable

@justin808
Copy link
Member

@thewoolleyman can you rebase this on top of master?

@thewoolleyman
Copy link
Contributor Author

@justin808 Rebased and pushed...

@justin808
Copy link
Member

:lgtm:


Reviewed 1 of 1 files at r3.
Review status: all files reviewed at latest revision, all discussions resolved.


Comments from Reviewable

@justin808 justin808 merged commit e2ca7e0 into master Apr 20, 2016
@justin808 justin808 deleted the fix-rake-ci-failures branch April 20, 2016 17:28
@justin808
Copy link
Member

Thanks @thewoolleyman


Review status: :shipit: all files reviewed at latest revision, all discussions resolved, all commit checks successful.


Comments from Reviewable

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants