Repository navigation
Broken build: bower install dies prematurely #3648
Description
I followed the instructions listed at the guidelines for contributing and for setting up my environment.
I'm unable to build or test angular.
Building issues
This seems to center mostly on the fact I don't have the google closure compiler installed in the proper spot.
when I run:
grunt package
I get the following: (it seems to make the "full" files, but it aborts while creating the minified files)
npm WARN package.json [email protected] No repository field.
npm WARN package.json [email protected] No repository field.
npm WARN package.json [email protected] No repository field.
npm WARN package.json [email protected] No repository field.
npm WARN package.json [email protected] devDependences should probably be devDependencies.
npm WARN package.json [email protected] No repository field.
npm WARN package.json [email protected] No repository field.
npm WARN package.json [email protected] No repository field.
npm WARN package.json [email protected] No repository field.
npm WARN package.json [email protected] 'repositories' (plural) Not supported.
npm WARN package.json Please pick one as the 'repository' field
npm WARN package.json [email protected] No repository field.
npm WARN package.json [email protected] No repository field.
npm WARN package.json [email protected] No repository field.
Running "shell:bower" (shell) taskRunning "clean:build" (clean) task
Cleaning "build"...OKRunning "buildall" task
File build/angular-scenario.js created.
File build/angular.js created.
File build/angular-loader.js created.
File build/angular-mobile.js created.
File build/angular-mocks.js created.
File build/angular-sanitize.js created.
File build/angular-resource.js created.
File build/angular-route.js created.
File build/angular-cookies.js created.Running "minall" task
Error: Unable to access jarfile components/closure-compiler/compiler.jar
Error: Unable to access jarfile components/closure-compiler/compiler.jar
Warning: Error minifying build/angular.js Use --force to continue.Aborted due to warnings.
Testing issues
If I run:
grunt test:unit
The output is as follows:
[2013-08-18 20:11:08.972] [DEBUG] config - autoWatch set to false, because of > > singleRun
INFO [karma]: Karma server started at http://localhost:9876/
INFO [launcher]: Starting browser Chrome
WARN [watcher]: Pattern "C:/Git/angular.js/components/jquery/jquery.js" does not match any file.
WARN [watcher]: All files matched by "C:/Git/angular.js/test/ngScenario/jstd-scenario-adapter/*.js" were excluded.
INFO [Chrome 28.0 (Windows)]: Connected on socket id 5OrjI9y4oLFkFN6J6TVL
Chrome 28.0 (Windows) ERROR
Uncaught ReferenceError: jQuery is not defined
at C:/Git/angular.js/test/jquery_remove.js:3
Chrome 28.0 (Windows): Executed 0 of 0 ERROR (1.056 secs / 0 secs)
Warning: Test(s) failed Use --force to continue.Aborted due to warnings.
I'm sure I'm just doing something wrong. I'd just like some guidance. I'd love to contribute.
Activity
benlesh commentedon Aug 19, 2013
Also, I apologize if this is the wrong place for an issue with the build.
benlesh commentedon Aug 19, 2013
A few things I found:
runs into an issue where the URL for the bootstrap 2.0.2 .zip file is no longer valid, resulting in a 404. Since this happens before the closure compiler dependency is updated, it never installs the closure compiler. So that's one thing. If you update that URL in bower.json to
"bootstrap": "https://github.com/twbs/bootstrap/archive/v2.0.2.zip",it gets past that.... then when I did a
bower installI got further, but I had an issue with "process.nextTick detected" in an infinite loop that originates from a dependency in bower called "tmp".IgorMinar commentedon Aug 23, 2013
it sounds like you are working off of an old branch or your master branch is very outdated.
we don't use shell:bower to do
bower installany more, but the issue you are describing is something we see on Travis and can't reproduce anywhere else!Can you please provide information about your environment? Mainly OS + node version.
I'm really intrigued about your "process.nextTick detected" comment, can you please provide more information about this? I suspected that the issue is bower specific (or something coming via bower dependencies) as well as that it has something to do with the event loop, but could never reproduce this on a machine that would allow me to confirm my suspicion.
cc: @btford @vojtajina @chirayuk
IgorMinar commentedon Aug 23, 2013
We initially field an issue with Travis travis-ci/travis-ci#1293 because that was the only place where we could see the bug manifest but I'm growing more and more convinced that it has nothing to do with Travis but is rather a node/bower/bower-dependency specific issue
IgorMinar commentedon Aug 23, 2013
this is likely unrelated, but recently I've seen several local build failures due to missing npm dependencies, as if
npm installexited prematurely too.. I'm likely wrong, but I'm adding the console output in case it is related:benlesh commentedon Aug 23, 2013
@IgorMinar thanks for the input... I'm probably not going to be able to check on this tonight, but I'll get a look at it tomorrow.
My environment is Windows 7 Ultimate and Node version is the latest as of last Sunday. I updated when I had problems.... I think that's 10.16... I think... I'll double check that when I get to my work machine as well.
IgorMinar commentedon Sep 4, 2013
we used this as a workaround for Travis: 3379eeb
benlesh commentedon Sep 4, 2013
Thanks. I'll have a look later this evening.Didn't get a chance last night, I'll try to work in time soon.