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

Stable versions are broken #3842

Closed
agjohnson opened this issue Mar 24, 2018 · 10 comments
Closed

Stable versions are broken #3842

agjohnson opened this issue Mar 24, 2018 · 10 comments
Labels
Bug A bug Priority: high High priority

Comments

@agjohnson
Copy link
Contributor

For instance: http://readthedocs.org/projects/docs/builds/6938938/

@agjohnson agjohnson added Priority: high High priority Bug A bug labels Mar 24, 2018
@agjohnson agjohnson added this to the Build stability milestone Mar 24, 2018
@stsewd
Copy link
Member

stsewd commented Mar 24, 2018

Related issues #3837

@humitos
Copy link
Member

humitos commented Mar 24, 2018

Previous stable passing is this one: http://readthedocs.org/projects/docs/builds/6933018/

Note that the only difference is that now the git checkout command is adding the origin/ to the commit. Guessing, I would say that maybe some output has changed between Git 1.9 and Git 2.7.4 that was upgraded with the Ubuntu upgrade (a couple of days ago). Not sure, anyway.

@stsewd
Copy link
Member

stsewd commented Mar 24, 2018

@humitos I think it is due the git upgrade, on my local instance I can't reproduce this. But the checkout commands are different

screenshot-2018-3-24 cice-consortium cice read the docs
screenshot-2018-3-23 test-build read the docs

@stsewd
Copy link
Member

stsewd commented Mar 24, 2018

Now I was able to reproduce this on my local instance with this project https://github.com/irmen/Pyro4

screenshot-2018-3-23 pyoro read the docs

@stsewd
Copy link
Member

stsewd commented Mar 24, 2018

Found it!

The error is here

https://github.com/rtfd/readthedocs.org/blob/f3c0c0aa33c6017951b900e540d61ef36ea71d4e/readthedocs/vcs_support/backends/git.py#L250-L252

https://github.com/rtfd/readthedocs.org/blob/f3c0c0aa33c6017951b900e540d61ef36ea71d4e/readthedocs/vcs_support/backends/git.py#L256-L258

This is because before code was the original exit_code of the command, but after #3831(I think) the original exit_code is losed. This is something I was wondering while writing tests on #3764 (comment)

@stsewd
Copy link
Member

stsewd commented Mar 24, 2018

So, probably other places that rely on the original exit_code are going to be in trouble...

@agjohnson
Copy link
Contributor Author

@stsewd great find! i think you're right

@humitos
Copy link
Member

humitos commented Mar 26, 2018

Just a note for next week.

We should be careful with all the record_as_success that use the exit code to decide something.

@agjohnson
Copy link
Contributor Author

Tags and stable are working again. Closing.

@stsewd
Copy link
Member

stsewd commented Mar 29, 2018

@agjohnson other projects still has this issue, can be tracked on #3837 anyway.

agjohnson added a commit that referenced this issue Mar 29, 2018
* Use gitpython to find a commit reference

Fixes #3842

* Add more exception handling

* Fix issue with a merge
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Bug A bug Priority: high High priority
Projects
None yet
Development

No branches or pull requests

3 participants