Сборка документа GitHub Actions не удалась в разветвленном репозитории pandas, но завершилась успешно локально и в восхо ⇐ Python

[Anonymous]

I’m getting started with contributing to pandas and began by looking at issues under the Docs label.
I’ve successfully forked the pandas repository, set up the local development environment, and I’m able to build the documentation locally without any errors. However, when I try to run the GitHub Actions workflow in my fork—specifically the “Doc Build and Upload” workflow—the build consistently fails.
What’s confusing is that:

• The same workflow succeeds in the upstream pandas repository
• The exact doc build command used in CI works locally
• I haven’t modified the failing documentation file

Despite debugging, I haven’t been able to identify why the workflow fails only in my forked repository.
What are the common reasons GitHub Actions doc builds might fail in a fork but pass locally and in the upstream репо? Are there any fork-specific CI limitations or configuration differences I should be aware of?
Traceback
=========

File "/home/runner/micromamba/envs/test/lib/python3.11/site-packages/sphinx/util/parallel.py", line 137, in _join_one
raise SphinxParallelError(*result)
sphinx.errors.SphinxParallelError: RuntimeError: Unexpected warning in `/home/runner/work/pandas/pandas/doc/source/development/internals.rst` line 69

The full traceback has been saved in:
/tmp/sphinx-err-gle2bs7i.log

To report this error to the developers, please open an issue at . Thanks!
Please also report this if it was a user error, so that a better error message can be provided next time.
Error: Process completed with exit code 2.


Подробнее здесь: https://stackoverflow.com/questions/798 ... lly-and-in