search

Strider-CD / strider

Open Source Continuous Integration & Deployment Server
http://strider-cd.github.io/
4.6k stars 432 forks source link

Worker stuck after test #188

Closed refack closed 10 years ago

refack commented 11 years ago

Last heard from:

←[39m: Done with phase test null ←[39m: done with sh [ '-c', 'npm test --color always' ] 0 ←[39m: Running phase deploy A the whole dyno is stuck.

What other info should I provide.

jaredly commented 11 years ago

:( hmm. Are you deploying to heroku or somewhere else? Do you have any custom deploy setup?

Jared

On Mon, Sep 16, 2013 at 3:11 PM, Refael Ackermann notifications@github.comwrote:

Last heard from:

←[39m: Done with phase test null ←[39m: done with sh [ '-c', 'npm test --color always' ] 0 ←[39m: Running phase deploy A the whole dyno is stuck.

What other info should I provide.

— Reply to this email directly or view it on GitHubhttps://github.com/Strider-CD/strider/issues/188 .

refack commented 11 years ago

Nope. Plain vanilla to heroku. It used to work up until a few days ago.

jaredly commented 11 years ago

What strider version are you running? Is this within docker or via NPM or the git repo?

refack commented 11 years ago

Tip of the git running on heroku, with one modification; I added npm to the package.json dependencies

jaredly commented 11 years ago

Also: you say "the whole dyno is stuck". Does the website still work, or is it totally hanging? "stuck jobs" are supposed to be cleared up after 10 minutes of inactivity.

On Wed, Sep 18, 2013 at 4:43 AM, Refael Ackermann notifications@github.comwrote:

Tip of the git running on heroku, with one modification; I added npm to the package.json dependencies

— Reply to this email directly or view it on GitHubhttps://github.com/Strider-CD/strider/issues/188#issuecomment-24655394 .

refack commented 11 years ago

The website is working, but no other jobs seems to even start. After 10 minutes I see the "job cleared" message, but no other job will work until I manually restart the dyno (heroku restart).

niallo commented 11 years ago

@refack: can you try 1.3.5 (latest stable) on heroku? want to try to figure out when this broke. also, what happens if you don't add npm to package.json?

some things with plugins did change in HEAD and it's possible this impacted heroku somehow. @jaredly have you tried HEAD on heroku at all?

jaredly commented 11 years ago

Not recently/

On Wed, Sep 18, 2013 at 3:43 PM, niallo notifications@github.com wrote:

@refack https://github.com/refack: can you try 1.3.5 (latest stable) on heroku? want to try to figure out when this broke. also, what happens if you don't add npm to package.json?

some things with plugins did change in HEAD and it's possible this impacted heroku somehow. @jaredly https://github.com/jaredly have you tried HEAD on heroku at all?

— Reply to this email directly or view it on GitHubhttps://github.com/Strider-CD/strider/issues/188#issuecomment-24701983 .

niallo commented 11 years ago

Yeah, sadly Heroku is a weird non-POSIX environment and I don't actively use it for anything. We need contributors who really care about it to help maintain Strider support for running on Heroku.

@refack any interest in helping us keep Strider stable on Heroku? :-)

jaredly commented 11 years ago

If we just have a stronger test suite, we can run it on heroku and probably catch things like this.

On Wed, Sep 18, 2013 at 5:00 PM, niallo notifications@github.com wrote:

Yeah, sadly Heroku is a weird non-POSIX environment and I don't actively use it for anything. We need contributors who really care about it to help maintain Strider support for running on Heroku.

@refack https://github.com/refack any interest in helping us keep Strider stable on Heroku? :-)

— Reply to this email directly or view it on GitHubhttps://github.com/Strider-CD/strider/issues/188#issuecomment-24706258 .

niallo commented 11 years ago

Yep. We need some integration tests. I'm going to open an issue :)

jaredly commented 10 years ago

Also: the heroku plugin will provide live updates to the console, as opposed to waiting until it has completed; so we'll have a better idea of what's going on.

niallo commented 10 years ago

Please try again in master and re-open if still broken.