Solve docs build issues - using different CI machine #564
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This was referenced Jun 28, 2022
mkundu1
approved these changes
Jun 28, 2022
seanpearsonuk
approved these changes
Jun 28, 2022
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
I have seen that the docs build was failing frequently lately.
This is due to the fact that your workflow is sometimes using the PyDIsco VM as a self-hosted runner. I have added a new tag to your pyfluent-ci-1 VM called "pyfluent". This has also occured with PyAEDT. By adding this tag to your workflow, we will force it to choose the adequate VM.
As new VMs appear as self-hosted runners for different projects, it is important that these self-hosted runners also have specific tags for each project: pyfluent, pymapdl, pyaedt, pydisco etc. And we should force the workflows to use their dedicated VMs (the PyDisco VM may not be suited for running your workflows and viceversa).