Skip to content

Conversation

@yyscamper
Copy link
Contributor

Fix the annoying Hound CI false alarm for undefined variables by adding those variables into the jshint "predef" tables. (previous jshint "globals" options doesn't work well for houndci, but I tested "predef" works well, see my test PR: yyscamper/on-tasks#10)

However, by introducing this change, there will be a new false alarm emerges:

Redefinition of '_'

This is caused by you use lodash not via injectable table but directly by require('lodash').
This false alarm usually only happens in "index.js", so it is rare to happen.

@RackHD/corecommitters @WangWinson @iceiilin

@yyscamper
Copy link
Contributor Author

Wondering why houndci report error parsing config for jshint only in on-core repo, the same config file in other repos don't have such error.

Copy link
Member

Choose a reason for hiding this comment

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

why remove 'files"?

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 files is not referenced anywhere, there will be houndci warning.

@JenkinsRHD
Copy link
Contributor

*** BUILD #89 ***

@anhou
Copy link
Member

anhou commented Jan 21, 2016

@yyscamper please fix the houndci

@yyscamper yyscamper force-pushed the fix-houndci branch 2 times, most recently from 2b1644d to 50462d4 Compare January 21, 2016 05:33
@yyscamper
Copy link
Contributor Author

@anhou I tried to fix the houndci error "Error parsing config for: jshint" but failed, I don't know why the houndci reports some error as I uses the same .jshintrc and .hound.ym with other repos (expect on-http), but those repos doesn't have such error.

I guess this may be houndci false alarm, but cannot make sure.

@benbp any idea for this?

@JenkinsRHD
Copy link
Contributor

*** BUILD #91 ***

@yyscamper
Copy link
Contributor Author

I enabled the houndci in my forked repo, I tested not change the .jshintrc, only copy an unitest file, it shows the houndci still complains "Error parsing config for: jshint", please checked this PR:
yyscamper#2, so it proves it's not my change introduces the houndci complain.

I guess maybe it is the file format problem (dos file / linux file/...), so I find a tool compared the .hound.yml and .jshintrc with the ones in on-tasks repo in binary level per byte, the tool shows they are exactly the same file even per byte.

@yyscamper
Copy link
Contributor Author

I finally resolved it, I reverted my change to spec/lib/common/file-loader-spec.js and keep this PR only change the .jshintrc, now houndci becomes work well. Wow!!

houndci is a strange and naughty robot !

@anhou
Copy link
Member

anhou commented Jan 21, 2016

@yyscamper Thanks, 👍

@iceiilin
Copy link
Member

+1

yyscamper added a commit that referenced this pull request Jan 21, 2016
fix houndci false alarm about undefined variable
@yyscamper yyscamper merged commit bbfcd72 into RackHD:master Jan 21, 2016
dalebremner pushed a commit to dalebremner/on-core that referenced this pull request Dec 1, 2017
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.

4 participants