Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

quits with no logging #2

Open
DTrejo opened this issue Aug 30, 2012 · 8 comments
Open

quits with no logging #2

DTrejo opened this issue Aug 30, 2012 · 8 comments
Labels

Comments

@DTrejo
Copy link
Owner

DTrejo commented Aug 30, 2012

David,

Any idea why this isn't working? I get no logging.

tiny:~/voxer/server$ (release) rotten -p release
Running against /Users/kip/voxer/server
Checking that branches are in production branch release
....................................tiny:~/voxer/server$ (release)

@rv-kip

@DTrejo
Copy link
Owner Author

DTrejo commented Sep 11, 2012

@rv-kip try this with the newest version of rotten from npm? I've just updated it to print more error output. TY!

@rv-kip
Copy link

rv-kip commented Sep 11, 2012

No dice. It is worse now.

$ rotten -p release
Running against /voxer/server
Checking that branches are in production branch release

 undefined
Please report bugs to https://github.com/dtrejo/rotten, thank you.

@DTrejo
Copy link
Owner Author

DTrejo commented Sep 12, 2012

I accidentally published a broken version, would you mind doing

npm rm rotten; npm cache clean rotten; npm -g install rotten

Thank you and sorry for releasing broken code!

On Tue, Sep 11, 2012 at 4:37 PM, Kip Gebhardt notifications@github.comwrote:

No dice. It is worse now.

$ rotten -p release
Running against /voxer/server
Checking that branches are in production branch release

undefined
Please report bugs to https://github.com/dtrejo/rotten, thank you.


Reply to this email directly or view it on GitHubhttps://github.com//issues/2#issuecomment-8471809.

See my projects at dtrejo.com

@rv-kip
Copy link

rv-kip commented Sep 12, 2012

Works great! Thanks.

On Tue, Sep 11, 2012 at 8:01 PM, David Trejo notifications@github.comwrote:

I accidentally published a broken version, would you mind doing

npm rm rotten; npm cache clean rotten; npm -g install rotten

Thank you and sorry for releasing broken code!

On Tue, Sep 11, 2012 at 4:37 PM, Kip Gebhardt notifications@github.comwrote:

No dice. It is worse now.

$ rotten -p release
Running against /voxer/server
Checking that branches are in production branch release

undefined
Please report bugs to https://github.com/dtrejo/rotten, thank you.


Reply to this email directly or view it on GitHub<
https://github.com/DTrejo/rotten/issues/2#issuecomment-8471809>.

See my projects at dtrejo.com


Reply to this email directly or view it on GitHubhttps://github.com//issues/2#issuecomment-8479924.

@rv-kip
Copy link

rv-kip commented Oct 17, 2012

@DTrejo I am getting the "quit with no logging" error again

$ (release) rotten -p release
Running against /voxer/server
Checking that branches are in production branch release
..........................................................................................................................Please report bugs to https://github.com/dtrejo/rotten, thank you.

Node v0.8.7

@DTrejo
Copy link
Owner Author

DTrejo commented Oct 17, 2012

:(

Maybe I will clone the linux kernel repo and see if I can reproduce this. May be a while before I get to it though, sorry.

@DTrejo
Copy link
Owner Author

DTrejo commented Nov 27, 2012

I think I just fixed this. testing on the linux repo and then pushing.

@DTrejo
Copy link
Owner Author

DTrejo commented Nov 27, 2012

Damn... the linux repo on github at least does not have any remote branches...

Pushing an update anyway I suppose.

Please let me know if this fixes the problem kip!
(Or at least gives informative error messages).

Cheers,
D

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants