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

optimize: fix build action warning #5944

Merged
merged 2 commits into from
Oct 20, 2023

Conversation

leizhiyuan
Copy link
Contributor

@leizhiyuan leizhiyuan commented Oct 20, 2023

  • I have registered the PR changes.

Ⅰ. Describe what this PR did

Ⅱ. Does this pull request fix one issue?

fixes #5943

Ⅲ. Why don't you add test cases (unit test/integration test)?

Ⅳ. Describe how to verify it

run the action

Ⅴ. Special notes for reviews

@@ -54,7 +54,7 @@ jobs:
# step 2
- name: "Set up QEMU"
id: qemu
uses: docker/setup-qemu-action@v1
uses: docker/setup-qemu-action@v3
Copy link
Member

Choose a reason for hiding this comment

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

The build_arm64-binary action only works on push events, so there is no way to confirm that this issue has been resolved until this PR merge. Therefore, I propose to temporarily add build_arm64-binary action to pull request in this PR and remove it after confirming that there is no problem.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Copy link
Contributor Author

Choose a reason for hiding this comment

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

https://github.com/leizhiyuan/seata/actions/runs/6582999974 (to speed up)

the waring has been resolved, To accelerate the verification process, I mock some command scripts that are unrelated to warnings.

Copy link
Member

Choose a reason for hiding this comment

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

ok, it seems to be working fine.

Copy link
Member

@slievrly slievrly left a comment

Choose a reason for hiding this comment

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

LGTM

@codecov
Copy link

codecov bot commented Oct 20, 2023

Codecov Report

Merging #5944 (c609540) into 2.x (e3bfb6c) will decrease coverage by 0.02%.
The diff coverage is n/a.

Additional details and impacted files

Impacted file tree graph

@@             Coverage Diff              @@
##                2.x    #5944      +/-   ##
============================================
- Coverage     49.77%   49.76%   -0.02%     
+ Complexity     4543     4540       -3     
============================================
  Files           854      854              
  Lines         29880    29880              
  Branches       3660     3660              
============================================
- Hits          14874    14870       -4     
- Misses        13517    13519       +2     
- Partials       1489     1491       +2     

see 5 files with indirect coverage changes

Copy link
Contributor

@wangliang181230 wangliang181230 left a comment

Choose a reason for hiding this comment

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

LGTM

@wangliang181230 wangliang181230 merged commit 5aca41d into apache:2.x Oct 20, 2023
8 checks passed
@wangliang181230
Copy link
Contributor

Does the develop branch also have this problem?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

github actions is deprecated and will be disabled soon
3 participants