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

fix fuzzer extract message error #3899

Merged
merged 1 commit into from Jun 13, 2022

Conversation

vincentgoat
Copy link
Member

@vincentgoat vincentgoat commented Jun 6, 2022

Signed-off-by: vincentgoat linguohui1@huawei.com

What type of PR is this?

/kind bug

What this PR does / why we need it:
To address the oss-fuzz issue

cc @AdamKorcz

Which issue(s) this PR fixes:

Fixes #

Special notes for your reviewer:

Does this PR introduce a user-facing change?:


@kubeedge-bot kubeedge-bot added the kind/bug Categorizes issue or PR as related to a bug. label Jun 6, 2022
@kubeedge-bot kubeedge-bot added the size/M Denotes a PR that changes 30-99 lines, ignoring generated files. label Jun 6, 2022
@gy95
Copy link
Member

gy95 commented Jun 6, 2022

keadm e2e fails just as #3894 (comment)

@vincentgoat vincentgoat force-pushed the fuzzer_extractMsg branch 3 times, most recently from 6ef5a91 to ad88818 Compare June 7, 2022 01:52
@vincentgoat
Copy link
Member Author

image
Check build passed.

@AdamKorcz
Copy link
Contributor

image Check build passed.

From the OSS-Fuzz side, LGTM.

@gy95
Copy link
Member

gy95 commented Jun 9, 2022

please rebase the upstream master to fix CI :) @vincentgoat

Signed-off-by: vincentgoat <linguohui1@huawei.com>
@vincentgoat
Copy link
Member Author

please rebase the upstream master to fix CI :) @vincentgoat

Thanks. Done

@vincentgoat vincentgoat closed this Jun 9, 2022
@vincentgoat vincentgoat reopened this Jun 9, 2022
@fisherxu
Copy link
Member

image Check build passed.

From the OSS-Fuzz side, LGTM.

Is it needed to have the check in CI? cc @vincentgoat @AdamKorcz

Copy link
Member

@fisherxu fisherxu left a comment

Choose a reason for hiding this comment

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

/lgtm
/approve

@kubeedge-bot kubeedge-bot added the lgtm Indicates that a PR is ready to be merged. label Jun 13, 2022
@kubeedge-bot
Copy link
Collaborator

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: fisherxu

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

The pull request process is described here

Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@kubeedge-bot kubeedge-bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Jun 13, 2022
@kubeedge-bot kubeedge-bot merged commit ea23549 into kubeedge:master Jun 13, 2022
19 of 20 checks passed
kubeedge-bot added a commit that referenced this pull request Jun 21, 2022
…899-upstream-release-1.9

Automated cherry pick of #3899: fix fuzzer extract message error
kubeedge-bot added a commit that referenced this pull request Jun 21, 2022
…899-upstream-release-1.10

Automated cherry pick of #3899: fix fuzzer extract message error
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
approved Indicates a PR has been approved by an approver from all required OWNERS files. kind/bug Categorizes issue or PR as related to a bug. lgtm Indicates that a PR is ready to be merged. size/M Denotes a PR that changes 30-99 lines, ignoring generated files.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

5 participants