Skip to content
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

build: use make testSuite to ensure all testSuites enabled #11627

Merged
merged 11 commits into from
Aug 8, 2019

Conversation

SunRunAway
Copy link
Contributor

What problem does this PR solve?

use make testSuite to ensure all testSuites enabled

What is changed and how it works?

add a bash script in ./tools/check/check_testSuite.sh

Check List

Tests

  • Unit test

Code changes

  • None

Side effects

  • The script runs a little slowly.

Related changes

  • None

@SunRunAway SunRunAway added type/bugfix This PR fixes a bug. type/enhancement The issue or PR belongs to an enhancement. component/test labels Aug 5, 2019
@SunRunAway
Copy link
Contributor Author

/run-all-tests

@SunRunAway
Copy link
Contributor Author

/run-all-tests

@codecov
Copy link

codecov bot commented Aug 5, 2019

Codecov Report

Merging #11627 into master will decrease coverage by 0.2176%.
The diff coverage is n/a.

@@               Coverage Diff                @@
##             master     #11627        +/-   ##
================================================
- Coverage   81.4775%   81.2599%   -0.2177%     
================================================
  Files           428        426         -2     
  Lines         92380      92054       -326     
================================================
- Hits          75269      74803       -466     
- Misses        11739      11877       +138     
- Partials       5372       5374         +2

@SunRunAway
Copy link
Contributor Author

/run-all-tests

1 similar comment
@zyxbest
Copy link
Contributor

zyxbest commented Aug 6, 2019

/run-all-tests

@SunRunAway
Copy link
Contributor Author

/run-all-tests

@SunRunAway
Copy link
Contributor Author

/run-unit-test

@@ -37,6 +37,6 @@ func (s *testBackoffSuite) TearDownTest(c *C) {
func (s *testBackoffSuite) TestBackoffWithMax(c *C) {
b := NewBackoffer(context.TODO(), 2000)
err := b.BackoffWithMaxSleep(boTxnLockFast, 30, errors.New("test"))
c.Assert(err, NotNil)
c.Assert(err, IsNil)
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

why this test result is changed?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This test case fails but never runs once before :(

Copy link
Member

@zz-jason zz-jason left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@zz-jason
Copy link
Member

zz-jason commented Aug 6, 2019

How about cherry-pick this commit to the release branch?

@zz-jason
Copy link
Member

zz-jason commented Aug 6, 2019

@SunRunAway Please follow CONTRIBUTING.md to refine the PR title.

@zz-jason zz-jason added the status/LGT1 Indicates that a PR has LGTM 1. label Aug 6, 2019
@SunRunAway SunRunAway changed the title use make testSuite to ensure all testSuites enabled build: use make testSuite to ensure all testSuites enabled Aug 6, 2019
executor/executor_test.go Outdated Show resolved Hide resolved
Copy link
Contributor

@alivxxx alivxxx left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@alivxxx alivxxx added status/can-merge Indicates a PR has been approved by a committer. and removed status/PTAL labels Aug 8, 2019
@alivxxx alivxxx added status/LGT2 Indicates that a PR has LGTM 2. and removed status/LGT1 Indicates that a PR has LGTM 1. labels Aug 8, 2019
@sre-bot
Copy link
Contributor

sre-bot commented Aug 8, 2019

/run-all-tests

@sre-bot sre-bot merged commit 554594b into pingcap:master Aug 8, 2019
@sre-bot
Copy link
Contributor

sre-bot commented Aug 8, 2019

cherry pick to release-2.1 failed

@sre-bot
Copy link
Contributor

sre-bot commented Aug 8, 2019

cherry pick to release-3.0 in PR #11685

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
component/build component/test status/can-merge Indicates a PR has been approved by a committer. status/LGT2 Indicates that a PR has LGTM 2. type/bugfix This PR fixes a bug. type/enhancement The issue or PR belongs to an enhancement.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants