update TiFlash proxy to raftstore-proxy-6.0 for up(down)grade test

[CalvinNeo]

Signed-off-by: CalvinNeo [email protected]

What problem does this PR solve?

Issue Number: ref #4618

Problem Summary:

Though we have already passed all test cases, we still have to check whether there are problems when TiFlash is updated from any versions to versions using proxy 6.0, before we merge PR pingcap/tidb-engine-ext#55.

As the automated procedure to do this needs new proxy be used by TiFlash at master branch, so we have this PR.

After this test is completed, we will then merge proxy's PR to the main branch, thus redirect TiFlash's proxy to main branch.

What is changed and how it works?

Check List

Tests

• Unit test
• Integration test
• Manual test (add detailed scripts or steps below)
• No code

Side effects

• Performance regression: Consumes more CPU
• Performance regression: Consumes more Memory
• Breaking backward compatibility

Documentation

• Affects user behaviors
• Contains syntax changes
• Contains variable changes
• Contains experimental features
• Changes MySQL compatibility

Release note

None

[ti-chi-bot]

[REVIEW NOTIFICATION]

This pull request has been approved by:

• jiaqizho
• solotzg

To complete the pull request process, please ask the reviewers in the list to review by filling /cc @reviewer in the comment.
After your PR has acquired the required number of LGTMs, you can assign this pull request to the committer in the list by filling /assign @committer in the comment to help you merge this pull request.

The full list of commands accepted by this bot can be found here.

Reviewer can indicate their review by submitting an approval review.
Reviewer can cancel approval by submitting a request changes review.

[CalvinNeo]

/cc @solotzg @flowbehappy

[CalvinNeo]

/run-all-tests

[sre-bot]

Coverage for changed files

no c/c++ source change detected

Coverage summary

Functions  MissedFunctions  Executed  Lines   MissedLines  Cover
17250      9408             45.46%    194273  95797        50.69%

full coverage report (for internal network access only)

[CalvinNeo]

/cc @jiaqizho

[CalvinNeo]

/merge

[ti-chi-bot]

@CalvinNeo: It seems you want to merge this PR, I will help you trigger all the tests:

/run-all-tests

You only need to trigger /merge once, and if the CI test fails, you just re-trigger the test that failed and the bot will merge the PR for you after the CI passes.

If you have any questions about the PR merge process, please refer to pr process.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the ti-community-infra/tichi repository.

[ti-chi-bot]

This pull request has been accepted and is ready to merge.

Commit hash: 2170b0f

[sre-bot]

Coverage for changed files

no c/c++ source change detected

Coverage summary

Functions  MissedFunctions  Executed  Lines   MissedLines  Cover
17250      9408             45.46%    194273  95784        50.70%

full coverage report (for internal network access only)

[CalvinNeo]

/run-all-tests

[sre-bot]

Coverage for changed files

no c/c++ source change detected

Coverage summary

Functions  MissedFunctions  Executed  Lines   MissedLines  Cover
17257      9415             45.44%    194309  95819        50.69%

full coverage report (for internal network access only)

[breezewish]

In my M1 Pro I experienced compiling error since this PR:

= note: ld: warning: directory not found for option '-L/Users/breezewish/Work/tiflash/contrib/tiflash-proxy/target/debug/build/libz-sys-981451fd99e28b0e/out/build'
          Undefined symbols for architecture arm64:
            "_SSL_get_peer_certificate", referenced from:
                ssl_handshaker_result_extract_peer(tsi_handshaker_result const*, tsi_peer*) in libgrpcio_sys-57002017520551a2.rlib(ssl_transport_security.cc.o)
          ld: symbol(s) not found for architecture arm64
          clang: error: linker command failed with exit code 1 (use -v to see invocation)

However I can compile successfully in TiKV master branch. Do you have any ideas?