Skip to content

build fails without error #4358

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

Closed
gdementen opened this issue Jul 11, 2018 · 9 comments
Closed

build fails without error #4358

gdementen opened this issue Jul 11, 2018 · 9 comments
Labels
Support Support question

Comments

@gdementen
Copy link

Details

Expected Result

Successfully build our project documentation

Actual Result

Build failed just after "git clean" without any visible error, making it impossible to debug for us.
This is just one build in a series of failed builds: https://readthedocs.org/projects/larray/builds/

This might be related to the fact the url of the git repository of the project changed (from https://github.com/liam2/larray to https://github.com/larray-project/larray) because we have not had any successful build since the move, but we did change the project url in rtd's config.

Any help would be greatly appreciated!

PS: I tried wiping the build environment to no effect...

@stsewd stsewd added the Support Support question label Jul 11, 2018
@stsewd
Copy link
Member

stsewd commented Jul 11, 2018

I can see this error in my local instance UnicodeDecodeError: 'utf8' codec can't decode byte 0xeb in position 78: invalid continuation byte. Maybe a file with wrong encoding?

@gdementen
Copy link
Author

@stsewd Do you have any extra info you can tell me? Obviously, the filename would be best, but I guess you don't have it. But do you have the full traceback? Or at least during what shell command the error happens?

@stsewd
Copy link
Member

stsewd commented Jul 11, 2018

There isn't a traceback, just the msg error :/ I'll need to inspect with pdb to give you more details, I think later I'll have some time.

@gdementen
Copy link
Author

Thanks a lot!

@stsewd
Copy link
Member

stsewd commented Jul 11, 2018

It seems that the error happens when parsing the tags, rtd uses gitpython internally for git operations, it fails trying to recover the commit of this tag <git.TagReference "refs/tags/0.27">.

I did a git show 0.27, this is the output

tag 0.27
Tagger: Ga<EB>tan de Menten <[email protected]>
Date:   Thu Nov 30 11:40:18 2017 +0100

There is a weird invalid character in the tagger field.

@gdementen
Copy link
Author

Ah! My name causing problems again ;-). Seriously it was mangled by "git gui" which has troubles with some encodings in committer names. The strange thing is that we managed to make release 0.27 and 0.28 without problems, so this must be a relatively new problem in gitpython.

Sadly, there is nothing I can do about that now, short of rebasing and redoing that commit then force pushing but that will mess up with people who cloned our repository :(. Fixing the problem on gitpython would be the right move from me but I don't expect to have the time to do that in the near future. Anyway, thanks a lot for your great support!

@gdementen
Copy link
Author

might be related to gitpython-developers/GitPython#332

@stsewd
Copy link
Member

stsewd commented Jul 11, 2018

The strange thing is that we managed to make release 0.27 and 0.28 without problems, so this must be a relatively new problem in gitpython.

Actually, the problem may be old, we just move to gitpython recently, previously we were parsing the git tags by hand.

@stsewd
Copy link
Member

stsewd commented Jul 12, 2018

There is nothing we can do from the rtd side here, closing this as the main problem is a no-valid utf-8 character in the commit object.

@stsewd stsewd closed this as completed Jul 12, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Support Support question
Projects
None yet
Development

No branches or pull requests

2 participants