A work flow to run secondary configurations every night - currently only MacOS #267
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
…to run MacOS but could also include other flavors of linux and some perf tests. This is meant to run on a schedule (nightly) and doesn't matter if files changed or not.
TalZaccai
approved these changes
Apr 12, 2024
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
These secondary configurations could be not only MacOS (which is set up for now) but could also include other flavors of Linux and some perf tests. This is meant to run on a schedule (nightly) and doesn't matter if files changed or not. The tests that are ran are Garnet, Garnet Cluster and Tsvaorite.
NOTE: This work flow has been ran in a private fork and there are test failures in all three areas, so it is recommended that this will be "disabled" until we get tests fixed. However, I feel it is a good idea to get this merged and in place so when devs start fixing the test failures, they will have the workflow available to verify their fixes.