random ENOTEMPTY in Travis run #933
Comments
|
@nexik - Did you ever figure out what this was? I'm having the same issue. |
|
@nexik @mattvv I'm having the same issue as well. Is there still no talk of a solution for this? |
|
unfortunatelly no, my team is no longer using travis as CI server. There were more weird problems in Travis Pro so we are migrating. I'll leave issue as open because I see other devs have the same problem. |
|
Looks like a collision in the bower temp directory. I added this to my .bowerrc to change the bower directories to be local to my project directory. The tmp is probably the most important one, but figured it couldn't hurt to make the others local also. |
|
I'm getting this error in my CircleCI test runs. |
|
Having the same problem in our Jenkins setup adding |
|
+1 - same for me. |
|
can anyone confirm |
|
@joscha This is what my .bowerrc looks like. {
"directory": "vendor/assets/components",
"json": "config/bower.json",
"storage": {
"packages": ".bower-cache",
"registry": ".bower-registry"
},
"tmp": ".bower-tmp"
}The relevant lines being the |
|
@jacortinas Thanks, I just reused a shared dir: {
"storage": {
"packages": ".bower/cache",
"registry": ".bower/registry"
},
"tmp": ".bower/tmp"
} |
|
Unfortunately, I still get this error even with custom cache, registry and tmp folders |
|
ENOTEMPTY error still occurs even with custom local cache, registry and tmp folders. This error also isn't only with Angular. We also get it with jQuery. This is breaking some of our Continuous Integration builds, is making CI unreliable, which means teams can't trust it. It would be much appreciated to have an eye on this from the bower team. |
|
Same issue on jenkins build server: |
|
I'm hitting this, please fix |
|
I'm getting a similar error |
|
I ran -- Seems that angular 1.2.6 is resolving to install all versions of angular? |
|
+1 same issue. If it helps anyone with their struggles, I did: bower cache clean Worked for me, where bower install was consistently failing. Hopefully fixed soon! |
|
Also seeing this on Heroku deploys. I have tried
Seems to get stuck on handlebars for me. |
|
For me the fix with the different temp folder seems to have done the trick on our Jenkins build environment: { |
|
+1 bower cache clean fixed it for me. my error was with a angular related package |
|
Yeah |
|
I've tried everything and my build gets stuck every time. Please, help! |
… root in an attempt to fix ENOENT/ENOTEMPTY errors with heroku deployment. Reference: bower/bower#933
|
Hello, I can say that the The problem does seems to happens when multiple bower install are run. One thing to note is that it seems to only happen with the angular project. |
|
We've seen jquery fail.
|
|
👏 Now we can start getting our builds out the door! |
We need at least version 1.3.2 to avoid a race condition: bower/bower#1211 bower/bower#933 https://www.openproject.org/work_packages/5645 Signed-off-by: Alex Coles <alex@alexbcoles.com>
nexik
changed the title
|
I got following error while running grunt-google-cdn: |
|
Same here, I'm not doing anything fancy Also encountering |
|
@quentindemetz Please make sure you're using bower 1.3.3 which fixes those issues. Also it's possible that other users on Travis instance are using 1.3.2 which would make your build fail. |
|
can not install bower... sad |
|
@lokielse This is completely unrelated issue. Please notify npm team about this. |
|
I have this errors also with 1.3.3. |
|
@cebor have you fully cleaned the cache? I've got a sneaking suspicion that the people who are still having issues, even after upgrading to 1.3.3, either have old badly permissioned cache directories (did you accidentally run as root one time?) or as @sheerun guessed, someone else on the same box running <= 1.3.2 |
|
yes i cleared bower and npm cache several times, the problem occurs randomly. |
|
If you clear bower cache, you're breaking other people builds. They clear cache and they break yours. I guess for now solution would be to pass |
|
@sheerun I dont have this problem on Travis, only locally when i'm building a page with generator-angular (master version) @ the google-cdnify Task |
|
Ok i think i fixed it: changing all angular versions in bower.json: |
|
@cebor Could you post |
|
bower.json: https://gist.github.com/cebor/5890f5bd58a8e4e6ae6e Error @ Update: The conflicting bower package was always Bower version: 1.3.3 |
|
👍 |
|
I could install all packages in my Node project without -g parameter. And that causes the issue for me. Same issue you are all describing. So i reinstallt bower with -g and all is working fine for me |
|
This thread got really messy. If someone still experiences any issues, please open another issues with steps to reproduce. Thank you! |
and others
I use this command to install bower in travis
randomly I get this error:
The text was updated successfully, but these errors were encountered: