pkg/tso: add go trace information for tso allocation

[tiancaiamao]

What problem does this PR solve?

Issue Number: Close #4399

What is changed and how does it work?

Add some trace annotation so 'go tool trace' can show the execution tracing information.

Check List

Tests

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

curl 'http://127.0.0.1:2379/pd/api/v1/debug/pprof/trace?seconds=3' > trace.out
go tool trace -http=:6060 trace.out

And observe the trace result on the web.

• No code

Code changes

• Has the configuration change
• Has HTTP API interfaces changed (Don't forget to add the declarative for the new API)
• Has persistent data change

Side effects

• Possible performance regression
• Increased code complexity
• Breaking backward compatibility

Related changes

• PR to update pingcap/docs/pingcap/docs-cn:
• PR to update pingcap/tiup:
• Need to cherry-pick to the release branch

Release note

None.

[ti-chi-bot]

[REVIEW NOTIFICATION]

This pull request has been approved by:

• lhy1024
• nolouch

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.

[ti-chi-bot]

Hi @tiancaiamao. Thanks for your PR.

I'm waiting for a tikv member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

I understand the commands that are listed here.

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 kubernetes/test-infra repository.

[tiancaiamao]

PTAL @lhy1024 @nolouch @rleungx

[codecov]

Codecov Report

Merging #6884 (f153616) into master (27a3cc5) will decrease coverage by 0.03%.
Report is 1 commits behind head on master.
The diff coverage is 86.20%.

❗ Current head f153616 differs from pull request most recent head 19d92ff. Consider uploading reports for the commit 19d92ff to get more accurate results

Additional details and impacted files

@@            Coverage Diff             @@
##           master    #6884      +/-   ##
==========================================
- Coverage   74.05%   74.02%   -0.03%     
==========================================
  Files         428      420       -8     
  Lines       45088    44204     -884     
==========================================
- Hits        33390    32724     -666     
+ Misses       8737     8575     -162     
+ Partials     2961     2905      -56     

Flag	Coverage Δ
unittests	74.02% <86.20%> (-0.03%)	⬇️

Flags with carried forward coverage won't be shown. Click here to find out more.

[lhy1024]

ci failed with not enough arguments in call to allocator.GenerateTSO in tests/server/tso/allocator_test.go

[lhy1024]

/ok-to-test

[nolouch]

/merge

[ti-chi-bot]

@nolouch: 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: f153616

[ti-chi-bot]

@tiancaiamao: Your PR was out of date, I have automatically updated it for you.

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.

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.