Skip to content

Build failure for PyWWT #5133

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
astrofrog opened this issue Jan 20, 2019 · 4 comments
Closed

Build failure for PyWWT #5133

astrofrog opened this issue Jan 20, 2019 · 4 comments
Labels
Needed: replication Bug replication is required Support Support question

Comments

@astrofrog
Copy link

Today I noticed that the build for the 'pywwt' project is failing just after the git clean step, and I get the message:

There was a problem with Read the Docs while building your documentation. Please try again later. However, if this problem persists, please report this to us with your build id (8419772).

The full log is:

Read the Docs build information
Build id: 8419772
Project: pywwt
Version: latest
Commit: c08bdbf37f31e7c6dca970443c73ec6b64d37fab
Date: 2019-01-20T09:16:03.519773Z
State: finished
Success: False


[rtd-command-info] start-time: 2019-01-20T09:16:03.909211Z, end-time: 2019-01-20T09:16:05.439721Z, duration: 1, exit-code: 0
git clone --no-single-branch --depth 50 https://github.com/WorldWideTelescope/pywwt .
Cloning into '.'...

[rtd-command-info] start-time: 2019-01-20T09:16:05.674727Z, end-time: 2019-01-20T09:16:05.748276Z, duration: 0, exit-code: 0
git checkout --force origin/master
Note: checking out 'origin/master'.

You are in 'detached HEAD' state. You can look around, make experimental
changes and commit them, and you can discard any commits you make in this
state without impacting any branches by performing another checkout.

If you want to create a new branch to retain commits you create, you may
do so (now or later) by using -b with the checkout command again. Example:

  git checkout -b <new-branch-name>

HEAD is now at c08bdbf Added release date for v0.5.3

[rtd-command-info] start-time: 2019-01-20T09:16:05.807591Z, end-time: 2019-01-20T09:16:05.816593Z, duration: 0, exit-code: 0
git clean -d -f -f

What could be going wrong?

@humitos
Copy link
Member

humitos commented Jan 20, 2019

Hi! This is what I see in the logs:

Gitmodule path 'astropy_helpers' did not exist in revision of parent commit HEAD
"Blob or Tree named 'astropy_helpers' not found"

Maybe that helps you to fix it. I can go back to this during the week, maybe.

(if the submodule exists, maybe a wipe fixes the problem)

@humitos humitos added Support Support question Needed: replication Bug replication is required labels Jan 20, 2019
@astrofrog
Copy link
Author

@humitos - that helped, thanks! Basically our package had a .gitmodules file but no submodule checked out in the repository. I'm not sure why this didn't come up as an issue before though, but it was definitely a problem on our side.

@humitos
Copy link
Member

humitos commented Jan 20, 2019

We were communicating similar errors in a friendly user way on build details page, so probably there is a regression here.

@stsewd
Copy link
Member

stsewd commented Jan 20, 2019

@humitos the submodules issue is still open #4371 and I'm working in submitting a patch in gitpython

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Needed: replication Bug replication is required Support Support question
Projects
None yet
Development

No branches or pull requests

3 participants