Fix building docs

[artbataev]

Important

The Update branch button must only be pressed in very rare occassions.
An outdated branch is never blocking the merge of a PR.
Please reach out to the automation team before pressing that button.

What does this PR do ?

Fix broken docs build.
E.g.: https://github.com/NVIDIA-NeMo/NeMo/actions/runs/23453370171/job/68236176085?pr=15447 (broken pipeline)

• Fix numba-cuda and cuda-python installation and usage #15506 added (intentionally) mutually exclusive cu12 and cu13 options (the user should select explicitly CUDA version, it cannot be determined by pip automatically)
• the new workflow tried to install all dependencies -> failure

Solution:

• added explicitly requirements to build the documentation
• removed mocking for test requirements: mocked coverage throws an error with numba, which results in broken docs build

Changelog

• Add specific line by line info of high level changes in this PR.

Usage

• You can potentially add a usage example below

# Add a code snippet demonstrating how to use this 

GitHub Actions CI

The Jenkins CI system has been replaced by GitHub Actions self-hosted runners.

The GitHub Actions CI will run automatically when the "Run CICD" label is added to the PR.
To re-run CI remove and add the label again.
To run CI on an untrusted fork, a NeMo user with write access must first click "Approve and run".

Before your PR is "Ready for review"

Pre checks:

• Make sure you read and followed Contributor guidelines
• Did you write any new necessary tests?
• Did you add or update any necessary documentation?
• Does the PR affect components that are optional to install? (Ex: Numba, Pynini, Apex etc)
  • Reviewer: Does the PR have correct import guards for all optional libraries?

PR Type:

• New Feature
• Bugfix
• Documentation

If you haven't finished some of the above items you can still open "Draft" PR.

Who can review?

Anyone in the community is free to review the PR once the checks have passed.
Contributor guidelines contains specific people who can review PRs to various areas.

Additional Information

• Related to # (issue)

[coderabbitai]

Caution

Review failed

An error occurred during the review process. Please try again later.

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch vbataev/fix_docs

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[artbataev]

/claude review

[claude]

LGTM

[artbataev]

@chtruong814 Is the issue fully fixed in #15548 ?
If everything is working after that PR, we can close this one.

[artbataev]

@chtruong814 Is the issue fully fixed in #15548 ? If everything is working after that PR, we can close this one.

As I see in #15542 (I merged main into that PR), docs build is still broken in main. So, this PR is still relevant

[pzelasko]

Thanks @artbataev! Let's resolve the conflicts and LGTM.

[artbataev]

Closing since the concurrent PR #15553 fixed the issues with documentation