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

tests: use python3 to run http_api test to fix failed integration_tests (#5473) #5479

Conversation

ti-chi-bot
Copy link
Member

This is an automated cherry-pick of #5473

What problem does this PR solve?

Issue Number: close #5474

What is changed and how it works?

Our CI envs still default to python2 to run tests. http_api requires using requests which brings certifi. Actually certifi's recent releases doesn't support python2 any more.

Release note

None

@ti-chi-bot
Copy link
Member Author

[REVIEW NOTIFICATION]

This pull request has not been approved.

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 ti-chi-bot added the release-note-none Denotes a PR that doesn't merit a release note. label May 19, 2022
@ti-chi-bot ti-chi-bot added size/S Denotes a PR that changes 10-29 lines, ignoring generated files. status/LGT2 Indicates that a PR has LGTM 2. type/cherry-pick-for-release-6.0 This PR is cherry-picked to release-6.0 from a source PR. labels May 19, 2022
@zhangyangyu
Copy link
Member

/run-all-tests

@zhangyangyu
Copy link
Member

/run-all-tests

@zhangyangyu
Copy link
Member

/run-kafka-integration-test

@zhangyangyu
Copy link
Member

/run-verify

@zhangyangyu
Copy link
Member

/run-verify

@codecov-commenter
Copy link

codecov-commenter commented May 20, 2022

Codecov Report

❗ No coverage uploaded for pull request base (release-6.0@2f363f6). Click here to learn what that means.
The diff coverage is n/a.

Flag Coverage Δ
cdc 60.9495% <0.0000%> (?)
dm 51.8829% <0.0000%> (?)

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

@@               Coverage Diff                @@
##             release-6.0      #5479   +/-   ##
================================================
  Coverage               ?   55.9046%           
================================================
  Files                  ?        524           
  Lines                  ?      66905           
  Branches               ?          0           
================================================
  Hits                   ?      37403           
  Misses                 ?      25827           
  Partials               ?       3675           

@Rustin170506
Copy link
Member

/merge

@ti-chi-bot
Copy link
Member Author

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

Commit hash: 9c023ad

@ti-chi-bot ti-chi-bot added the status/can-merge Indicates a PR has been approved by a committer. label May 20, 2022
@VelocityLight
Copy link

This pull request is closed because it's related version has closed automatic cherry-picking.
If it's still needed, you can reopen it or just regenerate it using bot,
see:

You can find more details at:

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
do-not-merge/cherry-pick-not-approved release-note-none Denotes a PR that doesn't merit a release note. size/S Denotes a PR that changes 10-29 lines, ignoring generated files. status/can-merge Indicates a PR has been approved by a committer. status/LGT2 Indicates that a PR has LGTM 2. type/cherry-pick-for-release-6.0 This PR is cherry-picked to release-6.0 from a source PR.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants