-
Notifications
You must be signed in to change notification settings - Fork 5.9k
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
*: improve makefile #41399
*: improve makefile #41399
Conversation
Signed-off-by: Weizhen Wang <[email protected]>
[REVIEW NOTIFICATION] This pull request has been approved by:
To complete the pull request process, please ask the reviewers in the list to review by filling The full list of commands accepted by this bot can be found here. Reviewer can indicate their review by submitting an approval review. |
@@ -31,7 +31,7 @@ dev: checklist check explaintest gogenerate br_unit_test test_part_parser_dev ut | |||
# Install the check tools. | |||
check-setup:tools/bin/revive | |||
|
|||
check: parser_yacc check-parallel lint tidy testSuite errdoc license check-bazel-prepare | |||
check: check-bazel-prepare parser_yacc check-parallel lint tidy testSuite errdoc license |
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.
It is a more common problem that developers forget to run make bazel_prepare
.
@@ -409,7 +409,7 @@ bazel_test: failpoint-enable bazel_ci_prepare | |||
-//tests/globalkilltest/... -//tests/readonlytest/... -//br/pkg/task:task_test | |||
|
|||
|
|||
bazel_coverage_test: failpoint-enable bazel_ci_prepare | |||
bazel_coverage_test: check-bazel-prepare failpoint-enable bazel_ci_prepare |
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.
If forget to make bazel_prepare
. Please stop to run ut.
/merge |
This pull request has been accepted and is ready to merge. Commit hash: 9352a8b
|
Signed-off-by: Weizhen Wang [email protected]
What problem does this PR solve?
Issue Number: close #xxx
Problem Summary:
What is changed and how it works?
Check List
Tests
Side effects
Documentation
Release note
Please refer to Release Notes Language Style Guide to write a quality release note.