Latest repeatedly builds stale code

[jaraco]

Details

• Project URL: https://github.com/pypa/setuptools
• Build URL (if applicable):
• Read the Docs username (if applicable): jaraco

Per pypa/setuptools#604, I'm migrating the project to RTD as PyPI is dropping support for doc hosting. I've gotten access to the setuptools project, which was formerly configured for Mercurial (Bitbucket), which may be implicated in this issue.

After moving from Mercurial to Git, the project failed to build because it was missing dependencies, so I pushed this commit and reconfigured the project in RTD to use for docs/requirements.txt. The build failed, so I retried a couple of times manually building latest.

Excepted (erm, Expected) Result

As seen in the UI, latest should build the VCS default branch. In this case, it's a git repo and 'master' is configured as the default branch in Github. Therefore, it should build the aforementioned commit, which is in master.

Actual Result

Instead, the build failed:

I retried several times, but repeatedly got the same error.

[jaraco]

it seems that after waiting a few minutes and triggering another latest build, it now got the latest commit:

So while I thought maybe it was an issue with having been a Mercurial project, because I saw default here:

Apparently the issue is only a lag between when commits are pushed and when they can be pulled. Is that by design?

[jaraco]

It's happening again, now with pypa/setuptools@8fea560. I'll keep repeatedly building until I get a different response and see if I can assess how long the stale builds continue.

[jaraco]

Oh, this is interesting. It seems one build went back to a commit even older than the one that finally built before:

[jaraco]

And again

How weird.

[jaraco]

More than 6 minutes and RTD is still building pypa/setuptools@f12843c13

[jaraco]

15 minutes and it's still building one of two older commits. I'm going to take a break from this effort for now.

[jaraco]

Hours later, problem still exists.

[jaraco]

I set the branch to the default, master, and that triggered a build, which grabbed the latest tip:

[agjohnson]

I'll take a look into this, it seems I might need to go in an clean out the old project commit history.

[agjohnson]

It seems the last build did in fact complete successfully without having to alter the out of date versions:
http://readthedocs.org/projects/setuptools/builds/4068321/

Does this seem resolved?

[jaraco]

Yes, sort-of. It seems that setting the branch manually seems to have worked around the issue.

[agjohnson]

I suspect this is a matter of stale version/commit info. If it stops working, I can wipe the existing version and commit info from the project.

[jaraco]

I'll remove the branch override and see if the issue re-emerges, in which case it's worth trying a wipe to see if the project can be restored to a state that behaves as expected.

[hldh214]

Server Error

[Grummfy]

seems same as #2255

[stsewd]

@jaraco I think this is related to #3913

[agjohnson]

Closing as a duplicate, and due to lack of activity.