Comments (5)
I'm not sure what's going on here. Tests pass locally on both Linux and OSX.
$ nvm use 0.11
Now using node v0.11.9
stephenmathieson at 0x6D746873 in ~/work/grunt-jslint on master
$ npm test
> [email protected] test /Users/stephenmathieson/work/grunt-jslint
> make test
node test/acceptance/all.js
ok
node test/acceptance/client-server.js
ok
node test/acceptance/deprecation.js
ok
node test/acceptance/itself.js
ok
node_modules/.bin/vows \
test/*.js \
--spec
♢ validate
metadata
✓ should expose the JSLint edition
missing file
✓ should error
no directives
✓ should not error
✓ should pass an Array of issues
✓ should contain required issue properties
✓ should report at least 9 issues
shebang option
✓ should not error
✓ should pass an empty Array
unused option
✓ should not error
✓ should report at least two violations
✓ should report on unused parameters
✓ should report on unused vars
predef -> globals with directives.globals
✓ should not error
✓ should not pass violations
predef -> globals without directives.globals
✓ should not error
✓ should pass a global violation
directives: sloppy
✓ should not error
✓ should pass an empty Array
directives: white
✓ should not error
✓ should pass an empty Array
util.print: Use console.log instead
♢ reporters
standard
✓ should not have errored
✓ should return a String
checkstyle
✓ should not have errored
✓ should return a String
junit-xml
✓ should not have errored
✓ should return a String
jslint-xml
✓ should not have errored
✓ should return a String
errors-only
✓ should not have errored
✓ should return a String
outputted xml: checkstyle
✓ should not error
✓ should use the "checkstyle" namespace
✓ should contain three file nodes
✓ should contain an error node for each file
✓ each error should contain all required attributes
outputted xml: jslint
✓ should not error
✓ should use the "jslint" namespace
✓ should contain three file nodes
✓ should contain an issue node for each file
✓ each error should contain all required attributes
outputted xml: junit
✓ should not error
✓ should use the "testsuites" namespace
✓ should contain one "testsuite" node
✓ should contain the "testcase" namespace
outputted xml: junit testcases
✓ should have "valid" pseudo-classnames (package name)
✓ should have a (somewhat) unique test name
✓ each testcase should only contain one failure
✓ each failure should have a message
util.print: Use console.log instead
♢ runner
multiple files
✓ should not error
✓ should pass a report Object
✓ report should contain number of failures
✓ report should contain number of files
✓ report should contain number of files in violation
✓ report should contain a "files" object
✓ files object should contain multiple keys
✓ each key in the files object should be an Array of issues
✓ each issue contained in a file should hold all required properties
single file
✓ should not error
✓ should pass a report Object
✓ report should contain number of failures
✓ report should contain number of files
✓ report should contain number of files in violation
✓ report should contain a "files" object
✓ files object should contain multiple keys
✓ each key in the files object should be an Array of issues
✓ each issue contained in a file should hold all required properties
multiple directives
✓ should not error
✓ should pass a report Object
✓ report should contain number of failures
✓ report should contain number of files
✓ report should contain number of files in violation
✓ report should contain a "files" object
✓ files object should contain multiple keys
✓ each key in the files object should be an Array of issues
✓ each issue contained in a file should hold all required properties
single directive
✓ should not error
✓ should pass a report Object
✓ report should contain number of failures
✓ report should contain number of files
✓ report should contain number of files in violation
✓ report should contain a "files" object
✓ files object should contain multiple keys
✓ each key in the files object should be an Array of issues
✓ each issue contained in a file should hold all required properties
util.print: Use console.log instead
♢ templates
sanity
✓ should be an object
✓ should have multiple keys
✓ should contain an "errorsOnly" template
✓ should contain an "standard" template
✓ should contain an "jslint" template
✓ should contain a "checkstyle" template
✓ should contain an "junit" template
util.print: Use console.log instead
util.print: Use console.log instead
✓ OK » 91 honored (0.066s)
from grunt-jslint.
Weird. I would assume the travis environment is running under Linux.
from grunt-jslint.
Linux (Ubuntu) is fine too:
stephen@xxx:~/grunt-jslint$ cat /etc/*-release
DISTRIB_ID=Ubuntu
DISTRIB_RELEASE=12.04
DISTRIB_CODENAME=precise
DISTRIB_DESCRIPTION="Ubuntu 12.04.1 LTS"
stephen@xxx:~/grunt-jslint$ node --version
v0.11.9
stephen@xxx:~/grunt-jslint$ npm test
> [email protected] test /home/stephen/grunt-jslint
> make test
node test/acceptance/all.js
ok
node test/acceptance/client-server.js
ok
node test/acceptance/deprecation.js
ok
node test/acceptance/itself.js
ok
node_modules/.bin/vows \
test/*.js \
--spec
♢ validate
metadata
✓ should expose the JSLint edition
[ . . . ]
✓ OK » 91 honored (0.107s)
stephen@xxx:~/grunt-jslint$
from grunt-jslint.
I wonder if the travis 0.11 environment had a hiccup? I noticed that bootstrap also failed CI transiently (the other day) even though it looks good now. Closing this for now and will re-open if the next commit still fails CI
from grunt-jslint.
And indeed it was a hiccup, as travis is now happy even though nothing relevant changed.
from grunt-jslint.
Related Issues (20)
- Use node-jslint rather than a submodule HOT 9
- Passing es5 -- Not Catching Trailing Commas HOT 8
- Non-trivial exclude rules take forever to filter.
- Remove shelljs dep
- exclude array is ignored HOT 7
- Honor excludes, but use faster algorithm HOT 5
- Error: EISDIR HOT 15
- Reading and removing BOM from UTF8 file HOT 3
- Options.edition with the aboslute path didn't work HOT 7
- Changes to node-jslint HOT 3
- node-jslint will require node 0.8 HOT 1
- How to set jslint options... HOT 1
- Warning: grunt-jslint's interface has changed HOT 2
- Ignore specific warnings HOT 4
- Request - option to run custom function if JSLint fails HOT 1
- Why is this error been thrown when I run jslint using grunt to improve my code quality? HOT 2
- Exclude is not working ... HOT 14
- will it be updated? HOT 9
- array.forEach is not a function HOT 1
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from grunt-jslint.