-
Notifications
You must be signed in to change notification settings - Fork 465
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
Add UX improvements to run-slice Makefile #1077
Conversation
$(PRIME_CMD) >> $(PRIME_LOG_FILE) 2>&1 & | ||
$(REGION_CMD) >> $(REGION_LOG_FILE) 2>&1 & | ||
$(ZONE_CMD) >> $(ZONE_LOG_FILE) 2>&1 & | ||
@nohup $(PRIME_CMD) >> $(PRIME_LOG_FILE) 2>&1 & |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
run slice is invalid, we need to remove it
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
how so?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Even running a slice uses make run-all
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Then why do we have 'run-all' as a make target? We should just have 'run', if there's no longer two run targets to differentiate between.
$(PRIME_CMD) >> $(PRIME_LOG_FILE) 2>&1 & | ||
$(REGION_CMD) >> $(REGION_LOG_FILE) 2>&1 & | ||
$(ZONE_CMD) >> $(ZONE_LOG_FILE) 2>&1 & | ||
@nohup $(PRIME_CMD) >> $(PRIME_LOG_FILE) 2>&1 & |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Even running a slice uses make run-all
@dominant-strategies/core-dev