Skip to content
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

Debugging read the docs build flow could be easier #2650

Open
valentinThomazic opened this issue Dec 4, 2024 · 4 comments
Open

Debugging read the docs build flow could be easier #2650

valentinThomazic opened this issue Dec 4, 2024 · 4 comments
Assignees
Labels
Component:Doc For issues in the Documentation (e.g. for README.md files)

Comments

@valentinThomazic
Copy link
Contributor

The build of read the docs has been broken for about a month because of an incorrect configuration and the local build (running make -C docs was also broken during a week.

The local build has been fixed by #2641
The read the docs build still needs fixing (in progress : #2641 #2643).

Currently, the only way I have found to debug efficiently is to fork the cva6 repo and to setup read the docs on the fork.

There is an option in Read the Docs enabling the build on each pull request as a Github action. This would not only make debugging easier but would also prevent merging commits that break the documentation build while providing a preview of what is to be merged when the build is successful.

Here is the (read the docs) documentation about this feature: feature feature configuration

Of course, it is up to OpenHW Group to decide wether they want to do that or not, since this would trigger more builds.

@valentinThomazic
Copy link
Contributor Author

@MikeOpenHWGroup would you mind taking a look at this issue ?

@MikeOpenHWGroup MikeOpenHWGroup added the Component:Doc For issues in the Documentation (e.g. for README.md files) label Dec 4, 2024
@MikeOpenHWGroup
Copy link
Member

It seems the problem was caused by pull-request #2558, which included this update to .readthedocs.yaml.

Hi @JeanRochCoulon, I am not currently set-up to support the CVA6 RTD flow. Someone with the GitHub handle slgth created the PR above. @valentinThomazic suggested slgth is a person named Simon from Thales SIX, but as they are not a member of this repo I cannot assign this Issue to them.

@JeanRochCoulon
Copy link
Contributor

Simondoes not work anymore on cva6 project, maybe @ASintzoff can have a look from next Monday (oOo currently).

@JeanRochCoulon
Copy link
Contributor

@MikeOpenHWGroup In the meantime, the option pointed by @valentinThomazic can highly prevent such a issue generation. Would it be possible to enable it in ReadTheDocs ?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Component:Doc For issues in the Documentation (e.g. for README.md files)
Projects
None yet
Development

No branches or pull requests

3 participants