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
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.
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.
@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 ?
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.
The text was updated successfully, but these errors were encountered: