You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Read the Docs build times out while compiling ABACUS to generate parameter documentation #8171
The available log contains no C++ compilation error. Parameter export and Sphinx had not started. The separate abacus-develop RTD check succeeded for the same commit, so the failure is not consistent across the two RTD projects.
Why documentation builds compile ABACUS
The current .readthedocs.yaml builds and installs ABACUS to generate the INPUT parameter documentation from the current code:
This makes documentation checks depend on a full executable build fitting within RTD's resource limits. ABACUS will support more abilities and the compiling time will be longer and longer.
Proposed next step
A lightweight parameter-export target, or generating the parameter documentation in GitHub Actions before rendering it on RTD.
... generating the parameter documentation in GitHub Actions before rendering it on RTD.
I tried some attempts but failed. And some of them introduce complexity to CI workflow which I think shouldn't be the case. I'm not sure how to resolve the concern in a better way.
If RTD have some mechanism like API key, it should be possible to build document in GitHub Actions and deploy it to RTD webpage.
If RTD have some mechanism like API key, it should be possible to build document in GitHub Actions and deploy it to RTD webpage.
Good news: I found it have an direct upload approach. That said, adapting to this will mean dropping the currect RTD CI-workflow entirely and requiring a READTHEDOCS_TOKEN.
Activity
Growl1234 commentedon Oct 18, 2026
I tried some attempts but failed. And some of them introduce complexity to CI workflow which I think shouldn't be the case. I'm not sure how to resolve the concern in a better way.
If RTD have some mechanism like API key, it should be possible to build document in GitHub Actions and deploy it to RTD webpage.
Growl1234 commentedon Oct 18, 2026
Good news: I found it have an direct upload approach. That said, adapting to this will mean dropping the currect RTD CI-workflow entirely and requiring a
READTHEDOCS_TOKEN.