Readthedocs.org: Build 828171 is failing

Created on 2 Mar 2018  路  5Comments  路  Source: readthedocs/readthedocs.org

Details

Expected Result

Build success for stable for the latest tag release v1.37 on Github

A description of what you wanted to happen

Actual Result

Build failed due to wrong version

A description of what actually happened

The stable version is still pointing to an old commit which did not fix the build.

3279 should fix it.

Background

We did a migration of the Github link from:
https://github.com/jacquev6/PyGithub to https://github.com/PyGithub/PyGithub

replication Support

Most helpful comment

You have two different things happening here:

  1. The error reported by RTD is
  File "conf.py", line 324, in <module>
    assert method is None or (githubClass, method) in [("github.StatsPunchCard.StatsPunchCard", "get")], githubClass + "." + method + " has no :calls: section"
AssertionError: github.PullRequestReviewerRequest.PullRequestReviewerRequest.__repr__ has no :calls: section

Which is related to your own project, not RTD.

  1. v1.37 is not being selected as stable version automatically. I'd say that this is not related to #3279 because it should be automatically by RTD since it's the general rule and that issue linked is to skip that general rule for some other consideration. Anyway, in this case I think that you don't need to skip that rule, but you need that rule to work properly in your RTD project instead :)

All 5 comments

You have two different things happening here:

  1. The error reported by RTD is
  File "conf.py", line 324, in <module>
    assert method is None or (githubClass, method) in [("github.StatsPunchCard.StatsPunchCard", "get")], githubClass + "." + method + " has no :calls: section"
AssertionError: github.PullRequestReviewerRequest.PullRequestReviewerRequest.__repr__ has no :calls: section

Which is related to your own project, not RTD.

  1. v1.37 is not being selected as stable version automatically. I'd say that this is not related to #3279 because it should be automatically by RTD since it's the general rule and that issue linked is to skip that general rule for some other consideration. Anyway, in this case I think that you don't need to skip that rule, but you need that rule to work properly in your RTD project instead :)

@humitos Thank you very much for your response

  1. I am aware and this is already fixed in master, but as I said in the description the reason is because stable is pointing to the wrong sha, if it's pointing to master or 1.37 this failure should not appear.

  2. Okay, what is the solution then?

@sfdye I import your project on my local instance, the sha for stable match the one from v1.37

screenshot-2018-3-8 versions read the docs

This seems related to #3729. The user took an _extreme step_ to solve the issue https://github.com/rtfd/readthedocs.org/issues/3729#issuecomment-370644289

I'm markng this a Needed: replication since it seems that we have a bug on our selection of the stable that it would be great to research a little more, but I'm not able to reproduce it.

I finally get it working by deleting the project on rtd and importing again, thanks to advice from @stsewd . Don't think it's worth the effort to investigate and reproduce though, thus closing the issue. Re-open if anyone interested to dig in deeper.

Was this page helpful?
0 / 5 - 0 ratings

Related issues

adamjstewart picture adamjstewart  路  4Comments

PowerKiKi picture PowerKiKi  路  4Comments

dxgldotorg picture dxgldotorg  路  3Comments

jaraco picture jaraco  路  4Comments

davidism picture davidism  路  4Comments