Skip to content

Read the Docs build times out while compiling ABACUS to generate parameter documentation #8171

Open

Description

@Flying-dragon-boxing

Description

The abacus-rtd Read the Docs build for PR #8093 timed out before reaching Sphinx.

Where it stopped

CMake configuration succeeded with MPI and LCAO disabled:

cmake -Bbuild -GNinja -DCMAKE_INSTALL_PREFIX=install -DENABLE_MPI=OFF -DENABLE_LCAO=OFF

The build was terminated during:

cmake --build build --target install -j $(nproc)

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:

install/bin/abacus --generate-parameters-yaml > docs/parameters.yaml
python3 docs/generate_input_main.py docs/parameters.yaml

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.

Activity

  1. Growl1234 commented on Oct 18, 2026

    @Growl1234

    ... 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.

  2. Growl1234 commented on Oct 18, 2026

    @Growl1234

    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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions