Adding important note in the testbed configuration #24
Conversation
This file contains 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
removing unused file adjusting KUBECONFIG setting in Usage section adding an important note about architecture configuration
frisso
reviewed
Dec 6, 2023
frisso
reviewed
Dec 6, 2023
frisso
reviewed
Dec 7, 2023
frisso
reviewed
Dec 7, 2023
frisso
reviewed
Dec 7, 2023
frisso
reviewed
Dec 7, 2023
frisso
approved these changes
Dec 7, 2023
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Dear all,
I'm submitting this pull request to introduce a crucial note during the flavour creation phase using the provided sample solver.yaml.
This note serves as guidance for users, prompting them to select the appropriate architecture value based on their local machine architecture, ensuring the smooth functionality of the testbed.
Failure to adhere to this requirement may result in users encountering difficulties in running the testbed case, as they won't find any suitable peering candidate capable of fulfilling the request.
Thank you for your attention.
I welcome any feedback and look forward to your insights.
Best regards,
Francesco