-
-
Notifications
You must be signed in to change notification settings - Fork 3.6k
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
Unable to switch latest from master
to main
and build successfully
#11321
Comments
I took a quick look at this and it seems that AutoAPI is ignoring all the Python files on the build that fails. Example:
and
It seems that's the problem. Maybe there is a Sphinx configuration that needs to be changed? |
@humitos thanks for your reply. I'm not sure I understand why a sphinx change would be necessary if the build already succeeds when it's pointed directly to |
@kevingreenman No, I'm not sure what it could be 🤷🏼 . The only differences that I found taking a look at the logs was that reading/ignoring coming from Sphinx. |
@kevingreenman As @humitos noted, this seems to be a Sphinx configuration issue with your project. If you inspect the raw logs between the two builds, you'll see that the build on version I found the following in your configuration: autoapi_ignore = ["*test*", "*cli*"] https://beta.readthedocs.org/projects/chemprop/builds/24434895/#231043343--42 This pattern match is too open, it will match a path with any instance of the string Hopefully that points you in the right direction. I'll close this issue as it is not an issue with Read the Docs but is instead a content issue. |
@agjohnson thank you! This was fixed in our most recent build by changing from |
I had posted this in a comment in a closed issue a couple weeks ago, but decided to open a separate issue because I think it might be a different problem than what others were facing in #7907
I'm having an issue with this while using RTD with the chemprop package. Chemprop has been on RTD for several years and has previously always had
master
as its primary branch. In the RTD settings, the default branch was never set (it said---------
and thus pointed to the default ofmaster
).We recently released a new version of chemprop that we had been developing on our
v2/dev
branch, which was also active as a version on RTD. When we were ready to release our new stable version, we renamedv2/dev
tomain
and then changed our primary branch in our GitHub repo settings frommaster
tomain
. On RTD, I deactivated thev2/dev
version and changed the default branch from---------
tomain
. The latest build now fails.The error we're seeing is
I created a new RTD version that points directly to
main
, and that build succeeds, even though the code is exactly the same as for thelatest
version.We're also tracking this in our own issue: chemprop/chemprop#828
Originally posted by @kevingreenman in #7907 (comment)
The text was updated successfully, but these errors were encountered: